CVE-2026-90006 (GCVE-0-2026-90006)

Vulnerability from cvelistv5 – Published: 2026-09-16 10:33 – Updated: 2026-10-19 08:56
VLAI
Title
samples/damon/mtier: handle damon_stop() failure
Summary
In the Linux kernel, the following vulnerability has been resolved: samples/damon/mtier: handle damon_stop() failure damon_sample_mtier_stop() assumes its damon_stop() call will always successfully stops the two DAMON contexts. Hence it deallocates the two DAMON contexts after the damon_stop() call. However, if a given context is already stopped, damon_stop() fails and returns an error while letting the DAMON contexts that have not yet stopped keep running. This kind of unexpected early DAMON context stops could happen due to memory allocation failures in kdamond_fn(). Because damon_sample_mtier_stop() just deallocates all DAMON contexts with damon_target and damon_region objects that are linked to the contexts, the execution of the unstopped DAMON context (kdamond) ends up using the memory that freed (use-after-free). Fix the issue by separating the damon_stop() to be invoked per context. Note that DAMON_SYSFS also allows multiple DAMON contexts execution. But, it calls damon_stop() for each context one by one. Hence this issue is only in mtier. For the long term, it would be better to refactor damon_stop() to always ensure stopping all contexts regardless of the failures in the middle. Make this fix in the current way, though, to keep it simple and easy to backport. I will do the refactoring later. 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
Impacted products
Vendor Product Version CPE status
Linux Linux Affected: 82a08bde3cf7bbbe90de57baa181bebf676582c7 , < 3c07c57b894116ae26f01b84c68e68b538ada7ed (git)
Affected: 82a08bde3cf7bbbe90de57baa181bebf676582c7 , < 215f9a7e4f1dcfc05ebcdc5c1ad0ea0dcb47bd09 (git)
Affected: 82a08bde3cf7bbbe90de57baa181bebf676582c7 , < 9dc5b6d66fd51b103eff21ed0df3e292f489ebc0 (git)
guessed Create a notification for this product.
Linux Linux Affected: 6.16
Unaffected: 0 , < 6.16 (semver)
Unaffected: 6.18.51 , ≤ 6.18.* (semver)
Unaffected: 7.2.5 , ≤ 7.2.* (semver)
Unaffected: 7.3 , ≤ * (original_commit_for_fix)
guessed Create a notification for this product.
Show details on NVD website
To clipboard 

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "samples/damon/mtier.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "3c07c57b894116ae26f01b84c68e68b538ada7ed",
              "status": "affected",
              "version": "82a08bde3cf7bbbe90de57baa181bebf676582c7",
              "versionType": "git"
            },
            {
              "lessThan": "215f9a7e4f1dcfc05ebcdc5c1ad0ea0dcb47bd09",
              "status": "affected",
              "version": "82a08bde3cf7bbbe90de57baa181bebf676582c7",
              "versionType": "git"
            },
            {
              "lessThan": "9dc5b6d66fd51b103eff21ed0df3e292f489ebc0",
              "status": "affected",
              "version": "82a08bde3cf7bbbe90de57baa181bebf676582c7",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "samples/damon/mtier.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "6.16"
            },
            {
              "lessThan": "6.16",
              "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.16",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.2.5",
                  "versionStartIncluding": "6.16",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.3",
                  "versionStartIncluding": "6.16",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nsamples/damon/mtier: handle damon_stop() failure\n\ndamon_sample_mtier_stop() assumes its damon_stop() call will always\nsuccessfully stops the two DAMON contexts.  Hence it deallocates the two\nDAMON contexts after the damon_stop() call.  However, if a given context\nis already stopped, damon_stop() fails and returns an error while letting\nthe DAMON contexts that have not yet stopped keep running.  This kind of\nunexpected early DAMON context stops could happen due to memory allocation\nfailures in kdamond_fn().  Because damon_sample_mtier_stop() just\ndeallocates all DAMON contexts with damon_target and damon_region objects\nthat are linked to the contexts, the execution of the unstopped DAMON\ncontext (kdamond) ends up using the memory that freed (use-after-free). \nFix the issue by separating the damon_stop() to be invoked per context.\n\nNote that DAMON_SYSFS also allows multiple DAMON contexts execution.  But,\nit calls damon_stop() for each context one by one.  Hence this issue is\nonly in mtier.\n\nFor the long term, it would be better to refactor damon_stop() to always\nensure stopping all contexts regardless of the failures in the middle. \nMake this fix in the current way, though, to keep it simple and easy to\nbackport.  I will do the refactoring later.\n\nThe issue was discovered [1] by Sashiko."
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-10-19T08:56:20.156Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/3c07c57b894116ae26f01b84c68e68b538ada7ed"
        },
        {
          "url": "https://git.kernel.org/stable/c/215f9a7e4f1dcfc05ebcdc5c1ad0ea0dcb47bd09"
        },
        {
          "url": "https://git.kernel.org/stable/c/9dc5b6d66fd51b103eff21ed0df3e292f489ebc0"
        }
      ],
      "title": "samples/damon/mtier: handle damon_stop() failure",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2026-90006",
    "datePublished": "2026-09-16T10:33:15.423Z",
    "dateReserved": "2026-09-11T19:38:34.781Z",
    "dateUpdated": "2026-10-19T08:56:20.156Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2026-90006",
      "date": "2026-11-09",
      "epss": "0.00222",
      "percentile": "0.12884"
    },
    "microsoft_vex": {
      "current_release_date": "2026-10-21T18:41:54.000Z",
      "cve": "CVE-2026-90006",
      "id": "msrc_CVE-2026-90006",
      "initial_release_date": "2026-10-20T22:22:19.000Z",
      "product_status:under_investigation": "1",
      "source": "Microsoft CSAF VEX",
      "status": "final",
      "title": "samples/damon/mtier: handle damon_stop() failure",
      "url": "https://msrc.microsoft.com/csaf/vex/2026/msrc_cve-2026-90006.json",
      "version": "2"
    },
    "nvd": {
      "cve": {
        "affected": [
          {
            "affectedData": [
              {
                "defaultStatus": "unaffected",
                "product": "Linux",
                "programFiles": [
                  "samples/damon/mtier.c"
                ],
                "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
                "vendor": "Linux",
                "versions": [
                  {
                    "lessThan": "3c07c57b894116ae26f01b84c68e68b538ada7ed",
                    "status": "affected",
                    "version": "82a08bde3cf7bbbe90de57baa181bebf676582c7",
                    "versionType": "git"
                  },
                  {
                    "lessThan": "215f9a7e4f1dcfc05ebcdc5c1ad0ea0dcb47bd09",
                    "status": "affected",
                    "version": "82a08bde3cf7bbbe90de57baa181bebf676582c7",
                    "versionType": "git"
                  },
                  {
                    "lessThan": "9dc5b6d66fd51b103eff21ed0df3e292f489ebc0",
                    "status": "affected",
                    "version": "82a08bde3cf7bbbe90de57baa181bebf676582c7",
                    "versionType": "git"
                  }
                ]
              },
              {
                "defaultStatus": "affected",
                "product": "Linux",
                "programFiles": [
                  "samples/damon/mtier.c"
                ],
                "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
                "vendor": "Linux",
                "versions": [
                  {
                    "status": "affected",
                    "version": "6.16"
                  },
                  {
                    "lessThan": "6.16",
                    "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"
                  }
                ]
              }
            ],
            "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
          }
        ],
        "cveTags": [],
        "descriptions": [
          {
            "lang": "en",
            "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nsamples/damon/mtier: handle damon_stop() failure\n\ndamon_sample_mtier_stop() assumes its damon_stop() call will always\nsuccessfully stops the two DAMON contexts.  Hence it deallocates the two\nDAMON contexts after the damon_stop() call.  However, if a given context\nis already stopped, damon_stop() fails and returns an error while letting\nthe DAMON contexts that have not yet stopped keep running.  This kind of\nunexpected early DAMON context stops could happen due to memory allocation\nfailures in kdamond_fn().  Because damon_sample_mtier_stop() just\ndeallocates all DAMON contexts with damon_target and damon_region objects\nthat are linked to the contexts, the execution of the unstopped DAMON\ncontext (kdamond) ends up using the memory that freed (use-after-free). \nFix the issue by separating the damon_stop() to be invoked per context.\n\nNote that DAMON_SYSFS also allows multiple DAMON contexts execution.  But,\nit calls damon_stop() for each context one by one.  Hence this issue is\nonly in mtier.\n\nFor the long term, it would be better to refactor damon_stop() to always\nensure stopping all contexts regardless of the failures in the middle. \nMake this fix in the current way, though, to keep it simple and easy to\nbackport.  I will do the refactoring later.\n\nThe issue was discovered [1] by Sashiko."
          }
        ],
        "id": "CVE-2026-90006",
        "lastModified": "2026-10-19T09:18:48.317",
        "metrics": {},
        "published": "2026-09-16T11:17:13.213",
        "references": [
          {
            "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
            "url": "https://git.kernel.org/stable/c/215f9a7e4f1dcfc05ebcdc5c1ad0ea0dcb47bd09"
          },
          {
            "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
            "url": "https://git.kernel.org/stable/c/3c07c57b894116ae26f01b84c68e68b538ada7ed"
          },
          {
            "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
            "url": "https://git.kernel.org/stable/c/9dc5b6d66fd51b103eff21ed0df3e292f489ebc0"
          }
        ],
        "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "vulnStatus": "Received"
      }
    },
    "redhat_vex": {
      "aggregate_severity": "Moderate",
      "current_release_date": "2026-11-07T11:27:11+00:00",
      "cve": "CVE-2026-90006",
      "id": "CVE-2026-90006",
      "initial_release_date": "2026-09-16T00:00:00+00:00",
      "product_status:known_not_affected": "203",
      "source": "Red Hat CSAF VEX",
      "status": "final",
      "title": "kernel: samples/damon/mtier: handle damon_stop() failure",
      "url": "https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-90006.json",
      "version": "3"
    }
  }
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

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

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.

Loading timeline…




    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.