Bluetooth: btintel: validate DDC record lengths
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 145f2368c5fd7962e37315ccc092670743019d08 · < b0fce76873a5e6a6820354409b26693ac5f8b251| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: btintel: validate DDC record lengths
Parse DDC record lengths in unsigned storage so 0xFF does not wrap. Reject records smaller than the mandatory three-byte header, records exceeding U8_MAX, and records exceeding remaining firmware bytes before issuing Intel_Write_DDC.
This issue was reported by Claude Mythos.
From the CVE record · Linux
The Linux kernel’s Bluetooth btintel code did not properly validate DDC record lengths before issuing Intel_Write_DDC. Malformed firmware records could reach that operation; the input does not specify attacker access, authentication requirements, or user interaction.
Engineers running the Linux kernel should check whether their version includes the btintel DDC record-length fix; affected versions are not specified.