The immediate technical result is a stack memory overwrite in the PX4 process, with confirmed crash and memory-corruption outcomes. Availability of the flight-control process can be lost when it crashes, while the integrity of in-process state can be affected. The evidence does not establish data disclosure, reliable code execution, privilege escalation, or impact beyond the affected component. Because the attacker needs physical CAN-injection capability and the impact scope is unchanged, exposure depends heavily on vehicle wiring, bus access, and deployment configuration. Organisational consequences may include interrupted missions, recovery or maintenance work, and a safety review; no specific physical incident is established.