CVE-2026-72375 (GCVE-0-2026-72375)
Vulnerability from cvelistv5
Published
2026-08-15 05:56
Modified
2026-08-17 05:43
Severity ?
VLAI Severity ?
EPSS score ?
Summary
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.
References
Impacted products
{
"containers": {
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"fs/afs/inode.c",
"fs/afs/super.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "63d3f283858fae097fb09ddd4ce46bb0bc1f9d01",
"status": "affected",
"version": "e8d6c554126b830217c5e9f549e0e21f865a0a8a",
"versionType": "git"
},
{
"lessThan": "ebfd13c0367adb43d7c0a72f5cd7e004e60c6b28",
"status": "affected",
"version": "e8d6c554126b830217c5e9f549e0e21f865a0a8a",
"versionType": "git"
},
{
"lessThan": "5597fbd1e7c161914f20315a726e54025b0fdadb",
"status": "affected",
"version": "e8d6c554126b830217c5e9f549e0e21f865a0a8a",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"fs/afs/inode.c",
"fs/afs/super.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "2.6.23"
},
{
"lessThan": "2.6.23",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.18.*",
"status": "unaffected",
"version": "6.18.40",
"versionType": "semver"
},
{
"lessThanOrEqual": "7.1.*",
"status": "unaffected",
"version": "7.1.5",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.2",
"versionType": "original_commit_for_fix"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.18.40",
"versionStartIncluding": "2.6.23",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.1.5",
"versionStartIncluding": "2.6.23",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.2",
"versionStartIncluding": "2.6.23",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nafs: Fix reinitialisation of the inode, in particular -\u003elock_work\n\nIt seems that initalising afs_vnode::lock_work a single time in the slab\u0027s\ninit function isn\u0027t sufficient for work_structs. This results in the\nDEBUG_OBJECTS debugging stuff producing a warning occasionally when running\nthe generic/131 xfstest:\n\n ODEBUG: activate not available (active state 0) object: 0000000016d8760f object type: work_struct hint: afs_lock_work+0x0/0x220\n WARNING: lib/debugobjects.c:629 at debug_print_object+0x4b/0x90, CPU#3: locktest/7695\n ...\n CPU: 3 UID: 0 PID: 7695 Comm: locktest Tainted: G S 7.1.0-build3+ #2771 PREEMPT\n ...\n RIP: 0010:debug_print_object+0x65/0x90\n ...\n Call Trace:\n \u003cTASK\u003e\n ? __pfx_afs_lock_work+0x10/0x10\n debug_object_activate+0x122/0x170\n insert_work+0x25/0x60\n __queue_work+0x2e0/0x340\n queue_delayed_work_on+0x48/0x70\n afs_fl_release_private+0x57/0x70\n locks_release_private+0x5c/0xa0\n locks_free_lock+0xe/0x20\n posix_lock_inode+0x55f/0x5b0\n locks_lock_inode_wait+0x81/0x140\n ? file_write_and_wait_range+0x50/0x70\n afs_lock+0xcd/0x110\n fcntl_setlk+0x10d/0x260\n do_fcntl+0x24e/0x5b0\n __do_sys_fcntl+0x6a/0x90\n do_syscall_64+0x11e/0x310\n entry_SYSCALL_64_after_hwframe+0x71/0x79\n\nFix this by reinitialising -\u003elock_work after allocating an inode.\n\nAlso, flush -\u003elock_work when the inode is being evicted to make sure it\u0027s\nnot still running."
}
],
"metrics": [
{
"cvssV3_1": {
"baseScore": 7.8,
"baseSeverity": "HIGH",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"scenarios": [
{
"lang": "en",
"value": "AV:L - The bug is reached only via the local VFS file-locking path (fcntl/F_SETLK/F_SETLKW \u2192 afs_lock \u2192 afs_fl_release_private \u2192 queue_delayed_work on vnode-\u003elock_work), not from inbound AFS/RxRPC network packet handling.\nAC:L - An attacker can reliably drive the fault by cycling POSIX locks and inode eviction/reuse on AFS files they control; both sides of the workqueue/slab race are attacker-influenced and freely retryable, matching the intermittent generic/131 locktest reproducer.\nPR:L - On the highest-impact deployment (enterprise/university hosts with AFS already mounted), any unprivileged local user who can open files on that mount can trigger fcntl locking without real root or CAP_SYS_ADMIN in the init namespace.\nUI:N - Exploitation requires no action by another user; the attacker directly issues fcntl lock/unlock operations on file descriptors they hold on the shared AFS mount.\nS:U - Impact is confined to kernel memory corruption and privilege escalation within the same kernel security boundary; this is not a VM escape, IOMMU bypass, or cross-authority sandbox breakout.\nC:H - Stale lock_work reuse and eviction without flush_delayed_work() can leave afs_lock_work operating on freed/reallocated afs_vnode slab memory, a classic use-after-free that can disclose or corrupt adjacent kernel heap contents.\nI:H - Corrupting or re-queuing a stale delayed_work can corrupt workqueue lists and attacker-controlled vnode fields, providing primitives consistent with arbitrary kernel write and control-flow hijack, not merely a benign warning.\nA:H - Invalid work_struct state triggers kernel warnings/oops in testing and can panic the system when deferred lock work runs against an evicted inode or poisoned slab object during normal lock release."
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-08-17T05:43:28.699Z",
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"shortName": "Linux"
},
"references": [
{
"url": "https://git.kernel.org/stable/c/63d3f283858fae097fb09ddd4ce46bb0bc1f9d01"
},
{
"url": "https://git.kernel.org/stable/c/ebfd13c0367adb43d7c0a72f5cd7e004e60c6b28"
},
{
"url": "https://git.kernel.org/stable/c/5597fbd1e7c161914f20315a726e54025b0fdadb"
}
],
"title": "afs: Fix reinitialisation of the inode, in particular -\u003elock_work",
"x_generator": {
"engine": "bippy-1.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"assignerShortName": "Linux",
"cveId": "CVE-2026-72375",
"datePublished": "2026-08-15T05:56:09.790Z",
"dateReserved": "2026-08-09T03:40:39.922Z",
"dateUpdated": "2026-08-17T05:43:28.699Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
Loading…
Loading…
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.
Loading…
Loading…