CVE-2026-99043: Linux kernel · ice: fix metadata_dst refcount handling on representor teardown
Source GCVE Database
Not known to be exploited · fixed in beb05f484a1e4a5a66e3678e4b7f3147f651c080 : patch Linux kernel soon.
Data as of 26 Oct 2026, 13:47 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in beb05f484a1e4a5a66e3678e4b7f3147f651c080, 58858b8f14803a7eeac297b3ce20f3b21bf2ff66, 6f5544f53f1e58ea8a49fb9f9158d5793b9205b0 +2
Exploitation evidence
Disclosed: evidence found.
CVE published 23 Oct 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– |
Description
In the Linux kernel, the following vulnerability has been resolved: ice: fix metadata_dst refcount handling on representor teardown ice_eswitch_release_repr() uses metadata_dst_free() to release the representor's metadata_dst. metadata_dst_free() directly frees the underlying memory without checking the dst_entry refcount. When ice_eswitch_port_start_xmit() processes a packet, it takes a reference via dst_hold() and attaches the metadata_dst to the skb. If the representor is torn down while packets are still queued on the lower device (e.g. in a qdisc), the metadata_dst is freed while references are still held. Use dst_release() instead, which correctly decrements the refcount and only frees the object when all references are dropped. The dst subsystem already handles metadata_dst cleanup in dst_destroy() when DST_METADATA is set. Other drivers sharing this pattern (nfp, airoha, bnxt) already use dst_release() for their metadata_dst lifecycle.
References
- nvd.nist.gov/vuln/detail/CVE-2026-99043 (opens in a new tab)
- git.kernel.org/stable/c/1f263235651775f93c15d90c9f25c3f4a4ef6512 (opens in a new tab)
- git.kernel.org/stable/c/58858b8f14803a7eeac297b3ce20f3b21bf2ff66 (opens in a new tab)
- git.kernel.org/stable/c/5e4d20db5179e83a4948927bc39e489a9a83256d (opens in a new tab)
- git.kernel.org/stable/c/6f5544f53f1e58ea8a49fb9f9158d5793b9205b0 (opens in a new tab)
- git.kernel.org/stable/c/beb05f484a1e4a5a66e3678e4b7f3147f651c080 (opens in a new tab)