Bluetooth: MGMT: fix crash in set_mesh_sync and set_mesh_complete
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: MGMT: fix crash in set_mesh_sync and set_mesh_complete
There is a BUG: KASAN: stack-out-of-bounds in set_mesh_sync due to memcpy from badly declared on-stack flexible array.
Another crash is in set_mesh_complete() due to double list_del via mgmt_pending_valid + mgmt_pending_remove.
Use DEFINE_FLEX to declare the flexible array right, and don't memcpy outside bounds.
As mgmt_pending_valid removes the cmd from list, use mgmt_pending_free, and also report status on error.
From the CVE record · Linux
The Linux kernel’s Bluetooth MGMT code has an out-of-bounds stack access in set_mesh_sync and a double list removal in set_mesh_complete, both of which can cause crashes. The input does not specify how an attacker could trigger these bugs or whether access or user interaction is required.
Engineers running Linux kernels with Bluetooth MGMT should check whether their kernel is affected; affected versions are not specified.