Vulnerability-Lookup

GHSA-RJC9-Q3Q5-8F95

Vulnerability from github – Published: 2026-09-16 12:30 – Updated: 2026-09-16 12:30

Details

In the Linux kernel, the following vulnerability has been resolved:

samples/damon/wsse: handle damon_start() failure

Patch series "samples/damon: handle damon_{start,stop}() failures".

All DAMON sample modules are not correctly handling failures from damon_start(). Among those, mtier also has an additional problem for handling of damon_stop() failures. wsse and prcl also have a problem in their damon_call() failure handling. As a result, memory leaks, next DAMON operation disruptions, and use-after-free can happen. Fix those.

Note that only the damon_start() failure caused issues can reliably be reproduced. Reproducing those issues require the admin permission, though.

This patch (of 6):

damon_sample_wsse_start() callers assume it will clean up resources when it fails. And the function does the cleanup for context buildup failures. However, it is not doing the cleanup for damon_start() failure. As a result, when damon_start() fails, it leaks the memory for DAMON context. Free the context in case of the failure to fix the issues.

Note that the issue can reliably be reproduced because the module calls damon_start() in the exclusive mode. For example,

$ sudo damo start
$ echo $$ | sudo tee /sys/module/damon_sample_wsse/parameters/target_pid
$ echo Y | sudo tee /sys/module/damon_sample_wsse/parameters/enabled
$ sudo cat /proc/allocinfo | grep damon_new_ctx

Because the first command is running another DAMON instance, the third command fails the damon_start() call because the new DAMON instance cannot exclusively run. And without this fix, by repeating the third and the fourth commands above, we can show the memory consumption is only increasing due to the leaks. It requires the sudo permission though.

The issue was discovered [1] by Sashiko.

Show details on source website

JSON

To clipboard

{
  "affected": [],
  "aliases": [
    "CVE-2026-90005"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-09-16T11:17:13Z",
    "severity": null
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nsamples/damon/wsse: handle damon_start() failure\n\nPatch series \"samples/damon: handle damon_{start,stop}() failures\".\n\nAll DAMON sample modules are not correctly handling failures from\ndamon_start().  Among those, mtier also has an additional problem for\nhandling of damon_stop() failures.  wsse and prcl also have a problem in\ntheir damon_call() failure handling.  As a result, memory leaks, next\nDAMON operation disruptions, and use-after-free can happen.  Fix those.\n\nNote that only the damon_start() failure caused issues can reliably be\nreproduced.  Reproducing those issues require the admin permission,\nthough.\n\n\nThis patch (of 6):\n\ndamon_sample_wsse_start() callers assume it will clean up resources when\nit fails.  And the function does the cleanup for context buildup failures.\nHowever, it is not doing the cleanup for damon_start() failure.  As a\nresult, when damon_start() fails, it leaks the memory for DAMON context. \nFree the context in case of the failure to fix the issues.\n\nNote that the issue can reliably be reproduced because the module calls\ndamon_start() in the exclusive mode.  For example,\n\n    $ sudo damo start\n    $ echo $$ | sudo tee /sys/module/damon_sample_wsse/parameters/target_pid\n    $ echo Y | sudo tee /sys/module/damon_sample_wsse/parameters/enabled\n    $ sudo cat /proc/allocinfo | grep damon_new_ctx\n\nBecause the first command is running another DAMON instance, the third\ncommand fails the damon_start() call because the new DAMON instance cannot\nexclusively run.  And without this fix, by repeating the third and the\nfourth commands above, we can show the memory consumption is only\nincreasing due to the leaks.  It requires the sudo permission though.\n\nThe issue was discovered [1] by Sashiko.",
  "id": "GHSA-rjc9-q3q5-8f95",
  "modified": "2026-09-16T12:30:45Z",
  "published": "2026-09-16T12:30:45Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-90005"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/6179c7f47876d576dfe30efa8fbf1b0b1fdd13c0"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/e4742be45ea45bf554399ce89a09f71e525d7981"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/e60774d6335b89fac0be8b17a041fcffc508d281"
    }
  ],
  "schema_version": "1.4.0",
  "severity": []
}

CVE-2026-90005 (GCVE-0-2026-90005)

Vulnerability from cvelistv5 – Published: 2026-09-16 10:33 – Updated: 2026-10-19 08:56

Title

samples/damon/wsse: handle damon_start() failure

Summary

In the Linux kernel, the following vulnerability has been resolved: samples/damon/wsse: handle damon_start() failure Patch series "samples/damon: handle damon_{start,stop}() failures". All DAMON sample modules are not correctly handling failures from damon_start(). Among those, mtier also has an additional problem for handling of damon_stop() failures. wsse and prcl also have a problem in their damon_call() failure handling. As a result, memory leaks, next DAMON operation disruptions, and use-after-free can happen. Fix those. Note that only the damon_start() failure caused issues can reliably be reproduced. Reproducing those issues require the admin permission, though. This patch (of 6): damon_sample_wsse_start() callers assume it will clean up resources when it fails. And the function does the cleanup for context buildup failures. However, it is not doing the cleanup for damon_start() failure. As a result, when damon_start() fails, it leaks the memory for DAMON context. Free the context in case of the failure to fix the issues. Note that the issue can reliably be reproduced because the module calls damon_start() in the exclusive mode. For example, $ sudo damo start $ echo $$ | sudo tee /sys/module/damon_sample_wsse/parameters/target_pid $ echo Y | sudo tee /sys/module/damon_sample_wsse/parameters/enabled $ sudo cat /proc/allocinfo | grep damon_new_ctx Because the first command is running another DAMON instance, the third command fails the damon_start() call because the new DAMON instance cannot exclusively run. And without this fix, by repeating the third and the fourth commands above, we can show the memory consumption is only increasing due to the leaks. It requires the sudo permission though. The issue was discovered [1] by Sashiko.

Severity

No CVSS data available.

Assigner

Linux CNA under the mitre root

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

References

3 references

URL	Tags
https://git.kernel.org/stable/c/6179c7f47876d576d…
https://git.kernel.org/stable/c/e60774d6335b89fac…
https://git.kernel.org/stable/c/e4742be45ea45bf55…

Impacted products

2 products

Vendor	Product	Version
Linux	Linux	Affected: b757c6cfc696d43501632861f731412b14a7be86 , < 6179c7f47876d576dfe30efa8fbf1b0b1fdd13c0 (git) Affected: b757c6cfc696d43501632861f731412b14a7be86 , < e60774d6335b89fac0be8b17a041fcffc508d281 (git) Affected: b757c6cfc696d43501632861f731412b14a7be86 , < e4742be45ea45bf554399ce89a09f71e525d7981 (git)
Linux	Linux	Affected: 6.14 Unaffected: 0 , < 6.14 (semver) Unaffected: 6.18.51 , ≤ 6.18.* (semver) Unaffected: 7.2.5 , ≤ 7.2.* (semver) Unaffected: 7.3 , ≤ * (original_commit_for_fix)

Show details on NVD website

JSON

To clipboard

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "samples/damon/wsse.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "6179c7f47876d576dfe30efa8fbf1b0b1fdd13c0",
              "status": "affected",
              "version": "b757c6cfc696d43501632861f731412b14a7be86",
              "versionType": "git"
            },
            {
              "lessThan": "e60774d6335b89fac0be8b17a041fcffc508d281",
              "status": "affected",
              "version": "b757c6cfc696d43501632861f731412b14a7be86",
              "versionType": "git"
            },
            {
              "lessThan": "e4742be45ea45bf554399ce89a09f71e525d7981",
              "status": "affected",
              "version": "b757c6cfc696d43501632861f731412b14a7be86",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "samples/damon/wsse.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "6.14"
            },
            {
              "lessThan": "6.14",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.18.*",
              "status": "unaffected",
              "version": "6.18.51",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "7.2.*",
              "status": "unaffected",
              "version": "7.2.5",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "7.3",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.18.51",
                  "versionStartIncluding": "6.14",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.2.5",
                  "versionStartIncluding": "6.14",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.3",
                  "versionStartIncluding": "6.14",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nsamples/damon/wsse: handle damon_start() failure\n\nPatch series \"samples/damon: handle damon_{start,stop}() failures\".\n\nAll DAMON sample modules are not correctly handling failures from\ndamon_start().  Among those, mtier also has an additional problem for\nhandling of damon_stop() failures.  wsse and prcl also have a problem in\ntheir damon_call() failure handling.  As a result, memory leaks, next\nDAMON operation disruptions, and use-after-free can happen.  Fix those.\n\nNote that only the damon_start() failure caused issues can reliably be\nreproduced.  Reproducing those issues require the admin permission,\nthough.\n\n\nThis patch (of 6):\n\ndamon_sample_wsse_start() callers assume it will clean up resources when\nit fails.  And the function does the cleanup for context buildup failures.\nHowever, it is not doing the cleanup for damon_start() failure.  As a\nresult, when damon_start() fails, it leaks the memory for DAMON context. \nFree the context in case of the failure to fix the issues.\n\nNote that the issue can reliably be reproduced because the module calls\ndamon_start() in the exclusive mode.  For example,\n\n    $ sudo damo start\n    $ echo $$ | sudo tee /sys/module/damon_sample_wsse/parameters/target_pid\n    $ echo Y | sudo tee /sys/module/damon_sample_wsse/parameters/enabled\n    $ sudo cat /proc/allocinfo | grep damon_new_ctx\n\nBecause the first command is running another DAMON instance, the third\ncommand fails the damon_start() call because the new DAMON instance cannot\nexclusively run.  And without this fix, by repeating the third and the\nfourth commands above, we can show the memory consumption is only\nincreasing due to the leaks.  It requires the sudo permission though.\n\nThe issue was discovered [1] by Sashiko."
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-10-19T08:56:19.196Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/6179c7f47876d576dfe30efa8fbf1b0b1fdd13c0"
        },
        {
          "url": "https://git.kernel.org/stable/c/e60774d6335b89fac0be8b17a041fcffc508d281"
        },
        {
          "url": "https://git.kernel.org/stable/c/e4742be45ea45bf554399ce89a09f71e525d7981"
        }
      ],
      "title": "samples/damon/wsse: handle damon_start() failure",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2026-90005",
    "datePublished": "2026-09-16T10:33:14.753Z",
    "dateReserved": "2026-09-11T19:38:34.780Z",
    "dateUpdated": "2026-10-19T08:56:19.196Z",
    "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

How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

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