<?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:54.242862+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-98422</id>
    <title>BELL-CVE-2026-98422</title>
    <updated>2026-11-17T09:48:54.343452+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-98422"/>
  </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:54.343516+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-388765</id>
    <title>EUVD-2026-388765</title>
    <updated>2026-11-17T09:48:54.343537+00:00</updated>
    <content>EUVD-2026-388765</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-388765"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-98422</id>
    <title>fkie_cve-2026-98422</title>
    <updated>2026-11-17T09:48:54.343549+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: mac80211: reset the AP_VLAN tailroom counter on ifdown</p>
<p>On ifup, AP_VLAN interfaces get crypto_tx_tailroom_needed_cnt from
the AP interface, but it's never decremented again unless the AP is
also brought down. Thus, bringing the same AP_VLAN up again will
increment the counter again and eventually hit the sanity check:</p>
<p>WARN_ON_ONCE(sdata-&gt;crypto_tx_tailroom_needed_cnt !=
               master-&gt;crypto_tx_tailroom_needed_cnt);</p>
<p>Reset it on ifdown to avoid that.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-98422"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-7fq6-p34m-gv65</id>
    <title>GHSA-7fq6-p34m-gv65</title>
    <updated>2026-11-17T09:48:54.343581+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: mac80211: reset the AP_VLAN tailroom counter on ifdown</p>
<p>On ifup, AP_VLAN interfaces get crypto_tx_tailroom_needed_cnt from
the AP interface, but it's never decremented again unless the AP is
also brought down. Thus, bringing the same AP_VLAN up again will
increment the counter again and eventually hit the sanity check:</p>
<p>WARN_ON_ONCE(sdata-&gt;crypto_tx_tailroom_needed_cnt !=
               master-&gt;crypto_tx_tailroom_needed_cnt);</p>
<p>Reset it on ifdown to avoid that.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-7fq6-p34m-gv65"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/msrc_cve-2026-98422</id>
    <title>msrc_CVE-2026-98422 — wifi: mac80211: reset the AP_VLAN tailroom counter on ifdown</title>
    <updated>2026-11-17T09:48:54.343602+00:00</updated>
    <content>msrc_CVE-2026-98422</content>
    <link href="https://cve.radiocsirt.org/vuln/msrc_cve-2026-98422"/>
  </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:54.343618+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-98422</id>
    <title>UBUNTU-CVE-2026-98422</title>
    <updated>2026-11-17T09:48:54.343800+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: mac80211: reset the AP_VLAN tailroom counter on ifdown On ifup, AP_VLAN interfaces get crypto_tx_tailroom_needed_cnt from the AP interface, but it's never decremented again unless the AP is also brought down. Thus, bringing the same AP_VLAN up again will increment the counter again and eventually hit the sanity check:   WARN_ON_ONCE(sdata-&gt;crypto_tx_tailroom_needed_cnt !=                master-&gt;crypto_tx_tailroom_needed_cnt); Reset it on ifdown to avoid that.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-98422"/>
  </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:54.344250+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>
