afs: Fix reinitialisation of the inode, in particular ->lock_work
CVE-2026-72375 · published 15 Aug 2026
How serious is it
- Severity: high, CVSS score 7.8 out of 10.
- No exploit prediction (EPSS) score yet.
- Not on the CISA list of exploited vulnerabilities.
- No public exploit in Exploit-DB.
Is your app affected by CVE-2026-72375?
Paste this prompt into Claude Code, Cursor or any AI coding tool: it runs a free Shippable scan of your project and fixes what it finds. Built with Lovable, Bolt or v0? Scan your live app. Or upload your package file.
Who is affected
- Linux Linux: e8d6c554126b830217c5e9f549e0e21f865a0a8a to < 2e7888bb635d9bc84359491347b236cc232ca4df, e8d6c554126b830217c5e9f549e0e21f865a0a8a to < 34dff35154e2fb3987ec5e0b40def14c64eadeb1, e8d6c554126b830217c5e9f549e0e21f865a0a8a to < 63d3f283858fae097fb09ddd4ce46bb0bc1f9d01, e8d6c554126b830217c5e9f549e0e21f865a0a8a to < ebfd13c0367adb43d7c0a72f5cd7e004e60c6b28
- Linux Linux: 2.6.23
How to check
- Find out whether you run the affected product and which version, then compare it with the versions above.
How to fix
Copies a prompt for Claude Code, Cursor or Codex that asks it to check whether you run this product.
- Apply the vendor's update or mitigation from the references below. If there is none yet, limit exposure of the affected service until there is.
- If a vulnerable version was live, check your logs and rotate the secrets that server could read.
The advisory
In the Linux kernel, the following vulnerability has been resolved:
afs: Fix reinitialisation of the inode, in particular ->lock_work
It seems that initalising afs_vnode::lock_work a single time in the slab's
init function isn't sufficient for work_structs. This results in the
DEBUG_OBJECTS debugging stuff producing a warning occasionally when running
the generic/131 xfstest:
ODEBUG: activate not available (active state 0) object: 0000000016d8760f object type: work_struct hint: afs_lock_work+0x0/0x220
WARNING: lib/debugobjects.c:629 at debug_print_object+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:debug_print_object+0x65/0x90
...
Call Trace:
<TASK>
? __pfx_afs_lock_work+0x10/0x10
debug_object_activate+0x122/0x170
insert_work+0x25/0x60
__queue_work+0x2e0/0x340
queue_delayed_work_on+0x48/0x70
afs_fl_release_private+0x57/0x70
locks_release_private+0x5c/0xa0
locks_free_lock+0xe/0x20
posix_lock_inode+0x55f/0x5b0
locks_lock_inode_wait+0x81/0x140
? file_write_and_wait_range+0x50/0x70
afs_lock+0xcd/0x110
fcntl_setlk+0x10d/0x260
do_fcntl+0x24e/0x5b0
__do_sys_fcntl+0x6a/0x90
do_syscall_64+0x11e/0x310
entry_SYSCALL_64_after_hwframe+0x71/0x79
Fix this by reinitialising ->lock_work after allocating an inode.
Also, flush ->lock_work when the inode is being evicted to make sure it's
not still running.
Check your whole app
Dependencies are only half of it. Free and read-only: before you push, run npx shippable-dev scan localhost:3000 in your project folder, no account needed. For your live app, you prove it's yours with a one-line tag first.
References
- git.kernel.org/stable/c/2e7888bb635d9bc84359491347b236cc232ca4df
- git.kernel.org/stable/c/34dff35154e2fb3987ec5e0b40def14c64eadeb1
- git.kernel.org/stable/c/63d3f283858fae097fb09ddd4ce46bb0bc1f9d01
- git.kernel.org/stable/c/ebfd13c0367adb43d7c0a72f5cd7e004e60c6b28
- git.kernel.org/stable/c/5597fbd1e7c161914f20315a726e54025b0fdadb
Merged from CVE List. Last updated 25 Oct 2026. All vulnerabilities · RSS · JSON