Поиск уязвимостей
Количество 21
Количество 21
CVE-2025-71127
In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211: Discard Beacon frames to non-broadcast address Beacon frames are required to be sent to the broadcast address, see IEEE Std 802.11-2020, 11.1.3.1 ("The Address 1 field of the Beacon .. frame shall be set to the broadcast address"). A unicast Beacon frame might be used as a targeted attack to get one of the associated STAs to do something (e.g., using CSA to move it to another channel). As such, it is better have strict filtering for this on the received side and discard all Beacon frames that are sent to an unexpected address. This is even more important for cases where beacon protection is used. The current implementation in mac80211 is correctly discarding unicast Beacon frames if the Protected Frame bit in the Frame Control field is set to 0. However, if that bit is set to 1, the logic used for checking for configured BIGTK(s) does not actually work. If the driver does not have logic for dropping ...
CVE-2025-71127
In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211: Discard Beacon frames to non-broadcast address Beacon frames are required to be sent to the broadcast address, see IEEE Std 802.11-2020, 11.1.3.1 ("The Address 1 field of the Beacon .. frame shall be set to the broadcast address"). A unicast Beacon frame might be used as a targeted attack to get one of the associated STAs to do something (e.g., using CSA to move it to another channel). As such, it is better have strict filtering for this on the received side and discard all Beacon frames that are sent to an unexpected address. This is even more important for cases where beacon protection is used. The current implementation in mac80211 is correctly discarding unicast Beacon frames if the Protected Frame bit in the Frame Control field is set to 0. However, if that bit is set to 1, the logic used for checking for configured BIGTK(s) does not actually work. If the driver does not have logic for dropping ...
CVE-2025-71127
In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211: Discard Beacon frames to non-broadcast address Beacon frames are required to be sent to the broadcast address, see IEEE Std 802.11-2020, 11.1.3.1 ("The Address 1 field of the Beacon .. frame shall be set to the broadcast address"). A unicast Beacon frame might be used as a targeted attack to get one of the associated STAs to do something (e.g., using CSA to move it to another channel). As such, it is better have strict filtering for this on the received side and discard all Beacon frames that are sent to an unexpected address. This is even more important for cases where beacon protection is used. The current implementation in mac80211 is correctly discarding unicast Beacon frames if the Protected Frame bit in the Frame Control field is set to 0. However, if that bit is set to 1, the logic used for checking for configured BIGTK(s) does not actually work. If the driver does not have logic for dropping
CVE-2025-71127
wifi: mac80211: Discard Beacon frames to non-broadcast address
CVE-2025-71127
In the Linux kernel, the following vulnerability has been resolved: w ...
GHSA-xmv5-397p-vvvx
In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211: Discard Beacon frames to non-broadcast address Beacon frames are required to be sent to the broadcast address, see IEEE Std 802.11-2020, 11.1.3.1 ("The Address 1 field of the Beacon .. frame shall be set to the broadcast address"). A unicast Beacon frame might be used as a targeted attack to get one of the associated STAs to do something (e.g., using CSA to move it to another channel). As such, it is better have strict filtering for this on the received side and discard all Beacon frames that are sent to an unexpected address. This is even more important for cases where beacon protection is used. The current implementation in mac80211 is correctly discarding unicast Beacon frames if the Protected Frame bit in the Frame Control field is set to 0. However, if that bit is set to 1, the logic used for checking for configured BIGTK(s) does not actually work. If the driver does not have logic for droppi...
BDU:2026-11504
Уязвимость компонента mac80211/rx.c ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
ROS-20260929-80-0230
Уязвимость kernel-lt
ROS-20260929-73-0197
Уязвимость kernel-lt
RLSA-2026:67468
Important: kernel security update
ELSA-2026-67468-0
ELSA-2026-67468-0: kernel security update (IMPORTANT)
ELSA-2026-50144
ELSA-2026-50144: Unbreakable Enterprise kernel security update (IMPORTANT)
ALT-PU-2026-3159
ALT-PU-2026-3159: package `kernel-image-rt` update to version 5.10.248-alt1.rt143
ALT-PU-2026-2816
ALT-PU-2026-2816: package `kernel-image-std-def` update to version 5.10.248-alt1
ALT-PU-2026-3819
ALT-PU-2026-3819: package `kernel-image-un-def` update to version 6.1.160-alt1
ALT-PU-2026-3823
ALT-PU-2026-3823: package `kernel-image-rt` update to version 6.12.65-alt1
ALT-PU-2026-3822
ALT-PU-2026-3822: package `kernel-image-6.12` update to version 6.12.65-alt1
ELSA-2026-50145
ELSA-2026-50145: Unbreakable Enterprise kernel security update (IMPORTANT)
ALT-PU-2026-6044
ALT-PU-2026-6044: package `kernel-image-rpi-un` update to version 6.12.79-alt1
ALT-PU-2026-1529
ALT-PU-2026-1529: package `kernel-image-pine` update to version 6.12.66-alt1
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
CVE-2025-71127 In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211: Discard Beacon frames to non-broadcast address Beacon frames are required to be sent to the broadcast address, see IEEE Std 802.11-2020, 11.1.3.1 ("The Address 1 field of the Beacon .. frame shall be set to the broadcast address"). A unicast Beacon frame might be used as a targeted attack to get one of the associated STAs to do something (e.g., using CSA to move it to another channel). As such, it is better have strict filtering for this on the received side and discard all Beacon frames that are sent to an unexpected address. This is even more important for cases where beacon protection is used. The current implementation in mac80211 is correctly discarding unicast Beacon frames if the Protected Frame bit in the Frame Control field is set to 0. However, if that bit is set to 1, the logic used for checking for configured BIGTK(s) does not actually work. If the driver does not have logic for dropping ... | CVSS3: 5.5 | 0% Низкий | 10 месяцев назад | |
CVE-2025-71127 In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211: Discard Beacon frames to non-broadcast address Beacon frames are required to be sent to the broadcast address, see IEEE Std 802.11-2020, 11.1.3.1 ("The Address 1 field of the Beacon .. frame shall be set to the broadcast address"). A unicast Beacon frame might be used as a targeted attack to get one of the associated STAs to do something (e.g., using CSA to move it to another channel). As such, it is better have strict filtering for this on the received side and discard all Beacon frames that are sent to an unexpected address. This is even more important for cases where beacon protection is used. The current implementation in mac80211 is correctly discarding unicast Beacon frames if the Protected Frame bit in the Frame Control field is set to 0. However, if that bit is set to 1, the logic used for checking for configured BIGTK(s) does not actually work. If the driver does not have logic for dropping ... | CVSS3: 6.3 | 0% Низкий | 10 месяцев назад | |
CVE-2025-71127 In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211: Discard Beacon frames to non-broadcast address Beacon frames are required to be sent to the broadcast address, see IEEE Std 802.11-2020, 11.1.3.1 ("The Address 1 field of the Beacon .. frame shall be set to the broadcast address"). A unicast Beacon frame might be used as a targeted attack to get one of the associated STAs to do something (e.g., using CSA to move it to another channel). As such, it is better have strict filtering for this on the received side and discard all Beacon frames that are sent to an unexpected address. This is even more important for cases where beacon protection is used. The current implementation in mac80211 is correctly discarding unicast Beacon frames if the Protected Frame bit in the Frame Control field is set to 0. However, if that bit is set to 1, the logic used for checking for configured BIGTK(s) does not actually work. If the driver does not have logic for dropping | CVSS3: 5.5 | 0% Низкий | 10 месяцев назад | |
CVE-2025-71127 wifi: mac80211: Discard Beacon frames to non-broadcast address | CVSS3: 5.5 | 0% Низкий | 10 месяцев назад | |
CVE-2025-71127 In the Linux kernel, the following vulnerability has been resolved: w ... | CVSS3: 5.5 | 0% Низкий | 10 месяцев назад | |
GHSA-xmv5-397p-vvvx In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211: Discard Beacon frames to non-broadcast address Beacon frames are required to be sent to the broadcast address, see IEEE Std 802.11-2020, 11.1.3.1 ("The Address 1 field of the Beacon .. frame shall be set to the broadcast address"). A unicast Beacon frame might be used as a targeted attack to get one of the associated STAs to do something (e.g., using CSA to move it to another channel). As such, it is better have strict filtering for this on the received side and discard all Beacon frames that are sent to an unexpected address. This is even more important for cases where beacon protection is used. The current implementation in mac80211 is correctly discarding unicast Beacon frames if the Protected Frame bit in the Frame Control field is set to 0. However, if that bit is set to 1, the logic used for checking for configured BIGTK(s) does not actually work. If the driver does not have logic for droppi... | CVSS3: 5.5 | 0% Низкий | 10 месяцев назад | |
BDU:2026-11504 Уязвимость компонента mac80211/rx.c ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании | CVSS3: 5.5 | 0% Низкий | 11 месяцев назад | |
ROS-20260929-80-0230 Уязвимость kernel-lt | CVSS3: 5.5 | 0% Низкий | около 1 месяца назад | |
ROS-20260929-73-0197 Уязвимость kernel-lt | CVSS3: 5.5 | 0% Низкий | около 1 месяца назад | |
RLSA-2026:67468 Important: kernel security update | около 2 месяцев назад | |||
ELSA-2026-67468-0 ELSA-2026-67468-0: kernel security update (IMPORTANT) | около 2 месяцев назад | |||
ELSA-2026-50144 ELSA-2026-50144: Unbreakable Enterprise kernel security update (IMPORTANT) | 8 месяцев назад | |||
ALT-PU-2026-3159 ALT-PU-2026-3159: package `kernel-image-rt` update to version 5.10.248-alt1.rt143 | CVSS3: 8.2 | 9 месяцев назад | ||
ALT-PU-2026-2816 ALT-PU-2026-2816: package `kernel-image-std-def` update to version 5.10.248-alt1 | CVSS3: 8.2 | 9 месяцев назад | ||
ALT-PU-2026-3819 ALT-PU-2026-3819: package `kernel-image-un-def` update to version 6.1.160-alt1 | CVSS3: 8.2 | 10 месяцев назад | ||
ALT-PU-2026-3823 ALT-PU-2026-3823: package `kernel-image-rt` update to version 6.12.65-alt1 | CVSS3: 8.2 | 10 месяцев назад | ||
ALT-PU-2026-3822 ALT-PU-2026-3822: package `kernel-image-6.12` update to version 6.12.65-alt1 | CVSS3: 8.2 | 10 месяцев назад | ||
ELSA-2026-50145 ELSA-2026-50145: Unbreakable Enterprise kernel security update (IMPORTANT) | 8 месяцев назад | |||
ALT-PU-2026-6044 ALT-PU-2026-6044: package `kernel-image-rpi-un` update to version 6.12.79-alt1 | CVSS3: 9.8 | 7 месяцев назад | ||
ALT-PU-2026-1529 ALT-PU-2026-1529: package `kernel-image-pine` update to version 6.12.66-alt1 | CVSS3: 9.8 | 10 месяцев назад |
Уязвимостей на страницу