CVE-2024-49934

MEDIUMNVD 4.64.6
EchelonGraph scoreMEDIUM confidence

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

Score 4.6 from GitHub Security Advisory published 2024-10-21. NVD baseline CVSS 4.6; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
4.6EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 4.6Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

fs/inode: Prevent dump_mapping() accessing invalid dentry.d_name.name

It's observed that a crash occurs during hot-remove a memory device, in which user is accessing the hugetlb. See calltrace as following:

------------[ cut here ]------------ WARNING: CPU: 1 PID: 14045 at arch/x86/mm/fault.c:1278 do_user_addr_fault+0x2a0/0x790 Modules linked in: kmem device_dax cxl_mem cxl_pmem cxl_port cxl_pci dax_hmem dax_pmem nd_pmem cxl_acpi nd_btt cxl_core crc32c_intel nvme virtiofs fuse nvme_core nfit libnvdimm dm_multipath scsi_dh_rdac scsi_dh_emc s mirror dm_region_hash dm_log dm_mod CPU: 1 PID: 14045 Comm: daxctl Not tainted 6.10.0-rc2-lizhijian+ #492 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org 04/01/2014 RIP: 0010:do_user_addr_fault+0x2a0/0x790 Code: 48 8b 00 a8 04 0f 84 b5 fe ff ff e9 1c ff ff ff 4c 89 e9 4c 89 e2 be 01 00 00 00 bf 02 00 00 00 e8 b5 ef 24 00 e9 42 fe ff ff <0f> 0b 48 83 c4 08 4c 89 ea 48 89 ee 4c 89 e7 5b 5d 41 5c 41 5d 41 RSP: 0000:ffffc90000a575f0 EFLAGS: 00010046 RAX: ffff88800c303600 RBX: 0000000000000000 RCX: 0000000000000000 RDX: 0000000000001000 RSI: ffffffff82504162 RDI: ffffffff824b2c36 RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000000 R12: ffffc90000a57658 R13: 0000000000001000 R14: ffff88800bc2e040 R15: 0000000000000000 FS: 00007f51cb57d880(0000) GS:ffff88807fd00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000001000 CR3: 00000000072e2004 CR4: 00000000001706f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: ? __warn+0x8d/0x190 ? do_user_addr_fault+0x2a0/0x790 ? report_bug+0x1c3/0x1d0 ? handle_bug+0x3c/0x70 ? exc_invalid_op+0x14/0x70 ? asm_exc_invalid_op+0x16/0x20 ? do_user_addr_fault+0x2a0/0x790 ? exc_page_fault+0x31/0x200 exc_page_fault+0x68/0x200 <...snip...> BUG: unable to handle page fault for address: 0000000000001000 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page PGD 800000000ad92067 P4D 800000000ad92067 PUD 7677067 PMD 0 Oops: Oops: 0000 [#1] PREEMPT SMP PTI ---[ end trace 0000000000000000 ]--- BUG: unable to handle page fault for address: 0000000000001000 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page PGD 800000000ad92067 P4D 800000000ad92067 PUD 7677067 PMD 0 Oops: Oops: 0000 [#1] PREEMPT SMP PTI CPU: 1 PID: 14045 Comm: daxctl Kdump: loaded Tainted: G W 6.10.0-rc2-lizhijian+ #492 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org 04/01/2014 RIP: 0010:dentry_name+0x1f4/0x440 <...snip...> ? dentry_name+0x2fa/0x440 vsnprintf+0x1f3/0x4f0 vprintk_store+0x23a/0x540 vprintk_emit+0x6d/0x330 _printk+0x58/0x80 dump_mapping+0x10b/0x1a0 ? __pfx_free_object_rcu+0x10/0x10 __dump_page+0x26b/0x3e0 ? vprintk_emit+0xe0/0x330 ? _printk+0x58/0x80 ? dump_page+0x17/0x50 dump_page+0x17/0x50 do_migrate_range+0x2f7/0x7f0 ? do_migrate_range+0x42/0x7f0 ? offline_pages+0x2f4/0x8c0 offline_pages+0x60a/0x8c0 memory_subsys_offline+0x9f/0x1c0 ? lockdep_hardirqs_on+0x77/0x100 ? _raw_spin_unlock_irqrestore+0x38/0x60 device_offline+0xe3/0x110 state_store+0x6e/0xc0 kernfs_fop_write_iter+0x143/0x200 vfs_write+0x39f/0x560 ksys_write+0x65/0xf0 do_syscall_64+0x62/0x130

Previously, some sanity check have been done in dump_mapping() before the print facility parsing '%pd' though, it's still possible to run into an invalid dentry.d_name.name.

Since dump_mapping() only needs to dump the filename only, retrieve it by itself in a safer way to prevent an unnecessary crash.

Note that either retrieving the filename with '%pd' or strncpy_from_kernel_nofault(), the filename could be unreliable.

CVSS v3
4.6
EG Score
4.6MEDIUMmedium confidence
EG Risk
21
EG Risk 21/100

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 (value × EchelonGraph’s weight)
Severity46% × 45%
The EG Score, 4.6 of 10.
Exploitation0.3% × 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.3%
EPSS %ILE
16th
KEV
Not listed

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.

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

August 5, 2026

Vendor Advisories for CVE-2024-49934(2)

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

Patch Availability(17)

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

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (498 versions)
  • every version on: no fix on record
—
linux-6.16.1.106-3~deb11u1, 6.1.106-3~deb11u2, 6.1.106-3~deb11u3, 6.1.112-1~deb11u1, 6.1.119-1~deb11u1
  • every version up to 6.1.128-1~deb11u1: fixed in 6.1.128-1~deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (32 versions)
  • every version up to 6.1.123-1: fixed in 6.1.123-1
—
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
—

Additional Vendor Advisories

(15)

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2024-49934?
CVE-2024-49934 is a medium-severity vulnerability; its CVE record was published on October 21, 2024. In the Linux kernel, the following vulnerability has been resolved: fs/inode: Prevent dumpmapping() accessing invalid dentry.dname.name It's observed that a crash occurs during hot-remove a memory device, in which user is accessing the hugetlb. See calltrace as following: ------------[ cut here…
When was the CVE record for CVE-2024-49934 published?
The CVE record for CVE-2024-49934 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 August 5, 2026; the record at its source may have been updated since.
Is CVE-2024-49934 actively exploited?
CVE-2024-49934 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (16th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-49934?
CVE-2024-49934 has a CVSS v3 base score of 4.6 (NVD).
How do I remediate CVE-2024-49934?
A fix for CVE-2024-49934 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-49934 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-49934

Explore →

Is Your Infrastructure Affected by CVE-2024-49934?

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