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.

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - 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. (CVE-2026-89796)

Note that Nessus relies on the presence of the package as reported by the vendor.

ID	Name	Product	Family	Type	Severity
373463	Amazon Linux 2023 : bpftool, kernel, kernel-devel (ALAS2023-2026-3336)	Nessus	Amazon Linux Local Security Checks	Local	medium
371759	Amazon Linux 2 : kernel (ALASKERNEL-5.15-2026-119)	Nessus	Amazon Linux Local Security Checks	Local	medium
366919	Debian dla-4841 : ata-modules-6.1.0-53-armmp-di - security update	Nessus	Debian Local Security Checks	Local	high
365258	Amazon Linux 2023 : bpftool6.18, kernel6.18, kernel6.18-devel (ALAS2023-2026-3192)	Nessus	Amazon Linux Local Security Checks	Local	high
365209	Amazon Linux 2023 : bpftool6.12, kernel6.12, kernel6.12-devel (ALAS2023-2026-3193)	Nessus	Amazon Linux Local Security Checks	Local	medium
364137	Oracle Linux 10 / 9 : Unbreakable Enterprise kernel (ELSA-2026-500374)	Nessus	Oracle Linux Local Security Checks	Local	high
362907	Debian dla-4817 : ata-modules-6.12.107+deb12-armmp-di - security update	Nessus	Debian Local Security Checks	Local	high
351155	Debian dsa-6528 : ata-modules-6.12.111+deb13-armmp-di - security update	Nessus	Debian Local Security Checks	Local	high
346519	Linux Distros Unpatched Vulnerability : CVE-2026-89796	Nessus	Misc.	Local	medium

Detections

Analytics

CVE-2026-89796

medium

Tenable Plugins

medium

medium

high

high

medium

high

high

high

medium