CVE-2026-43495

net: wwan: t7xx: validate port_count against message length in t7xx_port_enum_msg_handler

CVE-2026-43495 is fixed in 14 products on 1 platform, first by DEBIAN-CVE-2026-43495, released May 27, 2026. It is not reported as exploited. Patch Radar priority: High.

High
CVSS
8.8
Moderate
Exploitation
None reported
No vendor assessment
CISA KEV
Not listed
Not in the Known Exploited Vulnerabilities catalog
EPSS
0.0032
24th percentile

In the Linux kernel, the following vulnerability has been resolved: net: wwan: t7xx: validate port_count against message length in t7xx_port_enum_msg_handler t7xx_port_enum_msg_handler() uses the modem-supplied port_count field as a loop bound over port_msg->data[] without checking that the message buffer contains sufficient data. A modem sending port_count=65535 in a 12-byte buffer triggers a slab-out-of-bounds read of up to 262140 bytes. Add a sizeof(*port_msg) check before accessing the port message header fields to guard against undersized messages. Add a struct_size() check after extracting port_count and before the loop. In t7xx_parse_host_rt_data(), guard the rt_feature header read with a remaining-buffer check before accessing data_len, validate feat_data_len against the actual remaining buffer to prevent OOB reads and signed integer overflow on offset. Pass msg_len from both call sites: skb->len at the DPMAIF path after skb_pull(), and the validated feat_data_len at the handshake path.

Where it's fixed

ProductFixed inFixReleased
Linux
dtb-aarch64 · opensuse-leap 16.0 6.12.0-160000.37.1 OPENSUSE-SU-2026:21555-1 Aug 12, 2026
kernel-64kb · opensuse-leap 16.0 6.12.0-160000.37.1 OPENSUSE-SU-2026:21555-1 Aug 12, 2026
kernel-64kb · sles 16.0 6.12.0-160000.37.1 SUSE-SU-2026:23231-1 Aug 11, 2026
kernel-azure · opensuse-leap 16.0 6.12.0-160000.37.1 OPENSUSE-SU-2026:21555-1 Aug 12, 2026
kernel-azure · sles 16.0 6.12.0-160000.37.1 SUSE-SU-2026:23231-1 Aug 11, 2026
kernel-default · opensuse-leap 16.0 6.12.0-160000.37.1 OPENSUSE-SU-2026:21555-1 Aug 12, 2026
kernel-default · sles 16.0 6.12.0-160000.37.1 SUSE-SU-2026:23237-1 Aug 11, 2026
kernel-default-base · opensuse-leap 16.0 6.12.0-160000.37.1.160000.2.19 OPENSUSE-SU-2026:21555-1 Aug 12, 2026
kernel-default-base · sles 16.0 6.12.0-160000.37.1.160000.2.19 SUSE-SU-2026:23231-1 Aug 11, 2026
kernel-docs · opensuse-leap 16.0 6.12.0-160000.37.1 OPENSUSE-SU-2026:21555-1 Aug 12, 2026
kernel-docs · sles 16.0 6.12.0-160000.37.1 SUSE-SU-2026:23231-1 Aug 11, 2026
kernel-kvmsmall · opensuse-leap 16.0 6.12.0-160000.37.1 OPENSUSE-SU-2026:21555-1 Aug 12, 2026
kernel-kvmsmall · sles 16.0 6.12.0-160000.37.1 SUSE-SU-2026:23231-1 Aug 11, 2026
kernel-obs-build · opensuse-leap 16.0 6.12.0-160000.37.1 OPENSUSE-SU-2026:21555-1 Aug 12, 2026
kernel-obs-qa · opensuse-leap 16.0 6.12.0-160000.37.1 OPENSUSE-SU-2026:21555-1 Aug 12, 2026
kernel-obs-qa · sles 16.0 6.12.0-160000.37.1 SUSE-SU-2026:23231-1 Aug 11, 2026
kernel-rt · opensuse-leap 16.0 6.12.0-160000.37.1 OPENSUSE-SU-2026:21555-1 Aug 12, 2026
kernel-source · opensuse-leap 16.0 6.12.0-160000.37.1 OPENSUSE-SU-2026:21555-1 Aug 12, 2026
kernel-source · sles 16.0 6.12.0-160000.37.1 SUSE-SU-2026:23231-1 Aug 11, 2026
kernel-syms · opensuse-leap 16.0 6.12.0-160000.37.1 OPENSUSE-SU-2026:21555-1 Aug 12, 2026
kernel-syms · sles 16.0 6.12.0-160000.37.1 SUSE-SU-2026:23231-1 Aug 11, 2026
kernel-zfcpdump · opensuse-leap 16.0 6.12.0-160000.37.1 OPENSUSE-SU-2026:21555-1 Aug 12, 2026
kernel-zfcpdump · sles 16.0 6.12.0-160000.37.1 SUSE-SU-2026:23231-1 Aug 11, 2026
linux · Debian 12.15 (bookworm) 6.1.176-1 DEBIAN-CVE-2026-43495 May 27, 2026
linux · Debian 13.5 (trixie) 6.12.88-1 DEBIAN-CVE-2026-43495 May 27, 2026
linux · Debian 14 7.0.7-1 DEBIAN-CVE-2026-43495 May 27, 2026

Patch Radar data is free to use with attribution. Terms and how to credit it.

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.