CVE-2023-52864

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2024-05-21. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
35(Track)
EG Risk 35/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
18%
KEV
Not listed

Published

May 21, 2024

Last Modified

August 5, 2026

Advisory Details (8)

Auto-updated Aug 4, 2026
No patch confirmed yet.
generic

platform/x86: wmi: Fix opening of char device - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/44a96796d25809502c75771d40ee693c2e44724e
generic

platform/x86: wmi: Fix opening of char device - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/36d85fa7ae0d6be651c1a745191fa7ef055db43e
generic

platform/x86: wmi: Fix opening of char device - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/fb7b06b59c6887659c6ed0ecd3110835eecbb6a3
generic

platform/x86: wmi: Fix opening of char device - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/eba9ac7abab91c8f6d351460239108bef5e7a0b6
generic

platform/x86: wmi: Fix opening of char device - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/e0bf076b734a2fab92d8fddc2b8b03462eee7097
generic

platform/x86: wmi: Fix opening of char device - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d426a2955e45a95b2282764105fcfb110a540453
generic

platform/x86: wmi: Fix opening of char device - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/cf098e937dd125c0317a0d6f261ac2a950a233d6
generic

platform/x86: wmi: Fix opening of char device - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9fb0eed09e1470cd4021ff52b2b9dfcbcee4c203

Patch Availability(8)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatkernel-0:4.18.0-477.74.1.el8_82024-09-24redhat
redhatkernel-0:4.18.0-372.119.1.el8_62024-08-21redhat
redhatkernel-0:5.14.0-427.31.1.el9_42024-08-15redhat
redhatkernel-rt-0:5.14.0-284.79.1.rt14.364.el9_22024-08-14redhat
redhatkernel-0:5.14.0-284.79.1.el9_22024-08-14redhat
redhatkernel-0:4.18.0-553.16.1.el8_102024-08-08redhat
redhatkernel-rt-0:4.18.0-553.16.1.rt7.357.el8_102024-08-08redhat
linuxKernel @ 4.19.299osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(2)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 15× in last 7d / 49× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 123 total refreshes for this CVE.

  1. 2026-08-07 16:25 UTCEPSS rescore
  2. 2026-08-06 13:45 UTCEPSS rescore
  3. 2026-08-05 19:15 UTCEPSS rescore
  4. 2026-08-05 19:15 UTCEPSS rescore
  5. 2026-08-05 10:24 UTCEG score recompute
  6. 2026-08-05 10:24 UTCVendor advisory
  7. 2026-08-05 10:24 UTCGHSA enrichment
  8. 2026-08-04 12:10 UTCEG score recompute
  9. 2026-08-04 12:10 UTCVendor advisory
  10. 2026-08-04 12:10 UTCGHSA enrichment
  11. 2026-08-04 10:36 UTCEPSS rescore
  12. 2026-08-04 09:50 UTCEG score recompute
  13. 2026-08-04 09:50 UTCVendor advisory
  14. 2026-08-04 09:50 UTCGHSA enrichment
  15. 2026-08-03 10:34 UTCEPSS rescore
  16. 2026-08-01 04:14 UTCEPSS rescore
  17. 2026-08-01 02:12 UTCOSV refresh
  18. 2026-07-30 16:26 UTCEPSS rescore
  19. 2026-07-30 01:29 UTCEPSS rescore
  20. 2026-07-28 15:34 UTCEPSS rescore
  21. 2026-07-28 15:34 UTCEPSS rescore
  22. 2026-07-26 14:53 UTCEPSS rescore
  23. 2026-07-25 14:16 UTCEPSS rescore
  24. 2026-07-24 14:16 UTCEPSS rescore
  25. 2026-07-23 14:16 UTCEPSS rescore
Show 75 more
  1. 2026-07-23 02:29 UTCEG score recompute
  2. 2026-07-22 23:16 UTCEG score recompute
  3. 2026-07-22 14:07 UTCEPSS rescore
  4. 2026-07-22 14:07 UTCEPSS rescore
  5. 2026-07-21 15:23 UTCEPSS rescore
  6. 2026-07-20 17:06 UTCEPSS rescore
  7. 2026-07-19 14:30 UTCEPSS rescore
  8. 2026-07-19 14:29 UTCEPSS rescore
  9. 2026-07-19 02:27 UTCEPSS rescore
  10. 2026-07-19 02:27 UTCEPSS rescore
  11. 2026-07-18 10:03 UTCEPSS rescore
  12. 2026-07-18 10:03 UTCEPSS rescore
  13. 2026-07-16 17:01 UTCEPSS rescore
  14. 2026-07-15 16:56 UTCEPSS rescore
  15. 2026-07-15 01:59 UTCEPSS rescore
  16. 2026-07-15 01:59 UTCEPSS rescore
  17. 2026-07-14 09:25 UTCOSV refresh
  18. 2026-07-13 22:28 UTCEPSS rescore
  19. 2026-07-13 22:28 UTCEPSS rescore
  20. 2026-07-13 06:11 UTCEPSS rescore
  21. 2026-07-12 05:45 UTCEPSS rescore
  22. 2026-07-12 05:45 UTCEPSS rescore
  23. 2026-07-11 08:26 UTCEPSS rescore
  24. 2026-07-09 19:08 UTCEPSS rescore
  25. 2026-07-08 15:13 UTCEPSS rescore
  26. 2026-07-07 13:45 UTCEPSS rescore
  27. 2026-07-07 13:44 UTCEPSS rescore
  28. 2026-07-06 16:26 UTCEPSS rescore
  29. 2026-07-06 16:26 UTCEPSS rescore
  30. 2026-07-06 02:22 UTCEPSS rescore
  31. 2026-07-06 02:22 UTCEPSS rescore
  32. 2026-07-05 02:29 UTCEPSS rescore
  33. 2026-07-04 06:29 UTCEPSS rescore
  34. 2026-07-01 15:05 UTCEPSS rescore
  35. 2026-06-30 23:21 UTCEPSS rescore
  36. 2026-06-30 23:21 UTCEPSS rescore
  37. 2026-06-29 14:05 UTCEPSS rescore
  38. 2026-06-28 14:06 UTCEPSS rescore
  39. 2026-06-28 14:06 UTCEPSS rescore
  40. 2026-06-28 04:55 UTCEPSS rescore
  41. 2026-06-27 03:07 UTCEPSS rescore
  42. 2026-06-26 10:07 UTCOSV refresh
  43. 2026-06-25 13:48 UTCEPSS rescore
  44. 2026-06-25 13:48 UTCEPSS rescore
  45. 2026-06-24 14:04 UTCEPSS rescore
  46. 2026-06-24 14:04 UTCEPSS rescore
  47. 2026-06-23 21:31 UTCEPSS rescore
  48. 2026-06-23 21:31 UTCEPSS rescore
  49. 2026-06-22 14:24 UTCEPSS rescore
  50. 2026-06-22 14:24 UTCEPSS rescore
  51. 2026-06-21 14:55 UTCEPSS rescore
  52. 2026-06-21 14:55 UTCEPSS rescore
  53. 2026-06-21 01:58 UTCEPSS rescore
  54. 2026-06-21 01:58 UTCEPSS rescore
  55. 2026-06-19 19:24 UTCEPSS rescore
  56. 2026-06-19 19:24 UTCEPSS rescore
  57. 2026-06-18 17:51 UTCEPSS rescore
  58. 2026-06-17 17:51 UTCEPSS rescore
  59. 2026-06-16 17:51 UTCEPSS rescore
  60. 2026-06-16 17:51 UTCEPSS rescore
  61. 2026-06-15 17:47 UTCEPSS rescore
  62. 2026-06-14 23:16 UTCEPSS rescore
  63. 2026-06-13 22:59 UTCEPSS rescore
  64. 2026-06-13 22:59 UTCEPSS rescore
  65. 2026-06-12 23:11 UTCEPSS rescore
  66. 2026-06-11 13:59 UTCEPSS rescore
  67. 2026-06-10 22:17 UTCEPSS rescore
  68. 2026-06-10 13:21 UTCEPSS rescore
  69. 2026-06-08 16:41 UTCOSV refresh
  70. 2026-06-08 14:16 UTCEPSS rescore
  71. 2026-06-08 14:16 UTCEPSS rescore
  72. 2026-06-07 15:24 UTCEPSS rescore
  73. 2026-06-07 15:24 UTCEPSS rescore
  74. 2026-06-06 13:46 UTCEPSS rescore
  75. 2026-06-06 13:46 UTCEPSS rescore

Frequently asked(5)

What is CVE-2023-52864?
CVE-2023-52864 is a high vulnerability published on May 21, 2024. 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…
When was CVE-2023-52864 disclosed?
CVE-2023-52864 was first published in the National Vulnerability Database on May 21, 2024, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2023-52864 actively exploited?
CVE-2023-52864 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 81.7% of all scored CVEs.
What is the CVSS score of CVE-2023-52864?
CVE-2023-52864 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2023-52864?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2023-52864, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2023-52864

Explore →

Is Your Infrastructure Affected by CVE-2023-52864?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.