CVE-2026-43495

HIGHPre-NVD 8.88.8
EchelonGraph scoreMEDIUM confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-05-21. a secondary CVSS source baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
8.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
8.8
EG Score
8.8(medium)
EPSS
19.1%
KEV
Not listed

Published

May 21, 2026

Last Modified

June 26, 2026

Advisory Details (5)

Auto-updated Jun 2, 2026
No patch confirmed yet.
generic

net: wwan: t7xx: validate port_count against message length in t7xx_port_enum_msg_handler - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f94450ce5053b36002995b72d1fa1db3bb08c5bf
generic

net: wwan: t7xx: validate port_count against message length in t7xx_port_enum_msg_handler - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/dd4f4c93c1488d7100b9964f2da4c8b3c29652f1
generic

net: wwan: t7xx: validate port_count against message length in t7xx_port_enum_msg_handler - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9855e063e063158cc5bded576382599dc3133202
generic

net: wwan: t7xx: validate port_count against message length in t7xx_port_enum_msg_handler - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2b56d7903ab804481f5233a259d5f341e9fd513c
generic

net: wwan: t7xx: validate port_count against message length in t7xx_port_enum_msg_handler - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0e7c074cfcd9bd93765505f9eb8b42f03ed2a744

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 55× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 148 total refreshes for this CVE.

  1. 2026-07-15 16:57 UTCEPSS rescore
  2. 2026-07-15 02:00 UTCEPSS rescore
  3. 2026-07-13 22:30 UTCEPSS rescore
  4. 2026-07-13 06:13 UTCEPSS rescore
  5. 2026-07-12 05:46 UTCEPSS rescore
  6. 2026-07-11 08:27 UTCEPSS rescore
  7. 2026-07-09 19:10 UTCEPSS rescore
  8. 2026-07-08 15:16 UTCEPSS rescore
  9. 2026-07-07 13:46 UTCEPSS rescore
  10. 2026-07-06 16:27 UTCEPSS rescore
  11. 2026-07-06 02:23 UTCEPSS rescore
  12. 2026-07-05 02:30 UTCEPSS rescore
  13. 2026-07-04 06:31 UTCEPSS rescore
  14. 2026-07-01 15:07 UTCEPSS rescore
  15. 2026-06-30 23:22 UTCEPSS rescore
  16. 2026-06-29 20:11 UTCEG score recompute
  17. 2026-06-29 20:11 UTCGHSA enrichment
  18. 2026-06-29 14:06 UTCEPSS rescore
  19. 2026-06-28 14:07 UTCEPSS rescore
  20. 2026-06-28 08:22 UTCEG score recompute
  21. 2026-06-28 08:21 UTCGHSA enrichment
  22. 2026-06-28 04:56 UTCEPSS rescore
  23. 2026-06-27 20:04 UTCEG score recompute
  24. 2026-06-27 20:04 UTCGHSA enrichment
  25. 2026-06-27 07:43 UTCEG score recompute
Show 75 more
  1. 2026-06-27 07:43 UTCGHSA enrichment
  2. 2026-06-27 03:08 UTCEPSS rescore
  3. 2026-06-26 19:26 UTCEG score recompute
  4. 2026-06-26 19:25 UTCGHSA enrichment
  5. 2026-06-26 03:38 UTCEG score recompute
  6. 2026-06-26 03:38 UTCGHSA enrichment
  7. 2026-06-25 14:26 UTCEG score recompute
  8. 2026-06-25 14:26 UTCGHSA enrichment
  9. 2026-06-25 13:49 UTCEPSS rescore
  10. 2026-06-25 13:49 UTCEPSS rescore
  11. 2026-06-24 14:05 UTCEPSS rescore
  12. 2026-06-23 21:33 UTCEPSS rescore
  13. 2026-06-22 14:25 UTCEPSS rescore
  14. 2026-06-22 14:25 UTCEPSS rescore
  15. 2026-06-21 14:56 UTCEPSS rescore
  16. 2026-06-21 14:56 UTCEPSS rescore
  17. 2026-06-21 01:59 UTCEPSS rescore
  18. 2026-06-19 19:25 UTCEPSS rescore
  19. 2026-06-18 17:52 UTCEPSS rescore
  20. 2026-06-18 17:52 UTCEPSS rescore
  21. 2026-06-17 23:41 UTCEG score recompute
  22. 2026-06-17 23:41 UTCGHSA enrichment
  23. 2026-06-17 17:53 UTCEPSS rescore
  24. 2026-06-17 11:15 UTCEG score recompute
  25. 2026-06-17 11:15 UTCGHSA enrichment
  26. 2026-06-16 20:00 UTCEG score recompute
  27. 2026-06-16 20:00 UTCGHSA enrichment
  28. 2026-06-16 17:52 UTCEPSS rescore
  29. 2026-06-16 04:01 UTCEG score recompute
  30. 2026-06-16 04:00 UTCGHSA enrichment
  31. 2026-06-15 17:49 UTCEPSS rescore
  32. 2026-06-15 15:43 UTCEG score recompute
  33. 2026-06-15 15:43 UTCGHSA enrichment
  34. 2026-06-14 22:59 UTCEG score recompute
  35. 2026-06-14 22:59 UTCGHSA enrichment
  36. 2026-06-14 10:41 UTCEG score recompute
  37. 2026-06-14 10:41 UTCGHSA enrichment
  38. 2026-06-13 23:00 UTCEPSS rescore
  39. 2026-06-13 22:23 UTCEG score recompute
  40. 2026-06-13 22:23 UTCGHSA enrichment
  41. 2026-06-13 10:04 UTCEG score recompute
  42. 2026-06-13 10:04 UTCGHSA enrichment
  43. 2026-06-12 23:12 UTCEPSS rescore
  44. 2026-06-12 23:12 UTCEPSS rescore
  45. 2026-06-12 21:46 UTCEG score recompute
  46. 2026-06-12 21:46 UTCGHSA enrichment
  47. 2026-06-12 09:28 UTCEG score recompute
  48. 2026-06-12 09:27 UTCGHSA enrichment
  49. 2026-06-11 21:10 UTCEG score recompute
  50. 2026-06-11 21:10 UTCGHSA enrichment
  51. 2026-06-11 14:00 UTCEPSS rescore
  52. 2026-06-11 08:52 UTCEG score recompute
  53. 2026-06-11 08:52 UTCGHSA enrichment
  54. 2026-06-10 22:18 UTCEPSS rescore
  55. 2026-06-10 20:34 UTCEG score recompute
  56. 2026-06-10 20:34 UTCGHSA enrichment
  57. 2026-06-10 13:22 UTCEPSS rescore
  58. 2026-06-10 13:22 UTCEPSS rescore
  59. 2026-06-10 08:17 UTCEG score recompute
  60. 2026-06-10 08:17 UTCGHSA enrichment
  61. 2026-06-09 19:59 UTCEG score recompute
  62. 2026-06-09 19:59 UTCGHSA enrichment
  63. 2026-06-09 07:42 UTCEG score recompute
  64. 2026-06-09 07:42 UTCGHSA enrichment
  65. 2026-06-08 19:24 UTCEG score recompute
  66. 2026-06-08 19:24 UTCGHSA enrichment
  67. 2026-06-08 14:17 UTCEPSS rescore
  68. 2026-06-08 14:17 UTCEPSS rescore
  69. 2026-06-08 06:56 UTCEG score recompute
  70. 2026-06-08 06:55 UTCGHSA enrichment
  71. 2026-06-07 18:38 UTCEG score recompute
  72. 2026-06-07 18:38 UTCGHSA enrichment
  73. 2026-06-07 15:25 UTCEPSS rescore
  74. 2026-06-07 15:25 UTCEPSS rescore
  75. 2026-06-07 06:19 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-43495?
CVE-2026-43495 is a high vulnerability published on May 21, 2026. In the Linux kernel, the following vulnerability has been resolved: net: wwan: t7xx: validate portcount against message length in t7xxportenummsg_handler t7xxportenummsghandler() uses the modem-supplied port_count field as a loop bound over port_msg->data[] without checking that the message buffer…
When was CVE-2026-43495 disclosed?
CVE-2026-43495 was first published in the National Vulnerability Database on May 21, 2026, with the most recent update on June 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-43495 actively exploited?
CVE-2026-43495 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 19.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-43495?
CVE-2026-43495 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-43495?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-43495, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-43495

Explore →

Is Your Infrastructure Affected by CVE-2026-43495?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.