CVE-2026-99240
mm/damon/core: error damos_commit_quota_goal() for zero target_value
What happened?
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.
Affected software and versions
| Software | Version information | Fixed version |
|---|---|---|
| LinuxLinux | affected: c5e67d40a10234541e220750297304df79aaedd0 to < d5482be6243b816730689099c017109eb8730dd5; affected: c5e67d40a10234541e220750297304df79aaedd0 to < cc190c4073f570fd78a9d00dd3d13a71eced5403; affected: c5e67d40a10234541e220750297304df79aaedd0 to < 156aeda4d74e9007b56492ed1f3b5838822632be; affected: c5e67d40a10234541e220750297304df79aaedd0 to < 610c4438fb66e06d9e693c0ad3b2c1be54c0d61f | See vendor advisory |
| LinuxLinux | affected: 6.17; unaffected: 0 to < 6.17; unaffected: 6.18.60 to ≤ 6.18.*; unaffected: 7.2.14 to ≤ 7.2.*; unaffected: 7.3.1 to ≤ 7.3.*; unaffected: 7.4-rc1 to ≤ * | See vendor advisory |
Version information comes from the source record and can include unaffected products and exceptions. Distribution packages may contain backported fixes: an older upstream version alone does not prove a server is affected.
Is it being exploited?
This CVE was not listed in the CISA catalogue at our last retrieval. This does not establish that exploitation is absent.
How to respond
- Confirm the product, installed package version, and any configuration requirements in the vendor advisory.
- Follow the vendor’s remediation or workaround guidance in the references below. Structured fixed-version data is unavailable here; the publisher’s description may include a fix or workaround.
- Restart affected services if required, then verify the running version. Known exploitation may warrant investigation as well as patching.
Sources and remediation references
- https://www.cve.org/CVERecord?id=CVE-2026-99240
- https://git.kernel.org/stable/c/d5482be6243b816730689099c017109eb8730dd5
- https://git.kernel.org/stable/c/cc190c4073f570fd78a9d00dd3d13a71eced5403
- https://git.kernel.org/stable/c/156aeda4d74e9007b56492ed1f3b5838822632be
- https://git.kernel.org/stable/c/610c4438fb66e06d9e693c0ad3b2c1be54c0d61f