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.
Security readout for executives and security teams
Plain-English summary
A Linux WWAN driver can write beyond a kernel fragment array when modem firmware supplies an unexpectedly fragmented packet. This may corrupt kernel memory, crash the device, or cause other unpredictable behavior. Normal modem traffic should not require this fragmentation, so practical risk is concentrated in systems using the t7xx driver with buggy, malicious, or compromised firmware.
Executive priority
Identify exposed devices immediately and patch confirmed affected systems on an accelerated schedule. Prioritize operationally important WWAN-enabled devices. The potential impact is severe kernel compromise or outage, but the supplied evidence does not support treating this as an internet-wide emergency or an actively exploited vulnerability.
Technical view
The t7xx DPMAIF receive path added page fragments to skb_shinfo(skb)->frags[] without enforcing MAX_SKB_FRAGS. Excess fragments could overflow the array and corrupt adjacent kernel memory. The fix checks the fragment count before skb_add_rx_frag() and before DMA unmapping, preventing overflow while avoiding page leaks and double unmapping during teardown.
Likely exposure
Exposure is limited to Linux systems using the affected t7xx WWAN receive path. The supplied record lists 5.19, 6.1.162, 6.6.123, 6.12.69, 6.18.9, and 6.19 as affected, but also contains an anomalous version entry of "0". Confirm applicability through the device or Linux distribution vendor.
Exploitation context
The CVE is not listed as KEV, and the supplied sources provide no evidence of active exploitation. Triggering requires the modem firmware to send packets with excessive fragments, contrary to normal stated MTU and buffer conditions. The plausible threat scenarios are faulty, malicious, or previously compromised modem firmware; broader attacker reachability is not established.
Researcher notes
Static analysis identified the flaw by comparison with a similar driver issue. The source describes potential memory corruption and undefined behavior, not a demonstrated exploitation outcome. Fix ordering matters: the bounds check precedes DMA unmapping to prevent resource leakage and double unmapping. Version metadata is imperfect, so commit or vendor-package verification is more reliable than the anomalous version list alone.
Mitigation direction
Install a vendor-supported kernel update containing the cited fragment bounds-check fix.
Check device and Linux distribution advisories for corrected package versions and deployment guidance.
Prioritize systems actively using the t7xx WWAN driver and affected kernel branches.
Maintain vendor-supported modem firmware and protect its update process against unauthorized modification.
Validation and detection
Inventory systems for the t7xx WWAN driver and determine whether it is active.
Compare installed kernel versions with vendor advisories and the supplied affected-version data.
Verify the deployed kernel contains the MAX_SKB_FRAGS check before skb_add_rx_frag().
Confirm the installed update incorporates the applicable cited Linux stable fix.
Review device logs for unexplained kernel crashes or memory-corruption symptoms involving the t7xx receive path.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2026-23172 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
0ADP providers
6Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.