<?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>Fri, 09 Oct 2026 07:39:43 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-383449</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-383449</link>
      <description>EUVD-2026-383449</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-383449</guid>
    </item>
    <item>
      <title>fkie_cve-2026-98337</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-98337</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;wifi: mac80211: don&amp;#39;t start a ROC while scanning&lt;/p&gt;
&lt;p&gt;The ROC work can be pending when a scan starts (which requires
ROC list to be empty, but that&amp;#39;s possible), and then a new ROC
can be added to the list and the work will pick it up.&lt;/p&gt;
&lt;p&gt;Avoid starting that ROC if a scan made it between things, as
otherwise we&amp;#39;ll hit a warning later:&lt;/p&gt;
&lt;p&gt;WARNING: net/mac80211/offchannel.c:404 at ieee80211_start_next_roc+0x256/0x2d0
  Workqueue: events_unbound cfg80211_wiphy_work
  Call Trace:
   __ieee80211_scan_completed+0x4fd/0xe40 net/mac80211/scan.c:537
   ieee80211_scan_work+0x472/0x1ff0 net/mac80211/scan.c:1193
   cfg80211_wiphy_work+0x410/0x570 net/wireless/core.c:513&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: don&amp;#39;t start a ROC while scanning&lt;/p&gt;
&lt;p&gt;The ROC work can be pending when a scan starts (which requires
ROC list to be empty, but that&amp;#39;s possible), and then a new ROC
can be added to the list and the work will pick it up.&lt;/p&gt;
&lt;p&gt;Avoid starting that ROC if a scan made it between things, as
otherwise we&amp;#39;ll hit a warning later:&lt;/p&gt;
&lt;p&gt;WARNING: net/mac80211/offchannel.c:404 at ieee80211_start_next_roc+0x256/0x2d0
  Workqueue: events_unbound cfg80211_wiphy_work
  Call Trace:
   __ieee80211_scan_completed+0x4fd/0xe40 net/mac80211/scan.c:537
   ieee80211_scan_work+0x472/0x1ff0 net/mac80211/scan.c:1193
   cfg80211_wiphy_work+0x410/0x570 net/wireless/core.c:513&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-98337</guid>
    </item>
    <item>
      <title>GHSA-pccj-pwww-vq83</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-pccj-pwww-vq83</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;wifi: mac80211: don&amp;#39;t start a ROC while scanning&lt;/p&gt;
&lt;p&gt;The ROC work can be pending when a scan starts (which requires
ROC list to be empty, but that&amp;#39;s possible), and then a new ROC
can be added to the list and the work will pick it up.&lt;/p&gt;
&lt;p&gt;Avoid starting that ROC if a scan made it between things, as
otherwise we&amp;#39;ll hit a warning later:&lt;/p&gt;
&lt;p&gt;WARNING: net/mac80211/offchannel.c:404 at ieee80211_start_next_roc+0x256/0x2d0
  Workqueue: events_unbound cfg80211_wiphy_work
  Call Trace:
   __ieee80211_scan_completed+0x4fd/0xe40 net/mac80211/scan.c:537
   ieee80211_scan_work+0x472/0x1ff0 net/mac80211/scan.c:1193
   cfg80211_wiphy_work+0x410/0x570 net/wireless/core.c:513&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: don&amp;#39;t start a ROC while scanning&lt;/p&gt;
&lt;p&gt;The ROC work can be pending when a scan starts (which requires
ROC list to be empty, but that&amp;#39;s possible), and then a new ROC
can be added to the list and the work will pick it up.&lt;/p&gt;
&lt;p&gt;Avoid starting that ROC if a scan made it between things, as
otherwise we&amp;#39;ll hit a warning later:&lt;/p&gt;
&lt;p&gt;WARNING: net/mac80211/offchannel.c:404 at ieee80211_start_next_roc+0x256/0x2d0
  Workqueue: events_unbound cfg80211_wiphy_work
  Call Trace:
   __ieee80211_scan_completed+0x4fd/0xe40 net/mac80211/scan.c:537
   ieee80211_scan_work+0x472/0x1ff0 net/mac80211/scan.c:1193
   cfg80211_wiphy_work+0x410/0x570 net/wireless/core.c:513&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-pccj-pwww-vq83</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-98337 — wifi: mac80211: don't start a ROC while scanning</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2026-98337</link>
      <description>msrc_CVE-2026-98337</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2026-98337</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-98337</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-98337</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, 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, Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:18.04:LTS: linux, Ubuntu:Pro:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.0 and 239 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211: don&amp;#39;t start a ROC while scanning The ROC work can be pending when a scan starts (which requires ROC list to be empty, but that&amp;#39;s possible), and then a new ROC can be added to the list and the work will pick it up. Avoid starting that ROC if a scan made it between things, as otherwise we&amp;#39;ll hit a warning later:   WARNING: net/mac80211/offchannel.c:404 at ieee80211_start_next_roc+0x256/0x2d0   Workqueue: events_unbound cfg80211_wiphy_work   Call Trace:    __ieee80211_scan_completed+0x4fd/0xe40 net/mac80211/scan.c:537    ieee80211_scan_work+0x472/0x1ff0 net/mac80211/scan.c:1193    cfg80211_wiphy_work+0x410/0x570 net/wireless/core.c:513&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, 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, Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:18.04:LTS: linux, Ubuntu:Pro:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.0 and 239 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211: don&amp;#39;t start a ROC while scanning The ROC work can be pending when a scan starts (which requires ROC list to be empty, but that&amp;#39;s possible), and then a new ROC can be added to the list and the work will pick it up. Avoid starting that ROC if a scan made it between things, as otherwise we&amp;#39;ll hit a warning later:   WARNING: net/mac80211/offchannel.c:404 at ieee80211_start_next_roc+0x256/0x2d0   Workqueue: events_unbound cfg80211_wiphy_work   Call Trace:    __ieee80211_scan_completed+0x4fd/0xe40 net/mac80211/scan.c:537    ieee80211_scan_work+0x472/0x1ff0 net/mac80211/scan.c:1193    cfg80211_wiphy_work+0x410/0x570 net/wireless/core.c:513&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-98337</guid>
    </item>
  </channel>
</rss>
