Kernel warning via uninitialized AppArmor list heads
Published Sep 24, 2026 · Updated Sep 24, 2026
Improper initialization in Linux AppArmor allows local users to trigger a kernel warning through a failed profile load. aa_policy_init initializes the policy list heads only after allocating the profile name, so an earlier allocation failure sends uninitialized lists to profile_free and aa_policy_destroy. Loading a profile requires administrative policy-management access, and the validated reproducer shows a warning rather than service interruption or privilege-boundary impact.
Summary
What happened
Improper initialization in Linux AppArmor allows local users to trigger a kernel warning through a failed profile load. aa_policy_init initializes the policy list heads only after allocating the profile name, so an earlier allocation failure sends uninitialized lists to profile_free and aa_policy_destroy. Loading a profile requires administrative policy-management access, and the validated reproducer shows a warning rather than service interruption or privilege-boundary impact.
The record
- CVE
- CVE-2026-93245
- Published
- Sep 24, 2026
- Updated
- Sep 24, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Sep 24, 2026CVE publishedPublication date reported by the CVE source.
- Sep 24, 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=4.11
- Affected versionversion=fe6bb31f590c9cd9c8d3ddbdfd4301f72db91718 <0664c75afe87a1d7d4f4e1d7eecf50ad829fb6e8
- Affected versionversion=fe6bb31f590c9cd9c8d3ddbdfd4301f72db91718 <3daad923a8685adb66087e0d819559b7eb6ba975
- Affected versionversion=fe6bb31f590c9cd9c8d3ddbdfd4301f72db91718 <4a09a5e6512a3792c78ae8e3ca79cb55a11eed57
- Affected versionversion=fe6bb31f590c9cd9c8d3ddbdfd4301f72db91718 <5449f715f24e86648f8cc8fba8d97ff6b5d04981
- Affected versionversion=fe6bb31f590c9cd9c8d3ddbdfd4301f72db91718 <62f159fac76468dbbfd977f4f18472d4a01e8d74
- Affected versionversion=fe6bb31f590c9cd9c8d3ddbdfd4301f72db91718 <88ba930e7d0586ca2700757249f1e6fc0bbab0fc
- Affected versionversion=fe6bb31f590c9cd9c8d3ddbdfd4301f72db91718 <dd52ab1c5436be86f5b8ca118fa8e5d61d63ffed
- Affected versionversion=fe6bb31f590c9cd9c8d3ddbdfd4301f72db91718 <ee017ef9aa2cf20d85d4a20c09ef3db9fb240310
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
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.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
- syzbot reproducer for WARNING in aa_policy_destroyproof 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
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started