System crash via undersized sd_bench block allocation
Published Sep 2, 2026 · Updated Sep 2, 2026
Heap buffer overflow in PX4 Autopilot 1.17.0 and earlier allows attackers to crash the system through the sd_bench command. sd_bench allocates exactly the requested block size, then write_test stores a four-byte block number at its start without requiring at least four bytes. The command must be compiled in, and command access through a PX4 shell or MAVLink channel is required; block sizes of one to three bytes corrupt the heap.
Summary
What happened
Heap buffer overflow in PX4 Autopilot 1.17.0 and earlier allows attackers to crash the system through the sd_bench command. sd_bench allocates exactly the requested block size, then write_test stores a four-byte block number at its start without requiring at least four bytes. The command must be compiled in, and command access through a PX4 shell or MAVLink channel is required; block sizes of one to three bytes corrupt the heap.
The record
- CVE
- CVE-2026-84698
- Published
- Sep 2, 2026
- Updated
- Sep 2, 2026
- Vendor
- PX4
- Product
- PX4 Autopilot
- Classifications
- CWE-787, T1499
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 2, 2026CVE publishedPublication date reported by the CVE source.
- Sep 2, 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 <=1.17.0
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.
Public exploit references
- sd_bench undersized-block proof of conceptproof 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