Skip to content
CVE Tracker
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • MCP serverPage
  • Data sourcesPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
Back

CVE-2023-52864

platform/x86: wmi: Fix opening of char device

High7.0EPSS 0.27%
Published
Updated
Reserved
Assigned by
Linux

Description

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.

Scores

CVSS scores of CVE-2023-52864, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.0CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Modified3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.27% · top 81% of all CVEs (6 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.0.

Weakness

Affected products

  • Linux · Linux

    • affected 44b6b7661132b1b0e5fd3147ded66f1e4a817ca9 – < cf098e937dd125c0317a0d6f261ac2a950a233d6
    • affected 44b6b7661132b1b0e5fd3147ded66f1e4a817ca9 – < 9fb0eed09e1470cd4021ff52b2b9dfcbcee4c203
    • affected 44b6b7661132b1b0e5fd3147ded66f1e4a817ca9 – < d426a2955e45a95b2282764105fcfb110a540453
    • affected 44b6b7661132b1b0e5fd3147ded66f1e4a817ca9 – < e0bf076b734a2fab92d8fddc2b8b03462eee7097
    • affected 44b6b7661132b1b0e5fd3147ded66f1e4a817ca9 – < 44a96796d25809502c75771d40ee693c2e44724e
    • affected 44b6b7661132b1b0e5fd3147ded66f1e4a817ca9 – < 36d85fa7ae0d6be651c1a745191fa7ef055db43e
    • affected 44b6b7661132b1b0e5fd3147ded66f1e4a817ca9 – < fb7b06b59c6887659c6ed0ecd3110835eecbb6a3
    • affected 44b6b7661132b1b0e5fd3147ded66f1e4a817ca9 – < eba9ac7abab91c8f6d351460239108bef5e7a0b6
  • Linux · Linux

    • affected 4.15
    • unaffected < 4.15
    • unaffected 4.19.299 – ≤ 4.19.*
    • unaffected 5.4.261 – ≤ 5.4.*
    • unaffected 5.10.201 – ≤ 5.10.*
    • unaffected 5.15.139 – ≤ 5.15.*
    • unaffected 6.1.63 – ≤ 6.1.*
    • unaffected 6.5.12 – ≤ 6.5.*
    • unaffected 6.6.2 – ≤ 6.6.*
    • unaffected 6.7 – ≤ *

References (8)

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2023-52864 badge
[![CVE-2023-52864](https://trackcve.app/badge/CVE-2023-52864.svg)](https://trackcve.app/cve/CVE-2023-52864)

Record last updated .