<?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:01:39 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-08019</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-08019</link>
      <description>bdu:2025-08019</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-08019</guid>
    </item>
    <item>
      <title>BELL-CVE-2024-47738</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2024-47738</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-2024-47738</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0999 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Certaines d'entre elles permettent à un at…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2024-avi-0999</link>
      <description>certfr-2024-avi-0999</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2024-avi-0999</guid>
    </item>
    <item>
      <title>EUVD-2026-320700</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-320700</link>
      <description>EUVD-2026-320700</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-320700</guid>
    </item>
    <item>
      <title>fkie_cve-2024-47738</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-47738</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 use rate mask for offchannel TX either&lt;/p&gt;
&lt;p&gt;Like the commit ab9177d83c04 (&amp;#34;wifi: mac80211: don&amp;#39;t use rate mask for
scanning&amp;#34;), ignore incorrect settings to avoid no supported rate warning
reported by syzbot.&lt;/p&gt;
&lt;p&gt;The syzbot did bisect and found cause is commit 9df66d5b9f45 (&amp;#34;cfg80211:
fix default HE tx bitrate mask in 2G band&amp;#34;), which however corrects
bitmask of HE MCS and recognizes correctly settings of empty legacy rate
plus HE MCS rate instead of returning -EINVAL.&lt;/p&gt;
&lt;p&gt;As suggestions [1], follow the change of SCAN TX to consider this case of
offchannel TX as well.&lt;/p&gt;
&lt;p&gt;[1] https://lore.kernel.org/linux-wireless/6ab2dc9c3afe753ca6fdcdd1421e7a1f47e87b84.camel@sipsolutions.net/T/#m2ac2a6d2be06a37c9c47a3d8a44b4f647ed4f024&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 use rate mask for offchannel TX either&lt;/p&gt;
&lt;p&gt;Like the commit ab9177d83c04 (&amp;#34;wifi: mac80211: don&amp;#39;t use rate mask for
scanning&amp;#34;), ignore incorrect settings to avoid no supported rate warning
reported by syzbot.&lt;/p&gt;
&lt;p&gt;The syzbot did bisect and found cause is commit 9df66d5b9f45 (&amp;#34;cfg80211:
fix default HE tx bitrate mask in 2G band&amp;#34;), which however corrects
bitmask of HE MCS and recognizes correctly settings of empty legacy rate
plus HE MCS rate instead of returning -EINVAL.&lt;/p&gt;
&lt;p&gt;As suggestions [1], follow the change of SCAN TX to consider this case of
offchannel TX as well.&lt;/p&gt;
&lt;p&gt;[1] https://lore.kernel.org/linux-wireless/6ab2dc9c3afe753ca6fdcdd1421e7a1f47e87b84.camel@sipsolutions.net/T/#m2ac2a6d2be06a37c9c47a3d8a44b4f647ed4f024&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-47738</guid>
    </item>
    <item>
      <title>GHSA-8mgj-pm8q-9jpq</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-8mgj-pm8q-9jpq</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 use rate mask for offchannel TX either&lt;/p&gt;
&lt;p&gt;Like the commit ab9177d83c04 (&amp;#34;wifi: mac80211: don&amp;#39;t use rate mask for
scanning&amp;#34;), ignore incorrect settings to avoid no supported rate warning
reported by syzbot.&lt;/p&gt;
&lt;p&gt;The syzbot did bisect and found cause is commit 9df66d5b9f45 (&amp;#34;cfg80211:
fix default HE tx bitrate mask in 2G band&amp;#34;), which however corrects
bitmask of HE MCS and recognizes correctly settings of empty legacy rate
plus HE MCS rate instead of returning -EINVAL.&lt;/p&gt;
&lt;p&gt;As suggestions [1], follow the change of SCAN TX to consider this case of
offchannel TX as well.&lt;/p&gt;
&lt;p&gt;[1] https://lore.kernel.org/linux-wireless/6ab2dc9c3afe753ca6fdcdd1421e7a1f47e87b84.camel@sipsolutions.net/T/#m2ac2a6d2be06a37c9c47a3d8a44b4f647ed4f024&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 use rate mask for offchannel TX either&lt;/p&gt;
&lt;p&gt;Like the commit ab9177d83c04 (&amp;#34;wifi: mac80211: don&amp;#39;t use rate mask for
scanning&amp;#34;), ignore incorrect settings to avoid no supported rate warning
reported by syzbot.&lt;/p&gt;
&lt;p&gt;The syzbot did bisect and found cause is commit 9df66d5b9f45 (&amp;#34;cfg80211:
fix default HE tx bitrate mask in 2G band&amp;#34;), which however corrects
bitmask of HE MCS and recognizes correctly settings of empty legacy rate
plus HE MCS rate instead of returning -EINVAL.&lt;/p&gt;
&lt;p&gt;As suggestions [1], follow the change of SCAN TX to consider this case of
offchannel TX as well.&lt;/p&gt;
&lt;p&gt;[1] https://lore.kernel.org/linux-wireless/6ab2dc9c3afe753ca6fdcdd1421e7a1f47e87b84.camel@sipsolutions.net/T/#m2ac2a6d2be06a37c9c47a3d8a44b4f647ed4f024&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-8mgj-pm8q-9jpq</guid>
    </item>
    <item>
      <title>msrc_CVE-2024-47738 — wifi: mac80211: don't use rate mask for offchannel TX either</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2024-47738</link>
      <description>msrc_CVE-2024-47738</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2024-47738</guid>
    </item>
    <item>
      <title>OESA-2024-2537 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2024-2537</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:  xhci: Handle TD clearing for multiple streams case  When multiple streams are in use, multiple TDs might be in flight when an endpoint is stopped. We need to issue a Set TR Dequeue Pointer for each, to ensure everything is reset properly and the caches cleared. Change the logic so that any N&amp;amp;gt;1 TDs found active for different streams are deferred until after the first one is processed, calling xhci_invalidate_cancelled_tds() again from xhci_handle_cmd_set_deq() to queue another command until we are done with all of them. Also change the error/&amp;amp;quot;should never happen&amp;amp;quot; paths to ensure we at least clear any affected TDs, even if we can&amp;amp;apos;t issue a command to clear the hardware cache, and complain loudly with an xhci_warn() if this ever happens.  This problem case dates back to commit e9df17eb1408 (&amp;amp;quot;USB: xhci: Correct assumptions about number of rings per endpoint.&amp;amp;quot;) early on in the XHCI driver&amp;amp;apos;s life, when stream support was first added. It was then identified but not fixed nor made into a warning in commit 674f8438c121 (&amp;amp;quot;xhci: split handling halted endpoints into two steps&amp;amp;quot;), which added a FIXME comment for the problem case (without materially changing the behavior as far as I can tell, though the new logic made the problem more obvious).  Then later, in commit 94f339147fc3 (&amp;amp;quot;xhci: Fix failure…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:  xhci: Handle TD clearing for multiple streams case  When multiple streams are in use, multiple TDs might be in flight when an endpoint is stopped. We need to issue a Set TR Dequeue Pointer for each, to ensure everything is reset properly and the caches cleared. Change the logic so that any N&amp;amp;gt;1 TDs found active for different streams are deferred until after the first one is processed, calling xhci_invalidate_cancelled_tds() again from xhci_handle_cmd_set_deq() to queue another command until we are done with all of them. Also change the error/&amp;amp;quot;should never happen&amp;amp;quot; paths to ensure we at least clear any affected TDs, even if we can&amp;amp;apos;t issue a command to clear the hardware cache, and complain loudly with an xhci_warn() if this ever happens.  This problem case dates back to commit e9df17eb1408 (&amp;amp;quot;USB: xhci: Correct assumptions about number of rings per endpoint.&amp;amp;quot;) early on in the XHCI driver&amp;amp;apos;s life, when stream support was first added. It was then identified but not fixed nor made into a warning in commit 674f8438c121 (&amp;amp;quot;xhci: split handling halted endpoints into two steps&amp;amp;quot;), which added a FIXME comment for the problem case (without materially changing the behavior as far as I can tell, though the new logic made the problem more obvious).  Then later, in commit 94f339147fc3 (&amp;amp;quot;xhci: Fix failure…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2024-2537</guid>
    </item>
    <item>
      <title>openSUSE-SU-2024:14500-1 — kernel-devel-6.11.8-1.1 on GA media</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2024:14500-1</link>
      <description>&lt;p&gt;kernel-devel-6.11.8-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel-devel-6.11.8-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2024:14500-1</guid>
    </item>
    <item>
      <title>SUSE-SU-2024:3983-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2024:3983-1</link>
      <description>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/suse-su-2024:3983-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-47738</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-47738</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 139 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211: don&amp;#39;t use rate mask for offchannel TX either Like the commit ab9177d83c04 (&amp;#34;wifi: mac80211: don&amp;#39;t use rate mask for scanning&amp;#34;), ignore incorrect settings to avoid no supported rate warning reported by syzbot. The syzbot did bisect and found cause is commit 9df66d5b9f45 (&amp;#34;cfg80211: fix default HE tx bitrate mask in 2G band&amp;#34;), which however corrects bitmask of HE MCS and recognizes correctly settings of empty legacy rate plus HE MCS rate instead of returning -EINVAL. As suggestions [1], follow the change of SCAN TX to consider this case of offchannel TX as well. [1] https://lore.kernel.org/linux-wireless/6ab2dc9c3afe753ca6fdcdd1421e7a1f47e87b84.camel@sipsolutions.net/T/#m2ac2a6d2be06a37c9c47a3d8a44b4f647ed4f024&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 139 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211: don&amp;#39;t use rate mask for offchannel TX either Like the commit ab9177d83c04 (&amp;#34;wifi: mac80211: don&amp;#39;t use rate mask for scanning&amp;#34;), ignore incorrect settings to avoid no supported rate warning reported by syzbot. The syzbot did bisect and found cause is commit 9df66d5b9f45 (&amp;#34;cfg80211: fix default HE tx bitrate mask in 2G band&amp;#34;), which however corrects bitmask of HE MCS and recognizes correctly settings of empty legacy rate plus HE MCS rate instead of returning -EINVAL. As suggestions [1], follow the change of SCAN TX to consider this case of offchannel TX as well. [1] https://lore.kernel.org/linux-wireless/6ab2dc9c3afe753ca6fdcdd1421e7a1f47e87b84.camel@sipsolutions.net/T/#m2ac2a6d2be06a37c9c47a3d8a44b4f647ed4f024&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-47738</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-3251 — Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-3251</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder andere, nicht näher bekannte Auswirkungen zu erzielen..&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder andere, nicht näher bekannte Auswirkungen zu erzielen..&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2024-3251</guid>
    </item>
  </channel>
</rss>
