CVE-2025-9020
BaseFortify
Publication date: 2025-08-15
Last updated on: 2025-08-15
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| px4 | px4-autopilot | 1.15.4 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-119 | The product performs operations on a memory buffer, but it reads from or writes to a memory location outside the buffer's intended boundary. This may result in read or write operations on unexpected memory locations that could be linked to other variables, data structures, or internal program data. |
| CWE-416 | The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in the PX4 PX4-Autopilot software up to version 1.15.4, specifically in the MavlinkReceiver::handle_message_serial_control function. It involves a use-after-free issue caused by manipulation of the _mavlink_shell argument. Exploiting this vulnerability requires local access and is considered difficult due to high attack complexity.
How can this vulnerability impact me? :
Exploitation of this vulnerability could lead to unintended behavior or crashes in the PX4 autopilot system due to use-after-free memory errors. Since it requires local access and is difficult to exploit, the immediate risk is limited but could potentially affect system stability or control if successfully exploited.
What immediate steps should I take to mitigate this vulnerability?
It is recommended to apply the patch identified by commit 4395d4f00c49b888f030f5b43e2a779f1fa78708 to fix this issue.