CVE-2023-53634— bpf, arm64: Fixed a BTI error on returning to patched function
Quick assessment
Affected
Linux Linux
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.
Linux kernel是美国Linux基金会的开源操作系统Linux所使用的内核。 Linux kernel存在安全漏洞，该漏洞源于BPF跳板使用BLR指令返回修补函数时未检查BTI指令，可能导致分支目标识别异常。
Possible ATT&CK Techniques 2 AI
T1068 · Exploitation for Privilege Escalation T1190 · Exploit Public-Facing ApplicationAffected Version Matrix 8
| Vendor | Product | Version Range | Status |
|---|---|---|---|
| Linux | Linux | efc9909fdce00a827a37609628223cd45bf95d0b< 8b9c64942ada229f52fe6f1b537a50f88b3c2673 |
affected |
efc9909fdce00a827a37609628223cd45bf95d0b< eabc166919d169e105263974991f52b0351e431a |
affected | ||
efc9909fdce00a827a37609628223cd45bf95d0b< 738a96c4a8c36950803fdd27e7c30aca92dccefd |
affected | ||
6.0 |
affected | ||
< 6.0 |
unaffected | ||
6.1.25≤ 6.1.* |
unaffected | ||
6.2.12≤ 6.2.* |
unaffected | ||
6.3≤ * |
unaffected |
Get alerts for future matching vulnerabilities
Log in to subscribe
I. Basic Information for CVE-2023-53634
Vulnerability Information
Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗
Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.
Vulnerability Title
bpf, arm64: Fixed a BTI error on returning to patched function
Source: CVE Program / CVE List V5
Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved:
bpf, arm64: Fixed a BTI error on returning to patched function
When BPF_TRAMP_F_CALL_ORIG is set, BPF trampoline uses BLR to jump
back to the instruction next to call site to call the patched function.
For BTI-enabled kernel, the instruction next to call site is usually
PACIASP, in this case, it's safe to jump back with BLR. But when
the call site is not followed by a PACIASP or bti, a BTI exception
is triggered.
Here is a fault log:
Unhandled 64-bit el1h sync exception on CPU0, ESR 0x0000000034000002 -- BTI
CPU: 0 PID: 263 Comm: test_progs Tainted: GF
Hardware name: linux,dummy-virt (DT)
pstate: 40400805 (nZcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=-c)
pc : bpf_fentry_test1+0xc/0x30
lr : bpf_trampoline_6442573892_0+0x48/0x1000
sp : ffff80000c0c3a50
x29: ffff80000c0c3a90 x28: ffff0000c2e6c080 x27: 0000000000000000
x26: 0000000000000000 x25: 0000000000000000 x24: 0000000000000050
x23: 0000000000000000 x22: 0000ffffcfd2a7f0 x21: 000000000000000a
x20: 0000ffffcfd2a7f0 x19: 0000000000000000 x18: 0000000000000000
x17: 0000000000000000 x16: 0000000000000000 x15: 0000ffffcfd2a7f0
x14: 0000000000000000 x13: 0000000000000000 x12: 0000000000000000
x11: 0000000000000000 x10: ffff80000914f5e4 x9 : ffff8000082a1528
x8 : 0000000000000000 x7 : 0000000000000000 x6 : 0101010101010101
x5 : 0000000000000000 x4 : 00000000fffffff2 x3 : 0000000000000001
x2 : ffff8001f4b82000 x1 : 0000000000000000 x0 : 0000000000000001
Kernel panic - not syncing: Unhandled exception
CPU: 0 PID: 263 Comm: test_progs Tainted: GF
Hardware name: linux,dummy-virt (DT)
Call trace:
dump_backtrace+0xec/0x144
show_stack+0x24/0x7c
dump_stack_lvl+0x8c/0xb8
dump_stack+0x18/0x34
panic+0x1cc/0x3ec
__el0_error_handler_common+0x0/0x130
el1h_64_sync_handler+0x60/0xd0
el1h_64_sync+0x78/0x7c
bpf_fentry_test1+0xc/0x30
bpf_fentry_test1+0xc/0x30
bpf_prog_test_run_tracing+0xdc/0x2a0
__sys_bpf+0x438/0x22a0
__arm64_sys_bpf+0x30/0x54
invoke_syscall+0x78/0x110
el0_svc_common.constprop.0+0x6c/0x1d0
do_el0_svc+0x38/0xe0
el0_svc+0x30/0xd0
el0t_64_sync_handler+0x1ac/0x1b0
el0t_64_sync+0x1a0/0x1a4
Kernel Offset: disabled
CPU features: 0x0000,00034c24,f994fdab
Memory Limit: none
And the instruction next to call site of bpf_fentry_test1 is ADD,
not PACIASP:
<bpf_fentry_test1>:
bti c
nop
nop
add w0, w0, #0x1
paciasp
For BPF prog, JIT always puts a PACIASP after call site for BTI-enabled
kernel, so there is no problem. To fix it, replace BLR with RET to bypass
the branch target check.
Source: CVE Program / CVE List V5
CVSS Information
N/A
Source: CVE Program / CVE List V5
Vulnerability Type
N/A
Source: CVE Program / CVE List V5
Vulnerability Title
Linux kernel 安全漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
Linux kernel是美国Linux基金会的开源操作系统Linux所使用的内核。 Linux kernel存在安全漏洞，该漏洞源于BPF跳板使用BLR指令返回修补函数时未检查BTI指令，可能导致分支目标识别异常。
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)
Affected Products
II. Public POCs for CVE-2023-53634
| # | POC Description | Source Link | Shenlong Link |
|---|
AI-Generated POC
Premium
No public POC found.
Login to generate AI POCIII. Intelligence Information for CVE-2023-53634
请登录查看更多情报信息。
Patches & Fixes for CVE-2023-53634 (3)
Same Patch Batch · Linux · 2025-10-07 · 118 CVEs total
| CVE-2023-53629 | 9.8 CRITICAL | fs: dlm: fix use after free in midcomms commit |
| CVE-2023-53630 | 8.8 HIGH | iommufd: Fix unpinning of pages when an access is present |
| CVE-2023-53676 | 8.8 HIGH | scsi: target: iscsi: Fix buffer overflow in lio_target_nacl_info_show() |
| CVE-2023-53675 | 8.8 HIGH | scsi: ses: Fix possible desc_ptr out-of-bounds accesses |
| CVE-2023-53673 | 8.8 HIGH | Bluetooth: hci_event: call disconnect callback before deleting conn |
| CVE-2023-53679 | 8.3 HIGH | wifi: mt7601u: fix an integer underflow |
| CVE-2023-53635 | 8.2 HIGH | netfilter: conntrack: fix wrong ct->timeout value |
| CVE-2023-53669 | 7.8 HIGH | tcp: fix skb_copy_ubufs() vs BIG TCP |
| CVE-2022-50555 | 7.8 HIGH | tipc: fix a null-ptr-deref in tipc_topsrv_accept |
| CVE-2023-53627 | 7.8 HIGH | scsi: hisi_sas: Grab sas_dev lock when traversing the members of sas_dev.list |
| CVE-2023-53626 | 7.8 HIGH | ext4: fix possible double unlock when moving a directory |
| CVE-2023-53660 | 7.8 HIGH | bpf, cpumap: Handle skb as well when clean up ptr_ring |
| CVE-2023-53659 | 7.8 HIGH | iavf: Fix out-of-bounds when setting channels on remove |
| CVE-2023-53619 | 7.8 HIGH | netfilter: conntrack: Avoid nf_ct_helper_hash uses after free |
| CVE-2023-53643 | 7.8 HIGH | nvme-tcp: don't access released socket during error recovery |
| CVE-2023-53645 | 7.8 HIGH | bpf: Make bpf_refcount_acquire fallible for non-owning refs |
| CVE-2023-53646 | 7.8 HIGH | drm/i915/perf: add sentinel to xehp_oa_b_counters |
| CVE-2022-50528 | 7.8 HIGH | drm/amdkfd: Fix memory leakage |
| CVE-2023-53651 | 7.8 HIGH | Input: exc3000 - properly stop timer on shutdown |
| CVE-2022-50543 | 7.8 HIGH | RDMA/rxe: Fix mr->map double free |
Showing top 20 of 118 CVEs. View all on vendor page → →
IV. Related Vulnerabilities
Same product: Linux
-
CVE-2023-7356
Bluetooth: ISO: Copy BASE if service data matches EIR_BAA_SE -
CVE-2026-98869
bpf: Infer zext_dst based on static register liveness analys -
CVE-2026-98868
dm-pcache: reject a kset that overruns its segment -
CVE-2026-98867
dm-pcache: bound the logical key offset from persistent memo -
CVE-2026-98866
sched/cache: Introduce task_struct->sched_cache_grp to fix U
Same vendor: Linux
-
CVE-2023-7356
Bluetooth: ISO: Copy BASE if service data matches EIR_BAA_SE -
CVE-2026-98869
bpf: Infer zext_dst based on static register liveness analys -
CVE-2026-98868
dm-pcache: reject a kset that overruns its segment -
CVE-2026-98867
dm-pcache: bound the logical key offset from persistent memo -
CVE-2026-98866
sched/cache: Introduce task_struct->sched_cache_grp to fix U
V. Comments for CVE-2023-53634
No comments yet