CVE-2026-68478: memstick: ms_block: reject a card that reports too many blocks
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.22% (FIRST EPSS).
- Fixed version: Linux Linux 39151f0708c84221e94cdd6aa070aba5d7cb1c01, 47f0c7d856c67c9935546d2644f18c0d0131b449, 718178f524b98bc920d74bc771aed823c8b81425.
Low priority for now. Upgrade to Linux Linux 39151f0708c84221e94cdd6aa070aba5d7cb1c01, 47f0c7d856c67c9935546d2644f18c0d0131b449, 718178f524b98bc920d74bc771aed823c8b81425 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Aug 15, 2026
- Updated
- Aug 17, 2026
- EPSS
- 0.2% · 12th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 3.12affected
- 0ab30494bc4f3bc1ea4659b7c5d97c5218554a63 and later · before a4b9961efe8640f50800811b4a2b2046b3dc2cccaffected · git
- 0ab30494bc4f3bc1ea4659b7c5d97c5218554a63 and later · before 8937b11f1c3896e066c3fb07387ba17bc8c50b8aaffected · git
- 0ab30494bc4f3bc1ea4659b7c5d97c5218554a63 and later · before f1c675ecf6e5ad02722f0019f729d8bb588d502eaffected · git
- 0ab30494bc4f3bc1ea4659b7c5d97c5218554a63 and later · before d5db3439ee8d1c165a09a47e984c4ba508c130dfaffected · git
- 0ab30494bc4f3bc1ea4659b7c5d97c5218554a63 and later · before b86666ac4009a252501cc17242582a7ec9ed976eaffected · git
- 0ab30494bc4f3bc1ea4659b7c5d97c5218554a63 and later · before 39151f0708c84221e94cdd6aa070aba5d7cb1c01affected · git
- 0ab30494bc4f3bc1ea4659b7c5d97c5218554a63 and later · before 47f0c7d856c67c9935546d2644f18c0d0131b449affected · git
- 0ab30494bc4f3bc1ea4659b7c5d97c5218554a63 and later · before 718178f524b98bc920d74bc771aed823c8b81425affected · git
- before 3.12not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.180-1 | 6.1.180-1 |
| Debian:13 | linux | before 6.12.100-1 | 6.12.100-1 |
| Debian:14 | linux | before 7.1.5-1 | 7.1.5-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-68475Aug 15, 2026 · reset: sunxi: fix memory region leak on ioremap failure0Monitor
- ← EarlierCVE-2026-68476Aug 15, 2026 · ipvs: reload ip header after head reallocation39Monitor
- Later →CVE-2026-72004Aug 15, 2026 · wifi: mac80211: fix memory leak in ieee80211_register_hw()0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 39151f0708c84221e94cdd6aa070aba5d7cb1c01 | Vendor (CNA) |
| Linux Linux | 47f0c7d856c67c9935546d2644f18c0d0131b449 | Vendor (CNA) |
| Linux Linux | 718178f524b98bc920d74bc771aed823c8b81425 | Vendor (CNA) |
| Linux Linux | 8937b11f1c3896e066c3fb07387ba17bc8c50b8a | Vendor (CNA) |
| Linux Linux | a4b9961efe8640f50800811b4a2b2046b3dc2ccc | Vendor (CNA) |
| Linux Linux | b86666ac4009a252501cc17242582a7ec9ed976e | Vendor (CNA) |
| Linux Linux | d5db3439ee8d1c165a09a47e984c4ba508c130df | Vendor (CNA) |
| Linux Linux | f1c675ecf6e5ad02722f0019f729d8bb588d502e | Vendor (CNA) |
| debian:linux | 6.1.180-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/47f0c7d856c67c9935546d2644f18c0d0131b449
- git.kernel.org/stable/c/718178f524b98bc920d74bc771aed823c8b81425
- git.kernel.org/stable/c/8937b11f1c3896e066c3fb07387ba17bc8c50b8a
- git.kernel.org/stable/c/a4b9961efe8640f50800811b4a2b2046b3dc2ccc
- git.kernel.org/stable/c/b86666ac4009a252501cc17242582a7ec9ed976e
- git.kernel.org/stable/c/d5db3439ee8d1c165a09a47e984c4ba508c130df
- git.kernel.org/stable/c/f1c675ecf6e5ad02722f0019f729d8bb588d502e
Vendor advisories and official records. Exploit/PoC links are deliberately left out.