CVE-2025-38123: net: wwan: t7xx: Fix napi rx poll issue
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.47% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 66542e9430c625f878a5b5dc0fe41e3458d614bf, 905fe0845bb27e4eed2ca27ea06e6c4847f1b2b1, cc89f457d9133a558d4e8ef26dc20843c2d12073; azl3 kernel 6.6.92.2-2 on Azure Linux 3.0 6.6.96.1-1.
- Severity is disputed: the assigning authority (CNA) scores it 9.8, NVD 5.5.
Low priority for now. Upgrade to Linux Linux 66542e9430c625f878a5b5dc0fe41e3458d614bf, 905fe0845bb27e4eed2ca27ea06e6c4847f1b2b1, cc89f457d9133a558d4e8ef26dc20843c2d12073; azl3 kernel 6.6.92.2-2 on Azure Linux 3.0 6.6.96.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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>
- Published
- Jul 3, 2025
- Updated
- Aug 5, 2026
- EPSS
- 0.4% · 41th percentile
- CWE
- CWE-476
Report tools
Action score
22
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
CNA vs NVD score
- NVD
- 5.5
- CNA · Linux
- 9.8
- 4.3 point gap
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 6.2affected
- 5545b7b9f294de7f95ec6a7cb1de0db52296001c and later · before cc89f457d9133a558d4e8ef26dc20843c2d12073affected · git
- 5545b7b9f294de7f95ec6a7cb1de0db52296001c and later · before e2df04e69c3f10b412f54be036dd0ed3b14756cfaffected · git
- 5545b7b9f294de7f95ec6a7cb1de0db52296001c and later · before 66542e9430c625f878a5b5dc0fe41e3458d614bfaffected · git
- 5545b7b9f294de7f95ec6a7cb1de0db52296001c and later · before 905fe0845bb27e4eed2ca27ea06e6c4847f1b2b1affected · git
- before 6.2not affected · semver
- 6.6.94 and later · up to and including 6.6.*not affected · semver
- 6.12.34 and later · up to and including 6.12.*not affected · semver
- 6.15.3 and later · up to and including 6.15.*not affected · semver
- 6.16 and laternot affected · original_commit_for_fix
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel6.2 and later · before 6.6.94
- linux linux kernel6.7 and later · before 6.12.34
- linux linux kernel6.13 and later · before 6.15.3
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:13 | linux | before 6.12.35-1 | 6.12.35-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2025-38119Jul 3, 2025 · scsi: core: ufs: Fix a hang in the error handler22Monitor
- ← EarlierCVE-2025-38121Jul 3, 2025 · wifi: iwlwifi: mld: avoid panic on init failure22Monitor
- Later →CVE-2025-38124Jul 3, 2025 · net: fix udp gso skb_segment after pull from frag_list22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 66542e9430c625f878a5b5dc0fe41e3458d614bf | Vendor (CNA) |
| Linux Linux | 905fe0845bb27e4eed2ca27ea06e6c4847f1b2b1 | Vendor (CNA) |
| Linux Linux | cc89f457d9133a558d4e8ef26dc20843c2d12073 | Vendor (CNA) |
| Linux Linux | e2df04e69c3f10b412f54be036dd0ed3b14756cf | Vendor (CNA) |
| azl3 kernel 6.6.92.2-2 on Azure Linux 3.0 | 6.6.96.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.12.35-1 · Debian:13 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-476 · NULL Pointer DereferenceCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.