CVE-2026-90006
Last modified
CVE-2026-90006 is a vulnerability of currently unknown severity. In the Linux kernel, the following vulnerability has been resolved: samples/damon/mtier: handle damon_stop() failure damon_sample_mtier_stop() assumes its damon_stop() call will always successfully stops the two DAMON contexts. Hence it deallocates the two DAMON contexts after the damon_stop() call.
Description
In the Linux kernel, the following vulnerability has been resolved: samples/damon/mtier: handle damon_stop() failure damon_sample_mtier_stop() assumes its damon_stop() call will always successfully stops the two DAMON contexts. Hence it deallocates the two DAMON contexts after the damon_stop() call. However, if a given context is already stopped, damon_stop() fails and returns an error while letting the DAMON contexts that have not yet stopped keep running. This kind of unexpected early DAMON context stops could happen due to memory allocation failures in kdamond_fn(). Because damon_sample_mtier_stop() just deallocates all DAMON contexts with damon_target and damon_region objects that are linked to the contexts, the execution of the unstopped DAMON context (kdamond) ends up using the memory that freed (use-after-free). Fix the issue by separating the damon_stop() to be invoked per context. Note that DAMON_SYSFS also allows multiple DAMON contexts execution. But, it calls damon_stop() for each context one by one. Hence this issue is only in mtier. For the long term, it would be better to refactor damon_stop() to always ensure stopping all contexts regardless of the failures in the middle. Make this fix in the current way, though, to keep it simple and easy to backport. I will do the refactoring later. The issue was discovered [1] by Sashiko.
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 82a08bde3cf7bbbe90de57baa181bebf676582c7, < 3c07c57b894116ae26f01b84c68e68b538ada7ed; >= 82a08bde3cf7bbbe90de57baa181bebf676582c7, < 215f9a7e4f1dcfc05ebcdc5c1ad0ea0dcb47bd09; >= 82a08bde3cf7bbbe90de57baa181bebf676582c7, < 9dc5b6d66fd51b103eff21ed0df3e292f489ebc0 |
| Linux | Linux | 6.16 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-90006?
How severe is CVE-2026-90006?
How do I fix CVE-2026-90006?
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-90000In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2026-90001In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-90002In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-90003In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-90004In the Linux kernel, the following vulnerability has been re…
- CVE-2026-90005In the Linux kernel, the following vulnerability has been re…
- CVE-2026-90007In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-90008In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-90009In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-90010In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-90011In the Linux kernel, the following vulnerability has been re…9.1
- CVE-2026-90012In the Linux kernel, the following vulnerability has been re…9.8
Are you affected by CVE-2026-90006?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
