Security readout for executives and security teams
Plain-English summary
An affected Linux kernel can mishandle changing ext4 filesystem metadata and read memory that is no longer valid. The demonstrated result is a kernel use-after-free during a directory operation. This can threaten system stability and, based on the supplied CVSS assessment, confidentiality and integrity. The issue is local rather than remotely reachable by itself.
Executive priority
Address within the normal high-severity kernel patch cycle, accelerating for multi-user systems and environments using loop-backed ext4 storage. The evidence does not support an internet-wide emergency because exploitation is local and active attacks are not reported. Delay only where the vendor confirms the running kernel has a backported fix or is unaffected.
Technical view
CVE-2024-47701 is an ext4 bounds-validation flaw in inline-directory lookup. If the system.data extended attribute’s e_value_offs changes after the inode location is read, ext4_search_dir can access memory out of bounds; KASAN reported a use-after-free. The fix validates the extended attributes immediately after locating the inode and before using them.
Likely exposure
Exposure requires Linux running an affected kernel and using ext4, particularly inline directories on storage whose metadata can change underneath the mounted filesystem. The CVSS vector indicates local, low-privilege access without user interaction, but the evidence does not establish whether low-privilege access alone enables the required storage change. The supplied version data is insufficient for reliable distribution-build mapping.
Exploitation context
The supplied evidence does not support active exploitation, and the bundle marks the CVE as absent from KEV. The failure was demonstrated through syzkaller and KASAN using a QEMU loop device. This proves a kernel memory-safety defect but does not demonstrate reliable real-world compromise.
Researcher notes
The crash occurred on Linux 6.11.0-rc4 during symlink creation after a loop-device capacity change. The source attributes the flaw to e_value_offs changing underneath the filesystem. Stable-branch fixes are linked, but the flattened affected-version list is difficult to interpret. Prefer vendor package mapping over version-string assumptions.
Mitigation direction
Update to a vendor-supported kernel containing the applicable upstream stable fix.
Use distribution or appliance advisories to identify exact fixed packages; the supplied version mapping is ambiguous.
Prioritize ext4 systems accessible to untrusted local users or using mutable loop-backed storage.
If updates are delayed, seek vendor-approved temporary mitigations; none are named in the supplied sources.
Validation and detection
Inventory running kernel builds and ext4 mounts across potentially affected systems.
Map each vendor kernel package to CVE-2024-47701 or an applicable stable fix commit.
After updating and rebooting, confirm the running kernel is vendor-designated as fixed.
Review kernel logs for ext4_search_dir, ext4_find_inline_entry, use-after-free reports, or related crashes.
Confirm remediation records cover affected servers, virtual-machine hosts, and Linux-based appliances.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2024-47701 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.