CVE-2025-15150
Unknown Unknown - Not Provided
Stack-Based Buffer Overflow in PX4 MavlinkLogHandler Module

Publication date: 2025-12-28

Last updated on: 2025-12-28

Assigner: VulDB

Description
A vulnerability was found in PX4 PX4-Autopilot up to 1.16.0. Affected by this issue is the function MavlinkLogHandler::state_listing/MavlinkLogHandler::log_entry_from_id of the file src/modules/mavlink/mavlink_log_handler.cpp. The manipulation results in stack-based buffer overflow. The attack is only possible with local access. The patch is identified as 338595edd1d235efd885fd5e9f45e7f9dcf4013d. It is best practice to apply a patch to resolve this issue.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-12-28
Last Modified
2025-12-28
Generated
2026-06-16
AI Q&A
2025-12-28
EPSS Evaluated
2026-06-15
NVD
CVE-2025-15150
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
px4 px4-autopilot 1.16.0
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
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-121 A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function).
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Impact Analysis

The vulnerability can lead to a compromise of the system's integrity, confidentiality, and availability since it allows a stack-based buffer overflow. An attacker with local access could potentially execute arbitrary code or cause a denial of service, impacting the affected system's operation.

Executive Summary

This vulnerability is a stack-based buffer overflow found in the PX4 PX4-Autopilot software up to version 1.16.0. It affects specific functions in the mavlink_log_handler.cpp file. The overflow occurs due to improper handling of data in these functions, and an attacker with local access can exploit this issue.

Detection Guidance

This vulnerability can be detected by monitoring for the presence of log files with excessively long filenames in the PX4 Autopilot log directory, as these trigger the stack buffer overflow when processed. Detection involves checking for unusually long filenames in the logdata.txt or log directory. Since the vulnerability is triggered by processing these long filenames via MAVLink FTP messages (LOG_REQUEST_LIST and LOG_REQUEST_DATA), you can look for suspicious FTP activity creating or requesting log files with long names. Suggested commands include listing files in the PX4 log directory and filtering for long filenames, for example: `ls -l /path/to/px4/logs | awk 'length($9) > 60'` to find filenames longer than 60 characters. Additionally, monitoring MAVLink FTP traffic for LOG_REQUEST_LIST and LOG_REQUEST_DATA messages requesting or returning log entries with long filenames can help detect exploitation attempts. However, no specific detection commands or tools are provided in the resources. [1, 4]

Mitigation Strategies

Apply the patch identified as commit 338595edd1d235efd885fd5e9f45e7f9dcf4013d to the PX4 PX4-Autopilot software to resolve the stack-based buffer overflow vulnerability. Since the attack requires local access, ensure that only trusted users have local access to the system until the patch is applied.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2025-15150. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart