LiveActive security incident?Get immediate response
CVE Record

CVE-2026-23172: net: wwan: t7xx: fix potential skb->frags overflow in RX path

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.

HighCVSS 8.4Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-23172 is a Linux kernel memory-corruption flaw in the t7xx WWAN receive path. Malicious, buggy, or compromised modem firmware could trigger excessive packet fragments, potentially causing kernel crashes or broader memory corruption.

Executive priority

Treat as high priority for fleets with cellular WWAN Linux endpoints. Broad enterprise urgency is lower where t7xx hardware is absent, but kernel memory corruption warrants timely patch validation.

Technical view

t7xx_dpmaif_set_frag_to_skb() added receive page fragments without checking MAX_SKB_FRAGS before skb_add_rx_frag(). The fix adds a bounds check before DMA unmapping to avoid skb_shinfo(skb)->frags[] overflow, page leaks, and double DMA unmap during teardown.

Likely exposure

Exposure appears limited to Linux systems using affected kernels with the t7xx WWAN driver and relevant modem hardware or firmware paths. Distribution backports may change practical exposure, so kernel package status matters more than upstream version strings alone.

Exploitation context

The CVE is not listed as KEV in the provided bundle, and no cited source states active exploitation. The trigger described is excessive fragments from modem firmware, making exploitability dependent on firmware behavior or compromise.

Researcher notes

The vulnerability was found by static analysis and compared with a prior mt76 fragment-overflow fix. The source explicitly says normal MTU and BAT sizing should not require extra fragments, so abnormal firmware behavior is central to risk.

Mitigation direction

  • Update to a kernel containing the referenced stable fixes.
  • Check Linux distribution advisories for backported t7xx fixes.
  • Prioritize systems using WWAN modem hardware relying on t7xx.
  • Restrict untrusted firmware update paths where operationally possible.
  • Monitor kernel logs for modem or t7xx receive-path instability.

Validation and detection

  • Inventory Linux kernel versions and enabled t7xx WWAN driver usage.
  • Map installed kernels to vendor advisories or referenced stable commits.
  • Confirm whether affected devices include compatible WWAN modem hardware.
  • Review crash reports for t7xx, DPMAIF, skb, or DMA teardown indicators.
  • Verify remediation through package metadata, not only uname output.
Prepared
Confidence
medium
Sources
7

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.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.4 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

ScoreVersionSeverityVectorExploitImpactSource
8.4CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H2.55.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

8.4High
CVSS 3.1 vector shape for CVE-2026-23172Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxd642b012df70a76dd5723f2d426b40bffe83ac49, d642b012df70a76dd5723f2d426b40bffe83ac49, d642b012df70a76dd5723f2d426b40bffe83ac49, d642b012df70a76dd5723f2d426b40bffe83ac49, d642b012df70a76dd5723f2d426b40bffe83ac49unaffected
LinuxLinux5.19, 0, 6.1.162, 6.6.123, 6.12.69, 6.18.9, 6.19affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.