Поиск уязвимостей
Количество 26
Количество 26
CVE-2024-26812
In the Linux kernel, the following vulnerability has been resolved: vfio/pci: Create persistent INTx handler A vulnerability exists where the eventfd for INTx signaling can be deconfigured, which unregisters the IRQ handler but still allows eventfds to be signaled with a NULL context through the SET_IRQS ioctl or through unmask irqfd if the device interrupt is pending. Ideally this could be solved with some additional locking; the igate mutex serializes the ioctl and config space accesses, and the interrupt handler is unregistered relative to the trigger, but the irqfd path runs asynchronous to those. The igate mutex cannot be acquired from the atomic context of the eventfd wake function. Disabling the irqfd relative to the eventfd registration is potentially incompatible with existing userspace. As a result, the solution implemented here moves configuration of the INTx interrupt handler to track the lifetime of the INTx context object and irq_type configuration, rather than regis...
CVE-2024-26812
In the Linux kernel, the following vulnerability has been resolved: vfio/pci: Create persistent INTx handler A vulnerability exists where the eventfd for INTx signaling can be deconfigured, which unregisters the IRQ handler but still allows eventfds to be signaled with a NULL context through the SET_IRQS ioctl or through unmask irqfd if the device interrupt is pending. Ideally this could be solved with some additional locking; the igate mutex serializes the ioctl and config space accesses, and the interrupt handler is unregistered relative to the trigger, but the irqfd path runs asynchronous to those. The igate mutex cannot be acquired from the atomic context of the eventfd wake function. Disabling the irqfd relative to the eventfd registration is potentially incompatible with existing userspace. As a result, the solution implemented here moves configuration of the INTx interrupt handler to track the lifetime of the INTx context object and irq_type configuration, rather than regis...
CVE-2024-26812
In the Linux kernel, the following vulnerability has been resolved: vfio/pci: Create persistent INTx handler A vulnerability exists where the eventfd for INTx signaling can be deconfigured, which unregisters the IRQ handler but still allows eventfds to be signaled with a NULL context through the SET_IRQS ioctl or through unmask irqfd if the device interrupt is pending. Ideally this could be solved with some additional locking; the igate mutex serializes the ioctl and config space accesses, and the interrupt handler is unregistered relative to the trigger, but the irqfd path runs asynchronous to those. The igate mutex cannot be acquired from the atomic context of the eventfd wake function. Disabling the irqfd relative to the eventfd registration is potentially incompatible with existing userspace. As a result, the solution implemented here moves configuration of the INTx interrupt handler to track the lifetime of the INTx context object and irq_type configuration, rather than regi
CVE-2024-26812
vfio/pci: Create persistent INTx handler
CVE-2024-26812
In the Linux kernel, the following vulnerability has been resolved: v ...
GHSA-p8g6-7v7w-4whg
In the Linux kernel, the following vulnerability has been resolved: vfio/pci: Create persistent INTx handler A vulnerability exists where the eventfd for INTx signaling can be deconfigured, which unregisters the IRQ handler but still allows eventfds to be signaled with a NULL context through the SET_IRQS ioctl or through unmask irqfd if the device interrupt is pending. Ideally this could be solved with some additional locking; the igate mutex serializes the ioctl and config space accesses, and the interrupt handler is unregistered relative to the trigger, but the irqfd path runs asynchronous to those. The igate mutex cannot be acquired from the atomic context of the eventfd wake function. Disabling the irqfd relative to the eventfd registration is potentially incompatible with existing userspace. As a result, the solution implemented here moves configuration of the INTx interrupt handler to track the lifetime of the INTx context object and irq_type configuration, rather than r...
BDU:2024-09205
Уязвимость компонента vfio ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании(DoS)
ROS-20241024-02
Множественные уязвимости kernel-lt
SUSE-SU-2024:3189-1
Security update for the Linux Kernel
SUSE-SU-2024:3252-1
Security update for the Linux Kernel
SUSE-SU-2024:3251-1
Security update for the Linux Kernel
ALT-PU-2024-18366
ALT-PU-2024-18366: package `kernel-image-std-def` update to version 6.1.84-alt1
ALT-PU-2024-18059
ALT-PU-2024-18059: package `kernel-image-un-def` update to version 6.1.84-alt1
ALT-PU-2024-18470
ALT-PU-2024-18470: package `kernel-image-un-def` update to version 6.6.24-alt1
ALT-PU-2024-18142
ALT-PU-2024-18142: package `kernel-image-6.8` update to version 6.8.3-alt1
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-18212
ALT-PU-2024-18212: package `kernel-image-pine` update to version 6.6.27-alt1
SUSE-SU-2024:3195-1
Security update for the Linux Kernel
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
CVE-2024-26812 In the Linux kernel, the following vulnerability has been resolved: vfio/pci: Create persistent INTx handler A vulnerability exists where the eventfd for INTx signaling can be deconfigured, which unregisters the IRQ handler but still allows eventfds to be signaled with a NULL context through the SET_IRQS ioctl or through unmask irqfd if the device interrupt is pending. Ideally this could be solved with some additional locking; the igate mutex serializes the ioctl and config space accesses, and the interrupt handler is unregistered relative to the trigger, but the irqfd path runs asynchronous to those. The igate mutex cannot be acquired from the atomic context of the eventfd wake function. Disabling the irqfd relative to the eventfd registration is potentially incompatible with existing userspace. As a result, the solution implemented here moves configuration of the INTx interrupt handler to track the lifetime of the INTx context object and irq_type configuration, rather than regis... | CVSS3: 5.5 | 0% Низкий | больше 2 лет назад | |
CVE-2024-26812 In the Linux kernel, the following vulnerability has been resolved: vfio/pci: Create persistent INTx handler A vulnerability exists where the eventfd for INTx signaling can be deconfigured, which unregisters the IRQ handler but still allows eventfds to be signaled with a NULL context through the SET_IRQS ioctl or through unmask irqfd if the device interrupt is pending. Ideally this could be solved with some additional locking; the igate mutex serializes the ioctl and config space accesses, and the interrupt handler is unregistered relative to the trigger, but the irqfd path runs asynchronous to those. The igate mutex cannot be acquired from the atomic context of the eventfd wake function. Disabling the irqfd relative to the eventfd registration is potentially incompatible with existing userspace. As a result, the solution implemented here moves configuration of the INTx interrupt handler to track the lifetime of the INTx context object and irq_type configuration, rather than regis... | CVSS3: 4.1 | 0% Низкий | больше 2 лет назад | |
CVE-2024-26812 In the Linux kernel, the following vulnerability has been resolved: vfio/pci: Create persistent INTx handler A vulnerability exists where the eventfd for INTx signaling can be deconfigured, which unregisters the IRQ handler but still allows eventfds to be signaled with a NULL context through the SET_IRQS ioctl or through unmask irqfd if the device interrupt is pending. Ideally this could be solved with some additional locking; the igate mutex serializes the ioctl and config space accesses, and the interrupt handler is unregistered relative to the trigger, but the irqfd path runs asynchronous to those. The igate mutex cannot be acquired from the atomic context of the eventfd wake function. Disabling the irqfd relative to the eventfd registration is potentially incompatible with existing userspace. As a result, the solution implemented here moves configuration of the INTx interrupt handler to track the lifetime of the INTx context object and irq_type configuration, rather than regi | CVSS3: 5.5 | 0% Низкий | больше 2 лет назад | |
CVE-2024-26812 vfio/pci: Create persistent INTx handler | CVSS3: 5.5 | 0% Низкий | 9 месяцев назад | |
CVE-2024-26812 In the Linux kernel, the following vulnerability has been resolved: v ... | CVSS3: 5.5 | 0% Низкий | больше 2 лет назад | |
GHSA-p8g6-7v7w-4whg In the Linux kernel, the following vulnerability has been resolved: vfio/pci: Create persistent INTx handler A vulnerability exists where the eventfd for INTx signaling can be deconfigured, which unregisters the IRQ handler but still allows eventfds to be signaled with a NULL context through the SET_IRQS ioctl or through unmask irqfd if the device interrupt is pending. Ideally this could be solved with some additional locking; the igate mutex serializes the ioctl and config space accesses, and the interrupt handler is unregistered relative to the trigger, but the irqfd path runs asynchronous to those. The igate mutex cannot be acquired from the atomic context of the eventfd wake function. Disabling the irqfd relative to the eventfd registration is potentially incompatible with existing userspace. As a result, the solution implemented here moves configuration of the INTx interrupt handler to track the lifetime of the INTx context object and irq_type configuration, rather than r... | CVSS3: 5.5 | 0% Низкий | больше 2 лет назад | |
BDU:2024-09205 Уязвимость компонента vfio ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании(DoS) | CVSS3: 5.5 | 0% Низкий | больше 2 лет назад | |
ROS-20241024-02 Множественные уязвимости kernel-lt | CVSS3: 8.8 | около 2 лет назад | ||
SUSE-SU-2024:3189-1 Security update for the Linux Kernel | около 2 лет назад | |||
SUSE-SU-2024:3252-1 Security update for the Linux Kernel | около 2 лет назад | |||
SUSE-SU-2024:3251-1 Security update for the Linux Kernel | около 2 лет назад | |||
ALT-PU-2024-18366 ALT-PU-2024-18366: package `kernel-image-std-def` update to version 6.1.84-alt1 | CVSS3: 8.8 | больше 2 лет назад | ||
ALT-PU-2024-18059 ALT-PU-2024-18059: package `kernel-image-un-def` update to version 6.1.84-alt1 | CVSS3: 8.8 | больше 2 лет назад | ||
ALT-PU-2024-18470 ALT-PU-2024-18470: package `kernel-image-un-def` update to version 6.6.24-alt1 | CVSS3: 8.8 | больше 2 лет назад | ||
ALT-PU-2024-18142 ALT-PU-2024-18142: package `kernel-image-6.8` update to version 6.8.3-alt1 | CVSS3: 8.8 | больше 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-18212 ALT-PU-2024-18212: package `kernel-image-pine` update to version 6.6.27-alt1 | CVSS3: 9.8 | больше 2 лет назад | ||
SUSE-SU-2024:3195-1 Security update for the Linux Kernel | около 2 лет назад |
Уязвимостей на страницу