Vulnerability · Published Feb 25, 2024 · Assigned by Linux
CVE-2023-52473thermal: core: Fix NULL pointer dereference in zone registration error path
Medium 5.5
In plain English
A medium-severity security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.3% (higher than 20% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.
Official description
In the Linux kernel, the following vulnerability has been resolved: thermal: core: Fix NULL pointer dereference in zone registration error path If device_register() in thermal_zone_device_register_with_trips() returns an error, the tz variable is set to NULL and subsequently dereferenced in kfree(tz->tzp). Commit adc8749b150c ("thermal/drivers/core: Use put_device() if device_register() fails") added the tz = NULL assignment in question to avoid a possible double-free after dropping the reference to the zone device. However, after commit 4649620d9404 ("thermal: core: Make thermal_zone_device_unregister() return after freeing the zone"), that assignment has become redundant, because dropping the reference to the zone device does not cause the zone object to be freed any more. Drop it to address the NULL pointer dereference.
Affected packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian:13 | linux | 6.6.15-1 | DEBIAN-CVE-2023-52473 |
| Debian:14 | linux | 6.6.15-1 | DEBIAN-CVE-2023-52473 |
| Ubuntu:22.04:LTS | linux-allwinner-5.19 | no fix listed | UBUNTU-CVE-2023-52473 |
| Ubuntu:22.04:LTS | linux-aws-5.19 | no fix listed | UBUNTU-CVE-2023-52473 |
| Ubuntu:22.04:LTS | linux-aws-6.2 | no fix listed | UBUNTU-CVE-2023-52473 |
| Ubuntu:22.04:LTS | linux-aws-6.5 | no fix listed | UBUNTU-CVE-2023-52473 |
| Ubuntu:22.04:LTS | linux-azure-5.19 | no fix listed | UBUNTU-CVE-2023-52473 |
| Ubuntu:22.04:LTS | linux-azure-6.2 | no fix listed | UBUNTU-CVE-2023-52473 |
| Ubuntu:22.04:LTS | linux-azure-6.5 | 6.5.0-1022.23~22.04.1 | USN-6819-1 |
| Ubuntu:22.04:LTS | linux-azure-6.5 | 6.5.0-1022.23~22.04.1 | UBUNTU-CVE-2023-52473 |
| Ubuntu:22.04:LTS | linux-azure-fde-5.19 | no fix listed | UBUNTU-CVE-2023-52473 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.2 | no fix listed | UBUNTU-CVE-2023-52473 |
| Ubuntu:22.04:LTS | linux-gcp-5.19 | no fix listed | UBUNTU-CVE-2023-52473 |
| Ubuntu:22.04:LTS | linux-gcp-6.2 | no fix listed | UBUNTU-CVE-2023-52473 |
| Ubuntu:22.04:LTS | linux-gcp-6.5 | 6.5.0-1022.24~22.04.1 | USN-6818-1 |
| Ubuntu:22.04:LTS | linux-gcp-6.5 | 6.5.0-1022.24~22.04.1 | UBUNTU-CVE-2023-52473 |
| Ubuntu:22.04:LTS | linux-hwe-5.19 | no fix listed | UBUNTU-CVE-2023-52473 |
| Ubuntu:22.04:LTS | linux-hwe-6.2 | no fix listed | UBUNTU-CVE-2023-52473 |
| Ubuntu:22.04:LTS | linux-hwe-6.5 | 6.5.0-41.41~22.04.2 | USN-6818-4 |
| Ubuntu:22.04:LTS | linux-hwe-6.5 | 6.5.0-41.41~22.04.2 | UBUNTU-CVE-2023-52473 |
| Ubuntu:22.04:LTS | linux-intel-iot-realtime | no fix listed | UBUNTU-CVE-2023-52473 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-5.19 | no fix listed | UBUNTU-CVE-2023-52473 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.2 | no fix listed | UBUNTU-CVE-2023-52473 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.5 | 6.5.0-41.41.1~22.04.1 | USN-6818-1 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.5 | 6.5.0-41.41.1~22.04.1 | UBUNTU-CVE-2023-52473 |
| Ubuntu:22.04:LTS | linux-nvidia-6.2 | no fix listed | UBUNTU-CVE-2023-52473 |
| Ubuntu:22.04:LTS | linux-nvidia-6.5 | 6.5.0-1021.22 | USN-6818-3 |
| Ubuntu:22.04:LTS | linux-nvidia-6.5 | 6.5.0-1021.22 | UBUNTU-CVE-2023-52473 |
| Ubuntu:22.04:LTS | linux-oem-5.17 | no fix listed | UBUNTU-CVE-2023-52473 |
| Ubuntu:22.04:LTS | linux-oem-6.0 | no fix listed | UBUNTU-CVE-2023-52473 |
| Ubuntu:22.04:LTS | linux-oem-6.5 | 6.5.0-1024.25 | UBUNTU-CVE-2023-52473 |
| Ubuntu:22.04:LTS | linux-oem-6.5 | 6.5.0-1024.25 | USN-6819-3 |
| Ubuntu:22.04:LTS | linux-oracle-6.5 | 6.5.0-1024.24~22.04.1 | USN-6819-4 |
| Ubuntu:22.04:LTS | linux-oracle-6.5 | 6.5.0-1024.24~22.04.1 | UBUNTU-CVE-2023-52473 |
| Ubuntu:22.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2023-52473 |
| Ubuntu:22.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2023-52473 |
| Ubuntu:22.04:LTS | linux-riscv-5.19 | no fix listed | UBUNTU-CVE-2023-52473 |
| Ubuntu:22.04:LTS | linux-riscv-6.5 | 6.5.0-40.40.1~22.04.1 | UBUNTU-CVE-2023-52473 |
| Ubuntu:22.04:LTS | linux-starfive-5.19 | no fix listed | UBUNTU-CVE-2023-52473 |
| Ubuntu:22.04:LTS | linux-starfive-6.2 | no fix listed | UBUNTU-CVE-2023-52473 |
| Ubuntu:22.04:LTS | linux-starfive-6.5 | 6.5.0-1015.16~22.04.1 | UBUNTU-CVE-2023-52473 |
| Ubuntu:22.04:LTS | linux-starfive-6.5 | 6.5.0-1015.16~22.04.1 | USN-6819-1 |
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 3d439b1a2ad36c8b4ea151c8de25309d60d17407 – before 335176dd8ebaca6493807dceea33c478305667fa3d439b1a2ad36c8b4ea151c8de25309d60d17407 – before 02871710b93058eb1249d5847c0b2d1c2c3c98ae3d439b1a2ad36c8b4ea151c8de25309d60d17407 – before 04e6ccfc93c5a1aa1d75a537cf27e418895e20ea |
| Linux | Linux | 6.4 |