Vulnerability · Published Feb 29, 2024 · Assigned by Linux
CVE-2023-52478HID: logitech-hidpp: Fix kernel crash on receiver USB disconnect
High 8.8
In plain English
A high-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 17% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.
Official description
In the Linux kernel, the following vulnerability has been resolved: HID: logitech-hidpp: Fix kernel crash on receiver USB disconnect hidpp_connect_event() has *four* time-of-check vs time-of-use (TOCTOU) races when it races with itself. hidpp_connect_event() primarily runs from a workqueue but it also runs on probe() and if a "device-connected" packet is received by the hw when the thread running hidpp_connect_event() from probe() is waiting on the hw, then a second thread running hidpp_connect_event() will be started from the workqueue. This opens the following races (note the below code is simplified): 1. Retrieving + printing the protocol (harmless race): if (!hidpp->protocol_major) { hidpp_root_get_protocol_version() hidpp->protocol_major = response.rap.params[0]; } We can actually see this race hit in the dmesg in the abrt output attached to rhbz#2227968: [ 3064.624215] logitech-hidpp-device 0003:046D:4071.0049: HID++ 4.5 device connected. [ 3064.658184] logitech-hidpp-device 0003:046D:4071.0049: HID++ 4.5 device connected. Testing with extra logging added has shown that after this the 2 threads take turn grabbing the hw access mutex (send_mutex) so they ping-pong through all the other TOCTOU cases managing to hit all of them: 2. Updating the name to the HIDPP name (harmless race): if (hidpp->name == hdev->name) { ... hidpp->name = new_name; } 3. Initializing the power_supply class for the battery (problematic!): hidpp_initialize_battery() { if (hidpp->battery.ps) return 0; probe_battery(); /* Blocks, threads take turns executing this */ hidpp->battery.desc.properties = devm_kmemdup(dev, hidpp_battery_props, cnt, GFP_KERNEL); hidpp->battery.ps = devm_power_supply_register(&hidpp->hid_dev->dev, &hidpp->battery.desc, cfg); } 4. Creating delayed input_device (potentially problematic): if (hidpp->delayed_input) return; hidpp->delayed_input = hidpp_allocate_input(hdev); The really big problem here is 3. Hitting the race leads to the following sequence: hidpp->battery.desc.properties = devm_kmemdup(dev, hidpp_battery_props, cnt, GFP_KERNEL); hidpp->battery.ps = devm_power_supply_register(&hidpp->hid_dev->dev, &hidpp->battery.desc, cfg); ... hidpp->battery.desc.properties = devm_kmemdup(dev, hidpp_battery_props, cnt, GFP_KERNEL); hidpp->battery.ps = devm_power_supply_register(&hidpp->hid_dev->dev, &hidpp->battery.desc, cfg); So now we have registered 2 power supplies for the same battery, which looks a bit weird from userspace's pov but this is not even the really big problem. Notice how: 1. This is all devm-maganaged 2. The hidpp->battery.desc struct is shared between the 2 power supplies 3. hidpp->battery.desc.properties points to the result from the second devm_kmemdup() This causes a use after free scenario on USB disconnect of the receiver: 1. The last registered power supply class device gets unregistered 2. The memory from the last devm_kmemdup() call gets freed, hidpp->battery.desc.properties now points to freed memory 3. The first registered power supply class device gets unregistered, this involves sending a remove uevent to userspace which invokes power_supply_uevent() to fill the uevent data 4. power_supply_uevent() uses hidpp->battery.desc.properties which now points to freed memory leading to backtraces like this one: Sep 22 20:01:35 eric kernel: BUG: unable to handle page fault for address: ffffb2140e017f08 ... Sep 22 20:01:35 eric kernel: Workqueue: usb_hub_wq hub_event Sep 22 20:01:35 eric kernel: RIP: 0010:power_supply_uevent+0xee/0x1d0 ... Sep 22 20:01:35 eric kernel: ? asm_exc_page_fault+0x26/0x30 Sep 22 20:01:35 eric kernel: ? power_supply_uevent+0xee/0x1d0 Sep 22 20:01:35 eric kernel: ? power_supply_uevent+0x10d/0x1d0 Sep 22 20:01:35 eric kernel: dev_uevent+0x10f/0x2d0 Sep 22 20:01:35 eric kernel: kobject_uevent_env+0x291/0x680 Sep 22 20:01:35 eric kernel: ---truncated---
Affected packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| AlmaLinux:8 | bpftool | 4.18.0-553.22.1.el8_10 | ALSA-2024:7000 |
| AlmaLinux:8 | kernel | 4.18.0-553.22.1.el8_10 | ALSA-2024:7000 |
| AlmaLinux:8 | kernel-abi-stablelists | 4.18.0-553.22.1.el8_10 | ALSA-2024:7000 |
| AlmaLinux:8 | kernel-core | 4.18.0-553.22.1.el8_10 | ALSA-2024:7000 |
| AlmaLinux:8 | kernel-cross-headers | 4.18.0-553.22.1.el8_10 | ALSA-2024:7000 |
| AlmaLinux:8 | kernel-debug | 4.18.0-553.22.1.el8_10 | ALSA-2024:7000 |
| AlmaLinux:8 | kernel-debug-core | 4.18.0-553.22.1.el8_10 | ALSA-2024:7000 |
| AlmaLinux:8 | kernel-debug-devel | 4.18.0-553.22.1.el8_10 | ALSA-2024:7000 |
| AlmaLinux:8 | kernel-debug-modules | 4.18.0-553.22.1.el8_10 | ALSA-2024:7000 |
| AlmaLinux:8 | kernel-debug-modules-extra | 4.18.0-553.22.1.el8_10 | ALSA-2024:7000 |
| AlmaLinux:8 | kernel-devel | 4.18.0-553.22.1.el8_10 | ALSA-2024:7000 |
| AlmaLinux:8 | kernel-doc | 4.18.0-553.22.1.el8_10 | ALSA-2024:7000 |
| AlmaLinux:8 | kernel-headers | 4.18.0-553.22.1.el8_10 | ALSA-2024:7000 |
| AlmaLinux:8 | kernel-modules | 4.18.0-553.22.1.el8_10 | ALSA-2024:7000 |
| AlmaLinux:8 | kernel-modules-extra | 4.18.0-553.22.1.el8_10 | ALSA-2024:7000 |
| AlmaLinux:8 | kernel-rt | 4.18.0-553.22.1.rt7.363.el8_10 | ALSA-2024:7001 |
| AlmaLinux:8 | kernel-rt-core | 4.18.0-553.22.1.rt7.363.el8_10 | ALSA-2024:7001 |
| AlmaLinux:8 | kernel-rt-debug | 4.18.0-553.22.1.rt7.363.el8_10 | ALSA-2024:7001 |
| AlmaLinux:8 | kernel-rt-debug-core | 4.18.0-553.22.1.rt7.363.el8_10 | ALSA-2024:7001 |
| AlmaLinux:8 | kernel-rt-debug-devel | 4.18.0-553.22.1.rt7.363.el8_10 | ALSA-2024:7001 |
| AlmaLinux:8 | kernel-rt-debug-kvm | 4.18.0-553.22.1.rt7.363.el8_10 | ALSA-2024:7001 |
| AlmaLinux:8 | kernel-rt-debug-modules | 4.18.0-553.22.1.rt7.363.el8_10 | ALSA-2024:7001 |
| AlmaLinux:8 | kernel-rt-debug-modules-extra | 4.18.0-553.22.1.rt7.363.el8_10 | ALSA-2024:7001 |
| AlmaLinux:8 | kernel-rt-devel | 4.18.0-553.22.1.rt7.363.el8_10 | ALSA-2024:7001 |
| AlmaLinux:8 | kernel-rt-kvm | 4.18.0-553.22.1.rt7.363.el8_10 | ALSA-2024:7001 |
| AlmaLinux:8 | kernel-rt-modules | 4.18.0-553.22.1.rt7.363.el8_10 | ALSA-2024:7001 |
| AlmaLinux:8 | kernel-rt-modules-extra | 4.18.0-553.22.1.rt7.363.el8_10 | ALSA-2024:7001 |
| AlmaLinux:8 | kernel-tools | 4.18.0-553.22.1.el8_10 | ALSA-2024:7000 |
| AlmaLinux:8 | kernel-tools-libs | 4.18.0-553.22.1.el8_10 | ALSA-2024:7000 |
| AlmaLinux:8 | kernel-tools-libs-devel | 4.18.0-553.22.1.el8_10 | ALSA-2024:7000 |
| AlmaLinux:8 | kernel-zfcpdump | 4.18.0-553.22.1.el8_10 | ALSA-2024:7000 |
| AlmaLinux:8 | kernel-zfcpdump-core | 4.18.0-553.22.1.el8_10 | ALSA-2024:7000 |
| AlmaLinux:8 | kernel-zfcpdump-devel | 4.18.0-553.22.1.el8_10 | ALSA-2024:7000 |
| AlmaLinux:8 | kernel-zfcpdump-modules | 4.18.0-553.22.1.el8_10 | ALSA-2024:7000 |
| AlmaLinux:8 | kernel-zfcpdump-modules-extra | 4.18.0-553.22.1.el8_10 | ALSA-2024:7000 |
| AlmaLinux:8 | perf | 4.18.0-553.22.1.el8_10 | ALSA-2024:7000 |
| AlmaLinux:8 | python3-perf | 4.18.0-553.22.1.el8_10 | ALSA-2024:7000 |
| Debian:12 | linux | 6.1.64-1 | DEBIAN-CVE-2023-52478 |
| Debian:13 | linux | 6.5.8-1 | DEBIAN-CVE-2023-52478 |
| Debian:14 | linux | 6.5.8-1 | DEBIAN-CVE-2023-52478 |
| Rocky Linux:8 | kernel | 0:4.18.0-553.22.1.el8_10 | RLSA-2024:7000 |
| Rocky Linux:8 | kernel-rt | 0:4.18.0-553.22.1.rt7.363.el8_10 | RLSA-2024:7001 |
| Ubuntu:22.04:LTS | linux | 5.15.0-94.104 | UBUNTU-CVE-2023-52478 |
| Ubuntu:22.04:LTS | linux-allwinner-5.19 | no fix listed | UBUNTU-CVE-2023-52478 |
| Ubuntu:22.04:LTS | linux-aws | 5.15.0-1053.58 | UBUNTU-CVE-2023-52478 |
| Ubuntu:22.04:LTS | linux-aws-5.19 | no fix listed | UBUNTU-CVE-2023-52478 |
| Ubuntu:22.04:LTS | linux-aws-6.2 | no fix listed | UBUNTU-CVE-2023-52478 |
| Ubuntu:22.04:LTS | linux-aws-6.5 | no fix listed | UBUNTU-CVE-2023-52478 |
| Ubuntu:22.04:LTS | linux-azure | 5.15.0-1056.64 | UBUNTU-CVE-2023-52478 |
| Ubuntu:22.04:LTS | linux-azure-5.19 | no fix listed | UBUNTU-CVE-2023-52478 |
| Ubuntu:22.04:LTS | linux-azure-6.2 | no fix listed | UBUNTU-CVE-2023-52478 |
| Ubuntu:22.04:LTS | linux-azure-6.5 | no fix listed | UBUNTU-CVE-2023-52478 |
| Ubuntu:22.04:LTS | linux-azure-fde | 5.15.0-1056.64.1 | UBUNTU-CVE-2023-52478 |
| Ubuntu:22.04:LTS | linux-azure-fde-5.19 | no fix listed | UBUNTU-CVE-2023-52478 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.2 | no fix listed | UBUNTU-CVE-2023-52478 |
| Ubuntu:22.04:LTS | linux-gcp | 5.15.0-1051.59 | UBUNTU-CVE-2023-52478 |
| Ubuntu:22.04:LTS | linux-gcp-5.19 | no fix listed | UBUNTU-CVE-2023-52478 |
| Ubuntu:22.04:LTS | linux-gcp-6.2 | no fix listed | UBUNTU-CVE-2023-52478 |
| Ubuntu:22.04:LTS | linux-gcp-6.5 | no fix listed | UBUNTU-CVE-2023-52478 |
| Ubuntu:22.04:LTS | linux-gke | 5.15.0-1050.55 | UBUNTU-CVE-2023-52478 |
| Ubuntu:22.04:LTS | linux-gkeop | 5.15.0-1036.42 | UBUNTU-CVE-2023-52478 |
| Ubuntu:22.04:LTS | linux-hwe-5.19 | no fix listed | UBUNTU-CVE-2023-52478 |
| Ubuntu:22.04:LTS | linux-hwe-6.2 | no fix listed | UBUNTU-CVE-2023-52478 |
| Ubuntu:22.04:LTS | linux-hwe-6.5 | no fix listed | UBUNTU-CVE-2023-52478 |
| Ubuntu:22.04:LTS | linux-ibm | 5.15.0-1046.49 | UBUNTU-CVE-2023-52478 |
| Ubuntu:22.04:LTS | linux-intel-iotg | 5.15.0-1047.53 | UBUNTU-CVE-2023-52478 |
| Ubuntu:22.04:LTS | linux-kvm | 5.15.0-1050.55 | UBUNTU-CVE-2023-52478 |
| Ubuntu:22.04:LTS | linux-lowlatency | 5.15.0-94.104 | UBUNTU-CVE-2023-52478 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-5.19 | no fix listed | UBUNTU-CVE-2023-52478 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.2 | no fix listed | UBUNTU-CVE-2023-52478 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.5 | no fix listed | UBUNTU-CVE-2023-52478 |
| Ubuntu:22.04:LTS | linux-nvidia | 5.15.0-1044.44 | UBUNTU-CVE-2023-52478 |
| Ubuntu:22.04:LTS | linux-nvidia-6.2 | no fix listed | UBUNTU-CVE-2023-52478 |
| Ubuntu:22.04:LTS | linux-nvidia-6.5 | 6.5.0-1014.14 | UBUNTU-CVE-2023-52478 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra | 5.15.0-1022.22 | UBUNTU-CVE-2023-52478 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra-igx | 5.15.0-1009.9 | UBUNTU-CVE-2023-52478 |
| Ubuntu:22.04:LTS | linux-oem-5.17 | no fix listed | UBUNTU-CVE-2023-52478 |
| Ubuntu:22.04:LTS | linux-oem-6.0 | no fix listed | UBUNTU-CVE-2023-52478 |
| Ubuntu:22.04:LTS | linux-oem-6.1 | no fix listed | UBUNTU-CVE-2023-52478 |
| Ubuntu:22.04:LTS | linux-oem-6.5 | no fix listed | UBUNTU-CVE-2023-52478 |
| Ubuntu:22.04:LTS | linux-oracle | 5.15.0-1051.57 | UBUNTU-CVE-2023-52478 |
| Ubuntu:22.04:LTS | linux-oracle-6.5 | no fix listed | UBUNTU-CVE-2023-52478 |
| Ubuntu:22.04:LTS | linux-raspi | 5.15.0-1046.49 | UBUNTU-CVE-2023-52478 |
| Ubuntu:24.04:LTS | linux-raspi-realtime | no fix listed | UBUNTU-CVE-2023-52478 |
| Ubuntu:22.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2023-52478 |
| Ubuntu:22.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2023-52478 |
| Ubuntu:22.04:LTS | linux-riscv-5.19 | no fix listed | UBUNTU-CVE-2023-52478 |
| Ubuntu:22.04:LTS | linux-starfive-5.19 | no fix listed | UBUNTU-CVE-2023-52478 |
| Ubuntu:22.04:LTS | linux-starfive-6.2 | no fix listed | UBUNTU-CVE-2023-52478 |
| Ubuntu:22.04:LTS | linux-xilinx-zynqmp | 5.15.0-1027.31 | UBUNTU-CVE-2023-52478 |
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | c39e3d5fc9dd3e16c6f59dd94d827540040de66d – before ca0c4cc1d215dc22ab0e738c9f017c650f3183f5c39e3d5fc9dd3e16c6f59dd94d827540040de66d – before 44481b244fcaa2b895a53081d6204c574720c38cc39e3d5fc9dd3e16c6f59dd94d827540040de66d – before cd0e2bf7fb22fe9b989c59c42dca06367fd10e6bc39e3d5fc9dd3e16c6f59dd94d827540040de66d – before 093af62c023537f097d2ebdfaa0bc7c1a6e874e1c39e3d5fc9dd3e16c6f59dd94d827540040de66d – before 28ddc1e0b898291323b62d770b1b931de131a528c39e3d5fc9dd3e16c6f59dd94d827540040de66d – before fd72ac9556a473fc7daf54efb6ca8a97180d621dc39e3d5fc9dd3e16c6f59dd94d827540040de66d – before f7b2c7d9831af99369fe8ad9b2a68d78942f414ec39e3d5fc9dd3e16c6f59dd94d827540040de66d – before dac501397b9d81e4782232c39f94f4307b137452 |
| Linux | Linux | 3.19 |
References
- https://git.kernel.org/stable/c/ca0c4cc1d215dc22ab0e738c9f017c650f3183f5
- https://git.kernel.org/stable/c/44481b244fcaa2b895a53081d6204c574720c38c
- https://git.kernel.org/stable/c/cd0e2bf7fb22fe9b989c59c42dca06367fd10e6b
- https://git.kernel.org/stable/c/093af62c023537f097d2ebdfaa0bc7c1a6e874e1
- https://git.kernel.org/stable/c/28ddc1e0b898291323b62d770b1b931de131a528
- https://git.kernel.org/stable/c/fd72ac9556a473fc7daf54efb6ca8a97180d621d
- https://git.kernel.org/stable/c/f7b2c7d9831af99369fe8ad9b2a68d78942f414e
- https://git.kernel.org/stable/c/dac501397b9d81e4782232c39f94f4307b137452