Description (CNA)
In the Linux kernel, the following vulnerability has been resolved: mm/damon/core: avoid infinite kdamond_merge_regions() internal loop Patch series "mm/damon: unurgent fixes for infinite loop, NULL de-ref and races", v1.1. Sashiko found a few issues in DAMON that could cause infinite loop, NULL dereference and monitoring results degradation. The first two sounds scary but the infinite loop happens only under unreasonable user setup. The NULL dereference is only in a unit test. Monitoring results degradation is trivial since it is only best-effort, and those happens from only unlikely races. Still those are bugs that better to fix if possible. Fix those. This patch (of 6): Due to online parameter update like events, the number of DAMON regions could be higher than the user-set upper limit. kdamond_merge_regions() repeats merge regions until the number meets the limit, while doubling the merge threshold up to the theoretical maximum threshold. It is tried only up to the theoretical maximum threshold because even the aggressive merging can fail from reducing the number of regions under the user-defined upper limit. For example, there could be many user-defined non-contiguous regions that cannot be merged. The threshold based loop break condition is evaluated by comparing the threshold for the next merging try against the theoretical maximum threshold. If max_thres is larger than UINT_MAX / 2, doubling the threshold could make it overflow, and bypass the loop break condition. In the case, if the number of regions cannot be reduced under the upper limit like explained above, the loop will run infinitely. Prevent the case by doing the break condition check before doubling the threshold. Also, prevent the threshold exceeding the maximum threshold, as it could overflow and apply the wrong merge threshold. This issue is unlikely to occur in real world, since having the max_thres higher than UINT_MAX / 2 require unrealistically large aggregation intervals compared to the sampling interval. Also, it requires an unrealistically large number of uncontiguous regions setup. Nonetheless, the consequence is bad and the fix is simple. The issue was discovered [1] by Sashiko.
Affected (CNA)
| Vendor / product | Versions |
|---|---|
| Linux / Linux | affected 1e865019cef354a5f0314491b4b4fc9f9a613642 before 407da1dd7f48e5ba22ceb8834f6923390632d025; affected d7eda72e59bbf3ed592db7ff0fd8c246c73149a8 before 65edd8b3a88278c9f8e5c7d8c15d4f296ce35078; affected 11078e2d11465518a9e85096bd28f8cd5fa1ea41 before 5b0953f86d65855dc901050f40bbe6da0475d198; affected 310d6c15e9104c99d5d9d0ff8e5383a79da7d5e6 before 769c16699c89811386eb003c8fd9dcb8d405b316; affected 310d6c15e9104c99d5d9d0ff8e5383a79da7d5e6 before 50a7a5aec1aa43efc297fd4377c1cbdc7d15620d; affected 310d6c15e9104c99d5d9d0ff8e5383a79da7d5e6 before 8a96a06e04d210845be5d9581c0e9e338947e8f8; affected 310d6c15e9104c99d5d9d0ff8e5383a79da7d5e6 before 123e4619ab6c8ab1c4cb1d7a58311a2af13929cd; affected f2bd3184b6aeca6a497394b558337246e09fc02d; affected 5.15.164 before 5.15.222; affected 6.1.101 before 6.1.189; affected 6.6.41 before 6.6.158; affected 6.9.10 before 6.10 |
| Linux / Linux | affected 6.10; unaffected 0 before 6.10; unaffected 5.15.222 through 5.15.*; unaffected 6.1.189 through 6.1.*; unaffected 6.6.158 through 6.6.*; unaffected 6.12.111 through 6.12.*; unaffected 6.18.53 through 6.18.*; unaffected 7.2.5 through 7.2.*; unaffected 7.3 through * |
CWE
No CWE identifiers supplied.
References
- https://git.kernel.org/stable/c/407da1dd7f48e5ba22ceb8834f6923390632d025
- https://git.kernel.org/stable/c/65edd8b3a88278c9f8e5c7d8c15d4f296ce35078
- https://git.kernel.org/stable/c/5b0953f86d65855dc901050f40bbe6da0475d198
- https://git.kernel.org/stable/c/769c16699c89811386eb003c8fd9dcb8d405b316
- https://git.kernel.org/stable/c/50a7a5aec1aa43efc297fd4377c1cbdc7d15620d
- https://git.kernel.org/stable/c/8a96a06e04d210845be5d9581c0e9e338947e8f8
- https://git.kernel.org/stable/c/123e4619ab6c8ab1c4cb1d7a58311a2af13929cd