Vulnerability-Lookup

GHSA-36PF-5FQ6-8GFR

Vulnerability from github – Published: 2026-11-02 18:32 – Updated: 2026-11-03 21:32

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.

Show details on source website

JSON

To clipboard

{
  "affected": [],
  "aliases": [
    "CVE-2026-99240"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-11-02T16:17:49Z",
    "severity": null
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nmm/damon/core: error damos_commit_quota_goal() for zero target_value\n\nPatch series \"mm/damon: move zero damos quota target_value handling to the\ncore layer\".\n\nHaving zero DAMOS quota target value can cause division by zero.  DAMON\nAPI callers are checking the target value parameters to avoid that.  It is\neasy to make mistakes in some of the multiple API callers.  Move that to\nthe core layer.\n\nPatch 1 adds the corner case handling into the core layer DAMON parameters\nvalidation logic.  Patches 2 and 3 remove no more needed DAMON API callers\nside handling of the corner case in DAMON_LRU_SORT and DMON_SAMPLIE_MTIER,\nrespectively.\n\n\nThis patch (of 3):\n\nIf a DAMOS scheme has a damos_quota_goal of zero target_value,\ndamos_quota_goal() could trigger division-by-zero error.  Hence each DAMON\nAPI callers should do the zero target_value validation.  It is easy to\nmake mistakes.  Actually such bugs in DAMON_LRU_SORT and\nDAMON_SAMPLE_MTIER were found and fixed [1].\n\nIt is better to handle the corner case only once in the core layer,\ninstead of multiple places in all DAMON API callers.  One straightforward\noption is using an alternative denominator for the corner case in the\ndamos_quota_goal().  However, the zero target_value is meaningless.  In\nthis case, the quota goal is always evaluated as achieved or\nover-achieved.  The quota will only keep being reduced.\n\nSimply avoid using zero target_value by adding a check in the core layer\nDAMOS quota goal parameters validation/commit path,\ndamos_commit_quota_goal().  Update it to return an error in the case. \nAlso update its caller to propagate the error.",
  "id": "GHSA-36pf-5fq6-8gfr",
  "modified": "2026-11-03T21:32:00Z",
  "published": "2026-11-02T18:32:27Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-99240"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/156aeda4d74e9007b56492ed1f3b5838822632be"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/610c4438fb66e06d9e693c0ad3b2c1be54c0d61f"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/cc190c4073f570fd78a9d00dd3d13a71eced5403"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/d5482be6243b816730689099c017109eb8730dd5"
    }
  ],
  "schema_version": "1.4.0",
  "severity": []
}

CVE-2026-99240 (GCVE-0-2026-99240)

Vulnerability from cvelistv5 – Published: 2026-11-02 16:06 – Updated: 2026-11-03 19:13

Title

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

Summary

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.

Severity

No CVSS data available.

Assigner

Linux CNA under the mitre root

CNA scorecard D 53/100 over 6637 records in the last 180 days details

References

4 references

URL	Tags
https://git.kernel.org/stable/c/d5482be6243b81673…
https://git.kernel.org/stable/c/cc190c4073f570fd7…
https://git.kernel.org/stable/c/156aeda4d74e9007b…
https://git.kernel.org/stable/c/610c4438fb66e06d9…

Impacted products

2 products

Vendor	Product	Version
Linux	Linux	Affected: c5e67d40a10234541e220750297304df79aaedd0 , < d5482be6243b816730689099c017109eb8730dd5 (git) Affected: c5e67d40a10234541e220750297304df79aaedd0 , < cc190c4073f570fd78a9d00dd3d13a71eced5403 (git) Affected: c5e67d40a10234541e220750297304df79aaedd0 , < 156aeda4d74e9007b56492ed1f3b5838822632be (git) Affected: c5e67d40a10234541e220750297304df79aaedd0 , < 610c4438fb66e06d9e693c0ad3b2c1be54c0d61f (git)
Linux	Linux	Affected: 6.17 Unaffected: 0 , < 6.17 (semver) Unaffected: 6.18.60 , ≤ 6.18.* (semver) Unaffected: 7.2.14 , ≤ 7.2.* (semver) Unaffected: 7.3.1 , ≤ 7.3.* (semver) Unaffected: 7.4-rc1 , ≤ * (original_commit_for_fix)

Show details on NVD website

JSON

To clipboard

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "mm/damon/core.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "d5482be6243b816730689099c017109eb8730dd5",
              "status": "affected",
              "version": "c5e67d40a10234541e220750297304df79aaedd0",
              "versionType": "git"
            },
            {
              "lessThan": "cc190c4073f570fd78a9d00dd3d13a71eced5403",
              "status": "affected",
              "version": "c5e67d40a10234541e220750297304df79aaedd0",
              "versionType": "git"
            },
            {
              "lessThan": "156aeda4d74e9007b56492ed1f3b5838822632be",
              "status": "affected",
              "version": "c5e67d40a10234541e220750297304df79aaedd0",
              "versionType": "git"
            },
            {
              "lessThan": "610c4438fb66e06d9e693c0ad3b2c1be54c0d61f",
              "status": "affected",
              "version": "c5e67d40a10234541e220750297304df79aaedd0",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "mm/damon/core.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "6.17"
            },
            {
              "lessThan": "6.17",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.18.*",
              "status": "unaffected",
              "version": "6.18.60",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "7.2.*",
              "status": "unaffected",
              "version": "7.2.14",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "7.3.*",
              "status": "unaffected",
              "version": "7.3.1",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "7.4-rc1",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.18.60",
                  "versionStartIncluding": "6.17",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.2.14",
                  "versionStartIncluding": "6.17",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.3.1",
                  "versionStartIncluding": "6.17",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.4-rc1",
                  "versionStartIncluding": "6.17",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nmm/damon/core: error damos_commit_quota_goal() for zero target_value\n\nPatch series \"mm/damon: move zero damos quota target_value handling to the\ncore layer\".\n\nHaving zero DAMOS quota target value can cause division by zero.  DAMON\nAPI callers are checking the target value parameters to avoid that.  It is\neasy to make mistakes in some of the multiple API callers.  Move that to\nthe core layer.\n\nPatch 1 adds the corner case handling into the core layer DAMON parameters\nvalidation logic.  Patches 2 and 3 remove no more needed DAMON API callers\nside handling of the corner case in DAMON_LRU_SORT and DMON_SAMPLIE_MTIER,\nrespectively.\n\n\nThis patch (of 3):\n\nIf a DAMOS scheme has a damos_quota_goal of zero target_value,\ndamos_quota_goal() could trigger division-by-zero error.  Hence each DAMON\nAPI callers should do the zero target_value validation.  It is easy to\nmake mistakes.  Actually such bugs in DAMON_LRU_SORT and\nDAMON_SAMPLE_MTIER were found and fixed [1].\n\nIt is better to handle the corner case only once in the core layer,\ninstead of multiple places in all DAMON API callers.  One straightforward\noption is using an alternative denominator for the corner case in the\ndamos_quota_goal().  However, the zero target_value is meaningless.  In\nthis case, the quota goal is always evaluated as achieved or\nover-achieved.  The quota will only keep being reduced.\n\nSimply avoid using zero target_value by adding a check in the core layer\nDAMOS quota goal parameters validation/commit path,\ndamos_commit_quota_goal().  Update it to return an error in the case. \nAlso update its caller to propagate the error."
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-11-03T19:13:07.661Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/d5482be6243b816730689099c017109eb8730dd5"
        },
        {
          "url": "https://git.kernel.org/stable/c/cc190c4073f570fd78a9d00dd3d13a71eced5403"
        },
        {
          "url": "https://git.kernel.org/stable/c/156aeda4d74e9007b56492ed1f3b5838822632be"
        },
        {
          "url": "https://git.kernel.org/stable/c/610c4438fb66e06d9e693c0ad3b2c1be54c0d61f"
        }
      ],
      "title": "mm/damon/core: error damos_commit_quota_goal() for zero target_value",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2026-99240",
    "datePublished": "2026-11-02T16:06:43.703Z",
    "dateReserved": "2026-09-25T10:25:14.403Z",
    "dateUpdated": "2026-11-03T19:13:07.661Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

Sightings

Author	Source	Type	Date	Other

Nomenclature

Seen: The vulnerability was mentioned, discussed, or observed by the user.
Confirmed: The vulnerability has been validated from an analyst's perspective.
Published Proof of Concept: A public proof of concept is available for this vulnerability.
Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
Not confirmed: The user expressed doubt about the validity of the vulnerability.
Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

Order JSON

Publication & reservation Sightings KEV catalogs Other timestamps

Loading timeline…

The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base model, served locally by ML-Gateway. They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.

Related by attack behaviour

Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.

Action not permitted