{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-68200 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-68200 is a high-severity use after free 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-68200 and fix it if it is affected.\n\nWhat it is: CVE-2026-68200 is a high-severity use after free 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-68200 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-68200/ (Markdown: https://insights.sbomify.com/CVE-2026-68200/index.md)","id":"CVE-2026-68200","markdown":"https://insights.sbomify.com/CVE-2026-68200/index.md","name":"CVE-2026-68200","record":{"aliases":["BELL-CVE-2026-68200","DEBIAN-CVE-2026-68200","GHSA-78vp-jqhh-pcc3","UBUNTU-CVE-2026-68200"],"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 ALSA","requires_auth":"low_privilege","summary":"A race condition in the Linux kernel ALSA timer allows local attackers to trigger a use-after-free, potentially leading to code execution or privilege escalation.","user_interaction":"not_required","vuln_class":"use_after_free"},"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":[{"id":"CWE-362","name":"Concurrent Execution using Shared Resource with Improper Synchronization"}],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nALSA: timer: don't re-enter an instance callback that is still running\n\nThe userspace-driven timer (utimer) TRIGGER ioctl calls\nsnd_timer_interrupt() directly with no serialization, so two threads\ntriggering the same utimer can run snd_timer_interrupt() on one\nsnd_timer concurrently.\n\nsnd_timer_process_callbacks() drops timer-\u003elock around each instance\ncallback and marks the in-flight callback with the single\nSNDRV_TIMER_IFLG_CALLBACK bit; snd_timer_close_locked() waits on that\nbit to drain an in-flight callback before freeing the instance. The bit\ncannot represent two concurrent callbacks: when a second interrupt\nre-queues an instance whose callback is still running, both run at once,\nthe first to finish clears the bit, and the close-path drain then frees\nthe instance (and its callback_data) while the other callback is still\nlive - a use-after-free reachable by any user able to open\n/dev/snd/timer, both via a user timer instance and via a sequencer queue\ntimer bound to the utimer.\n\nsnd_timer_interrupt() sets IFLG_CALLBACK before dropping timer-\u003elock, so\na concurrent interrupt already observes it under the lock. Skip\nre-queuing an instance (and its slaves) to the ack/sack list while its\ncallback is in flight; the accumulated pticks are delivered on the next\ntick, so no event is lost.","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":"ALSA: timer: don't re-enter an instance callback that is still running","id":"CVE-2026-68200","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"use_after_free","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"ALSA: timer: drain a slave's callback before its master detaches it","id":"CVE-2026-68201"},"packages":[],"prev":{"headline":"wifi: ath6kl: fix OOB access from firmware ADDBA window size","id":"CVE-2026-68199"},"products":["Linux"],"published":"2026-08-10","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"A race condition in the Linux kernel ALSA timer allows local attackers to trigger a use-after-free, potentially leading to code execution or privilege escalation.","url":"https://insights.sbomify.com/CVE-2026-68200/"}