CVE-2026-98014: Linux kernel · net/mlx5: E-Switch, prevent mc_list repopulation during vport disable
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in c0c6f4ba8a37688f7b4d4044898d88f0450d44c2 : patch Linux kernel soon.
Data as of 26 Oct 2026, 16:39 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in c0c6f4ba8a37688f7b4d4044898d88f0450d44c2, 69904608e25e8ba58111aadd9210892cf3876201, 2196f9d3358b00fcb28835a5fde14071f51ecb96 +8
Exploitation evidence
Disclosed: evidence found.
CVE published 25 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
A fix is available and has been applied in Linux kernel versions 5.15.222, 6.1.189, 6.3, and related commits. Users should upgrade to these fixed versions or later to mitigate the issue. No additional mitigation steps are required beyond applying the official kernel updates.
Description
A vulnerability in the Linux kernel's mlx5 Ethernet switch (E-Switch) component could lead to use-after-free and memory corruption during virtual port (vport) disable operations. The flaw occurs due to improper handling of multicast list repopulation during firmware fatal recovery, causing dangling pointers and potential kernel crashes. The issue has been fixed by reordering function calls to ensure proper clearing of multicast rules before changes are applied.
References
- git.kernel.org/stable/c/413e04adcc1fd263cf02b1b83b4a0dbdc66bcee9 (opens in a new tab)
- git.kernel.org/stable/c/2196f9d3358b00fcb28835a5fde14071f51ecb96 (opens in a new tab)
- git.kernel.org/stable/c/5a2b87dfceccf9065157a14a599d395c2b6281b8 (opens in a new tab)
- git.kernel.org/stable/c/69904608e25e8ba58111aadd9210892cf3876201 (opens in a new tab)
- git.kernel.org/stable/c/72cfcb79026cffb6490f5044153a841d360b0cfc (opens in a new tab)
- git.kernel.org/stable/c/668e050429c7ca688cf4e7112f97f0cd269d446b (opens in a new tab)
- git.kernel.org/stable/c/c0c6f4ba8a37688f7b4d4044898d88f0450d44c2 (opens in a new tab)