CVE-2024-46780: nilfs2: protect references to superblock parameters exposed in sysfs
In the Linux kernel, the following vulnerability has been resolved:
nilfs2: protect references to superblock parameters exposed in sysfs
The superblock buffers of nilfs2 can not only be overwritten at runtime
for modifications/repairs, but they are also regularly swapped, replaced
during resizing, and even abandoned when degrading to one side due to
backing device issues. So, accessing them requires mutual exclusion using
the reader/writer semaphore "nilfs->ns_sem".
Some sysfs attribute show methods read this superblock buffer without the
necessary mutual exclusion, which can cause problems with pointer
dereferencing and memory access, so fix it.
Security readout for executives and security teams
Plain-English summary
A locking flaw in Linux’s nilfs2 filesystem lets certain sysfs status reads race with superblock replacement or removal. This can leave the kernel using an unsafe reference and cause invalid memory access. The issue requires local, low-privileged access according to the CVSS vector; it is not described as remotely exploitable. Potential impact spans confidentiality, integrity, and availability.
Executive priority
Treat this as a high-priority kernel maintenance issue on multi-user or shared-compute systems using nilfs2. Accelerate remediation where untrusted users or workloads have local access. Other systems should follow normal expedited kernel patching after confirming nilfs2 exposure and vendor package status.
Technical view
nilfs2 superblock buffers can be overwritten, swapped during resizing, replaced, or abandoned after backing-device degradation. Some sysfs attribute show methods read those buffers without holding the nilfs->ns_sem reader/writer semaphore. Concurrent lifecycle changes can therefore produce unsafe pointer dereferences and memory access. The supplied record scores this CVSS 3.1 7.8: AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.
Likely exposure
Exposure is most likely on systems running a listed affected Linux kernel where nilfs2 is in use and its sysfs attributes are accessible. The supplied version data is kernel-oriented and does not establish distribution package fix boundaries. Systems not using nilfs2 are less likely to reach the vulnerable path, but administrators should confirm with their vendor.
Exploitation context
The supplied bundle marks KEV false and provides no evidence of active exploitation or a public proof of concept. The vector indicates a local, low-complexity, low-privilege attack requiring no user interaction. Real-world reliability and prerequisites beyond nilfs2 and concurrent superblock activity are not established here.
Researcher notes
The record describes a missing synchronization control around sysfs reads of mutable nilfs2 superblock buffers. Referenced stable-kernel commits provide the correction. No CWE, proof of concept, crash trace, exploitation telemetry, or distribution-wide fixed-package matrix is supplied. The duplicated commit identifiers and mixed version entries should not be treated as reliable package-level boundaries.
Mitigation direction
Apply a distribution kernel update incorporating the referenced stable-kernel fix, then reboot into the updated kernel.
Confirm package-specific fixed versions with the Linux distribution or vendor advisory before rollout.
Prioritize hosts that use nilfs2 and permit untrusted local accounts or workloads.
Use vendor-recommended temporary mitigations if patching is delayed; none are identified in the supplied bundle.
Validation and detection
Inventory running kernel versions and identify systems using or loading nilfs2.
Map each kernel package to its distribution advisory or a referenced fixed stable commit.
After updating, verify each host booted the intended fixed kernel.
Recheck nilfs2-dependent workloads and monitor kernel logs for memory-access faults.
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-46780 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.