Bug 2355492 (CVE-2023-52993) - CVE-2023-52993 kernel: x86/i8259: Mark legacy PIC interrupts with IRQ_LEVEL
Summary: CVE-2023-52993 kernel: x86/i8259: Mark legacy PIC interrupts with IRQ_LEVEL
Keywords:
Status: NEW
Alias: CVE-2023-52993
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-03-27 17:04 UTC by OSIDB Bzimport
Modified: 2025-05-05 15:16 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2025-03-27 17:04:11 UTC
In the Linux kernel, the following vulnerability has been resolved:

x86/i8259: Mark legacy PIC interrupts with IRQ_LEVEL

Baoquan reported that after triggering a crash the subsequent crash-kernel
fails to boot about half of the time. It triggers a NULL pointer
dereference in the periodic tick code.

This happens because the legacy timer interrupt (IRQ0) is resent in
software which happens in soft interrupt (tasklet) context. In this context
get_irq_regs() returns NULL which leads to the NULL pointer dereference.

The reason for the resend is a spurious APIC interrupt on the IRQ0 vector
which is captured and leads to a resend when the legacy timer interrupt is
enabled. This is wrong because the legacy PIC interrupts are level
triggered and therefore should never be resent in software, but nothing
ever sets the IRQ_LEVEL flag on those interrupts, so the core code does not
know about their trigger type.

Ensure that IRQ_LEVEL is set when the legacy PCI interrupts are set up.

Comment 5 Avinash Hanwate 2025-03-28 04:54:30 UTC
Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2025032709-CVE-2023-52993-3697@gregkh/T


Note You need to log in before you can comment on or make changes to this bug.