CVE Tools

CVE-2026-98421

wifi: mac80211: require a peer station for TDLS setup confirm

No known exploitation. EPSS puts it in the 11th 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: ≥ 6f7eaa47e1de30159277f91f1145a6687f13ffd9, < 6bae6ef511a29ef12ab969adeea691067d4d5d74Upgrade to: 6bae6ef511a29ef12ab969adeea691067d4d5d74Affected: ≥ 6f7eaa47e1de30159277f91f1145a6687f13ffd9, < d0afa5395c46d73ad2090aa50209886e84f179bdUpgrade to: d0afa5395c46d73ad2090aa50209886e84f179bdAffected: ≥ 6f7eaa47e1de30159277f91f1145a6687f13ffd9, < 742c762bee59c973684f70dfed7de4945d3141e2Upgrade to: 742c762bee59c973684f70dfed7de4945d3141e2Affected: ≥ 6f7eaa47e1de30159277f91f1145a6687f13ffd9, < fce36d242a18ddf64731d816a37564103172da11Upgrade to: fce36d242a18ddf64731d816a37564103172da11 + 2 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: require a peer station for TDLS setup confirm It's nonsense for the setup confirm to go to station that doesn't even exist, and it hits a warning when building the frame: WARN_ON_ONCE(!sta || !ap_sta) Only accept WLAN_TDLS_SETUP_CONFIRM when the station is already there as a TDLS station. Need to copy the call to ieee80211_tdls_prep_mgmt_packet() since the existing WLAN_TDLS_DISCOVERY_REQUEST already falls through to it.

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.

EPSS11th
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 11th 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.