{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-90060 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-90060 is a vulnerability in Linux, published on 17 Sep 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-90060 and fix it if it is affected.\n\nWhat it is: CVE-2026-90060 is a vulnerability in Linux, published on 17 Sep 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-90060 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-90060/ (Markdown: https://insights.sbomify.com/CVE-2026-90060/index.md)","id":"CVE-2026-90060","markdown":"https://insights.sbomify.com/CVE-2026-90060/index.md","name":"CVE-2026-90060","record":{"aliases":["AZL-102021","BELL-CVE-2026-90060","DEBIAN-CVE-2026-90060","GHSA-pxhq-v7w3-j8wf","UBUNTU-CVE-2026-90060"],"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 local attacker can trigger a kernel crash by creating a write-only ALSA control element, causing a NULL pointer dereference in the LED layer.","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: control: Don't add invalid kcontrols to LED layer\n\nThe kcontrol LED state layer tries to track the all associated\nkcontrol elements with naive assumptions that they are readable.\nBut one can create a write-only element that has no get callback (even\na user element can do it), and this may lead to a NULL dereference at\nthe call chain of snd_ctl_led_notify(), as found by syzkaller.\n\nFor avoiding the Oops, add a sanity check of the kcontrol's info and\nget callbacks, and just skip the invalid kcontrols before assigning\nthe kctl to the LED layer.","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: control: Don't add invalid kcontrols to LED layer","id":"CVE-2026-90060","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"netfilter: nf_tables: skip double clone set expressions on element insert","id":"CVE-2026-90061"},"packages":[],"prev":{"headline":"net: stmmac: restore NET_IP_ALIGN in the RX DMA offset","id":"CVE-2026-90059"},"products":["Linux"],"published":"2026-09-17","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 local attacker can trigger a kernel crash by creating a write-only ALSA control element, causing a NULL pointer dereference in the LED layer.","url":"https://insights.sbomify.com/CVE-2026-90060/"}