boxscore/security
CVE · referencelatest edition

Reference page — cumulative record through Thursday, November 19, 2026 UTC. Reference pages update as the archive grows; only dated daily editions are immutable pages of record.

CVE-2026-64458

Linux Linux — mm/damon/ops-common: handle extreme intervals in damon_hot_score()
  AV  AC  PR  UI  S  C  I  A   CVSS    EPSS   %ile   KEV
   L   L   L   N  U  N  N  H    5.5   .0013    2.6     —
AFFECTED
  Product  Versions                                    Fixed
  Linux    198f0f4c58b9f481e4e51c8c70a6ab9852bbab7f –  —
  Linux    5.16 –                                      6.1.178
TIMELINE
  Jul 19  Reserved by Linux
  Jul 25  Published (CNA: Linux)
  Nov 12  ENRICHED — CVE-2026-64458 (Linux). Received CVSS 5.5 and CPE data from NVD.
CWE-369 · CNA: Linux · CVSS v3.1 · 6 references · NVD status: Analyzed

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 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.

Lifecycle

Complete event history — 3 events, chronological
DateEventDetail
July 19, 2026ReservedReserved by Linux
July 25, 2026PublishedPublished (CNA: Linux)
November 12, 2026ENRICHEDENRICHED — CVE-2026-64458 (Linux). Received CVSS 5.5 and CPE data from NVD.

Affected

Affected products and packages — 2 rows
VendorProduct / PackageEcosystemVersion introducedFixed
LinuxLinux—198f0f4c58b9f481e4e51c8c70a6ab9852bbab7f—
LinuxLinux—5.166.1.178

Weaknesses

CWE-369

References (6)

Related

Authoritative record: CVE-2026-64458 at cve.org

Vendors: linux

Weaknesses: CWE-369

About this page

This is a reference page, not a dated page of record. It assembles the complete lifecycle of CVE-2026-64458 from the CVE Program record, NVD enrichment, the CISA KEV catalog, EPSS, and OSV advisories. The box score's numbers (CVSS, EPSS, KEV status) are current as of Thursday, November 19, 2026 UTC and are re-derived as the archive grows; only dated daily editions are immutable pages of record. The authoritative source for this identifier is cve.org.