Answer in brief
CVE-2026-23172 records a High severity (CVSS 8.4) vulnerability in net: wwan: t7xx: fix potential skb->frags overflow in RX path. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 8.4. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=d642b012df70a76dd5723f2d426b40bffe83ac49 <f9747a7521a48afded5bff2faf1f2dcfff48c577 || >=d642b012df70a76dd5723f2d426b40bffe83ac49 <2a0522f564acd34442652ea083091c329fa7c5d5 || >=d642b012df70a76dd5723f2d426b40bffe83ac49 <af4b8577d0b388cc3d0039eb0cdd9ca5bbbc9276 || >=d642b012df70a76dd5723f2d426b40bffe83ac49 <2c0fb0f60bc1545c52da61bc6bd4855c1e7814ba || >=d642b012df70a76dd5723f2d426b40bffe83ac49 <f0813bcd2d9d97fdbdf2efb9532ab03ae92e99e6 | f9747a7521a48afded5bff2faf1f2dcfff48c577, 2a0522f564acd34442652ea083091c329fa7c5d5, af4b8577d0b388cc3d0039eb0cdd9ca5bbbc9276, 2c0fb0f60bc1545c52da61bc6bd4855c1e7814ba, f0813bcd2d9d97fdbdf2efb9532ab03ae92e99e6 |
| Linux/Linuxgeneric | 5.19 | Not reported |
Published upstream
Feb 14, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 16, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 16, 2026
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.
Quoted source text, attributed separately from HOL analysis.