Поиск уязвимостей
Количество 23
Количество 23
CVE-2024-42302
In the Linux kernel, the following vulnerability has been resolved: PCI/DPC: Fix use-after-free on concurrent DPC and hot-removal Keith reports a use-after-free when a DPC event occurs concurrently to hot-removal of the same portion of the hierarchy: The dpc_handler() awaits readiness of the secondary bus below the Downstream Port where the DPC event occurred. To do so, it polls the config space of the first child device on the secondary bus. If that child device is concurrently removed, accesses to its struct pci_dev cause the kernel to oops. That's because pci_bridge_wait_for_secondary_bus() neglects to hold a reference on the child device. Before v6.3, the function was only called on resume from system sleep or on runtime resume. Holding a reference wasn't necessary back then because the pciehp IRQ thread could never run concurrently. (On resume from system sleep, IRQs are not enabled until after the resume_noirq phase. And runtime resume is always awaited before a PCI devi...
CVE-2024-42302
In the Linux kernel, the following vulnerability has been resolved: PCI/DPC: Fix use-after-free on concurrent DPC and hot-removal Keith reports a use-after-free when a DPC event occurs concurrently to hot-removal of the same portion of the hierarchy: The dpc_handler() awaits readiness of the secondary bus below the Downstream Port where the DPC event occurred. To do so, it polls the config space of the first child device on the secondary bus. If that child device is concurrently removed, accesses to its struct pci_dev cause the kernel to oops. That's because pci_bridge_wait_for_secondary_bus() neglects to hold a reference on the child device. Before v6.3, the function was only called on resume from system sleep or on runtime resume. Holding a reference wasn't necessary back then because the pciehp IRQ thread could never run concurrently. (On resume from system sleep, IRQs are not enabled until after the resume_noirq phase. And runtime resume is always awaited before a PCI devi...
CVE-2024-42302
In the Linux kernel, the following vulnerability has been resolved: PCI/DPC: Fix use-after-free on concurrent DPC and hot-removal Keith reports a use-after-free when a DPC event occurs concurrently to hot-removal of the same portion of the hierarchy: The dpc_handler() awaits readiness of the secondary bus below the Downstream Port where the DPC event occurred. To do so, it polls the config space of the first child device on the secondary bus. If that child device is concurrently removed, accesses to its struct pci_dev cause the kernel to oops. That's because pci_bridge_wait_for_secondary_bus() neglects to hold a reference on the child device. Before v6.3, the function was only called on resume from system sleep or on runtime resume. Holding a reference wasn't necessary back then because the pciehp IRQ thread could never run concurrently. (On resume from system sleep, IRQs are not enabled until after the resume_noirq phase. And runtime resume is always awaited before a PCI dev
CVE-2024-42302
CVE-2024-42302
In the Linux kernel, the following vulnerability has been resolved: P ...
GHSA-37c4-pj3v-mf79
In the Linux kernel, the following vulnerability has been resolved: PCI/DPC: Fix use-after-free on concurrent DPC and hot-removal Keith reports a use-after-free when a DPC event occurs concurrently to hot-removal of the same portion of the hierarchy: The dpc_handler() awaits readiness of the secondary bus below the Downstream Port where the DPC event occurred. To do so, it polls the config space of the first child device on the secondary bus. If that child device is concurrently removed, accesses to its struct pci_dev cause the kernel to oops. That's because pci_bridge_wait_for_secondary_bus() neglects to hold a reference on the child device. Before v6.3, the function was only called on resume from system sleep or on runtime resume. Holding a reference wasn't necessary back then because the pciehp IRQ thread could never run concurrently. (On resume from system sleep, IRQs are not enabled until after the resume_noirq phase. And runtime resume is always awaited before a PCI ...
BDU:2024-10086
Уязвимость функции pci_bridge_wait_for_secondary_bus() драйвера шины PCI ядра операционной системы Linux, позволяющая нарушителю оказать воздействие на конфиденциальность, целостность и доступность защищаемой информации
ROS-20250131-01
Множественные уязвимости kernel-lt
ALT-PU-2024-12232
ALT-PU-2024-12232: package `kernel-image-rt` update to version 5.10.224-alt1.rt116
ALT-PU-2024-11345
ALT-PU-2024-11345: package `kernel-image-std-def` update to version 5.10.224-alt1
ELSA-2024-12815
ELSA-2024-12815: Unbreakable Enterprise kernel security update (IMPORTANT)
SUSE-SU-2024:3209-1
Security update for the Linux Kernel
SUSE-SU-2024:3190-1
Security update for the Linux Kernel
SUSE-SU-2024:3483-1
Security update for the Linux Kernel
ALT-PU-2024-11863
ALT-PU-2024-11863: package `kernel-image-std-def` update to version 6.1.107-alt0.p11.1
ELSA-2025-6966
ELSA-2025-6966: kernel security update (MODERATE)
SUSE-SU-2024:3195-1
Security update for the Linux Kernel
SUSE-SU-2024:3383-1
Security update for the Linux Kernel
SUSE-SU-2024:3194-1
Security update for the Linux Kernel
ALT-PU-2024-11855
ALT-PU-2024-11855: package `kernel-image-un-def` update to version 6.6.48-alt0.p11.1
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
CVE-2024-42302 In the Linux kernel, the following vulnerability has been resolved: PCI/DPC: Fix use-after-free on concurrent DPC and hot-removal Keith reports a use-after-free when a DPC event occurs concurrently to hot-removal of the same portion of the hierarchy: The dpc_handler() awaits readiness of the secondary bus below the Downstream Port where the DPC event occurred. To do so, it polls the config space of the first child device on the secondary bus. If that child device is concurrently removed, accesses to its struct pci_dev cause the kernel to oops. That's because pci_bridge_wait_for_secondary_bus() neglects to hold a reference on the child device. Before v6.3, the function was only called on resume from system sleep or on runtime resume. Holding a reference wasn't necessary back then because the pciehp IRQ thread could never run concurrently. (On resume from system sleep, IRQs are not enabled until after the resume_noirq phase. And runtime resume is always awaited before a PCI devi... | CVSS3: 7.8 | 0% Низкий | около 2 лет назад | |
CVE-2024-42302 In the Linux kernel, the following vulnerability has been resolved: PCI/DPC: Fix use-after-free on concurrent DPC and hot-removal Keith reports a use-after-free when a DPC event occurs concurrently to hot-removal of the same portion of the hierarchy: The dpc_handler() awaits readiness of the secondary bus below the Downstream Port where the DPC event occurred. To do so, it polls the config space of the first child device on the secondary bus. If that child device is concurrently removed, accesses to its struct pci_dev cause the kernel to oops. That's because pci_bridge_wait_for_secondary_bus() neglects to hold a reference on the child device. Before v6.3, the function was only called on resume from system sleep or on runtime resume. Holding a reference wasn't necessary back then because the pciehp IRQ thread could never run concurrently. (On resume from system sleep, IRQs are not enabled until after the resume_noirq phase. And runtime resume is always awaited before a PCI devi... | CVSS3: 7.1 | 0% Низкий | около 2 лет назад | |
CVE-2024-42302 In the Linux kernel, the following vulnerability has been resolved: PCI/DPC: Fix use-after-free on concurrent DPC and hot-removal Keith reports a use-after-free when a DPC event occurs concurrently to hot-removal of the same portion of the hierarchy: The dpc_handler() awaits readiness of the secondary bus below the Downstream Port where the DPC event occurred. To do so, it polls the config space of the first child device on the secondary bus. If that child device is concurrently removed, accesses to its struct pci_dev cause the kernel to oops. That's because pci_bridge_wait_for_secondary_bus() neglects to hold a reference on the child device. Before v6.3, the function was only called on resume from system sleep or on runtime resume. Holding a reference wasn't necessary back then because the pciehp IRQ thread could never run concurrently. (On resume from system sleep, IRQs are not enabled until after the resume_noirq phase. And runtime resume is always awaited before a PCI dev | CVSS3: 7.8 | 0% Низкий | около 2 лет назад | |
CVSS3: 7.8 | 0% Низкий | около 2 лет назад | ||
CVE-2024-42302 In the Linux kernel, the following vulnerability has been resolved: P ... | CVSS3: 7.8 | 0% Низкий | около 2 лет назад | |
GHSA-37c4-pj3v-mf79 In the Linux kernel, the following vulnerability has been resolved: PCI/DPC: Fix use-after-free on concurrent DPC and hot-removal Keith reports a use-after-free when a DPC event occurs concurrently to hot-removal of the same portion of the hierarchy: The dpc_handler() awaits readiness of the secondary bus below the Downstream Port where the DPC event occurred. To do so, it polls the config space of the first child device on the secondary bus. If that child device is concurrently removed, accesses to its struct pci_dev cause the kernel to oops. That's because pci_bridge_wait_for_secondary_bus() neglects to hold a reference on the child device. Before v6.3, the function was only called on resume from system sleep or on runtime resume. Holding a reference wasn't necessary back then because the pciehp IRQ thread could never run concurrently. (On resume from system sleep, IRQs are not enabled until after the resume_noirq phase. And runtime resume is always awaited before a PCI ... | CVSS3: 7.8 | 0% Низкий | около 2 лет назад | |
BDU:2024-10086 Уязвимость функции pci_bridge_wait_for_secondary_bus() драйвера шины PCI ядра операционной системы Linux, позволяющая нарушителю оказать воздействие на конфиденциальность, целостность и доступность защищаемой информации | CVSS3: 7.8 | 0% Низкий | больше 2 лет назад | |
ROS-20250131-01 Множественные уязвимости kernel-lt | CVSS3: 7.8 | почти 2 года назад | ||
ALT-PU-2024-12232 ALT-PU-2024-12232: package `kernel-image-rt` update to version 5.10.224-alt1.rt116 | CVSS3: 7.8 | около 2 лет назад | ||
ALT-PU-2024-11345 ALT-PU-2024-11345: package `kernel-image-std-def` update to version 5.10.224-alt1 | CVSS3: 7.8 | около 2 лет назад | ||
ELSA-2024-12815 ELSA-2024-12815: Unbreakable Enterprise kernel security update (IMPORTANT) | почти 2 года назад | |||
SUSE-SU-2024:3209-1 Security update for the Linux Kernel | около 2 лет назад | |||
SUSE-SU-2024:3190-1 Security update for the Linux Kernel | около 2 лет назад | |||
SUSE-SU-2024:3483-1 Security update for the Linux Kernel | около 2 лет назад | |||
ALT-PU-2024-11863 ALT-PU-2024-11863: package `kernel-image-std-def` update to version 6.1.107-alt0.p11.1 | CVSS3: 7.8 | около 2 лет назад | ||
ELSA-2025-6966 ELSA-2025-6966: kernel security update (MODERATE) | больше 1 года назад | |||
SUSE-SU-2024:3195-1 Security update for the Linux Kernel | около 2 лет назад | |||
SUSE-SU-2024:3383-1 Security update for the Linux Kernel | около 2 лет назад | |||
SUSE-SU-2024:3194-1 Security update for the Linux Kernel | около 2 лет назад | |||
ALT-PU-2024-11855 ALT-PU-2024-11855: package `kernel-image-un-def` update to version 6.6.48-alt0.p11.1 | CVSS3: 8.8 | около 2 лет назад |
Уязвимостей на страницу