Kernel-memory disclosure or crash via unchecked NAT identifier
Published Apr 19, 2021 · Updated Aug 3, 2024
Out-of-bounds read in Linux Kernel F2FS before 5.12.0-rc4 allows local users to crash the system or expose kernel memory. During checkpointing, remove_nats_in_journal accepts an out-of-range node identifier from a corrupted NAT journal, and get_next_nat_page uses it as a nat_bitmap offset. Exploitation requires local low-privileged access and processing of the corrupted checkpoint journal; the bounded effects are kernel-information disclosure or a system crash.
Summary
What happened
Out-of-bounds read in Linux Kernel F2FS before 5.12.0-rc4 allows local users to crash the system or expose kernel memory. During checkpointing, remove_nats_in_journal accepts an out-of-range node identifier from a corrupted NAT journal, and get_next_nat_page uses it as a nat_bitmap offset. Exploitation requires local low-privileged access and processing of the corrupted checkpoint journal; the bounded effects are kernel-information disclosure or a system crash.
The record
- CVE
- CVE-2021-3506
- Published
- Apr 19, 2021
- Updated
- Aug 3, 2024
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-125, CAPEC-540, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 19, 2021CVE 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=kernel 5.12.0-rc4
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