Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1359 CNY

100%
Buy Us a Coffee

CVE-2023-53067— LoongArch: Only call get_timer_irq() once in constant_clockevent_init()

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存在安全漏洞，该漏洞源于在preemption disable上下文中调用might_sleep。

AI Predicted 5.3 Difficulty: Moderate EPSS 0.20% · P9

Affected Version Matrix 8

VendorProduct Version RangeStatus
Linux Linux fa96b57c149061f71a70bd6582d995f6424fbbf4< b9c379e1d7e141b102f41858c9b8f6f36e7c89a4 affected
fa96b57c149061f71a70bd6582d995f6424fbbf4< acadbd058fa12b510fbecca11eae22bd6f654250 affected
fa96b57c149061f71a70bd6582d995f6424fbbf4< bb7a78e343468873bf00b2b181fcfd3c02d8cb56 affected
5.19 affected
< 5.19 unaffected
6.1.21≤ 6.1.* unaffected
6.2.8≤ 6.2.* unaffected
6.3≤ * unaffected
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2023-53067

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
LoongArch: Only call get_timer_irq() once in constant_clockevent_init()
Source: CVE Program / CVE List V5
Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved: LoongArch: Only call get_timer_irq() once in constant_clockevent_init() Under CONFIG_DEBUG_ATOMIC_SLEEP=y and CONFIG_DEBUG_PREEMPT=y, we can see the following messages on LoongArch, this is because using might_sleep() in preemption disable context. [ 0.001127] smp: Bringing up secondary CPUs ... [ 0.001222] Booting CPU#1... [ 0.001244] 64-bit Loongson Processor probed (LA464 Core) [ 0.001247] CPU1 revision is: 0014c012 (Loongson-64bit) [ 0.001250] FPU1 revision is: 00000000 [ 0.001252] BUG: sleeping function called from invalid context at kernel/locking/mutex.c:283 [ 0.001255] in_atomic(): 1, irqs_disabled(): 1, non_block: 0, pid: 0, name: swapper/1 [ 0.001257] preempt_count: 1, expected: 0 [ 0.001258] RCU nest depth: 0, expected: 0 [ 0.001259] Preemption disabled at: [ 0.001261] [<9000000000223800>] arch_dup_task_struct+0x20/0x110 [ 0.001272] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 6.2.0-rc7+ #43 [ 0.001275] Hardware name: Loongson Loongson-3A5000-7A1000-1w-A2101/Loongson-LS3A5000-7A1000-1w-A2101, BIOS vUDK2018-LoongArch-V4.0.05132-beta10 12/13/202 [ 0.001277] Stack : 0072617764726148 0000000000000000 9000000000222f1c 90000001001e0000 [ 0.001286] 90000001001e3be0 90000001001e3be8 0000000000000000 0000000000000000 [ 0.001292] 90000001001e3be8 0000000000000040 90000001001e3cb8 90000001001e3a50 [ 0.001297] 9000000001642000 90000001001e3be8 be694d10ce4139dd 9000000100174500 [ 0.001303] 0000000000000001 0000000000000001 00000000ffffe0a2 0000000000000020 [ 0.001309] 000000000000002f 9000000001354116 00000000056b0000 ffffffffffffffff [ 0.001314] 0000000000000000 0000000000000000 90000000014f6e90 9000000001642000 [ 0.001320] 900000000022b69c 0000000000000001 0000000000000000 9000000001736a90 [ 0.001325] 9000000100038000 0000000000000000 9000000000222f34 0000000000000000 [ 0.001331] 00000000000000b0 0000000000000004 0000000000000000 0000000000070000 [ 0.001337] ... [ 0.001339] Call Trace: [ 0.001342] [<9000000000222f34>] show_stack+0x5c/0x180 [ 0.001346] [<90000000010bdd80>] dump_stack_lvl+0x60/0x88 [ 0.001352] [<9000000000266418>] __might_resched+0x180/0x1cc [ 0.001356] [<90000000010c742c>] mutex_lock+0x20/0x64 [ 0.001359] [<90000000002a8ccc>] irq_find_matching_fwspec+0x48/0x124 [ 0.001364] [<90000000002259c4>] constant_clockevent_init+0x68/0x204 [ 0.001368] [<900000000022acf4>] start_secondary+0x40/0xa8 [ 0.001371] [<90000000010c0124>] smpboot_entry+0x60/0x64 Here are the complete call chains: smpboot_entry() start_secondary() constant_clockevent_init() get_timer_irq() irq_find_matching_fwnode() irq_find_matching_fwspec() mutex_lock() might_sleep() __might_sleep() __might_resched() In order to avoid the above issue, we should break the call chains, using timer_irq_installed variable as check condition to only call get_timer_irq() once in constant_clockevent_init() is a simple and proper way.
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存在安全漏洞，该漏洞源于在preemption disable上下文中调用might_sleep。
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

Vendor Product Affected Versions CPE Subscribe
Linux Linux fa96b57c149061f71a70bd6582d995f6424fbbf4 ~ b9c379e1d7e141b102f41858c9b8f6f36e7c89a4 -
Linux Linux 5.19 -

II. Public POCs for CVE-2023-53067

# POC Description Source Link Shenlong Link
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2023-53067

请登录查看更多情报信息。

Patches & Fixes for CVE-2023-53067 (3)

Same Patch Batch · Linux · 2025-05-02 · 107 CVEs total

CVE-2023-53116 9.8 CRITICAL nvmet: avoid potential UAF in nvmet_req_complete()
CVE-2023-53083 9.8 CRITICAL nfsd: don't replace page in rq_pages if it's a continuation of last page
CVE-2023-53086 8.8 HIGH wifi: mt76: connac: do not check WED status for non-mmio devices
CVE-2025-37798 7.8 HIGH codel: remove sch->q.qlen check before qdisc_tree_reduce_backlog()
CVE-2023-53138 7.8 HIGH net: caif: Fix use-after-free in cfusbl_device_notify()
CVE-2023-53111 7.8 HIGH loop: Fix use-after-free issues
CVE-2023-53107 7.8 HIGH veth: Fix use after free in XDP_REDIRECT
CVE-2023-53102 7.8 HIGH ice: xsk: disable txq irq before flushing hw
CVE-2023-53100 7.8 HIGH ext4: fix WARNING in ext4_update_inline_data
CVE-2023-53094 7.8 HIGH tty: serial: fsl_lpuart: fix race on RX DMA shutdown
CVE-2023-53090 7.8 HIGH drm/amdkfd: Fix an illegal memory access
CVE-2023-53088 7.8 HIGH mptcp: fix UaF in listener shutdown
CVE-2023-53087 7.8 HIGH drm/i915/active: Fix misuse of non-idle barriers as fence trackers
CVE-2023-53084 7.8 HIGH drm/shmem-helper: Remove another errant put in error path
CVE-2023-53080 7.8 HIGH xsk: Add missing overflow check in xdp_umem_reg
CVE-2023-53072 7.8 HIGH mptcp: use the workqueue to destroy unaccepted sockets
CVE-2023-53065 7.8 HIGH perf/core: Fix perf_output_begin parameter is incorrectly invoked in perf_event_bpf_output
CVE-2023-53057 7.8 HIGH Bluetooth: HCI: Fix global-out-of-bounds
CVE-2023-53052 7.8 HIGH cifs: fix use-after-free bug in refresh_cache_worker()
CVE-2023-53043 7.8 HIGH arm64: dts: qcom: sc7280: Mark PCIe controller as cache coherent

Showing top 20 of 107 CVEs. View all on vendor page &rarr; →

IV. Related Vulnerabilities

Same product: Linux
Same vendor: Linux

V. Comments for CVE-2023-53067

No comments yet

Leave a comment