CVE-2026-46070

HIGHPre-NVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2026-05-27. the CNA's CVSS baseline 7.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
7.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.1Exploit: None knownExposed: 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)
EG Risk
37(Track)
EG Risk 37/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity71% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

May 27, 2026

Last Modified

August 5, 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.

Patch Availability(30)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-27.27) @ resolute2026-08-25ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1008.8) @ resolute2026-08-25ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1014.14) @ resolute2026-08-25ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1013.13) @ resolute2026-08-25ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1064.72+fips1) @ noble2026-08-25ubuntu
ubuntulinux-tools-ibm-edge (5.15.0.1106.110~20.04.1) @ focal2026-08-25ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-08-25ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1063.71) @ noble2026-08-25ubuntu
ubuntulinux-tools-azure-fde-lts-24.04 (6.8.0-1062.69) @ noble2026-08-25ubuntu
ubuntulinux-tools-oracle-lts-22.04 (5.15.0.1109.105) @ jammy2026-08-25ubuntu
ubuntulinux-tools-aws-lts-24.04 (6.8.0-1061.64+1) @ noble2026-08-25ubuntu
ubuntulinux-tools-azure-fde-lts-22.04 (5.15.0.1117.126) @ jammy2026-08-25ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1059.62.1) @ noble2026-08-25ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1064.66~20.04.1) @ focal2026-08-25ubuntu
ubuntulinux-tools-oracle-lts-24.04 (6.8.0-1058.61) @ noble2026-08-25ubuntu
ubuntulinux-tools-oracle-edge (6.8.0-1058.61~22.04.1) @ jammy2026-08-25ubuntu
ubuntulinux-tools-realtime-hwe-22.04 (6.8.1-1056.57~22.04.2) @ jammy2026-08-25ubuntu
ubuntulinux-tools-nvidia-lowlatency-5.15 (5.15.0.1107.107) @ jammy2026-08-25ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1063.71+fips2) @ noble2026-08-25ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1064.64) @ jammy2026-08-25ubuntu
ubuntulinux-tools-azure-fde-6.8 (6.8.0-1062.69~22.04.1) @ jammy2026-08-25ubuntu
ubuntulinux-tools-aws-fips-6.8 (6.8.0-1061.64+fips1) @ noble2026-08-25ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1033.34) @ noble2026-08-25ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-136.136~22.04.1) @ jammy2026-08-25ubuntu
ubuntulinux-tools-oracle-edge (5.15.0.1109.115~20.04.1) @ focal2026-08-25ubuntu
ubuntulinux-tools-intel-iotg-edge (5.15.0.1107.113~20.04.1) @ focal2026-08-25ubuntu
ubuntulinux-tools-gcp-edge (5.15.0.1112.122~20.04.1) @ focal2026-08-25ubuntu
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-28.28~24.04.1) @ noble2026-08-25ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.15.0-1075 (5.15.0-1075.79) @ jammy2026-08-25ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2050.52) @ noble2026-08-25ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (54 versions)5.10.259-1—
linux-6.16.1.106-3~deb11u1 ... 6.1.174-1~deb11u1 (20 versions)6.1.176-1~deb11u1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)6.1.176-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.86-1~bpo12+1 (19 versions)6.12.86-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.4-1~bpo13+1 (131 versions)7.0.4-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(24)

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.

Data Freshness Timeline

(refreshed 4× in last 7d / 85× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 277 total refreshes for this CVE.

  1. 2026-09-04 05:06 UTCEPSS rescore
  2. 2026-09-02 14:12 UTCEPSS rescore
  3. 2026-09-01 13:54 UTCEPSS rescore
  4. 2026-08-30 01:22 UTCEPSS rescore
  5. 2026-08-28 21:41 UTCEPSS rescore
  6. 2026-08-27 14:25 UTCEPSS rescore
  7. 2026-08-26 14:46 UTCEPSS rescore
  8. 2026-08-25 13:49 UTCEPSS rescore
  9. 2026-08-25 05:21 UTCEG score recompute
  10. 2026-08-25 05:21 UTCVendor advisory
  11. 2026-08-25 05:21 UTCGHSA enrichment
  12. 2026-08-23 15:07 UTCEG score recompute
  13. 2026-08-23 15:07 UTCVendor advisory
  14. 2026-08-23 15:07 UTCGHSA enrichment
  15. 2026-08-21 23:49 UTCEPSS rescore
  16. 2026-08-21 20:38 UTCEG score recompute
  17. 2026-08-21 20:38 UTCVendor advisory
  18. 2026-08-21 20:38 UTCGHSA enrichment
  19. 2026-08-20 22:55 UTCEPSS rescore
  20. 2026-08-20 22:36 UTCVendor advisory
  21. 2026-08-20 22:36 UTCGHSA enrichment
  22. 2026-08-20 11:24 UTCEG score recompute
  23. 2026-08-20 11:24 UTCVendor advisory
  24. 2026-08-20 11:23 UTCGHSA enrichment
  25. 2026-08-19 17:04 UTCEPSS rescore
Show 75 more
  1. 2026-08-18 13:48 UTCEPSS rescore
  2. 2026-08-17 13:47 UTCEPSS rescore
  3. 2026-08-17 09:17 UTCVendor advisory
  4. 2026-08-17 09:17 UTCGHSA enrichment
  5. 2026-08-16 15:14 UTCEG score recompute
  6. 2026-08-16 15:14 UTCVendor advisory
  7. 2026-08-16 15:14 UTCGHSA enrichment
  8. 2026-08-16 14:56 UTCEPSS rescore
  9. 2026-08-16 02:50 UTCEG score recompute
  10. 2026-08-16 02:50 UTCVendor advisory
  11. 2026-08-16 02:50 UTCGHSA enrichment
  12. 2026-08-16 02:14 UTCEPSS rescore
  13. 2026-08-15 01:30 UTCEPSS rescore
  14. 2026-08-14 23:21 UTCVendor advisory
  15. 2026-08-14 23:21 UTCGHSA enrichment
  16. 2026-08-14 12:24 UTCVendor advisory
  17. 2026-08-14 12:24 UTCGHSA enrichment
  18. 2026-08-14 01:28 UTCEG score recompute
  19. 2026-08-14 01:28 UTCVendor advisory
  20. 2026-08-14 01:27 UTCGHSA enrichment
  21. 2026-08-13 22:00 UTCEPSS rescore
  22. 2026-08-13 09:23 UTCVendor advisory
  23. 2026-08-13 09:23 UTCGHSA enrichment
  24. 2026-08-12 22:27 UTCEG score recompute
  25. 2026-08-12 22:27 UTCVendor advisory
  26. 2026-08-12 22:27 UTCGHSA enrichment
  27. 2026-08-12 13:51 UTCEPSS rescore
  28. 2026-08-12 11:30 UTCVendor advisory
  29. 2026-08-12 11:30 UTCGHSA enrichment
  30. 2026-08-12 00:32 UTCEG score recompute
  31. 2026-08-12 00:32 UTCVendor advisory
  32. 2026-08-12 00:32 UTCGHSA enrichment
  33. 2026-08-11 13:35 UTCVendor advisory
  34. 2026-08-11 13:35 UTCGHSA enrichment
  35. 2026-08-11 00:13 UTCEG score recompute
  36. 2026-08-11 00:13 UTCVendor advisory
  37. 2026-08-11 00:13 UTCGHSA enrichment
  38. 2026-08-11 00:00 UTCEPSS rescore
  39. 2026-08-10 06:14 UTCVendor advisory
  40. 2026-08-10 06:14 UTCGHSA enrichment
  41. 2026-08-09 19:18 UTCVendor advisory
  42. 2026-08-09 19:18 UTCGHSA enrichment
  43. 2026-08-09 08:21 UTCVendor advisory
  44. 2026-08-09 08:21 UTCGHSA enrichment
  45. 2026-08-08 21:24 UTCEG score recompute
  46. 2026-08-08 21:24 UTCVendor advisory
  47. 2026-08-08 21:24 UTCGHSA enrichment
  48. 2026-08-08 16:37 UTCEPSS rescore
  49. 2026-08-08 09:17 UTCVendor advisory
  50. 2026-08-08 09:17 UTCGHSA enrichment
  51. 2026-08-07 22:20 UTCVendor advisory
  52. 2026-08-07 22:20 UTCGHSA enrichment
  53. 2026-08-07 11:23 UTCVendor advisory
  54. 2026-08-07 11:23 UTCGHSA enrichment
  55. 2026-08-07 00:27 UTCEG score recompute
  56. 2026-08-07 00:27 UTCVendor advisory
  57. 2026-08-07 00:27 UTCGHSA enrichment
  58. 2026-08-06 13:47 UTCEPSS rescore
  59. 2026-08-06 11:45 UTCVendor advisory
  60. 2026-08-06 11:45 UTCGHSA enrichment
  61. 2026-08-06 00:39 UTCEG score recompute
  62. 2026-08-06 00:39 UTCVendor advisory
  63. 2026-08-06 00:39 UTCGHSA enrichment
  64. 2026-08-05 19:17 UTCEPSS rescore
  65. 2026-08-05 13:42 UTCEG score recompute
  66. 2026-08-05 13:42 UTCVendor advisory
  67. 2026-08-05 13:42 UTCGHSA enrichment
  68. 2026-08-04 15:10 UTCEPSS rescore
  69. 2026-08-04 10:39 UTCEPSS rescore
  70. 2026-08-04 03:25 UTCVendor advisory
  71. 2026-08-04 03:25 UTCGHSA enrichment
  72. 2026-08-03 16:27 UTCEG score recompute
  73. 2026-08-03 16:27 UTCVendor advisory
  74. 2026-08-03 16:27 UTCGHSA enrichment
  75. 2026-08-03 10:36 UTCEPSS rescore

Related CVEs(same vendor + same CWE)

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 August 5, 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 0% probability of exploitation in the next 30 days, which ranks it in the top 97.4% of all scored CVEs.
What is the CVSS score of CVE-2026-46070?
CVE-2026-46070 has a CVSS v4.0 base score of 7.1 (CNA self-assessment; NVD's own analysis pending).
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

See which npm, PyPI, Go, and Maven packages are affected by 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