Поиск уязвимостей
Количество 22
Количество 22
CVE-2023-52993
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.
CVE-2023-52993
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.
CVE-2023-52993
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.
CVE-2023-52993
In the Linux kernel, the following vulnerability has been resolved: x ...
GHSA-g7hp-hfwm-x3rp
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.
BDU:2025-06265
Уязвимость функции init_ISA_irqs() и make_8259A_irq() ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
ROS-20250528-01
Множественные уязвимости kernel-lt
ALT-PU-2023-8451
ALT-PU-2023-8451: package `kernel-image-std-def` update to version 5.10.166-alt1
SUSE-SU-2025:1195-1
Security update for the Linux Kernel
ALT-PU-2023-1206
ALT-PU-2023-1206: package `kernel-image-un-def` update to version 5.15.91-alt1
ALT-PU-2023-1169
ALT-PU-2023-1169: package `kernel-image-std-def` update to version 5.15.91-alt1
ALT-PU-2023-1168
ALT-PU-2023-1168: package `kernel-image-un-def` update to version 6.1.9-alt1
ALT-PU-2023-1311
ALT-PU-2023-1311: package `kernel-image-rt` update to version 5.10.168-alt1.rt83
ALT-PU-2023-1309
ALT-PU-2023-1309: package `kernel-image-rt` update to version 5.10.168-alt1.rt83
ALT-PU-2023-1282
ALT-PU-2023-1282: package `kernel-image-std-kvm` update to version 5.10.168-alt1
SUSE-SU-2025:01983-1
Security update for the Linux Kernel
ALT-PU-2023-1267
ALT-PU-2023-1267: package `kernel-image-mp` update to version 6.1.12-alt1
SUSE-SU-2025:1241-1
Security update for the Linux Kernel
ALT-PU-2023-7682
ALT-PU-2023-7682: package `kernel-image-rpi-def` update to version 5.15.92-alt2
ALT-PU-2023-7007
ALT-PU-2023-7007: package `kernel-image-rpi-def` update to version 5.15.92-alt1
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
CVE-2023-52993 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. | CVSS3: 5.5 | 0% Низкий | больше 1 года назад | |
CVE-2023-52993 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. | CVSS3: 5.5 | 0% Низкий | больше 1 года назад | |
CVE-2023-52993 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. | CVSS3: 5.5 | 0% Низкий | больше 1 года назад | |
CVE-2023-52993 In the Linux kernel, the following vulnerability has been resolved: x ... | CVSS3: 5.5 | 0% Низкий | больше 1 года назад | |
GHSA-g7hp-hfwm-x3rp 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. | CVSS3: 5.5 | 0% Низкий | больше 1 года назад | |
BDU:2025-06265 Уязвимость функции init_ISA_irqs() и make_8259A_irq() ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании | CVSS3: 5.5 | 0% Низкий | почти 4 года назад | |
ROS-20250528-01 Множественные уязвимости kernel-lt | CVSS3: 7.8 | больше 1 года назад | ||
ALT-PU-2023-8451 ALT-PU-2023-8451: package `kernel-image-std-def` update to version 5.10.166-alt1 | CVSS3: 7.8 | больше 3 лет назад | ||
SUSE-SU-2025:1195-1 Security update for the Linux Kernel | больше 1 года назад | |||
ALT-PU-2023-1206 ALT-PU-2023-1206: package `kernel-image-un-def` update to version 5.15.91-alt1 | CVSS3: 7.8 | почти 4 года назад | ||
ALT-PU-2023-1169 ALT-PU-2023-1169: package `kernel-image-std-def` update to version 5.15.91-alt1 | CVSS3: 7.8 | почти 4 года назад | ||
ALT-PU-2023-1168 ALT-PU-2023-1168: package `kernel-image-un-def` update to version 6.1.9-alt1 | CVSS3: 7.8 | почти 4 года назад | ||
ALT-PU-2023-1311 ALT-PU-2023-1311: package `kernel-image-rt` update to version 5.10.168-alt1.rt83 | CVSS3: 8.8 | больше 3 лет назад | ||
ALT-PU-2023-1309 ALT-PU-2023-1309: package `kernel-image-rt` update to version 5.10.168-alt1.rt83 | CVSS3: 8.8 | больше 3 лет назад | ||
ALT-PU-2023-1282 ALT-PU-2023-1282: package `kernel-image-std-kvm` update to version 5.10.168-alt1 | CVSS3: 8.8 | больше 3 лет назад | ||
SUSE-SU-2025:01983-1 Security update for the Linux Kernel | больше 1 года назад | |||
ALT-PU-2023-1267 ALT-PU-2023-1267: package `kernel-image-mp` update to version 6.1.12-alt1 | CVSS3: 8.8 | больше 3 лет назад | ||
SUSE-SU-2025:1241-1 Security update for the Linux Kernel | больше 1 года назад | |||
ALT-PU-2023-7682 ALT-PU-2023-7682: package `kernel-image-rpi-def` update to version 5.15.92-alt2 | CVSS3: 9.3 | почти 3 года назад | ||
ALT-PU-2023-7007 ALT-PU-2023-7007: package `kernel-image-rpi-def` update to version 5.15.92-alt1 | CVSS3: 9.3 | около 3 лет назад |
Уязвимостей на страницу