CVE-2026-46183
published 2026-05-28CVE-2026-46183: In the Linux kernel, the following vulnerability has been resolved: mm/damon/sysfs-schemes: protect path kfree() with damon_sysfs_lock…
PriorityP341high7.8CVSS 3.1
AVLACLPRLUINSUCHIHAH
EPSS
0.12%
2.2th percentile
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.
Affected
5 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| linux | linux | — | — |
| linux | linux | >= c41e253a411eb73a5ac651c14f40c2ea2f274ebd < a34ca3e33da4b924c66bcca3729bf68ec5936910 | a34ca3e33da4b924c66bcca3729bf68ec5936910 |
| linux | linux | >= c41e253a411eb73a5ac651c14f40c2ea2f274ebd < cf3b71421ca00807328c6d9cd242f9de3b77a4bf | cf3b71421ca00807328c6d9cd242f9de3b77a4bf |
| linux | linux_kernel | — | — |
| linux | linux_kernel | >= 6.19 < 7.0.7 | 7.0.7 |
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Red Hat
kernel: mm/damon/sysfs-schemes: protect path kfree() with damon_sysfs_lock
vendor_redhat·2026-05-28
CVE-2026-46183 CWE-413 kernel: mm/damon/sysfs-schemes: protect path kfree() with damon_sysfs_lock
kernel: mm/damon/sysfs-schemes: protect path kfree() with damon_sysfs_lock
A flaw was found in the Linux kernel's DAMON (Data Access MONitor) sysfs (system file system) component. This vulnerability, a use-after-free, occurs because the `damon_sysfs_quot_goal->path` buffer can be deallocated during a write operation without proper locking. A local user could exploit this race condition by reading the 'path' file while it is being deallocated, potentially leading to information disclosure or a denial of service.
Package: kernel (Red Hat Enterprise Linux 10) - Not affected
Package: kernel (Red Hat Enterprise Linux 6) - Not affected
Package: kernel (Red Hat Enterprise Linux 7) - Not affected
Package: kernel-rt (Red Hat Enterprise Linux 7) - Not affected
Package: kernel (Red Hat Enterpri
GHSA
GHSA-82v4-79hw-3g4g: In the Linux kernel, the following vulnerability has been resolved:
mm/damon/sysfs-schemes: protect path kfree() with damon_sysfs_lock
damon_sysfs_q
ghsa_unreviewed·2026-05-28
CVE-2026-46183 GHSA-82v4-79hw-3g4g: In the Linux kernel, the following vulnerability has been resolved:
mm/damon/sysfs-schemes: protect path kfree() with damon_sysfs_lock
damon_sysfs_q
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. N
No detection rules found.
No public exploits indexed.
2026-05-28
Published