{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-68228 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-68228 is a high-severity 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-68228 and fix it if it is affected.\n\nWhat it is: CVE-2026-68228 is a high-severity 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-68228 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-68228/ (Markdown: https://insights.sbomify.com/CVE-2026-68228/index.md)","id":"CVE-2026-68228","markdown":"https://insights.sbomify.com/CVE-2026-68228/index.md","name":"CVE-2026-68228","record":{"aliases":["BELL-CVE-2026-68228","DEBIAN-CVE-2026-68228","GHSA-rh59-gx8h-f2g3","UBUNTU-CVE-2026-68228"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel media driver","requires_auth":"low_privilege","summary":"A race condition in the Linux kernel wave5 media driver can cause a self-loop in the buffer queue, leading to pointer corruption and potential denial of service.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":7.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nmedia: chips-media: wave5: Move src_buf Removal to finish_encode\n\nDuring encoder processing, there is a case where the IRQ response could\nreturn the buffer back to userspace via v4l2_m2m_buf_done call. In this\ntime, userspace could queue up this same buffer before start_encode removes\nthe index from the ready queue. This would then lead to a case where the\nbuffer in the ready queue could be a self loop due to the\nWRITE_ONCE(prev-\u003enext, new) call in __list_add.\n\nWhen __list_del is finally called, the loop is already made so nothing\npoints back to ready queue list head and pointers are poisoned.\n\nA buffer should not be marked as DONE before the buffer is removed from\nm2m ready queue. Move removal entirely to finish_encode.","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: chips-media: wave5: Move src_buf Removal to finish_encode","id":"CVE-2026-68228","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"media: cedrus: skip invalid H.264 reference list entries","id":"CVE-2026-68229"},"packages":[],"prev":{"headline":"media: cx231xx: fix devres lifetime","id":"CVE-2026-68227"},"products":["Linux"],"published":"2026-08-10","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-08-17","vendors":["Linux"]},"summary":"A race condition in the Linux kernel wave5 media driver can cause a self-loop in the buffer queue, leading to pointer corruption and potential denial of service.","url":"https://insights.sbomify.com/CVE-2026-68228/"}