Local privilege escalation via uninitialized NILFS inode pointer
Published Aug 24, 2022 · Updated Aug 3, 2024
Use-after-free in Linux kernel NILFS2 before 6.0-rc3 allows local users to crash the system or escalate privileges. When security_inode_alloc fails, inode->i_private remains uninitialized, yet nilfs_free_inode can pass it to nilfs_mdt_destroy for release. Triggering requires local low-privileged access and the allocation failure; successful exploitation can panic the kernel or gain kernel privileges.
Summary
What happened
Use-after-free in Linux kernel NILFS2 before 6.0-rc3 allows local users to crash the system or escalate privileges. When security_inode_alloc fails, inode->i_private remains uninitialized, yet nilfs_free_inode can pass it to nilfs_mdt_destroy for release. Triggering requires local low-privileged access and the allocation failure; successful exploitation can panic the kernel or gain kernel privileges.
The record
- CVE
- CVE-2022-2978
- Published
- Aug 24, 2022
- Updated
- Aug 3, 2024
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-416, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 24, 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=Linux kernel 6.0-rc3
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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.
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