Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. · 14 days later

    Published

  3. · 5 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-46070, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.1CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
NVDNVD · Undergoing Analysis3.1High7.1CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
EPSS (exploitation in 30 days)
0.13% · top 97% of all CVEs (15 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.1.

Affected products

  • Linux · Linux

    • affected b4c625c67362b3940f619c1a836b4e8329106658 – < c96c6f01d84b5c67db1bf1cc8591c0b7146826fc
    • affected b4c625c67362b3940f619c1a836b4e8329106658 – < ef4851d8324fd978ca1ff9ec76a275438f887743
    • affected b4c625c67362b3940f619c1a836b4e8329106658 – < 28d3ff7109c66e99dc1b7cddacb5c760849620ef
    • affected b4c625c67362b3940f619c1a836b4e8329106658 – < 33698bd1b2db9764a29df7751533d33967ff5c98
    • affected b4c625c67362b3940f619c1a836b4e8329106658 – < c3a1cf78bd1bbb51b2cc5189b4743056553c1e0e
    • affected b4c625c67362b3940f619c1a836b4e8329106658 – < 73ce72edd113374801045924d4417199963f73a3
    • affected b4c625c67362b3940f619c1a836b4e8329106658 – < 406aa86394ead347c47428fb51b6359bdaa2257d
    • affected b4c625c67362b3940f619c1a836b4e8329106658 – < b0cc3ae97e893bf54bbce447f4e9fd2e0b88bff9
  • Linux · Linux

    • affected 4.10
    • unaffected < 4.10
    • unaffected 5.10.258 – ≤ 5.10.*
    • unaffected 5.15.209 – ≤ 5.15.*
    • unaffected 6.1.175 – ≤ 6.1.*
    • unaffected 6.6.140 – ≤ 6.6.*
    • unaffected 6.12.86 – ≤ 6.12.*
    • unaffected 6.18.27 – ≤ 6.18.*
    • unaffected 7.0.4 – ≤ 7.0.*
    • unaffected 7.1 – ≤ *

References

References9

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-46070 badge
[![CVE-2026-46070](https://cveledger.app/badge/CVE-2026-46070.svg)](https://cveledger.app/cve/CVE-2026-46070)

Record last updated .