From mboxrd@z Thu Jan 1 00:00:00 1970 From: AL-KERNEL To: kernel-cve@kernelcve.org Subject: [CVE-2023-53510][MODERATE REGULAR] scsi: ufs: core: Fix handling of lrbp->cmd [ Upstream Date: Sun, 18 Oct 2026 22:43:02 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-AL-KERNEL-CVE: CVE-2023-53510 X-AL-KERNEL-Priority: MODERATE REGULAR X-AL-KERNEL-Severity: MODERATE REGULAR X-AL-KERNEL-Base-Severity: MODERATE X-AL-KERNEL-KPANIC: NO X-AL-KERNEL-ActionableScore: 0 X-AL-KERNEL-ActionableScore-Lower: unknown X-AL-KERNEL-Commit: f3ee24af62681b942bbd799ac77b90a6d7e1fdb1 List-Id: CVE: CVE-2023-53510 Priority: MODERATE REGULAR AL-KERNEL base severity: MODERATE KPANIC flag: NO Patch: scsi: ufs: core: Fix handling of lrbp->cmd [ Upstream Commit: f3ee24af62681b942bbd799ac77b90a6d7e1fdb1 Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=f3ee24af62681b942bbd799ac77b90a6d7e1fdb1 Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2023-53510 Analysis date: Sun, 18 Oct 2026 22:43:02 -0400 ActionableScore: 0 ActionableScore lower bound: unknown Actionable bucket: Ordinary Moderate Manual review required: NO Summary: The UFS driver incorrectly warned when SCSI error handling resubmitted the same command before completion, but the supplied code establishes only command-state bookkeeping and a WARN_ON rather than UAF, memory corruption, or an independently reliable kernel crash. ====================================================================== ABOUT THIS REPORT ====================================================================== The original Linux kernel CVE announcement for CVE-2023-53510 is available here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2023-53510 The original announcement does not normally provide a security severity estimate, CVSS assessment, or enough information to determine whether the reported kernel bug represents a practically relevant security issue. This report was generated by AL-KERNEL, an AI-assisted Linux kernel vulnerability analysis system developed by Alexander Larkin. It combines an autonomous classifier with LLM-assisted technical analysis and a separate ActionableScore mechanism. The purpose of this report is to prioritize Linux kernel CVEs before manual review, identify cases that require prompt investigation, and support automatic closure of issues that are unlikely to have meaningful security impact. Published priority for this report: MODERATE REGULAR Manual review required: NO A detailed explanation of the methodology and priority rules is included at the end of this message. ====================================================================== AL-KERNEL CLASSIFICATION RESULT ====================================================================== CVE-2023-53510 MODERATE https://www.kernelcve.org/list/?q=CVE-2023-53510 CHECK WITH IMPACT FROM ORIG NN LOW | AEGIS IMPACT MODERATE AEGIS_AS=0 LEGACY=MODERATE RESULT=SAME V39_AEGIS_ONE_STEP_UP=LOW->MODERATE (final reconciliation agrees; DECISION: both MODERATE) Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H';CWE-362;*CWE-664;**CWE-476;Other CVSS 'AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:L';BEST CVSS score: '4.7';DESCR 'The UFS core handled lrbp cmd as if each SCSI command could be queued only once before completion, although SCSI error handling may submit the same command again through scsi_send_eh_cmnd. Clearing or validating this pointer at the wrong stage can create inconsistent command state and produces a kernel warning when a timed out command enters recovery. The demonstrated impact is a warning and possible local denial of service when panic_on_warn is enabled. A more general command completion failure or kernel crash is plausible if the inconsistent pointer state reaches another completion path, but the available code does not establish UAF, OOB access, information disclosure, or an arbitrary write primitive. For the CVSS the PR:L value is used for the paranoid score because a local user can generate storage I/O and may reach the recovery path when the UFS device is already timing out, although reliable creation of the timeout may require device control or an existing hardware fault. The issue is not network reachable. Impact is limited to availability based on the currently supported evidence. Automated impact decision path. The original SimpleNet classifier selected LOW. The primary LLM estimated paranoid CVSS 4.7 and the production ActionableScore returned 0 with recommendation Ordinary Moderate. The production rules then evaluated CVSS thresholds and ActionableScore thresholds. Recorded rule transitions were final reconciliation stage LOW to MODERATE because KP specialist did not establish a qualifying panic and the cross model evidence reconciliation rule was applied. The legacy KP specialist has no review artifact for this run. The legacy FD or DH downgrade specialist has no review artifact for this run. Exact triggered rule markers were KPANIC_UNSUPPORTED_REMOVED and V39_AEGIS_ONE_STEP_UP and MANUAL_REVIEW_REQUIRED. The independent weaker Aegis shadow evaluated CVSS 0.0 and ActionableScore 0 with primitive class CLASS_C and manual review NO. Its independently reconciled impact was MODERATE. Cross model aggregation changed the production result under an enabled evidence gated merge rule. The final reported impact is MODERATE.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate (with actual score 0) MAYBE DISK WARNONLY ERRORPATH IMPROVEONLY LINUS CVEOUTDATED KPANIC_UNSUPPORTED_REMOVED V39_AEGIS_ONE_STEP_UP MANUAL_REVIEW_REQUIRED - - checked ====================================================================== ACTIONABLESCORE ANALYSIS ====================================================================== ActionableScore=0 PrimitiveClass=CLASS_C RealUAF=NO HostAdminRequired=UNKNOWN NamespaceScopedPrivilege=UNKNOWN ImportantCandidate=NO ManualReview=NO AutoDowngradeAllowed=YES RequiresHostUID0=UNKNOWN AuthorizationDecisionBypass=NO ProtectedResourceImpact=NONE B4PendingReview=NO B4PendingConfirmed=NO 1. ActionableScore * Raw conservative score: 0 * Conservative score: 0 * Raw paranoid score: 0 * Paranoid score: 0 * No floor or cap was applied. * Final recommended bucket: **Ordinary Moderate**:: 2. Signal breakdown * +0 WARN_ON behavior. The demonstrated result is a warning after a UFS command timeout. WARN_ON alone does not establish a fatal consequence. * +0 kernel corruption. The patch does not establish UAF, OOB access, double release, invalid DMA, or dereference of a freed `scsi_cmnd`. * +0 availability. A kernel panic requires an additional `panic_on_warn` policy. The patch does not demonstrate an independent crash caused by `lrbp->cmd`. * +0 local unprivileged trigger. Ordinary storage I/O may be available, but the supplied evidence does not show that an ordinary user can reliably cause the required UFS command timeout. * +0 authorization impact. No access-control decision or protected resource is involved. * No privilege, hardware-rarity, race, or configuration penalty was applied because the complete trigger requirements are unresolved. * Controlled reclaim, arbitrary write, information disclosure, privilege escalation, remote reachability, and repeated lifetime mutation are not demonstrated. * NEW52 B5-R does not apply. There is no heap OOB write, retry-accumulated offset, or consumption of corrupted heap state. * NEW53 B3-PENDING does not apply. No shared-backing write or missing writable isolation is present. * NEW54 B4-PENDING does not apply. No DENY-to-ALLOW authorization change exists. 3. Reachability analysis The warning occurs when SCSI error handling resubmits a command through `scsi_send_eh_cmnd()` after a UFS command timeout. A local process can generate storage requests, but control over the timeout itself is not established. Device failure, controller behavior, or administrative fault injection may be required. No network trigger, namespace capability path, delegated interface, or host UID 0 requirement is shown. The complete privilege boundary therefore remains unknown rather than proven unprivileged or host-admin-only. UFS hardware is required, but the mere use of a hardware driver is insufficient for a rarity penalty. This is an ordered recovery sequence, not an established race. 4. Primitive and severity interpretation The exact demonstrated behavior is a false or obsolete command-state warning. `lrbp->cmd` cannot be treated as an exclusive in-flight marker because the SCSI error handler may submit the same `scsi_cmnd` again before its lifecycle is complete. No actual post-lifetime dereference is established. The patch intentionally stops clearing `lrbp->cmd` in SCSI release and mapping-error paths, while device-management paths explicitly initialize it to `NULL`. This indicates corrected ownership bookkeeping rather than evidence that the old code used freed storage. There is no first lifetime-ending release followed by a second operation on the same dangling reference. The repeated-release signal and UAF floors do not apply. The issue is therefore CLASS_C warning or invalid-state behavior, not CLASS_B lifetime corruption. The demonstrated consequence is diagnostic noise. Panic under `panic_on_warn` is conditional and does not independently establish a security-relevant DoS. ImportantCandidate is NO because no corruption, authorization, ownership, or cross-boundary primitive exists. AutoDowngradeAllowed is YES because the available evidence supports automatic treatment as a low-priority correctness fix rather than an Important-class security issue. 5. One-sentence report phrase The UFS driver incorrectly warned when SCSI error handling resubmitted the same command before completion, but the supplied code establishes only command-state bookkeeping and a WARN_ON rather than UAF, memory corruption, or an independently reliable kernel crash. 6. Manual review recommendation NO MANUAL CHECK NEEDED The patch demonstrates a warning caused by valid SCSI recovery behavior and does not establish a security primitive. Reopen for manual review only if additional evidence shows dereference of a freed `scsi_cmnd`, incorrect DMA unmapping, a reproducible kernel crash independent of `panic_on_warn`, or reliable low-privilege control over UFS timeouts. 7. Call-site confidence Call-site confidence: medium ====================================================================== UPSTREAM PATCH SUMMARY ====================================================================== Patch: scsi: ufs: core: Fix handling of lrbp->cmd [ Upstream Commit: f3ee24af62681b942bbd799ac77b90a6d7e1fdb1 Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=f3ee24af62681b942bbd799ac77b90a6d7e1fdb1 Changed files: drivers/ufs/core/ufshcd.c Diff excerpt: Not included in this email. See the upstream URL for the full patch. Full patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=f3ee24af62681b942bbd799ac77b90a6d7e1fdb1 ====================================================================== DETAILED REPORT METHODOLOGY ====================================================================== The original Linux kernel CVE announcement for CVE-2023-53510 can be found here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2023-53510 The original CVE announcement normally does not include a security-level estimate. In particular, it may not contain a CVSS assessment, an impact level, or enough information to determine whether the reported bug is a practically relevant security issue. One purpose of this parallel CVE list is to provide that missing technical and prioritization information. The original goal of the AL-KERNEL project was to prioritize Linux kernel CVE analysis automatically before manual review. The system can also help identify non-security issues that may be suitable for automatic closure. This report was generated by AL-KERNEL, an AI-assisted Linux kernel vulnerability analysis system developed by Alexander Larkin. The first analysis stage combines an autonomous classifier with additional LLM-based analysis. The autonomous classifier runs locally on a CPU and is based on a backpropagation neural network. Together, these mechanisms produce a technical vulnerability description, identify likely weakness types, estimate CVSS severity, and provide input for ActionableScore. Two CVSS estimates are retained because incomplete kernel vulnerability information often permits more than one defensible interpretation: Conservative CVSS vector: AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:L The Best / paranoid CVSS vector: AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H The Best / paranoid CVSS score: 4.7 The conservative vector represents a lower-impact interpretation. The Best/paranoid vector intentionally represents a plausible upper-bound interpretation and should not automatically be treated as demonstrated real-world impact. CVSS may also need to be adjusted for a particular Linux deployment, because actual reachability, privileges, enabled kernel configuration, hardware, namespaces, exposed device nodes, and other environmental conditions can differ significantly between systems. A separate ActionableScore mechanism evaluates practical remediation urgency. Its analysis may include reachability, attack prerequisites, subsystem exposure, memory-corruption characteristics, denial-of-service reliability, and possible confidentiality, integrity, or privilege-escalation impact. Conservative ActionableScore: unknown Paranoid ActionableScore: 0 The final base severity is taken directly from the second tab-separated field of the AL-KERNEL classification result. ActionableScore does not replace or independently override that final AL-KERNEL decision, and if ActionableScore adjusted impact level of ALKERNEL, then you would see self-readable flags above like INCREASED_TO_HIGH_BASED_ON_ACTIONABLESCOREHIGHEREQTHAN7. For an AL-KERNEL result of MODERATE, this report uses the following additional presentation split: ActionableScore below 5 -> MODERATE REGULAR ActionableScore 5 or more -> MODERATE 7.0 The distinction between MODERATE REGULAR and MODERATE 7.0 makes it possible to identify Moderate issues that should receive manual analysis and fixes before lower-priority MODERATE REGULAR issues. In many cases, MODERATE REGULAR fixes may wait for a later rebase or routine update. There is one override in which MODERATE REGULAR becomes MODERATE 7.0 even when the ActionableScore is below 5. When the AL-KERNEL result contains the KPANIC flag, a MODERATE result is always presented as MODERATE 7.0. The KPANIC flag selected with few regexps without usage of AI at all, so it helps to detect cases when Kernel Crash happens and similar (to filter False-Negative results from the LLM usage). KPANIC indicates that a reliable kernel crash, kernel panic, or similarly serious kernel availability impact was identified by the classification workflow. AL-KERNEL base severity for this report: MODERATE KPANIC detected for this report: NO Published priority for this report (same as in Subject): MODERATE REGULAR These results are intended to support engineering triage. They are machine-generated estimates, and cases marked for manual review should be validated by a human security engineer before final disposition. For more info read docs linked from here: https://kernelcve.org/ (and you can submit you own patch there to generate such a report for non-existant CVE-id yet). Note that in many cases this AI tool selects higher severity, than real is (means you can expect Importants instead of Moderate 7.0 or Moderates 7.0 instead of regular Moderates). If you see such cases, please use reply email interface to add additional manual analyses info to this particular CVE. And please, please, let me know when you see Lows instead of Importants or Important instead of Low (because particular for such cases I need to tune this AI tool to make it better for this one and next similar). My contact email for such notifications is alexanjelausa@gmail.com (and both send reply to CVE record itself too and see "reply" button below for howto reply).