CVE-2024-35949

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

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

btrfs: make sure that WRITTEN is set on all metadata blocks

We previously would call btrfs_check_leaf() if we had the check integrity code enabled, which meant that we could only run the extended leaf checks if we had WRITTEN set on the header flags.

This leaves a gap in our checking, because we could end up with corruption on disk where WRITTEN isn't set on the leaf, and then the extended leaf checks don't get run which we rely on to validate all of the item pointers to make sure we don't access memory outside of the extent buffer.

However, since 732fab95abe2 ("btrfs: check-integrity: remove CONFIG_BTRFS_FS_CHECK_INTEGRITY option") we no longer call btrfs_check_leaf() from btrfs_mark_buffer_dirty(), which means we only ever call it on blocks that are being written out, and thus have WRITTEN set, or that are being read in, which should have WRITTEN set.

Add checks to make sure we have WRITTEN set appropriately, and then make sure __btrfs_check_leaf() always does the item checking. This will protect us from file systems that have been corrupted and no longer have WRITTEN set on some of the blocks.

This was hit on a crafted image tweaking the WRITTEN bit and reported by KASAN as out-of-bound access in the eb accessors. The example is a dir item at the end of an eb.

[2.042] BTRFS warning (device loop1): bad eb member start: ptr 0x3fff start 30572544 member offset 16410 size 2 [2.040] general protection fault, probably for non-canonical address 0xe0009d1000000003: 0000 [#1] PREEMPT SMP KASAN NOPTI [2.537] KASAN: maybe wild-memory-access in range [0x0005088000000018-0x000508800000001f] [2.729] CPU: 0 PID: 2587 Comm: mount Not tainted 6.8.2 #1 [2.729] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/01/2014 [2.621] RIP: 0010:btrfs_get_16+0x34b/0x6d0 [2.621] RSP: 0018:ffff88810871fab8 EFLAGS: 00000206 [2.621] RAX: 0000a11000000003 RBX: ffff888104ff8720 RCX: ffff88811b2288c0 [2.621] RDX: dffffc0000000000 RSI: ffffffff81dd8aca RDI: ffff88810871f748 [2.621] RBP: 000000000000401a R08: 0000000000000001 R09: ffffed10210e3ee9 [2.621] R10: ffff88810871f74f R11: 205d323430333737 R12: 000000000000001a [2.621] R13: 000508800000001a R14: 1ffff110210e3f5d R15: ffffffff850011e8 [2.621] FS: 00007f56ea275840(0000) GS:ffff88811b200000(0000) knlGS:0000000000000000 [2.621] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [2.621] CR2: 00007febd13b75c0 CR3: 000000010bb50000 CR4: 00000000000006f0 [2.621] Call Trace: [2.621] [2.621] ? show_regs+0x74/0x80 [2.621] ? die_addr+0x46/0xc0 [2.621] ? exc_general_protection+0x161/0x2a0 [2.621] ? asm_exc_general_protection+0x26/0x30 [2.621] ? btrfs_get_16+0x33a/0x6d0 [2.621] ? btrfs_get_16+0x34b/0x6d0 [2.621] ? btrfs_get_16+0x33a/0x6d0 [2.621] ? __pfx_btrfs_get_16+0x10/0x10 [2.621] ? __pfx_mutex_unlock+0x10/0x10 [2.621] btrfs_match_dir_item_name+0x101/0x1a0 [2.621] btrfs_lookup_dir_item+0x1f3/0x280 [2.621] ? __pfx_btrfs_lookup_dir_item+0x10/0x10 [2.621] btrfs_get_tree+0xd25/0x1910

[ copy more details from report ]

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
35(Track)
EG Risk 35/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
15%
KEV
Not listed

Published

May 20, 2024

Last Modified

August 5, 2026

Advisory Details (4)

Auto-updated Aug 4, 2026
No patch confirmed yet.
generic

[SECURITY] Fedora 40 Update: kernel-6.8.10-300.fc40 - package-announce - Fedora mailing-lists

https://lists.fedoraproject.org/archives/list/[email protected]/message/OTB4HWU2PTVW5NEYHHLOCXDKG3PYA534/
generic

btrfs: make sure that WRITTEN is set on all metadata blocks - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ef3ba8ce8cf7075b716aa4afcefc3034215878ee
generic

btrfs: make sure that WRITTEN is set on all metadata blocks - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/e03418abde871314e1a3a550f4c8afb7b89cb273
generic

btrfs: make sure that WRITTEN is set on all metadata blocks - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9dff3e36ea89e8003516841c27c45af562b6ef44

Patch Availability(5)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-hwe-24.04-edge (6.8.0-40.40) @ noble2026-05-24ubuntu
ubuntulinux-tools-raspi (6.8.0-1009.10) @ noble2026-05-24ubuntu
ubuntulinux-tools-oem-24.04a (6.8.0-1010.10) @ noble2026-05-24ubuntu
ubuntulinux-tools-oracle-64k (6.8.0-1010.10) @ noble2026-05-24ubuntu
linuxKernel @ 6.6.85—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.

Weakness Classification(1)

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

All Vendor Advisories

(4)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 13× in last 7d / 49× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 128 total refreshes for this CVE.

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2024-35949?
CVE-2024-35949 is a high vulnerability published on May 20, 2024. In the Linux kernel, the following vulnerability has been resolved: btrfs: make sure that WRITTEN is set on all metadata blocks We previously would call btrfscheckleaf() if we had the check integrity code enabled, which meant that we could only run the extended leaf checks if we had WRITTEN set on…
When was CVE-2024-35949 disclosed?
CVE-2024-35949 was first published in the National Vulnerability Database on May 20, 2024, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-35949 actively exploited?
CVE-2024-35949 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 85.1% of all scored CVEs.
What is the CVSS score of CVE-2024-35949?
CVE-2024-35949 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2024-35949?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-35949, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2024-35949

Explore →

Is Your Infrastructure Affected by CVE-2024-35949?

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

Start Free Scan →Browse All CVEs