CVE-2026-12519
Received Received - Intake

Buffer Overflow in WNC-M14A2A LTE-M Modem Driver

Vulnerability report for CVE-2026-12519, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-08-17

Last updated on: 2026-08-17

Assigner: Zephyr Project

Description

The WNC-M14A2A LTE-M modem driver mishandles unsolicited %NOTIFYEV: events in on_cmd_socknotifyev() (drivers/modem/vendor_standalone/wncm14a2a.c). The response line is linearized into a fixed 40-byte stack buffer via net_buf_linearize(), which caps the copy at 39 bytes and returns out_len <= 39. The two quote-delimiter scanning loops, however, were bounded by len β€” the full CR/LF-delimited frame length returned by net_buf_findcrlf() β€” rather than by out_len. When a %NOTIFYEV: line longer than 39 bytes contains no " within the linearized region, the loop indices p1/p2 walk past value[39] and read adjacent stack memory until a stray quote byte is found or the index reaches len. The over-read string is then passed to strncmp()/atoi()/LOG_*, and if a quote byte is found out of bounds the subsequent value[p2] = '\0' performs a single-NUL out-of-bounds stack write at an attacker-influenced offset. The %NOTIFYEV: payload carries network-derived content (LTIME network time, SIB1 base-station system information, CSPS/RRCSTATE), so a rogue cellular base station, a malicious or compromised modem module, or RF manipulation that induces an over-long notify line reaches the defect without any application interaction; the handler runs automatically on the unsolicited event in the modem RX thread. The impact is out-of-bounds stack disclosure (into logs and parsing) and stack corruption that can crash the modem RX thread (denial of service). The write offset is only weakly controlled, so memory-safe code execution is not demonstrated. The fix bounds both scanning loops by out_len, keeping all accesses within the linearized buffer.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-17
Last Modified
2026-08-17
Generated
2026-08-17
AI Q&A
2026-08-17
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 2 associated CPEs
Vendor Product Version / Range
zephyrproject zephyr From 1.13.0 (inc) to 4.4.2 (exc)
zephyrproject zephyr 4.4.2

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-787 The product writes data past the end, or before the beginning, of the intended buffer.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability is a buffer overflow in the WNC-M14A2A LTE-M modem driver for Zephyr RTOS. It occurs when handling unsolicited %NOTIFYEV: events. The driver uses a fixed 40-byte stack buffer to process modem responses. If a response exceeds 39 bytes and lacks a quote within the buffer, the code reads beyond the buffer into adjacent stack memory. This can lead to out-of-bounds stack disclosure and corruption, potentially crashing the modem's RX thread and causing a denial of service.

Detection Guidance

Detecting this vulnerability requires checking the Zephyr RTOS version and inspecting the modem driver code. Use 'git log --oneline' in the Zephyr repository to check for the vulnerable commit 042d79e. Inspect drivers/modem/vendor_standalone/wncm14a2a.c for the on_cmd_socknotifyev() function to see if it uses len instead of out_len for loop bounds.

Impact Analysis

The impact includes denial of service due to modem RX thread crashes. It may also expose sensitive data in logs through out-of-bounds stack reads. The vulnerability can be triggered remotely by a rogue cellular base station, compromised modem, or RF manipulation without user interaction.

Mitigation Strategies

Upgrade Zephyr RTOS to version 4.4.2 or later. If using an older branch, apply the backported fix from the v4.3, v3.7, or v4.4 branches. Alternatively, patch the on_cmd_socknotifyev() function to bound scanning loops by out_len instead of len.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-12519. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart