Поиск уязвимостей
Количество 25
Количество 25
CVE-2024-26897
In the Linux kernel, the following vulnerability has been resolved: wifi: ath9k: delay all of ath9k_wmi_event_tasklet() until init is complete The ath9k_wmi_event_tasklet() used in ath9k_htc assumes that all the data structures have been fully initialised by the time it runs. However, because of the order in which things are initialised, this is not guaranteed to be the case, because the device is exposed to the USB subsystem before the ath9k driver initialisation is completed. We already committed a partial fix for this in commit: 8b3046abc99e ("ath9k_htc: fix NULL pointer dereference at ath9k_htc_tx_get_packet()") However, that commit only aborted the WMI_TXSTATUS_EVENTID command in the event tasklet, pairing it with an "initialisation complete" bit in the TX struct. It seems syzbot managed to trigger the race for one of the other commands as well, so let's just move the existing synchronisation bit to cover the whole tasklet (setting it at the end of ath9k_htc_probe_device() inst...
CVE-2024-26897
In the Linux kernel, the following vulnerability has been resolved: wifi: ath9k: delay all of ath9k_wmi_event_tasklet() until init is complete The ath9k_wmi_event_tasklet() used in ath9k_htc assumes that all the data structures have been fully initialised by the time it runs. However, because of the order in which things are initialised, this is not guaranteed to be the case, because the device is exposed to the USB subsystem before the ath9k driver initialisation is completed. We already committed a partial fix for this in commit: 8b3046abc99e ("ath9k_htc: fix NULL pointer dereference at ath9k_htc_tx_get_packet()") However, that commit only aborted the WMI_TXSTATUS_EVENTID command in the event tasklet, pairing it with an "initialisation complete" bit in the TX struct. It seems syzbot managed to trigger the race for one of the other commands as well, so let's just move the existing synchronisation bit to cover the whole tasklet (setting it at the end of ath9k_htc_probe_device() inst...
CVE-2024-26897
In the Linux kernel, the following vulnerability has been resolved: wifi: ath9k: delay all of ath9k_wmi_event_tasklet() until init is complete The ath9k_wmi_event_tasklet() used in ath9k_htc assumes that all the data structures have been fully initialised by the time it runs. However, because of the order in which things are initialised, this is not guaranteed to be the case, because the device is exposed to the USB subsystem before the ath9k driver initialisation is completed. We already committed a partial fix for this in commit: 8b3046abc99e ("ath9k_htc: fix NULL pointer dereference at ath9k_htc_tx_get_packet()") However, that commit only aborted the WMI_TXSTATUS_EVENTID command in the event tasklet, pairing it with an "initialisation complete" bit in the TX struct. It seems syzbot managed to trigger the race for one of the other commands as well, so let's just move the existing synchronisation bit to cover the whole tasklet (setting it at the end of ath9k_htc_probe_device() ins
CVE-2024-26897
In the Linux kernel, the following vulnerability has been resolved: w ...
GHSA-96gr-7mgw-2637
In the Linux kernel, the following vulnerability has been resolved: wifi: ath9k: delay all of ath9k_wmi_event_tasklet() until init is complete The ath9k_wmi_event_tasklet() used in ath9k_htc assumes that all the data structures have been fully initialised by the time it runs. However, because of the order in which things are initialised, this is not guaranteed to be the case, because the device is exposed to the USB subsystem before the ath9k driver initialisation is completed. We already committed a partial fix for this in commit: 8b3046abc99e ("ath9k_htc: fix NULL pointer dereference at ath9k_htc_tx_get_packet()") However, that commit only aborted the WMI_TXSTATUS_EVENTID command in the event tasklet, pairing it with an "initialisation complete" bit in the TX struct. It seems syzbot managed to trigger the race for one of the other commands as well, so let's just move the existing synchronisation bit to cover the whole tasklet (setting it at the end of ath9k_htc_probe_device() ...
BDU:2026-01440
Уязвимость команды WMI_TXSTATUS_EVENTID ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
ROS-20241028-03
Множественные уязвимости kernel-lt
RLSA-2024:5363
Important: kernel security update
ELSA-2024-5363
ELSA-2024-5363: kernel security update (IMPORTANT)
RLSA-2024:3618
Moderate: kernel update
ELSA-2024-3618
ELSA-2024-3618: kernel update (MODERATE)
ALT-PU-2024-18365
ALT-PU-2024-18365: package `kernel-image-std-def` update to version 6.1.83-alt1
ALT-PU-2024-18257
ALT-PU-2024-18257: package `kernel-image-rt` update to version 6.1.83-alt1.rt28
ALT-PU-2024-18058
ALT-PU-2024-18058: package `kernel-image-un-def` update to version 6.1.83-alt1
SUSE-SU-2024:1644-1
Security update for the Linux Kernel
SUSE-SU-2024:1659-1
Security update for the Linux Kernel
SUSE-SU-2024:1663-1
Security update for the Linux Kernel
ALT-PU-2024-18469
ALT-PU-2024-18469: package `kernel-image-un-def` update to version 6.6.23-alt1
ALT-PU-2024-18211
ALT-PU-2024-18211: package `kernel-image-pine` update to version 6.6.23-alt1
ALT-PU-2024-18141
ALT-PU-2024-18141: package `kernel-image-6.8` update to version 6.8.2-alt1
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
CVE-2024-26897 In the Linux kernel, the following vulnerability has been resolved: wifi: ath9k: delay all of ath9k_wmi_event_tasklet() until init is complete The ath9k_wmi_event_tasklet() used in ath9k_htc assumes that all the data structures have been fully initialised by the time it runs. However, because of the order in which things are initialised, this is not guaranteed to be the case, because the device is exposed to the USB subsystem before the ath9k driver initialisation is completed. We already committed a partial fix for this in commit: 8b3046abc99e ("ath9k_htc: fix NULL pointer dereference at ath9k_htc_tx_get_packet()") However, that commit only aborted the WMI_TXSTATUS_EVENTID command in the event tasklet, pairing it with an "initialisation complete" bit in the TX struct. It seems syzbot managed to trigger the race for one of the other commands as well, so let's just move the existing synchronisation bit to cover the whole tasklet (setting it at the end of ath9k_htc_probe_device() inst... | CVSS3: 4.7 | 0% Низкий | больше 2 лет назад | |
CVE-2024-26897 In the Linux kernel, the following vulnerability has been resolved: wifi: ath9k: delay all of ath9k_wmi_event_tasklet() until init is complete The ath9k_wmi_event_tasklet() used in ath9k_htc assumes that all the data structures have been fully initialised by the time it runs. However, because of the order in which things are initialised, this is not guaranteed to be the case, because the device is exposed to the USB subsystem before the ath9k driver initialisation is completed. We already committed a partial fix for this in commit: 8b3046abc99e ("ath9k_htc: fix NULL pointer dereference at ath9k_htc_tx_get_packet()") However, that commit only aborted the WMI_TXSTATUS_EVENTID command in the event tasklet, pairing it with an "initialisation complete" bit in the TX struct. It seems syzbot managed to trigger the race for one of the other commands as well, so let's just move the existing synchronisation bit to cover the whole tasklet (setting it at the end of ath9k_htc_probe_device() inst... | CVSS3: 4.1 | 0% Низкий | больше 2 лет назад | |
CVE-2024-26897 In the Linux kernel, the following vulnerability has been resolved: wifi: ath9k: delay all of ath9k_wmi_event_tasklet() until init is complete The ath9k_wmi_event_tasklet() used in ath9k_htc assumes that all the data structures have been fully initialised by the time it runs. However, because of the order in which things are initialised, this is not guaranteed to be the case, because the device is exposed to the USB subsystem before the ath9k driver initialisation is completed. We already committed a partial fix for this in commit: 8b3046abc99e ("ath9k_htc: fix NULL pointer dereference at ath9k_htc_tx_get_packet()") However, that commit only aborted the WMI_TXSTATUS_EVENTID command in the event tasklet, pairing it with an "initialisation complete" bit in the TX struct. It seems syzbot managed to trigger the race for one of the other commands as well, so let's just move the existing synchronisation bit to cover the whole tasklet (setting it at the end of ath9k_htc_probe_device() ins | CVSS3: 4.7 | 0% Низкий | больше 2 лет назад | |
CVE-2024-26897 In the Linux kernel, the following vulnerability has been resolved: w ... | CVSS3: 4.7 | 0% Низкий | больше 2 лет назад | |
GHSA-96gr-7mgw-2637 In the Linux kernel, the following vulnerability has been resolved: wifi: ath9k: delay all of ath9k_wmi_event_tasklet() until init is complete The ath9k_wmi_event_tasklet() used in ath9k_htc assumes that all the data structures have been fully initialised by the time it runs. However, because of the order in which things are initialised, this is not guaranteed to be the case, because the device is exposed to the USB subsystem before the ath9k driver initialisation is completed. We already committed a partial fix for this in commit: 8b3046abc99e ("ath9k_htc: fix NULL pointer dereference at ath9k_htc_tx_get_packet()") However, that commit only aborted the WMI_TXSTATUS_EVENTID command in the event tasklet, pairing it with an "initialisation complete" bit in the TX struct. It seems syzbot managed to trigger the race for one of the other commands as well, so let's just move the existing synchronisation bit to cover the whole tasklet (setting it at the end of ath9k_htc_probe_device() ... | CVSS3: 4.7 | 0% Низкий | больше 2 лет назад | |
BDU:2026-01440 Уязвимость команды WMI_TXSTATUS_EVENTID ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании | CVSS3: 5.5 | 0% Низкий | почти 3 года назад | |
ROS-20241028-03 Множественные уязвимости kernel-lt | CVSS3: 8.8 | около 2 лет назад | ||
RLSA-2024:5363 Important: kernel security update | около 2 лет назад | |||
ELSA-2024-5363 ELSA-2024-5363: kernel security update (IMPORTANT) | около 2 лет назад | |||
RLSA-2024:3618 Moderate: kernel update | больше 2 лет назад | |||
ELSA-2024-3618 ELSA-2024-3618: kernel update (MODERATE) | больше 2 лет назад | |||
ALT-PU-2024-18365 ALT-PU-2024-18365: package `kernel-image-std-def` update to version 6.1.83-alt1 | CVSS3: 9.1 | больше 2 лет назад | ||
ALT-PU-2024-18257 ALT-PU-2024-18257: package `kernel-image-rt` update to version 6.1.83-alt1.rt28 | CVSS3: 9.1 | больше 2 лет назад | ||
ALT-PU-2024-18058 ALT-PU-2024-18058: package `kernel-image-un-def` update to version 6.1.83-alt1 | CVSS3: 9.1 | больше 2 лет назад | ||
SUSE-SU-2024:1644-1 Security update for the Linux Kernel | больше 2 лет назад | |||
SUSE-SU-2024:1659-1 Security update for the Linux Kernel | больше 2 лет назад | |||
SUSE-SU-2024:1663-1 Security update for the Linux Kernel | больше 2 лет назад | |||
ALT-PU-2024-18469 ALT-PU-2024-18469: package `kernel-image-un-def` update to version 6.6.23-alt1 | CVSS3: 9.1 | больше 2 лет назад | ||
ALT-PU-2024-18211 ALT-PU-2024-18211: package `kernel-image-pine` update to version 6.6.23-alt1 | CVSS3: 9.1 | больше 2 лет назад | ||
ALT-PU-2024-18141 ALT-PU-2024-18141: package `kernel-image-6.8` update to version 6.8.2-alt1 | CVSS3: 9.1 | больше 2 лет назад |
Уязвимостей на страницу