Kernel memory corruption via unchecked response length
Published Mar 14, 2026 · Updated Mar 14, 2026
Stack-based buffer overflow in the ATAES132A driver in Zephyr RTOS 4.3 and earlier allows physically proximate attackers to corrupt kernel memory. ataes132a_send_command copies count minus three response bytes into a 52-byte CCM stack buffer without bounding the copy to its capacity. A valid-CRC response with an inflated count requires control of the ATAES132A device or I2C bus and can crash the kernel or enable kernel-context code execution.
Summary
What happened
Stack-based buffer overflow in the ATAES132A driver in Zephyr RTOS 4.3 and earlier allows physically proximate attackers to corrupt kernel memory. ataes132a_send_command copies count minus three response bytes into a 52-byte CCM stack buffer without bounding the copy to its capacity. A valid-CRC response with an inflated count requires control of the ATAES132A device or I2C bus and can crash the kernel or enable kernel-context code execution.
The record
- CVE
- CVE-2026-0849
- Published
- Mar 14, 2026
- Updated
- Mar 14, 2026
- Vendor
- Zephyr Project
- Product
- Zephyr RTOS
- Classifications
- CWE-120
- Attack vector
- physical
- Privileges
- Unavailable
Timeline
How it unfolded
- Mar 14, 2026CVE publishedPublication date reported by the CVE source.
- Mar 14, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=* <=4.3
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- ATAES132A response-overflow ASAN harnessproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo