System crash via interrupted floppy-driver lock
Published Mar 11, 2021 · Updated Aug 3, 2024
A race condition in the Linux Kernel 5.12-rc2 floppy driver allows local users with device access to crash the system. The floppy_revalidate and floppy_check_events paths ignore an interrupted lock_fdc return and continue without the lockedfd critical-section guard. Access to /dev/fd0 requires root-equivalent permissions by default; relaxed device permissions expose memory corruption and possible privilege escalation.
Summary
What happened
A race condition in the Linux Kernel 5.12-rc2 floppy driver allows local users with device access to crash the system. The floppy_revalidate and floppy_check_events paths ignore an interrupted lock_fdc return and continue without the lockedfd critical-section guard. Access to /dev/fd0 requires root-equivalent permissions by default; relaxed device permissions expose memory corruption and possible privilege escalation.
The record
- CVE
- CVE-2021-20261
- Published
- Mar 11, 2021
- Updated
- Aug 3, 2024
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-362, T1068
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Mar 11, 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-rc2
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