CVE-2023-52864: platform/x86: wmi: Fix opening of char device
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->privatedata, which means that privatedata will not be NULL when wmicharopen() is called. This might cause memory corruption should wmicharopen() be unable to find its driver, something which can happen when the associated WMI device is deleted in wmifreedevices().
Fix the problem by using the miscdevice pointer to retrieve the WMI device data associated with a char device using containerof(). This also avoids wmicharopen() picking a wrong WMI device bound to a driver with the same name as the original driver.
Other sources
In the Linux kernel, the following vulnerability has been resolved:
platform/x86: wmi: Fix opening of char device
The Linux kernel CVE team has assigned CVE-2023-52864 to this issue.
Upstream advisory: https://lore.kernel.org/linux-cve-announce/2024052118-CVE-2023-52864-15cd@gregkh/T
— Red Hat
Linux Kernel is vulnerable to a denial of service, caused by a memory corruption flaw in the wmicharopen() function. By sending a specially crafted request, a local authenticated attacker could exploit this vulnerability to cause a denial of service condition.
— IBM
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2023-52864?
CVE-2023-52864 has been classified as a medium severity vulnerability.
How do I fix CVE-2023-52864?
To address CVE-2023-52864, update the kernel to one of the following versions: 4.19.299, 5.4.261, 5.10.201, 5.15.139, 6.1.63, 6.5.12, 6.6.2, or 6.7.
Which Linux distributions are affected by CVE-2023-52864?
CVE-2023-52864 affects various distributions that utilize the affected versions of the Linux kernel provided by Red Hat.
What components does CVE-2023-52864 impact?
CVE-2023-52864 impacts the WMI char device in the Linux kernel.
Is there a workaround for CVE-2023-52864?
There are no known workarounds for CVE-2023-52864; applying the recommended kernel updates is the suggested solution.