LiveActive security incident?Get immediate response
CVE Record

CVE-2023-53712: ARM: 9317/1: kexec: Make smp stop calls asynchronous

In the Linux kernel, the following vulnerability has been resolved: ARM: 9317/1: kexec: Make smp stop calls asynchronous If a panic is triggered by a hrtimer interrupt all online cpus will be notified and set offline. But as highlighted by commit 19dbdcb8039c ("smp: Warn on function calls from softirq context") this call should not be made synchronous with disabled interrupts: softdog: Initiating panic Kernel panic - not syncing: Software Watchdog Timer expired WARNING: CPU: 1 PID: 0 at kernel/smp.c:753 smp_call_function_many_cond unwind_backtrace: show_stack dump_stack_lvl __warn warn_slowpath_fmt smp_call_function_many_cond smp_call_function crash_smp_send_stop.part.0 machine_crash_shutdown __crash_kexec panic softdog_fire __hrtimer_run_queues hrtimer_interrupt Make the smp call for machine_crash_nonpanic_core() asynchronous.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

This CVE is a Linux kernel ARM crash-handling issue. During some panic paths, such as a watchdog timer firing from a high-resolution timer interrupt, the kernel could make a synchronous stop call in an unsafe context. The sources frame this as a reliability fix, not a remote compromise issue.

Executive priority

Handle through normal kernel maintenance unless ARM crash recovery is business-critical. There is no source-backed evidence of active exploitation or remote compromise, but affected systems should still receive routine vendor kernel updates.

Technical view

The fix changes ARM kexec crash shutdown so the SMP call for machine_crash_nonpanic_core() is asynchronous. The reported stack shows panic handling via softdog_fire and hrtimer_interrupt reaching crash_smp_send_stop and smp_call_function, where synchronous calls with disabled interrupts were warned against.

Likely exposure

Most relevant to ARM Linux systems using affected kernel ranges and kexec or crash-dump handling. Exposure is narrower than a normal network-facing kernel flaw because the described condition occurs during kernel panic handling.

Exploitation context

No active exploitation is cited, and CISA KEV status is false in the provided bundle. The sources do not describe attacker prerequisites, remote reachability, privilege requirements, or a weaponized exploit path.

Researcher notes

The public record lacks CVSS, CWE, exploitability detail, and downstream vendor mapping. Analysis should stay focused on ARM kexec panic handling and the referenced stable commits rather than broad Linux kernel exposure claims.

Mitigation direction

  • Apply vendor or distribution kernel updates containing the referenced stable fixes.
  • Prioritize ARM systems where kexec or crash dumps are operationally important.
  • Check vendor advisories before assuming exact affected downstream versions.
  • Retest crash-dump behavior after updating affected kernels.

Validation and detection

  • Inventory ARM Linux kernels and compare them with vendor fixed versions.
  • Confirm whether referenced stable commits are present in deployed kernel packages.
  • Review whether kexec or crash-dump paths are enabled on affected systems.
  • Validate panic crash collection in a controlled non-production test.
Prepared
Confidence
medium
Sources
6

Public sources used

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-53712 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.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxb23065313297e750edd57ab6edfd36224826724e, b23065313297e750edd57ab6edfd36224826724e, b23065313297e750edd57ab6edfd36224826724e, b23065313297e750edd57ab6edfd36224826724eunaffected
LinuxLinux2.6.38, 0, 5.15.133, 6.1.55, 6.5.5, 6.6affected
Weakness

CWE details

No CWE listed

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