CVE-2025-38123: net: wwan: t7xx: Fix napi rx poll issue
In the Linux kernel, the following vulnerability has been resolved:
net: wwan: t7xx: Fix napi rx poll issue
When driver handles the napi rx polling requests, the netdev might
have been released by the dellink logic triggered by the disconnect
operation on user plane. However, in the logic of processing skb in
polling, an invalid netdev is still being used, which causes a panic.
BUG: kernel NULL pointer dereference, address: 00000000000000f1
Oops: 0000 [#1] PREEMPT SMP NOPTI
RIP: 0010:dev_gro_receive+0x3a/0x620
[...]
Call Trace:
<IRQ>
? __die_body+0x68/0xb0
? page_fault_oops+0x379/0x3e0
? exc_page_fault+0x4f/0xa0
? asm_exc_page_fault+0x22/0x30
? __pfx_t7xx_ccmni_recv_skb+0x10/0x10 [mtk_t7xx (HASH:1400 7)]
? dev_gro_receive+0x3a/0x620
napi_gro_receive+0xad/0x170
t7xx_ccmni_recv_skb+0x48/0x70 [mtk_t7xx (HASH:1400 7)]
t7xx_dpmaif_napi_rx_poll+0x590/0x800 [mtk_t7xx (HASH:1400 7)]
net_rx_action+0x103/0x470
irq_exit_rcu+0x13a/0x310
sysvec_apic_timer_interrupt+0x56/0x90
</IRQ>
Security readout for executives and security teams
Plain-English summary
A race during mobile-broadband disconnection can leave the Linux MediaTek t7xx WWAN driver processing received data through a network device that has already been released. The documented result is a NULL-pointer dereference and kernel panic, causing system disruption. Exposure appears limited to systems using this driver and the affected kernel code.
Executive priority
Treat as urgent for systems using MediaTek t7xx mobile broadband, especially where unexpected reboot or downtime affects critical operations. It is not supported as an organization-wide Linux emergency without confirming driver presence. The supplied critical score warrants attention, but the public technical evidence currently establishes kernel panic rather than complete system compromise.
Technical view
During NAPI receive polling, user-plane disconnect logic can release the netdev while queued packet processing continues. The t7xx receive path then passes an invalid netdev into GRO processing, producing a NULL-pointer dereference in dev_gro_receive. The supplied description demonstrates an availability failure; it does not establish the claimed confidentiality or integrity impacts.
Likely exposure
Potentially exposed systems run Linux with the MediaTek t7xx WWAN driver and exercise its user-plane disconnect path while receive polling is active. The supplied affected-version metadata includes 6.2, 6.6.94, 6.12.34, 6.15.3, and 6.16, but does not provide clear affected-to-fixed ranges. Distribution-specific confirmation is required.
Exploitation context
The bundle marks this CVE as absent from KEV and provides no evidence of active exploitation or a public exploit. The documented trigger involves a timing-dependent disconnect and receive-polling race. Remote reachability and attacker-controlled confidentiality or integrity impact are not demonstrated by the supplied sources.
Researcher notes
The core issue appears to be netdev lifetime synchronization between disconnect-driven dellink processing and NAPI receive polling. Stable-kernel commit references indicate fixes exist, but the bundle does not explain branch mapping or exact fixed releases. The CVSS 9.8 vector claims full confidentiality, integrity, and availability impact, while the description and trace substantiate availability impact only.
Mitigation direction
Apply a distribution or kernel update incorporating the referenced stable fixes.
Confirm fixed package versions with the operating-system or appliance vendor.
Limit use of affected t7xx WWAN interfaces until updating, where operationally practical.
Prioritize resilient or safety-sensitive systems where a kernel panic has significant consequences.
Validation and detection
Inventory systems loading or shipping the MediaTek t7xx WWAN driver.
Map deployed kernel builds against vendor advisories and the referenced stable commits.
Review kernel logs for t7xx, dev_gro_receive, or NULL-pointer panic traces.
Safely test WWAN disconnect handling in a controlled, non-production environment after updating.
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-2025-38123 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
5Source 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.