platform/x86: wmi: Fix opening of char device
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 44b6b7661132b1b0e5fd3147ded66f1e4a817ca9 · < 36d85fa7ae0d6be651c1a745191fa7ef055db43e| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
platform/x86: wmi: Fix opening of char device
Since commit fa1f68db6ca7 ("drivers: misc: pass miscdevice pointer via file private data"), the miscdevice stores a pointer to itself inside filp->private_data, which means that private_data will not be NULL when wmi_char_open() is called. This might cause memory corruption should wmi_char_open() be unable to find its driver, something which can happen when the associated WMI device is deleted in wmi_free_devices().
Fix the problem by using the miscdevice pointer to retrieve the WMI device data associated with a char device using container_of(). This also avoids wmi_char_open() picking a wrong WMI device bound to a driver with the same name as the original driver.
From the CVE record · Linux
The Linux kernel's WMI character-device open path can mishandle device data. Memory corruption may occur if the associated WMI device is deleted and the open path cannot find its driver. The input does not specify authentication or user-interaction requirements.
Engineers running Linux kernels with the affected WMI character-device code should check their versions; no affected version range is provided.