System hang via recursive Device Mapper locking
Published Apr 25, 2023 · Updated Aug 2, 2024
Improper locking in Linux Kernel 6.2.0 allows local users with administrative privileges to hang the system through a Device Mapper ioctl. The table_clear function holds the Device Mapper hash write lock while __dev_status calls dm_get_inactive_table, which tries to acquire a read lock on the same semaphore. Administrative access to issue the ioctl is required, and triggering the path deadlocks the kernel rather than exposing or modifying data.
Summary
What happened
Improper locking in Linux Kernel 6.2.0 allows local users with administrative privileges to hang the system through a Device Mapper ioctl. The table_clear function holds the Device Mapper hash write lock while __dev_status calls dm_get_inactive_table, which tries to acquire a read lock on the same semaphore. Administrative access to issue the ioctl is required, and triggering the path deadlocks the kernel rather than exposing or modifying data.
The record
- CVE
- CVE-2023-2269
- Published
- Apr 25, 2023
- Updated
- Aug 2, 2024
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-413, CWE-667
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Apr 25, 2023CVE publishedPublication date reported by the CVE source.
- Aug 2, 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 version 6.2.0
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