CVE-2026-99240

Source
https://cve.org/CVERecord?id=CVE-2026-99240
Import Source
https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2026-99240.json
JSON Data
https://api.test.osv.dev/v1/vulns/CVE-2026-99240
Downstream
Related
Published
2026-11-02T16:06:43Z
Modified
2026-11-10T17:27:01Z
Summary
mm/damon/core: error damos_commit_quota_goal() for zero target_value
Details

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.

Database specific
{
    "cna_assigner": "Linux",
    "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/99xxx/CVE-2026-99240.json"
}
References

Affected packages

Git / git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git

Affected ranges

Type
GIT
Repo
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Events
Introduced
c5e67d40a10234541e220750297304df79aaedd0
Fixed
d5482be6243b816730689099c017109eb8730dd5
Fixed
cc190c4073f570fd78a9d00dd3d13a71eced5403
Fixed
156aeda4d74e9007b56492ed1f3b5838822632be
Fixed
610c4438fb66e06d9e693c0ad3b2c1be54c0d61f

Database specific

source
"https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2026-99240.json"

Linux / Kernel

Package

Name
Kernel

Affected ranges

Type
ECOSYSTEM
Events
Introduced
6.17.0
Fixed
6.18.60
Type
ECOSYSTEM
Events
Introduced
6.19.0
Fixed
7.2.14
Type
ECOSYSTEM
Events
Introduced
7.3.0
Fixed
7.3.1

Database specific

source
"https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2026-99240.json"