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-90086xsk: honor XDP_TX_METADATA in zero-copy path

Description

In the Linux kernel, the following vulnerability has been resolved: xsk: honor XDP_TX_METADATA in zero-copy path The zero-copy path reads TX metadata whenever the UMEM has metadata space, even if the descriptor does not set XDP_TX_METADATA. Pass descriptor options through the metadata helpers and ignore metadata unless the option is set. This does not fix the existing per-WQE metadata handling for mlx5 MPWQEs. Only the descriptor that starts a session passes through xsk_tx_metadata_request() and configures offload state shared by the batch. Metadata on descriptors joining an open session is therefore not validated and does not configure its requested offloads. In addition, a non-NULL metadata pointer from such a descriptor is treated as a timestamp completion request even when XDP_TXMD_FLAGS_TIMESTAMP is not set, so its metadata union can be overwritten with an unrequested timestamp. Fixing mixed metadata states within one MPWQE requires a separate change.

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 34 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.21% · top 89% of all CVEs (15 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 48eb03dd26304c24f03bdbb9382e89c8564e71df – < 8ba0d143e471c85f8a116707c0b42bf046b0a7b3
    • affected 48eb03dd26304c24f03bdbb9382e89c8564e71df – < 53a5b262d706b572840cbe8feae392538077ee19
    • affected 48eb03dd26304c24f03bdbb9382e89c8564e71df – < bf9387488d6394845076928c6ca5315ce5d84f54
    • affected 48eb03dd26304c24f03bdbb9382e89c8564e71df – < a6e4b9a6deb9362ef7a0706c70d674e92fe1411a
  • Linux · Linux

    • affected 6.8
    • unaffected < 6.8
    • unaffected 6.12.114 – ≤ 6.12.*
    • unaffected 6.18.52 – ≤ 6.18.*
    • unaffected 7.2.6 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References4

Sources

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

Badge for a README or a ticket

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

Record last updated .