Bluetooth: RFCOMM: Fix not validating setsockopt user input
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ bb23c0ab824653be4aa7dfca15b07b3059717004 · < a97de7bff13b1cc825c1b1344eaed8d6c2d3e695| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: RFCOMM: Fix not validating setsockopt user input
syzbot reported rfcomm_sock_setsockopt_old() is copying data without checking user input length.
BUG: KASAN: slab-out-of-bounds in copy_from_sockptr_offset include/linux/sockptr.h:49 [inline] BUG: KASAN: slab-out-of-bounds in copy_from_sockptr include/linux/sockptr.h:55 [inline] BUG: KASAN: slab-out-of-bounds in rfcomm_sock_setsockopt_old net/bluetooth/rfcomm/sock.c:632 [inline] BUG: KASAN: slab-out-of-bounds in rfcomm_sock_setsockopt+0x893/0xa70 net/bluetooth/rfcomm/sock.c:673 Read of size 4 at addr ffff8880209a8bc3 by task syz-executor632/5064
From the CVE record · Linux
The Linux kernel’s Bluetooth RFCOMM socket option handler does not validate the length of user input before copying it. A local caller supplying a malformed setsockopt input can trigger an out-of-bounds read.
Operators running Linux kernels with the affected Bluetooth RFCOMM code should check their vendor’s advisory for affected versions.