mm/damon/reclaim: handle ctx allocation failure
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 635b45ce61de53a9357e28ac97461428cdb650f0, Kernel 66bc00ea37fa8ec14be5a3909d067a5967ef234b and Kernel 7e2ed8a29427af534bf2cb9b8bc51762b8b6e654.
In the Linux kernel, the following vulnerability has been resolved: mm/damon/reclaim: handle ctx allocation failure Patch series "mm/damon/{reclaim,lru_sort}: handle ctx allocation failures". DAMON_RECLAIM and DAMON_LRU_SORT could dereference NULL pointers if their damon_ctx object allocations fail. The bugs are expected to happen infrequently because the allocations are arguably too small to fail on common setups. But theoretically they are possible and the consequences are bad. Fix those. The issues were discovered [1] by Sashiko. This patch (of 2): DAMON_RECLAIM allocates the damon_ctx object for its kdamond in its init function. damon_reclaim_enabled_store() wrongly assumes the allocation will always succeed once tried. If the damon_ctx allocation was failed, therefore, code execution reaches to damon_commit_ctx() while 'ctx' is NULL. As a result, it dereferences the NULL 'ctx' pointer. Avoid the NULL dereference by returning -ENOMEM if 'ctx' is NULL.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.18, >=3f7a914ab9a5e46cf8aac7de270f02aa3f63de04 <635b45ce61de53a9357e28ac97461428cdb650f0, >=3f7a914ab9a5e46cf8aac7de270f02aa3f63de04 <66bc00ea37fa8ec14be5a3909d067a5967ef234b, >=3f7a914ab9a5e46cf8aac7de270f02aa3f63de04 <7e2ed8a29427af534bf2cb9b8bc51762b8b6e654 | 635b45ce61de53a9357e28ac97461428cdb650f0, 66bc00ea37fa8ec14be5a3909d067a5967ef234b, 7e2ed8a29427af534bf2cb9b8bc51762b8b6e654 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket