CVE-2026-64458

Technical Description

In the Linux kernel, the following vulnerability has been resolved:

mm/damon/ops-common: handle extreme intervals in damon_hot_score()

Fix three issues in damon_hot_score() that comes from wrong handling of

extreme (zero or too high) monitoring intervals user setup.

When the user sets sampling interval zero, damon_max_nr_accesses(), which

is called from damon_hot_score(), causes a divide-by-zero. Needless to

say, it is a problem.

When the user sets the aggregation interval zero, the function returns

zero. It is wrong, since the real maximum nr_acceses in the setup should

be one. Worse yet, it can cause another divide-by-zero from its caller,

damon_hot_score(), since it uses damon_max_nr_accesses() return value as a

denominator.

When the user sets the aggregation interval very high, damon_hot_score()

could return a value out of [0, DAMOS_MAX_SCORE] range. Since the return

value is used as an index to the regions_score_histogram array, which is

DAMOS_MAX_SCORE+1 size, it causes

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

References