# CVE-2026-80743: ASoC: xilinx: formatter_pcm: pass aud_drv_data to irq handlers

> A race condition in the Xilinx formatter PCM driver causes a null pointer dereference and kernel crash if an interrupt occurs during probe.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 3 Sep 2026
- **Updated:** 3 Sep 2026
- **Also known as:** AZL-99077, BELL-CVE-2026-80743, DEBIAN-CVE-2026-80743, GHSA-x2vc-grmm-48qg, UBUNTU-CVE-2026-80743

## What is CVE-2026-80743?

CVE-2026-80743 is a vulnerability in Linux, published on 3 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:

ASoC: xilinx: formatter_pcm: pass aud_drv_data to irq handlers

The irq handlers take a struct device pointer and call
dev_get_drvdata() to obtain the driver data.  However, the driver
data is only set at the end of probe, after devm_request_irq(),
so an interrupt taken in between causes the handlers to pass a
NULL pointer to readl() and crash.

Pass the private data directly as the devm_request_irq() argument
instead of the device pointer, matching what the handlers expect.

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


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

Apply the vendor's patch.

## Is CVE-2026-80743 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-80743 is a vulnerability in Linux, published on 3 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-80743 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-80743/ (Markdown: https://insights.sbomify.com/CVE-2026-80743/index.md)
```

## Sources

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

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