LiveActive security incident?Get immediate response
CVE Record

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

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue can make affected systems deadlock during system-wide resume, especially under low-memory conditions. The practical business impact is availability: a server, workstation, or embedded Linux device may hang when leaving sleep or suspend. The sources do not report data theft, privilege escalation, or active exploitation.

Executive priority

Treat as a reliability patch, not an emergency breach response. Patch during the next kernel maintenance window, faster for laptops, appliances, or infrastructure where suspend/resume failure disrupts service availability.

Technical view

The bug is in Linux core power-management sleep code. async_schedule_dev() could execute a suspend or resume callback synchronously when allocation failed, causing mutex re-entry while already held and possible ordering violations between supplier and consumer devices. Stable kernel commits switch scheduling to async_schedule_dev_nocall() and explicitly run synchronously only when scheduling is unavailable.

Likely exposure

Exposure is limited to Linux systems running kernel builds with the affected PM sleep code. Highest practical concern is devices that use suspend/resume paths, run under memory pressure, or depend on reliable power-state transitions. The provided affected-version data is incomplete for exact range interpretation, so confirm against distro kernel advisories.

Exploitation context

The source bundle marks KEV as false and provides no cited evidence of active exploitation. The described condition involves low-memory suspend/resume behavior, pointing to denial of service or system hang rather than remote compromise. No public source in the bundle describes exploit tooling or attacker use.

Researcher notes

Key evidence is the kernel fix description and stable commit references. The CVE record does not provide CVSS, CWE, exploit status, or precise distro package mapping. Range semantics in the bundled affected-version list are not fully represented, so researchers should verify exact exposure through upstream and distribution metadata.

Mitigation direction

  • Update to a vendor or distribution kernel containing the referenced stable fixes.
  • Prioritize systems that suspend, hibernate, or resume under operational workloads.
  • Check Debian LTS and other distro advisories for packaged fixed kernel versions.
  • Avoid direct kernel changes unless validated through normal maintenance channels.
  • Monitor affected systems for resume hangs until patched.

Validation and detection

  • Inventory Linux kernel versions across servers, endpoints, and embedded devices.
  • Compare running kernels with vendor advisories for CVE-2023-52498.
  • Review suspend/resume incident logs for low-memory deadlocks or hangs.
  • Confirm patched kernels include the referenced PM sleep stable commits.
  • Run regression tests for suspend and resume on representative hardware.
Prepared
Confidence
medium
Sources
9

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2023-52498 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
8Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux0552e05fdfea191a2cf3a0abd33574b5ef9ca818, 0552e05fdfea191a2cf3a0abd33574b5ef9ca818, 0552e05fdfea191a2cf3a0abd33574b5ef9ca818, 0552e05fdfea191a2cf3a0abd33574b5ef9ca818, 0552e05fdfea191a2cf3a0abd33574b5ef9ca818, 0552e05fdfea191a2cf3a0abd33574b5ef9ca818, 5d56260c5e9fdbbba59655f63622f6159bf0e595, 76d587bd579a08ddcd51274c6d9fff4e885e184d, 7dce99d3182a1495bd14cac8403ee471ecdb7ea4, 0390e974020ebbbb64580fc205ecc892d1fdd462unaffected
LinuxLinux5.6, 0, 5.10.210, 5.15.149, 6.1.76, 6.6.15, 6.7.3, 6.8affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.