Security readout for executives and security teams
Plain-English summary
A corrupted NILFS2 directory can trigger a Linux kernel fault when it is renamed. Successful triggering could compromise confidentiality, integrity, or availability, but it requires local interaction with an affected NILFS2 filesystem. Systems not using NILFS2 are unlikely to be exposed.
Executive priority
Treat this as a high-priority kernel maintenance issue on NILFS2-using systems, especially those handling less-trusted storage. Prioritize targeted identification and patching rather than organization-wide emergency response. Escalate if NILFS2 use is widespread or affected hosts perform sensitive workloads.
Technical view
nilfs_dotdot() insufficiently validated the “.” and “..” entries in a broken directory. It could return an out-of-page location, causing __block_write_begin_int() to fail a BUG_ON bounds check during rename. The fix validates required entries within the directory’s first chunk.
Likely exposure
Exposure is concentrated on Linux systems running an affected kernel where NILFS2 is enabled and a malformed directory is processed during rename. The supplied CVSS vector indicates local access, low complexity, no privileges, and user interaction. Exact distribution package status requires vendor confirmation.
Exploitation context
CISA KEV status is false, and the supplied sources provide no evidence of active exploitation or a public weaponized exploit. The issue was reported by syzbot. Triggering depends on a broken NILFS2 directory and a rename operation, limiting exposure compared with remotely reachable vulnerabilities.
Researcher notes
The affected-version data includes kernel releases and repeated commit identifiers but does not clearly map every distribution build. Validate exposure against distribution advisories or the referenced stable commits. The source describes a kernel bounds assertion failure; it does not establish a demonstrated path to arbitrary code execution.
Mitigation direction
- Install a vendor-supported kernel package that incorporates the referenced NILFS2 correction.
- Prioritize systems that mount, process, or accept NILFS2 filesystems from less-trusted sources.
- If immediate updating is unavailable, consult distribution guidance for supported temporary mitigations.
- Schedule controlled reboots where required to activate the corrected kernel.
Validation and detection
- Inventory kernel versions and identify hosts where NILFS2 is enabled or mounted.
- Check distribution advisories and package changelogs specifically for CVE-2024-41034.
- Confirm the running kernel, not merely the installed package, contains the correction.
- Retest normal NILFS2 rename operations after updating without using intentionally malformed filesystems.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-2024-41034 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
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.
SSVC decision data
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H1.85.9LinuxVulnerability scoring details
Base CVSS 3.1 score
7.8HighVector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/stable/c/ff9767ba2cb949701e45e6e4287f8af82986b703CVE reference, Linux
- https://git.kernel.org/stable/c/24c1c8566a9b6be51f5347be2ea76e25fc82b11eCVE reference, Linux
- https://git.kernel.org/stable/c/a9a466a69b85059b341239766a10efdd3ee68a4bCVE reference, Linux
- https://git.kernel.org/stable/c/7000b438dda9d0f41a956fc9bffed92d2eb6be0dCVE reference, Linux
- https://git.kernel.org/stable/c/1a8879c0771a68d70ee2e5e66eea34207e8c6231CVE reference, Linux
- https://git.kernel.org/stable/c/60f61514374e4a0c3b65b08c6024dd7e26150bfdCVE reference, Linux
- https://git.kernel.org/stable/c/298cd810d7fb687c90a14d8f9fd1b8719a7cb8a5CVE reference, Linux
- https://git.kernel.org/stable/c/a9e1ddc09ca55746079cc479aa3eb6411f0d99d4CVE reference, Linux
- https://lists.debian.org/debian-lts-announce/2025/01/msg00001.htmlCVE reference, CVE
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.