CVE-2026-43415
CVE.org · Published
- Record status
- Published
- Identifier year (not publication year)
- 2026
- Source publication
- Source updated
- Imported by cveboard
- Source snapshot
- cve_2026-10-24_midnight_baseline ·
CNA source text (English)
scsi: ufs: core: Fix SError in ufshcd_rtc_work() during UFS suspend
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.
Scoped product and version facts
Fix information unknown; no fixed version is derived here. Missing information does not prove that no fix exists.
Exploitation unknown; this catalogue does not assess exploitation.
Linux
- Vendor
- Linux
- Product
- Linux
- Platforms
- Unknown
- Default status
unaffected
| Version (version) | Status (status) | Version scheme (versionType) | Exclusive end (lessThan) | Inclusive end (lessThanOrEqual) | Status changes (at → status) |
|---|---|---|---|---|---|
| 06701a545e9a3c4e007cff6872a074bf97c40619 | affected | git | a6a894413b043704b77a6294c379c93b1477e48d | Unavailable | None listed |
| 6bf999e0eb41850d5c857102535d5c53b2ede224 | affected | git | 2fcc2fc21cae7a0cbe73053f7fc70680ce2a7f69 | Unavailable | None listed |
| 6bf999e0eb41850d5c857102535d5c53b2ede224 | affected | git | b17211b512cbf0e07de27e1932428ee6c20df910 | Unavailable | None listed |
| 6bf999e0eb41850d5c857102535d5c53b2ede224 | affected | git | c387a8f1d3713f6b0415ece8485042d0f134b91a | Unavailable | None listed |
| 6bf999e0eb41850d5c857102535d5c53b2ede224 | affected | git | b0bd84c39289ef6a6c3827dd52c875659291970a | Unavailable | None listed |
| 6.6.81 | affected | semver | 6.6.130 | Unavailable | None listed |
Linux
- Vendor
- Linux
- Product
- Linux
- Platforms
- Unknown
- Default status
affected
| Version (version) | Status (status) | Version scheme (versionType) | Exclusive end (lessThan) | Inclusive end (lessThanOrEqual) | Status changes (at → status) |
|---|---|---|---|---|---|
| 6.8 | affected | Unavailable | Unavailable | Unavailable | None listed |
| 0 | unaffected | semver | 6.8 | Unavailable | None listed |
| 6.6.130 | unaffected | semver | Unavailable | 6.6.* | None listed |
| 6.12.78 | unaffected | semver | Unavailable | 6.12.* | None listed |
| 6.18.19 | unaffected | semver | Unavailable | 6.18.* | None listed |
| 6.19.9 | unaffected | semver | Unavailable | 6.19.* | None listed |
| 7.0 | unaffected | original_commit_for_fix | Unavailable | * | None listed |