Bluetooth: Mesh: net_key_status only pull one key idx
Fixes bug where the config client's net_key_status handler would attempt to pull two key indexes from a message which only holds one. Fixes #24601. Signed-off-by: Trond Einar Snekvik <Trond.Einar.Snekvik@nordicsemi.no>
This commit is contained in:
parent
32864ecbcc
commit
00ba872769
1 changed files with 2 additions and 2 deletions
|
@ -152,7 +152,7 @@ static void net_key_status(struct bt_mesh_model *model,
|
|||
struct net_buf_simple *buf)
|
||||
{
|
||||
struct net_key_param *param;
|
||||
u16_t net_idx, app_idx;
|
||||
u16_t net_idx;
|
||||
u8_t status;
|
||||
|
||||
BT_DBG("net_idx 0x%04x app_idx 0x%04x src 0x%04x len %u: %s",
|
||||
|
@ -165,7 +165,7 @@ static void net_key_status(struct bt_mesh_model *model,
|
|||
}
|
||||
|
||||
status = net_buf_simple_pull_u8(buf);
|
||||
key_idx_unpack(buf, &net_idx, &app_idx);
|
||||
net_idx = net_buf_simple_pull_le16(buf) & 0xfff;
|
||||
|
||||
param = cli->op_param;
|
||||
if (param->net_idx != net_idx) {
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue