Skip to main content
VulnerabilityPublished Updated

CVE-2024-49934: Linux kernel · fs/inode: Prevent dump_mapping() accessing invalid dentry.d_name.name

Source GCVE Database

0
Compare

Not known to be exploited · CVSS 4.6 Medium.

Data as of 30 Oct 2026, 00:40 UTC

CVSS 3.1 base score
4.6Medium
How severe the flaw is on the 0–10 CVSS scale.
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Oct 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

AI-suggested

A fix for this vulnerability is available as it has been resolved in the Linux kernel source. Users should update to a kernel version that includes this fix. Since no vendor advisory or patch links are provided, check the official Linux kernel repositories or distributions for the fixed version. No additional mitigation is indicated.

Description

CVE-2024-49934 is a vulnerability in the Linux kernel's fs/inode subsystem where the dump_mapping() function may access an invalid dentry.d_name.name, leading to a kernel crash. This occurs during hot-removal of a memory device when the user is accessing hugetlb. The issue arises because dump_mapping() attempts to print a filename using '%pd' or strncpy_from_kernel_nofault(), which can be unreliable and cause a page fault. The vulnerability has been resolved by changing dump_mapping() to retrieve the filename in a safer manner to prevent crashes.

References

Community reviews

Loading reviews…