CVE-2023-52866

HIGHNVD 7.17.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

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

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this week

Also known asEUVD-2023-59579 (ENISA EUVD) · GHSA-qp48-7h94-95cp (GitHub Security Advisories)Source: ENISA EUVD

7.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

HID: uclogic: Fix user-memory-access bug in uclogic_params_ugee_v2_init_event_hooks()

When CONFIG_HID_UCLOGIC=y and CONFIG_KUNIT_ALL_TESTS=y, launch kernel and then the below user-memory-access bug occurs.

In hid_test_uclogic_params_cleanup_event_hooks(),it call uclogic_params_ugee_v2_init_event_hooks() with the first arg=NULL, so when it calls uclogic_params_ugee_v2_has_battery(), the hid_get_drvdata() will access hdev->dev with hdev=NULL, which will cause below user-memory-access.

So add a fake_device with quirks member and call hid_set_drvdata() to assign hdev->dev->driver_data which avoids the null-ptr-def bug for drvdata->quirks in uclogic_params_ugee_v2_has_battery(). After applying this patch, the below user-memory-access bug never occurs.

general protection fault, probably for non-canonical address 0xdffffc0000000329: 0000 [#1] PREEMPT SMP KASAN KASAN: probably user-memory-access in range [0x0000000000001948-0x000000000000194f] CPU: 5 PID: 2189 Comm: kunit_try_catch Tainted: G B W N 6.6.0-rc2+ #30 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/01/2014 RIP: 0010:uclogic_params_ugee_v2_init_event_hooks+0x87/0x600 Code: f3 f3 65 48 8b 14 25 28 00 00 00 48 89 54 24 60 31 d2 48 89 fa c7 44 24 30 00 00 00 00 48 c7 44 24 28 02 f8 02 01 48 c1 ea 03 <80> 3c 02 00 0f 85 2c 04 00 00 48 8b 9d 48 19 00 00 48 b8 00 00 00 RSP: 0000:ffff88810679fc88 EFLAGS: 00010202 RAX: dffffc0000000000 RBX: 0000000000000004 RCX: 0000000000000000 RDX: 0000000000000329 RSI: ffff88810679fd88 RDI: 0000000000001948 RBP: 0000000000000000 R08: 0000000000000000 R09: ffffed1020f639f0 R10: ffff888107b1cf87 R11: 0000000000000400 R12: 1ffff11020cf3f92 R13: ffff88810679fd88 R14: ffff888100b97b08 R15: ffff8881030bb080 FS: 0000000000000000(0000) GS:ffff888119e80000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000000000 CR3: 0000000005286001 CR4: 0000000000770ee0 DR0: ffffffff8fdd6cf4 DR1: ffffffff8fdd6cf5 DR2: ffffffff8fdd6cf6 DR3: ffffffff8fdd6cf7 DR6: 00000000fffe0ff0 DR7: 0000000000000600 PKRU: 55555554 Call Trace: ? die_addr+0x3d/0xa0 ? exc_general_protection+0x144/0x220 ? asm_exc_general_protection+0x22/0x30 ? uclogic_params_ugee_v2_init_event_hooks+0x87/0x600 ? sched_clock_cpu+0x69/0x550 ? uclogic_parse_ugee_v2_desc_gen_params+0x70/0x70 ? load_balance+0x2950/0x2950 ? rcu_trc_cmpxchg_need_qs+0x67/0xa0 hid_test_uclogic_params_cleanup_event_hooks+0x9e/0x1a0 ? uclogic_params_ugee_v2_init_event_hooks+0x600/0x600 ? __switch_to+0x5cf/0xe60 ? migrate_enable+0x260/0x260 ? __kthread_parkme+0x83/0x150 ? kunit_try_run_case_cleanup+0xe0/0xe0 kunit_generic_run_threadfn_adapter+0x4a/0x90 ? kunit_try_catch_throw+0x80/0x80 kthread+0x2b5/0x380 ? kthread_complete_and_exit+0x20/0x20 ret_from_fork+0x2d/0x70 ? kthread_complete_and_exit+0x20/0x20 ret_from_fork_asm+0x11/0x20 Modules linked in: Dumping ftrace buffer: (ftrace buffer empty) ---[ end trace 0000000000000000 ]--- RIP: 0010:uclogic_params_ugee_v2_init_event_hooks+0x87/0x600 Code: f3 f3 65 48 8b 14 25 28 00 00 00 48 89 54 24 60 31 d2 48 89 fa c7 44 24 30 00 00 00 00 48 c7 44 24 28 02 f8 02 01 48 c1 ea 03 <80> 3c 02 00 0f 85 2c 04 00 00 48 8b 9d 48 19 00 00 48 b8 00 00 00 RSP: 0000:ffff88810679fc88 EFLAGS: 00010202 RAX: dffffc0000000000 RBX: 0000000000000004 RCX: 0000000000000000 RDX: 0000000000000329 RSI: ffff88810679fd88 RDI: 0000000000001948 RBP: 0000000000000000 R08: 0000000000000000 R09: ffffed1020f639f0 R10: ffff888107b1cf87 R11: 0000000000000400 R12: 1ffff11020cf3f92 R13: ffff88810679fd88 R14: ffff888100b97b08 R15: ffff8881030bb080 FS: 0000000000000000(0000) GS:ffff888119e80000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000000000 CR3: 0000000005286001 CR4: 0000000000770ee0 DR0: ffffffff8fdd6cf4 DR1: ---truncated---

CVSS v3
7.1
EG Score
7.1HIGHmedium confidence
EG Risk
32
EG Risk 32/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity71% × 45%
Impact severity (EG Severity): CVSS 7.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
13th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.1): severity, escalated by confirmed exploitation. This CVE's 7.1 is its impact severity (EG Severity), not escalated.

EG Severity
7.1 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-27). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

May 21, 2024

Last Modified

September 24, 2025

References (3)

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
linuxKernel @ 6.5.12 (fixes >=6.3.0)—osv

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.

Affected Packages

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.6.8-1: fixed in 6.6.8-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.6.8-1: fixed in 6.6.8-1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 38× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 93 of 196 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 7 repeat rows among the latest 100 are merged into the row they repeat. The 103 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-01 16:31 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  2. 2026-10-31 16:30 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  3. 2026-10-30 16:31 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  4. 2026-10-29 16:30 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  5. 2026-10-28 16:29 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  6. 2026-10-27 19:44 UTCEG score recompute
  7. 2026-10-27 19:44 UTCGHSA enrichmentGHSA-qp48-7h94-95cp · GitHub severity HIGH · GitHub CVSS 7.1
  8. 2026-10-27 16:29 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  9. 2026-10-26 16:29 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  10. 2026-10-25 17:28 UTCEG score recompute
  11. 2026-10-25 16:30 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  12. 2026-10-24 16:29 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  13. 2026-10-23 16:29 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  14. 2026-10-22 16:31 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  15. 2026-10-21 16:29 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  16. 2026-10-20 21:18 UTCEG score recompute
  17. 2026-10-20 21:18 UTCGHSA enrichmentGHSA-qp48-7h94-95cp · GitHub severity HIGH · GitHub CVSS 7.1
  18. 2026-10-20 16:30 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  19. 2026-10-19 16:29 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  20. 2026-10-18 07:42 UTCEG score recompute
  21. 2026-10-17 16:30 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  22. 2026-10-16 16:36 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  23. 2026-10-15 16:29 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  24. 2026-10-14 16:30 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  25. 2026-10-13 16:30 UTCEPSS rescoreEPSS 0.2% · 12th percentile
Show 68 more
  1. 2026-10-12 18:13 UTCEG score recompute
  2. 2026-10-12 16:31 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  3. 2026-10-11 21:38 UTCEG score recompute
  4. 2026-10-11 13:45 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  5. 2026-10-10 23:17 UTCOSV refresh
  6. 2026-10-10 19:58 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  7. 2026-10-09 20:05 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  8. 2026-10-08 17:06 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  9. 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  10. 2026-10-06 15:15 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  11. 2026-10-05 17:41 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  12. 2026-10-04 23:20 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  13. 2026-10-03 14:23 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  14. 2026-10-01 19:48 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  15. 2026-09-30 16:37 UTCEG score recompute
  16. 2026-09-30 15:01 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  17. 2026-09-29 15:17 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  18. 2026-09-28 13:49 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  19. 2026-09-26 00:22 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  20. 2026-09-24 14:01 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  21. 2026-09-23 13:46 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  22. 2026-09-21 11:19 UTCOSV refresh
  23. 2026-09-20 20:14 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  24. 2026-09-18 19:26 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  25. 2026-09-16 14:06 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  26. 2026-09-16 05:11 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  27. 2026-09-15 03:08 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  28. 2026-09-13 16:45 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  29. 2026-09-12 14:58 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  30. 2026-09-11 14:51 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  31. 2026-09-11 09:34 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  32. 2026-09-08 21:58 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  33. 2026-09-07 15:59 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  34. 2026-09-06 13:46 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  35. 2026-09-05 15:26 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  36. 2026-09-04 13:58 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  37. 2026-09-04 05:04 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  38. 2026-09-02 14:10 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  39. 2026-09-02 09:14 UTCOSV refresh
  40. 2026-09-01 13:52 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  41. 2026-09-01 04:36 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  42. 2026-08-30 19:15 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  43. 2026-08-28 21:39 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  44. 2026-08-27 14:23 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  45. 2026-08-26 14:44 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  46. 2026-08-25 13:47 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  47. 2026-08-20 22:53 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  48. 2026-08-19 17:02 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  49. 2026-08-18 13:46 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  50. 2026-08-16 14:54 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  51. 2026-08-16 08:17 UTCOSV refresh
  52. 2026-08-16 02:12 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  53. 2026-08-15 01:28 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  54. 2026-08-12 13:49 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  55. 2026-08-11 13:40 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  56. 2026-08-10 23:58 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  57. 2026-08-09 13:44 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  58. 2026-08-08 16:35 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  59. 2026-08-07 16:25 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  60. 2026-08-06 13:45 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  61. 2026-08-05 19:15 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  62. 2026-08-04 10:36 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  63. 2026-08-03 10:34 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  64. 2026-08-02 02:25 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  65. 2026-08-01 04:14 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  66. 2026-08-01 02:12 UTCOSV refresh
  67. 2026-07-30 16:26 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  68. 2026-07-30 01:29 UTCEPSS rescoreEPSS 0.2% · 13th percentile

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2023-52866?
CVE-2023-52866 is a high-severity vulnerability; its CVE record was published on May 21, 2024. In the Linux kernel, the following vulnerability has been resolved: HID: uclogic: Fix user-memory-access bug in uclogic_params_ugee_v2_init_event_hooks() When CONFIG_HID_UCLOGIC=y and CONFIG_KUNIT_ALL_TESTS=y, launch kernel and then the below user-memory-access bug occurs. In…
When was the CVE record for CVE-2023-52866 published?
The CVE record for CVE-2023-52866 was published on May 21, 2024. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 24, 2025; the record at its source may have been updated since.
Is CVE-2023-52866 actively exploited?
CVE-2023-52866 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (13th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-52866?
CVE-2023-52866 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2023-52866?
A fix for CVE-2023-52866 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2023-52866

Explore →

Is Your Infrastructure Affected by CVE-2023-52866?

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

Book a Demo →Browse All CVEs