# CVE-2026-90060: ALSA: control: Don't add invalid kcontrols to LED layer

> 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.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Sep 2026
- **Updated:** 21 Oct 2026
- **Also known as:** AZL-102021, BELL-CVE-2026-90060, DEBIAN-CVE-2026-90060, GHSA-pxhq-v7w3-j8wf, UBUNTU-CVE-2026-90060

## What is CVE-2026-90060?

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.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

ALSA: control: Don't add invalid kcontrols to LED layer

The kcontrol LED state layer tries to track the all associated
kcontrol elements with naive assumptions that they are readable.
But one can create a write-only element that has no get callback (even
a user element can do it), and this may lead to a NULL dereference at
the call chain of snd_ctl_led_notify(), as found by syzkaller.

For avoiding the Oops, add a sanity check of the kcontrol's info and
get callbacks, and just skip the invalid kcontrols before assigning
the kctl to the LED layer.

## Which versions are affected by CVE-2026-90060?


## How do I fix CVE-2026-90060?

Apply the vendor's patch.

## Is CVE-2026-90060 being exploited?

There is no known exploitation of CVE-2026-90060 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-90060 and fix it if it is affected.

What 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.
Exploitation: There is no known exploitation of CVE-2026-90060 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-90060/ (Markdown: https://insights.sbomify.com/CVE-2026-90060/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-90060
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-90060
- OSV: https://osv.dev/vulnerability/CVE-2026-90060

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-90060/
Summaries are generated and may contain mistakes; the official description above is the record.