<?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, 10 Oct 2026 20:55:05 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-98325</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-98325</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-2026-98325</guid>
    </item>
    <item>
      <title>EUVD-2026-383437</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-383437</link>
      <description>EUVD-2026-383437</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-383437</guid>
    </item>
    <item>
      <title>fkie_cve-2026-98325</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-98325</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;wifi: mac80211: set up the TX info early to fix failure paths&lt;/p&gt;
&lt;p&gt;The previous commit 2c51457d930f (&amp;#34;wifi: mac80211: free ack status
frame on TX header build failure&amp;#34;) cleaned up the leak, but still
left the code a bit messy and the failed SKB didn&amp;#39;t get reported
to userspace.&lt;/p&gt;
&lt;p&gt;Fix this up by initialising skb-&amp;gt;cb[] earlier, which allows using
ieee80211_free_txskb() and therefore reports it for the failure
in ieee80211_build_hdr(), and unifies the ieee80211_skb_resize()
failure path with it.&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: set up the TX info early to fix failure paths&lt;/p&gt;
&lt;p&gt;The previous commit 2c51457d930f (&amp;#34;wifi: mac80211: free ack status
frame on TX header build failure&amp;#34;) cleaned up the leak, but still
left the code a bit messy and the failed SKB didn&amp;#39;t get reported
to userspace.&lt;/p&gt;
&lt;p&gt;Fix this up by initialising skb-&amp;gt;cb[] earlier, which allows using
ieee80211_free_txskb() and therefore reports it for the failure
in ieee80211_build_hdr(), and unifies the ieee80211_skb_resize()
failure path with it.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-98325</guid>
    </item>
    <item>
      <title>GHSA-3437-mcr8-jcvh</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-3437-mcr8-jcvh</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;wifi: mac80211: set up the TX info early to fix failure paths&lt;/p&gt;
&lt;p&gt;The previous commit 2c51457d930f (&amp;#34;wifi: mac80211: free ack status
frame on TX header build failure&amp;#34;) cleaned up the leak, but still
left the code a bit messy and the failed SKB didn&amp;#39;t get reported
to userspace.&lt;/p&gt;
&lt;p&gt;Fix this up by initialising skb-&amp;gt;cb[] earlier, which allows using
ieee80211_free_txskb() and therefore reports it for the failure
in ieee80211_build_hdr(), and unifies the ieee80211_skb_resize()
failure path with it.&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: set up the TX info early to fix failure paths&lt;/p&gt;
&lt;p&gt;The previous commit 2c51457d930f (&amp;#34;wifi: mac80211: free ack status
frame on TX header build failure&amp;#34;) cleaned up the leak, but still
left the code a bit messy and the failed SKB didn&amp;#39;t get reported
to userspace.&lt;/p&gt;
&lt;p&gt;Fix this up by initialising skb-&amp;gt;cb[] earlier, which allows using
ieee80211_free_txskb() and therefore reports it for the failure
in ieee80211_build_hdr(), and unifies the ieee80211_skb_resize()
failure path with it.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-3437-mcr8-jcvh</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-98325 — wifi: mac80211: set up the TX info early to fix failure paths</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2026-98325</link>
      <description>msrc_CVE-2026-98325</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2026-98325</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-98325</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-98325</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 247 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211: set up the TX info early to fix failure paths The previous commit 2c51457d930f (&amp;#34;wifi: mac80211: free ack status frame on TX header build failure&amp;#34;) cleaned up the leak, but still left the code a bit messy and the failed SKB didn&amp;#39;t get reported to userspace. Fix this up by initialising skb-&amp;gt;cb[] earlier, which allows using ieee80211_free_txskb() and therefore reports it for the failure in ieee80211_build_hdr(), and unifies the ieee80211_skb_resize() failure path with it.&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 247 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211: set up the TX info early to fix failure paths The previous commit 2c51457d930f (&amp;#34;wifi: mac80211: free ack status frame on TX header build failure&amp;#34;) cleaned up the leak, but still left the code a bit messy and the failed SKB didn&amp;#39;t get reported to userspace. Fix this up by initialising skb-&amp;gt;cb[] earlier, which allows using ieee80211_free_txskb() and therefore reports it for the failure in ieee80211_build_hdr(), and unifies the ieee80211_skb_resize() failure path with it.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-98325</guid>
    </item>
  </channel>
</rss>
