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-2024-26999serial/pmac_zilog: Remove flawed mitigation for rx irq flood

Description

In the Linux kernel, the following vulnerability has been resolved: serial/pmac_zilog: Remove flawed mitigation for rx irq flood The mitigation was intended to stop the irq completely. That may be better than a hard lock-up but it turns out that you get a crash anyway if you're using pmac_zilog as a serial console: ttyPZ0: pmz: rx irq flood ! BUG: spinlock recursion on CPU#0, swapper/0 That's because the pr_err() call in pmz_receive_chars() results in pmz_console_write() attempting to lock a spinlock already locked in pmz_interrupt(). With CONFIG_DEBUG_SPINLOCK=y, this produces a fatal BUG splat. The spinlock in question is the one in struct uart_port. Even when it's not fatal, the serial port rx function ceases to work. Also, the iteration limit doesn't play nicely with QEMU, as can be seen in the bug report linked below. A web search for other reports of the error message "pmz: rx irq flood" didn't produce anything. So I don't think this code is needed any more. Remove it.

Timeline

  1. ID reserved

    By Linux

  2. · 2 months later

    Published

  3. · 2 years 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

CVSS scores of CVE-2024-26999, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.18% · top 92% of all CVEs (20 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 69a02273e288011b521ee7c1f3ab2c23fda633ce
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < d679c816929d62af51c8e6d7fc0e165c9412d2f3
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < ab86cf6f8d24e63e9aca23da5108af1aa5483928
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 7a3bbe41efa55323b6ea3c35fa15941d4dbecdef
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < bbaafbb4651fede8d3c3881601ecaa4f834f9d3f
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 52aaf1ff14622a04148dbb9ccce6d9de5d534ea7
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < ca09dfc3cfdf89e6af3ac24e1c6c0be5c575a729
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 1be3226445362bfbf461c92a5bcdb1723f2e4907
  • Linux · Linux

    • affected 2.6.12
    • unaffected < 2.6.12
    • unaffected 4.19.313 – ≤ 4.19.*
    • unaffected 5.4.275 – ≤ 5.4.*
    • unaffected 5.10.216 – ≤ 5.10.*
    • unaffected 5.15.157 – ≤ 5.15.*
    • unaffected 6.1.88 – ≤ 6.1.*
    • unaffected 6.6.29 – ≤ 6.6.*
    • unaffected 6.8.8 – ≤ 6.8.*
    • unaffected 6.9 – ≤ *

References

References12

Sources

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

Badge for a README or a ticket

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

Record last updated .