LiveActive security incident?Get immediate response
CVE Record

CVE-2023-53522: cgroup,freezer: hold cpu_hotplug_lock before freezer_mutex

In the Linux kernel, the following vulnerability has been resolved: cgroup,freezer: hold cpu_hotplug_lock before freezer_mutex syzbot is reporting circular locking dependency between cpu_hotplug_lock and freezer_mutex, for commit f5d39b020809 ("freezer,sched: Rewrite core freezer logic") replaced atomic_inc() in freezer_apply_state() with static_branch_inc() which holds cpu_hotplug_lock. cpu_hotplug_lock => cgroup_threadgroup_rwsem => freezer_mutex cgroup_file_write() { cgroup_procs_write() { __cgroup_procs_write() { cgroup_procs_write_start() { cgroup_attach_lock() { cpus_read_lock() { percpu_down_read(&cpu_hotplug_lock); } percpu_down_write(&cgroup_threadgroup_rwsem); } } cgroup_attach_task() { cgroup_migrate() { cgroup_migrate_execute() { freezer_attach() { mutex_lock(&freezer_mutex); (...snipped...) } } } } (...snipped...) } } } freezer_mutex => cpu_hotplug_lock cgroup_file_write() { freezer_write() { freezer_change_state() { mutex_lock(&freezer_mutex); freezer_apply_state() { static_branch_inc(&freezer_active) { static_key_slow_inc() { cpus_read_lock(); static_key_slow_inc_cpuslocked(); cpus_read_unlock(); } } } mutex_unlock(&freezer_mutex); } } } Swap locking order by moving cpus_read_lock() in freezer_apply_state() to before mutex_lock(&freezer_mutex) in freezer_change_state().

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue is a lock-ordering bug in the cgroup freezer path. Under the right kernel activity, two kernel locks can be taken in opposite order, creating a circular dependency. The sourced record does not provide CVSS, confirmed exploitability, or business impact beyond the kernel locking flaw.

Executive priority

Treat this as a kernel maintenance item unless vendor guidance raises severity. There is no sourced active exploitation, but kernel deadlock-class bugs can affect service availability and should not be ignored on shared or critical Linux infrastructure.

Technical view

The bug involves cpu_hotplug_lock, cgroup_threadgroup_rwsem, and freezer_mutex. freezer_apply_state() began using static_branch_inc(), which takes cpu_hotplug_lock while freezer_mutex is held. The fix changes freezer_change_state() so cpus_read_lock() is taken before freezer_mutex, matching the other cgroup path lock order.

Likely exposure

Exposure is limited to Linux kernels in the affected cgroup freezer code path. The bundle identifies Linux kernel versions including 6.1, 6.2.12, 6.1.25, and 6.3 context, but exact fleet impact requires vendor kernel mapping.

Exploitation context

No CISA KEV listing is reported, and the bundle provides no evidence of active exploitation or public weaponization. The issue was reported through syzbot as a circular locking dependency, not as a described real-world attack chain.

Researcher notes

The key research point is lock ordering: cpu_hotplug_lock can precede freezer_mutex through cgroup process writes, while freezer state changes previously held freezer_mutex before cpus_read_lock(). The source bundle does not include CVSS, CWE, exploit prerequisites, or full affected-version ranges.

Mitigation direction

  • Review vendor kernel advisories for CVE-2023-53522 applicability.
  • Prioritize kernel updates containing the referenced stable fixes.
  • Map running kernels to vendor package versions before assuming exposure.
  • For critical hosts, plan maintenance windows for kernel replacement and reboot.
  • Monitor kernel logs for lockdep or freezer/cgroup lock warnings.

Validation and detection

  • Inventory Linux kernel versions across production and container hosts.
  • Confirm whether deployed kernels include the referenced stable commits.
  • Check vendor changelogs for CVE-2023-53522 or freezer locking fixes.
  • Review dmesg or kernel logs for circular locking dependency reports.
  • Validate cgroup freezer usage in workloads and orchestration components.
Prepared
Confidence
medium
Sources
5

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-53522 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
3Timeline events
0ADP providers
4Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxf5d39b020809146cc28e6e73369bf8065e0310aa, f5d39b020809146cc28e6e73369bf8065e0310aa, f5d39b020809146cc28e6e73369bf8065e0310aaunaffected
LinuxLinux6.1, 0, 6.1.25, 6.2.12, 6.3affected
Weakness

CWE details

No CWE listed

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