System crash via invalid BTRFS device removal
Published Mar 7, 2022 · Updated Aug 3, 2024
NULL pointer dereference in Linux Kernel BTRFS before 5.15-rc1 allows local users with CAP_SYS_ADMIN to crash the system. The BTRFS_IOC_RM_DEV_V2 path accepts a nonexistent device ID, and btrfs_rm_device dereferences the resulting null device pointer. Exploitation requires local CAP_SYS_ADMIN access and a BTRFS filesystem; the documented security consequence is a host crash, while the source record also reports possible kernel-information disclosure.
Summary
What happened
NULL pointer dereference in Linux Kernel BTRFS before 5.15-rc1 allows local users with CAP_SYS_ADMIN to crash the system. The BTRFS_IOC_RM_DEV_V2 path accepts a nonexistent device ID, and btrfs_rm_device dereferences the resulting null device pointer. Exploitation requires local CAP_SYS_ADMIN access and a BTRFS filesystem; the documented security consequence is a host crash, while the source record also reports possible kernel-information disclosure.
The record
- CVE
- CVE-2021-3739
- Published
- Mar 7, 2022
- Updated
- Aug 3, 2024
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-476
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Mar 7, 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=Fixed in v5.15-rc1 and above.
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