CVE-2026-72375

HIGHPre-NVD 7.87.8—
EchelonGraph scoreHIGH confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-15. a secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 5 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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: ? __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.

CVSS v3
7.8
EG Score
7.8(high)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
7%
KEV
Not listed

Published

August 15, 2026

Last Modified

August 17, 2026

Advisory Details (3)

Auto-updated Aug 17, 2026
No patch confirmed yet.
generic

afs: Fix reinitialisation of the inode, in particular ->lock_work - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ebfd13c0367adb43d7c0a72f5cd7e004e60c6b28
generic

afs: Fix reinitialisation of the inode, in particular ->lock_work - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/63d3f283858fae097fb09ddd4ce46bb0bc1f9d01
generic

afs: Fix reinitialisation of the inode, in particular ->lock_work - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5597fbd1e7c161914f20315a726e54025b0fdadb

Vendor Advisories for CVE-2026-72375(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Data Freshness Timeline

(refreshed 29× in last 7d / 29× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-21 05:10 UTCEG score recompute
  2. 2026-08-21 05:10 UTCGHSA enrichment
  3. 2026-08-20 22:56 UTCEPSS rescore
  4. 2026-08-20 17:36 UTCGHSA enrichment
  5. 2026-08-20 05:59 UTCGHSA enrichment
  6. 2026-08-19 18:24 UTCEG score recompute
  7. 2026-08-19 18:24 UTCGHSA enrichment
  8. 2026-08-19 17:04 UTCEPSS rescore
  9. 2026-08-19 05:44 UTCGHSA enrichment
  10. 2026-08-18 18:09 UTCGHSA enrichment
  11. 2026-08-18 06:33 UTCGHSA enrichment
  12. 2026-08-17 18:59 UTCEG score recompute
  13. 2026-08-17 18:59 UTCGHSA enrichment
  14. 2026-08-17 13:47 UTCEPSS rescore
  15. 2026-08-17 06:29 UTCEG score recompute
  16. 2026-08-17 06:29 UTCGHSA enrichment
  17. 2026-08-17 05:58 UTCEG score recompute▲ 7.80
  18. 2026-08-17 05:58 UTCGHSA enrichment
  19. 2026-08-17 05:54 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  20. 2026-08-17 05:29 UTCEG score recompute
  21. 2026-08-17 05:29 UTCGHSA enrichment
  22. 2026-08-17 05:24 UTCMITRE cvelistV5
  23. 2026-08-16 14:56 UTCEPSS rescore
  24. 2026-08-16 14:56 UTCEPSS rescore
  25. 2026-08-16 02:15 UTCEPSS rescore
Show 4 more
  1. 2026-08-15 06:35 UTCGHSA enrichment
  2. 2026-08-15 06:23 UTCNVD update
  3. 2026-08-15 06:06 UTCEG score recompute
  4. 2026-08-15 06:02 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-72375?
CVE-2026-72375 is a high vulnerability published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: afs: Fix reinitialisation of the inode, in particular ->lock_work It seems that initalising afsvnode::lockwork a single time in the slab's init function isn't sufficient for work_structs. This results in the DEBUG_OBJECTS debugging…
When was CVE-2026-72375 disclosed?
CVE-2026-72375 was first published in the National Vulnerability Database on August 15, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-72375 actively exploited?
CVE-2026-72375 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 92.9% of all scored CVEs.
What is the CVSS score of CVE-2026-72375?
CVE-2026-72375 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-72375?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-72375, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-72375

Explore →

Is Your Infrastructure Affected by CVE-2026-72375?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs