PatchSiren cyber security CVE debrief
CVE-2026-64458 Linux CVE debrief
A divide-by-zero vulnerability exists in the Linux kernel's damon_hot_score() function. When a user sets the sampling interval to zero, damon_max_nr_accesses() causes a divide-by-zero error. Additionally, setting the aggregation interval to zero or a very high value can lead to incorrect results or out-of-bounds array access. The issue was discovered and resolved by fixing the damon_max_nr_accesses() and damon_hot_score() functions to handle extreme intervals correctly. Linux kernel users and administrators should verify their systems' exposure and update to a patched version if available.
- Vendor
- Linux
- Product
- Unknown
- CVSS
- Unknown
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-07-25
- Original CVE updated
- 2026-11-03
- Advisory published
- 2026-07-25
- Advisory updated
- 2026-11-03
Who should care
Linux kernel users and administrators, Linux distributions, and security teams responsible for vulnerability management and system security should verify their systems' exposure and update to a patched version if available. Affected operators and platforms may be impacted by this vulnerability.
Why it matters
A divide-by-zero vulnerability in the Linux kernel's damon_hot_score() function can cause system crashes or unexpected behavior. Linux kernel users and administrators should verify their systems' exposure and update to a patched version if available.
- Verify system exposure and update to a patched version
- Monitor system logs for potential exploitation attempts
- Review system configurations for vulnerable settings
Technical summary
The Linux kernel's damon_hot_score() function is vulnerable to a divide-by-zero error when the sampling interval is set to zero. Additionally, incorrect handling of extreme aggregation intervals can lead to out-of-bounds array access. The vulnerability was resolved by fixing the damon_max_nr_accesses() and damon_hot_score() functions to handle extreme intervals correctly. Linux kernel users should verify their systems' exposure and update to a patched version if available. The fix addresses divide-by-zero errors and out-of-bounds array access issues.
Defensive priority
Linux kernel users should verify their systems' exposure and update to a patched version if available.
Recommended defensive actions
- Verify Linux kernel version and check for updates
- Review system configurations for vulnerable settings
- Monitor system logs for potential exploitation attempts
- Check relevant monitoring, detection, and logs for exposed assets that need extra review
- Track exceptions, retest remediated assets, and close the item only after evidence is documented
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
- Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
Evidence notes
The issue was discovered [1] by Sashiko. The vulnerability was resolved by explicitly handling the zero intervals in damon_max_nr_accesses() and applying [0, DAMOS_MAX_SCORE] bounds before returning from damon_hot_score(). The fix addresses divide-by-zero errors and out-of-bounds array access issues. Linux kernel users should verify their systems' exposure and update to a patched version if available. Evidence is limited to public sources and may not be comprehensive.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-64458 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-64458
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-64458 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-64458
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/35d4a3cf70a855b50e53189ac2f8463e20a02046
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/58321b4e6e4f0f412069ab27ccdd56292757343a
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/74fef68d521150281e36cdaa20e9e1ee3e3aa146
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/76e415ea88d20f022ed5cfcf78c50e156a267e91
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/9c8f31eaae6140ecadec0c07320498a944556de2
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/ef2ae10a4582bc92b7e944181bbd2f87f3d30f3a
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.