CVE-2026-43227— Linux kernel 安全漏洞
一分钟漏洞结论
影响对象
Linux Linux
利用判断
尚无明确在野利用证据，仍需结合暴露面评估
建议动作
优先检查厂商安全公告和参考链接中的修复版本；无法立即升级时，限制受影响服务暴露并加强监测。
Linux kernel是美国Linux基金会的开源操作系统Linux所使用的内核。 Linux kernel存在安全漏洞，该漏洞源于TMU设备驱动在原始自旋锁上下文中管理电源状态和时钟，可能导致锁定问题。
可能的 ATT&CK 技术 1 AI
T1059 · Command and Scripting Interpreter影响版本矩阵 18
| 厂商 | 产品 | 版本范围 | 状态 |
|---|---|---|---|
| Linux | Linux | 9570ef20423b549757aa484ad388f9a7d5bdc4d9< 79d650695773f03de36b99228a090d33d1c18264 |
affected |
9570ef20423b549757aa484ad388f9a7d5bdc4d9< f0b31247e7d67a943b3a09d3cef7c0ae788d88e6 |
affected | ||
9570ef20423b549757aa484ad388f9a7d5bdc4d9< 016476afef993d1201a19decc9b5b2ea1e6620f2 |
affected | ||
9570ef20423b549757aa484ad388f9a7d5bdc4d9< 6f113ab549b864c1bc57d4f89846ee335394089a |
affected | ||
9570ef20423b549757aa484ad388f9a7d5bdc4d9< 88c76792180dffd83f1c5b9dc8fdaeb145cb94e0 |
affected | ||
9570ef20423b549757aa484ad388f9a7d5bdc4d9< bc59d5f3afe41fec5d673c27c703b761ae578d28 |
affected | ||
9570ef20423b549757aa484ad388f9a7d5bdc4d9< 0e513cc6b9cea190fe342cc222b1054e7e8acfc8 |
affected | ||
9570ef20423b549757aa484ad388f9a7d5bdc4d9< b1278972b08e480990e2789bdc6a7c918bc349be |
affected | ||
| … +10 条更多 | |||
获取后续新漏洞提醒
登录后订阅
一、 漏洞 CVE-2026-43227 基础信息
漏洞信息
对漏洞内容有疑问？看看神龙的深度分析是否有帮助！
查看神龙十问 ↗
尽管我们使用了先进的大模型技术，但其输出仍可能包含不准确或过时的信息。神龙努力确保数据的准确性，但请您根据实际情况进行核实和判断。
Vulnerability Title
clocksource/drivers/sh_tmu: Always leave device running after probe
来源: CVE Program / CVE List V5
Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved:
clocksource/drivers/sh_tmu: Always leave device running after probe
The TMU device can be used as both a clocksource and a clockevent
provider. The driver tries to be smart and power itself on and off, as
well as enabling and disabling its clock when it's not in operation.
This behavior is slightly altered if the TMU is used as an early
platform device in which case the device is left powered on after probe,
but the clock is still enabled and disabled at runtime.
This has worked for a long time, but recent improvements in PREEMPT_RT
and PROVE_LOCKING have highlighted an issue. As the TMU registers itself
as a clockevent provider, clockevents_register_device(), it needs to use
raw spinlocks internally as this is the context of which the clockevent
framework interacts with the TMU driver. However in the context of
holding a raw spinlock the TMU driver can't really manage its power
state or clock with calls to pm_runtime_*() and clk_*() as these calls
end up in other platform drivers using regular spinlocks to control
power and clocks.
This mix of spinlock contexts trips a lockdep warning.
=============================
[ BUG: Invalid wait context ]
6.18.0-arm64-renesas-09926-gee959e7c5e34 #1 Not tainted
-----------------------------
swapper/0/0 is trying to lock:
ffff000008c9e180 (&dev->power.lock){-...}-{3:3}, at: __pm_runtime_resume+0x38/0x88
other info that might help us debug this:
context-{5:5}
1 lock held by swapper/0/0:
ccree e6601000.crypto: ARM CryptoCell 630P Driver: HW version 0xAF400001/0xDCC63000, Driver version 5.0
#0: ffff8000817ec298
ccree e6601000.crypto: ARM ccree device initialized
(tick_broadcast_lock){-...}-{2:2}, at: __tick_broadcast_oneshot_control+0xa4/0x3a8
stack backtrace:
CPU: 0 UID: 0 PID: 0 Comm: swapper/0 Not tainted 6.18.0-arm64-renesas-09926-gee959e7c5e34 #1 PREEMPT
Hardware name: Renesas Salvator-X 2nd version board based on r8a77965 (DT)
Call trace:
show_stack+0x14/0x1c (C)
dump_stack_lvl+0x6c/0x90
dump_stack+0x14/0x1c
__lock_acquire+0x904/0x1584
lock_acquire+0x220/0x34c
_raw_spin_lock_irqsave+0x58/0x80
__pm_runtime_resume+0x38/0x88
sh_tmu_clock_event_set_oneshot+0x84/0xd4
clockevents_switch_state+0xfc/0x13c
tick_broadcast_set_event+0x30/0xa4
__tick_broadcast_oneshot_control+0x1e0/0x3a8
tick_broadcast_oneshot_control+0x30/0x40
cpuidle_enter_state+0x40c/0x680
cpuidle_enter+0x30/0x40
do_idle+0x1f4/0x280
cpu_startup_entry+0x34/0x40
kernel_init+0x0/0x130
do_one_initcall+0x0/0x230
__primary_switched+0x88/0x90
For non-PREEMPT_RT builds this is not really an issue, but for
PREEMPT_RT builds where normal spinlocks can sleep this might be an
issue. Be cautious and always leave the power and clock running after
probe.
来源: CVE Program / CVE List V5
CVSS Information
N/A
来源: CVE Program / CVE List V5
Vulnerability Type
N/A
来源: CVE Program / CVE List V5
Vulnerability Title
Linux kernel 安全漏洞
来源: 中国国家信息安全漏洞库 CNNVD
Vulnerability Description
Linux kernel是美国Linux基金会的开源操作系统Linux所使用的内核。 Linux kernel存在安全漏洞，该漏洞源于TMU设备驱动在原始自旋锁上下文中管理电源状态和时钟，可能导致锁定问题。
来源: 中国国家信息安全漏洞库 CNNVD
CVSS Information
N/A
来源: 中国国家信息安全漏洞库 CNNVD
Vulnerability Type
N/A
来源: 中国国家信息安全漏洞库 CNNVD
受影响产品
二、漏洞 CVE-2026-43227 的公开POC
| # | POC 描述 | 源链接 | 神龙链接 |
|---|
AI 生成 POC
高级
未找到公开 POC。
登录以生成 AI POC三、漏洞 CVE-2026-43227 的情报信息
请登录查看更多情报信息。
CVE-2026-43227 补丁与修复 (8)
同批安全公告 · Linux · 2026-05-06 · 共 224 条
| CVE-2026-43186 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-43185 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-43125 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-43208 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-43198 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-43114 | 9.4 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-43117 | 9.1 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-43083 | 9.1 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-43197 | 9.1 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-43232 | 8.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2026-43215 | 8.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2026-43112 | 8.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2026-43113 | 8.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2026-43110 | 8.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2026-43187 | 8.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2026-43283 | 8.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2026-43176 | 8.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2026-43239 | 8.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2026-43249 | 8.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2026-43172 | 8.8 HIGH | Linux kernel 安全漏洞 |
显示前 20 条，共 224 条。 查看全部 → →
IV. Related Vulnerabilities
V. Comments for CVE-2026-43227
暂无评论