Bluetooth: hci_event: validate skb length for unknown CC opcode
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 1a0ddaaf97405dbd11d4cb5a961a3f82400e8a50, Kernel 5c5f1f64681cc889d9b13e4a61285e9e029d6ab5, Kernel 779f83a91d4f1bf5ddfeaf528420cbb6dbf03fa8 and 2 more.
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_event: validate skb length for unknown CC opcode In hci_cmd_complete_evt(), if the command complete event has an unknown opcode, we assume the first byte of the remaining skb->data contains the return status. However, parameter data has previously been pulled in hci_event_func(), which may leave the skb empty. If so, using skb->data[0] for the return status uses un-init memory. The fix is to check skb->len before using skb->data.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.1, >=afcb3369f46ed5dc883a7b92f2dd1e264d79d388 <1a0ddaaf97405dbd11d4cb5a961a3f82400e8a50, >=afcb3369f46ed5dc883a7b92f2dd1e264d79d388 <5c5f1f64681cc889d9b13e4a61285e9e029d6ab5, >=afcb3369f46ed5dc883a7b92f2dd1e264d79d388 <779f83a91d4f1bf5ddfeaf528420cbb6dbf03fa8, >=afcb3369f46ed5dc883a7b92f2dd1e264d79d388 <cf2c2acec1cf456c3d11c11a7589e886a0f963a9, >=afcb3369f46ed5dc883a7b92f2dd1e264d79d388 <fea895de78d3bb2f0c09db9f10b18f8121b15759 | 1a0ddaaf97405dbd11d4cb5a961a3f82400e8a50, 5c5f1f64681cc889d9b13e4a61285e9e029d6ab5, 779f83a91d4f1bf5ddfeaf528420cbb6dbf03fa8, cf2c2acec1cf456c3d11c11a7589e886a0f963a9, fea895de78d3bb2f0c09db9f10b18f8121b15759 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket