<?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://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-22T23:45:58.361934+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" 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://db.gcve.eu/vuln/fkie_cve-2026-98407</id>
    <title>fkie_cve-2026-98407</title>
    <updated>2026-10-22T23:45:58.369391+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://db.gcve.eu/vuln/fkie_cve-2026-98407"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ghsa-5p9q-rqwh-2www</id>
    <title>GHSA-5p9q-rqwh-2www</title>
    <updated>2026-10-22T23:45:58.369473+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://db.gcve.eu/vuln/ghsa-5p9q-rqwh-2www"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/msrc_cve-2026-98407</id>
    <title>msrc_CVE-2026-98407 — wifi: rsi: fix heap OOB write on key removal</title>
    <updated>2026-10-22T23:45:58.369503+00:00</updated>
    <content>msrc_CVE-2026-98407</content>
    <link href="https://db.gcve.eu/vuln/msrc_cve-2026-98407"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/opensuse-su-2026:12165-1</id>
    <title>openSUSE-SU-2026:12165-1 — kernel-devel-7.2.11-1.1 on GA media</title>
    <updated>2026-10-22T23:45:58.369523+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>kernel-devel-7.2.11-1.1 on GA media</p>
      </div>
    </content>
    <link href="https://db.gcve.eu/vuln/opensuse-su-2026:12165-1"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ubuntu-cve-2026-98407</id>
    <title>UBUNTU-CVE-2026-98407</title>
    <updated>2026-10-22T23:45:58.369551+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 246 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://db.gcve.eu/vuln/ubuntu-cve-2026-98407"/>
  </entry>
</feed>
