Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. · 16 days later

    Published

  3. · 38 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.18% · top 93% of all CVEs (13 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 4c336e4b1556f4b722ba597bc6e3df786968a600 – < 007c9e637e0e0b9d946b7f0e8a42f1f1aca48d7a
    • affected 4c336e4b1556f4b722ba597bc6e3df786968a600 – < 2c9147b2c0d75091ab451c2461d1c91788a7e60b
    • affected 4c336e4b1556f4b722ba597bc6e3df786968a600 – < 07c2544a47da481043e945322b1bef71cdd7af79
    • affected 4c336e4b1556f4b722ba597bc6e3df786968a600 – < b0dc3f18af01ba9f157b7d810cb22d3752d244ef
    • affected 4c336e4b1556f4b722ba597bc6e3df786968a600 – < 73e89faee1f9b9119fa70b679058b045168ae633
    • affected 4c336e4b1556f4b722ba597bc6e3df786968a600 – < cde2d927c29e82380851f209222256c607969a1f
    • affected 4c336e4b1556f4b722ba597bc6e3df786968a600 – < aee2296d09f6aeff41db369c6fd2dcaea3ee302c
    • affected 4c336e4b1556f4b722ba597bc6e3df786968a600 – < 705c4ed0643366963547b2616d53165f2519c81f
  • Linux · Linux

    • affected 3.13
    • unaffected < 3.13
    • unaffected 5.10.270 – ≤ 5.10.*
    • unaffected 5.15.221 – ≤ 5.15.*
    • unaffected 6.1.188 – ≤ 6.1.*
    • unaffected 6.6.157 – ≤ 6.6.*
    • unaffected 6.12.109 – ≤ 6.12.*
    • unaffected 6.18.50 – ≤ 6.18.*
    • unaffected 7.2.4 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-80930 badge
[![CVE-2026-80930](https://cveledger.app/badge/CVE-2026-80930.svg)](https://cveledger.app/cve/CVE-2026-80930)

Record last updated .