# CVE-2026-80930: tpm: tpm_i2c_nuvoton: disable IRQ on wait timeout

> A missing IRQ disable in the Linux kernel TPM driver can cause resource leaks and denial of service when wait operations time out.

- **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:** 11 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-100532, BELL-CVE-2026-80930, DEBIAN-CVE-2026-80930, GHSA-6qqr-xmx9-c73w, UBUNTU-CVE-2026-80930

## What is CVE-2026-80930?

CVE-2026-80930 is a denial of service vulnerability in Linux, published on 11 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:

tpm: tpm_i2c_nuvoton: disable IRQ on wait timeout

i2c_nuvoton_wait_for_stat() enables the IRQ before waiting for the
interrupt handler to report a status change. If the wait times out, or is
interrupted before the handler runs, the function returns without
balancing the enable_irq() call.

Disable the IRQ before leaving the failed wait path. Also preserve an
interrupted wait's original error code instead of converting it to
-ETIMEDOUT inside the helper.

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


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

Apply the vendor's patch.

## Is CVE-2026-80930 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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