CVE-2024-26842: scsi: ufs: core: Fix shift issue in ufshcd_clear_cmd()
In the Linux kernel, the following vulnerability has been resolved:
scsi: ufs: core: Fix shift issue in ufshcd_clear_cmd()
When task_tag >= 32 (in MCQ mode) and sizeof(unsigned int) == 4, 1U <<
task_tag will out of bounds for a u32 mask. Fix this up to prevent
SHIFT_ISSUE (bitwise shifts that are out of bounds for their data type).
[name:debug_monitors&]Unexpected kernel BRK exception at EL1
[name:traps&]Internal error: BRK handler: 00000000f2005514 [#1] PREEMPT SMP
[name:mediatek_cpufreq_hw&]cpufreq stop DVFS log done
[name:mrdump&]Kernel Offset: 0x1ba5800000 from 0xffffffc008000000
[name:mrdump&]PHYS_OFFSET: 0x80000000
[name:mrdump&]pstate: 22400005 (nzCv daif +PAN -UAO)
[name:mrdump&]pc : [0xffffffdbaf52bb2c] ufshcd_clear_cmd+0x280/0x288
[name:mrdump&]lr : [0xffffffdbaf52a774] ufshcd_wait_for_dev_cmd+0x3e4/0x82c
[name:mrdump&]sp : ffffffc0081471b0
<snip>
Workqueue: ufs_eh_wq_0 ufshcd_err_handler
Call trace:
dump_backtrace+0xf8/0x144
show_stack+0x18/0x24
dump_stack_lvl+0x78/0x9c
dump_stack+0x18/0x44
mrdump_common_die+0x254/0x480 [mrdump]
ipanic_die+0x20/0x30 [mrdump]
notify_die+0x15c/0x204
die+0x10c/0x5f8
arm64_notify_die+0x74/0x13c
do_debug_exception+0x164/0x26c
el1_dbg+0x64/0x80
el1h_64_sync_handler+0x3c/0x90
el1h_64_sync+0x68/0x6c
ufshcd_clear_cmd+0x280/0x288
ufshcd_wait_for_dev_cmd+0x3e4/0x82c
ufshcd_exec_dev_cmd+0x5bc/0x9ac
ufshcd_verify_dev_init+0x84/0x1c8
ufshcd_probe_hba+0x724/0x1ce0
ufshcd_host_reset_and_restore+0x260/0x574
ufshcd_reset_and_restore+0x138/0xbd0
ufshcd_err_handler+0x1218/0x2f28
process_one_work+0x5fc/0x1140
worker_thread+0x7d8/0xe20
kthread+0x25c/0x468
ret_from_fork+0x10/0x20
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel storage-driver bug. On systems using UFS storage in MCQ mode, certain command tags can trigger an invalid bit shift and a kernel BRK exception, causing a crash. The public record does not show active exploitation or a CVSS score.
Executive priority
Schedule remediation through the normal kernel update process, with higher priority for fleets where UFS storage outages would affect customer service, device availability, or operational continuity. There is no source-backed evidence of active exploitation in the provided bundle.
Technical view
ufshcd_clear_cmd() used 1U << task_tag against a u32 mask. When task_tag is 32 or greater in MCQ mode, the shift is out of bounds for a 32-bit unsigned value, producing SHIFT_ISSUE behavior and observed kernel exception traces in UFS error handling.
Likely exposure
Exposure is most likely on Linux systems in the listed affected kernel ranges that use UFS storage with MCQ mode enabled. The bundle lists Linux 6.5, 6.6.19, 6.7.7, and 6.8 as affected, but product-specific distribution status is not provided.
Exploitation context
The source bundle does not cite public exploitation, weaponized techniques, or CISA KEV listing. The available evidence is a kernel crash trace and upstream stable fixes. Treat this primarily as an availability and reliability risk unless a vendor advisory states otherwise.
Researcher notes
The vulnerability is narrowly tied to UFS core command clearing in MCQ mode and an out-of-bounds shift on 32-bit masks. The bundle lacks CVSS, CWE, distro advisories, and exploitability analysis, so validation should focus on kernel version, UFS/MCQ presence, and backport evidence.
Mitigation direction
Review vendor or distribution advisories for kernels containing the referenced stable fixes.
Prioritize updates on UFS-based mobile, embedded, edge, or appliance Linux deployments.
If immediate patching is unavailable, monitor for UFS error-handler crashes and vendor workarounds.
Do not assume non-upstream kernels are fixed without checking their backport status.
Validation and detection
Inventory Linux kernel versions on systems using UFS storage controllers.
Confirm whether UFS MCQ mode is enabled or supported on affected devices.
Check kernel changelogs for the referenced ufshcd_clear_cmd() fix commits.
Review logs for BRK exceptions or crashes involving ufshcd_clear_cmd().
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2024-26842 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.