CVE-2026-90004
Last modified
CVE-2026-90004 is a vulnerability of currently unknown severity. In the Linux kernel, the following vulnerability has been resolved: mm/damon/core: handle region split failure in apply_min_nr_regions() damon_apply_min_nr_regions() repeatedly split each region until its size becomes small enough to meet the user-defined low limit of the number of regions. The loop assumes the split operation (damon_split_region_at()) will always succeed and create the new region.
Description
In the Linux kernel, the following vulnerability has been resolved: mm/damon/core: handle region split failure in apply_min_nr_regions() damon_apply_min_nr_regions() repeatedly split each region until its size becomes small enough to meet the user-defined low limit of the number of regions. The loop assumes the split operation (damon_split_region_at()) will always succeed and create the new region. But the operation could silently fail for memory allocation failures, for example. If such failure happens and the region was the last region, the linked list-based next region fetching returns invalid pointer. As a result, invalid memory dereference and corruption could happen. Even if the corner case is handled, it imposes stress to the allocator by trying split regions for other targets. Fix the issue by breaking all the loops for any region split failure. This means there could be a min_nr_regions violation. It will only rarely happen since the allocation is arguably too small to fail. Even if it happens, it is only temporal. damon_apply_min_nr_regions() will be called again after the aggregation interval. The user impact of the issue should be minor, since the allocation is arguably too small to fail. But, it could still theoretically happen, and the consequence is very bad. This issue was discovered [1] by Sashiko.
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= b1029f29eb1d5fbf07fa8db9b5e7ab6d9813ad67, < 463ebd63e8ee3d73022a18915ea43320dad8aad7; >= b1029f29eb1d5fbf07fa8db9b5e7ab6d9813ad67, < c608748607620f331196ed0ba9fe4017892c1457 |
| Linux | Linux | 7.1 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-90004?
How severe is CVE-2026-90004?
How do I fix CVE-2026-90004?
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-89998In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-89999In the Linux kernel, the following vulnerability has been re…8.1
- 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-90005In the Linux kernel, the following vulnerability has been re…
- CVE-2026-90006In 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
Are you affected by CVE-2026-90004?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
