CVE-2023-54013

UNRATEDCVSS · not yet scored

Also known asEUVD-2025-205143 (ENISA EUVD) · GHSA-v99q-84v2-8gvx (GitHub Security Advisories)Source: ENISA EUVD

—
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS v2: —Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

interconnect: Fix locking for runpm vs reclaim

For cases where icc_bw_set() can be called in callbaths that could deadlock against shrinker/reclaim, such as runpm resume, we need to decouple the icc locking. Introduce a new icc_bw_lock for cases where we need to serialize bw aggregation and update to decouple that from paths that require memory allocation such as node/link creation/ destruction.

Fixes this lockdep splat:

====================================================== WARNING: possible circular locking dependency detected 6.2.0-rc8-debug+ #554 Not tainted ------------------------------------------------------ ring0/132 is trying to acquire lock: ffffff80871916d0 (&gmu->lock){+.+.}-{3:3}, at: a6xx_pm_resume+0xf0/0x234

but task is already holding lock: ffffffdb5aee57e8 (dma_fence_map){++++}-{0:0}, at: msm_job_run+0x68/0x150

which lock already depends on the new lock.

the existing dependency chain (in reverse order) is:

-> #4 (dma_fence_map){++++}-{0:0}: __dma_fence_might_wait+0x74/0xc0 dma_resv_lockdep+0x1f4/0x2f4 do_one_initcall+0x104/0x2bc kernel_init_freeable+0x344/0x34c kernel_init+0x30/0x134 ret_from_fork+0x10/0x20

-> #3 (mmu_notifier_invalidate_range_start){+.+.}-{0:0}: fs_reclaim_acquire+0x80/0xa8 slab_pre_alloc_hook.constprop.0+0x40/0x25c __kmem_cache_alloc_node+0x60/0x1cc __kmalloc+0xd8/0x100 topology_parse_cpu_capacity+0x8c/0x178 get_cpu_for_node+0x88/0xc4 parse_cluster+0x1b0/0x28c parse_cluster+0x8c/0x28c init_cpu_topology+0x168/0x188 smp_prepare_cpus+0x24/0xf8 kernel_init_freeable+0x18c/0x34c kernel_init+0x30/0x134 ret_from_fork+0x10/0x20

-> #2 (fs_reclaim){+.+.}-{0:0}: __fs_reclaim_acquire+0x3c/0x48 fs_reclaim_acquire+0x54/0xa8 slab_pre_alloc_hook.constprop.0+0x40/0x25c __kmem_cache_alloc_node+0x60/0x1cc __kmalloc+0xd8/0x100 kzalloc.constprop.0+0x14/0x20 icc_node_create_nolock+0x4c/0xc4 icc_node_create+0x38/0x58 qcom_icc_rpmh_probe+0x1b8/0x248 platform_probe+0x70/0xc4 really_probe+0x158/0x290 __driver_probe_device+0xc8/0xe0 driver_probe_device+0x44/0x100 __driver_attach+0xf8/0x108 bus_for_each_dev+0x78/0xc4 driver_attach+0x2c/0x38 bus_add_driver+0xd0/0x1d8 driver_register+0xbc/0xf8 __platform_driver_register+0x30/0x3c qnoc_driver_init+0x24/0x30 do_one_initcall+0x104/0x2bc kernel_init_freeable+0x344/0x34c kernel_init+0x30/0x134 ret_from_fork+0x10/0x20

-> #1 (icc_lock){+.+.}-{3:3}: __mutex_lock+0xcc/0x3c8 mutex_lock_nested+0x30/0x44 icc_set_bw+0x88/0x2b4 _set_opp_bw+0x8c/0xd8 _set_opp+0x19c/0x300 dev_pm_opp_set_opp+0x84/0x94 a6xx_gmu_resume+0x18c/0x804 a6xx_pm_resume+0xf8/0x234 adreno_runtime_resume+0x2c/0x38 pm_generic_runtime_resume+0x30/0x44 __rpm_callback+0x15c/0x174 rpm_callback+0x78/0x7c rpm_resume+0x318/0x524 __pm_runtime_resume+0x78/0xbc adreno_load_gpu+0xc4/0x17c msm_open+0x50/0x120 drm_file_alloc+0x17c/0x228 drm_open_helper+0x74/0x118 drm_open+0xa0/0x144 drm_stub_open+0xd4/0xe4 chrdev_open+0x1b8/0x1e4 do_dentry_open+0x2f8/0x38c vfs_open+0x34/0x40 path_openat+0x64c/0x7b4 do_filp_open+0x54/0xc4 do_sys_openat2+0x9c/0x100 do_sys_open+0x50/0x7c __arm64_sys_openat+0x28/0x34 invoke_syscall+0x8c/0x128 el0_svc_common.constprop.0+0xa0/0x11c do_el0_ ---truncated---

CVSS v3
—
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
—
EG Risk
—
EPSS PROB
0.2%
EPSS %ILE
10th
KEV
Not listed

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

EG Severity
Not assessed: no CVSS publishedA missing CVSS is not a severity of zero.
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS. 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
No SSVC decision: EchelonGraph has not assessed this CVECISA BOD 26-04: 14 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 BOD 26-04 block below.

BOD 26-04 (CISA's remediation timeline, Table 1)14 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's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” 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

December 24, 2025

Last Modified

October 30, 2026

References (3)

Vendor Advisories for CVE-2023-54013(1)

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

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
linuxKernel @ 6.5.5 (fixes >=5.1.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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (499 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (353 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.5.6-1: fixed in 6.5.6-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.5.6-1: fixed in 6.5.6-1
—

Data Freshness Timeline

(refreshed 7× in last 7d / 42× 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 94 of 228 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. 6 repeat rows among the latest 100 are merged into the row they repeat. The 134 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(4)

What is CVE-2023-54013?
CVE-2023-54013 is a vulnerability whose severity is not yet rated; its CVE record was published on December 24, 2025. In the Linux kernel, the following vulnerability has been resolved: interconnect: Fix locking for runpm vs reclaim For cases where icc_bw_set() can be called in callbaths that could deadlock against shrinker/reclaim, such as runpm resume, we need to decouple the icc locking. Introduce a new…
When was the CVE record for CVE-2023-54013 published?
The CVE record for CVE-2023-54013 was published on December 24, 2025. 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 October 30, 2026; the record at its source may have been updated since.
Is CVE-2023-54013 actively exploited?
CVE-2023-54013 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (10th percentile of EPSS-scored CVEs).
How do I remediate CVE-2023-54013?
A fix for CVE-2023-54013 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2023-54013 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2023-54013?

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

Book a Demo →Browse All CVEs