CVE Tools

CVE-2026-98422

wifi: mac80211: reset the AP_VLAN tailroom counter on ifdown

No known exploitation. EPSS puts it in the 12th percentile. Fixed versions are out.

Published Updated Sources: CVE.org, NVD

What to do

Find your product and version, then upgrade to the build on the right.

  • LinuxAffected: ≥ f9dca80b98caac8b4bfb43a2edf1e9f877ccf322, < b0b32d3f163d24ea7134380666193bf398e9dc0bUpgrade to: b0b32d3f163d24ea7134380666193bf398e9dc0bAffected: ≥ f9dca80b98caac8b4bfb43a2edf1e9f877ccf322, < f6b34a7d64324faf28eedc0f8678b0f832f1cc36Upgrade to: f6b34a7d64324faf28eedc0f8678b0f832f1cc36Affected: ≥ f9dca80b98caac8b4bfb43a2edf1e9f877ccf322, < 304a874670a0b6ab5589a7f60b4af0251797b121Upgrade to: 304a874670a0b6ab5589a7f60b4af0251797b121Affected: ≥ f9dca80b98caac8b4bfb43a2edf1e9f877ccf322, < 7775759e3cb35ef5a571b2d877c2a9b70a5d5f08Upgrade to: 7775759e3cb35ef5a571b2d877c2a9b70a5d5f08 + 4 more branchesStated by: CVE record

Versions as the sources state them. Full version matrix after sign-in

What it is

From the CVE record

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->crypto_tx_tailroom_needed_cnt != master->crypto_tx_tailroom_needed_cnt); Reset it on ifdown to avoid that.

In plain language

No plain-language summary for this CVE yet.

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS12th
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

0.2% chance of exploitation activity in the next 30 days, which ranks it in the 12th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

4 events over 8 days, from the signal feeds we watch.

  1. OpenVAS check added
  2. Record updated
  3. Publishedrecord updated

Affected products

Sources

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Linux, not every advisory.