CVE-2023-53609: scsi: Revert "scsi: core: Do not increase scsi_device's iorequest_cnt if dispatch failed"
In the Linux kernel, the following vulnerability has been resolved:
scsi: Revert "scsi: core: Do not increase scsi_device's iorequest_cnt if dispatch failed"
The "atomic_inc(&cmd->device->iorequest_cnt)" in scsi_queue_rq() would
cause kernel panic because cmd->device may be freed after returning from
scsi_dispatch_cmd().
This reverts commit cfee29ffb45b1c9798011b19d454637d1b0fe87d.
Security readout for executives and security teams
Plain-English summary
CVE-2023-53609 is a Linux kernel SCSI core flaw that can cause a kernel panic. In business terms, affected systems may crash under the relevant storage I/O condition, creating availability risk. The provided sources do not give a CVSS score or evidence of active exploitation.
Executive priority
Treat this as an availability-risk patching item, not a confirmed emergency. Prioritize critical Linux systems where kernel crashes would affect production services, especially storage-heavy workloads, while awaiting vendor-specific severity and package guidance.
Technical view
The issue is tied to scsi_queue_rq() incrementing cmd->device->iorequest_cnt after scsi_dispatch_cmd() returns. The CVE description says cmd->device may already be freed, leading to a kernel panic. The upstream resolution is a revert of commit cfee29ffb45b1c9798011b19d454637d1b0fe87d.
Likely exposure
Exposure appears limited to Linux kernels containing the affected SCSI core change. The record lists Linux kernel version entries including 6.2, 6.3.4, and 6.4, but the affected-version data is sparse and should be verified against vendor kernel packages.
Exploitation context
The source bundle reports no CISA KEV listing and provides no public exploit evidence. The described impact is kernel panic, so the practical concern is availability loss rather than confirmed code execution or data compromise.
Researcher notes
Evidence is limited to the CVE record and kernel stable references. The root cause is a lifetime issue around cmd->device after scsi_dispatch_cmd(). The record does not provide CVSS, CWE, exploit status, or detailed distribution mapping.
Mitigation direction
Review Linux kernel vendor advisories for CVE-2023-53609 and affected package versions.
Prioritize kernel updates for production systems using SCSI-backed storage paths.
Apply stable kernel updates that include the referenced revert commits.
Avoid inventing local workarounds; use distribution or upstream kernel guidance.
Validation and detection
Inventory Linux kernel versions across servers, appliances, and VM images.
Check whether deployed kernels include commit cfee29ffb45b1c9798011b19d454637d1b0fe87d.
Confirm whether vendor kernel changelogs include the referenced stable fixes.
Monitor for unexplained kernel panics on systems using SCSI storage paths.
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-53609 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.
0CVSS vectors
3Timeline events
0ADP providers
3Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Oct 4, 2025, 15:44 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.