Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2023-54013: interconnect: Fix locking for runpm vs reclaim

Noroxi assessment

Priority: Monitor (action score 0/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.19% (FIRST EPSS).
  • Fixed version: Linux Linux 2f3a124696d43de3c837f87a9f767c56ee86cf2a, af42269c3523492d71ebbe11fefae2653e9cdc78, ffb8917c70a4c88725ee40f9eeee9240ad1c1869.

Low priority for now. Upgrade to Linux Linux 2f3a124696d43de3c837f87a9f767c56ee86cf2a, af42269c3523492d71ebbe11fefae2653e9cdc78, ffb8917c70a4c88725ee40f9eeee9240ad1c1869 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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---

—No exploit Fix available
Published
Dec 24, 2025
Updated
Oct 30, 2026
EPSS
0.1% · 9th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2023-54013

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 5.1affected
    • 11f1ceca7031deefc1a34236ab7b94360016b71d and later · before ffb8917c70a4c88725ee40f9eeee9240ad1c1869affected · git
    • 11f1ceca7031deefc1a34236ab7b94360016b71d and later · before 2f3a124696d43de3c837f87a9f767c56ee86cf2aaffected · git
    • 11f1ceca7031deefc1a34236ab7b94360016b71d and later · before af42269c3523492d71ebbe11fefae2653e9cdc78affected · git
    • before 5.1not affected · semver
    • 6.1.191 and later · up to and including 6.1.*not affected · semver
    • 6.5.5 and later · up to and including 6.5.*not affected · semver
    • 6.6 and laternot affected · original_commit_for_fix

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxfrom 0—
Debian:13linuxbefore 6.5.6-16.5.6-1
SUSE:Linux Enterprise Live Patching 15 SP7kernel-livepatch-SLE15-SP7_Update_9before 1-150700.15.3.11-150700.15.3.1
SUSE:Linux Enterprise Live Patching 15 SP7kernel-livepatch-SLE15-SP7-RT_Update_9before 1-150700.1.3.21-150700.1.3.2
SUSE:Linux Enterprise Module for Basesystem 15 SP7kernel-64kbbefore 6.4.0-150700.53.31.16.4.0-150700.53.31.1
SUSE:Linux Enterprise Module for Basesystem 15 SP7kernel-defaultbefore 6.4.0-150700.53.31.16.4.0-150700.53.31.1
SUSE:Linux Enterprise Module for Basesystem 15 SP7kernel-default-basebefore 6.4.0-150700.53.31.1.150700.17.21.16.4.0-150700.53.31.1.150700.17.21.1
SUSE:Linux Enterprise Module for Basesystem 15 SP7kernel-sourcebefore 6.4.0-150700.53.31.16.4.0-150700.53.31.1
SUSE:Linux Enterprise Module for Basesystem 15 SP7kernel-zfcpdumpbefore 6.4.0-150700.53.31.16.4.0-150700.53.31.1
SUSE:Linux Enterprise Module for Development Tools 15 SP7kernel-docsbefore 6.4.0-150700.53.31.16.4.0-150700.53.31.1
SUSE:Linux Enterprise Module for Development Tools 15 SP7kernel-obs-buildbefore 6.4.0-150700.53.31.16.4.0-150700.53.31.1
SUSE:Linux Enterprise Module for Development Tools 15 SP7kernel-symsbefore 6.4.0-150700.53.31.16.4.0-150700.53.31.1
SUSE:Linux Enterprise Module for Public Cloud 15 SP7kernel-azurebefore 6.4.0-150700.20.27.16.4.0-150700.20.27.1
SUSE:Linux Enterprise Module for Public Cloud 15 SP7kernel-source-azurebefore 6.4.0-150700.20.27.16.4.0-150700.20.27.1
SUSE:Linux Enterprise Module for Public Cloud 15 SP7kernel-syms-azurebefore 6.4.0-150700.20.27.16.4.0-150700.20.27.1
SUSE:Real Time Module 15 SP7kernel-rtbefore 6.4.0-150700.7.31.26.4.0-150700.7.31.2
SUSE:Real Time Module 15 SP7kernel-source-rtbefore 6.4.0-150700.7.31.16.4.0-150700.7.31.1
SUSE:Real Time Module 15 SP7kernel-syms-rtbefore 6.4.0-150700.7.31.16.4.0-150700.7.31.1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2023-54004Dec 24, 2025 · udplite: Fix NULL pointer dereference in __sk_mem_raise_allocated().
    30Monitor
  • ← EarlierCVE-2023-54012Dec 24, 2025 · net: fix stack overflow when LRO is disabled for virtual interfaces
    31Monitor
  • Later →CVE-2023-54019Dec 24, 2025 · sched/psi: use kernfs polling functions for PSI trigger polling
    31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux2f3a124696d43de3c837f87a9f767c56ee86cf2aVendor (CNA)
Linux Linuxaf42269c3523492d71ebbe11fefae2653e9cdc78Vendor (CNA)
Linux Linuxffb8917c70a4c88725ee40f9eeee9240ad1c1869Vendor (CNA)
debian:linux6.5.6-1 · Debian:13Package registry (OSV)
suse:kernel-64kb6.4.0-150700.53.31.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP7Package registry (OSV)
suse:kernel-azure6.4.0-150700.20.27.1 · SUSE:Linux Enterprise Module for Public Cloud 15 SP7Package registry (OSV)
suse:kernel-default6.4.0-150700.53.31.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP7Package registry (OSV)
suse:kernel-default-base6.4.0-150700.53.31.1.150700.17.21.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP7Package registry (OSV)
suse:kernel-docs6.4.0-150700.53.31.1 · SUSE:Linux Enterprise Module for Development Tools 15 SP7Package registry (OSV)
suse:kernel-livepatch-SLE15-SP7_Update_91-150700.15.3.1 · SUSE:Linux Enterprise Live Patching 15 SP7Package registry (OSV)
suse:kernel-obs-build6.4.0-150700.53.31.1 · SUSE:Linux Enterprise Module for Development Tools 15 SP7Package registry (OSV)
suse:kernel-source6.4.0-150700.53.31.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP7Package registry (OSV)
suse:kernel-source-azure6.4.0-150700.20.27.1 · SUSE:Linux Enterprise Module for Public Cloud 15 SP7Package registry (OSV)
suse:kernel-syms6.4.0-150700.53.31.1 · SUSE:Linux Enterprise Module for Development Tools 15 SP7Package registry (OSV)
suse:kernel-syms-azure6.4.0-150700.20.27.1 · SUSE:Linux Enterprise Module for Public Cloud 15 SP7Package registry (OSV)
suse:kernel-zfcpdump6.4.0-150700.53.31.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP7Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (2 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records