LiveActive security incident?Get immediate response
CVE Record

CVE-2024-41053: scsi: ufs: core: Fix ufshcd_abort_one racing issue

In the Linux kernel, the following vulnerability has been resolved: scsi: ufs: core: Fix ufshcd_abort_one racing issue When ufshcd_abort_one is racing with the completion ISR, the completed tag of the request's mq_hctx pointer will be set to NULL by ISR. Return success when request is completed by ISR because ufshcd_abort_one does not need to do anything. The racing flow is: Thread A ufshcd_err_handler step 1 ... ufshcd_abort_one ufshcd_try_to_abort_task ufshcd_cmd_inflight(true) step 3 ufshcd_mcq_req_to_hwq blk_mq_unique_tag rq->mq_hctx->queue_num step 5 Thread B ufs_mtk_mcq_intr(cq complete ISR) step 2 scsi_done ... __blk_mq_free_request rq->mq_hctx = NULL; step 4 Below is KE back trace. ufshcd_try_to_abort_task: cmd at tag 41 not pending in the device. ufshcd_try_to_abort_task: cmd at tag=41 is cleared. Aborting tag 41 / CDB 0x28 succeeded Unable to handle kernel NULL pointer dereference at virtual address 0000000000000194 pc : [0xffffffddd7a79bf8] blk_mq_unique_tag+0x8/0x14 lr : [0xffffffddd6155b84] ufshcd_mcq_req_to_hwq+0x1c/0x40 [ufs_mediatek_mod_ise] do_mem_abort+0x58/0x118 el1_abort+0x3c/0x5c el1h_64_sync_handler+0x54/0x90 el1h_64_sync+0x68/0x6c blk_mq_unique_tag+0x8/0x14 ufshcd_err_handler+0xae4/0xfa8 [ufs_mediatek_mod_ise] process_one_work+0x208/0x4fc worker_thread+0x228/0x438 kthread+0x104/0x1d4 ret_from_fork+0x10/0x20

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2024-41053 is a Linux kernel race condition in the UFS storage driver path. Under a specific timing condition, the kernel can dereference a NULL pointer during request abort handling, likely causing a kernel crash. The sources do not provide CVSS, confirmed exploitation, or product-specific advisories.

Executive priority

Handle as kernel maintenance with outage relevance, especially for UFS-based devices. There is no source-backed evidence of active exploitation, but a storage-path kernel crash can still affect availability and device reliability.

Technical view

The bug occurs when ufshcd_abort_one races with the completion ISR. The ISR may complete and free the request, setting rq->mq_hctx to NULL, while the abort path still reaches blk_mq_unique_tag through ufshcd_mcq_req_to_hwq. The stable fix treats an already completed request as successful.

Likely exposure

Exposure is most likely on Linux systems running affected kernel versions with the UFS storage stack in use. The bundle lists affected Linux kernel versions including 6.7, 6.6.41, 6.9.10, and 6.10, but does not map exposure to specific distributions or devices.

Exploitation context

The bundle does not cite active exploitation, and KEV is false. The available evidence describes a race-triggered kernel NULL pointer dereference observed in a crash trace, not a public exploit or remote attack path.

Researcher notes

The key condition is request completion racing with abort handling. The completion path clears mq_hctx before the abort path derives a hardware queue from the request. The fix avoids unnecessary abort work when the request has already completed.

Mitigation direction

  • Update to a kernel containing the referenced stable fixes.
  • Check distribution or device-vendor advisories for packaged fixed versions.
  • Prioritize systems using UFS storage or UFS host controller drivers.
  • Avoid inventing local workarounds; follow vendor guidance if patching is delayed.

Validation and detection

  • Inventory Linux kernel versions across affected fleets.
  • Confirm whether UFS kernel drivers are enabled or loaded.
  • Verify the referenced stable commits are present in deployed kernels.
  • Review crash logs for ufshcd_abort_one, blk_mq_unique_tag, or NULL pointer traces.
  • Run normal storage regression tests after kernel updates.
Prepared
Confidence
medium
Sources
5

Public sources used

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-41053 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

0CVSS vectors
3Timeline events
2ADP providers
4Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxff7699d3620763b0dfe2ff93df4528880bf903a8, 93e6c0e19d5bb12b49534a411c85e21d333731fa, 93e6c0e19d5bb12b49534a411c85e21d333731fa, 6.6.5unaffected
LinuxLinux6.7, 0, 6.6.41, 6.9.10, 6.10affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.