Bluetooth: SCO: Fix not validating setsockopt user input
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ b96e9c671b05f95126753a22145d4509d45ca197 · < 51eda36d33e43201e7a4fd35232e069b2c850b01| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: SCO: Fix not validating setsockopt user input
syzbot reported sco_sock_setsockopt() 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 sco_sock_setsockopt+0xc0b/0xf90 net/bluetooth/sco.c:893 Read of size 4 at addr ffff88805f7b15a3 by task syz-executor.5/12578
From the CVE record · Linux
The Linux kernel’s Bluetooth SCO setsockopt handler does not validate the length of user input before copying it, causing a slab out-of-bounds read. A local caller can trigger the read by supplying input to sco_sock_setsockopt(); the input does not establish whether authentication or other interaction is required.
Engineers running Linux kernels with the affected Bluetooth SCO code should check their kernel version against their vendor’s advisory; affected versions are not specified in the input.