BlueZ: suppress Qt-Security-QProcessStart in bluetoothdVersion()


The Axivion code analyzer issued the following problem:

 Qt-Security-QProcessStart: The program called could not be determined
 at compile time. [start()]

The warning is correct, in the sense that the code recieves the PID of
the process via D-Bus, and uses it to construct a path to the executable
using the /proc/<PID>/exe template.

This could be an issue if a malicious actor compromised D-Bus by
registering their own application under the org.bluez interface, or if
the /proc filesystem got compromised. However, none of these cases
falls under the responsibility of the Qt framework, and also there is
no easy way to rework the existing code.

As a result, this patch chooses the approach of suppressing the warning.

Axivion-Id: qt_Add-ons_qtbluetooth_dev_linux:SV203
Task-number: QTBUG-144754
Pick-to: 6.11 6.8
Change-Id: I2ceef7809a8433877e2e53c1aced892079805dc4
Reviewed-by: Juha Vuolle <juha.vuolle@qt.io>
commit0f5edb686de5bfa28a77c717bce8bc566b99e3f1
parent27a753e97e42c1773d58b42534b10df19b4859a0
authorIvan Solovev <ivan.solovev@qt.io>
committerIvan Solovev <ivan.solovev@qt.io>
commit timeMon, 20 Apr 2026 08:04:58 +0000