CVE-2023-53039

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
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:

HID: intel-ish-hid: ipc: Fix potential use-after-free in work function

When a reset notify IPC message is received, the ISR schedules a work function and passes the ISHTP device to it via a global pointer ishtp_dev. If ish_probe() fails, the devm-managed device resources including ishtp_dev are freed, but the work is not cancelled, causing a use-after-free when the work function tries to access ishtp_dev. Use devm_work_autocancel() instead, so that the work is automatically cancelled if probe fails.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/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%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
10%
KEV
Not listed

Published

May 2, 2025

Last Modified

August 5, 2026

Advisory Details (4)

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

HID: intel-ish-hid: ipc: Fix potential use-after-free in work function - kernel/git/stable/linux.git - Linux kernel stable tree

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

HID: intel-ish-hid: ipc: Fix potential use-after-free in work function - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8c1d378b8c224fd50247625255f09fc01dcc5836
generic

HID: intel-ish-hid: ipc: Fix potential use-after-free in work function - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8ae2f2b0a28416ed2f6d8478ac8b9f7862f36785
generic

HID: intel-ish-hid: ipc: Fix potential use-after-free in work function - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0a594cb490ca6232671fc09e2dc1a0fc7ccbb0b5

Vendor Advisories for CVE-2023-53039(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatkernel-0:4.18.0-513.5.1.el8_92023-11-14redhat
redhatkernel-0:5.14.0-362.8.1.el9_32023-11-07redhat
linuxKernel @ 5.15.105—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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (498 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux—6.1.25-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux—6.1.25-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux—6.1.25-1—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 29× 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 153 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2023-53039?
CVE-2023-53039 is a high vulnerability published on May 2, 2025. In the Linux kernel, the following vulnerability has been resolved: HID: intel-ish-hid: ipc: Fix potential use-after-free in work function When a reset notify IPC message is received, the ISR schedules a work function and passes the ISHTP device to it via a global pointer ishtpdev. If ishprobe()…
When was CVE-2023-53039 disclosed?
CVE-2023-53039 was first published in the National Vulnerability Database on May 2, 2025, 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-53039 actively exploited?
CVE-2023-53039 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 90.1% of all scored CVEs.
What is the CVSS score of CVE-2023-53039?
CVE-2023-53039 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2023-53039?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2023-53039, 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

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

Explore →

Is Your Infrastructure Affected by CVE-2023-53039?

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

Start Free Scan →Browse All CVEs