CVE-2026-99240mm/damon/core: error damos_commit_quota_goal() for zero target_value
- —Not scoredno CVSS score yet
- 0.16%Exploitation in 30 daysEPSS · top 95% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: mm/damon/core: error damos_commit_quota_goal() for zero target_value Patch series "mm/damon: move zero damos quota target_value handling to the core layer". Having zero DAMOS quota target value can cause division by zero. DAMON API callers are checking the target value parameters to avoid that. It is easy to make mistakes in some of the multiple API callers. Move that to the core layer. Patch 1 adds the corner case handling into the core layer DAMON parameters validation logic. Patches 2 and 3 remove no more needed DAMON API callers side handling of the corner case in DAMON_LRU_SORT and DMON_SAMPLIE_MTIER, respectively. This patch (of 3): If a DAMOS scheme has a damos_quota_goal of zero target_value, damos_quota_goal() could trigger division-by-zero error. Hence each DAMON API callers should do the zero target_value validation. It is easy to make mistakes. Actually such bugs in DAMON_LRU_SORT and DAMON_SAMPLE_MTIER were found and fixed [1]. It is better to handle the corner case only once in the core layer, instead of multiple places in all DAMON API callers. One straightforward option is using an alternative denominator for the corner case in the damos_quota_goal(). However, the zero target_value is meaningless. In this case, the quota goal is always evaluated as achieved or over-achieved. The quota will only keep being reduced. Simply avoid using zero target_value by adding a check in the core layer DAMOS quota goal parameters validation/commit path, damos_commit_quota_goal(). Update it to return an error in the case. Also update its caller to propagate the error.
Timeline
ID reserved
By Linux
- 38 days later
· 38 days later
Published
- 1 day later
· 1 day later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.16% · top 95% of all CVEs (13 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected c5e67d40a10234541e220750297304df79aaedd0 – < d5482be6243b816730689099c017109eb8730dd5
- affected c5e67d40a10234541e220750297304df79aaedd0 – < cc190c4073f570fd78a9d00dd3d13a71eced5403
- affected c5e67d40a10234541e220750297304df79aaedd0 – < 156aeda4d74e9007b56492ed1f3b5838822632be
- affected c5e67d40a10234541e220750297304df79aaedd0 – < 610c4438fb66e06d9e693c0ad3b2c1be54c0d61f
- affected 6.17
- unaffected < 6.17
- unaffected 6.18.60 – ≤ 6.18.*
- unaffected 7.2.14 – ≤ 7.2.*
- unaffected 7.3.1 – ≤ 7.3.*
- unaffected 7.4-rc1 – ≤ *
References
References4
- https://git.kernel.org/stable/c/d5482be6243b816730689099c017109eb8730dd5 (opens in a new tab)
- https://git.kernel.org/stable/c/cc190c4073f570fd78a9d00dd3d13a71eced5403 (opens in a new tab)
- https://git.kernel.org/stable/c/156aeda4d74e9007b56492ed1f3b5838822632be (opens in a new tab)
- https://git.kernel.org/stable/c/610c4438fb66e06d9e693c0ad3b2c1be54c0d61f (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-115282 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-99240)Record last updated .