# CVE-2026-80621: PCI: dwc: Avoid dwc_pcie_rasdes_debugfs_deinit() NULL dereference when no RAS DES capability

> A null pointer dereference in the Linux kernel PCI DWC driver can cause a system crash when debugfs teardown occurs without RAS DES capability.

- **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:** 28 Aug 2026
- **Updated:** 28 Aug 2026
- **Also known as:** BELL-CVE-2026-80621, DEBIAN-CVE-2026-80621, GHSA-257h-4q39-v2v3, UBUNTU-CVE-2026-80621

## What is CVE-2026-80621?

CVE-2026-80621 is a vulnerability in Linux, published on 28 Aug 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:

PCI: dwc: Avoid dwc_pcie_rasdes_debugfs_deinit() NULL dereference when no RAS DES capability

dwc_pcie_rasdes_debugfs_init() returns success when the controller has no
RAS DES capability, leaving pci->debugfs->rasdes_info unset. The common
debugfs teardown path still calls dwc_pcie_rasdes_debugfs_deinit(), which
dereferences rasdes_info unconditionally.

Return early when no RAS DES state was allocated. In that case no RAS DES
mutex was initialized, so there is nothing to destroy.

[mani: reworded subject]

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


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

Apply the vendor's patch.

## Is CVE-2026-80621 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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