| From bippy-1.2.0 Mon Sep 17 00:00:00 2001 |
| From: Greg Kroah-Hartman <gregkh@kernel.org> |
| To: <linux-cve-announce@vger.kernel.org> |
| Reply-to: <cve@kernel.org>, <linux-kernel@vger.kernel.org> |
| Subject: CVE-2025-37792: Bluetooth: btrtl: Prevent potential NULL dereference |
| |
| Description |
| =========== |
| |
| 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' |
| |
| The Linux kernel CVE team has assigned CVE-2025-37792 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 4.19 with commit 26503ad25de8c7c93a2037f919c2e49a62cf65f1 and fixed in 5.4.293 with commit c3e9717276affe59fd8213706db021b493e81e34 |
| Issue introduced in 4.19 with commit 26503ad25de8c7c93a2037f919c2e49a62cf65f1 and fixed in 5.10.237 with commit 73dc99c0ea94abd22379b2d82cacbc73f3e18ec1 |
| Issue introduced in 4.19 with commit 26503ad25de8c7c93a2037f919c2e49a62cf65f1 and fixed in 5.15.181 with commit 2d7c60c2a38b4b461fa960ad0995136a6bfe0756 |
| Issue introduced in 4.19 with commit 26503ad25de8c7c93a2037f919c2e49a62cf65f1 and fixed in 6.1.135 with commit d8441818690d795232331bd8358545c5c95b6b72 |
| Issue introduced in 4.19 with commit 26503ad25de8c7c93a2037f919c2e49a62cf65f1 and fixed in 6.6.88 with commit 3db6605043b50c8bb768547b23e0222f67ceef3e |
| Issue introduced in 4.19 with commit 26503ad25de8c7c93a2037f919c2e49a62cf65f1 and fixed in 6.12.25 with commit aaf356f872a60db1e96fb762a62c4607fd22741f |
| Issue introduced in 4.19 with commit 26503ad25de8c7c93a2037f919c2e49a62cf65f1 and fixed in 6.14.4 with commit 53ceef799dcfc22c734d600811bfc9dd32eaea0a |
| Issue introduced in 4.19 with commit 26503ad25de8c7c93a2037f919c2e49a62cf65f1 and fixed in 6.15 with commit 324dddea321078a6eeb535c2bff5257be74c9799 |
| |
| Please see https://www.kernel.org for a full list of currently supported |
| kernel versions by the kernel community. |
| |
| Unaffected versions might change over time as fixes are backported to |
| older supported kernel versions. The official CVE entry at |
| https://cve.org/CVERecord/?id=CVE-2025-37792 |
| will be updated if fixes are backported, please check that for the most |
| up to date information about this issue. |
| |
| |
| Affected files |
| ============== |
| |
| The file(s) affected by this issue are: |
| drivers/bluetooth/btrtl.c |
| |
| |
| Mitigation |
| ========== |
| |
| The Linux kernel CVE team recommends that you update to the latest |
| stable kernel version for this, and many other bugfixes. Individual |
| changes are never tested alone, but rather are part of a larger kernel |
| release. Cherry-picking individual commits is not recommended or |
| supported by the Linux kernel community at all. If however, updating to |
| the latest release is impossible, the individual changes to resolve this |
| issue can be found at these commits: |
| https://git.kernel.org/stable/c/c3e9717276affe59fd8213706db021b493e81e34 |
| https://git.kernel.org/stable/c/73dc99c0ea94abd22379b2d82cacbc73f3e18ec1 |
| https://git.kernel.org/stable/c/2d7c60c2a38b4b461fa960ad0995136a6bfe0756 |
| https://git.kernel.org/stable/c/d8441818690d795232331bd8358545c5c95b6b72 |
| https://git.kernel.org/stable/c/3db6605043b50c8bb768547b23e0222f67ceef3e |
| https://git.kernel.org/stable/c/aaf356f872a60db1e96fb762a62c4607fd22741f |
| https://git.kernel.org/stable/c/53ceef799dcfc22c734d600811bfc9dd32eaea0a |
| https://git.kernel.org/stable/c/324dddea321078a6eeb535c2bff5257be74c9799 |
