CVE-2026-46070

HIGHPre-NVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2026-05-27. a secondary CVSS source baseline 7.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
7.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.1Exploit: NoneExposed: 0

A fix is available — apply it.

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.

CVSS v3
7.1
EG Score
7.1(medium)
EPSS
2.6%
KEV
Not listed

Published

May 27, 2026

Last Modified

June 24, 2026

Advisory Details (8)

Auto-updated Jun 12, 2026
No patch confirmed yet.
generic

md/raid5: validate payload size before accessing journal metadata - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ef4851d8324fd978ca1ff9ec76a275438f887743
generic

md/raid5: validate payload size before accessing journal metadata - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c96c6f01d84b5c67db1bf1cc8591c0b7146826fc
generic

md/raid5: validate payload size before accessing journal metadata - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c3a1cf78bd1bbb51b2cc5189b4743056553c1e0e
generic

md/raid5: validate payload size before accessing journal metadata - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b0cc3ae97e893bf54bbce447f4e9fd2e0b88bff9
generic

md/raid5: validate payload size before accessing journal metadata - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/73ce72edd113374801045924d4417199963f73a3
generic

md/raid5: validate payload size before accessing journal metadata - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/406aa86394ead347c47428fb51b6359bdaa2257d
generic

md/raid5: validate payload size before accessing journal metadata - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/33698bd1b2db9764a29df7751533d33967ff5c98
generic

md/raid5: validate payload size before accessing journal metadata - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/28d3ff7109c66e99dc1b7cddacb5c760849620ef

Vendor Advisories for CVE-2026-46070(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Additional Vendor Advisories

(4)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Frequently asked(5)

What is CVE-2026-46070?
CVE-2026-46070 is a high vulnerability published on May 27, 2026. In the Linux kernel, the following vulnerability has been resolved: md/raid5: validate payload size before accessing journal metadata r5crecoveryanalyzemetablock() and r5lrecoveryverifydatachecksumformb() iterate over payloads in a journal metadata block using on-disk payload size fields without…
When was CVE-2026-46070 disclosed?
CVE-2026-46070 was first published in the National Vulnerability Database on May 27, 2026, with the most recent update on June 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46070 actively exploited?
CVE-2026-46070 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-46070?
CVE-2026-46070 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-46070?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46070, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-46070

Explore →

Is Your Infrastructure Affected by CVE-2026-46070?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs