CVE-2024-49869

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-10-21. 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-43823 (ENISA EUVD) · GHSA-gcv4-6hmh-xhwc (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: send: fix buffer overflow detection when copying path to cache entry

Starting with commit c0247d289e73 ("btrfs: send: annotate struct name_cache_entry with __counted_by()") we annotated the variable length array "name" from the name_cache_entry structure with __counted_by() to improve overflow detection. However that alone was not correct, because the length of that array does not match the "name_len" field - it matches that plus 1 to include the NUL string terminator, so that makes a fortified kernel think there's an overflow and report a splat like this:

strcpy: detected buffer overflow: 20 byte write of buffer size 19 WARNING: CPU: 3 PID: 3310 at __fortify_report+0x45/0x50 CPU: 3 UID: 0 PID: 3310 Comm: btrfs Not tainted 6.11.0-prnet #1 Hardware name: CompuLab Ltd. sbc-ihsw/Intense-PC2 (IPC2), BIOS IPC2_3.330.7 X64 03/15/2018 RIP: 0010:__fortify_report+0x45/0x50 Code: 48 8b 34 (...) RSP: 0018:ffff97ebc0d6f650 EFLAGS: 00010246 RAX: 7749924ef60fa600 RBX: ffff8bf5446a521a RCX: 0000000000000027 RDX: 00000000ffffdfff RSI: ffff97ebc0d6f548 RDI: ffff8bf84e7a1cc8 RBP: ffff8bf548574080 R08: ffffffffa8c40e10 R09: 0000000000005ffd R10: 0000000000000004 R11: ffffffffa8c70e10 R12: ffff8bf551eef400 R13: 0000000000000000 R14: 0000000000000013 R15: 00000000000003a8 FS: 00007fae144de8c0(0000) GS:ffff8bf84e780000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007fae14691690 CR3: 00000001027a2003 CR4: 00000000001706f0 Call Trace: ? __warn+0x12a/0x1d0 ? __fortify_report+0x45/0x50 ? report_bug+0x154/0x1c0 ? handle_bug+0x42/0x70 ? exc_invalid_op+0x1a/0x50 ? asm_exc_invalid_op+0x1a/0x20 ? __fortify_report+0x45/0x50 __fortify_panic+0x9/0x10 __get_cur_name_and_parent+0x3bc/0x3c0 get_cur_path+0x207/0x3b0 send_extent_data+0x709/0x10d0 ? find_parent_nodes+0x22df/0x25d0 ? mas_nomem+0x13/0x90 ? mtree_insert_range+0xa5/0x110 ? btrfs_lru_cache_store+0x5f/0x1e0 ? iterate_extent_inodes+0x52d/0x5a0 process_extent+0xa96/0x11a0 ? __pfx_lookup_backref_cache+0x10/0x10 ? __pfx_store_backref_cache+0x10/0x10 ? __pfx_iterate_backrefs+0x10/0x10 ? __pfx_check_extent_item+0x10/0x10 changed_cb+0x6fa/0x930 ? tree_advance+0x362/0x390 ? memcmp_extent_buffer+0xd7/0x160 send_subvol+0xf0a/0x1520 btrfs_ioctl_send+0x106b/0x11d0 ? __pfx___clone_root_cmp_sort+0x10/0x10 _btrfs_ioctl_send+0x1ac/0x240 btrfs_ioctl+0x75b/0x850 __se_sys_ioctl+0xca/0x150 do_syscall_64+0x85/0x160 ? __count_memcg_events+0x69/0x100 ? handle_mm_fault+0x1327/0x15c0 ? __se_sys_rt_sigprocmask+0xf1/0x180 ? syscall_exit_to_user_mode+0x75/0xa0 ? do_syscall_64+0x91/0x160 ? do_user_addr_fault+0x21d/0x630 entry_SYSCALL_64_after_hwframe+0x76/0x7e RIP: 0033:0x7fae145eeb4f Code: 00 48 89 (...) RSP: 002b:00007ffdf1cb09b0 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX: 0000000000000004 RCX: 00007fae145eeb4f RDX: 00007ffdf1cb0ad0 RSI: 0000000040489426 RDI: 0000000000000004 RBP: 00000000000078fe R08: 00007fae144006c0 R09: 00007ffdf1cb0927 R10: 0000000000000008 R11: 0000000000000246 R12: 00007ffdf1cb1ce8 R13: 0000000000000003 R14: 000055c499fab2e0 R15: 0000000000000004

Fix this by not storing the NUL string terminator since we don't actually need it for name cache entries, this way "name_len" corresponds to the actual size of the "name" array. This requires marking the "name" array field with __nonstring and using memcpy() instead of strcpy() as recommended by the guidelines at:

https://github.com/KSPP/linux/issues/90

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

October 21, 2024

Last Modified

October 24, 2024

Advisory Details (2)

Auto-updated Oct 1, 2026
Patch available.
Web page

btrfs: send: fix buffer overflow detection when copying path to cache entry - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/96c6ca71572a3556ed0c37237305657ff47174b7
Web page

btrfs: send: fix buffer overflow detection when copying path to cache entry - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/843738ede6cb8b959fb22591fcbabe8b456d7216

Patch Availability(4)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-oem-24.04b (6.11.0-1015.15) @ noble2026-10-27ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.11.0-18.18) @ oracular2026-10-27ubuntu
ubuntulinux-tools-realtime-hwe-24.04-edge (6.11.0-1005.5) @ oracular2026-10-27ubuntu
linuxKernel @ 6.11.3 (fixes >=6.11.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

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

Weakness Classification(1)

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

All Vendor Advisories

(3)

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 9× in last 7d / 40× 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 94 of 216 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. 6 repeat rows among the latest 100 are merged into the row they repeat. The 122 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2024-49869?
CVE-2024-49869 is a high-severity vulnerability; its CVE record was published on October 21, 2024. In the Linux kernel, the following vulnerability has been resolved: btrfs: send: fix buffer overflow detection when copying path to cache entry Starting with commit c0247d289e73 ("btrfs: send: annotate struct name_cache_entry with __counted_by()") we annotated the variable length array "name" from…
When was the CVE record for CVE-2024-49869 published?
The CVE record for CVE-2024-49869 was published on October 21, 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 October 24, 2024; the record at its source may have been updated since.
Is CVE-2024-49869 actively exploited?
CVE-2024-49869 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-49869?
CVE-2024-49869 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2024-49869?
A fix for CVE-2024-49869 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-2024-49869

Explore →

Is Your Infrastructure Affected by CVE-2024-49869?

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

Book a Demo →Browse All CVEs