Process hangs via recursive complain-mode hat locking
Published Sep 17, 2026 · Updated Sep 17, 2026
Deadlock in AppArmor in Linux Kernel allows local users to hang processes by requesting a missing hat in complain mode. In build_change_hat(), creation of a learning profile calls aa_new_learning_profile(), which reacquires the namespace mutex already held by change_hat(). The trigger requires a complain-mode profile and a nonexistent hat; the calling process becomes unkillable, and subsequent hat changes also hang.
Summary
What happened
Deadlock in AppArmor in Linux Kernel allows local users to hang processes by requesting a missing hat in complain mode. In build_change_hat(), creation of a learning profile calls aa_new_learning_profile(), which reacquires the namespace mutex already held by change_hat(). The trigger requires a complain-mode profile and a nonexistent hat; the calling process becomes unkillable, and subsequent hat changes also hang.
The record
- CVE
- CVE-2026-90179
- Published
- Sep 17, 2026
- Updated
- Sep 17, 2026
- Vendor
- Linux Foundation
- Product
- Linux Kernel
- Classifications
- T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 17, 2026CVE publishedPublication date reported by the CVE source.
- Sep 17, 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=32e92764d6f8d251c1bca62be33793287b453a81 <072fb5aeec2eac7d445bf28c7119a1d6f6a2e333
- Affected versionversion=32e92764d6f8d251c1bca62be33793287b453a81 <4ec11f14d1d6fdda787d991b142537be7841d395
- Affected versionversion=5.10.261 <5.11
- Affected versionversion=5.15.212 <5.16
- Affected versionversion=5acb878db41328dae4d3249bc87b9ee4f290a663
- Affected versionversion=6.1.178 <6.2
- Affected versionversion=6.12.97 <6.13
- Affected versionversion=6.18.40 <6.18.52
- Affected versionversion=6446dbe02f4a3592bf062b4d12105927993086af
- Affected versionversion=65f95c1e7ce70bf339504e22473879e02026cfc4
- Affected versionversion=6.6.145 <6.7
- Affected versionversion=67ee65ec1a3eebdde76ccaa664d20dcf5b125a2f
- Affected versionversion=7.1.5 <7.2
- Affected versionversion=7.2
- Affected versionversion=862ae1fcc78aea9acab2ac87cccf6431f4682b8e
- Affected versionversion=9735e300a1c9259bfe4dc5ecdba472bb25574e8a
- Affected versionversion=b427061ca498309bf581bb6f8df4ffcfe4c772cd <00cce5e457cb690a3b3b3d334e76e71049ec8ae5
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.
Activity data is delayed. The latest report is Sep 28, 2026.
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
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started