CVE-2023-54013

UNRATEDCVSS · not yet scored
—
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS v2: —Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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%
EPSS %ILE
7%
KEV
Not listed

Published

December 24, 2025

Last Modified

April 15, 2026

References (2)

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 6.5.5—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.

Data Freshness Timeline

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

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

Related CVEs(same product)

Frequently asked(4)

What is CVE-2023-54013?
CVE-2023-54013 is a publicly disclosed vulnerability 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 iccbwset() 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 iccbwlock…
When was CVE-2023-54013 disclosed?
CVE-2023-54013 was first published in the National Vulnerability Database on December 24, 2025, with the most recent update on April 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2023-54013 actively exploited?
CVE-2023-54013 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 93.4% of all scored CVEs.
How do I remediate CVE-2023-54013?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2023-54013, 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-54013

Explore →

Is Your Infrastructure Affected by CVE-2023-54013?

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

Start Free Scan →Browse All CVEs