In the Linux kernel, the following vulnerability has been resolved: afs: Fix reinitialisation of the inode, in particular ->lock_work It seems that… (CVE-2026-72375)
A vulnerability in the Linux kernel's AFS filesystem component related to improper reinitialization of the inode's lock_work structure has been resolved. The issue involved initializing afs_vnode::lock_work only once in the slab's init function, which is insufficient for work_structs, leading to occasional debug warnings. The fix involves reinitializing lock_work after inode allocation and flushing it upon inode eviction to ensure no lingering work is running.
AI Analysis
Technical Summary
The Linux kernel AFS module had a vulnerability where the inode's lock_work work_struct was only initialized once during slab initialization, which is inadequate. This caused sporadic debug warnings under DEBUG_OBJECTS when running certain tests, indicating potential improper handling of work_struct state. The vulnerability was fixed by reinitializing the lock_work field after each inode allocation and flushing it during inode eviction to prevent residual active work_structs.
Potential Impact
The vulnerability caused debug warnings indicating improper reinitialization of kernel work_structs, which could lead to unstable kernel behavior or potential resource management issues. There is no indication of direct exploitation or security breach impact. No known exploits in the wild have been reported.
Mitigation Recommendations
A fix has been implemented in the Linux kernel source to reinitialize the lock_work structure after inode allocation and flush it on inode eviction. Users should update to the patched Linux kernel version containing this fix once it is released. Patch status is not explicitly confirmed in the provided data; check the official Linux kernel advisories or source repositories for the exact fixed versions and apply updates accordingly.
In the Linux kernel, the following vulnerability has been resolved: afs: Fix reinitialisation of the inode, in particular ->lock_work It seems that… (CVE-2026-72375)
Description
A vulnerability in the Linux kernel's AFS filesystem component related to improper reinitialization of the inode's lock_work structure has been resolved. The issue involved initializing afs_vnode::lock_work only once in the slab's init function, which is insufficient for work_structs, leading to occasional debug warnings. The fix involves reinitializing lock_work after inode allocation and flushing it upon inode eviction to ensure no lingering work is running.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel AFS module had a vulnerability where the inode's lock_work work_struct was only initialized once during slab initialization, which is inadequate. This caused sporadic debug warnings under DEBUG_OBJECTS when running certain tests, indicating potential improper handling of work_struct state. The vulnerability was fixed by reinitializing the lock_work field after each inode allocation and flushing it during inode eviction to prevent residual active work_structs.
Potential Impact
The vulnerability caused debug warnings indicating improper reinitialization of kernel work_structs, which could lead to unstable kernel behavior or potential resource management issues. There is no indication of direct exploitation or security breach impact. No known exploits in the wild have been reported.
Mitigation Recommendations
A fix has been implemented in the Linux kernel source to reinitialize the lock_work structure after inode allocation and flush it on inode eviction. Users should update to the patched Linux kernel version containing this fix once it is released. Patch status is not explicitly confirmed in the provided data; check the official Linux kernel advisories or source repositories for the exact fixed versions and apply updates accordingly.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-fpj5-fm3g-5rvj
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-72375"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a808b6fbf8831d5394faae3
Added to database: 08/15/2026, 15:53:19 UTC
Last enriched: 08/15/2026, 16:30:55 UTC
Last updated: 08/16/2026, 03:01:09 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.