https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Thu, 01 Oct 2026 17:58:58 +0000 https://vulnerability.circl.lu/vuln/cve-2023-52864 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>platform/x86: wmi: Fix opening of char device</p> <p>Since commit fa1f68db6ca7 (&#34;drivers: misc: pass miscdevice pointer via file private data&#34;), the miscdevice stores a pointer to itself inside filp-&gt;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().</p> <p>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.</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>platform/x86: wmi: Fix opening of char device</p> <p>Since commit fa1f68db6ca7 (&#34;drivers: misc: pass miscdevice pointer via file private data&#34;), the miscdevice stores a pointer to itself inside filp-&gt;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().</p> <p>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.</p> https://vulnerability.circl.lu/vuln/cve-2023-52864