Linux
NFSv4: remove callback IDR entry on client allocation failure
In the Linux kernel, the following vulnerability has been resolved: NFSv4: remove callback IDR entry on client allocation failure nfs4_alloc_client() allocates an NFSv4.0 callback identifier before it finishes setting up the client. If any later initialization step fails, the error path frees the nfs_client directly with nfs_free_client(). That bypasses nfs_put_client(), which is where the callback IDR entry is removed during normal teardown. A failed allocation can therefore leave cb_ident_idr pointing at a freed nfs_client. A later NFSv4.0 callback lookup by cb_ident would find the stale pointer and take a reference to it. Make the callback IDR removal helper callable by the allocation failure path, and remove the callback identifier before freeing the client. This was found by a local static-analysis checker for publish-before-free lifetime bugs and confirmed by manual inspection.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= f4eecd5da3422e82e88e36c33cbd2595eebcacb1, < 68c721391b761dbe38d5b0094d2bb6e8489ad92b
- >= f4eecd5da3422e82e88e36c33cbd2595eebcacb1, < 9bfdd0f591307b5198826a0e7a5b2f35f87acd2d
- >= f4eecd5da3422e82e88e36c33cbd2595eebcacb1, < 7c4812eb96bdcafb31a65b12f2aa96659429d1d4
- >= f4eecd5da3422e82e88e36c33cbd2595eebcacb1, < fc95ca82d5ae598c428ab5a00ae69f8526d59371
- >= f4eecd5da3422e82e88e36c33cbd2595eebcacb1, < 80b1c3d5a881f7d9081aa9f46da9742878a0f893
- >= f4eecd5da3422e82e88e36c33cbd2595eebcacb1, < 3f2387e8bfbc4efda5d77c3a11a028d0a119c48f
- >= f4eecd5da3422e82e88e36c33cbd2595eebcacb1, < 5891c03e150920618db0e9c4ea2d772abacdcfd1
- >= f4eecd5da3422e82e88e36c33cbd2595eebcacb1, < d05c2007b3d84ccba11dc6e9cb3202768cc72f14
Fixed in 68c721391b761dbe38d5b0094d2bb6e8489ad92b, 9bfdd0f591307b5198826a0e7a5b2f35f87acd2d, 7c4812eb96bdcafb31a65b12f2aa96659429d1d4, fc95ca82d5ae598c428ab5a00ae69f8526d59371, 80b1c3d5a881f7d9081aa9f46da9742878a0f893, 3f2387e8bfbc4efda5d77c3a11a028d0a119c48f, 5891c03e150920618db0e9c4ea2d772abacdcfd1, d05c2007b3d84ccba11dc6e9cb3202768cc72f14
- 2.6.38
Fixed in 0, 5.10.270, 5.15.221, 6.1.188, 6.6.157, 6.12.110, 6.18.52, 7.2.6, 7.3
Mitigation
Upgrade Linux to 68c721391b761dbe38d5b0094d2bb6e8489ad92b or 9bfdd0f591307b5198826a0e7a5b2f35f87acd2d or 7c4812eb96bdcafb31a65b12f2aa96659429d1d4 or fc95ca82d5ae598c428ab5a00ae69f8526d59371 or 80b1c3d5a881f7d9081aa9f46da9742878a0f893 or 3f2387e8bfbc4efda5d77c3a11a028d0a119c48f or 5891c03e150920618db0e9c4ea2d772abacdcfd1 or d05c2007b3d84ccba11dc6e9cb3202768cc72f14 or later.
Upgrade Linux to 0 or 5.10.270 or 5.15.221 or 6.1.188 or 6.6.157 or 6.12.110 or 6.18.52 or 7.2.6 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.