<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Wed, 30 Sep 2026 15:55:56 +0000</lastBuildDate>
    <item>
      <title>CVE-2023-52478 — HID: logitech-hidpp: Fix kernel crash on receiver USB disconnect</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2023-52478</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;HID: logitech-hidpp: Fix kernel crash on receiver USB disconnect&lt;/p&gt;
&lt;p&gt;hidpp_connect_event() has *four* time-of-check vs time-of-use (TOCTOU)
races when it races with itself.&lt;/p&gt;
&lt;p&gt;hidpp_connect_event() primarily runs from a workqueue but it also runs
on probe() and if a &amp;#34;device-connected&amp;#34; 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.&lt;/p&gt;
&lt;p&gt;This opens the following races (note the below code is simplified):&lt;/p&gt;
&lt;p&gt;1. Retrieving + printing the protocol (harmless race):&lt;/p&gt;
&lt;p&gt;if (!hidpp-&amp;gt;protocol_major) {
		hidpp_root_get_protocol_version()
		hidpp-&amp;gt;protocol_major = response.rap.params[0];
	}&lt;/p&gt;
&lt;p&gt;We can actually see this race hit in the dmesg in the abrt output
attached to rhbz#2227968:&lt;/p&gt;
&lt;p&gt;[ 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.&lt;/p&gt;
&lt;p&gt;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:&lt;/p&gt;
&lt;p&gt;2. Updating the name to the HIDPP name (harmless race):&lt;/p&gt;
&lt;p&gt;if (hidpp-&amp;gt;name == hdev-&amp;gt;name) {
		...
		hidpp-&amp;gt;name = new_name;
	}&lt;/p&gt;
&lt;p&gt;3. Initializing the power_supply class for the battery (problematic!):&lt;/p&gt;
&lt;p&gt;hidpp_initialize_battery()
{…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;HID: logitech-hidpp: Fix kernel crash on receiver USB disconnect&lt;/p&gt;
&lt;p&gt;hidpp_connect_event() has *four* time-of-check vs time-of-use (TOCTOU)
races when it races with itself.&lt;/p&gt;
&lt;p&gt;hidpp_connect_event() primarily runs from a workqueue but it also runs
on probe() and if a &amp;#34;device-connected&amp;#34; 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.&lt;/p&gt;
&lt;p&gt;This opens the following races (note the below code is simplified):&lt;/p&gt;
&lt;p&gt;1. Retrieving + printing the protocol (harmless race):&lt;/p&gt;
&lt;p&gt;if (!hidpp-&amp;gt;protocol_major) {
		hidpp_root_get_protocol_version()
		hidpp-&amp;gt;protocol_major = response.rap.params[0];
	}&lt;/p&gt;
&lt;p&gt;We can actually see this race hit in the dmesg in the abrt output
attached to rhbz#2227968:&lt;/p&gt;
&lt;p&gt;[ 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.&lt;/p&gt;
&lt;p&gt;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:&lt;/p&gt;
&lt;p&gt;2. Updating the name to the HIDPP name (harmless race):&lt;/p&gt;
&lt;p&gt;if (hidpp-&amp;gt;name == hdev-&amp;gt;name) {
		...
		hidpp-&amp;gt;name = new_name;
	}&lt;/p&gt;
&lt;p&gt;3. Initializing the power_supply class for the battery (problematic!):&lt;/p&gt;
&lt;p&gt;hidpp_initialize_battery()
{…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2023-52478</guid>
    </item>
  </channel>
</rss>
