CVE-2026-98236

Unknown

Description

In the Linux kernel, the following vulnerability has been resolved: net: wwan: mhi_wwan_mbim: check skb_copy_bits() return value mhi_mbim_rx() ignores the return value of skb_copy_bits() when it copies each datagram out of the NTB. The datagram offset and length come from the DPE, which is only checked to lie within the NTB itself, so a modem can point a datagram outside the received skb. The copy then fails and the freshly allocated skbn is passed to netif_rx() with its uninitialized contents still in place, leaking kernel heap memory into the network stack. Free the skb and account an error when the copy fails. Verified in a QEMU guest with a fault injector pointing a DPE outside the received NTB: the copy fails, and the unpatched driver hands the uninitialized skbn to the network stack (observed as "unknown protocol" on bytes that were never written). With this check the failed datagram is dropped and counted as an rx error. Changes in v2: factor the free-and-count sequence out into mhi_mbim_rx_drop(), shared with the unknown-protocol path, as suggested by Loic Poulain.

SeverityUnknown
CVSS—
Exploit probability—
ProductLinux
PublishedOct 6, 2026
First seenOct 6, 2026

How to fix

Update
  • Linux Linux650af68435eaee783824457d2ef78cc5c03c1e88, 350fd3125ee26b5243935fd9e2b4d162ffba430a, dd136f1fdd1059f3bc25ede3a8def8f0ee151ce7, 298659c3677bf622afa9d77549cb4a967f9541e9, 02eba5f36d20283f144f75d47f0354a85e4f78f0, 7e98216e9da08b79e07a514d2a4f7646f8c9ccb9, 31550d585589fde1ae95bf7f7a8188b2d2fdf1c7 or later

Affected products

ProductAffected versionsFixed in
Linux Linuxaa730a9905b7b079ef2fffdab7f15dbb842f5c7c ≤ v < 650af68435eaee783824457d2ef78cc5c03c1e88, aa730a9905b7b079ef2fffdab7f15dbb842f5c7c ≤ v < 350fd3125ee26b5243935fd9e2b4d162ffba430a, aa730a9905b7b079ef2fffdab7f15dbb842f5c7c ≤ v < dd136f1fdd1059f3bc25ede3a8def8f0ee151ce7, aa730a9905b7b079ef2fffdab7f15dbb842f5c7c ≤ v < 298659c3677bf622afa9d77549cb4a967f9541e9, aa730a9905b7b079ef2fffdab7f15dbb842f5c7c ≤ v < 02eba5f36d20283f144f75d47f0354a85e4f78f0, aa730a9905b7b079ef2fffdab7f15dbb842f5c7c ≤ v < 7e98216e9da08b79e07a514d2a4f7646f8c9ccb9, aa730a9905b7b079ef2fffdab7f15dbb842f5c7c ≤ v < 31550d585589fde1ae95bf7f7a8188b2d2fdf1c7, 5.15650af68435eaee783824457d2ef78cc5c03c1e88, 350fd3125ee26b5243935fd9e2b4d162ffba430a, dd136f1fdd1059f3bc25ede3a8def8f0ee151ce7, 298659c3677bf622afa9d77549cb4a967f9541e9, 02eba5f36d20283f144f75d47f0354a85e4f78f0, 7e98216e9da08b79e07a514d2a4f7646f8c9ccb9, 31550d585589fde1ae95bf7f7a8188b2d2fdf1c7

Check your version

Choose the product and enter the version you run to see whether it falls in the affected range.

In the Intelligence 360 plan

Attack Surface Management

See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.