CVE-2026-98237
net: wwan: mhi_wwan_mbim: guard against a cyclic NDP chain
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: ≥ aa730a9905b7b079ef2fffdab7f15dbb842f5c7c, < 3ed36ee1b29b028f6bc2ebe100152f61a33df05aUpgrade to: 3ed36ee1b29b028f6bc2ebe100152f61a33df05aAffected: ≥ aa730a9905b7b079ef2fffdab7f15dbb842f5c7c, < e4b2c7b50d4f4aa1ddfff731b136d65f65b2b526Upgrade to: e4b2c7b50d4f4aa1ddfff731b136d65f65b2b526Affected: ≥ aa730a9905b7b079ef2fffdab7f15dbb842f5c7c, < 19b5e8dd884a530d04482e1a8e547f43cad17ed7Upgrade to: 19b5e8dd884a530d04482e1a8e547f43cad17ed7Affected: ≥ aa730a9905b7b079ef2fffdab7f15dbb842f5c7c, < 24ade82d6d993274e99c2c6998848751c35292e7Upgrade to: 24ade82d6d993274e99c2c6998848751c35292e7 + 3 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: mhi_wwan_mbim: guard against a cyclic NDP chain The NDP traversal in mhi_mbim_rx() only stops when wNextNdpIndex is zero. Nothing requires the offsets to advance, so a modem that points an NDP at itself, or at an earlier NDP, keeps the loop spinning forever on one CPU. Break out when the next NDP offset is not larger than the current one. Verified in a QEMU guest with a fault injector feeding the driver's receive callback an NTB whose single NDP points at itself: the unpatched driver spins in mhi_mbim_rx() with one CPU pinned at 100% and the thread never returns. With this check the loop terminates within one iteration. Changes in v2: move the non-increasing check to the wNextNdpIndex retrieval site, as suggested by Loic Poulain, instead of tracking the previous offset in a separate variable.
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/3ed36ee1b29b028f6bc2ebe100152f61a33df05a
- git.kernel.org/stable/c/e4b2c7b50d4f4aa1ddfff731b136d65f65b2b526
- git.kernel.org/stable/c/19b5e8dd884a530d04482e1a8e547f43cad17ed7
And 4 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