System crash via empty nodelist parsing
Published Apr 6, 2020 · Updated Aug 4, 2024
Out-of-bounds write in the Linux kernel through 5.6.2 allows local users with mount privileges to crash the system. mpol_parse_str fails to reject an empty MPOL_PREFERRED nodelist before first_node processes the empty nodemask, causing a stack out-of-bounds access. Triggering the flaw requires privileges to supply tmpfs mount options, and the record is disputed because those privileges already permit equivalent system disruption.
Summary
What happened
Out-of-bounds write in the Linux kernel through 5.6.2 allows local users with mount privileges to crash the system. mpol_parse_str fails to reject an empty MPOL_PREFERRED nodelist before first_node processes the empty nodemask, causing a stack out-of-bounds access. Triggering the flaw requires privileges to supply tmpfs mount options, and the record is disputed because those privileges already permit equivalent system disruption.
The record
- CVE
- CVE-2020-11565
- Published
- Apr 6, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1499.004
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Apr 6, 2020CVE 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
- mpol=prefer:, mount-option reproducerproof 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