Поиск уязвимостей
Количество 19
Количество 19
CVE-2022-48868
In the Linux kernel, the following vulnerability has been resolved: dmaengine: idxd: Let probe fail when workqueue cannot be enabled The workqueue is enabled when the appropriate driver is loaded and disabled when the driver is removed. When the driver is removed it assumes that the workqueue was enabled successfully and proceeds to free allocations made during workqueue enabling. Failure during workqueue enabling does not prevent the driver from being loaded. This is because the error path within drv_enable_wq() returns success unless a second failure is encountered during the error path. By returning success it is possible to load the driver even if the workqueue cannot be enabled and allocations that do not exist are attempted to be freed during driver remove. Some examples of problematic flows: (a) idxd_dmaengine_drv_probe() -> drv_enable_wq() -> idxd_wq_request_irq(): In above flow, if idxd_wq_request_irq() fails then idxd_wq_unmap_portal() is called on error exit path, but drv...
CVE-2022-48868
In the Linux kernel, the following vulnerability has been resolved: dmaengine: idxd: Let probe fail when workqueue cannot be enabled The workqueue is enabled when the appropriate driver is loaded and disabled when the driver is removed. When the driver is removed it assumes that the workqueue was enabled successfully and proceeds to free allocations made during workqueue enabling. Failure during workqueue enabling does not prevent the driver from being loaded. This is because the error path within drv_enable_wq() returns success unless a second failure is encountered during the error path. By returning success it is possible to load the driver even if the workqueue cannot be enabled and allocations that do not exist are attempted to be freed during driver remove. Some examples of problematic flows: (a) idxd_dmaengine_drv_probe() -> drv_enable_wq() -> idxd_wq_request_irq(): In above flow, if idxd_wq_request_irq() fails then idxd_wq_unmap_portal() is called on error exit path, but drv...
CVE-2022-48868
In the Linux kernel, the following vulnerability has been resolved: dmaengine: idxd: Let probe fail when workqueue cannot be enabled The workqueue is enabled when the appropriate driver is loaded and disabled when the driver is removed. When the driver is removed it assumes that the workqueue was enabled successfully and proceeds to free allocations made during workqueue enabling. Failure during workqueue enabling does not prevent the driver from being loaded. This is because the error path within drv_enable_wq() returns success unless a second failure is encountered during the error path. By returning success it is possible to load the driver even if the workqueue cannot be enabled and allocations that do not exist are attempted to be freed during driver remove. Some examples of problematic flows: (a) idxd_dmaengine_drv_probe() -> drv_enable_wq() -> idxd_wq_request_irq(): In above flow, if idxd_wq_request_irq() fails then idxd_wq_unmap_portal() is called on error exit path, bu
CVE-2022-48868
In the Linux kernel, the following vulnerability has been resolved: d ...
GHSA-35cf-498m-vj28
In the Linux kernel, the following vulnerability has been resolved: dmaengine: idxd: Let probe fail when workqueue cannot be enabled The workqueue is enabled when the appropriate driver is loaded and disabled when the driver is removed. When the driver is removed it assumes that the workqueue was enabled successfully and proceeds to free allocations made during workqueue enabling. Failure during workqueue enabling does not prevent the driver from being loaded. This is because the error path within drv_enable_wq() returns success unless a second failure is encountered during the error path. By returning success it is possible to load the driver even if the workqueue cannot be enabled and allocations that do not exist are attempted to be freed during driver remove. Some examples of problematic flows: (a) idxd_dmaengine_drv_probe() -> drv_enable_wq() -> idxd_wq_request_irq(): In above flow, if idxd_wq_request_irq() fails then idxd_wq_unmap_portal() is called on error exit path,...
BDU:2024-06856
Уязвимость компонента idxd ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
ROS-20240905-04
Множественные уязвимости kernel-lt
ALT-PU-2023-8786
ALT-PU-2023-8786: package `kernel-image-std-def` update to version 5.15.90-alt1
ALT-PU-2023-8555
ALT-PU-2023-8555: package `kernel-image-un-def` update to version 5.15.90-alt1
ALT-PU-2023-1124
ALT-PU-2023-1124: package `kernel-image-un-def` update to version 6.1.8-alt1
SUSE-SU-2024:3408-1
Security update for the Linux Kernel
ALT-PU-2023-1126
ALT-PU-2023-1126: package `kernel-image-mp` update to version 6.1.8-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-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
ALT-PU-2024-4843
ALT-PU-2024-4843: package `kernel-image-rpi-un` update to version 6.1.77-alt1
ALT-PU-2024-4263
ALT-PU-2024-4263: package `kernel-image-rpi-un` update to version 6.1.77-alt1
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
CVE-2022-48868 In the Linux kernel, the following vulnerability has been resolved: dmaengine: idxd: Let probe fail when workqueue cannot be enabled The workqueue is enabled when the appropriate driver is loaded and disabled when the driver is removed. When the driver is removed it assumes that the workqueue was enabled successfully and proceeds to free allocations made during workqueue enabling. Failure during workqueue enabling does not prevent the driver from being loaded. This is because the error path within drv_enable_wq() returns success unless a second failure is encountered during the error path. By returning success it is possible to load the driver even if the workqueue cannot be enabled and allocations that do not exist are attempted to be freed during driver remove. Some examples of problematic flows: (a) idxd_dmaengine_drv_probe() -> drv_enable_wq() -> idxd_wq_request_irq(): In above flow, if idxd_wq_request_irq() fails then idxd_wq_unmap_portal() is called on error exit path, but drv... | CVSS3: 5.5 | 0% Низкий | около 2 лет назад | |
CVE-2022-48868 In the Linux kernel, the following vulnerability has been resolved: dmaengine: idxd: Let probe fail when workqueue cannot be enabled The workqueue is enabled when the appropriate driver is loaded and disabled when the driver is removed. When the driver is removed it assumes that the workqueue was enabled successfully and proceeds to free allocations made during workqueue enabling. Failure during workqueue enabling does not prevent the driver from being loaded. This is because the error path within drv_enable_wq() returns success unless a second failure is encountered during the error path. By returning success it is possible to load the driver even if the workqueue cannot be enabled and allocations that do not exist are attempted to be freed during driver remove. Some examples of problematic flows: (a) idxd_dmaengine_drv_probe() -> drv_enable_wq() -> idxd_wq_request_irq(): In above flow, if idxd_wq_request_irq() fails then idxd_wq_unmap_portal() is called on error exit path, but drv... | CVSS3: 5.5 | 0% Низкий | около 2 лет назад | |
CVE-2022-48868 In the Linux kernel, the following vulnerability has been resolved: dmaengine: idxd: Let probe fail when workqueue cannot be enabled The workqueue is enabled when the appropriate driver is loaded and disabled when the driver is removed. When the driver is removed it assumes that the workqueue was enabled successfully and proceeds to free allocations made during workqueue enabling. Failure during workqueue enabling does not prevent the driver from being loaded. This is because the error path within drv_enable_wq() returns success unless a second failure is encountered during the error path. By returning success it is possible to load the driver even if the workqueue cannot be enabled and allocations that do not exist are attempted to be freed during driver remove. Some examples of problematic flows: (a) idxd_dmaengine_drv_probe() -> drv_enable_wq() -> idxd_wq_request_irq(): In above flow, if idxd_wq_request_irq() fails then idxd_wq_unmap_portal() is called on error exit path, bu | CVSS3: 5.5 | 0% Низкий | около 2 лет назад | |
CVE-2022-48868 In the Linux kernel, the following vulnerability has been resolved: d ... | CVSS3: 5.5 | 0% Низкий | около 2 лет назад | |
GHSA-35cf-498m-vj28 In the Linux kernel, the following vulnerability has been resolved: dmaengine: idxd: Let probe fail when workqueue cannot be enabled The workqueue is enabled when the appropriate driver is loaded and disabled when the driver is removed. When the driver is removed it assumes that the workqueue was enabled successfully and proceeds to free allocations made during workqueue enabling. Failure during workqueue enabling does not prevent the driver from being loaded. This is because the error path within drv_enable_wq() returns success unless a second failure is encountered during the error path. By returning success it is possible to load the driver even if the workqueue cannot be enabled and allocations that do not exist are attempted to be freed during driver remove. Some examples of problematic flows: (a) idxd_dmaengine_drv_probe() -> drv_enable_wq() -> idxd_wq_request_irq(): In above flow, if idxd_wq_request_irq() fails then idxd_wq_unmap_portal() is called on error exit path,... | CVSS3: 5.5 | 0% Низкий | около 2 лет назад | |
BDU:2024-06856 Уязвимость компонента idxd ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании | CVSS3: 5.5 | 0% Низкий | почти 4 года назад | |
ROS-20240905-04 Множественные уязвимости kernel-lt | CVSS3: 7.8 | около 2 лет назад | ||
ALT-PU-2023-8786 ALT-PU-2023-8786: package `kernel-image-std-def` update to version 5.15.90-alt1 | CVSS3: 7.8 | почти 4 года назад | ||
ALT-PU-2023-8555 ALT-PU-2023-8555: package `kernel-image-un-def` update to version 5.15.90-alt1 | CVSS3: 7.8 | почти 4 года назад | ||
ALT-PU-2023-1124 ALT-PU-2023-1124: package `kernel-image-un-def` update to version 6.1.8-alt1 | CVSS3: 7.8 | почти 4 года назад | ||
SUSE-SU-2024:3408-1 Security update for the Linux Kernel | около 2 лет назад | |||
ALT-PU-2023-1126 ALT-PU-2023-1126: package `kernel-image-mp` update to version 6.1.8-alt1 | CVSS3: 7.8 | почти 4 года назад | ||
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-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 лет назад | ||
ALT-PU-2024-4843 ALT-PU-2024-4843: package `kernel-image-rpi-un` update to version 6.1.77-alt1 | CVSS3: 10 | больше 2 лет назад | ||
ALT-PU-2024-4263 ALT-PU-2024-4263: package `kernel-image-rpi-un` update to version 6.1.77-alt1 | CVSS3: 10 | больше 2 лет назад |
Уязвимостей на страницу