<?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-16T09:05:11.760799+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/cve-2026-98422</id>
    <title>CVE-2026-98422 — wifi: mac80211: reset the AP_VLAN tailroom counter on ifdown</title>
    <updated>2026-10-16T09:05:11.762172+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<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://db.gcve.eu/vuln/cve-2026-98422"/>
  </entry>
</feed>
