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.

Severity (CVSS 3.1)8.8High
Exploit odds (30 days)0.3%top 83.1% of all CVEs
Exploited in the wildNo reportsCISA SSVC: none
Attack toolingNoneno public tooling known

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

EcosystemPackageFixed inAdvisory
AlmaLinux:8bpftool4.18.0-553.22.1.el8_10ALSA-2024:7000
AlmaLinux:8kernel4.18.0-553.22.1.el8_10ALSA-2024:7000
AlmaLinux:8kernel-abi-stablelists4.18.0-553.22.1.el8_10ALSA-2024:7000
AlmaLinux:8kernel-core4.18.0-553.22.1.el8_10ALSA-2024:7000
AlmaLinux:8kernel-cross-headers4.18.0-553.22.1.el8_10ALSA-2024:7000
AlmaLinux:8kernel-debug4.18.0-553.22.1.el8_10ALSA-2024:7000
AlmaLinux:8kernel-debug-core4.18.0-553.22.1.el8_10ALSA-2024:7000
AlmaLinux:8kernel-debug-devel4.18.0-553.22.1.el8_10ALSA-2024:7000
AlmaLinux:8kernel-debug-modules4.18.0-553.22.1.el8_10ALSA-2024:7000
AlmaLinux:8kernel-debug-modules-extra4.18.0-553.22.1.el8_10ALSA-2024:7000
AlmaLinux:8kernel-devel4.18.0-553.22.1.el8_10ALSA-2024:7000
AlmaLinux:8kernel-doc4.18.0-553.22.1.el8_10ALSA-2024:7000
AlmaLinux:8kernel-headers4.18.0-553.22.1.el8_10ALSA-2024:7000
AlmaLinux:8kernel-modules4.18.0-553.22.1.el8_10ALSA-2024:7000
AlmaLinux:8kernel-modules-extra4.18.0-553.22.1.el8_10ALSA-2024:7000
AlmaLinux:8kernel-rt4.18.0-553.22.1.rt7.363.el8_10ALSA-2024:7001
AlmaLinux:8kernel-rt-core4.18.0-553.22.1.rt7.363.el8_10ALSA-2024:7001
AlmaLinux:8kernel-rt-debug4.18.0-553.22.1.rt7.363.el8_10ALSA-2024:7001
AlmaLinux:8kernel-rt-debug-core4.18.0-553.22.1.rt7.363.el8_10ALSA-2024:7001
AlmaLinux:8kernel-rt-debug-devel4.18.0-553.22.1.rt7.363.el8_10ALSA-2024:7001
AlmaLinux:8kernel-rt-debug-kvm4.18.0-553.22.1.rt7.363.el8_10ALSA-2024:7001
AlmaLinux:8kernel-rt-debug-modules4.18.0-553.22.1.rt7.363.el8_10ALSA-2024:7001
AlmaLinux:8kernel-rt-debug-modules-extra4.18.0-553.22.1.rt7.363.el8_10ALSA-2024:7001
AlmaLinux:8kernel-rt-devel4.18.0-553.22.1.rt7.363.el8_10ALSA-2024:7001
AlmaLinux:8kernel-rt-kvm4.18.0-553.22.1.rt7.363.el8_10ALSA-2024:7001
AlmaLinux:8kernel-rt-modules4.18.0-553.22.1.rt7.363.el8_10ALSA-2024:7001
AlmaLinux:8kernel-rt-modules-extra4.18.0-553.22.1.rt7.363.el8_10ALSA-2024:7001
AlmaLinux:8kernel-tools4.18.0-553.22.1.el8_10ALSA-2024:7000
AlmaLinux:8kernel-tools-libs4.18.0-553.22.1.el8_10ALSA-2024:7000
AlmaLinux:8kernel-tools-libs-devel4.18.0-553.22.1.el8_10ALSA-2024:7000
AlmaLinux:8kernel-zfcpdump4.18.0-553.22.1.el8_10ALSA-2024:7000
AlmaLinux:8kernel-zfcpdump-core4.18.0-553.22.1.el8_10ALSA-2024:7000
AlmaLinux:8kernel-zfcpdump-devel4.18.0-553.22.1.el8_10ALSA-2024:7000
AlmaLinux:8kernel-zfcpdump-modules4.18.0-553.22.1.el8_10ALSA-2024:7000
AlmaLinux:8kernel-zfcpdump-modules-extra4.18.0-553.22.1.el8_10ALSA-2024:7000
AlmaLinux:8perf4.18.0-553.22.1.el8_10ALSA-2024:7000
AlmaLinux:8python3-perf4.18.0-553.22.1.el8_10ALSA-2024:7000
Debian:12linux6.1.64-1DEBIAN-CVE-2023-52478
Debian:13linux6.5.8-1DEBIAN-CVE-2023-52478
Debian:14linux6.5.8-1DEBIAN-CVE-2023-52478
Rocky Linux:8kernel0:4.18.0-553.22.1.el8_10RLSA-2024:7000
Rocky Linux:8kernel-rt0:4.18.0-553.22.1.rt7.363.el8_10RLSA-2024:7001
Ubuntu:22.04:LTSlinux5.15.0-94.104UBUNTU-CVE-2023-52478
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2023-52478
Ubuntu:22.04:LTSlinux-aws5.15.0-1053.58UBUNTU-CVE-2023-52478
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2023-52478
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2023-52478
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2023-52478
Ubuntu:22.04:LTSlinux-azure5.15.0-1056.64UBUNTU-CVE-2023-52478
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2023-52478
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2023-52478
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2023-52478
Ubuntu:22.04:LTSlinux-azure-fde5.15.0-1056.64.1UBUNTU-CVE-2023-52478
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2023-52478
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2023-52478
Ubuntu:22.04:LTSlinux-gcp5.15.0-1051.59UBUNTU-CVE-2023-52478
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2023-52478
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2023-52478
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2023-52478
Ubuntu:22.04:LTSlinux-gke5.15.0-1050.55UBUNTU-CVE-2023-52478
Ubuntu:22.04:LTSlinux-gkeop5.15.0-1036.42UBUNTU-CVE-2023-52478
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2023-52478
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2023-52478
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2023-52478
Ubuntu:22.04:LTSlinux-ibm5.15.0-1046.49UBUNTU-CVE-2023-52478
Ubuntu:22.04:LTSlinux-intel-iotg5.15.0-1047.53UBUNTU-CVE-2023-52478
Ubuntu:22.04:LTSlinux-kvm5.15.0-1050.55UBUNTU-CVE-2023-52478
Ubuntu:22.04:LTSlinux-lowlatency5.15.0-94.104UBUNTU-CVE-2023-52478
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2023-52478
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2023-52478
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2023-52478
Ubuntu:22.04:LTSlinux-nvidia5.15.0-1044.44UBUNTU-CVE-2023-52478
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2023-52478
Ubuntu:22.04:LTSlinux-nvidia-6.56.5.0-1014.14UBUNTU-CVE-2023-52478
Ubuntu:22.04:LTSlinux-nvidia-tegra5.15.0-1022.22UBUNTU-CVE-2023-52478
Ubuntu:22.04:LTSlinux-nvidia-tegra-igx5.15.0-1009.9UBUNTU-CVE-2023-52478
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2023-52478
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2023-52478
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2023-52478
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2023-52478
Ubuntu:22.04:LTSlinux-oracle5.15.0-1051.57UBUNTU-CVE-2023-52478
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2023-52478
Ubuntu:22.04:LTSlinux-raspi5.15.0-1046.49UBUNTU-CVE-2023-52478
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2023-52478
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2023-52478
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2023-52478
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2023-52478
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2023-52478
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2023-52478
Ubuntu:22.04:LTSlinux-xilinx-zynqmp5.15.0-1027.31UBUNTU-CVE-2023-52478

Affected products (as reported)

VendorProductVersions
Linux Linux c39e3d5fc9dd3e16c6f59dd94d827540040de66d – before ca0c4cc1d215dc22ab0e738c9f017c650f3183f5c39e3d5fc9dd3e16c6f59dd94d827540040de66d – before 44481b244fcaa2b895a53081d6204c574720c38cc39e3d5fc9dd3e16c6f59dd94d827540040de66d – before cd0e2bf7fb22fe9b989c59c42dca06367fd10e6bc39e3d5fc9dd3e16c6f59dd94d827540040de66d – before 093af62c023537f097d2ebdfaa0bc7c1a6e874e1c39e3d5fc9dd3e16c6f59dd94d827540040de66d – before 28ddc1e0b898291323b62d770b1b931de131a528c39e3d5fc9dd3e16c6f59dd94d827540040de66d – before fd72ac9556a473fc7daf54efb6ca8a97180d621dc39e3d5fc9dd3e16c6f59dd94d827540040de66d – before f7b2c7d9831af99369fe8ad9b2a68d78942f414ec39e3d5fc9dd3e16c6f59dd94d827540040de66d – before dac501397b9d81e4782232c39f94f4307b137452
Linux Linux 3.19

References