Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-99043ice: fix metadata_dst refcount handling on representor teardown

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.

Timeline

  1. ID reserved

    By Linux

  2. · 28 days later

    Published

  3. · 7 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.18% · top 92% of all CVEs (12 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected f5396b8a663f7a78ee5b75a47ee524b40795b265 – < 41f0d9ab158fb51f34bded5f8a40918e4f70b2b6
    • affected f5396b8a663f7a78ee5b75a47ee524b40795b265 – < 1f263235651775f93c15d90c9f25c3f4a4ef6512
    • affected f5396b8a663f7a78ee5b75a47ee524b40795b265 – < 6f5544f53f1e58ea8a49fb9f9158d5793b9205b0
    • affected f5396b8a663f7a78ee5b75a47ee524b40795b265 – < beb05f484a1e4a5a66e3678e4b7f3147f651c080
    • affected f5396b8a663f7a78ee5b75a47ee524b40795b265 – < 5e4d20db5179e83a4948927bc39e489a9a83256d
    • affected f5396b8a663f7a78ee5b75a47ee524b40795b265 – < 58858b8f14803a7eeac297b3ce20f3b21bf2ff66
  • Linux · Linux

    • affected 5.16
    • unaffected < 5.16
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.113 – ≤ 6.12.*
    • unaffected 6.18.57 – ≤ 6.18.*
    • unaffected 7.2.11 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-99043 badge
[![CVE-2026-99043](https://cveledger.app/badge/CVE-2026-99043.svg)](https://cveledger.app/cve/CVE-2026-99043)

Record last updated .