Kernel crash via unchecked quota block number
Published Mar 18, 2022 · Updated Aug 4, 2024
Use-after-free in the Linux kernel before 5.15.3 allows local users to crash the kernel by supplying a corrupted on-disk quota file. fs/quota/quota_tree.c accepts a quota-tree block number that is not smaller than dqi_blocks, allowing allocation of an already allocated block and creating a tree loop. Triggering the fault requires local interaction with a corrupted quota file; the demonstrated consequence is a kernel oops and service interruption.
Summary
What happened
Use-after-free in the Linux kernel before 5.15.3 allows local users to crash the kernel by supplying a corrupted on-disk quota file. fs/quota/quota_tree.c accepts a quota-tree block number that is not smaller than dqi_blocks, allowing allocation of an already allocated block and creating a tree loop. Triggering the fault requires local interaction with a corrupted quota file; the demonstrated consequence is a kernel oops and service interruption.
The record
- CVE
- CVE-2021-45868
- Published
- Mar 18, 2022
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-416, T1499
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 18, 2022CVE publishedPublication date reported by the CVE source.
- Aug 4, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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