CVE-2026-43415
Description
In the Linux kernel, the following vulnerability has been resolved:
scsi: ufs: core: Fix SError in ufshcd_rtc_work() during UFS suspend
In __ufshcd_wl_suspend(), cancel_delayed_work_sync() is called to cancel the UFS RTC work, but it is placed after ufshcd_vops_suspend(hba, pm_op, POST_CHANGE). This creates a race condition where ufshcd_rtc_work() can still be running while ufshcd_vops_suspend() is executing. When UFSHCD_CAP_CLK_GATING is not supported, the condition !hba->clk_gating.active_reqs is always true, causing ufshcd_update_rtc() to be executed. Since ufshcd_vops_suspend() typically performs clock gating operations, executing ufshcd_update_rtc() at that moment triggers an SError. The kernel panic trace is as follows:
Kernel panic - not syncing: Asynchronous SError Interrupt Call trace: dump_backtrace+0xec/0x128 show_stack+0x18/0x28 dump_stack_lvl+0x40/0xa0 dump_stack+0x18/0x24 panic+0x148/0x374 nmi_panic+0x3c/0x8c arm64_serror_panic+0x64/0x8c do_serror+0xc4/0xc8 el1h_64_error_handler+0x34/0x4c el1h_64_error+0x68/0x6c el1_interrupt+0x20/0x58 el1h_64_irq_handler+0x18/0x24 el1h_64_irq+0x68/0x6c ktime_get+0xc4/0x12c ufshcd_mcq_sq_stop+0x4c/0xec ufshcd_mcq_sq_cleanup+0x64/0x1dc ufshcd_clear_cmd+0x38/0x134 ufshcd_issue_dev_cmd+0x298/0x4d0 ufshcd_exec_dev_cmd+0x1a4/0x1c4 ufshcd_query_attr+0xbc/0x19c ufshcd_rtc_work+0x10c/0x1c8 process_scheduled_works+0x1c4/0x45c worker_thread+0x32c/0x3e8 kthread+0x120/0x1d8 ret_from_fork+0x10/0x20
Fix this by moving cancel_delayed_work_sync() before the call to ufshcd_vops_suspend(hba, pm_op, PRE_CHANGE), ensuring the UFS RTC work is fully completed or cancelled at that point.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
A race condition in the Linux kernel's UFS driver can cause a kernel panic (SError) during suspend due to delayed RTC work executing after clock gating.
In the Linux kernel's UFS core, the function __ufshcd_wl_suspend() calls cancel_delayed_work_sync() after ufshcd_vops_suspend(), creating a race where ufshcd_rtc_work() may still run during suspend, leading to an SError panic [1].
The race occurs when UFSHCD_CAP_CLK_GATING is not supported, making the condition !hba->clk_gating.active_reqs always true, causing ufshcd_update_rtc() to execute after clock gating operations have started. An attacker would need local access to trigger suspend/resume cycles, but no authentication is required beyond normal system operations.
An attacker can cause a kernel panic (SError) leading to denial of service (system crash). The panic trace shows it originates from ktime_get() during RTC work.
The fix moves cancel_delayed_work_sync() before the suspend call, ensuring the RTC work is cancelled before clock gating. The patch is available in the kernel stable tree [1].
AI Insight generated on May 18, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected products
1Patches
0No patches discovered yet.
Vulnerability mechanics
AI mechanics synthesis has not run for this CVE yet.
References
5- git.kernel.org/stable/c/2fcc2fc21cae7a0cbe73053f7fc70680ce2a7f69nvd
- git.kernel.org/stable/c/a6a894413b043704b77a6294c379c93b1477e48dnvd
- git.kernel.org/stable/c/b0bd84c39289ef6a6c3827dd52c875659291970anvd
- git.kernel.org/stable/c/b17211b512cbf0e07de27e1932428ee6c20df910nvd
- git.kernel.org/stable/c/c387a8f1d3713f6b0415ece8485042d0f134b91anvd
News mentions
0No linked articles in our index yet.