VDB

CVE-2026-64458

CVE-2026-64458 PUBLISHED

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

Reported by linux · Published July 25, 2026

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 out of bounds array access. The issues can be relatively easily reproduced like below. The sysfs write permission is required, though. # ./damo start --damos_action lru_prio --damos_quota_space 100M \ --damos_quota_interval 1s # cd /sys/kernel/mm/damon/admin/kdamonds/0 # echo 0 > contexts/0/monitoring_attrs/intervals/sample_us # echo 0 > contexts/0/monitoring_attrs/intervals/aggr_us # echo commit > state # dmesg [...] [ 131.329762] Oops: divide error: 0000 [#1] SMP NOPTI [...] [ 131.336089] RIP: 0010:damon_hot_score+0x27/0xd0 [...] Fix the divide-by-zero intervals problems by explicitly handling the zero intervals in damon_max_nr_accesses(). Fix the out-of-bound array access by applying [0, DAMOS_MAX_SCORE] bounds before returning from damon_hot_score(). The issue was discovered [1] by Sashiko.

Fixed versions

Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.

PackageEcosystemFixed in
kernel6.18-headersAmazon Linux1:6.18.39-79.141.amzn2023
python3-perf6.18Amazon Linux1:6.18.39-79.141.amzn2023
kernel6.18-tools-develAmazon Linux1:6.18.39-79.141.amzn2023
kernel6.18-toolsAmazon Linux1:6.18.39-79.141.amzn2023
kernel6.18-modules-extraAmazon Linux1:6.18.39-79.141.amzn2023
kernel-toolsAmazon Linux1:6.1.180-225.360.amzn2023
python3-perfAmazon Linux1:6.1.180-225.360.amzn2023
kernel6.12-develAmazon Linux1:6.12.100-125.179.amzn2023
perfAmazon Linux1:6.1.180-225.360.amzn2023
kernel6.18Amazon Linux1:6.18.39-79.141.amzn2023
kernel6.12-headersAmazon Linux1:6.12.100-125.179.amzn2023
kernel-livepatch-6.1.180-225.360Amazon Linux1:1.0-0.amzn2023

6 more packages have a fixed version. See every fix in Lookup.

Affected products

VendorProductVersions
LinuxLinux198f0f4c58b9f481e4e51c8c70a6ab9852bbab7f, 198f0f4c58b9f481e4e51c8c70a6ab9852bbab7f, 198f0f4c58b9f481e4e51c8c70a6ab9852bbab7f
LinuxLinux5.16, 0, 6.1.178
amazon:2023kernel6.18-headers0
amazon:2023python3-perf6.180
amazon:2023kernel6.18-tools-devel0
amazon:2023kernel6.18-tools0
amazon:2023kernel6.18-modules-extra0
amazon:2023kernel-tools0
amazon:2023python3-perf0
amazon:2023kernel6.12-devel0
amazon:2023perf0
amazon:2023kernel6.180
amazon:2023kernel6.12-headers0
amazon:2023kernel-livepatch-6.1.180-225.3600
amazon:2023kernel-modules-extra-common0
amazon:2023bpftool0
amazon:2023kernel-tools-devel0
amazon:2023microvm-kernel6.180
amazon:2023bpftool6.120
LinuxLinux7.2, 198f0f4c58b9f481e4e51c8c70a6ab9852bbab7f, 198f0f4c58b9f481e4e51c8c70a6ab9852bbab7f

…and 18 more

Timeline

  • Jul 25, 2026 EPSS Score (13 in total, the first dated here)
  • Jul 25, 2026 Coalition ESS Score
  • Jul 25, 2026 CVE Published
  • Jul 26, 2026 Security Advisory (20 in total, the first dated here)
  • Aug 12, 2026 Distribution Patch (21 in total, the first dated here)
  • Nov 6, 2026 CVE Updated

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln CVE-2026-64458
vulnetix vdb fixes CVE-2026-64458

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/CVE-2026-64458/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

References

Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›