<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-17T09:48:50.144592+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/bell-cve-2026-98407</id>
    <title>BELL-CVE-2026-98407</title>
    <updated>2026-11-17T09:48:50.224937+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p><strong>Affected:</strong> Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/bell-cve-2026-98407"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/certfr-2026-avi-1374</id>
    <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>
    <updated>2026-11-17T09:48:50.224994+00:00</updated>
    <content>certfr-2026-avi-1374</content>
    <link href="https://cve.radiocsirt.org/vuln/certfr-2026-avi-1374"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-388752</id>
    <title>EUVD-2026-388752</title>
    <updated>2026-11-17T09:48:50.225014+00:00</updated>
    <content>EUVD-2026-388752</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-388752"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-98407</id>
    <title>fkie_cve-2026-98407</title>
    <updated>2026-11-17T09:48:50.225026+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>wifi: rsi: fix heap OOB write on key removal</p>
<p>When a key is removed (data == NULL), rsi_hal_load_key() runs:</p>
<p>memset(&amp;set_key[FRAME_DESC_SZ], 0, frame_len - FRAME_DESC_SZ);</p>
<p>set_key is a struct rsi_set_key *, so the subscript is scaled by
sizeof(struct rsi_set_key) (160 bytes): &amp;set_key[FRAME_DESC_SZ] is
skb-&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.</p>
<p>The write fires on every DISABLE_KEY callback, so plain disconnects,
roams and interface teardowns trigger it on real networks.</p>
<p>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.</p>
<p>Discovered by Atuin - Automated Vulnerability Discovery Engine.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-98407"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-5p9q-rqwh-2www</id>
    <title>GHSA-5p9q-rqwh-2www</title>
    <updated>2026-11-17T09:48:50.225063+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>wifi: rsi: fix heap OOB write on key removal</p>
<p>When a key is removed (data == NULL), rsi_hal_load_key() runs:</p>
<p>memset(&amp;set_key[FRAME_DESC_SZ], 0, frame_len - FRAME_DESC_SZ);</p>
<p>set_key is a struct rsi_set_key *, so the subscript is scaled by
sizeof(struct rsi_set_key) (160 bytes): &amp;set_key[FRAME_DESC_SZ] is
skb-&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.</p>
<p>The write fires on every DISABLE_KEY callback, so plain disconnects,
roams and interface teardowns trigger it on real networks.</p>
<p>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.</p>
<p>Discovered by Atuin - Automated Vulnerability Discovery Engine.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-5p9q-rqwh-2www"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/msrc_cve-2026-98407</id>
    <title>msrc_CVE-2026-98407 — wifi: rsi: fix heap OOB write on key removal</title>
    <updated>2026-11-17T09:48:50.225089+00:00</updated>
    <content>msrc_CVE-2026-98407</content>
    <link href="https://cve.radiocsirt.org/vuln/msrc_cve-2026-98407"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/oesa-2026-4810</id>
    <title>OESA-2026-4810 — kernel security update</title>
    <updated>2026-11-17T09:48:50.225104+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> openEuler:22.03-LTS-SP4: kernel</p>
<p>The Linux Kernel, the operating system core itself.

Security Fix(es):</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>wifi: brcmsmac: Fix dma_free_coherent() size</p>
<p>dma_alloc_consistent() may change the size to align it. The new size is
saved in alloced.</p>
<p>Change the free size to match the allocation size.(CVE-2026-31661)</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>drm/amd/display: Validate GPIO pin LUT table size before iterating</p>
<p>[Why&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.</p>
<p>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.</p>
<p>(cherry picked from commit ba5e95b43b773ae1bf1f66ee6b31eb774e65afe3)(CVE-2026-64097)</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>usbip: vudc: fix NULL deref in vep_dequeue()</p>
<p>vep_alloc_request() wasn&amp;apos;t initializing vrequest-&amp;gt;udc, so cancellations
on the FunctionFS AIO path were arriving in vep_dequeue without a valid
UDC reference.</p>
<p>Since vrequest-&amp;gt;udc…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/oesa-2026-4810"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-98407</id>
    <title>UBUNTU-CVE-2026-98407</title>
    <updated>2026-11-17T09:48:50.225474+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> 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</p>
<p>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;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;set_key[FRAME_DESC_SZ] is skb-&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.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-98407"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3951</id>
    <title>WID-SEC-W-2026-3951 — Linux Kernel: Mehrere Schwachstellen</title>
    <updated>2026-11-17T09:48:50.225743+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>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.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3951"/>
  </entry>
</feed>
