{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-68478 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-68478 is a memory corruption vulnerability in Linux, published on 15 Aug 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-68478 and fix it if it is affected.\n\nWhat it is: CVE-2026-68478 is a memory corruption vulnerability in Linux, published on 15 Aug 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-68478 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-68478/ (Markdown: https://insights.sbomify.com/CVE-2026-68478/index.md)","id":"CVE-2026-68478","markdown":"https://insights.sbomify.com/CVE-2026-68478/index.md","name":"CVE-2026-68478","record":{"aliases":["BELL-CVE-2026-68478","DEBIAN-CVE-2026-68478","GHSA-ppgx-492f-63h6","UBUNTU-CVE-2026-68478"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel driver","requires_auth":"none","summary":"A malicious Memory Stick card can trigger a buffer overflow in the Linux kernel memstick driver, potentially allowing local attackers to execute code or escalate privileges.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nmemstick: ms_block: reject a card that reports too many blocks\n\nmsb_ftl_initialize() computes the zone count from the card block count\nwith no bound:\n\n\tmsb-\u003ezone_count = msb-\u003eblock_count / MS_BLOCKS_IN_ZONE;\n\t...\n\tfor (i = 0; i \u003c msb-\u003ezone_count; i++)\n\t\tmsb-\u003efree_block_count[i] = MS_BLOCKS_IN_ZONE;\n\nmsb-\u003eblock_count is a card value. msb_read_boot_blocks() reads\nnumber_of_blocks from the card boot page and byte swaps it.\nfree_block_count is a fixed int[MS_MAX_ZONES]. MS_MAX_ZONES is 16, so the\nvalid indices are 0 to 15. The init loop above indexes it by zone_count.\nmsb_mark_block_used() and msb_mark_block_unused() index it by\npba / MS_BLOCKS_IN_ZONE, for pba up to block_count - 1. A card may report\nup to 65535 blocks. A block_count above 8192 (MS_MAX_ZONES *\nMS_BLOCKS_IN_ZONE) lets the pba index reach 16. That writes past\nfree_block_count[] and corrupts struct msb_data. A larger count runs the\ninit loop past the end too.\n\nA real Memory Stick has at most 16 zones. So it has at most 8192 blocks.\nmsb_ftl_initialize() now rejects a card that reports more than\nMS_MAX_ZONES * MS_BLOCKS_IN_ZONE blocks.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"memstick: ms_block: reject a card that reports too many blocks","id":"CVE-2026-68478","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"Bluetooth: btrtl: validate firmware patch bounds","id":"CVE-2026-68479"},"packages":[],"prev":{"headline":"ipvs: fix more places with wrong ipv6 transport offsets","id":"CVE-2026-68477"},"products":["Linux"],"published":"2026-08-15","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-08-17","vendors":["Linux"]},"summary":"A malicious Memory Stick card can trigger a buffer overflow in the Linux kernel memstick driver, potentially allowing local attackers to execute code or escalate privileges.","url":"https://insights.sbomify.com/CVE-2026-68478/"}