CVE-2026-12519: memory-safety in zephyrproject zephyr
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.
AI Analysis
Technical Summary
The WNC-M14A2A LTE-M modem driver in Zephyr improperly handles unsolicited %NOTIFYEV: events in the on_cmd_socknotifyev() function. The response line is copied into a fixed 40-byte stack buffer with a maximum of 39 bytes, but two quote-delimiter scanning loops use the full frame length rather than the capped length, allowing them to read past the buffer boundary. If the %NOTIFYEV: line is longer than 39 bytes and contains no quotes within the linearized region, the loops read adjacent stack memory until a quote is found or the end is reached. This leads to an out-of-bounds single-byte stack write at an attacker-influenced offset. The payload includes network-derived data such as network time and base-station information, so an attacker controlling the cellular environment can trigger this without application interaction. The impact includes stack memory disclosure and potential denial of service via modem RX thread crash. The vulnerability does not demonstrate memory-safe code execution. The fix bounds the scanning loops by the capped buffer length to prevent out-of-bounds access.
Potential Impact
The vulnerability allows out-of-bounds stack memory disclosure and a single-byte out-of-bounds stack write, which can corrupt the stack and crash the modem RX thread, causing denial of service. The write offset is weakly controlled, so arbitrary code execution is not demonstrated. The vulnerability can be triggered remotely by a rogue cellular base station or compromised modem module without user or application interaction.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. The fix involves bounding the scanning loops by the capped buffer length to prevent out-of-bounds access. Until an official fix is available, monitor vendor communications for updates. No generic mitigations are specifically recommended by the vendor advisory.
CVE-2026-12519: memory-safety in zephyrproject zephyr
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 v3.1
Score 5.0medium
Affected software
zephyrproject
zephyr
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The WNC-M14A2A LTE-M modem driver in Zephyr improperly handles unsolicited %NOTIFYEV: events in the on_cmd_socknotifyev() function. The response line is copied into a fixed 40-byte stack buffer with a maximum of 39 bytes, but two quote-delimiter scanning loops use the full frame length rather than the capped length, allowing them to read past the buffer boundary. If the %NOTIFYEV: line is longer than 39 bytes and contains no quotes within the linearized region, the loops read adjacent stack memory until a quote is found or the end is reached. This leads to an out-of-bounds single-byte stack write at an attacker-influenced offset. The payload includes network-derived data such as network time and base-station information, so an attacker controlling the cellular environment can trigger this without application interaction. The impact includes stack memory disclosure and potential denial of service via modem RX thread crash. The vulnerability does not demonstrate memory-safe code execution. The fix bounds the scanning loops by the capped buffer length to prevent out-of-bounds access.
Potential Impact
The vulnerability allows out-of-bounds stack memory disclosure and a single-byte out-of-bounds stack write, which can corrupt the stack and crash the modem RX thread, causing denial of service. The write offset is weakly controlled, so arbitrary code execution is not demonstrated. The vulnerability can be triggered remotely by a rogue cellular base station or compromised modem module without user or application interaction.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. The fix involves bounding the scanning loops by the capped buffer length to prevent out-of-bounds access. Until an official fix is available, monitor vendor communications for updates. No generic mitigations are specifically recommended by the vendor advisory.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- zephyr
- Date Reserved
- 2026-06-17T12:59:10.511Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6a8339cebf8831d53935e2f6
Added to database: 08/17/2026, 16:41:50 UTC
Last enriched: 08/17/2026, 16:58:31 UTC
Last updated: 10/02/2026, 02:46:02 UTC
Views: 53
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.