cve.bz

CVE-2026-72375 linux linux

7.8 highEPSS 0.2%Fix available

High (7.8) in linux linux. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

7.8 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 7th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-10-16. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • Linux Linux: fixed in 6.1.191
  • Linux Linux: fixed in 6.6.160
  • Linux Linux: fixed in 6.12.114
  • Linux Linux: fixed in 6.18.40
  • Linux Linux: fixed in 7.1.5
  • Linux Linux: fixed in 7.2
  • Debian, Ubuntu, Alpaquita: fixed package versions per release

Ask an AI about this CVE

Show the promptExplain CVE-2026-72375 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-72375?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-72375?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-72375 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Linux2.6.23 and later

Fixed in

ProductRelease lineFixed in
Linux6.16.1.191
Linux6.66.6.160
Linux6.126.12.114
Linux6.186.18.40
Linux7.17.1.5
Linuxlater releases7.2

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12linux6.1.192-1DEBIAN-CVE-2026-72375
Debian12linux-6.126.12.115-2~deb12u1DEBIAN-CVE-2026-72375
Debian13linux6.12.115-2DEBIAN-CVE-2026-72375
Debian14linux7.1.5-1DEBIAN-CVE-2026-72375
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2026-72375
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2026-72375
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2026-72375
Ubuntu22.04:LTSlinux, linux-aws, linux-gcp and 57 moreno fix listedUBUNTU-CVE-2026-72375
Ubuntu24.04:LTSlinux, linux-aws, linux-gcp and 41 moreno fix listedUBUNTU-CVE-2026-72375
Ubuntu24.04:LTSlinux-aws-7.0, linux-gcp-7.07.0.0-1014.14~24.04.1UBUNTU-CVE-2026-72375 USN-8887-2 USN-8887-3
Ubuntu24.04:LTSlinux-azure-7.07.0.0-1017.17~24.04.1UBUNTU-CVE-2026-72375 USN-8888-2
Ubuntu24.04:LTSlinux-azure-fde-7.07.0.0-1016.16~24.04.1UBUNTU-CVE-2026-72375 USN-8888-2
Ubuntu24.04:LTSlinux-hwe-7.07.0.0-38.38~24.04.4UBUNTU-CVE-2026-72375 USN-8887-3
Ubuntu24.04:LTSlinux-nvidia-7.07.0.0-1024.25~24.04.1UBUNTU-CVE-2026-72375 USN-9003-1
Ubuntu24.04:LTSlinux-nvidia-tegra6.8.0-1036.39UBUNTU-CVE-2026-72375 USN-8886-1
Ubuntu24.04:LTSlinux-oracle-7.07.0.0-1013.13~24.04.1UBUNTU-CVE-2026-72375 USN-8887-3
21 more for Ubuntu in the JSON and on Ubuntu's page.
Alpaquita23linux-lts6.1.191-r0BELL-CVE-2026-72375
Alpaquita25linux-lts6.12.115-r0BELL-CVE-2026-72375
Alpaquitastreamlinux-lts6.18.43-r0BELL-CVE-2026-72375

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Alpaquita.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

A moderate-impact flaw was found in the Linux kernel AFS (Andrew File System) client shipped in Red Hat Enterprise Linux and Red Hat In-Vehicle OS. The afs_vnode::lock_work delayed work object is initialised only once in the slab constructor instead of being reinitialised each time an inode is allocated, and it is not flushed when an inode is evicted. As a result, the work_struct can be queued in an improper state during file-locking operations on AFS files (for example via fcntl()), which triggers kernel DEBUG_OBJECTS warnings and can lead to system instability. A local user able to perform file-locking operations on an AFS mount could exploit this flaw to cause a denial of service. Red Hat rated the impact as moderate because the demonstrated consequence is limited to availability (CVSS 5.5, AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H); the higher upstream CVEORG score of 7.8 additionally assumes high confidentiality and integrity impact, which the available evidence does not establish. Red Hat Enterprise Linux 6, 7, and 8 (kernel and kernel-rt) are not affected because the vulnerable code is not present in those streams. For the affected Red Hat Enterprise Linux 9, Red Hat Enterprise Linux 10, and Red Hat In-Vehicle OS streams the fix is deferred: the issue manifests as a debug warning and potential instability under specific local AFS file-locking workloads rather than a demonstrated privilege-escalation or memory-corruption exploit, so it will be addressed in a future planned update. Until then, the residual risk is a local denial of service on systems that actively use AFS filesystems.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10kernelFix deferred
Red Hat Enterprise Linux 6kernelNot affected
Red Hat Enterprise Linux 7kernelNot affected
Red Hat Enterprise Linux 7kernel-rtNot affected
Red Hat Enterprise Linux 8kernelNot affected
Red Hat Enterprise Linux 8kernel-rtNot affected
Red Hat Enterprise Linux 9kernelFix deferred
Red Hat Enterprise Linux 9kernel-rtFix deferred

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-72375.

References

Check your stackJSON