ACPI: scan: fix bus ID cleanup on device_add() failures
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ d783156ea38431b20af0d4f910a6f9f9054d33b9 · < a414485ebc2aa50907d0ce97cde2b1a353696897| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
ACPI: scan: fix bus ID cleanup on device_add() failures
When device_add() fails after acpi_device_set_name() has allocated an instance ID and a new acpi_device_bus_id has been linked into acpi_bus_id_list, the rollback path only removes wakeup_list and detaches the ACPI handle data.
That leaves the bus-ID bookkeeping behind and keeps the allocated instance number consumed.
Move the bus-ID cleanup and wakeup-list removal into a single helper.
Use it from both the normal device teardown path and the device_add() rollback path. The wakeup list node is initialized before registration, so it can be deleted without checking whether the device is wakeup- capable like in the original teardown path.
[ rjw: Rename acpi_device_del_list() to acpi_device_cleanup() ] [ rjw: Subject and changelog edits ]
From the CVE record · Linux
If device_add() fails after ACPI allocates an instance ID, the rollback leaves bus-ID bookkeeping behind and keeps the instance number consumed. The input does not describe an attacker-controlled trigger or specify network access, authentication, or user interaction requirements.
Engineers running the Linux kernel should check their versions; affected versions are not specified.