CVE-2026-98819: Bluetooth: btintel: validate DDC record lengths
Bluetooth: btintel: validate DDC record lengths
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.12.113-1 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 7.2.10-1 - Upgrade
Upgrade
debian/linux-6.12to a version that resolves this vulnerability.Fixed in 6.12.113-1~deb12u1 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.12.115-2Fixed in 7.2.12-1Fixed in 7.2.15-1 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 5.10.273 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 5.15.224 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.1.191 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.6.160 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.12.113 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.18.56 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 7.2.10 - Upgrade
Upgrade
azurelinux/kernelto a version that resolves this vulnerability.Fixed in 6.6.161.1-1
Event History
Frequently Asked Questions
What conditions are required to trigger the vulnerable code path?
The issue is triggered while parsing Bluetooth DDC records from firmware before sending them through Intel_Write_DDC. A malformed record length, including 0xFF or a length that is too short or extends beyond the remaining firmware data, is required.
Which systems are most likely exposed?
Systems using the Linux kernel Bluetooth btintel driver and processing Intel Bluetooth DDC firmware records are relevant. The provided information does not identify specific kernel versions, Intel adapter models, or default configurations.
What validation does the fix add?
The fix stores and parses DDC record lengths as unsigned values to prevent 0xFF from wrapping. It rejects records shorter than the required three-byte header, records larger than U8_MAX, and records that exceed the remaining firmware bytes.