mm/vmalloc: take vmap_purge_lock in shrinker
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 12f2341b4c235d5593a433abac201c1c6725787f, Kernel 687ccdf582169cd680aeaf24cc953807c4cd4345, Kernel c15ff206ba78820bf2873d0c668a882e99f4b631 and 1 more.
In the Linux kernel, the following vulnerability has been resolved: mm/vmalloc: take vmap_purge_lock in shrinker decay_va_pool_node() can be invoked concurrently from two paths: __purge_vmap_area_lazy() when pools are being purged, and the shrinker via vmap_node_shrink_scan(). However, decay_va_pool_node() is not safe to run concurrently, and the shrinker path currently lacks serialization, leading to races and possible leaks. Protect decay_va_pool_node() by taking vmap_purge_lock in the shrinker path to ensure serialization with purge users.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.9, >=7679ba6b36dbb300b757b672d6a32a606499e14b <12f2341b4c235d5593a433abac201c1c6725787f, >=7679ba6b36dbb300b757b672d6a32a606499e14b <687ccdf582169cd680aeaf24cc953807c4cd4345, >=7679ba6b36dbb300b757b672d6a32a606499e14b <c15ff206ba78820bf2873d0c668a882e99f4b631, >=7679ba6b36dbb300b757b672d6a32a606499e14b <ec05f51f1e65bce95528543eb73fda56fd201d94 | 12f2341b4c235d5593a433abac201c1c6725787f, 687ccdf582169cd680aeaf24cc953807c4cd4345, c15ff206ba78820bf2873d0c668a882e99f4b631, ec05f51f1e65bce95528543eb73fda56fd201d94 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket