CVE-2023-52498

PM: sleep: Fix possible deadlocks in core system-wide PM code

MEDIUM
5.5
CVSS Score
Published: February 29, 2024 at 03:52 PM UTC
Updated: June 17, 2026 at 06:42 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.5
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: PM: sleep: Fix possible deadlocks in core system-wide PM code It is reported that in low-memory situations the system-wide resume core code deadlocks, because async_schedule_dev() executes its argument function synchronously if it cannot allocate memory (and not only in that case) and that function attempts to acquire a mutex that is already held. Executing the argument function synchronously from within dpm_async_fn() may also be problematic for ordering reasons (it may cause a consumer device's resume callback to be invoked before a requisite supplier device's one, for example). Address this by changing the code in question to use async_schedule_dev_nocall() for scheduling the asynchronous execution of device suspend and resume functions and to directly run them synchronously if async_schedule_dev_nocall() returns false.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v ≥ 4.14.171v ≥ 4.19.103v ≥ 5.4.19v ≥ 5.5.3v < 5.10.2104.14.171 ≤ v < 4.154.19.103 ≤ v < 4.205.11 ≤ v < 5.15.1495.16 ≤ v < 6.1.765.4.19 ≤ v < 5.55.5.3 ≤ v < 5.65.6 ≤ v < 5.10.2105.6 ≤ v < 5.15.1495.6 ≤ v < 6.1.765.6 ≤ v < 6.6.155.6 ≤ v < 6.7.35.6 ≤ v < 6.86.2 ≤ v < 6.6.156.7 ≤ v < 6.7.3390e974020ebbbb64580fc205ecc892d1fdd4624.14.1714.19.1035.4.195.5.35.6552e5fdfea191a2cf3a0abd33574b5ef9ca8185d56260c5e9fdbbba59655f63622f6159bf0e59576d587bd579a08ddcd51274c6d9fff4e885e184d7dce99d3182a1495bd14cac8403ee471ecdb7ea4
Vendor states this is fixed in 7839d0078e0d5e6cc2fa0b0dfbee71de74f1e557 (fixed)
Vendor states this is fixed in 9bd3dce27b01c51295b60e1433e1dadfb16649f7 (fixed)
Vendor states this is fixed in a1d62c775b07213c73f81ae842424c74dd14b5f0 (fixed)
Vendor states this is fixed in e1c9d32c98309ae764893a481552d3f99d46cb34 (fixed)
Vendor states this is fixed in e681e29d1f59a04ef773296e4bebb17b1b79f8fe (fixed)
Vendor states this is fixed in f46eb832389f162ad13cb780d0b8cde93641990d (fixed)
Affected range stops below 4.15, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.20, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 5.10.210 (unaffected)
Vendor states this is fixed in 5.15.149 (unaffected)
Affected range stops below 5.5, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 5.6 (unaffected)
Vendor states this is fixed in 6.1.76 (unaffected)
Vendor states this is fixed in 6.6.15 (unaffected)
Vendor states this is fixed in 6.7.3 (unaffected)
Vendor states this is fixed in 6.8 (unaffected)

References (7)

Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/7839d0078e0d5e6cc2fa0b0dfbee71de74f1e557
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/9bd3dce27b01c51295b60e1433e1dadfb16649f7
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/a1d62c775b07213c73f81ae842424c74dd14b5f0
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/e1c9d32c98309ae764893a481552d3f99d46cb34
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/e681e29d1f59a04ef773296e4bebb17b1b79f8fe
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/f46eb832389f162ad13cb780d0b8cde93641990d
Mailing ListPatch
Source: af854a3a-2127-422b-91ae-364da2661108
https://lists.debian.org/debian-lts-announce/2024/06/msg00017.html

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusANALYZED
CWE
CWE-667

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card