CVE-2026-46070
Last modified
CVE-2026-46070 is a high-severity vulnerability rated 7.1/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: md/raid5: validate payload size before accessing journal metadata r5c_recovery_analyze_meta_block() and r5l_recovery_verify_data_checksum_for_mb() iterate over payloads in a journal metadata block using on-disk payload size fields without validating them against the remaining space in the metadata block. A corrupted journal contains payload sizes extending beyond the PAGE_SIZE boundary can cause out-of-bounds reads when accessing payload fields or computing offsets. Add bounds validation for each payload type to ensure the full payload fits within meta_size before processing.. EPSS estimates a 0.13% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: md/raid5: validate payload size before accessing journal metadata r5c_recovery_analyze_meta_block() and r5l_recovery_verify_data_checksum_for_mb() iterate over payloads in a journal metadata block using on-disk payload size fields without validating them against the remaining space in the metadata block. A corrupted journal contains payload sizes extending beyond the PAGE_SIZE boundary can cause out-of-bounds reads when accessing payload fields or computing offsets. Add bounds validation for each payload type to ensure the full payload fits within meta_size before processing.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | >= 4.10, < 5.10.258 |
| Linux | Linux Kernel | >= 5.11, < 5.15.209 |
| Linux | Linux Kernel | >= 5.16, < 6.1.175 |
| Linux | Linux Kernel | >= 6.2, < 6.6.140 |
| Linux | Linux Kernel | >= 6.7, < 6.12.86 |
| Linux | Linux Kernel | >= 6.13, < 6.18.27 |
| Linux | Linux Kernel | >= 6.19, < 7.0.4 |
References
Timeline
- Published
- Last Modified
- Status
- Undergoing Analysis
Frequently Asked Questions
What is CVE-2026-46070?
How severe is CVE-2026-46070?
How do I fix CVE-2026-46070?
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-46065In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-46066In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-46067In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2026-46068In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-46069In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-4607The ProfileGrid – User Profiles, Groups and Communities plug…4.3
- CVE-2026-46071In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-46072In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-46073In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-46074In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-46075In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-46076In the Linux kernel, the following vulnerability has been re…7.9
Are you affected by CVE-2026-46070?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST