CVE-2026-72368
Last modified
CVE-2026-72368 is a high-severity vulnerability rated 7.8/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: cachefiles: Fix double unlock in nomem_d_alloc error path When start_creating() fails and returns -ENOMEM, it has already released the parent directory lock in __start_dirop(): static struct dentry *__start_dirop(...) { ... inode_lock_nested(dir, I_MUTEX_PARENT); dentry = lookup_one_qstr_excl(name, parent, lookup_flags); if (IS_ERR(dentry)) inode_unlock(dir); <-- Lock released on error return dentry; } However, the nomem_d_alloc error path in cachefiles_get_directory() unconditionally calls inode_unlock(d_inode(dir)) again, causing a double unlock that corrupts the rwsem state. This is a leftover from commit 7ab96df840e60 which replaced manual locking with start_creating() but failed to update the nomem_d_alloc path (while correctly updating mkdir_error and lookup_error paths).. EPSS estimates a 0.20% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: cachefiles: Fix double unlock in nomem_d_alloc error path When start_creating() fails and returns -ENOMEM, it has already released the parent directory lock in __start_dirop(): static struct dentry *__start_dirop(...) { ... inode_lock_nested(dir, I_MUTEX_PARENT); dentry = lookup_one_qstr_excl(name, parent, lookup_flags); if (IS_ERR(dentry)) inode_unlock(dir); <-- Lock released on error return dentry; } However, the nomem_d_alloc error path in cachefiles_get_directory() unconditionally calls inode_unlock(d_inode(dir)) again, causing a double unlock that corrupts the rwsem state. This is a leftover from commit 7ab96df840e60 which replaced manual locking with start_creating() but failed to update the nomem_d_alloc path (while correctly updating mkdir_error and lookup_error paths).
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 7ab96df840e60eb933abfe65fc5fe44e72f16dc0, < 26757dac15175f2a42e3537f1ba86e62456d48f1; >= 7ab96df840e60eb933abfe65fc5fe44e72f16dc0, < 8c256fba2b46020004201c500b2a1fbc707a33ef |
| Linux | Linux | 6.19 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-72368?
How severe is CVE-2026-72368?
How do I fix CVE-2026-72368?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-72362In the Linux kernel, the following vulnerability has been re…
- CVE-2026-72363In the Linux kernel, the following vulnerability has been re…
- CVE-2026-72364In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2026-72365In the Linux kernel, the following vulnerability has been re…
- CVE-2026-72366In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-72367In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2026-72369In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-7237A vulnerability was detected in AgiFlow scaffold-mcp up to 1…7.3
- CVE-2026-72370In the Linux kernel, the following vulnerability has been re…
- CVE-2026-72371In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-72372In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-72373In the Linux kernel, the following vulnerability has been re…7.5
Are you affected by CVE-2026-72368?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
