Bluetooth: btrtl: Prevent potential NULL dereference
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 26503ad25de8c7c93a2037f919c2e49a62cf65f1 · < aaf356f872a60db1e96fb762a62c4607fd22741f| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: btrtl: Prevent potential NULL dereference
The btrtl_initialize() function checks that rtl_load_file() either had an error or it loaded a zero length file. However, if it loaded a zero length file then the error code is not set correctly. It results in an error pointer vs NULL bug, followed by a NULL pointer dereference. This was detected by Smatch:
drivers/bluetooth/btrtl.c:592 btrtl_initialize() warn: passing zero to 'ERR_PTR'
From the CVE record · Linux
The Linux kernel’s Bluetooth btrtl driver can dereference a NULL pointer when rtl_load_file() loads a zero-length file and btrtl_initialize() handles the result incorrectly. The input does not establish whether an attacker can trigger this condition, or whether it requires network access, authentication, or user interaction.
Teams running the Linux kernel should check whether their version includes the affected Bluetooth btrtl code; affected versions are not specified.