AP_Beacon: fix potential out-of-bounds write to beacon_state

uncovered by covarity and wickedshell
This commit is contained in:
Randy Mackay 2016-12-05 17:19:01 +09:00
parent d4d35bdcbd
commit 9fc0bc19e7
1 changed files with 2 additions and 2 deletions

View File

@ -38,7 +38,7 @@ void AP_Beacon_Backend::set_vehicle_position(const Vector3f& pos, float accuracy
void AP_Beacon_Backend::set_beacon_distance(uint8_t beacon_instance, float distance)
{
// sanity check instance
if (beacon_instance > AP_BEACON_MAX_BEACONS) {
if (beacon_instance >= AP_BEACON_MAX_BEACONS) {
return;
}
@ -57,7 +57,7 @@ void AP_Beacon_Backend::set_beacon_distance(uint8_t beacon_instance, float dista
void AP_Beacon_Backend::set_beacon_position(uint8_t beacon_instance, const Vector3f& pos)
{
// sanity check instance
if (beacon_instance > AP_BEACON_MAX_BEACONS) {
if (beacon_instance >= AP_BEACON_MAX_BEACONS) {
return;
}