LiveActive security incident?Get immediate response
CVE Record

CVE-2023-53510: scsi: ufs: core: Fix handling of lrbp->cmd

In the Linux kernel, the following vulnerability has been resolved: scsi: ufs: core: Fix handling of lrbp->cmd ufshcd_queuecommand() may be called two times in a row for a SCSI command before it is completed. Hence make the following changes: - In the functions that submit a command, do not check the old value of lrbp->cmd nor clear lrbp->cmd in error paths. - In ufshcd_release_scsi_cmd(), do not clear lrbp->cmd. See also scsi_send_eh_cmnd(). This commit prevents that the following appears if a command times out: WARNING: at drivers/ufs/core/ufshcd.c:2965 ufshcd_queuecommand+0x6f8/0x9a8 Call trace: ufshcd_queuecommand+0x6f8/0x9a8 scsi_send_eh_cmnd+0x2c0/0x960 scsi_eh_test_devices+0x100/0x314 scsi_eh_ready_devs+0xd90/0x114c scsi_error_handler+0x2b4/0xb70 kthread+0x16c/0x1e0

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue affects the UFS storage driver’s handling of an in-flight SCSI command. The public description shows a kernel warning during command timeout handling, not a confirmed data theft or remote compromise scenario. Business impact is currently best treated as reliability and patch hygiene until vendor or distro advisories provide more impact detail.

Executive priority

Handle through normal kernel patch management, with higher priority for fleets that depend on UFS storage or show storage timeout warnings. Current public evidence does not justify emergency response language, but incomplete impact detail means teams should not ignore it.

Technical view

In ufshcd_queuecommand(), the same SCSI command can be queued twice before completion. The fix changes UFS command submission and release paths so lrbp->cmd is not checked or cleared incorrectly. The source ties the bug to WARN output during SCSI error handling after a timeout.

Likely exposure

Exposure is likely limited to Linux kernels containing the affected UFS core code, especially systems that build, load, or rely on UFS storage support. The source bundle lists Linux as affected but does not provide distribution package names or device-specific exposure mapping.

Exploitation context

No active exploitation is stated in the provided sources, and KEV is false. The available evidence describes a kernel warning under timeout/error-handler conditions. It does not establish a remote attack vector, required privileges, or confidentiality/integrity impact.

Researcher notes

The source is authoritative but narrow: it documents the race-like command handling condition and fix, not a complete security impact analysis. Avoid inferring exploitability beyond the described warning path unless later vendor advisories add evidence.

Mitigation direction

  • Update affected Linux kernels through vendor or distribution-supported channels.
  • Confirm the target kernel includes one of the referenced stable fixes.
  • Prioritize UFS-dependent systems if storage reliability symptoms are present.
  • Monitor Linux distribution advisories for package-specific remediation guidance.

Validation and detection

  • Inventory systems running Linux kernels with UFS storage support enabled.
  • Compare kernel source or package changelogs against the referenced stable commits.
  • Review kernel logs for ufshcd_queuecommand warnings during SCSI timeout handling.
  • Confirm patched systems no longer show the described warning pattern.
Prepared
Confidence
medium
Sources
6

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-2023-53510 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
0ADP providers
5Source links

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.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux5a0b0cb9bee767ef10ff9ce2fb4141af06416288, 5a0b0cb9bee767ef10ff9ce2fb4141af06416288, 5a0b0cb9bee767ef10ff9ce2fb4141af06416288, 5a0b0cb9bee767ef10ff9ce2fb4141af06416288unaffected
LinuxLinux3.12, 0, 6.1.167, 6.3.13, 6.4.4, 6.5affected
Weakness

CWE details

No CWE listed

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