{"dataType": "CVE_RECORD", "dataVersion": "5.2", "cveMetadata": {"cveId": "CVE-2026-46183", "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "state": "PUBLISHED", "assignerShortName": "Linux", "dateReserved": "2026-05-13T15:03:33.103Z", "datePublished": "2026-05-28T09:36:36.582Z", "dateUpdated": "2026-05-28T09:36:36.582Z"}, "containers": {"cna": {"providerMetadata": {"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "shortName": "Linux", "dateUpdated": "2026-05-28T09:36:36.582Z"}, "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->path can be read and written by users, via DAMON\nsysfs 'path' 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't race when the same open file is used by the writer, due to kernfs's\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."}], "affected": [{"product": "Linux", "vendor": "Linux", "defaultStatus": "unaffected", "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "programFiles": ["mm/damon/sysfs-schemes.c"], "versions": [{"version": "c41e253a411eb73a5ac651c14f40c2ea2f274ebd", "lessThan": "a34ca3e33da4b924c66bcca3729bf68ec5936910", "status": "affected", "versionType": "git"}, {"version": "c41e253a411eb73a5ac651c14f40c2ea2f274ebd", "lessThan": "cf3b71421ca00807328c6d9cd242f9de3b77a4bf", "status": "affected", "versionType": "git"}]}, {"product": "Linux", "vendor": "Linux", "defaultStatus": "affected", "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "programFiles": ["mm/damon/sysfs-schemes.c"], "versions": [{"version": "6.19", "status": "affected"}, {"version": "0", "lessThan": "6.19", "status": "unaffected", "versionType": "semver"}, {"version": "7.0.7", "lessThanOrEqual": "7.0.*", "status": "unaffected", "versionType": "semver"}, {"version": "7.1-rc2", "lessThanOrEqual": "*", "status": "unaffected", "versionType": "original_commit_for_fix"}]}], "cpeApplicability": [{"nodes": [{"operator": "OR", "negate": false, "cpeMatch": [{"vulnerable": true, "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionStartIncluding": "6.19", "versionEndExcluding": "7.0.7"}, {"vulnerable": true, "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionStartIncluding": "6.19", "versionEndExcluding": "7.1-rc2"}]}]}], "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"}}}}

{}

{"cveTags": [], "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->path can be read and written by users, via DAMON\nsysfs 'path' 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't race when the same open file is used by the writer, due to kernfs's\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."}], "id": "CVE-2026-46183", "lastModified": "2026-05-28T10:16:33.933", "metrics": {}, "published": "2026-05-28T10:16:33.933", "references": [{"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "url": "https://git.kernel.org/stable/c/a34ca3e33da4b924c66bcca3729bf68ec5936910"}, {"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "url": "https://git.kernel.org/stable/c/cf3b71421ca00807328c6d9cd242f9de3b77a4bf"}], "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "vulnStatus": "Received"}

{}

{}