CVE-2026-98238
net: wwan: t7xx: validate the netif index in t7xx_ccmni_recv_skb()
No known exploitation. EPSS puts it in the 7th percentile. Fixed versions are out.
What to do
Find your product and version, then upgrade to the build on the right.
- LinuxAffected: ≥ 05d19bf500f8281f574713479b04679fa226d0a3, < 7c2fe308bda5a7e6222d7f0c3c311991372baab4Upgrade to: 7c2fe308bda5a7e6222d7f0c3c311991372baab4Affected: ≥ 05d19bf500f8281f574713479b04679fa226d0a3, < fba45070e25abdae08bcaebfadeef050dc39e208Upgrade to: fba45070e25abdae08bcaebfadeef050dc39e208Affected: ≥ 05d19bf500f8281f574713479b04679fa226d0a3, < e1b0609b1a40da03e385be290853a604eb4c3fb9Upgrade to: e1b0609b1a40da03e385be290853a604eb4c3fb9Affected: ≥ 05d19bf500f8281f574713479b04679fa226d0a3, < 9dbf13de4edff6fbc1f7ad9c4040326b6ed599adUpgrade to: 9dbf13de4edff6fbc1f7ad9c4040326b6ed599ad + 2 more branchesStated by: CVE record
Versions as the sources state them. Full version matrix after sign-in
What it is
From the CVE record
In the Linux kernel, the following vulnerability has been resolved: net: wwan: t7xx: validate the netif index in t7xx_ccmni_recv_skb() The netif index carried in the DPMAIF PIT header is five bits wide, but ccmni_inst[] only has room for NIC_DEV_MAX (21) entries. t7xx_ccmni_recv_skb() indexes the array without a bounds check, so indexes 21 to 31 read past it. The out-of-bounds value lands in the callback table that follows the array, which is never NULL, so the existing !ccmni check does not catch it and the driver dereferences whatever sits there as a struct t7xx_ccmni. Drop the skb when the index is out of range. Verified in a QEMU guest with a fault injector setting the netif index to 25: the unpatched driver reads a value past ccmni_inst[], which lands in the callback table, and dereferences it far enough to queue the skb. With this check the packet is dropped. Well-formed traffic on index 0 is unaffected. Changes in v2: none.
In plain language
No plain-language summary for this CVE yet.
Exploitation
Where each signal puts this CVE on the scale from published to confirmed exploited.
- CISA KEV
Not in the catalog. CISA has not confirmed exploitation.
- Public exploits
No public exploit or proof of concept found in the sources we track.
- EPSS
0.2% chance of exploitation activity in the next 30 days, which ranks it in the 7th percentile of scored CVEs.
Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.
Lifecycle
2 events over 0 days, from the signal feeds we watch.
- Publishedrecord updated
Affected products
Sources
References in the record
- git.kernel.org/stable/c/7c2fe308bda5a7e6222d7f0c3c311991372baab4
- git.kernel.org/stable/c/fba45070e25abdae08bcaebfadeef050dc39e208
- git.kernel.org/stable/c/e1b0609b1a40da03e385be290853a604eb4c3fb9
And 3 more references. See all after sign-in
In the news
Watch the software you run.
My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.
We'll flag the next CVE, public exploit or patch for Linux, not every advisory.
A free account adds
- The full version matrix and every affected product
- Exploit links, proofs of concept and Metasploit modules
- Email alerts for the products you watch
- The same data over REST API, MCP and CLI