CVE-2026-43495: net: wwan: t7xx: validate port_count against message length in t7xx_port_enum_msg_handler
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.
Security readout for executives and security teams
Plain-English summary
A malformed message from a connected modem can make the Linux t7xx WWAN driver read beyond allocated memory. This may expose sensitive data, crash the system, or potentially enable broader compromise. Systems without the t7xx driver and relevant modem path are unlikely to be exposed.
Executive priority
Treat this as a high-priority infrastructure update where t7xx cellular hardware is deployed. Patch exposed systems promptly, but avoid declaring fleet-wide exposure until hardware, driver loading, and vendor backport status are confirmed. There is no supplied evidence of exploitation in the wild.
Technical view
The t7xx driver trusted modem-supplied port_count as a loop bound without confirming the message contained the corresponding data. A value of 65,535 in a 12-byte buffer can cause a slab out-of-bounds read of up to 262,140 bytes. Related runtime-feature parsing also lacked remaining-buffer and integer-overflow checks. Stable kernel commits add length and structure-size validation.
Likely exposure
Exposure is concentrated in Linux systems using the MediaTek t7xx WWAN driver with a connected or otherwise reachable modem. The supplied version metadata identifies Linux as affected but is insufficiently clear for reliable distribution-specific version mapping. Confirm driver use and patched-kernel status with the operating-system vendor.
Exploitation context
The CVSS 8.8 vector describes adjacent, low-complexity exploitation requiring neither privileges nor user interaction. The triggering data is modem-supplied, so practical exploitation requires influence over that communication path. The supplied record says this CVE is not in KEV and provides no evidence of active exploitation or a public exploit.
Researcher notes
The primary flaw is insufficient message-length validation before iterating over variable-length port data. The correction checks the fixed header, validates struct_size against msg_len, and propagates trustworthy lengths from both parsing paths. Runtime-feature parsing additionally validates remaining bytes and feature length, preventing out-of-bounds reads and signed offset overflow. Exploitability beyond the documented read is not established here.
Mitigation direction
Install a vendor-supported kernel containing the applicable stable fix.
Prioritize systems actively using MediaTek t7xx WWAN hardware.
If immediate updating is impossible, disable unused t7xx WWAN functionality according to vendor guidance.
Monitor Linux distribution advisories for precise affected and fixed package versions.
Validation and detection
Inventory systems for the t7xx WWAN driver and associated modem hardware.
Compare installed kernel packages with distribution-specific security advisories.
Confirm the vendor kernel includes an applicable referenced stable commit or backport.
Review kernel logs for unexplained t7xx faults, memory errors, or crashes.
After updating, verify normal modem enumeration and connectivity.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2026-43495 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
7Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.