Linux
nfsd: release path refs on follow_down() error
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 versions and mitigation
From the CVE record and the vendor's references.Affected
- >= cc53ce53c86924bfe98a12ea20b7465038a08792, < bdf5a0f88d21239d8f9f7519b87359ba95fd045c
- >= cc53ce53c86924bfe98a12ea20b7465038a08792, < 18847cbf5900f5c6c55bef5a6f7a34a1918d1181
- >= cc53ce53c86924bfe98a12ea20b7465038a08792, < e301c5cdb0dc2c4aeffc0c055ea15615d9c51fdc
- >= cc53ce53c86924bfe98a12ea20b7465038a08792, < 085cfde7c2186acaad103f02d2c25435ad5224e9
- >= cc53ce53c86924bfe98a12ea20b7465038a08792, < 194316df81263519156ebe714c4a286bee00e5be
- >= cc53ce53c86924bfe98a12ea20b7465038a08792, < 467d56fd3ff57447a790c6dc3ede2d02a947d224
- >= cc53ce53c86924bfe98a12ea20b7465038a08792, < 2bc4343308d85ee4e0dd3877b384306c96f114c2
- >= cc53ce53c86924bfe98a12ea20b7465038a08792, < 6cba08dc1922140d260cfeb30bbda4ee1bf869d8
Fixed in bdf5a0f88d21239d8f9f7519b87359ba95fd045c, 18847cbf5900f5c6c55bef5a6f7a34a1918d1181, e301c5cdb0dc2c4aeffc0c055ea15615d9c51fdc, 085cfde7c2186acaad103f02d2c25435ad5224e9, 194316df81263519156ebe714c4a286bee00e5be, 467d56fd3ff57447a790c6dc3ede2d02a947d224, 2bc4343308d85ee4e0dd3877b384306c96f114c2, 6cba08dc1922140d260cfeb30bbda4ee1bf869d8
- 2.6.38
Fixed in 0, 5.10.273, 5.15.224, 6.1.191, 6.6.157, 6.12.109, 6.18.50, 7.2.4, 7.3
Mitigation
Upgrade Linux to bdf5a0f88d21239d8f9f7519b87359ba95fd045c or 18847cbf5900f5c6c55bef5a6f7a34a1918d1181 or e301c5cdb0dc2c4aeffc0c055ea15615d9c51fdc or 085cfde7c2186acaad103f02d2c25435ad5224e9 or 194316df81263519156ebe714c4a286bee00e5be or 467d56fd3ff57447a790c6dc3ede2d02a947d224 or 2bc4343308d85ee4e0dd3877b384306c96f114c2 or 6cba08dc1922140d260cfeb30bbda4ee1bf869d8 or later.
Upgrade Linux to 0 or 5.10.273 or 5.15.224 or 6.1.191 or 6.6.157 or 6.12.109 or 6.18.50 or 7.2.4 or 7.3 or later.
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.