Stack corruption via unchecked ACF frame count
Published Aug 17, 2026 · Updated Aug 18, 2026
Stack buffer overflow in acf-can-listener in COVESA Open1722 through 0.9.2 allows remote attackers to corrupt stack memory via a crafted UDP datagram. In examples/acf-can/acf-can-common.c, avtp_to_can() walks ACF-CAN messages into a caller-supplied frame_t array but never checks that its write index stays within the listener's fixed 15-element stack buffer before storing each decoded frame. Reachability requires the optional example listener to be built and exposed over UDP; any sender that knows the shipped plaintext AVTP stream ID can trigger memory corruption, while public testing demonstrates overflow and integrity impact but not a reliable crash or code-execution chain.
Summary
What happened
Stack buffer overflow in acf-can-listener in COVESA Open1722 through 0.9.2 allows remote attackers to corrupt stack memory via a crafted UDP datagram. In examples/acf-can/acf-can-common.c, avtp_to_can() walks ACF-CAN messages into a caller-supplied frame_t array but never checks that its write index stays within the listener's fixed 15-element stack buffer before storing each decoded frame. Reachability requires the optional example listener to be built and exposed over UDP; any sender that knows the shipped plaintext AVTP stream ID can trigger memory corruption, while public testing demonstrates overflow and integrity impact but not a reliable crash or code-execution chain.
The record
- CVE
- CVE-2026-73522
- Published
- Aug 17, 2026
- Updated
- Aug 18, 2026
- Vendor
- COVESA
- Product
- Open1722
- Classifications
- CWE-121, T1210
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 17, 2026CVE publishedPublication date reported by the CVE source.
- Aug 18, 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=0 <=0.9.2
What conditions does exploitation require?
What is affected?
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.
Public exploit references
- Oversized ACF-CAN datagram proof of concept in GitHub issue #154proof 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