CVE-2024-26944

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-05-01. 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 — 4 sources updated this week

Also known asEUVD-2024-24206 (ENISA EUVD) · GHSA-phc9-mf56-r5f6 (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:

btrfs: zoned: fix use-after-free in do_zone_finish()

Shinichiro reported the following use-after-free triggered by the device replace operation in fstests btrfs/070.

BTRFS info (device nullb1): scrub: finished on devid 1 with status: 0 ================================================================== BUG: KASAN: slab-use-after-free in do_zone_finish+0x91a/0xb90 [btrfs] Read of size 8 at addr ffff8881543c8060 by task btrfs-cleaner/3494007

CPU: 0 PID: 3494007 Comm: btrfs-cleaner Tainted: G W 6.8.0-rc5-kts #1 Hardware name: Supermicro Super Server/X11SPi-TF, BIOS 3.3 02/21/2020 Call Trace: dump_stack_lvl+0x5b/0x90 print_report+0xcf/0x670 ? __virt_addr_valid+0x200/0x3e0 kasan_report+0xd8/0x110 ? do_zone_finish+0x91a/0xb90 [btrfs] ? do_zone_finish+0x91a/0xb90 [btrfs] do_zone_finish+0x91a/0xb90 [btrfs] btrfs_delete_unused_bgs+0x5e1/0x1750 [btrfs] ? __pfx_btrfs_delete_unused_bgs+0x10/0x10 [btrfs] ? btrfs_put_root+0x2d/0x220 [btrfs] ? btrfs_clean_one_deleted_snapshot+0x299/0x430 [btrfs] cleaner_kthread+0x21e/0x380 [btrfs] ? __pfx_cleaner_kthread+0x10/0x10 [btrfs] kthread+0x2e3/0x3c0 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x31/0x70 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1b/0x30

Allocated by task 3493983: kasan_save_stack+0x33/0x60 kasan_save_track+0x14/0x30 __kasan_kmalloc+0xaa/0xb0 btrfs_alloc_device+0xb3/0x4e0 [btrfs] device_list_add.constprop.0+0x993/0x1630 [btrfs] btrfs_scan_one_device+0x219/0x3d0 [btrfs] btrfs_control_ioctl+0x26e/0x310 [btrfs] __x64_sys_ioctl+0x134/0x1b0 do_syscall_64+0x99/0x190 entry_SYSCALL_64_after_hwframe+0x6e/0x76

Freed by task 3494056: kasan_save_stack+0x33/0x60 kasan_save_track+0x14/0x30 kasan_save_free_info+0x3f/0x60 poison_slab_object+0x102/0x170 __kasan_slab_free+0x32/0x70 kfree+0x11b/0x320 btrfs_rm_dev_replace_free_srcdev+0xca/0x280 [btrfs] btrfs_dev_replace_finishing+0xd7e/0x14f0 [btrfs] btrfs_dev_replace_by_ioctl+0x1286/0x25a0 [btrfs] btrfs_ioctl+0xb27/0x57d0 [btrfs] __x64_sys_ioctl+0x134/0x1b0 do_syscall_64+0x99/0x190 entry_SYSCALL_64_after_hwframe+0x6e/0x76

The buggy address belongs to the object at ffff8881543c8000 which belongs to the cache kmalloc-1k of size 1024 The buggy address is located 96 bytes inside of freed 1024-byte region [ffff8881543c8000, ffff8881543c8400)

The buggy address belongs to the physical page: page:00000000fe2c1285 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x1543c8 head:00000000fe2c1285 order:3 entire_mapcount:0 nr_pages_mapped:0 pincount:0 flags: 0x17ffffc0000840(slab|head|node=0|zone=2|lastcpupid=0x1fffff) page_type: 0xffffffff() raw: 0017ffffc0000840 ffff888100042dc0 ffffea0019e8f200 dead000000000002 raw: 0000000000000000 0000000000100010 00000001ffffffff 0000000000000000 page dumped because: kasan: bad access detected

Memory state around the buggy address: ffff8881543c7f00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ffff8881543c7f80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >ffff8881543c8000: fa fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ^ ffff8881543c8080: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ffff8881543c8100: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb

This UAF happens because we're accessing stale zone information of a already removed btrfs_device in do_zone_finish().

The sequence of events is as follows:

btrfs_dev_replace_start btrfs_scrub_dev btrfs_dev_replace_finishing btrfs_dev_replace_update_device_in_mapping_tree <-- devices replaced btrfs_rm_dev_replace_free_srcdev btrfs_free_device <-- device freed

cleaner_kthread btrfs_delete_unused_bgs btrfs_zone_finish do_zone_finish <-- refers the freed device

The reason for this is that we're using a ---truncated---

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
15th
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

May 1, 2024

Last Modified

August 5, 2026

Advisory Details (2)

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

btrfs: zoned: fix use-after-free in do_zone_finish() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/34ca809e055eca5cfe63d9c7efbf80b7c21b4e57
Web page

btrfs: zoned: fix use-after-free in do_zone_finish() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1ec17ef59168a1a6f1105f5dc517f783839a5302

Vendor Advisories for CVE-2024-26944(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(6)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-gke (6.8.0-1004.7) @ noble2026-10-28ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.8.0-35.35) @ noble2026-10-28ubuntu
ubuntulinux-tools-oracle-64k (6.8.0-1006.6) @ noble2026-10-28ubuntu
ubuntulinux-tools-gcp (6.8.0-1008.9) @ noble2026-10-28ubuntu
ubuntulinux-tools-oem-24.04a (6.8.0-1006.6+1) @ noble2026-10-28ubuntu
linuxKernel @ 6.8.3 (fixes >=5.18.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
linux6.1.106-1 ... 7.2~rc7-1~exp1 (353 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.8.9-1: fixed in 6.8.9-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.8.9-1: fixed in 6.8.9-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(5)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 10× in last 7d / 41× 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 97 of 214 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. 3 repeat rows among the latest 100 are merged into the row they repeat. The 117 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2024-26944?
CVE-2024-26944 is a high-severity vulnerability; its CVE record was published on May 1, 2024. In the Linux kernel, the following vulnerability has been resolved: btrfs: zoned: fix use-after-free in do_zone_finish() Shinichiro reported the following use-after-free triggered by the device replace operation in fstests btrfs/070. BTRFS info (device nullb1): scrub: finished on devid 1 with…
When was the CVE record for CVE-2024-26944 published?
The CVE record for CVE-2024-26944 was published on May 1, 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-2024-26944 actively exploited?
CVE-2024-26944 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (15th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-26944?
CVE-2024-26944 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2024-26944?
A fix for CVE-2024-26944 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-26944 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-26944

Explore →

Is Your Infrastructure Affected by CVE-2024-26944?

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

Book a Demo →Browse All CVEs