CVE-2022-48913

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2024-08-22. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this week

Also known asEUVD-2022-53792 (ENISA EUVD) · GHSA-j2cw-jh9j-qmpx (GitHub Security Advisories)Source: ENISA EUVD

7.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

blktrace: fix use after free for struct blk_trace

When tracing the whole disk, 'dropped' and 'msg' will be created under 'q->debugfs_dir' and 'bt->dir' is NULL, thus blk_trace_free() won't remove those files. What's worse, the following UAF can be triggered because of accessing stale 'dropped' and 'msg':

================================================================== BUG: KASAN: use-after-free in blk_dropped_read+0x89/0x100 Read of size 4 at addr ffff88816912f3d8 by task blktrace/1188

CPU: 27 PID: 1188 Comm: blktrace Not tainted 5.17.0-rc4-next-20220217+ #469 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS ?-20190727_073836-4 Call Trace: dump_stack_lvl+0x34/0x44 print_address_description.constprop.0.cold+0xab/0x381 ? blk_dropped_read+0x89/0x100 ? blk_dropped_read+0x89/0x100 kasan_report.cold+0x83/0xdf ? blk_dropped_read+0x89/0x100 kasan_check_range+0x140/0x1b0 blk_dropped_read+0x89/0x100 ? blk_create_buf_file_callback+0x20/0x20 ? kmem_cache_free+0xa1/0x500 ? do_sys_openat2+0x258/0x460 full_proxy_read+0x8f/0xc0 vfs_read+0xc6/0x260 ksys_read+0xb9/0x150 ? vfs_write+0x3d0/0x3d0 ? fpregs_assert_state_consistent+0x55/0x60 ? exit_to_user_mode_prepare+0x39/0x1e0 do_syscall_64+0x35/0x80 entry_SYSCALL_64_after_hwframe+0x44/0xae RIP: 0033:0x7fbc080d92fd Code: ce 20 00 00 75 10 b8 00 00 00 00 0f 05 48 3d 01 f0 ff ff 73 31 c3 48 83 1 RSP: 002b:00007fbb95ff9cb0 EFLAGS: 00000293 ORIG_RAX: 0000000000000000 RAX: ffffffffffffffda RBX: 00007fbb95ff9dc0 RCX: 00007fbc080d92fd RDX: 0000000000000100 RSI: 00007fbb95ff9cc0 RDI: 0000000000000045 RBP: 0000000000000045 R08: 0000000000406299 R09: 00000000fffffffd R10: 000000000153afa0 R11: 0000000000000293 R12: 00007fbb780008c0 R13: 00007fbb78000938 R14: 0000000000608b30 R15: 00007fbb780029c8

Allocated by task 1050: kasan_save_stack+0x1e/0x40 __kasan_kmalloc+0x81/0xa0 do_blk_trace_setup+0xcb/0x410 __blk_trace_setup+0xac/0x130 blk_trace_ioctl+0xe9/0x1c0 blkdev_ioctl+0xf1/0x390 __x64_sys_ioctl+0xa5/0xe0 do_syscall_64+0x35/0x80 entry_SYSCALL_64_after_hwframe+0x44/0xae

Freed by task 1050: kasan_save_stack+0x1e/0x40 kasan_set_track+0x21/0x30 kasan_set_free_info+0x20/0x30 __kasan_slab_free+0x103/0x180 kfree+0x9a/0x4c0 __blk_trace_remove+0x53/0x70 blk_trace_ioctl+0x199/0x1c0 blkdev_common_ioctl+0x5e9/0xb30 blkdev_ioctl+0x1a5/0x390 __x64_sys_ioctl+0xa5/0xe0 do_syscall_64+0x35/0x80 entry_SYSCALL_64_after_hwframe+0x44/0xae

The buggy address belongs to the object at ffff88816912f380 which belongs to the cache kmalloc-96 of size 96 The buggy address is located 88 bytes inside of 96-byte region [ffff88816912f380, ffff88816912f3e0) The buggy address belongs to the page: page:000000009a1b4e7c refcount:1 mapcount:0 mapping:0000000000000000 index:0x0f flags: 0x17ffffc0000200(slab|node=0|zone=2|lastcpupid=0x1fffff) raw: 0017ffffc0000200 ffffea00044f1100 dead000000000002 ffff88810004c780 raw: 0000000000000000 0000000000200020 00000001ffffffff 0000000000000000 page dumped because: kasan: bad access detected

Memory state around the buggy address: ffff88816912f280: fa fb fb fb fb fb fb fb fb fb fb fb fc fc fc fc ffff88816912f300: fa fb fb fb fb fb fb fb fb fb fb fb fc fc fc fc >ffff88816912f380: fa fb fb fb fb fb fb fb fb fb fb fb fc fc fc fc ^ ffff88816912f400: fa fb fb fb fb fb fb fb fb fb fb fb fc fc fc fc ffff88816912f480: fa fb fb fb fb fb fb fb fb fb fb fb fc fc fc fc ==================================================================

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
35
EG Risk 35/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity78% × 45%
Impact severity (EG Severity): CVSS 7.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
11th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.8): severity, escalated by confirmed exploitation. This CVE's 7.8 is its impact severity (EG Severity), not escalated.

EG Severity
7.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-27). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 22, 2024

Last Modified

August 5, 2026

Advisory Details (3)

Auto-updated Aug 5, 2026
Patch available.
Web page

blktrace: fix use after free for struct blk_trace - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/30939293262eb433c960c4532a0d59c4073b2b84
Web page

blktrace: fix use after free for struct blk_trace - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6418634238ade86f2b08192928787f39d8afb58c
Web page

blktrace: fix use after free for struct blk_trace - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/78acc7dbd84a8c173a08584750845c31611160f2

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
linuxKernel @ 5.15.27 (fixes >=5.12.0)—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 5.16.14-1: fixed in 5.16.14-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 5.16.14-1: fixed in 5.16.14-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 5.16.14-1: fixed in 5.16.14-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 39× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 98 of 207 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 2 repeat rows among the latest 100 are merged into the row they repeat. The 109 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-02 16:39 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  2. 2026-11-01 16:30 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  3. 2026-10-31 16:29 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  4. 2026-10-30 16:31 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  5. 2026-10-29 16:30 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  6. 2026-10-28 16:28 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  7. 2026-10-28 15:04 UTCEG score recompute
  8. 2026-10-28 15:04 UTCGHSA enrichmentGHSA-j2cw-jh9j-qmpx · GitHub severity HIGH · GitHub CVSS 7.8
  9. 2026-10-27 16:28 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  10. 2026-10-26 16:28 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  11. 2026-10-25 17:55 UTCEG score recompute
  12. 2026-10-25 16:29 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  13. 2026-10-24 16:29 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  14. 2026-10-23 16:29 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  15. 2026-10-22 16:30 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  16. 2026-10-21 16:29 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  17. 2026-10-21 05:37 UTCEG score recompute
  18. 2026-10-21 05:37 UTCGHSA enrichmentGHSA-j2cw-jh9j-qmpx · GitHub severity HIGH · GitHub CVSS 7.8
  19. 2026-10-20 16:29 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  20. 2026-10-19 16:28 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  21. 2026-10-19 12:25 UTCOSV refresh
  22. 2026-10-18 16:29 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  23. 2026-10-18 08:21 UTCEG score recompute
  24. 2026-10-17 16:29 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  25. 2026-10-16 16:35 UTCEPSS rescoreEPSS 0.2% · 10th percentile
Show 73 more
  1. 2026-10-15 16:28 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  2. 2026-10-14 16:29 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  3. 2026-10-13 16:29 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  4. 2026-10-12 18:42 UTCEG score recompute
  5. 2026-10-12 16:30 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  6. 2026-10-11 22:06 UTCEG score recompute
  7. 2026-10-11 13:45 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  8. 2026-10-10 19:57 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  9. 2026-10-09 20:05 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  10. 2026-10-08 17:05 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  11. 2026-10-07 23:45 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  12. 2026-10-06 15:14 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  13. 2026-10-05 17:40 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  14. 2026-10-04 23:19 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  15. 2026-10-03 14:23 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  16. 2026-09-30 16:11 UTCEG score recompute
  17. 2026-09-30 15:01 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  18. 2026-09-27 13:42 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  19. 2026-09-26 19:33 UTCOSV refresh
  20. 2026-09-26 15:55 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  21. 2026-09-26 00:22 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  22. 2026-09-24 14:00 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  23. 2026-09-23 13:45 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  24. 2026-09-20 20:13 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  25. 2026-09-16 14:05 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  26. 2026-09-16 05:11 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  27. 2026-09-15 03:07 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  28. 2026-09-13 16:44 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  29. 2026-09-11 14:50 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  30. 2026-09-11 09:34 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  31. 2026-09-08 21:57 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  32. 2026-09-07 15:59 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  33. 2026-09-07 04:48 UTCOSV refresh
  34. 2026-09-06 13:45 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  35. 2026-09-05 15:25 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  36. 2026-09-04 13:57 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  37. 2026-09-04 05:04 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  38. 2026-09-02 14:09 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  39. 2026-09-01 13:51 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  40. 2026-08-30 19:15 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  41. 2026-08-30 01:19 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  42. 2026-08-28 21:38 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  43. 2026-08-27 14:22 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  44. 2026-08-26 14:43 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  45. 2026-08-25 13:46 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  46. 2026-08-23 00:17 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  47. 2026-08-21 23:46 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  48. 2026-08-20 22:53 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  49. 2026-08-20 14:31 UTCOSV refresh
  50. 2026-08-19 17:01 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  51. 2026-08-18 13:45 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  52. 2026-08-17 13:44 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  53. 2026-08-16 14:53 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  54. 2026-08-16 02:12 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  55. 2026-08-13 21:58 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  56. 2026-08-12 13:48 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  57. 2026-08-09 13:44 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  58. 2026-08-08 16:34 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  59. 2026-08-07 16:24 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  60. 2026-08-06 13:44 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  61. 2026-08-05 19:15 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  62. 2026-08-05 09:37 UTCEG score recompute
  63. 2026-08-05 09:37 UTCGHSA enrichmentGHSA-j2cw-jh9j-qmpx · GitHub severity HIGH · GitHub CVSS 7.8
  64. 2026-08-04 15:07 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  65. 2026-08-04 11:51 UTCEG score recompute
  66. 2026-08-04 11:51 UTCGHSA enrichmentGHSA-j2cw-jh9j-qmpx · GitHub severity HIGH · GitHub CVSS 7.8
  67. 2026-08-04 10:35 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  68. 2026-08-04 09:48 UTCEG score recompute
  69. 2026-08-04 09:48 UTCGHSA enrichmentGHSA-j2cw-jh9j-qmpx · GitHub severity HIGH · GitHub CVSS 7.8
  70. 2026-08-03 10:33 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  71. 2026-08-02 02:24 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  72. 2026-08-01 04:13 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  73. 2026-07-31 01:34 UTCOSV refresh

Frequently asked(5)

What is CVE-2022-48913?
CVE-2022-48913 is a high-severity vulnerability; its CVE record was published on August 22, 2024. In the Linux kernel, the following vulnerability has been resolved: blktrace: fix use after free for struct blk_trace When tracing the whole disk, 'dropped' and 'msg' will be created under 'q->debugfs_dir' and 'bt->dir' is NULL, thus blk_trace_free() won't remove those files. What's worse, the…
When was the CVE record for CVE-2022-48913 published?
The CVE record for CVE-2022-48913 was published on August 22, 2024. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of August 5, 2026; the record at its source may have been updated since.
Is CVE-2022-48913 actively exploited?
CVE-2022-48913 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (11th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2022-48913?
CVE-2022-48913 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2022-48913?
A fix for CVE-2022-48913 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2022-48913

Explore →

Is Your Infrastructure Affected by CVE-2022-48913?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.