System hang via recursive audit directory locking
Published Aug 10, 2026 · Updated Aug 10, 2026
Deadlock in the Linux kernel audit subsystem allows local users to hang the system by moving a file covered by an executable audit rule. audit_alloc_mark() calls kern_path_parent() while the VFS rename path already holds I_MUTEX_PARENT, recursively acquiring the same directory lock instead of reusing the resolved inode. The trigger requires an existing executable audit rule matching the moved file; successful exploitation leaves tasks unable to complete and can deadlock the entire system.
Summary
What happened
Deadlock in the Linux kernel audit subsystem allows local users to hang the system by moving a file covered by an executable audit rule. audit_alloc_mark() calls kern_path_parent() while the VFS rename path already holds I_MUTEX_PARENT, recursively acquiring the same directory lock instead of reusing the resolved inode. The trigger requires an existing executable audit rule matching the moved file; successful exploitation leaves tasks unable to complete and can deadlock the entire system.
The record
- CVE
- CVE-2026-68096
- Published
- Aug 10, 2026
- Updated
- Aug 10, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-833, CAPEC-25, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 10, 2026CVE publishedPublication date reported by the CVE source.
- Aug 10, 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=34d99af52ad40bd498ba66970579a5bc1fb1a3bc <36eb77f14b4e6f2dc1008c1fabe31236397be27a
- Affected versionversion=34d99af52ad40bd498ba66970579a5bc1fb1a3bc <3b601938314c24fcd1afb6659cad92fe96c9c2f8
- Affected versionversion=34d99af52ad40bd498ba66970579a5bc1fb1a3bc <40879c39d6740f3dddfb52b5d6ba7fb8cceb84d8
- Affected versionversion=34d99af52ad40bd498ba66970579a5bc1fb1a3bc <7d1f66c69898ffb1a718926c32a777ecc471caca
- Affected versionversion=34d99af52ad40bd498ba66970579a5bc1fb1a3bc <81905b5acbe77284734438df3fbec1158e6429a3
- Affected versionversion=4.3
What conditions does exploitation require?
What is affected?
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
- audit-dupe-exe-deadlock.shfunctional · 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