CVE-2024-26999: Vulnerability in Linux Linux
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.
AI Analysis
Technical Summary
CVE-2024-26999 is a vulnerability identified in the Linux kernel specifically related to the serial/pmac_zilog driver, which handles serial communication on certain Power Macintosh (pmac) hardware using the Zilog serial controller. The vulnerability stems from a flawed mitigation mechanism intended to handle receive (rx) interrupt request (irq) floods. The original mitigation aimed to stop the irq completely to prevent system lock-ups. However, this approach inadvertently causes a crash when the pmac_zilog driver is used as a serial console. The root cause is a spinlock recursion bug triggered by the pr_err() logging call inside the pmz_receive_chars() function. This call leads to pmz_console_write() attempting to acquire a spinlock that is already held by pmz_interrupt(), resulting in a fatal BUG splat when CONFIG_DEBUG_SPINLOCK=y is enabled. Even without fatal crashes, the serial port's receive function stops working, causing loss of serial console functionality. Additionally, the mitigation's iteration limit does not interact well with QEMU virtualization environments, further complicating stability. The vulnerability is considered to be a legacy issue since the problematic mitigation code appears unnecessary and has been removed in the patch. There are no known exploits in the wild, and the issue primarily affects systems using the pmac_zilog serial driver, which is niche hardware. The vulnerability impacts kernel stability and availability of serial console access rather than confidentiality or integrity.
Potential Impact
For European organizations, the impact of CVE-2024-26999 is likely limited due to the niche nature of the affected hardware and driver. The pmac_zilog driver is specific to older Power Macintosh hardware, which is uncommon in modern enterprise environments. However, organizations that rely on legacy Power Macintosh systems running Linux with serial console access via pmac_zilog could experience system crashes or loss of serial console functionality, impacting system availability and remote management capabilities. This could be critical in environments where serial consoles are used for out-of-band management or debugging, such as in industrial control systems, research labs, or specialized embedded systems. The vulnerability could also affect virtualized environments using QEMU if they emulate this hardware and use the affected driver, potentially causing instability. Overall, the threat is primarily a stability and availability concern rather than a direct security breach or data compromise. The lack of known exploits and the removal of the flawed mitigation code reduce the urgency but do not eliminate the need for patching in affected environments.
Mitigation Recommendations
1. Apply the latest Linux kernel updates that remove the flawed mitigation code in the pmac_zilog driver to prevent spinlock recursion and crashes. 2. For organizations using legacy Power Macintosh hardware with Linux, verify if the pmac_zilog driver is in use and plan for kernel upgrades or hardware replacement if feasible. 3. In virtualized environments using QEMU, ensure that the emulated hardware does not rely on the affected driver or apply kernel patches to avoid instability. 4. Enable kernel debugging and monitoring to detect any irq flood conditions or serial console failures early. 5. Avoid relying solely on serial console access for critical management on affected systems; implement alternative remote management methods where possible. 6. Conduct thorough testing of kernel updates in controlled environments before deployment to prevent unexpected downtime. 7. Document and communicate the update process to system administrators responsible for legacy hardware to ensure timely patching.
Affected Countries
Germany, United Kingdom, France, Netherlands, Sweden
CVE-2024-26999: Vulnerability in Linux Linux
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.
AI-Powered Analysis
Technical Analysis
CVE-2024-26999 is a vulnerability identified in the Linux kernel specifically related to the serial/pmac_zilog driver, which handles serial communication on certain Power Macintosh (pmac) hardware using the Zilog serial controller. The vulnerability stems from a flawed mitigation mechanism intended to handle receive (rx) interrupt request (irq) floods. The original mitigation aimed to stop the irq completely to prevent system lock-ups. However, this approach inadvertently causes a crash when the pmac_zilog driver is used as a serial console. The root cause is a spinlock recursion bug triggered by the pr_err() logging call inside the pmz_receive_chars() function. This call leads to pmz_console_write() attempting to acquire a spinlock that is already held by pmz_interrupt(), resulting in a fatal BUG splat when CONFIG_DEBUG_SPINLOCK=y is enabled. Even without fatal crashes, the serial port's receive function stops working, causing loss of serial console functionality. Additionally, the mitigation's iteration limit does not interact well with QEMU virtualization environments, further complicating stability. The vulnerability is considered to be a legacy issue since the problematic mitigation code appears unnecessary and has been removed in the patch. There are no known exploits in the wild, and the issue primarily affects systems using the pmac_zilog serial driver, which is niche hardware. The vulnerability impacts kernel stability and availability of serial console access rather than confidentiality or integrity.
Potential Impact
For European organizations, the impact of CVE-2024-26999 is likely limited due to the niche nature of the affected hardware and driver. The pmac_zilog driver is specific to older Power Macintosh hardware, which is uncommon in modern enterprise environments. However, organizations that rely on legacy Power Macintosh systems running Linux with serial console access via pmac_zilog could experience system crashes or loss of serial console functionality, impacting system availability and remote management capabilities. This could be critical in environments where serial consoles are used for out-of-band management or debugging, such as in industrial control systems, research labs, or specialized embedded systems. The vulnerability could also affect virtualized environments using QEMU if they emulate this hardware and use the affected driver, potentially causing instability. Overall, the threat is primarily a stability and availability concern rather than a direct security breach or data compromise. The lack of known exploits and the removal of the flawed mitigation code reduce the urgency but do not eliminate the need for patching in affected environments.
Mitigation Recommendations
1. Apply the latest Linux kernel updates that remove the flawed mitigation code in the pmac_zilog driver to prevent spinlock recursion and crashes. 2. For organizations using legacy Power Macintosh hardware with Linux, verify if the pmac_zilog driver is in use and plan for kernel upgrades or hardware replacement if feasible. 3. In virtualized environments using QEMU, ensure that the emulated hardware does not rely on the affected driver or apply kernel patches to avoid instability. 4. Enable kernel debugging and monitoring to detect any irq flood conditions or serial console failures early. 5. Avoid relying solely on serial console access for critical management on affected systems; implement alternative remote management methods where possible. 6. Conduct thorough testing of kernel updates in controlled environments before deployment to prevent unexpected downtime. 7. Document and communicate the update process to system administrators responsible for legacy hardware to ensure timely patching.
Affected Countries
For access to advanced analysis and higher rate limits, contact root@offseq.com
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- Linux
- Date Reserved
- 2024-02-19T14:20:24.206Z
- Cisa Enriched
- true
- Cvss Version
- null
- State
- PUBLISHED
Threat ID: 682d9829c4522896dcbe3063
Added to database: 5/21/2025, 9:08:57 AM
Last enriched: 6/29/2025, 2:11:13 PM
Last updated: 8/15/2025, 7:04:06 AM
Views: 11
Related Threats
CVE-2025-53948: CWE-415 Double Free in Santesoft Sante PACS Server
HighCVE-2025-52584: CWE-122 Heap-based Buffer Overflow in Ashlar-Vellum Cobalt
HighCVE-2025-46269: CWE-122 Heap-based Buffer Overflow in Ashlar-Vellum Cobalt
HighCVE-2025-54862: CWE-79 Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') in Santesoft Sante PACS Server
MediumCVE-2025-54759: CWE-79 Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') in Santesoft Sante PACS Server
MediumActions
Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.
External Links
Need enhanced features?
Contact root@offseq.com for Pro access with improved analysis and higher rate limits.