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-43092xsk: validate MTU against usable frame size on bind

Description

In the Linux kernel, the following vulnerability has been resolved: xsk: validate MTU against usable frame size on bind AF_XDP bind currently accepts zero-copy pool configurations without verifying that the device MTU fits into the usable frame space provided by the UMEM chunk. This becomes a problem since we started to respect tailroom which is subtracted from chunk_size (among with headroom). 2k chunk size might not provide enough space for standard 1500 MTU, so let us catch such settings at bind time. Furthermore, validate whether underlying HW will be able to satisfy configured MTU wrt XSK's frame size multiplied by supported Rx buffer chain length (that is exposed via net_device::xdp_zc_max_segs).

Timeline

  1. ID reserved

    By Linux

  2. · 5 days later

    Published

  3. · 5 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

CVSS scores of CVE-2026-43092, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.12% · top 98% of all CVEs (16 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 24ea50127ecf0efe819c1f6230add27abc6ca9d9 – < a55793e5a97d4e39bdb380873a9780fe0010bff6
    • affected 24ea50127ecf0efe819c1f6230add27abc6ca9d9 – < f669d60db11dbabb96279f2b20f9d1cba43cddb2
    • affected 24ea50127ecf0efe819c1f6230add27abc6ca9d9 – < 25e1e91a8da819924df0b16e3812d7b24c8ce133
    • affected 24ea50127ecf0efe819c1f6230add27abc6ca9d9 – < b2f4daa6422fd6cc0cec969794dab4a88ea4cea1
    • affected 24ea50127ecf0efe819c1f6230add27abc6ca9d9 – < 36ee60b569ba0dfb6f961333b90d19ab5b323fa9
  • Linux · Linux

    • affected 6.6
    • unaffected < 6.6
    • unaffected 6.6.136 – ≤ 6.6.*
    • unaffected 6.12.83 – ≤ 6.12.*
    • unaffected 6.18.24 – ≤ 6.18.*
    • unaffected 6.19.14 – ≤ 6.19.*
    • unaffected 7.0 – ≤ *

References

References5

Sources

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

Badge for a README or a ticket

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

Record last updated .