Strix
68.9K

CVE-2026-98236

Unknown

Last modified

CVE-2026-98236 is a vulnerability of currently unknown severity. 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).

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.

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= aa730a9905b7b079ef2fffdab7f15dbb842f5c7c, < 650af68435eaee783824457d2ef78cc5c03c1e88; >= aa730a9905b7b079ef2fffdab7f15dbb842f5c7c, < 350fd3125ee26b5243935fd9e2b4d162ffba430a; >= aa730a9905b7b079ef2fffdab7f15dbb842f5c7c, < dd136f1fdd1059f3bc25ede3a8def8f0ee151ce7; >= aa730a9905b7b079ef2fffdab7f15dbb842f5c7c, < 298659c3677bf622afa9d77549cb4a967f9541e9; >= aa730a9905b7b079ef2fffdab7f15dbb842f5c7c, < 02eba5f36d20283f144f75d47f0354a85e4f78f0; >= aa730a9905b7b079ef2fffdab7f15dbb842f5c7c, < 7e98216e9da08b79e07a514d2a4f7646f8c9ccb9; >= aa730a9905b7b079ef2fffdab7f15dbb842f5c7c, < 31550d585589fde1ae95bf7f7a8188b2d2fdf1c7
LinuxLinux5.15

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-98236?
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.
How severe is CVE-2026-98236?
Severity scoring for CVE-2026-98236 is pending analysis.
How do I fix CVE-2026-98236?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

View all 2026CVEs →

Are you affected by CVE-2026-98236?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST