CVE-2023-54013

/// Technical description

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 exist

/// Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

/// References