CVE-2026-53334
N/A
Summary
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 Software
| Vendor | Product | Version Range | Status |
|---|---|---|---|
| Linux | Linux | 3f7a914ab9a5e46cf8aac7de270f02aa3f63de04 < 66bc00ea37fa8ec14be5a3909d067a5967ef234b | affected |
| Linux | Linux | 3f7a914ab9a5e46cf8aac7de270f02aa3f63de04 < 635b45ce61de53a9357e28ac97461428cdb650f0 | affected |
| Linux | Linux | 3f7a914ab9a5e46cf8aac7de270f02aa3f63de04 < 7e2ed8a29427af534bf2cb9b8bc51762b8b6e654 | affected |
| Linux | Linux | 6.18 | affected |
| Linux | Linux | 0 < 6.18 | unaffected |
| Linux | Linux | 6.18.36 <= 6.18.* | unaffected |
| Linux | Linux | 7.0.13 <= 7.0.* | unaffected |
| Linux | Linux | 7.1 <= * | unaffected |
Weaknesses
References
- https://git.kernel.org/stable/c/66bc00ea37fa8ec14be5a3909d067a5967ef234b
- https://git.kernel.org/stable/c/635b45ce61de53a9357e28ac97461428cdb650f0
- https://git.kernel.org/stable/c/7e2ed8a29427af534bf2cb9b8bc51762b8b6e654
Feedback
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.