{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-68208 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-68208 is a 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-68208 and fix it if it is affected.\n\nWhat it is: CVE-2026-68208 is a 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-68208 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-68208/ (Markdown: https://insights.sbomify.com/CVE-2026-68208/index.md)","id":"CVE-2026-68208","markdown":"https://insights.sbomify.com/CVE-2026-68208/index.md","name":"CVE-2026-68208","record":{"aliases":["DEBIAN-CVE-2026-68208","GHSA-vq2x-638j-2gq9","UBUNTU-CVE-2026-68208"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel driver","requires_auth":"none","summary":"A flaw in the TI VPE driver incorrectly handles memory allocation failures, potentially leading to a null pointer dereference and system crash.","user_interaction":"not_required","vuln_class":"null_dereference"},"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: ti: vpe: Fix the error code of devm_kzalloc() in vip_probe_slice()\n\nIn vip_probe_slice(), the error check for devm_kzalloc() incorrectly\nuses PTR_ERR_OR_ZERO() which returns 0 for NULL pointer.\n\nReturn -ENOMEM for devm_kzalloc() failure.","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: ti: vpe: Fix the error code of devm_kzalloc() in vip_probe_slice()","id":"CVE-2026-68208","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"media: sun4i-csi: Return queued buffers on start_streaming() failure","id":"CVE-2026-68209"},"packages":[],"prev":{"headline":"media: ti: vpe: unwind v4l2 device registration on probe error","id":"CVE-2026-68207"},"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-08-17","vendors":["Linux"]},"summary":"A flaw in the TI VPE driver incorrectly handles memory allocation failures, potentially leading to a null pointer dereference and system crash.","url":"https://insights.sbomify.com/CVE-2026-68208/"}