CVE-2026-64458: mm/damon/ops-common: handle extreme intervals in damon_hot_score()
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.12% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 35d4a3cf70a855b50e53189ac2f8463e20a02046, 58321b4e6e4f0f412069ab27ccdd56292757343a, 74fef68d521150281e36cdaa20e9e1ee3e3aa146.
Low priority for now. Upgrade to Linux Linux 35d4a3cf70a855b50e53189ac2f8463e20a02046, 58321b4e6e4f0f412069ab27ccdd56292757343a, 74fef68d521150281e36cdaa20e9e1ee3e3aa146 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Jul 25, 2026
- Updated
- Nov 12, 2026
- EPSS
- 0.1% · 2th percentile
- CWE
- CWE-369
Report tools
Action score
22
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.16affected
- 198f0f4c58b9f481e4e51c8c70a6ab9852bbab7f and later · before 58321b4e6e4f0f412069ab27ccdd56292757343aaffected · git
- 198f0f4c58b9f481e4e51c8c70a6ab9852bbab7f and later · before 74fef68d521150281e36cdaa20e9e1ee3e3aa146affected · git
- 198f0f4c58b9f481e4e51c8c70a6ab9852bbab7f and later · before ef2ae10a4582bc92b7e944181bbd2f87f3d30f3aaffected · git
- 198f0f4c58b9f481e4e51c8c70a6ab9852bbab7f and later · before 9c8f31eaae6140ecadec0c07320498a944556de2affected · git
- 198f0f4c58b9f481e4e51c8c70a6ab9852bbab7f and later · before 76e415ea88d20f022ed5cfcf78c50e156a267e91affected · git
- 198f0f4c58b9f481e4e51c8c70a6ab9852bbab7f and later · before 35d4a3cf70a855b50e53189ac2f8463e20a02046affected · git
- before 5.16not affected · semver
- 6.1.178 and later · up to and including 6.1.*not affected · semver
- 6.6.145 and later · up to and including 6.6.*not affected · semver
Affected versions · NVD (6)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel5.16 and later · before 6.1.178
- linux linux kernel6.2 and later · before 6.6.145
- linux linux kernel6.7 and later · before 6.12.96
- linux linux kernel6.13 and later · before 6.18.39
- linux linux kernel6.19 and later · before 7.1.4
- linux linux kernel7.2
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.180-1 | 6.1.180-1 |
| Debian:12 | linux-6.12 | before 6.12.100-1~deb12u1 | 6.12.100-1~deb12u1 |
| Debian:13 | linux | before 6.12.96-1 | 6.12.96-1 |
| Debian:14 | linux | before 7.1.4-1 | 7.1.4-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2026-64456Jul 25, 2026 · hwrng: virtio: clamp device-reported used.len at copy_data()30Monitor
- ← EarlierCVE-2026-64457Jul 25, 2026 · virtio_pci: fix vq info pointer lookup via wrong index22Monitor
- Later →CVE-2026-64460Jul 25, 2026 · PCI/IOV: Skip VF Resizable BAR restore on read error28Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 35d4a3cf70a855b50e53189ac2f8463e20a02046 | Vendor (CNA) |
| Linux Linux | 58321b4e6e4f0f412069ab27ccdd56292757343a | Vendor (CNA) |
| Linux Linux | 74fef68d521150281e36cdaa20e9e1ee3e3aa146 | Vendor (CNA) |
| Linux Linux | 76e415ea88d20f022ed5cfcf78c50e156a267e91 | Vendor (CNA) |
| Linux Linux | 9c8f31eaae6140ecadec0c07320498a944556de2 | Vendor (CNA) |
| Linux Linux | ef2ae10a4582bc92b7e944181bbd2f87f3d30f3a | Vendor (CNA) |
| debian:linux | 6.1.180-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.100-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-642750 days apartInput: elan_i2c - prevent division by zero and arithmetic underflow22Monitor
- CVE-2026-642361 days aparti2c: davinci: fix division by zero on missing clock-frequency22Monitor
- CVE-2026-638366 days apartbatman-adv: tp_meter: avoid divide-by-zero for dec_cwnd22Monitor
- CVE-2026-639316 days apartiio: chemical: scd30: fix division by zero in write_raw22Monitor
- CVE-2026-639336 days apartiio: gyro: adis16260: fix division by zero in write_raw22Monitor
- CVE-2026-639356 days apartiio: adc: nxp-sar-adc: fix division by zero in write_raw22Monitor
Not on record for this CVE: patch commit or PR link · researcher credit · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-369 · Divide By ZeroCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- CVSS— → 5.5
- Severity— → medium
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/58321b4e6e4f0f412069ab27ccdd56292757343a
- git.kernel.org/stable/c/74fef68d521150281e36cdaa20e9e1ee3e3aa146
- git.kernel.org/stable/c/76e415ea88d20f022ed5cfcf78c50e156a267e91
- git.kernel.org/stable/c/9c8f31eaae6140ecadec0c07320498a944556de2
- git.kernel.org/stable/c/ef2ae10a4582bc92b7e944181bbd2f87f3d30f3a
Vendor advisories and official records. Exploit/PoC links are deliberately left out.