afs: Fix reinitialisation of the inode, in particular ->lock_work (CVE-2026-72375) | HOL Guard CVE

High · CVSS 7.8CVE-2026-72375

afs: Fix reinitialisation of the inode, in particular ->lock_work

Answer in brief

CVE-2026-72375 records a High severity (CVSS 7.8) vulnerability in afs: Fix reinitialisation of the inode, in particular ->lock_work. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Aug 15, 2026Updated Aug 17, 2026Source checked Sep 29, 2026First seen by HOL Aug 15, 2026Material review Aug 17, 2026

Upstream Advisory

Key facts

Risk: High · CVSS 7.8
Exploitation: Not marked as known exploited
Affected software: 2 mapped packages or products
Fix availability: Available

Why this deserves its current priority

CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Linux/Linuxgeneric	>=e8d6c554126b830217c5e9f549e0e21f865a0a8a <63d3f283858fae097fb09ddd4ce46bb0bc1f9d01 \|\| >=e8d6c554126b830217c5e9f549e0e21f865a0a8a <ebfd13c0367adb43d7c0a72f5cd7e004e60c6b28 \|\| >=e8d6c554126b830217c5e9f549e0e21f865a0a8a <5597fbd1e7c161914f20315a726e54025b0fdadb	63d3f283858fae097fb09ddd4ce46bb0bc1f9d01, ebfd13c0367adb43d7c0a72f5cd7e004e60c6b28, 5597fbd1e7c161914f20315a726e54025b0fdadb
Linux/Linuxgeneric	2.6.23	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for Linux/Linux, Linux/Linux.
Review the reported fix. Update Linux/Linux to 63d3f283858fae097fb09ddd4ce46bb0bc1f9d01 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Aug 17, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Aug 15, 2026

Sources and claim methodology

Upstream source description

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.

Quoted source text, attributed separately from HOL analysis.