System crash via cyclic AppArmor policy chains
Published Apr 1, 2026 · Updated Apr 1, 2026
Infinite-loop handling in affected Linux Kernel releases allows local users to crash the system by loading a crafted AppArmor policy. The differential-encoding verifier in security/apparmor/match.c confuses verified states with states in the current chain and compares inner iterators instead of the outer-loop iterator, so a cyclic chain passes validation. Exploitation requires the ability to load arbitrary AppArmor profiles, obtained through a cooperating privileged application or an attacker-controlled container.
Summary
What happened
Infinite-loop handling in affected Linux Kernel releases allows local users to crash the system by loading a crafted AppArmor policy. The differential-encoding verifier in security/apparmor/match.c confuses verified states with states in the current chain and compares inner iterators instead of the outer-loop iterator, so a cyclic chain passes validation. Exploitation requires the ability to load arbitrary AppArmor profiles, obtained through a cooperating privileged application or an attacker-controlled container.
The record
- CVE
- CVE-2026-23409
- Published
- Apr 1, 2026
- Updated
- Apr 1, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-835, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 1, 2026CVE publishedPublication date reported by the CVE source.
- Apr 1, 2026Record 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=031dcc8f4e84fea37dc6f78fdc7288aa7f8386c3 <1ff4857fac56ac5a90ee63b24db05fa5e91a45aa
- Affected versionversion=031dcc8f4e84fea37dc6f78fdc7288aa7f8386c3 <34fc60b125ed1d4eb002c76b0664bf0619492167
- Affected versionversion=031dcc8f4e84fea37dc6f78fdc7288aa7f8386c3 <39440b137546a3aa383cfdabc605fb73811b6093
- Affected versionversion=031dcc8f4e84fea37dc6f78fdc7288aa7f8386c3 <623a9d211bbbb031bb1cbdb38b23487648167f8a
- Affected versionversion=031dcc8f4e84fea37dc6f78fdc7288aa7f8386c3 <f90e3ecd9e1ed69f1a370f866ceed1f104f3ab4a
- Affected versionversion=4.17
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