Vulnerability · Published Sep 15, 2025 · Assigned by Linux

CVE-2023-53216arm64: efi: Make efi_rt_lock a raw_spinlock

High 7.8

In plain English

A high-severity security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 6% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS 3.1)7.8High
Exploit odds (30 days)0.2%top 93.9% of all CVEs
Exploited in the wildNo reportsCISA SSVC: none
Attack toolingNoneno public tooling known

Official description

In the Linux kernel, the following vulnerability has been resolved: arm64: efi: Make efi_rt_lock a raw_spinlock Running a rt-kernel base on 6.2.0-rc3-rt1 on an Ampere Altra outputs the following: BUG: sleeping function called from invalid context at kernel/locking/spinlock_rt.c:46 in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 9, name: kworker/u320:0 preempt_count: 2, expected: 0 RCU nest depth: 0, expected: 0 3 locks held by kworker/u320:0/9: #0: ffff3fff8c27d128 ((wq_completion)efi_rts_wq){+.+.}-{0:0}, at: process_one_work (./include/linux/atomic/atomic-long.h:41) #1: ffff80000861bdd0 ((work_completion)(&efi_rts_work.work)){+.+.}-{0:0}, at: process_one_work (./include/linux/atomic/atomic-long.h:41) #2: ffffdf7e1ed3e460 (efi_rt_lock){+.+.}-{3:3}, at: efi_call_rts (drivers/firmware/efi/runtime-wrappers.c:101) Preemption disabled at: efi_virtmap_load (./arch/arm64/include/asm/mmu_context.h:248) CPU: 0 PID: 9 Comm: kworker/u320:0 Tainted: G W 6.2.0-rc3-rt1 Hardware name: WIWYNN Mt.Jade Server System B81.03001.0005/Mt.Jade Motherboard, BIOS 1.08.20220218 (SCP: 1.08.20220218) 2022/02/18 Workqueue: efi_rts_wq efi_call_rts Call trace: dump_backtrace (arch/arm64/kernel/stacktrace.c:158) show_stack (arch/arm64/kernel/stacktrace.c:165) dump_stack_lvl (lib/dump_stack.c:107 (discriminator 4)) dump_stack (lib/dump_stack.c:114) __might_resched (kernel/sched/core.c:10134) rt_spin_lock (kernel/locking/rtmutex.c:1769 (discriminator 4)) efi_call_rts (drivers/firmware/efi/runtime-wrappers.c:101) [...] This seems to come from commit ff7a167961d1 ("arm64: efi: Execute runtime services from a dedicated stack") which adds a spinlock. This spinlock is taken through: efi_call_rts() \-efi_call_virt() \-efi_call_virt_pointer() \-arch_efi_call_virt_setup() Make 'efi_rt_lock' a raw_spinlock to avoid being preempted. [ardb: The EFI runtime services are called with a different set of translation tables, and are permitted to use the SIMD registers. The context switch code preserves/restores neither, and so EFI calls must be made with preemption disabled, rather than only disabling migration.]

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:12linux6.1.20-1DEBIAN-CVE-2023-53216
Debian:13linux6.1.20-1DEBIAN-CVE-2023-53216
Debian:14linux6.1.20-1DEBIAN-CVE-2023-53216
Ubuntu:22.04:LTSlinux5.15.0-79.86UBUNTU-CVE-2023-53216
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2023-53216
Ubuntu:22.04:LTSlinux-aws5.15.0-1042.47UBUNTU-CVE-2023-53216
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2023-53216
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2023-53216
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2023-53216
Ubuntu:22.04:LTSlinux-azure5.15.0-1045.52UBUNTU-CVE-2023-53216
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2023-53216
Ubuntu:24.04:LTSlinux-azure-6.11no fix listedUBUNTU-CVE-2023-53216
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2023-53216
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2023-53216
Ubuntu:22.04:LTSlinux-azure-fde5.15.0-1045.52.1UBUNTU-CVE-2023-53216
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2023-53216
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2023-53216
Ubuntu:22.04:LTSlinux-gcp5.15.0-1039.47UBUNTU-CVE-2023-53216
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2023-53216
Ubuntu:24.04:LTSlinux-gcp-6.11no fix listedUBUNTU-CVE-2023-53216
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2023-53216
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2023-53216
Ubuntu:22.04:LTSlinux-gke5.15.0-1039.44UBUNTU-CVE-2023-53216
Ubuntu:22.04:LTSlinux-gkeop5.15.0-1025.30UBUNTU-CVE-2023-53216
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2023-53216
Ubuntu:24.04:LTSlinux-hwe-6.11no fix listedUBUNTU-CVE-2023-53216
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2023-53216
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2023-53216
Ubuntu:22.04:LTSlinux-ibm5.15.0-1035.38UBUNTU-CVE-2023-53216
Ubuntu:24.04:LTSlinux-intelno fix listedUBUNTU-CVE-2023-53216
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2023-53216
Ubuntu:22.04:LTSlinux-intel-iotg5.15.0-1037.42UBUNTU-CVE-2023-53216
Ubuntu:22.04:LTSlinux-kvm5.15.0-1039.44UBUNTU-CVE-2023-53216
Ubuntu:22.04:LTSlinux-lowlatency5.15.0-79.88UBUNTU-CVE-2023-53216
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2023-53216
Ubuntu:24.04:LTSlinux-lowlatency-hwe-6.11no fix listedUBUNTU-CVE-2023-53216
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2023-53216
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2023-53216
Ubuntu:22.04:LTSlinux-nvidia5.15.0-1030.30UBUNTU-CVE-2023-53216
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2023-53216
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2023-53216
Ubuntu:22.04:LTSlinux-nvidia-tegra5.15.0-1016.16UBUNTU-CVE-2023-53216
Ubuntu:22.04:LTSlinux-nvidia-tegra-igx5.15.0-1002.2UBUNTU-CVE-2023-53216
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2023-53216
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2023-53216
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2023-53216
Ubuntu:24.04:LTSlinux-oem-6.11no fix listedUBUNTU-CVE-2023-53216
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2023-53216
Ubuntu:24.04:LTSlinux-oem-6.8no fix listedUBUNTU-CVE-2023-53216
Ubuntu:22.04:LTSlinux-oracle5.15.0-1040.46UBUNTU-CVE-2023-53216
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2023-53216
Ubuntu:22.04:LTSlinux-raspi5.15.0-1035.38UBUNTU-CVE-2023-53216
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2023-53216
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2023-53216
Ubuntu:24.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2023-53216
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2023-53216
Ubuntu:24.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2023-53216
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2023-53216
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2023-53216
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2023-53216
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2023-53216
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2023-53216
Ubuntu:22.04:LTSlinux-xilinx-zynqmp5.15.0-1025.29UBUNTU-CVE-2023-53216

Affected products (as reported)

VendorProductVersions
Linux Linux 4012603cbd469223f225637d265a233f034c567a – before 030b1c4217a4f504c7d0795a2bd86b7181e56f11de2af657cab92afc13a4ccd8780370481ed0eb61 – before 6a72729ed6accc86dad5522895e8fa2f96642a2cf75a91c82dc805af8f718ff106ec9c090234b37b – before 8b38969fa01662ec539a0d08a8ea5ec6f31fa4edff7a167961d1b97e0e205f245f806e564d3505e7 – before 4e8f7d998b582a99aadedd07ae6086e99b89c97aff7a167961d1b97e0e205f245f806e564d3505e7 – before 0e68b5517d3767562889f1d83fdb828c26adb24f5.10.165 – before 5.10.1755.15.90 – before 5.15.1036.1.8 – before 6.1.18
Linux Linux 6.2

References