# CVE-2022-48735: ALSA: hda: Fix UAF of leds class devs at unbinding

> A use-after-free vulnerability in the Linux kernel ALSA HDA driver allows attackers to cause a denial of service or potentially execute code during device unbinding.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 20 Jun 2024
- **Updated:** 5 Aug 2026
- **Also known as:** DEBIAN-CVE-2022-48735, GHSA-cq4f-h5g8-8r5h, UBUNTU-CVE-2022-48735

## What is CVE-2022-48735?

CVE-2022-48735 is a high-severity use after free vulnerability in Linux kernel, published on 20 Jun 2024. 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: hda: Fix UAF of leds class devs at unbinding

The LED class devices that are created by HD-audio codec drivers are
registered via devm_led_classdev_register() and associated with the
HD-audio codec device.  Unfortunately, it turned out that the devres
release doesn't work for this case; namely, since the codec resource
release happens before the devm call chain, it triggers a NULL
dereference or a UAF for a stale set_brightness_delay callback.

For fixing the bug, this patch changes the LED class device register
and unregister in a manual manner without devres, keeping the
instances in hda_gen_spec.

Weakness: CWE-476 (NULL Pointer Dereference), CWE-416 (Use After Free)

## Which versions are affected by CVE-2022-48735?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2022-48735?

Apply the vendor's patch.

## Is CVE-2022-48735 being exploited?

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

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-48735 and fix it if it is affected.

What it is: CVE-2022-48735 is a high-severity use after free vulnerability in Linux kernel, published on 20 Jun 2024. 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-2022-48735 in the wild and no public exploit code.

Affected product: Linux kernel. 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-2022-48735/ (Markdown: https://insights.sbomify.com/CVE-2022-48735/index.md)
```

## Sources

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

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