<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Sat, 03 Oct 2026 05:05:33 +0000</lastBuildDate>
    <item>
      <title>ALSA-2026:67468 — Important: kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/alsa-2026:67468</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; AlmaLinux:8: bpftool, AlmaLinux:8: kernel, AlmaLinux:8: kernel-abi-stablelists, AlmaLinux:8: kernel-core, AlmaLinux:8: kernel-cross-headers, AlmaLinux:8: kernel-debug, AlmaLinux:8: kernel-debug-core, AlmaLinux:8: kernel-debug-devel, AlmaLinux:8: kernel-debug-modules, AlmaLinux:8: kernel-debug-modules-extra and 15 more&lt;/p&gt;
&lt;p&gt;The kernel packages contain the Linux kernel, the core of any Linux operating system.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;* kernel: EDAC/bluefield: Fix potential integer overflow (CVE-2024-53161)
  * kernel: wifi: mac80211: Discard Beacon frames to non-broadcast address (CVE-2025-71127)
  * kernel: KVM: nSVM: Always use vmcb01 in VMLOAD/VMSAVE emulation (CVE-2026-43133)
  * kernel: net: qrtr: fix refcount saturation and potential UAF in qrtr_port_remove (CVE-2026-52947)
  * kernel: wifi: nl80211: reject oversized EMA RNR lists (CVE-2026-53182)
  * kernel: blk-cgroup: fix UAF in __blkcg_rstat_flush() (CVE-2026-63802)
  * kernel: scsi: scsi_transport_fc: Widen FPIN pname walker counter to u32 (CVE-2026-63889)
  * kernel: wifi: mac80211: capture fast-RX rate before mesh reuses skb-&amp;gt;cb (CVE-2026-64117)
  * kernel: Linux kernel: ath9k Wi-Fi driver use-after-free vulnerability leading to system crash (CVE-2026-68363)
  * kernel: dm-verity: fix buffer overflow in FEC calculation (CVE-2026-72098)
  * kernel: scsi: libiscsi_tcp: Bound SCSI Response data segment to the connection buffer (CVE-2026-74556)&lt;/p&gt;
&lt;p&gt;For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; AlmaLinux:8: bpftool, AlmaLinux:8: kernel, AlmaLinux:8: kernel-abi-stablelists, AlmaLinux:8: kernel-core, AlmaLinux:8: kernel-cross-headers, AlmaLinux:8: kernel-debug, AlmaLinux:8: kernel-debug-core, AlmaLinux:8: kernel-debug-devel, AlmaLinux:8: kernel-debug-modules, AlmaLinux:8: kernel-debug-modules-extra and 15 more&lt;/p&gt;
&lt;p&gt;The kernel packages contain the Linux kernel, the core of any Linux operating system.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;* kernel: EDAC/bluefield: Fix potential integer overflow (CVE-2024-53161)
  * kernel: wifi: mac80211: Discard Beacon frames to non-broadcast address (CVE-2025-71127)
  * kernel: KVM: nSVM: Always use vmcb01 in VMLOAD/VMSAVE emulation (CVE-2026-43133)
  * kernel: net: qrtr: fix refcount saturation and potential UAF in qrtr_port_remove (CVE-2026-52947)
  * kernel: wifi: nl80211: reject oversized EMA RNR lists (CVE-2026-53182)
  * kernel: blk-cgroup: fix UAF in __blkcg_rstat_flush() (CVE-2026-63802)
  * kernel: scsi: scsi_transport_fc: Widen FPIN pname walker counter to u32 (CVE-2026-63889)
  * kernel: wifi: mac80211: capture fast-RX rate before mesh reuses skb-&amp;gt;cb (CVE-2026-64117)
  * kernel: Linux kernel: ath9k Wi-Fi driver use-after-free vulnerability leading to system crash (CVE-2026-68363)
  * kernel: dm-verity: fix buffer overflow in FEC calculation (CVE-2026-72098)
  * kernel: scsi: libiscsi_tcp: Bound SCSI Response data segment to the connection buffer (CVE-2026-74556)&lt;/p&gt;
&lt;p&gt;For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/alsa-2026:67468</guid>
    </item>
    <item>
      <title>bdu:2026-11504</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-11504</link>
      <description>bdu:2026-11504</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-11504</guid>
    </item>
    <item>
      <title>BELL-CVE-2025-71127</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2025-71127</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2025-71127</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0166 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Elles permettent à un attaquant de provo…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-0166</link>
      <description>certfr-2026-avi-0166</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-0166</guid>
    </item>
    <item>
      <title>EUVD-2026-347551</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-347551</link>
      <description>EUVD-2026-347551</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-347551</guid>
    </item>
    <item>
      <title>fkie_cve-2025-71127</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-71127</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;wifi: mac80211: Discard Beacon frames to non-broadcast address&lt;/p&gt;
&lt;p&gt;Beacon frames are required to be sent to the broadcast address, see IEEE
Std 802.11-2020, 11.1.3.1 (&amp;#34;The Address 1 field of the Beacon .. frame
shall be set to the broadcast address&amp;#34;). 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.&lt;/p&gt;
&lt;p&gt;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 unicast Beacon frames with Protected Frame bit
1, these frames would be accepted in mac80211 processing as valid Beacon
frames even though they are not protected. This would allow beacon
protection to be bypassed. While the logic for checking beacon
protection could be extended to cover this corner case, a more generic
check for discard all Beacon frames based on A1=unicast address covers
this without needing additional changes.&lt;/p&gt;
&lt;p&gt;Address all these issues by dropping received Beacon frames if th…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;wifi: mac80211: Discard Beacon frames to non-broadcast address&lt;/p&gt;
&lt;p&gt;Beacon frames are required to be sent to the broadcast address, see IEEE
Std 802.11-2020, 11.1.3.1 (&amp;#34;The Address 1 field of the Beacon .. frame
shall be set to the broadcast address&amp;#34;). 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.&lt;/p&gt;
&lt;p&gt;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 unicast Beacon frames with Protected Frame bit
1, these frames would be accepted in mac80211 processing as valid Beacon
frames even though they are not protected. This would allow beacon
protection to be bypassed. While the logic for checking beacon
protection could be extended to cover this corner case, a more generic
check for discard all Beacon frames based on A1=unicast address covers
this without needing additional changes.&lt;/p&gt;
&lt;p&gt;Address all these issues by dropping received Beacon frames if th…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-71127</guid>
    </item>
    <item>
      <title>GHSA-xmv5-397p-vvvx</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-xmv5-397p-vvvx</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;wifi: mac80211: Discard Beacon frames to non-broadcast address&lt;/p&gt;
&lt;p&gt;Beacon frames are required to be sent to the broadcast address, see IEEE
Std 802.11-2020, 11.1.3.1 (&amp;#34;The Address 1 field of the Beacon .. frame
shall be set to the broadcast address&amp;#34;). 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.&lt;/p&gt;
&lt;p&gt;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 unicast Beacon frames with Protected Frame bit
1, these frames would be accepted in mac80211 processing as valid Beacon
frames even though they are not protected. This would allow beacon
protection to be bypassed. While the logic for checking beacon
protection could be extended to cover this corner case, a more generic
check for discard all Beacon frames based on A1=unicast address covers
this without needing additional changes.&lt;/p&gt;
&lt;p&gt;Address all these issues by dropping received Beacon frames if th…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;wifi: mac80211: Discard Beacon frames to non-broadcast address&lt;/p&gt;
&lt;p&gt;Beacon frames are required to be sent to the broadcast address, see IEEE
Std 802.11-2020, 11.1.3.1 (&amp;#34;The Address 1 field of the Beacon .. frame
shall be set to the broadcast address&amp;#34;). 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.&lt;/p&gt;
&lt;p&gt;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 unicast Beacon frames with Protected Frame bit
1, these frames would be accepted in mac80211 processing as valid Beacon
frames even though they are not protected. This would allow beacon
protection to be bypassed. While the logic for checking beacon
protection could be extended to cover this corner case, a more generic
check for discard all Beacon frames based on A1=unicast address covers
this without needing additional changes.&lt;/p&gt;
&lt;p&gt;Address all these issues by dropping received Beacon frames if th…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-xmv5-397p-vvvx</guid>
    </item>
    <item>
      <title>msrc_CVE-2025-71127 — wifi: mac80211: Discard Beacon frames to non-broadcast address</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2025-71127</link>
      <description>msrc_CVE-2025-71127</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2025-71127</guid>
    </item>
    <item>
      <title>RHSA-2026:67468 — Red Hat Security Advisory: kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2026:67468</link>
      <description>&lt;p&gt;kernel: EDAC/bluefield: Fix potential integer overflow kernel: wifi: mac80211: Discard Beacon frames to non-broadcast address kernel: KVM: nSVM: Always use vmcb01 in VMLOAD/VMSAVE emulation kernel: net: qrtr: fix refcount saturation and potential UAF in qrtr_port_remove kernel: wifi: nl80211: reject oversized EMA RNR lists kernel: blk-cgroup: fix UAF in __blkcg_rstat_flush() kernel: scsi: scsi_transport_fc: Widen FPIN pname walker counter to u32 kernel: wifi: mac80211: capture fast-RX rate before mesh reuses skb-&amp;gt;cb kernel: Linux kernel: ath9k Wi-Fi driver use-after-free vulnerability leading to system crash kernel: dm-verity: fix buffer overflow in FEC calculation kernel: scsi: libiscsi_tcp: Bound SCSI Response data segment to the connection buffer&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel: EDAC/bluefield: Fix potential integer overflow kernel: wifi: mac80211: Discard Beacon frames to non-broadcast address kernel: KVM: nSVM: Always use vmcb01 in VMLOAD/VMSAVE emulation kernel: net: qrtr: fix refcount saturation and potential UAF in qrtr_port_remove kernel: wifi: nl80211: reject oversized EMA RNR lists kernel: blk-cgroup: fix UAF in __blkcg_rstat_flush() kernel: scsi: scsi_transport_fc: Widen FPIN pname walker counter to u32 kernel: wifi: mac80211: capture fast-RX rate before mesh reuses skb-&amp;gt;cb kernel: Linux kernel: ath9k Wi-Fi driver use-after-free vulnerability leading to system crash kernel: dm-verity: fix buffer overflow in FEC calculation kernel: scsi: libiscsi_tcp: Bound SCSI Response data segment to the connection buffer&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2026:67468</guid>
    </item>
    <item>
      <title>RHSA-2026:67469 — Red Hat Security Advisory: kernel-rt security update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2026:67469</link>
      <description>&lt;p&gt;kernel: EDAC/bluefield: Fix potential integer overflow kernel: wifi: mac80211: Discard Beacon frames to non-broadcast address kernel: KVM: nSVM: Always use vmcb01 in VMLOAD/VMSAVE emulation kernel: net: qrtr: fix refcount saturation and potential UAF in qrtr_port_remove kernel: wifi: nl80211: reject oversized EMA RNR lists kernel: blk-cgroup: fix UAF in __blkcg_rstat_flush() kernel: scsi: scsi_transport_fc: Widen FPIN pname walker counter to u32 kernel: wifi: mac80211: capture fast-RX rate before mesh reuses skb-&amp;gt;cb kernel: net: qrtr: restrict socket creation to the initial network namespace kernel: Linux kernel: ath9k Wi-Fi driver use-after-free vulnerability leading to system crash kernel: dm-verity: fix buffer overflow in FEC calculation kernel: scsi: libiscsi_tcp: Bound SCSI Response data segment to the connection buffer&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel: EDAC/bluefield: Fix potential integer overflow kernel: wifi: mac80211: Discard Beacon frames to non-broadcast address kernel: KVM: nSVM: Always use vmcb01 in VMLOAD/VMSAVE emulation kernel: net: qrtr: fix refcount saturation and potential UAF in qrtr_port_remove kernel: wifi: nl80211: reject oversized EMA RNR lists kernel: blk-cgroup: fix UAF in __blkcg_rstat_flush() kernel: scsi: scsi_transport_fc: Widen FPIN pname walker counter to u32 kernel: wifi: mac80211: capture fast-RX rate before mesh reuses skb-&amp;gt;cb kernel: net: qrtr: restrict socket creation to the initial network namespace kernel: Linux kernel: ath9k Wi-Fi driver use-after-free vulnerability leading to system crash kernel: dm-verity: fix buffer overflow in FEC calculation kernel: scsi: libiscsi_tcp: Bound SCSI Response data segment to the connection buffer&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2026:67469</guid>
    </item>
    <item>
      <title>RLSA-2026:67468 — Important: kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/rlsa-2026:67468</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Rocky Linux:8: kernel&lt;/p&gt;
&lt;p&gt;The kernel packages contain the Linux kernel, the core of any Linux operating system.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;* kernel: EDAC/bluefield: Fix potential integer overflow (CVE-2024-53161)&lt;/p&gt;
&lt;p&gt;* kernel: wifi: mac80211: Discard Beacon frames to non-broadcast address (CVE-2025-71127)&lt;/p&gt;
&lt;p&gt;* kernel: KVM: nSVM: Always use vmcb01 in VMLOAD/VMSAVE emulation (CVE-2026-43133)&lt;/p&gt;
&lt;p&gt;* kernel: net: qrtr: fix refcount saturation and potential UAF in qrtr_port_remove (CVE-2026-52947)&lt;/p&gt;
&lt;p&gt;* kernel: wifi: nl80211: reject oversized EMA RNR lists (CVE-2026-53182)&lt;/p&gt;
&lt;p&gt;* kernel: blk-cgroup: fix UAF in __blkcg_rstat_flush() (CVE-2026-63802)&lt;/p&gt;
&lt;p&gt;* kernel: scsi: scsi_transport_fc: Widen FPIN pname walker counter to u32 (CVE-2026-63889)&lt;/p&gt;
&lt;p&gt;* kernel: wifi: mac80211: capture fast-RX rate before mesh reuses skb-&amp;gt;cb (CVE-2026-64117)&lt;/p&gt;
&lt;p&gt;* kernel: Linux kernel: ath9k Wi-Fi driver use-after-free vulnerability leading to system crash (CVE-2026-68363)&lt;/p&gt;
&lt;p&gt;* kernel: dm-verity: fix buffer overflow in FEC calculation (CVE-2026-72098)&lt;/p&gt;
&lt;p&gt;* kernel: scsi: libiscsi_tcp: Bound SCSI Response data segment to the connection buffer (CVE-2026-74556)&lt;/p&gt;
&lt;p&gt;For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Rocky Linux:8: kernel&lt;/p&gt;
&lt;p&gt;The kernel packages contain the Linux kernel, the core of any Linux operating system.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;* kernel: EDAC/bluefield: Fix potential integer overflow (CVE-2024-53161)&lt;/p&gt;
&lt;p&gt;* kernel: wifi: mac80211: Discard Beacon frames to non-broadcast address (CVE-2025-71127)&lt;/p&gt;
&lt;p&gt;* kernel: KVM: nSVM: Always use vmcb01 in VMLOAD/VMSAVE emulation (CVE-2026-43133)&lt;/p&gt;
&lt;p&gt;* kernel: net: qrtr: fix refcount saturation and potential UAF in qrtr_port_remove (CVE-2026-52947)&lt;/p&gt;
&lt;p&gt;* kernel: wifi: nl80211: reject oversized EMA RNR lists (CVE-2026-53182)&lt;/p&gt;
&lt;p&gt;* kernel: blk-cgroup: fix UAF in __blkcg_rstat_flush() (CVE-2026-63802)&lt;/p&gt;
&lt;p&gt;* kernel: scsi: scsi_transport_fc: Widen FPIN pname walker counter to u32 (CVE-2026-63889)&lt;/p&gt;
&lt;p&gt;* kernel: wifi: mac80211: capture fast-RX rate before mesh reuses skb-&amp;gt;cb (CVE-2026-64117)&lt;/p&gt;
&lt;p&gt;* kernel: Linux kernel: ath9k Wi-Fi driver use-after-free vulnerability leading to system crash (CVE-2026-68363)&lt;/p&gt;
&lt;p&gt;* kernel: dm-verity: fix buffer overflow in FEC calculation (CVE-2026-72098)&lt;/p&gt;
&lt;p&gt;* kernel: scsi: libiscsi_tcp: Bound SCSI Response data segment to the connection buffer (CVE-2026-74556)&lt;/p&gt;
&lt;p&gt;For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rlsa-2026:67468</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-71127</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-71127</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 178 more&lt;/p&gt;
&lt;p&gt;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 (&amp;#34;The Address 1 field of the Beacon .. frame shall be set to the broadcast address&amp;#34;). 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 unicast Beacon frames with Protected Frame bit 1, these frames would be accepted in mac80211 processing as valid Beacon frames even though they are not protected. This would allow beacon protection to be bypassed. While the logic for checking beacon protection could be extended to cover this corner case, a more generic check for discard all Beacon frames based on A1=unicast address covers this without needing additional changes. Address all these issues by dropping received Beacon frames if they a…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 178 more&lt;/p&gt;
&lt;p&gt;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 (&amp;#34;The Address 1 field of the Beacon .. frame shall be set to the broadcast address&amp;#34;). 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 unicast Beacon frames with Protected Frame bit 1, these frames would be accepted in mac80211 processing as valid Beacon frames even though they are not protected. This would allow beacon protection to be bypassed. While the logic for checking beacon protection could be extended to cover this corner case, a more generic check for discard all Beacon frames based on A1=unicast address covers this without needing additional changes. Address all these issues by dropping received Beacon frames if they a…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-71127</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-0119 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0119</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen um nicht näher spezifizierte Angriffe durchzuführen, die möglicherweise zu einer Denial-of-Service- Bedingung führen oder eine Speicherbeschädigung verursachen können.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen um nicht näher spezifizierte Angriffe durchzuführen, die möglicherweise zu einer Denial-of-Service- Bedingung führen oder eine Speicherbeschädigung verursachen können.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0119</guid>
    </item>
  </channel>
</rss>
