BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2025
CVE-2023-53510High confidence

scsi: ufs: core: Fix handling of lrbp->cmd

Linux · Linux

7.8HighCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 9 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:Medium, lowered one band.downgradedsince 5 Aug 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.15% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Linux Linux and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: As exposure requiresRemediation target: Within 365 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 9 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

13 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 9 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.4.4-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.170-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.4.4-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.4.4-1Debian Security Tracker ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gcp-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-hwe-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-intelAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-lowlatency-hwe-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oem-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspi-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-riscvAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

2 current
CVE-2023-53510 · CSAF 2.0 · revision 52 · interimSUSE Product Security TeamCVE-2023-53510
391 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • kernel-default as component of SLES-LTSS-TERADATA 15 SP2
  • kernel-source as component of SLES-LTSS-TERADATA 15 SP2
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • kernel-macros as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • kernel-source as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP4
Summary
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
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
CVE-2023-53510 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: scsi: ufs: core: Fix handling of lrbp->cmd
22 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • kernel-rt as a component of Red Hat Enterprise Linux 9
  • kernel-rt-core as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-core as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-devel as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-devel-matched as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-kvm as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-modules as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-modules-core as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-modules-extra as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-modules-internal as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-modules-partner as a component of Red Hat Enterprise Linux 9
Summary
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
Remediation
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2025-32785

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 9 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

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

What

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

Why

The product calls free() twice on the same memory address.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

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

Why

The product calls free() twice on the same memory address.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
local access → Double Free → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-415 ↗

CWE-415: Double Free. The product calls free() twice on the same memory address.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
CWE-415
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2025-2187Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen und um nicht nähere beschriebene Effekte zu verursachen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20251008Security Bulletin 08 Oct 2025

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 08 Oct 2025, published on 8 October 2025. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0547Multiples vulnérabilités dans le noyau Linux de Debian LTS

nux de Debian LTS. Certaines d'entre elles permettent à un attaquant de provoquer une élévation de privilèges, une atteinte à la confidentialité des données et un déni de service. Solutions Se référer au bulletin de sécurité de l'éditeur pour l'obtention des correctifs (cf. section Documentation). Documentation Bulletin de sécurité Debian LTS msg00004 du 02 mai 2026 https://lists.debian.org/debian-lts-announce/2026/05/msg00004.html Bulletin de sécurité Debian LTS msg00005 du 02 mai 2026 https://lists.debian.org/debian-lts-announce/2026/05/msg00005.html Référence CVE CVE-2023-53228 https://www.cve.org/CVERecord?id=CVE-2023-53228 Référence CVE CVE-2023-53510 https://www.cve.org/CVERecord?id=CVE-2023-53510 Référence CVE CVE-2023-53545 https://www.cve.org/CVERecord?id=CVE-2023-53545 Référence CVE CVE-2024-47736 https://www.cve.org/CVERecord?id=CVE-2024-47736 Référence CVE CVE-2024-47809 https://www.cve.org/CVERecord?id=CVE-2024-47809 Référence CVE CVE-2024-49998 https://www.cve.org/CVERecord?id=CVE-2024-49998 Référence CVE CVE-2024-50298 https://www.cve.org/CVERecord?id=CVE-2024-50298 Référence CVE CVE-2024-56719 https://www.cve.org/CVERecord?id=CVE-2024-56719 Référence CVE CVE-2025-21676 https://www.cve.org/CVERecord?id=CVE-2025-21676 Référence CVE CVE-2025-21682 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0548Multiples vulnérabilités dans le noyau Linux de Debian

yau Linux de Debian. Certaines d'entre elles permettent à un attaquant de provoquer une élévation de privilèges, une atteinte à la confidentialité des données et un déni de service. Solutions Se référer au bulletin de sécurité de l'éditeur pour l'obtention des correctifs (cf. section Documentation). Documentation Bulletin de sécurité Debian msg00148 du 30 avril 2026 https://lists.debian.org/debian-security-announce/2026/msg00148.html Bulletin de sécurité Debian msg00154 du 01 mai 2026 https://lists.debian.org/debian-security-announce/2026/msg00154.html Référence CVE CVE-2023-53228 https://www.cve.org/CVERecord?id=CVE-2023-53228 Référence CVE CVE-2023-53510 https://www.cve.org/CVERecord?id=CVE-2023-53510 Référence CVE CVE-2023-53545 https://www.cve.org/CVERecord?id=CVE-2023-53545 Référence CVE CVE-2024-14027 https://www.cve.org/CVERecord?id=CVE-2024-14027 Référence CVE CVE-2024-47736 https://www.cve.org/CVERecord?id=CVE-2024-47736 Référence CVE CVE-2024-47809 https://www.cve.org/CVERecord?id=CVE-2024-47809 Référence CVE CVE-2024-49998 https://www.cve.org/CVERecord?id=CVE-2024-49998 Référence CVE CVE-2024-50298 https://www.cve.org/CVERecord?id=CVE-2024-50298 Référence CVE CVE-2024-56719 https://www.cve.org/CVERecord?id=CVE-2024-56719 Référence CVE CVE-2025-21676 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0326Multiples vulnérabilités dans les produits VMware

d?id=CVE-2023-53438 Référence CVE CVE-2023-53447 https://www.cve.org/CVERecord?id=CVE-2023-53447 Référence CVE CVE-2023-53452 https://www.cve.org/CVERecord?id=CVE-2023-53452 Référence CVE CVE-2023-53460 https://www.cve.org/CVERecord?id=CVE-2023-53460 Référence CVE CVE-2023-53466 https://www.cve.org/CVERecord?id=CVE-2023-53466 Référence CVE CVE-2023-53478 https://www.cve.org/CVERecord?id=CVE-2023-53478 Référence CVE CVE-2023-53483 https://www.cve.org/CVERecord?id=CVE-2023-53483 Référence CVE CVE-2023-53491 https://www.cve.org/CVERecord?id=CVE-2023-53491 Référence CVE CVE-2023-53509 https://www.cve.org/CVERecord?id=CVE-2023-53509 Référence CVE CVE-2023-53510 https://www.cve.org/CVERecord?id=CVE-2023-53510 Référence CVE CVE-2023-53520 https://www.cve.org/CVERecord?id=CVE-2023-53520 Référence CVE CVE-2023-53529 https://www.cve.org/CVERecord?id=CVE-2023-53529 Référence CVE CVE-2023-53538 https://www.cve.org/CVERecord?id=CVE-2023-53538 Référence CVE CVE-2023-53539 https://www.cve.org/CVERecord?id=CVE-2023-53539 Référence CVE CVE-2023-53540 https://www.cve.org/CVERecord?id=CVE-2023-53540 Référence CVE CVE-2023-53544 https://www.cve.org/CVERecord?id=CVE-2023-53544 Référence CVE CVE-2023-53545 https://www.cve.org/CVERecord?id=CVE-2023-53545 Référence CVE CVE-2023-53547 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0316Multiples vulnérabilités dans les produits VMware

d?id=CVE-2023-53438 Référence CVE CVE-2023-53447 https://www.cve.org/CVERecord?id=CVE-2023-53447 Référence CVE CVE-2023-53452 https://www.cve.org/CVERecord?id=CVE-2023-53452 Référence CVE CVE-2023-53460 https://www.cve.org/CVERecord?id=CVE-2023-53460 Référence CVE CVE-2023-53466 https://www.cve.org/CVERecord?id=CVE-2023-53466 Référence CVE CVE-2023-53478 https://www.cve.org/CVERecord?id=CVE-2023-53478 Référence CVE CVE-2023-53483 https://www.cve.org/CVERecord?id=CVE-2023-53483 Référence CVE CVE-2023-53491 https://www.cve.org/CVERecord?id=CVE-2023-53491 Référence CVE CVE-2023-53509 https://www.cve.org/CVERecord?id=CVE-2023-53509 Référence CVE CVE-2023-53510 https://www.cve.org/CVERecord?id=CVE-2023-53510 Référence CVE CVE-2023-53520 https://www.cve.org/CVERecord?id=CVE-2023-53520 Référence CVE CVE-2023-53529 https://www.cve.org/CVERecord?id=CVE-2023-53529 Référence CVE CVE-2023-53538 https://www.cve.org/CVERecord?id=CVE-2023-53538 Référence CVE CVE-2023-53539 https://www.cve.org/CVERecord?id=CVE-2023-53539 Référence CVE CVE-2023-53540 https://www.cve.org/CVERecord?id=CVE-2023-53540 Référence CVE CVE-2023-53544 https://www.cve.org/CVERecord?id=CVE-2023-53544 Référence CVE CVE-2023-53545 https://www.cve.org/CVERecord?id=CVE-2023-53545 Référence CVE CVE-2023-53547 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-1032Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2023-53493 Référence CVE CVE-2023-53495 https://www.cve.org/CVERecord?id=CVE-2023-53495 Référence CVE CVE-2023-53496 https://www.cve.org/CVERecord?id=CVE-2023-53496 Référence CVE CVE-2023-53500 https://www.cve.org/CVERecord?id=CVE-2023-53500 Référence CVE CVE-2023-53501 https://www.cve.org/CVERecord?id=CVE-2023-53501 Référence CVE CVE-2023-53504 https://www.cve.org/CVERecord?id=CVE-2023-53504 Référence CVE CVE-2023-53505 https://www.cve.org/CVERecord?id=CVE-2023-53505 Référence CVE CVE-2023-53507 https://www.cve.org/CVERecord?id=CVE-2023-53507 Référence CVE CVE-2023-53508 https://www.cve.org/CVERecord?id=CVE-2023-53508 Référence CVE CVE-2023-53510 https://www.cve.org/CVERecord?id=CVE-2023-53510 Référence CVE CVE-2023-53515 https://www.cve.org/CVERecord?id=CVE-2023-53515 Référence CVE CVE-2023-53516 https://www.cve.org/CVERecord?id=CVE-2023-53516 Référence CVE CVE-2023-53518 https://www.cve.org/CVERecord?id=CVE-2023-53518 Référence CVE CVE-2023-53519 https://www.cve.org/CVERecord?id=CVE-2023-53519 Référence CVE CVE-2023-53520 https://www.cve.org/CVERecord?id=CVE-2023-53520 Référence CVE CVE-2023-53523 https://www.cve.org/CVERecord?id=CVE-2023-53523 Référence CVE CVE-2023-53526 https://www.cve.org/CVERecord?id=CVE-2023-53526 Référence CVE CVE-2023-53527 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-1009Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2023-53493 Référence CVE CVE-2023-53495 https://www.cve.org/CVERecord?id=CVE-2023-53495 Référence CVE CVE-2023-53496 https://www.cve.org/CVERecord?id=CVE-2023-53496 Référence CVE CVE-2023-53500 https://www.cve.org/CVERecord?id=CVE-2023-53500 Référence CVE CVE-2023-53501 https://www.cve.org/CVERecord?id=CVE-2023-53501 Référence CVE CVE-2023-53504 https://www.cve.org/CVERecord?id=CVE-2023-53504 Référence CVE CVE-2023-53505 https://www.cve.org/CVERecord?id=CVE-2023-53505 Référence CVE CVE-2023-53507 https://www.cve.org/CVERecord?id=CVE-2023-53507 Référence CVE CVE-2023-53508 https://www.cve.org/CVERecord?id=CVE-2023-53508 Référence CVE CVE-2023-53510 https://www.cve.org/CVERecord?id=CVE-2023-53510 Référence CVE CVE-2023-53515 https://www.cve.org/CVERecord?id=CVE-2023-53515 Référence CVE CVE-2023-53516 https://www.cve.org/CVERecord?id=CVE-2023-53516 Référence CVE CVE-2023-53518 https://www.cve.org/CVERecord?id=CVE-2023-53518 Référence CVE CVE-2023-53519 https://www.cve.org/CVERecord?id=CVE-2023-53519 Référence CVE CVE-2023-53520 https://www.cve.org/CVERecord?id=CVE-2023-53520 Référence CVE CVE-2023-53523 https://www.cve.org/CVERecord?id=CVE-2023-53523 Référence CVE CVE-2023-53526 https://www.cve.org/CVERecord?id=CVE-2023-53526 Référence CVE CVE-2023-53527 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0921Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2023-53499 Référence CVE CVE-2023-53500 https://www.cve.org/CVERecord?id=CVE-2023-53500 Référence CVE CVE-2023-53501 https://www.cve.org/CVERecord?id=CVE-2023-53501 Référence CVE CVE-2023-53504 https://www.cve.org/CVERecord?id=CVE-2023-53504 Référence CVE CVE-2023-53505 https://www.cve.org/CVERecord?id=CVE-2023-53505 Référence CVE CVE-2023-53506 https://www.cve.org/CVERecord?id=CVE-2023-53506 Référence CVE CVE-2023-53507 https://www.cve.org/CVERecord?id=CVE-2023-53507 Référence CVE CVE-2023-53508 https://www.cve.org/CVERecord?id=CVE-2023-53508 Référence CVE CVE-2023-53509 https://www.cve.org/CVERecord?id=CVE-2023-53509 Référence CVE CVE-2023-53510 https://www.cve.org/CVERecord?id=CVE-2023-53510 Référence CVE CVE-2023-53512 https://www.cve.org/CVERecord?id=CVE-2023-53512 Référence CVE CVE-2023-53513 https://www.cve.org/CVERecord?id=CVE-2023-53513 Référence CVE CVE-2023-53515 https://www.cve.org/CVERecord?id=CVE-2023-53515 Référence CVE CVE-2023-53516 https://www.cve.org/CVERecord?id=CVE-2023-53516 Référence CVE CVE-2023-53518 https://www.cve.org/CVERecord?id=CVE-2023-53518 Référence CVE CVE-2023-53519 https://www.cve.org/CVERecord?id=CVE-2023-53519 Référence CVE CVE-2023-53520 https://www.cve.org/CVERecord?id=CVE-2023-53520 Référence CVE CVE-2023-53521 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0895Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2023-53499 Référence CVE CVE-2023-53500 https://www.cve.org/CVERecord?id=CVE-2023-53500 Référence CVE CVE-2023-53501 https://www.cve.org/CVERecord?id=CVE-2023-53501 Référence CVE CVE-2023-53504 https://www.cve.org/CVERecord?id=CVE-2023-53504 Référence CVE CVE-2023-53505 https://www.cve.org/CVERecord?id=CVE-2023-53505 Référence CVE CVE-2023-53506 https://www.cve.org/CVERecord?id=CVE-2023-53506 Référence CVE CVE-2023-53507 https://www.cve.org/CVERecord?id=CVE-2023-53507 Référence CVE CVE-2023-53508 https://www.cve.org/CVERecord?id=CVE-2023-53508 Référence CVE CVE-2023-53509 https://www.cve.org/CVERecord?id=CVE-2023-53509 Référence CVE CVE-2023-53510 https://www.cve.org/CVERecord?id=CVE-2023-53510 Référence CVE CVE-2023-53511 https://www.cve.org/CVERecord?id=CVE-2023-53511 Référence CVE CVE-2023-53512 https://www.cve.org/CVERecord?id=CVE-2023-53512 Référence CVE CVE-2023-53515 https://www.cve.org/CVERecord?id=CVE-2023-53515 Référence CVE CVE-2023-53516 https://www.cve.org/CVERecord?id=CVE-2023-53516 Référence CVE CVE-2023-53518 https://www.cve.org/CVERecord?id=CVE-2023-53518 Référence CVE CVE-2023-53519 https://www.cve.org/CVERecord?id=CVE-2023-53519 Référence CVE CVE-2023-53520 https://www.cve.org/CVERecord?id=CVE-2023-53520 Référence CVE CVE-2023-53521 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2025-025450LinuxのLinux Kernelにおける二重解放に関する脆弱性

Linuxカーネルのscsi: ufs: coreにおいて、ufshcd_queuecommand()関数がSCSIコマンドの完了前に2回連続で呼び出される可能性があり、古いlrbp-cmdの値を参照したりエラーパスでクリアしたりして警告が発生していました。この問題は、コマンド送信時にlrbp-cmdの値を確認せず、クリアもしないようにし、またufshcd_release_scsi_cmd()関数でもlrbp-cmdをクリアしないよう修正することで解決されました。この修正によって、タイムアウト時の警告メッセージの発生を防いでいます。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
Linux: < 3.12, 6.1.167 ≤ 6.1.*, 6.3.13 ≤ 6.3.*, 6.4.4 ≤ 6.4.*, 6.5 ≤ *
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 1 Oct 2025 · Last source change 5 Aug 2026, 09:14 UTC · CWE-415 · Double Free

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2025-32785
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceNIST NVD
NVD statusNVD modified after enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2025-32785↗Vendor CSAF · SUSE Product Security Team↗CVE authority or vendor reference↗Patch or update reference↗Patch or update reference↗Patch or update reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2023-53510 · cve.blacktree.nl