CVE-2026-0849: 
NixOS vulnerability analysis and mitigation

CVE-2026-0849 is a stack-based buffer overflow vulnerability in the Zephyr RTOS ATAES132A crypto driver that allows a compromised device or I²C bus attacker to corrupt kernel memory and potentially hijack execution. It affects Zephyr versions in the v4.3.x series (including 4.3.0, 4.3.0-rc1, 4.3.0-rc2, and 4.3.0-rc3). The vulnerability was published on March 14, 2026, with a patch submitted to the main branch. The GitHub Security Advisory assigns a CVSS v3.1 score of 3.8 (Low) with a physical attack vector, while Feedly's NVD-sourced data estimates a higher score of 6.8 (Medium) reflecting the potential for full confidentiality, integrity, and availability impact (Zephyr Advisory).

The root cause is a classic buffer overflow (CWE-120) in ataes132a_send_command within drivers/crypto/crypto_ataes132a.c. The function reads a device response and copies count - 3 bytes into a caller-supplied buffer without bounding the copy operation (lines 140–166). During CCM decrypt operations, the destination is a 52-byte stack buffer (param_buffer[52], lines 208–357); a forged response with a count value up to 64 (the maximum read size) overflows this buffer, overwriting adjacent stack data. An attacker controlling the ATAES132A device or the I²C bus can trigger the overflow by returning a valid-CRC packet with an inflated count field, leading to kernel-level memory corruption (Zephyr Advisory).

Successful exploitation can result in kernel stack memory corruption, enabling denial of service or potential arbitrary code execution in kernel context. Any Zephyr build using the ATAES132A crypto driver is affected, meaning embedded and IoT devices relying on this hardware security element for cryptographic operations are at risk. The impact spans confidentiality, integrity, and availability — a successful attacker could disrupt device operation, exfiltrate sensitive cryptographic material, or gain persistent kernel-level control (Zephyr Advisory, Feedly).

A proof-of-concept (PoC) exploit is publicly available as ataes132a-response-overflow-poc.tar.gz, hosted in the GitHub Security Advisory. The PoC is an ASAN harness written in C that stubs a malicious device response and executes the vulnerable driver code, producing a confirmed stack-buffer-overflow report in ataes132a_send_command. There is no evidence of in-the-wild exploitation at this time, and the vulnerability is not listed in the CISA KEV catalog. The EPSS score is approximately 0.015% (0.000150), reflecting low probability of near-term exploitation (Zephyr Advisory).

1. Physical/Bus Access: Gain physical access to the target embedded device or compromise the I²C bus connecting the host microcontroller to the ATAES132A secure element (e.g., via bus interposer, logic analyzer with injection capability, or a compromised peripheral device).
2. Craft Malformed Response: Prepare a forged ATAES132A response packet with a valid CRC but an inflated count field (up to 64, the maximum read size), which is larger than the legitimate response payload.
3. Trigger CCM Decrypt Operation: Wait for or induce the Zephyr host to initiate a CCM decrypt operation that calls ataes132a_send_command, which will read the device response.
4. Inject Forged Response: Deliver the malformed response over the I²C bus so the driver reads the oversized count value and copies count - 3 bytes into the 52-byte param_buffer stack buffer without bounds checking.
5. Achieve Stack Overflow: The copy operation overflows param_buffer by up to 9 bytes (64 - 3 - 52 = 9), overwriting adjacent stack data including saved registers or return addresses.
6. Kernel Memory Corruption / Code Execution: Depending on stack layout and available mitigations, the overflow can cause a crash (DoS) or, with careful payload crafting, redirect kernel execution to attacker-controlled code (Zephyr Advisory).

• Process/Kernel Behavior: Unexpected kernel panics, hard faults, or system resets on devices using the ATAES132A crypto driver, particularly during CCM decrypt operations.
• Logs: Zephyr kernel fault logs or ASAN output referencing ataes132a_send_command with stack-buffer-overflow errors; unusual error codes returned from crypto operations.
• Hardware/Bus: Anomalous I²C traffic on the bus connected to the ATAES132A device, particularly response packets with count fields exceeding expected values (greater than 55, i.e., 52 + 3); unexpected devices or interposers detected on the I²C bus.
• File System: Presence of ataes132a-response-overflow-poc.tar.gz or related ASAN harness files on development or build systems, indicating potential attacker reconnaissance or testing (Zephyr Advisory).

The Zephyr project has issued a patch for the main branch via pull request #103163; users should upgrade to a patched Zephyr build once a fixed release is available. As an interim workaround, implement physical security controls to prevent unauthorized access to the ATAES132A device or its I²C communication bus (e.g., tamper-evident enclosures, bus authentication). Developers can also apply a manual fix by adding bounds checking on the count field before the copy operation in drivers/crypto/crypto_ataes132a.c to ensure the copy does not exceed the 52-byte param_buffer size. Disabling the ATAES132A driver in builds where it is not required is also a viable risk reduction measure (Zephyr Advisory).

The vulnerability was discovered and reported by SecMate (https://secmate.dev), with credit also given to reporters max-r-b and enitmar in the GitHub Security Advisory. A Bluesky post from the CVE tracking account noted the disclosure shortly after publication. Coverage has been picked up by vulnerability aggregators including Tenable, VulDB, CIRCL, and ENISA's EUVD (EUVD-2026-12186), as well as a technical write-up on infinitsec.net. Community reaction has been limited given the physical attack vector requirement and low EPSS score (Zephyr Advisory).