<?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://db.gcve.eu</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>Tue, 03 Nov 2026 04:30:13 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-98810</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-98810</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;wifi: mac80211: fix slab-out-of-bounds read in ieee80211_monitor_select_queue()&lt;/p&gt;
&lt;p&gt;ieee80211_monitor_select_queue() validates the skb length using skb-&amp;gt;len
before dereferencing pointers into skb-&amp;gt;data to access the 802.11 header.
However, skb-&amp;gt;len includes data in both the linear head buffer and
non-linear fragments/pages. When AF_PACKET sends a packet large enough to
become non-linear, the 802.11 header at skb-&amp;gt;data + len_rthdr may extend
past the linear head buffer even though skb-&amp;gt;len appears sufficient.&lt;/p&gt;
&lt;p&gt;This leads to a slab-out-of-bounds read when accessing hdr-&amp;gt;frame_control,
as the kernel reads beyond the allocated skb head buffer:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-out-of-bounds in ieee80211_monitor_select_queue+0x1ed/0x220&lt;/p&gt;
&lt;p&gt;syzbot has hit the same issues.&lt;/p&gt;
&lt;p&gt;Fix this by checking skb_headlen(skb) (which gives the length of the
linear data region) instead of skb-&amp;gt;len before dereferencing skb-&amp;gt;data
pointers. This ensures the required bytes are actually present in the
linear portion of the skb.&lt;/p&gt;
&lt;p&gt;Apply the same fix to ieee80211_validate_radiotap_len() which has the
same class of bug: it uses skb-&amp;gt;len to validate accesses to skb-&amp;gt;data,
and to the corresponding checks in ieee80211_monitor_start_xmit(): for
drivers advertising NETIF_F_SG the skb is not linearized before
ndo_start_xmit, so the 802.11 header can be read past the linear
buffer there as well.&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: fix slab-out-of-bounds read in ieee80211_monitor_select_queue()&lt;/p&gt;
&lt;p&gt;ieee80211_monitor_select_queue() validates the skb length using skb-&amp;gt;len
before dereferencing pointers into skb-&amp;gt;data to access the 802.11 header.
However, skb-&amp;gt;len includes data in both the linear head buffer and
non-linear fragments/pages. When AF_PACKET sends a packet large enough to
become non-linear, the 802.11 header at skb-&amp;gt;data + len_rthdr may extend
past the linear head buffer even though skb-&amp;gt;len appears sufficient.&lt;/p&gt;
&lt;p&gt;This leads to a slab-out-of-bounds read when accessing hdr-&amp;gt;frame_control,
as the kernel reads beyond the allocated skb head buffer:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-out-of-bounds in ieee80211_monitor_select_queue+0x1ed/0x220&lt;/p&gt;
&lt;p&gt;syzbot has hit the same issues.&lt;/p&gt;
&lt;p&gt;Fix this by checking skb_headlen(skb) (which gives the length of the
linear data region) instead of skb-&amp;gt;len before dereferencing skb-&amp;gt;data
pointers. This ensures the required bytes are actually present in the
linear portion of the skb.&lt;/p&gt;
&lt;p&gt;Apply the same fix to ieee80211_validate_radiotap_len() which has the
same class of bug: it uses skb-&amp;gt;len to validate accesses to skb-&amp;gt;data,
and to the corresponding checks in ieee80211_monitor_start_xmit(): for
drivers advertising NETIF_F_SG the skb is not linearized before
ndo_start_xmit, so the 802.11 header can be read past the linear
buffer there as well.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-98810</guid>
    </item>
    <item>
      <title>GHSA-8wg2-h9c3-q8hh</title>
      <link>https://db.gcve.eu/vuln/ghsa-8wg2-h9c3-q8hh</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;wifi: mac80211: fix slab-out-of-bounds read in ieee80211_monitor_select_queue()&lt;/p&gt;
&lt;p&gt;ieee80211_monitor_select_queue() validates the skb length using skb-&amp;gt;len
before dereferencing pointers into skb-&amp;gt;data to access the 802.11 header.
However, skb-&amp;gt;len includes data in both the linear head buffer and
non-linear fragments/pages. When AF_PACKET sends a packet large enough to
become non-linear, the 802.11 header at skb-&amp;gt;data + len_rthdr may extend
past the linear head buffer even though skb-&amp;gt;len appears sufficient.&lt;/p&gt;
&lt;p&gt;This leads to a slab-out-of-bounds read when accessing hdr-&amp;gt;frame_control,
as the kernel reads beyond the allocated skb head buffer:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-out-of-bounds in ieee80211_monitor_select_queue+0x1ed/0x220&lt;/p&gt;
&lt;p&gt;syzbot has hit the same issues.&lt;/p&gt;
&lt;p&gt;Fix this by checking skb_headlen(skb) (which gives the length of the
linear data region) instead of skb-&amp;gt;len before dereferencing skb-&amp;gt;data
pointers. This ensures the required bytes are actually present in the
linear portion of the skb.&lt;/p&gt;
&lt;p&gt;Apply the same fix to ieee80211_validate_radiotap_len() which has the
same class of bug: it uses skb-&amp;gt;len to validate accesses to skb-&amp;gt;data,
and to the corresponding checks in ieee80211_monitor_start_xmit(): for
drivers advertising NETIF_F_SG the skb is not linearized before
ndo_start_xmit, so the 802.11 header can be read past the linear
buffer there as well.&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: fix slab-out-of-bounds read in ieee80211_monitor_select_queue()&lt;/p&gt;
&lt;p&gt;ieee80211_monitor_select_queue() validates the skb length using skb-&amp;gt;len
before dereferencing pointers into skb-&amp;gt;data to access the 802.11 header.
However, skb-&amp;gt;len includes data in both the linear head buffer and
non-linear fragments/pages. When AF_PACKET sends a packet large enough to
become non-linear, the 802.11 header at skb-&amp;gt;data + len_rthdr may extend
past the linear head buffer even though skb-&amp;gt;len appears sufficient.&lt;/p&gt;
&lt;p&gt;This leads to a slab-out-of-bounds read when accessing hdr-&amp;gt;frame_control,
as the kernel reads beyond the allocated skb head buffer:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-out-of-bounds in ieee80211_monitor_select_queue+0x1ed/0x220&lt;/p&gt;
&lt;p&gt;syzbot has hit the same issues.&lt;/p&gt;
&lt;p&gt;Fix this by checking skb_headlen(skb) (which gives the length of the
linear data region) instead of skb-&amp;gt;len before dereferencing skb-&amp;gt;data
pointers. This ensures the required bytes are actually present in the
linear portion of the skb.&lt;/p&gt;
&lt;p&gt;Apply the same fix to ieee80211_validate_radiotap_len() which has the
same class of bug: it uses skb-&amp;gt;len to validate accesses to skb-&amp;gt;data,
and to the corresponding checks in ieee80211_monitor_start_xmit(): for
drivers advertising NETIF_F_SG the skb is not linearized before
ndo_start_xmit, so the 802.11 header can be read past the linear
buffer there as well.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-8wg2-h9c3-q8hh</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-98810 — wifi: mac80211: fix slab-out-of-bounds read in ieee80211_monitor_select_queue()</title>
      <link>https://db.gcve.eu/vuln/msrc_cve-2026-98810</link>
      <description>msrc_CVE-2026-98810</description>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/msrc_cve-2026-98810</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-98810</title>
      <link>https://db.gcve.eu/vuln/ubuntu-cve-2026-98810</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 248 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211: fix slab-out-of-bounds read in ieee80211_monitor_select_queue() ieee80211_monitor_select_queue() validates the skb length using skb-&amp;gt;len before dereferencing pointers into skb-&amp;gt;data to access the 802.11 header. However, skb-&amp;gt;len includes data in both the linear head buffer and non-linear fragments/pages. When AF_PACKET sends a packet large enough to become non-linear, the 802.11 header at skb-&amp;gt;data + len_rthdr may extend past the linear head buffer even though skb-&amp;gt;len appears sufficient. This leads to a slab-out-of-bounds read when accessing hdr-&amp;gt;frame_control, as the kernel reads beyond the allocated skb head buffer:   BUG: KASAN: slab-out-of-bounds in ieee80211_monitor_select_queue+0x1ed/0x220 syzbot has hit the same issues. Fix this by checking skb_headlen(skb) (which gives the length of the linear data region) instead of skb-&amp;gt;len before dereferencing skb-&amp;gt;data pointers. This ensures the required bytes are actually present in the linear portion of the skb. Apply the same fix to ieee80211_validate_radiotap_len() which has the same class of bug: it uses skb-&amp;gt;len to validate accesses to skb-&amp;gt;data, and to the corresponding checks in ieee80211_monitor_start_xmit(): for drivers advertising NETIF_F_SG the skb is not linearized before ndo_start_xmit, so the 802.11 header can be read past the linear buffer there as well.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 248 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211: fix slab-out-of-bounds read in ieee80211_monitor_select_queue() ieee80211_monitor_select_queue() validates the skb length using skb-&amp;gt;len before dereferencing pointers into skb-&amp;gt;data to access the 802.11 header. However, skb-&amp;gt;len includes data in both the linear head buffer and non-linear fragments/pages. When AF_PACKET sends a packet large enough to become non-linear, the 802.11 header at skb-&amp;gt;data + len_rthdr may extend past the linear head buffer even though skb-&amp;gt;len appears sufficient. This leads to a slab-out-of-bounds read when accessing hdr-&amp;gt;frame_control, as the kernel reads beyond the allocated skb head buffer:   BUG: KASAN: slab-out-of-bounds in ieee80211_monitor_select_queue+0x1ed/0x220 syzbot has hit the same issues. Fix this by checking skb_headlen(skb) (which gives the length of the linear data region) instead of skb-&amp;gt;len before dereferencing skb-&amp;gt;data pointers. This ensures the required bytes are actually present in the linear portion of the skb. Apply the same fix to ieee80211_validate_radiotap_len() which has the same class of bug: it uses skb-&amp;gt;len to validate accesses to skb-&amp;gt;data, and to the corresponding checks in ieee80211_monitor_start_xmit(): for drivers advertising NETIF_F_SG the skb is not linearized before ndo_start_xmit, so the 802.11 header can be read past the linear buffer there as well.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ubuntu-cve-2026-98810</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-4019 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://db.gcve.eu/vuln/wid-sec-w-2026-4019</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise einen Denial-of-Service-Angriff auszulösen, Daten zu manipulieren oder offenzulegen oder Sicherheitsmaßnahmen zu umgehen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise einen Denial-of-Service-Angriff auszulösen, Daten zu manipulieren oder offenzulegen oder Sicherheitsmaßnahmen zu umgehen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/wid-sec-w-2026-4019</guid>
    </item>
  </channel>
</rss>
