SUNRPC: always drain cache_cleaner before destroying a cache_detail
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 820f9442e711a81749e70c40f149fc54c4ce0ca8 · < 2e861ce2aaa468351a6a47c4cbb4971ebb740c7b| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
SUNRPC: always drain cache_cleaner before destroying a cache_detail
sunrpc_destroy_cache_detail() only cancels the global cache_cleaner delayed_work when cache_list is empty. During per-netns teardown cache_list is never empty because init_net's caches remain registered, so the cancel never fires. After unlink, the caller proceeds to cache_destroy_net() which kfrees the cache_detail while cache_clean() may still hold a dangling pointer to it. The result is a use-after-free: cache_dequeue() takes cd->queue_lock on freed memory, and cache_put() dereferences cd->cache_put as a function pointer from freed slab.
Drop the list_empty guard so that cancel_delayed_work_sync() always runs, ensuring any in-flight cache_clean() completes before the cache_detail is freed. Re-arm the cleaner afterwards if other caches are still registered.
From the CVE record · Linux
A race during per-network-namespace teardown can free a SUNRPC cache_detail while cache_clean() still uses it, causing a use-after-free. The input does not specify how an attacker could trigger the race or whether access, authentication, or user interaction is required.
Engineers running Linux kernels with SUNRPC should check their builds; affected versions are not specified.