CVE-2026-99240

mm/damon/core: error damos_commit_quota_goal() for zero target_value

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.

Key facts

Published
2 Nov 2026
Last changed
3 Nov 2026
Assigned by
Linux
EPSS
0.157% likely to be exploited in the next 30 days, higher than 4.885% of CVEs (scores for 16 Nov 2026)

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
LinuxLinux
  • Default status: unaffected
  • c5e67d40a10234541e220750297304df79aaedd0 up to but excluding d5482be6243b816730689099c017109eb8730dd5 (affected)
  • c5e67d40a10234541e220750297304df79aaedd0 up to but excluding cc190c4073f570fd78a9d00dd3d13a71eced5403 (affected)
  • c5e67d40a10234541e220750297304df79aaedd0 up to but excluding 156aeda4d74e9007b56492ed1f3b5838822632be (affected)
  • c5e67d40a10234541e220750297304df79aaedd0 up to but excluding 610c4438fb66e06d9e693c0ad3b2c1be54c0d61f (affected)
LinuxLinux
  • Default status: affected
  • 6.17 (affected)
  • 0 up to but excluding 6.17 (unaffected)
  • 6.18.60 up to and including 6.18.* (unaffected)
  • 7.2.14 up to and including 7.2.* (unaffected)
  • 7.3.1 up to and including 7.3.* (unaffected)
  • 7.4-rc1 up to and including * (unaffected)

Timeline

  1. 2 Nov 2026 Published

References