CVE-2026-46183 (GCVE-0-2026-46183)
Vulnerability from cvelistv5
Published
2026-05-28 09:36
Modified
2026-06-14 18:00
Severity ?
Summary
In the Linux kernel, the following vulnerability has been resolved: mm/damon/sysfs-schemes: protect path kfree() with damon_sysfs_lock damon_sysfs_quot_goal->path can be read and written by users, via DAMON sysfs 'path' file. It can also be indirectly read, for the parameters {on,off}line committing to DAMON. The reads for parameters committing are protected by damon_sysfs_lock to avoid the sysfs files being destroyed while any of the parameters are being read. But the user-driven direct reads and writes are not protected by any lock, while the write is deallocating the path-pointing buffer. As a result, the readers could read the already freed buffer (user-after-free). Note that the user-reads don't race when the same open file is used by the writer, due to kernfs's open file locking. Nonetheless, doing the reads and writes with separate open files would be common. Fix it by protecting both the user-direct reads and writes with damon_sysfs_lock.
References
Impacted products
Vendor Product Version
Linux Linux Version: c41e253a411eb73a5ac651c14f40c2ea2f274ebd
Version: c41e253a411eb73a5ac651c14f40c2ea2f274ebd
 Create a notification for this product.
Show details on NVD website

To clipboard 

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "mm/damon/sysfs-schemes.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "a34ca3e33da4b924c66bcca3729bf68ec5936910",
              "status": "affected",
              "version": "c41e253a411eb73a5ac651c14f40c2ea2f274ebd",
              "versionType": "git"
            },
            {
              "lessThan": "cf3b71421ca00807328c6d9cd242f9de3b77a4bf",
              "status": "affected",
              "version": "c41e253a411eb73a5ac651c14f40c2ea2f274ebd",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "mm/damon/sysfs-schemes.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "6.19"
            },
            {
              "lessThan": "6.19",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "7.0.*",
              "status": "unaffected",
              "version": "7.0.7",
              "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": "7.0.7",
                  "versionStartIncluding": "6.19",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.1",
                  "versionStartIncluding": "6.19",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nmm/damon/sysfs-schemes: protect path kfree() with damon_sysfs_lock\n\ndamon_sysfs_quot_goal-\u003epath can be read and written by users, via DAMON\nsysfs \u0027path\u0027 file.  It can also be indirectly read, for the parameters\n{on,off}line committing to DAMON.  The reads for parameters committing are\nprotected by damon_sysfs_lock to avoid the sysfs files being destroyed\nwhile any of the parameters are being read.  But the user-driven direct\nreads and writes are not protected by any lock, while the write is\ndeallocating the path-pointing buffer.  As a result, the readers could\nread the already freed buffer (user-after-free).  Note that the user-reads\ndon\u0027t race when the same open file is used by the writer, due to kernfs\u0027s\nopen file locking.  Nonetheless, doing the reads and writes with separate\nopen files would be common.  Fix it by protecting both the user-direct\nreads and writes with damon_sysfs_lock."
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-06-14T18:00:54.954Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/a34ca3e33da4b924c66bcca3729bf68ec5936910"
        },
        {
          "url": "https://git.kernel.org/stable/c/cf3b71421ca00807328c6d9cd242f9de3b77a4bf"
        }
      ],
      "title": "mm/damon/sysfs-schemes: protect path kfree() with damon_sysfs_lock",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2026-46183",
    "datePublished": "2026-05-28T09:36:36.582Z",
    "dateReserved": "2026-05-13T15:03:33.103Z",
    "dateUpdated": "2026-06-14T18:00:54.954Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.