GHSA-FPJ5-FM3G-5RVJ
Vulnerability from github – Published: 2026-08-15 06:32 – Updated: 2026-08-17 06:33In 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: ? __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.
{
"affected": [],
"aliases": [
"CVE-2026-72375"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-08-15T06:22:10Z",
"severity": "HIGH"
},
"details": "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.",
"id": "GHSA-fpj5-fm3g-5rvj",
"modified": "2026-08-17T06:33:26Z",
"published": "2026-08-15T06:32:22Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-72375"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/5597fbd1e7c161914f20315a726e54025b0fdadb"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/63d3f283858fae097fb09ddd4ce46bb0bc1f9d01"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/ebfd13c0367adb43d7c0a72f5cd7e004e60c6b28"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.