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-97481serial: 8250: fix possible ISR soft lockup

Description

In the Linux kernel, the following vulnerability has been resolved: serial: 8250: fix possible ISR soft lockup There are rare cases in which the host gets stuck in the ISR because it is flooded with messages during the startup phase. The reason for the soft lockup in the ISR is the missing FIFO error IRQ (FIFOE) handling. Not handling it and reporting IRQ_HANDLED triggers the IRQ immediately again. Fix this by adding a check for the FIFOE status and clearing the FIFO if no data is ready (DR). This behavior was observed on an AM62L device which uses the OMAP 8250 driver. Fix it for all 8250 drivers, since the OMAP driver's special IRQ setup handling may trigger this behavior more frequently, but it is not ensured that other 8250 drivers aren't affected.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 9 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.17% · top 93% of all CVEs (12 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 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 4bce4a6f6318035d77d6b6199527b1950bb015f4
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 8b67af8cd90542b2607623e3282811849e191b79
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 95d0b40c0623fd2b58c753f8dd6adda7263e3cd1
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 03ed804a0ddc3d069faf94c47f9e702afe5ca084
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 2881b2e6da02daea1eb8254247ba8fd20c9d3348
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 4295c58990b7a84e8349a2226db692e252825b60
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 0c6bf45e5a345cc3b9ffbeaf9083ecac3c2293eb
  • Linux · Linux

    • affected 2.6.12
    • unaffected < 2.6.12
    • unaffected 5.10.271 – ≤ 5.10.*
    • unaffected 5.15.222 – ≤ 5.15.*
    • unaffected 6.1.189 – ≤ 6.1.*
    • unaffected 6.6.158 – ≤ 6.6.*
    • unaffected 6.12.111 – ≤ 6.12.*
    • unaffected 6.18.53 – ≤ 6.18.*
    • unaffected 7.2 – ≤ *

References

References7

Sources

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

Badge for a README or a ticket

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

Record last updated .