Local arbitrary write via DOI refcount mishandling
Published May 14, 2021 · Updated Aug 3, 2024
Use-after-free in the Linux kernel before 5.11.14 allows local users to write an arbitrary value through CIPSO label processing. The cipso_v4_genopt function dereferences a DOI definition after CIPSO and CALIPSO code mishandles its reference count. A local user must reach the SMACK/NetLabel socket path; triggering the flaw corrupts kernel memory and interrupts service by crashing the kernel.
Summary
What happened
Use-after-free in the Linux kernel before 5.11.14 allows local users to write an arbitrary value through CIPSO label processing. The cipso_v4_genopt function dereferences a DOI definition after CIPSO and CALIPSO code mishandles its reference count. A local user must reach the SMACK/NetLabel socket path; triggering the flaw corrupts kernel memory and interrupts service by crashing the kernel.
The record
- CVE
- CVE-2021-33033
- Published
- May 14, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-416, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 14, 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?
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
- syzkaller C reproducer for cipso_v4_genopt use-after-freeproof 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