Menu

Star on GitHub · 3.2k

CVE-2026-43415

4.7 · MEDIUM

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 cal…

Published May 8, 2026CWE-362EPSS 0.11%

Overview

CVE-2026-43415 is a medium-severity vulnerability. It was published on May 8, 2026 and has a CVSS 3.1 base score of 4.7 (MEDIUM).

This vulnerability has a CVSS 3.1 base score of 4.7, rated MEDIUM. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical 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

el

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2026-43415?

CVE-2026-43415 is a medium-severity vulnerability. It was published on May 8, 2026 and has a CVSS 3.1 base score of 4.7 (MEDIUM).

How severe is CVE-2026-43415?

This vulnerability has a CVSS 3.1 base score of 4.7, rated MEDIUM. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2026-43415?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-43415?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-43415 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related MEDIUM CVEs from 2026

View all