CVE-2026-14368
The LwM2M JSON content formatter's get_string() in subsys/net/lib/lwm2m/lwm2m_rw_json.c copies a parsed JSON string into a caller-supplied buffer and NUL-terminates it. The length guard used if (string_length > buflen), which accepts a string whose length is exactly buflen. After memcpy() fills the whole buffer, buf[string_length] = '\0' then writes one byte past the end of the buffer (CWE-787). The string value and its length are taken directly from the incoming CoAP payload during a LwM2M WRITE: do_write_op_json() parses the payload obtained from coap_packet_get_payload(), and get_string() is invoked from lwm2m_write_handler() (engine_get_string() in subsys/net/lib/lwm2m/lwm2m_message_handling.c) for a LWM2M_RES_TYPE_STRING resource. The destination buf/buflen is either the resource instance's fixed data buffer (res_inst->data_ptr/max_data_len) or the engine validation buffer (msg->ctx->validate_buf). A LwM2M server (the client's DTLS peer) can therefore write a string resource with a value whose length equals the target buffer size and force a one-byte overflow. The overflow is a single out-of-bounds write of the constant byte 0x00 immediately past the resource or validation buffer, corrupting the adjacent byte in memory. It is not an information leak and the written value is fixed, so it is not a direct code-execution primitive, but it can corrupt adjacent state (an adjacent resource value, a length/flag field, or a struct field) and cause data corruption or a crash. Triggering the write is deterministic; the resulting impact depends on memory layout. The fix changes the guard to string_length >= buflen, rejecting the exact-length case and aligning the JSON formatter with the other content formatters (lwm2m_rw_plain_text.c, lwm2m_rw_oma_tlv.c, lwm2m_rw_senml_json.c, lwm2m_rw_cbor.c, lwm2m_rw_senml_cbor.c), which already used the correct boundary check.
Scoring
- Severity
- MEDIUM
- CVSS base score
- 5.4
- CVSS vector
- CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
- EPSS probability
- 0.23%
- CWE
- CWE-787, CWE-193
- Published
- 2026-08-31
- Last modified
- 2026-09-01
Affected products
- zephyrproject zephyr
Weakness type
Related vulnerabilities
- CVE-2026-45770 — Suricata lua: excessive flow variable registration can bypass sandbox
- CVE-2026-88053 — Tesseract: Heap out-of-bounds write in Classify::ReadIntTemplates via unvalidated counts in crafted .traineddata
- CVE-2026-88052 — Tesseract: Heap out-of-bounds write in UNICHARSET::load_via_fgets via count/insert desynchronization
- CVE-2026-88051 — Tesseract: Heap out-of-bounds write in GenericVector<T>::read due to independent reserved/size_used_ fields
- CVE-2026-88050 — Tesseract: Out-of-bounds write in UnicharCompress via unvalidated recoder code values
- CVE-2026-88049 — Tesseract: Heap out-of-bounds write in LSTM::Forward via na_/gate-matrix dimension mismatch
- CVE-2026-88048 — Tesseract: Heap out-of-bounds write/read in FullyConnected::Forward via layer/weight-matrix dimension mismatch
- CVE-2026-0310 — PAN-OS: Buffer Overflow Vulnerability via XML Processing