Linux kernel registration state inconsistency in Steam HID
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 385a4886778f6d6e61eff1d4d295af332d7130e1 · < cf71a6ee1d4e36b8e65b81c064e2797a10247280| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
HID: steam: Refactor registration
This refactors and simplifies the registration/unregistration flow. Since we now only perform registration when the client isn't opened anymore, the logic for handling that can be removed, and the rest of the function streamlined.
We also remove the previous assumption that we have a serial number to show we're registered, replacing it with a single purpose boolean.
In a previous refactor the code for unregistering a battery if later registration steps failed was accidentally left out. As a result, a lingering power_supply object could get left over after the steam object was torn down. This is also fixed here.
From the CVE record · Linux
The Linux kernel’s HID steam registration flow can leave a power_supply object behind when later registration steps fail and the steam object is torn down. The input does not describe what an attacker could do or whether exploitation requires network access, local access, authentication, or user interaction.
Engineers running Linux kernels with the HID steam component should check their versions; affected versions are not specified.