{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-68203 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-68203 is a memory corruption vulnerability in Linux, published on 10 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-68203 and fix it if it is affected.\n\nWhat it is: CVE-2026-68203 is a memory corruption vulnerability in Linux, published on 10 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-68203 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-68203/ (Markdown: https://insights.sbomify.com/CVE-2026-68203/index.md)","id":"CVE-2026-68203","markdown":"https://insights.sbomify.com/CVE-2026-68203/index.md","name":"CVE-2026-68203","record":{"aliases":["AZL-95166","BELL-CVE-2026-68203","DEBIAN-CVE-2026-68203","GHSA-m883-8hm9-jvgx","UBUNTU-CVE-2026-68203"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"none","summary":"A reference leak and incorrect cleanup in the Linux kernel vivid driver can lead to memory corruption and denial of service.","user_interaction":"not_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\nmedia: vivid: fix cleanup bugs in vivid_init()\n\nWhen platform_device_register() fails in vivid_init(), the embedded\nstruct device in vivid_pdev has already been initialized by\ndevice_initialize(), but the failure path jumps to free_output_strings\nwithout dropping the device reference for the current platform device:\n\n  vivid_init()\n    -\u003e platform_device_register(\u0026vivid_pdev)\n       -\u003e device_initialize(\u0026vivid_pdev.dev)\n       -\u003e setup_pdev_dma_masks(\u0026vivid_pdev)\n       -\u003e platform_device_add(\u0026vivid_pdev)\n\nThis leads to a reference leak when platform_device_register() fails.\nFix this by calling platform_device_put() before jumping to the common\ncleanup path.\n\nAlso, the unreg_driver label incorrectly calls\nplatform_driver_register() instead of platform_driver_unregister(),\nwhich breaks cleanup when workqueue creation fails after successful\ndriver registration. Fix that as well.\n\nThe reference leak was identified by a static analysis tool I developed\nand confirmed by manual review. The incorrect cleanup call was found\nduring code inspection.","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":"media: vivid: fix cleanup bugs in vivid_init()","id":"CVE-2026-68203","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"media: vivid: check for vb2_is_busy() when toggling caps","id":"CVE-2026-68204"},"packages":[],"prev":{"headline":"ALSA: seq: close a re-opened queue timer in the destructor","id":"CVE-2026-68202"},"products":["Linux"],"published":"2026-08-10","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-10-21","vendors":["Linux"]},"summary":"A reference leak and incorrect cleanup in the Linux kernel vivid driver can lead to memory corruption and denial of service.","url":"https://insights.sbomify.com/CVE-2026-68203/"}