LiveActive security incident?Get immediate response
CVE Record

CVE-2023-53656: drivers/perf: hisi: Don't migrate perf to the CPU going to teardown

In the Linux kernel, the following vulnerability has been resolved: drivers/perf: hisi: Don't migrate perf to the CPU going to teardown The driver needs to migrate the perf context if the current using CPU going to teardown. By the time calling the cpuhp::teardown() callback the cpu_online_mask() hasn't updated yet and still includes the CPU going to teardown. In current driver's implementation we may migrate the context to the teardown CPU and leads to the below calltrace: ... [ 368.104662][ T932] task:cpuhp/0 state:D stack: 0 pid: 15 ppid: 2 flags:0x00000008 [ 368.113699][ T932] Call trace: [ 368.116834][ T932] __switch_to+0x7c/0xbc [ 368.120924][ T932] __schedule+0x338/0x6f0 [ 368.125098][ T932] schedule+0x50/0xe0 [ 368.128926][ T932] schedule_preempt_disabled+0x18/0x24 [ 368.134229][ T932] __mutex_lock.constprop.0+0x1d4/0x5dc [ 368.139617][ T932] __mutex_lock_slowpath+0x1c/0x30 [ 368.144573][ T932] mutex_lock+0x50/0x60 [ 368.148579][ T932] perf_pmu_migrate_context+0x84/0x2b0 [ 368.153884][ T932] hisi_pcie_pmu_offline_cpu+0x90/0xe0 [hisi_pcie_pmu] [ 368.160579][ T932] cpuhp_invoke_callback+0x2a0/0x650 [ 368.165707][ T932] cpuhp_thread_fun+0xe4/0x190 [ 368.170316][ T932] smpboot_thread_fn+0x15c/0x1a0 [ 368.175099][ T932] kthread+0x108/0x13c [ 368.179012][ T932] ret_from_fork+0x10/0x18 ... Use function cpumask_any_but() to find one correct active cpu to fixes this issue.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel reliability flaw in the HiSilicon PCIe PMU performance-monitoring driver. During CPU shutdown, the driver can move performance state back onto the CPU being removed, causing a blocked kernel CPU hotplug thread. The documented impact is system availability, not data theft or privilege escalation.

Executive priority

Treat this as a targeted kernel availability issue. It is not currently evidenced as internet-exploited, but affected production systems using HiSilicon PMU hardware should receive normal kernel patching priority, with higher urgency for environments that offline CPUs or rely on uptime during hardware maintenance.

Technical view

The hisi_pcie_pmu CPU teardown callback uses the online CPU mask before it reflects the CPU being removed. That can select the teardown CPU as the migration target for perf context and block in perf_pmu_migrate_context. The fix uses cpumask_any_but() to select a different active CPU.

Likely exposure

Likely limited to Linux systems using the affected HiSilicon PCIe PMU perf driver, especially where CPU hotplug, CPU offlining, suspend, maintenance, or topology changes occur. The bundle lists Linux versions and stable commit references but does not identify distributions or hardware SKUs.

Exploitation context

The source bundle does not report active exploitation, and KEV is false. No remote attack path is described. The evidence points to a local or operational availability issue triggered around CPU teardown behavior on affected kernel and driver combinations.

Researcher notes

The CVE record provides no CVSS, CWE, proof of exploitation, or distro-specific affected matrix. Analysis should stay tied to the hisi_pcie_pmu teardown migration bug and stable kernel patches. Avoid broad Linux exposure claims without confirming hardware, driver presence, and backported fixes.

Mitigation direction

  • Apply kernel or distribution updates containing the referenced stable fixes.
  • Check vendor or distribution guidance for affected package versions and backports.
  • Prioritize systems with HiSilicon PCIe PMU hardware and CPU hotplug usage.
  • Avoid unsupported kernel workarounds unless vendor guidance recommends them.
  • Track this as availability risk where CPU offlining is operationally common.

Validation and detection

  • Inventory Linux kernel versions against vendor advisories and linked stable commits.
  • Confirm whether the HiSilicon PCIe PMU driver is present or loaded.
  • Review kernel logs for hisi_pcie_pmu_offline_cpu and perf_pmu_migrate_context call traces.
  • Verify patched systems include the cpumask_any_but() migration fix.
  • Document any CPU hotplug, suspend, or maintenance workflows on exposed systems.
Prepared
Confidence
medium
Sources
6

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-53656 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
5Source 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
LinuxLinux8404b0fbc7fbd42e5c5d28cdedd450e70829c77a, 8404b0fbc7fbd42e5c5d28cdedd450e70829c77a, 8404b0fbc7fbd42e5c5d28cdedd450e70829c77a, 8404b0fbc7fbd42e5c5d28cdedd450e70829c77aunaffected
LinuxLinux5.17, 0, 6.1.39, 6.3.13, 6.4.4, 6.5affected
Weakness

CWE details

No CWE listed

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