CVE-2026-72375: afs: Fix reinitialisation of the inode, in particular ->lock_work
In the Linux kernel, the following vulnerability has been resolved:
afs: Fix reinitialisation of the inode, in particular ->lockwork
It seems that initalising afsvnode::lockwork a single time in the slab's init function isn't sufficient for workstructs. This results in the DEBUGOBJECTS debugging stuff producing a warning occasionally when running the generic/131 xfstest:
ODEBUG: activate not available (active state 0) object: 0000000016d8760f object type: workstruct hint: afslockwork+0x0/0x220 WARNING: lib/debugobjects.c:629 at debugprintobject+0x4b/0x90, CPU#3: locktest/7695 ... CPU: 3 UID: 0 PID: 7695 Comm: locktest Tainted: G S 7.1.0-build3+ #2771 PREEMPT ... RIP: 0010:debugprintobject+0x65/0x90 ... Call Trace: <TASK> ? pfxafslockwork+0x10/0x10 debugobjectactivate+0x122/0x170 insertwork+0x25/0x60 queuework+0x2e0/0x340 queuedelayedworkon+0x48/0x70 afsflreleaseprivate+0x57/0x70 locksreleaseprivate+0x5c/0xa0 locksfreelock+0xe/0x20 posixlockinode+0x55f/0x5b0 lockslockinodewait+0x81/0x140 ? filewriteandwaitrange+0x50/0x70 afslock+0xcd/0x110 fcntlsetlk+0x10d/0x260 dofcntl+0x24e/0x5b0 dosysfcntl+0x6a/0x90 dosyscall64+0x11e/0x310 entrySYSCALL64afterhwframe+0x71/0x79
Fix this by reinitialising ->lockwork after allocating an inode.
Also, flush ->lockwork when the inode is being evicted to make sure it's not still running.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.1.191 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.6.160 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.12.114 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.18.40 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 7.1.5 - Upgrade
Upgrade
ubuntu/linux-aws-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-1014.14~24.04.1 - Upgrade
Upgrade
ubuntu/linux-azure-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-1017.17~24.04.1 - Upgrade
Upgrade
ubuntu/linux-azure-fde-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-1016.16~24.04.1 - Upgrade
Upgrade
ubuntu/linux-gcp-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-1014.14~24.04.1 - Upgrade
Upgrade
ubuntu/linux-hwe-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-38.38~24.04.4 - Upgrade
Upgrade
ubuntu/linux-nvidia-tegrato a version that resolves this vulnerability.Fixed in 6.8.0-1036.39 - Upgrade
Upgrade
ubuntu/linux-oracle-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-1013.13~24.04.1 - Upgrade
Upgrade
ubuntu/linux-riscv-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-38.38.1~24.04.1 - Upgrade
Upgrade
ubuntu/linuxto a version that resolves this vulnerability.Fixed in 7.0.0-38.38 - Upgrade
Upgrade
ubuntu/linux-awsto a version that resolves this vulnerability.Fixed in 7.0.0-1014.14 - Upgrade
Upgrade
ubuntu/linux-azureto a version that resolves this vulnerability.Fixed in 7.0.0-1017.17 - Upgrade
Upgrade
ubuntu/linux-azure-fdeto a version that resolves this vulnerability.Fixed in 7.0.0-1016.16 - Upgrade
Upgrade
ubuntu/linux-gcpto a version that resolves this vulnerability.Fixed in 7.0.0-1014.14 - Upgrade
Upgrade
ubuntu/linux-gketo a version that resolves this vulnerability.Fixed in 7.0.0-1008.9 - Upgrade
Upgrade
ubuntu/linux-ibmto a version that resolves this vulnerability.Fixed in 7.0.0-1015.15 - Upgrade
Upgrade
ubuntu/linux-oem-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-1015.15 - Upgrade
Upgrade
ubuntu/linux-oracleto a version that resolves this vulnerability.Fixed in 7.0.0-1013.13 - Upgrade
Upgrade
ubuntu/linux-realtimeto a version that resolves this vulnerability.Fixed in 7.0.0-38.38.1 - Upgrade
Upgrade
ubuntu/linux-riscvto a version that resolves this vulnerability.Fixed in 7.0.0-38.38.1 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 7.1.5-1 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 7.2.12-1Fixed in 7.2.14-1 - Compensating control
Reinitialize afs_vnode::lock_work after allocating an inode, rather than initializing it only once in the slab init function.
- Compensating control
Flush ->lock_work when the inode is being evicted to ensure the work is no longer running.
Event History
Frequently Asked Questions
What is the severity of CVE-2026-72375?
The severity of CVE-2026-72375 is rated at 6 on the CVSS scale.
What is CVE-2026-72375?
CVE-2026-72375 addresses an issue in the Linux kernel related to the reinitialisation of the inode and specifically the ->lock_work structure.
How does CVE-2026-72375 affect the Linux kernel?
CVE-2026-72375 can lead to improper handling of work_structs due to insufficient initialisation, potentially causing debugging issues.
How do I fix CVE-2026-72375?
To fix CVE-2026-72375, update your Linux kernel to the latest version where the vulnerability has been resolved.
When was CVE-2026-72375 published?
CVE-2026-72375 was published on August 15, 2026.