{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98314 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-98314 is a vulnerability in Linux, published on 6 Oct 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-98314 and fix it if it is affected.\n\nWhat it is: CVE-2026-98314 is a vulnerability in Linux, published on 6 Oct 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-98314 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-98314/ (Markdown: https://insights.sbomify.com/CVE-2026-98314/index.md)","id":"CVE-2026-98314","markdown":"https://insights.sbomify.com/CVE-2026-98314/index.md","name":"CVE-2026-98314","record":{"aliases":["AZL-106380","BELL-CVE-2026-98314","DEBIAN-CVE-2026-98314","GHSA-f958-2rwj-98rc","UBUNTU-CVE-2026-98314"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"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 PCM timer allows local attackers to trigger a NULL pointer dereference and cause a 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\nALSA: pcm: set timer-\u003eprivate_data before registering the PCM timer\n\nsnd_pcm_timer_init() calls snd_device_register() to link the new\nstruct snd_timer into the global timer list while it still carries\nhw.c_resolution = snd_pcm_timer_resolution (and hw.start/hw.stop),\nand only afterwards sets timer-\u003eprivate_data = substream.\n\nOnce the timer is on the list under register_mutex, a concurrent\nreader can already reach it through the same mutex and invoke these\ncallbacks. /proc/asound/timers does this via c_resolution(), and\nsnd_timer_open()+snd_timer_start() reach start()/stop() the same way.\nAll three dereference timer-\u003eprivate_data, which for this brief\nwindow is NULL, giving a NULL-pointer dereference:\n\n  substream = timer-\u003eprivate_data;\n  return substream-\u003eruntime ? ...   // substream is NULL\n\nMove the private_data/private_free assignment before\nsnd_device_register() so the timer is never visible on the list\nwithout its private_data set. On the snd_device_register() failure\npath, private_free() (snd_pcm_timer_free()) can now run, but it only\ndoes substream-\u003etimer = NULL, which is already NULL at that point\nsince substream-\u003etimer is set to the new timer just once, after a\nsuccessful registration -- so the failure path stays safe.","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: pcm: set timer-\u003eprivate_data before registering the PCM timer","id":"CVE-2026-98314","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"ntfs: protect runlist updates with the runlist lock","id":"CVE-2026-98315"},"packages":[],"prev":{"headline":"drm/msm/dp: skip PUSH_IDLE when the link was never enabled","id":"CVE-2026-98313"},"products":["Linux"],"published":"2026-10-06","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-19","vendors":["Linux"]},"summary":"A race condition in the Linux kernel ALSA PCM timer allows local attackers to trigger a NULL pointer dereference and cause a system crash.","url":"https://insights.sbomify.com/CVE-2026-98314/"}