CVE-2026-98016: Linux kernel · net/mlx5e: Fix use-after-free race in sample_restore_put()
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in cdf920e44cbbee1900c66f002fb50afee20977d4 : patch Linux kernel soon.
Data as of 26 Oct 2026, 14:05 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 cdf920e44cbbee1900c66f002fb50afee20977d4, af3aef0245abbab5e9f6302e7a7d6407187afb71, 72324da8eeca269db9196c2a555abf72eb0385c5 +4
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
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
AI-suggested
A fix for this vulnerability is available and has been applied in several Linux kernel commits. Users should update to a Linux kernel version that includes these fixes. No additional mitigation steps are indicated by the vendor advisory.
Description
A use-after-free race condition was identified and fixed in the Linux kernel's net/mlx5e driver within the sample_restore_put() function. The flaw occurs during concurrent teardown of TC sample rules sharing the same restore context, where a thread may access a freed restore object after another thread has completed cleanup. The fix involves using the refcount decrement result while holding the restore_lock to safely determine if cleanup is required.
References
- git.kernel.org/stable/c/cdf920e44cbbee1900c66f002fb50afee20977d4 (opens in a new tab)
- git.kernel.org/stable/c/308e1cbb0d9712081f90860fe839ccb47bc196ee (opens in a new tab)
- git.kernel.org/stable/c/8267e46d14e847e80e0aebe366d348e8a484a619 (opens in a new tab)
- git.kernel.org/stable/c/3efd1a1938cbb33c53b0d75e55b6c0fe2ebad79a (opens in a new tab)
- git.kernel.org/stable/c/72324da8eeca269db9196c2a555abf72eb0385c5 (opens in a new tab)
- git.kernel.org/stable/c/1daecd76ab9e5f055fe3970462410ad1d40bd177 (opens in a new tab)
- git.kernel.org/stable/c/af3aef0245abbab5e9f6302e7a7d6407187afb71 (opens in a new tab)