<?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>Tue, 17 Nov 2026 09:48:49 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-98407</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-98407</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-98407</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1374 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Certaines d'entre elles permettent à un…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-1374</link>
      <description>certfr-2026-avi-1374</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-1374</guid>
    </item>
    <item>
      <title>EUVD-2026-388752</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-388752</link>
      <description>EUVD-2026-388752</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-388752</guid>
    </item>
    <item>
      <title>fkie_cve-2026-98407</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-98407</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;wifi: rsi: fix heap OOB write on key removal&lt;/p&gt;
&lt;p&gt;When a key is removed (data == NULL), rsi_hal_load_key() runs:&lt;/p&gt;
&lt;p&gt;memset(&amp;amp;set_key[FRAME_DESC_SZ], 0, frame_len - FRAME_DESC_SZ);&lt;/p&gt;
&lt;p&gt;set_key is a struct rsi_set_key *, so the subscript is scaled by
sizeof(struct rsi_set_key) (160 bytes): &amp;amp;set_key[FRAME_DESC_SZ] is
skb-&amp;gt;data + 2560, and the memset writes 144 zero bytes starting
2.4KB past the end of the 160-byte skb data buffer, corrupting
unrelated heap objects. The intended byte offset would have been
(u8 *)set_key + FRAME_DESC_SZ.&lt;/p&gt;
&lt;p&gt;The write fires on every DISABLE_KEY callback, so plain disconnects,
roams and interface teardowns trigger it on real networks.&lt;/p&gt;
&lt;p&gt;The memset is redundant: the whole buffer is zeroed right after
allocation, so the frame sent to the device is byte-identical
without it. Drop the else branch; normal operation is unaffected.&lt;/p&gt;
&lt;p&gt;Discovered by Atuin - Automated Vulnerability Discovery Engine.&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: rsi: fix heap OOB write on key removal&lt;/p&gt;
&lt;p&gt;When a key is removed (data == NULL), rsi_hal_load_key() runs:&lt;/p&gt;
&lt;p&gt;memset(&amp;amp;set_key[FRAME_DESC_SZ], 0, frame_len - FRAME_DESC_SZ);&lt;/p&gt;
&lt;p&gt;set_key is a struct rsi_set_key *, so the subscript is scaled by
sizeof(struct rsi_set_key) (160 bytes): &amp;amp;set_key[FRAME_DESC_SZ] is
skb-&amp;gt;data + 2560, and the memset writes 144 zero bytes starting
2.4KB past the end of the 160-byte skb data buffer, corrupting
unrelated heap objects. The intended byte offset would have been
(u8 *)set_key + FRAME_DESC_SZ.&lt;/p&gt;
&lt;p&gt;The write fires on every DISABLE_KEY callback, so plain disconnects,
roams and interface teardowns trigger it on real networks.&lt;/p&gt;
&lt;p&gt;The memset is redundant: the whole buffer is zeroed right after
allocation, so the frame sent to the device is byte-identical
without it. Drop the else branch; normal operation is unaffected.&lt;/p&gt;
&lt;p&gt;Discovered by Atuin - Automated Vulnerability Discovery Engine.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-98407</guid>
    </item>
    <item>
      <title>GHSA-5p9q-rqwh-2www</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-5p9q-rqwh-2www</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;wifi: rsi: fix heap OOB write on key removal&lt;/p&gt;
&lt;p&gt;When a key is removed (data == NULL), rsi_hal_load_key() runs:&lt;/p&gt;
&lt;p&gt;memset(&amp;amp;set_key[FRAME_DESC_SZ], 0, frame_len - FRAME_DESC_SZ);&lt;/p&gt;
&lt;p&gt;set_key is a struct rsi_set_key *, so the subscript is scaled by
sizeof(struct rsi_set_key) (160 bytes): &amp;amp;set_key[FRAME_DESC_SZ] is
skb-&amp;gt;data + 2560, and the memset writes 144 zero bytes starting
2.4KB past the end of the 160-byte skb data buffer, corrupting
unrelated heap objects. The intended byte offset would have been
(u8 *)set_key + FRAME_DESC_SZ.&lt;/p&gt;
&lt;p&gt;The write fires on every DISABLE_KEY callback, so plain disconnects,
roams and interface teardowns trigger it on real networks.&lt;/p&gt;
&lt;p&gt;The memset is redundant: the whole buffer is zeroed right after
allocation, so the frame sent to the device is byte-identical
without it. Drop the else branch; normal operation is unaffected.&lt;/p&gt;
&lt;p&gt;Discovered by Atuin - Automated Vulnerability Discovery Engine.&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: rsi: fix heap OOB write on key removal&lt;/p&gt;
&lt;p&gt;When a key is removed (data == NULL), rsi_hal_load_key() runs:&lt;/p&gt;
&lt;p&gt;memset(&amp;amp;set_key[FRAME_DESC_SZ], 0, frame_len - FRAME_DESC_SZ);&lt;/p&gt;
&lt;p&gt;set_key is a struct rsi_set_key *, so the subscript is scaled by
sizeof(struct rsi_set_key) (160 bytes): &amp;amp;set_key[FRAME_DESC_SZ] is
skb-&amp;gt;data + 2560, and the memset writes 144 zero bytes starting
2.4KB past the end of the 160-byte skb data buffer, corrupting
unrelated heap objects. The intended byte offset would have been
(u8 *)set_key + FRAME_DESC_SZ.&lt;/p&gt;
&lt;p&gt;The write fires on every DISABLE_KEY callback, so plain disconnects,
roams and interface teardowns trigger it on real networks.&lt;/p&gt;
&lt;p&gt;The memset is redundant: the whole buffer is zeroed right after
allocation, so the frame sent to the device is byte-identical
without it. Drop the else branch; normal operation is unaffected.&lt;/p&gt;
&lt;p&gt;Discovered by Atuin - Automated Vulnerability Discovery Engine.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-5p9q-rqwh-2www</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-98407 — wifi: rsi: fix heap OOB write on key removal</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2026-98407</link>
      <description>msrc_CVE-2026-98407</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2026-98407</guid>
    </item>
    <item>
      <title>OESA-2026-4810 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2026-4810</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP4: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;wifi: brcmsmac: Fix dma_free_coherent() size&lt;/p&gt;
&lt;p&gt;dma_alloc_consistent() may change the size to align it. The new size is
saved in alloced.&lt;/p&gt;
&lt;p&gt;Change the free size to match the allocation size.(CVE-2026-31661)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/amd/display: Validate GPIO pin LUT table size before iterating&lt;/p&gt;
&lt;p&gt;[Why&amp;amp;amp;How]
The GPIO pin table parsers in get_gpio_i2c_info() and
bios_parser_get_gpio_pin_info() derive an element count from the VBIOS
table_header.structuresize field, then iterate over gpio_pin[] entries.
However, GET_IMAGE() only validates that the table header itself fits
within the BIOS image. If the VBIOS reports a structuresize larger than
the actual mapped data, the loop reads past the end of the BIOS image,
causing an out-of-bounds read.&lt;/p&gt;
&lt;p&gt;Fix this by calling bios_get_image() to validate that the full claimed
structuresize is accessible within the BIOS image before entering the
loop in both functions.&lt;/p&gt;
&lt;p&gt;(cherry picked from commit ba5e95b43b773ae1bf1f66ee6b31eb774e65afe3)(CVE-2026-64097)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;usbip: vudc: fix NULL deref in vep_dequeue()&lt;/p&gt;
&lt;p&gt;vep_alloc_request() wasn&amp;amp;apos;t initializing vrequest-&amp;amp;gt;udc, so cancellations
on the FunctionFS AIO path were arriving in vep_dequeue without a valid
UDC reference.&lt;/p&gt;
&lt;p&gt;Since vrequest-&amp;amp;gt;udc…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP4: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;wifi: brcmsmac: Fix dma_free_coherent() size&lt;/p&gt;
&lt;p&gt;dma_alloc_consistent() may change the size to align it. The new size is
saved in alloced.&lt;/p&gt;
&lt;p&gt;Change the free size to match the allocation size.(CVE-2026-31661)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/amd/display: Validate GPIO pin LUT table size before iterating&lt;/p&gt;
&lt;p&gt;[Why&amp;amp;amp;How]
The GPIO pin table parsers in get_gpio_i2c_info() and
bios_parser_get_gpio_pin_info() derive an element count from the VBIOS
table_header.structuresize field, then iterate over gpio_pin[] entries.
However, GET_IMAGE() only validates that the table header itself fits
within the BIOS image. If the VBIOS reports a structuresize larger than
the actual mapped data, the loop reads past the end of the BIOS image,
causing an out-of-bounds read.&lt;/p&gt;
&lt;p&gt;Fix this by calling bios_get_image() to validate that the full claimed
structuresize is accessible within the BIOS image before entering the
loop in both functions.&lt;/p&gt;
&lt;p&gt;(cherry picked from commit ba5e95b43b773ae1bf1f66ee6b31eb774e65afe3)(CVE-2026-64097)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;usbip: vudc: fix NULL deref in vep_dequeue()&lt;/p&gt;
&lt;p&gt;vep_alloc_request() wasn&amp;amp;apos;t initializing vrequest-&amp;amp;gt;udc, so cancellations
on the FunctionFS AIO path were arriving in vep_dequeue without a valid
UDC reference.&lt;/p&gt;
&lt;p&gt;Since vrequest-&amp;amp;gt;udc…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2026-4810</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-98407</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-98407</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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, Ubuntu:16.04:LTS: linux-hwe-edge and 247 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: wifi: rsi: fix heap OOB write on key removal When a key is removed (data == NULL), rsi_hal_load_key() runs: 	memset(&amp;amp;set_key[FRAME_DESC_SZ], 0, frame_len - FRAME_DESC_SZ); set_key is a struct rsi_set_key *, so the subscript is scaled by sizeof(struct rsi_set_key) (160 bytes): &amp;amp;set_key[FRAME_DESC_SZ] is skb-&amp;gt;data + 2560, and the memset writes 144 zero bytes starting 2.4KB past the end of the 160-byte skb data buffer, corrupting unrelated heap objects. The intended byte offset would have been (u8 *)set_key + FRAME_DESC_SZ. The write fires on every DISABLE_KEY callback, so plain disconnects, roams and interface teardowns trigger it on real networks. The memset is redundant: the whole buffer is zeroed right after allocation, so the frame sent to the device is byte-identical without it. Drop the else branch; normal operation is unaffected. Discovered by Atuin - Automated Vulnerability Discovery Engine.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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, Ubuntu:16.04:LTS: linux-hwe-edge and 247 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: wifi: rsi: fix heap OOB write on key removal When a key is removed (data == NULL), rsi_hal_load_key() runs: 	memset(&amp;amp;set_key[FRAME_DESC_SZ], 0, frame_len - FRAME_DESC_SZ); set_key is a struct rsi_set_key *, so the subscript is scaled by sizeof(struct rsi_set_key) (160 bytes): &amp;amp;set_key[FRAME_DESC_SZ] is skb-&amp;gt;data + 2560, and the memset writes 144 zero bytes starting 2.4KB past the end of the 160-byte skb data buffer, corrupting unrelated heap objects. The intended byte offset would have been (u8 *)set_key + FRAME_DESC_SZ. The write fires on every DISABLE_KEY callback, so plain disconnects, roams and interface teardowns trigger it on real networks. The memset is redundant: the whole buffer is zeroed right after allocation, so the frame sent to the device is byte-identical without it. Drop the else branch; normal operation is unaffected. Discovered by Atuin - Automated Vulnerability Discovery Engine.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-98407</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-3951 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3951</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://cve.radiocsirt.org/vuln/wid-sec-w-2026-3951</guid>
    </item>
  </channel>
</rss>
