Driver crash via unbounded BST name length
Published Mar 13, 2026 · Updated Mar 13, 2026
Stack-based buffer overflow in PX4 Autopilot before 1.17.0-rc2 allows physically proximate attackers to crash the BST driver task. BST::probe uses the untrusted dev_name_len from an I2C device reply as an index into the 32-byte dev_name stack buffer before writing a null terminator. Exploitation requires control of a BST device or the I2C bus; successful memory corruption can also execute code in the driver context.
Summary
What happened
Stack-based buffer overflow in PX4 Autopilot before 1.17.0-rc2 allows physically proximate attackers to crash the BST driver task. BST::probe uses the untrusted dev_name_len from an I2C device reply as an index into the 32-byte dev_name stack buffer before writing a null terminator. Exploitation requires control of a BST device or the I2C bus; successful memory corruption can also execute code in the driver context.
The record
- CVE
- CVE-2026-32705
- Published
- Mar 13, 2026
- Updated
- Mar 13, 2026
- Vendor
- PX4
- Product
- PX4 Autopilot
- Classifications
- CWE-121
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 13, 2026CVE publishedPublication date reported by the CVE source.
- Mar 13, 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=< 1.17.0-rc2
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
- px4-bst-dev-name-overflow-poc.tar.gzproof 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