CVE-2026-46025 (GCVE-0-2026-46025)

Vulnerability from cvelistv5 – Published: 2026-05-27 12:56 – Updated: 2026-06-14 17:48
VLAI
Title
mm/damon/core: fix damon_call() vs kdamond_fn() exit race
Summary
In the Linux kernel, the following vulnerability has been resolved: mm/damon/core: fix damon_call() vs kdamond_fn() exit race Patch series "mm/damon/core: fix damon_call()/damos_walk() vs kdmond exit race". damon_call() and damos_walk() can leak memory and/or deadlock when they race with kdamond terminations. Fix those. This patch (of 2); When kdamond_fn() main loop is finished, the function cancels all remaining damon_call() requests and unset the damon_ctx->kdamond so that API callers and API functions themselves can know the context is terminated. damon_call() adds the caller's request to the queue first. After that, it shows if the kdamond of the damon_ctx is still running (damon_ctx->kdamond is set). Only if the kdamond is running, damon_call() starts waiting for the kdamond's handling of the newly added request. The damon_call() requests registration and damon_ctx->kdamond unset are protected by different mutexes, though. Hence, damon_call() could race with damon_ctx->kdamond unset, and result in deadlocks. For example, let's suppose kdamond successfully finished the damon_call() requests cancelling. Right after that, damon_call() is called for the context. It registers the new request, and shows the context is still running, because damon_ctx->kdamond unset is not yet done. Hence the damon_call() caller starts waiting for the handling of the request. However, the kdamond is already on the termination steps, so it never handles the new request. As a result, the damon_call() caller threads infinitely waits. Fix this by introducing another damon_ctx field, namely call_controls_obsolete. It is protected by the damon_ctx->call_controls_lock, which protects damon_call() requests registration. Initialize (unset) it in kdamond_fn() before letting damon_start() returns and set it just before the cancelling of remaining damon_call() requests is executed. damon_call() reads the obsolete field under the lock and avoids adding a new request. After this change, only requests that are guaranteed to be handled or cancelled are registered. Hence the after-registration DAMON context termination check is no longer needed. Remove it together. Note that the deadlock will not happen when damon_call() is called for repeat mode request. In tis case, damon_call() returns instead of waiting for the handling when the request registration succeeds and it shows the kdamond is running. However, if the request also has dealloc_on_cancel, the request memory would be leaked. The issue is found by sashiko [1].
Impacted products
Vendor Product Version CPE status
Linux Linux Affected: 42b7491af14cbba2393329ce43d508a957bd94fa , < 2691332ad88b57179c38653e2cd613d5820a52cf (git)
Affected: 42b7491af14cbba2393329ce43d508a957bd94fa , < e6a053a6f4b5048746c49432a5cc5b79fe4695fe (git)
Affected: 42b7491af14cbba2393329ce43d508a957bd94fa , < 55da81663b9642dd046b26dd6f1baddbcf337c1e (git)
guessed Create a notification for this product.
Linux Linux Affected: 6.14
Unaffected: 0 , < 6.14 (semver)
Unaffected: 6.18.27 , ≤ 6.18.* (semver)
Unaffected: 7.0.4 , ≤ 7.0.* (semver)
Unaffected: 7.1 , ≤ * (original_commit_for_fix)
guessed Create a notification for this product.
Show details on NVD website

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "include/linux/damon.h",
            "mm/damon/core.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "2691332ad88b57179c38653e2cd613d5820a52cf",
              "status": "affected",
              "version": "42b7491af14cbba2393329ce43d508a957bd94fa",
              "versionType": "git"
            },
            {
              "lessThan": "e6a053a6f4b5048746c49432a5cc5b79fe4695fe",
              "status": "affected",
              "version": "42b7491af14cbba2393329ce43d508a957bd94fa",
              "versionType": "git"
            },
            {
              "lessThan": "55da81663b9642dd046b26dd6f1baddbcf337c1e",
              "status": "affected",
              "version": "42b7491af14cbba2393329ce43d508a957bd94fa",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "include/linux/damon.h",
            "mm/damon/core.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.27",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "7.0.*",
              "status": "unaffected",
              "version": "7.0.4",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "7.1",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.18.27",
                  "versionStartIncluding": "6.14",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.0.4",
                  "versionStartIncluding": "6.14",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.1",
                  "versionStartIncluding": "6.14",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nmm/damon/core: fix damon_call() vs kdamond_fn() exit race\n\nPatch series \"mm/damon/core: fix damon_call()/damos_walk() vs kdmond exit\nrace\".\n\ndamon_call() and damos_walk() can leak memory and/or deadlock when they\nrace with kdamond terminations.  Fix those.\n\n\nThis patch (of 2);\n\nWhen kdamond_fn() main loop is finished, the function cancels all\nremaining damon_call() requests and unset the damon_ctx-\u003ekdamond so that\nAPI callers and API functions themselves can know the context is\nterminated.  damon_call() adds the caller\u0027s request to the queue first. \nAfter that, it shows if the kdamond of the damon_ctx is still running\n(damon_ctx-\u003ekdamond is set).  Only if the kdamond is running, damon_call()\nstarts waiting for the kdamond\u0027s handling of the newly added request.\n\nThe damon_call() requests registration and damon_ctx-\u003ekdamond unset are\nprotected by different mutexes, though.  Hence, damon_call() could race\nwith damon_ctx-\u003ekdamond unset, and result in deadlocks.\n\nFor example, let\u0027s suppose kdamond successfully finished the damon_call()\nrequests cancelling.  Right after that, damon_call() is called for the\ncontext.  It registers the new request, and shows the context is still\nrunning, because damon_ctx-\u003ekdamond unset is not yet done.  Hence the\ndamon_call() caller starts waiting for the handling of the request. \nHowever, the kdamond is already on the termination steps, so it never\nhandles the new request.  As a result, the damon_call() caller threads\ninfinitely waits.\n\nFix this by introducing another damon_ctx field, namely\ncall_controls_obsolete.  It is protected by the\ndamon_ctx-\u003ecall_controls_lock, which protects damon_call() requests\nregistration.  Initialize (unset) it in kdamond_fn() before letting\ndamon_start() returns and set it just before the cancelling of remaining\ndamon_call() requests is executed.  damon_call() reads the obsolete field\nunder the lock and avoids adding a new request.\n\nAfter this change, only requests that are guaranteed to be handled or\ncancelled are registered.  Hence the after-registration DAMON context\ntermination check is no longer needed.  Remove it together.\n\nNote that the deadlock will not happen when damon_call() is called for\nrepeat mode request.  In tis case, damon_call() returns instead of waiting\nfor the handling when the request registration succeeds and it shows the\nkdamond is running.  However, if the request also has dealloc_on_cancel,\nthe request memory would be leaked.\n\nThe issue is found by sashiko [1]."
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-06-14T17:48:48.849Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/2691332ad88b57179c38653e2cd613d5820a52cf"
        },
        {
          "url": "https://git.kernel.org/stable/c/e6a053a6f4b5048746c49432a5cc5b79fe4695fe"
        },
        {
          "url": "https://git.kernel.org/stable/c/55da81663b9642dd046b26dd6f1baddbcf337c1e"
        }
      ],
      "title": "mm/damon/core: fix damon_call() vs kdamond_fn() exit race",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2026-46025",
    "datePublished": "2026-05-27T12:56:31.784Z",
    "dateReserved": "2026-05-13T15:03:33.093Z",
    "dateUpdated": "2026-06-14T17:48:48.849Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2026-46025",
      "date": "2026-10-01",
      "epss": "0.00109",
      "percentile": "0.0114"
    },
    "nvd": {
      "cve": {
        "affected": [
          {
            "affectedData": [
              {
                "defaultStatus": "unaffected",
                "product": "Linux",
                "programFiles": [
                  "include/linux/damon.h",
                  "mm/damon/core.c"
                ],
                "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
                "vendor": "Linux",
                "versions": [
                  {
                    "lessThan": "2691332ad88b57179c38653e2cd613d5820a52cf",
                    "status": "affected",
                    "version": "42b7491af14cbba2393329ce43d508a957bd94fa",
                    "versionType": "git"
                  },
                  {
                    "lessThan": "e6a053a6f4b5048746c49432a5cc5b79fe4695fe",
                    "status": "affected",
                    "version": "42b7491af14cbba2393329ce43d508a957bd94fa",
                    "versionType": "git"
                  },
                  {
                    "lessThan": "55da81663b9642dd046b26dd6f1baddbcf337c1e",
                    "status": "affected",
                    "version": "42b7491af14cbba2393329ce43d508a957bd94fa",
                    "versionType": "git"
                  }
                ]
              },
              {
                "defaultStatus": "affected",
                "product": "Linux",
                "programFiles": [
                  "include/linux/damon.h",
                  "mm/damon/core.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.27",
                    "versionType": "semver"
                  },
                  {
                    "lessThanOrEqual": "7.0.*",
                    "status": "unaffected",
                    "version": "7.0.4",
                    "versionType": "semver"
                  },
                  {
                    "lessThanOrEqual": "*",
                    "status": "unaffected",
                    "version": "7.1",
                    "versionType": "original_commit_for_fix"
                  }
                ]
              }
            ],
            "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
          }
        ],
        "configurations": [
          {
            "nodes": [
              {
                "cpeMatch": [
                  {
                    "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                    "matchCriteriaId": "09521A36-58DA-4204-AE3E-627063BA9807",
                    "versionEndExcluding": "6.18.27",
                    "versionStartIncluding": "6.14",
                    "vulnerable": true
                  },
                  {
                    "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                    "matchCriteriaId": "CDB78D6D-22C3-4154-B0D0-94AF1CE5C2E3",
                    "versionEndExcluding": "7.0.4",
                    "versionStartIncluding": "6.19",
                    "vulnerable": true
                  }
                ],
                "negate": false,
                "operator": "OR"
              }
            ]
          }
        ],
        "cveTags": [],
        "descriptions": [
          {
            "lang": "en",
            "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nmm/damon/core: fix damon_call() vs kdamond_fn() exit race\n\nPatch series \"mm/damon/core: fix damon_call()/damos_walk() vs kdmond exit\nrace\".\n\ndamon_call() and damos_walk() can leak memory and/or deadlock when they\nrace with kdamond terminations.  Fix those.\n\n\nThis patch (of 2);\n\nWhen kdamond_fn() main loop is finished, the function cancels all\nremaining damon_call() requests and unset the damon_ctx-\u003ekdamond so that\nAPI callers and API functions themselves can know the context is\nterminated.  damon_call() adds the caller\u0027s request to the queue first. \nAfter that, it shows if the kdamond of the damon_ctx is still running\n(damon_ctx-\u003ekdamond is set).  Only if the kdamond is running, damon_call()\nstarts waiting for the kdamond\u0027s handling of the newly added request.\n\nThe damon_call() requests registration and damon_ctx-\u003ekdamond unset are\nprotected by different mutexes, though.  Hence, damon_call() could race\nwith damon_ctx-\u003ekdamond unset, and result in deadlocks.\n\nFor example, let\u0027s suppose kdamond successfully finished the damon_call()\nrequests cancelling.  Right after that, damon_call() is called for the\ncontext.  It registers the new request, and shows the context is still\nrunning, because damon_ctx-\u003ekdamond unset is not yet done.  Hence the\ndamon_call() caller starts waiting for the handling of the request. \nHowever, the kdamond is already on the termination steps, so it never\nhandles the new request.  As a result, the damon_call() caller threads\ninfinitely waits.\n\nFix this by introducing another damon_ctx field, namely\ncall_controls_obsolete.  It is protected by the\ndamon_ctx-\u003ecall_controls_lock, which protects damon_call() requests\nregistration.  Initialize (unset) it in kdamond_fn() before letting\ndamon_start() returns and set it just before the cancelling of remaining\ndamon_call() requests is executed.  damon_call() reads the obsolete field\nunder the lock and avoids adding a new request.\n\nAfter this change, only requests that are guaranteed to be handled or\ncancelled are registered.  Hence the after-registration DAMON context\ntermination check is no longer needed.  Remove it together.\n\nNote that the deadlock will not happen when damon_call() is called for\nrepeat mode request.  In tis case, damon_call() returns instead of waiting\nfor the handling when the request registration succeeds and it shows the\nkdamond is running.  However, if the request also has dealloc_on_cancel,\nthe request memory would be leaked.\n\nThe issue is found by sashiko [1]."
          }
        ],
        "id": "CVE-2026-46025",
        "lastModified": "2026-06-17T10:52:55.270",
        "metrics": {
          "cvssMetricV31": [
            {
              "cvssData": {
                "attackComplexity": "HIGH",
                "attackVector": "LOCAL",
                "availabilityImpact": "HIGH",
                "baseScore": 4.7,
                "baseSeverity": "MEDIUM",
                "confidentialityImpact": "NONE",
                "integrityImpact": "NONE",
                "privilegesRequired": "LOW",
                "scope": "UNCHANGED",
                "userInteraction": "NONE",
                "vectorString": "CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H",
                "version": "3.1"
              },
              "exploitabilityScore": 1.0,
              "impactScore": 3.6,
              "source": "nvd@nist.gov",
              "type": "Primary"
            }
          ]
        },
        "published": "2026-05-27T14:17:21.013",
        "references": [
          {
            "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
            "tags": [
              "Patch"
            ],
            "url": "https://git.kernel.org/stable/c/2691332ad88b57179c38653e2cd613d5820a52cf"
          },
          {
            "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
            "tags": [
              "Patch"
            ],
            "url": "https://git.kernel.org/stable/c/55da81663b9642dd046b26dd6f1baddbcf337c1e"
          },
          {
            "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
            "tags": [
              "Patch"
            ],
            "url": "https://git.kernel.org/stable/c/e6a053a6f4b5048746c49432a5cc5b79fe4695fe"
          }
        ],
        "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "vulnStatus": "Analyzed",
        "weaknesses": [
          {
            "description": [
              {
                "lang": "en",
                "value": "CWE-362"
              }
            ],
            "source": "nvd@nist.gov",
            "type": "Primary"
          }
        ]
      }
    },
    "redhat_vex": {
      "aggregate_severity": "None",
      "current_release_date": "2026-06-28T06:45:53+00:00",
      "cve": "CVE-2026-46025",
      "id": "CVE-2026-46025",
      "initial_release_date": "2026-05-27T00:00:00+00:00",
      "product_status:known_not_affected": "274",
      "source": "Red Hat CSAF VEX",
      "status": "final",
      "title": "kernel: mm/damon/core: fix damon_call() vs kdamond_fn() exit race",
      "url": "https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-46025.json",
      "version": "3"
    },
    "suse_vex": {
      "aggregate_severity": "moderate",
      "current_release_date": "2026-08-27T16:57:10Z",
      "cve": "CVE-2026-46025",
      "id": "CVE-2026-46025",
      "initial_release_date": "2026-05-28T03:54:10Z",
      "product_status:known_not_affected": "299",
      "product_status:recommended": "4",
      "source": "SUSE CSAF VEX",
      "status": "interim",
      "title": "SUSE CVE CVE-2026-46025",
      "url": "https://ftp.suse.com/pub/projects/security/csaf-vex/cve-2026-46025.json",
      "version": "6"
    }
  }
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

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.

Loading…

Loading…

Loading…

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.


Loading…