Remote kernel crash via malformed CIPSO bitmap
Published May 22, 2020 · Updated Aug 4, 2024
NULL pointer dereference in the SELinux subsystem of Red Hat Kernel before 5.7 allows remote attackers to crash the kernel via a CIPSO packet. cipso_v4_parsetag_rbm marks the category bitmap as present even when none was allocated, and ebitmap_netlbl_import then dereferences the NULL bitmap. A network-reachable CIPSO path and a restricted-bitmap tag with a null category are required; successful exploitation panics the host kernel.
Summary
What happened
NULL pointer dereference in the SELinux subsystem of Red Hat Kernel before 5.7 allows remote attackers to crash the kernel via a CIPSO packet. cipso_v4_parsetag_rbm marks the category bitmap as present even when none was allocated, and ebitmap_netlbl_import then dereferences the NULL bitmap. A network-reachable CIPSO path and a restricted-bitmap tag with a null category are required; successful exploitation panics the host kernel.
The record
- CVE
- CVE-2020-10711
- Published
- May 22, 2020
- Updated
- Aug 4, 2024
- Vendor
- Red Hat
- Product
- Red Hat Kernel
- Classifications
- CWE-476, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 22, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=all kernel versions before 5.7
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.
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