Skip to main content
VulnerabilityPublished Updated

CVE-2026-90086: Linux kernel · xsk: honor XDP_TX_METADATA in zero-copy path

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · fixed in bf9387488d6394845076928c6ca5315ce5d84f54 : update Linux kernel when convenient.

Data as of 26 Oct 2026, 13:47 UTC

Severity
Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

EPSS
0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in bf9387488d6394845076928c6ca5315ce5d84f54, a6e4b9a6deb9362ef7a0706c70d674e92fe1411a, 53a5b262d706b572840cbe8feae392538077ee19 +1

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 Linux kernel to bf9387488d6394845076928c6ca5315ce5d84f54, a6e4b9a6deb9362ef7a0706c70d674e92fe1411a, 53a5b262d706b572840cbe8feae392538077ee19 or 8ba0d143e471c85f8a116707c0b42bf046b0a7b3.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 48eb03dd26304c24f03bdbb9382e89c8564e71df, < bf9387488d6394845076928c6ca5315ce5d84f54
Fixed in
  • bf9387488d6394845076928c6ca5315ce5d84f54
LinuxLinuxAffected
  • ≥ 48eb03dd26304c24f03bdbb9382e89c8564e71df, < a6e4b9a6deb9362ef7a0706c70d674e92fe1411a
Fixed in
  • a6e4b9a6deb9362ef7a0706c70d674e92fe1411a
LinuxLinuxAffected
  • ≥ 48eb03dd26304c24f03bdbb9382e89c8564e71df, < 53a5b262d706b572840cbe8feae392538077ee19
Fixed in
  • 53a5b262d706b572840cbe8feae392538077ee19
LinuxLinuxAffected
  • ≥ 48eb03dd26304c24f03bdbb9382e89c8564e71df, < 8ba0d143e471c85f8a116707c0b42bf046b0a7b3
Fixed in
  • 8ba0d143e471c85f8a116707c0b42bf046b0a7b3
LinuxLinuxAffected
  • =6.8
Fixed in–

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.

References

Community reviews

Loading reviews…