CVE-2026-46121
Last modified
CVE-2026-46121 is a high-severity vulnerability rated 7.8/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: mm/damon/sysfs-schemes: protect memcg_path kfree() with damon_sysfs_lock Patch series "mm/damon/sysfs-schemes: fix use-after-free for [memcg_]path". Reads of 'memcg_path' and 'path' files in DAMON sysfs interface could race with their writes, results in use-after-free. Fix those. This patch (of 2): damon_sysfs_scheme_filter->mmecg_path can be read and written by users, via DAMON sysfs memcg_path file. EPSS estimates a 0.13% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: mm/damon/sysfs-schemes: protect memcg_path kfree() with damon_sysfs_lock Patch series "mm/damon/sysfs-schemes: fix use-after-free for [memcg_]path". Reads of 'memcg_path' and 'path' files in DAMON sysfs interface could race with their writes, results in use-after-free. Fix those. This patch (of 2): damon_sysfs_scheme_filter->mmecg_path can be read and written by users, via DAMON sysfs memcg_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 memcg_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.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 6.6.96, < 6.6.140 | — |
| Linux | Linux Kernel | >= 6.12.36, < 6.12.88 | — |
| Linux | Linux Kernel | >= 6.15.5, < 6.16 | — |
| Linux | Linux Kernel | >= 6.16.1, < 6.18.30 | — |
| Linux | Linux Kernel | >= 6.19, < 7.0.7 | — |
| Linux | Linux Kernel | 6.16 | — |
| Linux | Linux Kernel | 7.1 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Undergoing Analysis
Frequently Asked Questions
What is CVE-2026-46121?
How severe is CVE-2026-46121?
How do I fix CVE-2026-46121?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-46116In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-46117In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-46118In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-46119In the Linux kernel, the following vulnerability has been re…9.1
- CVE-2026-4612A vulnerability has been found in itsourcecode Free Hotel Re…7.3
- CVE-2026-46120In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-46122In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-46123In the Linux kernel, the following vulnerability has been re…7.7
- CVE-2026-46124In the Linux kernel, the following vulnerability has been re…7.5
- CVE-2026-46125In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2026-46126In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-46127In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2026-46121?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
