CVE-2024-26999

serial/pmac_zilog: Remove flawed mitigation for rx irq flood

MEDIUM
5.5
CVSS Score
Published: May 1, 2024 at 05:28 AM UTC
Updated: June 17, 2026 at 07:18 AM UTC
2 products affected across 2 vendorsLinux KernelDebian Linux

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.5
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

2.6.12 ≤ v < 4.19.3132.6.12 ≤ v < 5.10.2162.6.12 ≤ v < 5.15.1572.6.12 ≤ v < 5.4.2752.6.12 ≤ v < 6.1.882.6.12 ≤ v < 6.6.292.6.12 ≤ v < 6.8.82.6.12 ≤ v < 6.95.16 ≤ v < 6.1.886.2 ≤ v < 6.6.296.7 ≤ v < 6.8.81da177e4c3f41524e886b7f1b8a0c1fc7321cac26.9 rc16.9 rc26.9 rc36.9 rc4
Vendor states this is fixed in 1be3226445362bfbf461c92a5bcdb1723f2e4907 (fixed)
Vendor states this is fixed in 52aaf1ff14622a04148dbb9ccce6d9de5d534ea7 (fixed)
Vendor states this is fixed in 69a02273e288011b521ee7c1f3ab2c23fda633ce (fixed)
Vendor states this is fixed in 7a3bbe41efa55323b6ea3c35fa15941d4dbecdef (fixed)
Vendor states this is fixed in ab86cf6f8d24e63e9aca23da5108af1aa5483928 (fixed)
Vendor states this is fixed in bbaafbb4651fede8d3c3881601ecaa4f834f9d3f (fixed)
Vendor states this is fixed in ca09dfc3cfdf89e6af3ac24e1c6c0be5c575a729 (fixed)
Vendor states this is fixed in d679c816929d62af51c8e6d7fc0e165c9412d2f3 (fixed)
Vendor states this is fixed in 2.6.12 (unaffected)
Vendor states this is fixed in 4.19.313 (unaffected)
Vendor states this is fixed in 5.10.216 (unaffected)
Vendor states this is fixed in 5.15.157 (unaffected)
Vendor states this is fixed in 5.4.275 (unaffected)
Vendor states this is fixed in 6.1.88 (unaffected)
Vendor states this is fixed in 6.6.29 (unaffected)
Vendor states this is fixed in 6.8.8 (unaffected)
Vendor states this is fixed in 6.9 (unaffected)

References (12)

Mailing ListPatch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/1be3226445362bfbf461c92a5bcdb1723f2e4907
Mailing ListPatch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/52aaf1ff14622a04148dbb9ccce6d9de5d534ea7
Mailing ListPatch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/69a02273e288011b521ee7c1f3ab2c23fda633ce
Mailing ListPatch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/7a3bbe41efa55323b6ea3c35fa15941d4dbecdef
Mailing ListPatch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/ab86cf6f8d24e63e9aca23da5108af1aa5483928
Mailing ListPatch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/bbaafbb4651fede8d3c3881601ecaa4f834f9d3f
Mailing ListPatch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/ca09dfc3cfdf89e6af3ac24e1c6c0be5c575a729
Mailing ListPatch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/d679c816929d62af51c8e6d7fc0e165c9412d2f3

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-667

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card