Compiler crash via retained freed class-permission list
Published Jul 1, 2021 · Updated Nov 3, 2025
Use-after-free in the SELinux 3.2 CIL compiler allows local users to crash policy compilation through crafted CIL policy input. When an optional block is reset, cil_reset_classpermission retains a classperms list whose referenced entries can be freed, and later verification dereferences those entries. Exploitation requires user interaction to compile attacker-controlled CIL; the demonstrated consequence is a compiler crash.
Summary
What happened
Use-after-free in the SELinux 3.2 CIL compiler allows local users to crash policy compilation through crafted CIL policy input. When an optional block is reset, cil_reset_classpermission retains a classperms list whose referenced entries can be freed, and later verification dereferences those entries. Exploitation requires user interaction to compile attacker-controlled CIL; the demonstrated consequence is a compiler crash.
The record
- CVE
- CVE-2021-36084
- Published
- Jul 1, 2021
- Updated
- Nov 3, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-416
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 1, 2021CVE publishedPublication date reported by the CVE source.
- Nov 3, 2025Record 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.
Weakness, pattern, technique
Public exploit references
- Minimized CIL policy 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