nfsd: release path refs on follow_down() error
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in Kernel e301c5cdb0dc2c4aeffc0c055ea15615d9c51fdc, Kernel 085cfde7c2186acaad103f02d2c25435ad5224e9, Kernel 18847cbf5900f5c6c55bef5a6f7a34a1918d1181 and 12 more.
In the Linux kernel, the following vulnerability has been resolved: nfsd: release path refs on follow_down() error nfsd_cross_mnt() initializes a local struct path with mntget() and dget() before calling follow_down(). On a negative return the error arm jumps to out without releasing those references: err = follow_down(&path, follow_flags); if (err < 0) goto out; follow_down() never drops the caller's entry-time refs on any error sub-case; for example a pre-cross d_manage() failure leaves path untouched, so the mntget()/dget() taken on entry survive the call. Every other early-exit arm in nfsd_cross_mnt() (other-namespace return, IS_ERR(exp2), and the success tail after the swap) already calls path_put(&path); the err < 0 arm is the lone omission. The leak inflates mnt_count and d_count on each failed cross-mount, blocking umount and pinning dentries against the shrinker, and is reachable by any authenticated NFS client through nfsd_lookup_dentry or the NFSv4 READDIR encode path. Fix by calling path_put(&path) before the goto out in the err < 0 arm so the entry-time refs are released on all follow_down() error returns.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=cc53ce53c86924bfe98a12ea20b7465038a08792 <e301c5cdb0dc2c4aeffc0c055ea15615d9c51fdc, >=cc53ce53c86924bfe98a12ea20b7465038a08792 <085cfde7c2186acaad103f02d2c25435ad5224e9, >=cc53ce53c86924bfe98a12ea20b7465038a08792 <18847cbf5900f5c6c55bef5a6f7a34a1918d1181, >=cc53ce53c86924bfe98a12ea20b7465038a08792 <194316df81263519156ebe714c4a286bee00e5be, >=cc53ce53c86924bfe98a12ea20b7465038a08792 <2bc4343308d85ee4e0dd3877b384306c96f114c2, >=cc53ce53c86924bfe98a12ea20b7465038a08792 <467d56fd3ff57447a790c6dc3ede2d02a947d224, >=cc53ce53c86924bfe98a12ea20b7465038a08792 <6cba08dc1922140d260cfeb30bbda4ee1bf869d8, >=cc53ce53c86924bfe98a12ea20b7465038a08792 <bdf5a0f88d21239d8f9f7519b87359ba95fd045c, =2.6.38 | e301c5cdb0dc2c4aeffc0c055ea15615d9c51fdc, 085cfde7c2186acaad103f02d2c25435ad5224e9, 18847cbf5900f5c6c55bef5a6f7a34a1918d1181, 194316df81263519156ebe714c4a286bee00e5be, 2bc4343308d85ee4e0dd3877b384306c96f114c2, 467d56fd3ff57447a790c6dc3ede2d02a947d224, 6cba08dc1922140d260cfeb30bbda4ee1bf869d8, bdf5a0f88d21239d8f9f7519b87359ba95fd045c |
| linux-kernel: Kernel | >=5.11.0 <5.15.224, >=5.16.0 <6.1.191, >=6.13.0 <6.18.50, >=6.19.0 <7.2.4, >=6.2.0 <6.6.157, >=6.7.0 <6.12.109, >=2.6.38 <5.10.273 | 5.15.224, 6.1.191, 6.18.50, 7.2.4, 6.6.157, 6.12.109, 5.10.273 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket