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-23172net: wwan: t7xx: fix potential skb->frags overflow in RX path

Description

In the Linux kernel, the following vulnerability has been resolved: net: wwan: t7xx: fix potential skb->frags overflow in RX path When receiving data in the DPMAIF RX path, the t7xx_dpmaif_set_frag_to_skb() function adds page fragments to an skb without checking if the number of fragments has exceeded MAX_SKB_FRAGS. This could lead to a buffer overflow in skb_shinfo(skb)->frags[] array, corrupting adjacent memory and potentially causing kernel crashes or other undefined behavior. This issue was identified through static code analysis by comparing with a similar vulnerability fixed in the mt76 driver commit b102f0c522cf ("mt76: fix array overflow on receiving too many fragments for a packet"). The vulnerability could be triggered if the modem firmware sends packets with excessive fragments. While under normal protocol conditions (MTU 3080 bytes, BAT buffer 3584 bytes), a single packet should not require additional fragments, the kernel should not blindly trust firmware behavior. Malicious, buggy, or compromised firmware could potentially craft packets with more fragments than the kernel expects. Fix this by adding a bounds check before calling skb_add_rx_frag() to ensure nr_frags does not exceed MAX_SKB_FRAGS. The check must be performed before unmapping to avoid a page leak and double DMA unmap during device teardown.

Timeline

  1. ID reserved

    By Linux

  2. · 32 days 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-23172, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High8.4CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.20% · top 90% of all CVEs (16 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: total
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected d642b012df70a76dd5723f2d426b40bffe83ac49 – < f9747a7521a48afded5bff2faf1f2dcfff48c577
    • affected d642b012df70a76dd5723f2d426b40bffe83ac49 – < 2a0522f564acd34442652ea083091c329fa7c5d5
    • affected d642b012df70a76dd5723f2d426b40bffe83ac49 – < af4b8577d0b388cc3d0039eb0cdd9ca5bbbc9276
    • affected d642b012df70a76dd5723f2d426b40bffe83ac49 – < 2c0fb0f60bc1545c52da61bc6bd4855c1e7814ba
    • affected d642b012df70a76dd5723f2d426b40bffe83ac49 – < f0813bcd2d9d97fdbdf2efb9532ab03ae92e99e6
  • Linux · Linux

    • affected 5.19
    • unaffected < 5.19
    • unaffected 6.1.162 – ≤ 6.1.*
    • unaffected 6.6.123 – ≤ 6.6.*
    • unaffected 6.12.69 – ≤ 6.12.*
    • unaffected 6.18.9 – ≤ 6.18.*
    • unaffected 6.19 – ≤ *

References

References5

Sources

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

Badge for a README or a ticket

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

Record last updated .