CVE-2026-72170

published 15 Aug 2026 · updated 16 Oct 2026

9p: skip nlink update in cacheless mode to fix WARN_ON

7.8HighCVSS 7.8EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 4ec4ebe40c82cb4c60756732f6593055d010c59c, Kernel 574aa0b4799470ac814479f1138d19efe6262255, Kernel 6086469f7d469549bfd070348b717a6e43736200 and 5 more.

In the Linux kernel, the following vulnerability has been resolved: 9p: skip nlink update in cacheless mode to fix WARN_ON v9fs_dec_count() unconditionally calls drop_nlink() on regular files, even when the inode's nlink is already zero. In cacheless mode the client refetches inode metadata from the server (the source of truth) on every operation, so by the time v9fs_remove() returns, the locally cached nlink may already reflect the post-unlink value: 1. Client initiates unlink, server processes it and sets nlink to 0 2. Client refetches inode metadata (nlink=0) before unlink returns 3. Client's v9fs_remove() completes successfully 4. Client calls v9fs_dec_count() which calls drop_nlink() on nlink=0 This race is easily triggered under heavy unlink workloads, such as stress-ng's unlink stressor, producing the following warning: WARNING: fs/inode.c:417 at drop_nlink+0x4c/0xc8 Call trace: drop_nlink+0x4c/0xc8 v9fs_remove+0x1e0/0x250 [9p] v9fs_vfs_unlink+0x20/0x38 [9p] vfs_unlink+0x13c/0x258 ... In cacheless mode the server is authoritative and the inode is on its way out, so locally adjusting nlink buys nothing. Skip v9fs_dec_count() entirely when neither CACHE_META nor CACHE_LOOSE is set, which both avoids the warning and removes a class of nlink races (two concurrent unlinkers observing nlink > 0 and both calling drop_nlink()) that an nlink == 0 guard alone would only narrow rather than close.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel=4.17, >=ac89b2ef9b55924bcf922251f043ba73a32d05bb <4ec4ebe40c82cb4c60756732f6593055d010c59c, >=ac89b2ef9b55924bcf922251f043ba73a32d05bb <574aa0b4799470ac814479f1138d19efe6262255, >=ac89b2ef9b55924bcf922251f043ba73a32d05bb <6086469f7d469549bfd070348b717a6e43736200, >=ac89b2ef9b55924bcf922251f043ba73a32d05bb <8d610017c992de705b304d3d727a6e3a86af6149, >=ac89b2ef9b55924bcf922251f043ba73a32d05bb <8faccac11e1369adddf5d80f4a45af93f13b2e1a, >=ac89b2ef9b55924bcf922251f043ba73a32d05bb <a5a682b016ef5b5384e28f6d652d47a8f8e73d37, >=ac89b2ef9b55924bcf922251f043ba73a32d05bb <ab257019cb72f467b55c95384d99c94e3908b928, >=ac89b2ef9b55924bcf922251f043ba73a32d05bb <de79c3f3643841b8659a71958df7cf2a66bfd4094ec4ebe40c82cb4c60756732f6593055d010c59c, 574aa0b4799470ac814479f1138d19efe6262255, 6086469f7d469549bfd070348b717a6e43736200, 8d610017c992de705b304d3d727a6e3a86af6149, 8faccac11e1369adddf5d80f4a45af93f13b2e1a, a5a682b016ef5b5384e28f6d652d47a8f8e73d37, ab257019cb72f467b55c95384d99c94e3908b928, de79c3f3643841b8659a71958df7cf2a66bfd409

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-72170 severity on Zeptric[![CVE-2026-72170](https://zeptric.io/badge/cve/CVE-2026-72170.svg)](https://zeptric.io/cve/CVE-2026-72170)