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-23377ice: change XDP RxQ frag_size from DMA write length to xdp.frame_sz

Description

In the Linux kernel, the following vulnerability has been resolved: ice: change XDP RxQ frag_size from DMA write length to xdp.frame_sz The only user of frag_size field in XDP RxQ info is bpf_xdp_frags_increase_tail(). It clearly expects whole buff size instead of DMA write size. Different assumptions in ice driver configuration lead to negative tailroom. This allows to trigger kernel panic, when using XDP_ADJUST_TAIL_GROW_MULTI_BUFF xskxceiver test and changing packet size to 6912 and the requested offset to a huge value, e.g. XSK_UMEM__MAX_FRAME_SIZE * 100. Due to other quirks of the ZC configuration in ice, panic is not observed in ZC mode, but tailroom growing still fails when it should not. Use fill queue buffer truesize instead of DMA write size in XDP RxQ info. Fix ZC mode too by using the new helper.

Timeline

  1. ID reserved

    By Linux

  2. · 2 months later

    Published

  3. · 8 months 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-23377, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.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.17% · top 94% of all CVEs (17 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
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 2fba7dc5157b6f85dbf1b8e26e63a724db1f3d79 – < f2b29bbe355221a65c3eccf9500e5e33e4f1cb5c
    • affected 2fba7dc5157b6f85dbf1b8e26e63a724db1f3d79 – < 6aed180a44b1c0a3971107fa052a41b03acdb31e
    • affected 2fba7dc5157b6f85dbf1b8e26e63a724db1f3d79 – < 2a2927e95cf1b8efb15bcb741bbd06c9bb0537b7
    • affected 2fba7dc5157b6f85dbf1b8e26e63a724db1f3d79 – < b0f05100e8795aadd1c0606bae9caefbda070d63
    • affected 2fba7dc5157b6f85dbf1b8e26e63a724db1f3d79 – < e142dc4ef0f451b7ef99d09aaa84e9389af629d7
  • Linux · Linux

    • affected 6.3
    • unaffected < 6.3
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.114 – ≤ 6.12.*
    • unaffected 6.18.60 – ≤ 6.18.*
    • unaffected 6.19.7 – ≤ 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-23377 badge
[![CVE-2026-23377](https://cveledger.app/badge/CVE-2026-23377.svg)](https://cveledger.app/cve/CVE-2026-23377)

Record last updated .