System crash via corrupted NILFS2 inode bitmap
Published Oct 21, 2022 · Updated Aug 3, 2024
Use-after-free in the Linux Kernel NILFS2 implementation allows local users to crash the system by mounting a corrupted filesystem image. nilfs_new_inode() can allocate a reserved root inode from an inconsistent bitmap, after which nilfs_clear_inode() wrongly decrements and frees the nilfs_root object. A user permitted to mount arbitrary filesystem images can trigger a kernel oops and service interruption; network input alone does not reach the flaw.
Summary
What happened
Use-after-free in the Linux Kernel NILFS2 implementation allows local users to crash the system by mounting a corrupted filesystem image. nilfs_new_inode() can allocate a reserved root inode from an inconsistent bitmap, after which nilfs_clear_inode() wrongly decrements and frees the nilfs_root object. A user permitted to mount arbitrary filesystem images can trigger a kernel oops and service interruption; network input alone does not reach the flaw.
The record
- CVE
- CVE-2022-3649
- Published
- Oct 21, 2022
- Updated
- Aug 3, 2024
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-416, CWE-119, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 21, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=n/a
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo