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-68478memstick: ms_block: reject a card that reports too many blocks

Description

In the Linux kernel, the following vulnerability has been resolved: memstick: ms_block: reject a card that reports too many blocks msb_ftl_initialize() computes the zone count from the card block count with no bound: msb->zone_count = msb->block_count / MS_BLOCKS_IN_ZONE; ... for (i = 0; i < msb->zone_count; i++) msb->free_block_count[i] = MS_BLOCKS_IN_ZONE; msb->block_count is a card value. msb_read_boot_blocks() reads number_of_blocks from the card boot page and byte swaps it. free_block_count is a fixed int[MS_MAX_ZONES]. MS_MAX_ZONES is 16, so the valid indices are 0 to 15. The init loop above indexes it by zone_count. msb_mark_block_used() and msb_mark_block_unused() index it by pba / MS_BLOCKS_IN_ZONE, for pba up to block_count - 1. A card may report up to 65535 blocks. A block_count above 8192 (MS_MAX_ZONES * MS_BLOCKS_IN_ZONE) lets the pba index reach 16. That writes past free_block_count[] and corrupts struct msb_data. A larger count runs the init loop past the end too. A real Memory Stick has at most 16 zones. So it has at most 8192 blocks. msb_ftl_initialize() now rejects a card that reports more than MS_MAX_ZONES * MS_BLOCKS_IN_ZONE blocks.

Timeline

  1. ID reserved

    By Linux

  2. · 16 days later

    Published

  3. · 2 days 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

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.22% · top 87% of all CVEs (12 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 0ab30494bc4f3bc1ea4659b7c5d97c5218554a63 – < a4b9961efe8640f50800811b4a2b2046b3dc2ccc
    • affected 0ab30494bc4f3bc1ea4659b7c5d97c5218554a63 – < 8937b11f1c3896e066c3fb07387ba17bc8c50b8a
    • affected 0ab30494bc4f3bc1ea4659b7c5d97c5218554a63 – < f1c675ecf6e5ad02722f0019f729d8bb588d502e
    • affected 0ab30494bc4f3bc1ea4659b7c5d97c5218554a63 – < d5db3439ee8d1c165a09a47e984c4ba508c130df
    • affected 0ab30494bc4f3bc1ea4659b7c5d97c5218554a63 – < b86666ac4009a252501cc17242582a7ec9ed976e
    • affected 0ab30494bc4f3bc1ea4659b7c5d97c5218554a63 – < 39151f0708c84221e94cdd6aa070aba5d7cb1c01
    • affected 0ab30494bc4f3bc1ea4659b7c5d97c5218554a63 – < 47f0c7d856c67c9935546d2644f18c0d0131b449
    • affected 0ab30494bc4f3bc1ea4659b7c5d97c5218554a63 – < 718178f524b98bc920d74bc771aed823c8b81425
  • Linux · Linux

    • affected 3.12
    • unaffected < 3.12
    • unaffected 5.10.261 – ≤ 5.10.*
    • unaffected 5.15.212 – ≤ 5.15.*
    • unaffected 6.1.178 – ≤ 6.1.*
    • unaffected 6.6.145 – ≤ 6.6.*
    • unaffected 6.12.97 – ≤ 6.12.*
    • unaffected 6.18.40 – ≤ 6.18.*
    • unaffected 7.1.5 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .