CVE-2026-16514

MEDIUMPre-NVD 4.34.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 4.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (13th percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
4.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 4.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

gptp_mi_qualify_announce() in subsys/net/l2/ethernet/gptp/gptp_mi.c walks the Path Trace TLV of a received IEEE 802.1AS Announce message, comparing each clock identity against the local one. The loop bound was taken solely from the attacker-controlled wire field announce->steps_removed (accepted up to 254), never from announce->tlv.len, which is the field that states how many identities the TLV actually carries. Because path_sequence is the flexible member of the wire TLV (struct gptp_path_trace_tlv) and GPTP_ANNOUNCE() yields a raw pointer into the received packet buffer, the memcmp() inside the loop can address memory well past the end of the received frame.

The stack's only length validation, GPTP_ANNOUNCE_CHECK_LEN(), requires the received gPTP payload to be exactly 68 + tlv.len bytes — so it does not constrain the loop, it guarantees the data is absent. An unauthenticated attacker on the same Ethernet segment can send a single Announce frame declaring tlv.len = 0 with steps_removed = 254; the frame passes the length check and reception path (net_gptp_recv() → gptp_handle_msg() → gptp_mi_qualify_announce()), which performs no authentication, and the loop then reads 255 entries of 8 bytes each — about 2 KB — beyond the end of the network buffer.

The impact is an out-of-bounds read. The bytes read are only used as a memcmp() operand and are never returned to the attacker, so there is no meaningful information disclosure; the practical risk is that the overread crosses a network buffer pool boundary into unmapped or MPU-protected memory and faults the networking RX thread, causing a denial of service. Exposure is limited to builds that enable the opt-in, experimental CONFIG_NET_GPTP (TSN/AVB deployments) and to attackers with layer-2 adjacency, since gPTP frames are sent to a link-local multicast address and are not routed.

The fix computes the true entry count as tlv.len / GPTP_CLOCK_ID_LEN and rejects the announce when steps_removed + 1 exceeds it, so the loop can no longer run past the data the packet-length check proved present.

CVSS v3
4.3
EG Score
4.3MEDIUMmedium confidence
EG Risk
19
EG Risk 19/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity43% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at every mission impact level.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
13th
KEV
Not listed

CISA SSVCTrack at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 18, 2026

Last Modified

September 18, 2026

Advisory Details (2)

Auto-updated Sep 18, 2026
Patch available. Sources: github_commit, github.
github Patch Available

Out-of-bounds read in gPTP Announce path-trace validation via unvalidated stepsRemoved · Advisory · zephyrproject-rtos/zephyr · GitHub

https://github.com/zephyrproject-rtos/zephyr/security/advisories/GHSA-mgxg-89rr-6855
github_commit

commit a2c882db7a57 (zephyrproject-rtos/zephyr)

Fix landed in zephyrproject-rtos/zephyr commit a2c882db7a57 — awaiting tagged release

https://github.com/zephyrproject-rtos/zephyr/commit/a2c882db7a57cf08a06b4d27bead22b07a9c3c61

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 12× in last 7d / 26× 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.

  1. 2026-10-04 07:07 UTCEG score recompute
  2. 2026-10-03 14:25 UTCEPSS rescore
  3. 2026-10-03 07:54 UTCEG score recompute
  4. 2026-10-02 08:36 UTCEG score recompute
  5. 2026-10-01 19:49 UTCEPSS rescore
  6. 2026-10-01 09:22 UTCEG score recompute
  7. 2026-09-30 15:02 UTCEPSS rescore
  8. 2026-09-30 10:09 UTCEG score recompute
  9. 2026-09-29 15:20 UTCEPSS rescore
  10. 2026-09-29 10:53 UTCEG score recompute
  11. 2026-09-28 13:51 UTCEPSS rescore
  12. 2026-09-28 11:40 UTCEG score recompute
  13. 2026-09-27 13:47 UTCEPSS rescore
  14. 2026-09-27 12:23 UTCEG score recompute
  15. 2026-09-26 15:58 UTCEPSS rescore
  16. 2026-09-26 13:09 UTCEG score recompute
  17. 2026-09-24 14:38 UTCEG score recompute
  18. 2026-09-23 15:25 UTCEG score recompute
  19. 2026-09-22 16:10 UTCEG score recompute
  20. 2026-09-21 16:56 UTCEG score recompute
  21. 2026-09-19 18:26 UTCEG score recompute
  22. 2026-09-18 17:26 UTCEG score recompute
  23. 2026-09-18 16:49 UTCEG score recompute
  24. 2026-09-18 15:24 UTCEG score recompute
  25. 2026-09-18 14:34 UTCEG score recompute
Show 1 more
  1. 2026-09-18 14:34 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-16514?
CVE-2026-16514 is a medium vulnerability published on September 18, 2026. gptpmiqualifyannounce() in subsys/net/l2/ethernet/gptp/gptpmi.c walks the Path Trace TLV of a received IEEE 802.1AS Announce message, comparing each clock identity against the local one. The loop bound was taken solely from the attacker-controlled wire field announce->stepsremoved (accepted up to…
When was CVE-2026-16514 disclosed?
CVE-2026-16514 was first published on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-16514 actively exploited?
CVE-2026-16514 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (13th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-16514?
CVE-2026-16514 has a CVSS base score of 4.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-16514?
A fix for CVE-2026-16514 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-16514?

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