Kernel crash via undersized device-list buffer
Published May 6, 2021 · Updated Aug 3, 2024
Out-of-bounds write in the Linux Kernel before 5.12 allows local users with CAP_SYS_ADMIN to crash the system via DM_LIST_DEVICES_CMD. When no device-mapper devices exist, list_devices accepts a result buffer smaller than nl->dev and still clears that field beyond the allocation. Root-equivalent local privilege is required; the overwrite can crash the host or disclose internal kernel memory.
Summary
What happened
Out-of-bounds write in the Linux Kernel before 5.12 allows local users with CAP_SYS_ADMIN to crash the system via DM_LIST_DEVICES_CMD. When no device-mapper devices exist, list_devices accepts a result buffer smaller than nl->dev and still clears that field beyond the allocation. Root-equivalent local privilege is required; the overwrite can crash the host or disclose internal kernel memory.
The record
- CVE
- CVE-2021-31916
- Published
- May 6, 2021
- Updated
- Aug 3, 2024
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-787, T1499
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- May 6, 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
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.
Public exploit references
- DM_LIST_DEVICES_CMD proof of conceptproof of concept · demonstrated
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