Bluetooth: btrtl: Don't leak return code when parsing firmware format v2
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: btrtl: Don't leak return code when parsing firmware format v2
When key_id from chip is zero, rtlbt_parse_firmware_v2() intentionally ignores all security headers. However, the implementation simply breaks from a switch statement and leaks uninitialized return code `rc' (if the first section is a security one) or the previous section's `rc'.
Fix it by really skipping a loop with `continue'. For consistency and readability, also do the same for the default case.
From the CVE record · Linux
The Linux kernel Bluetooth btrtl firmware v2 parser can return an uninitialized or stale return code when the chip's key_id is zero and it encounters a security header. The input does not specify how an attacker could trigger this or whether authentication or user interaction is required.
Engineers running Linux kernels with the Bluetooth btrtl driver should check their versions; affected versions are not specified.