CVE-2026-68478
Vulnerability Scoring
Analysis In Progress
CVE-2026-68478 Vulnerability Analysis & Exploit Details
CVE-2026-68478
Attack Complexity Details
-
Attack Complexity:
Attack Complexity Analysis In Progress
-
Attack Vector:
Attack Vector Under Analysis
-
Privileges Required:
None
No authentication is required for exploitation.
-
Scope:
Impact is confined to the initially vulnerable component.
-
User Interaction:
None
No user interaction is necessary for exploitation.
CVE-2026-68478 Details
Status: Received on 15 Aug 2026, 06:20 UTC
Last updated: 🕕 17 Aug 2026, 06:17 UTC
Originally published on: 🕕 15 Aug 2026, 06:20 UTC
Time between publication and last update: 1 days
CVSS Release:
CVE-2026-68478 Vulnerability Summary
CVE-2026-68478: 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.
Assessing the Risk of CVE-2026-68478
Access Complexity Graph
The exploitability of CVE-2026-68478 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).
Exploitability Analysis for CVE-2026-68478
No exploitability data is available for CVE-2026-68478.
Understanding AC and PR
A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.
Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.
Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.
CVSS Score Breakdown Chart
Above is the CVSS Sub-score Breakdown for CVE-2026-68478, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.
CIA Impact Analysis
Below is the Impact Analysis for CVE-2026-68478, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.
-
Confidentiality:
None
CVE-2026-68478 does not compromise confidentiality.
-
Integrity:
None
CVE-2026-68478 does not impact data integrity.
-
Availability:
None
CVE-2026-68478 does not affect system availability.
CVE-2026-68478 References
External References
- https://git.kernel.org/stable/c/39151f0708c84221e94cdd6aa070aba5d7cb1c01
- https://git.kernel.org/stable/c/47f0c7d856c67c9935546d2644f18c0d0131b449
- https://git.kernel.org/stable/c/718178f524b98bc920d74bc771aed823c8b81425
- https://git.kernel.org/stable/c/8937b11f1c3896e066c3fb07387ba17bc8c50b8a
- https://git.kernel.org/stable/c/a4b9961efe8640f50800811b4a2b2046b3dc2ccc
- https://git.kernel.org/stable/c/b86666ac4009a252501cc17242582a7ec9ed976e
- https://git.kernel.org/stable/c/d5db3439ee8d1c165a09a47e984c4ba508c130df
- https://git.kernel.org/stable/c/f1c675ecf6e5ad02722f0019f729d8bb588d502e
CWE Common Weakness Enumeration
Unknown
Protect Your Infrastructure against CVE-2026-68478: Combat Critical CVE Threats
Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.
Other 5 Recently Published CVEs Vulnerabilities
- CVE-2026-85200 – The GEO my WP plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 4.5.5.3 via the gmw_posts_locator_aj...
- CVE-2026-85198 – The MPG – Multiple Page Generator, Bulk Landing Pages & Programmatic SEO plugin for WordPress is vulnerable to generic SQL Injection via URL Path i...
- CVE-2026-78175 – The Tutor LMS – eLearning and online course solution plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and includin...
- CVE-2026-78159 – The The Events Calendar plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 6.17.3 via the parse_arra...
- CVE-2026-78006 – The The Events Calendar plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 6.17.4 via the is_safe_wi...