CVE-2026-64458
- Assigned byThe organization (CNA) that assigned this CVE ID and published the record, usually the vendor.
- kernel.org (opens in new tab)
- Published
- Last modified
- NVD statusWhether NVD has reviewed the record. Until it has, scores and product data come from the reporting organization alone. About NVD's statuses
- 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.
Exploitation
Whether attackers are exploiting this vulnerability, and how likely they are to try in the next 30 days.
CISA SSVC assessmentAbout SSVC (opens in new tab)
CISA's assessment of whether it's exploited, whether attacks can be automated and how much control an attacker gains.
- ExploitationWhether CISA has seen exploit code or attacks for this vulnerability.
- None known
- AutomatableWhether attackers can exploit it at scale without manual steps.
- No
- Technical impactHow much control of the affected system an attacker gains.
- Partial control
- Assessed
FIRST Exploit Prediction Scoring System (EPSS)About EPSS (opens in new tab)
FIRST's estimate of the chance attackers try to exploit this vulnerability in the next 30 days.
- Probability of exploitationIt predicts attempts, not success, and is updated daily.
- 0.128%
- Compared with other CVEs
- At or above 2.487% of scored CVEs
- Scored
Affected products
The products and versions with the vulnerability.
Listed by CNA
The products and versions affected, according to the organization that published this CVE.
| Vendor | Product | Affected versions |
|---|---|---|
| Linux | Linux |
6 commit ranges Not affected: < 5.16, 6.1.178, 6.6.145, 6.12.96, 6.18.39, 7.1.4, 7.2 |
Recommended actions
How to fix the vulnerability, or reduce the risk until you can.
Severity
How serious the vulnerability is if exploited, scored from 0 to 10 with the CVSS standard (opens in new tab).
- 5.5 MediumCVSS 3.1 · PrimaryPrimary scores are NVD's own. Secondary scores come from the organization that published the CVE, or from CISA. · Scored by NVD (opens in new tab)
- Attack vectorWhere the attacker has to be. Network is the widest: anywhere on the Internet.
- Local
- Attack complexityWhether the attack depends on conditions the attacker doesn't control.
- Low
- Privileges requiredThe access the attacker needs before attacking.
- Low
- User interactionWhether someone other than the attacker has to do something, like open a link.
- None
- ScopeWhether the attack can reach beyond the vulnerable component.
- Unchanged
- ConfidentialityHow much data the attacker can read.
- None
- IntegrityHow much data the attacker can change.
- None
- AvailabilityHow much the attacker can disrupt the system or service.
- High
CVSS:3.1/View in FIRST's calculator (opens in new tab)AV:L/ AC:L/ PR:L/ UI:N/ S:U/ C:N/ I:N/ A:H
Weaknesses and attack patterns
The type of bug behind the vulnerability, and how attackers exploit that type.
Divide By Zero · CWE-369 (opens in new tab)
The product divides a value by zero.
- Likelihood of exploitHow likely MITRE rates attacks on this type of weakness, in general rather than for this vulnerability.
- Medium
- AbstractionHow specific this weakness type is in MITRE's hierarchy, from broad pillars to specific variants. About MITRE's abstractions
- Base
- Mapping guidanceWhether MITRE recommends citing this weakness type for a single vulnerability. Broad types are discouraged in favor of more specific ones. About MITRE's mapping guidance
- Allowed
- Part ofThe broader weakness types this one belongs to. About MITRE's hierarchy
References
Advisories, patches, exploits and more about this vulnerability.
- Patch
- Patch
- Patch
- Patch
- Patch
- Patch
- View on NVD (opens in new tab)Last changed
- View on CVE.org (opens in new tab)Last changed
This product uses the NVD API but is not endorsed or certified by the NVD (opens in new tab). CVE records from the CVE List (opens in new tab), weakness types from MITRE's CWE (opens in new tab)™ and attack patterns from its CAPEC (opens in new tab)™ are © The MITRE Corporation, used under the CVE (opens in new tab), CWE (opens in new tab) and CAPEC (opens in new tab) terms of use. Known exploited vulnerabilities and SSVC assessments are from CISA. Exploit predictions are from FIRST's EPSS (opens in new tab). About this data