LiveActive security incident?Get immediate response
CVE Record

CVE-2023-53207: ublk: fail to recover device if queue setup is interrupted

In the Linux kernel, the following vulnerability has been resolved: ublk: fail to recover device if queue setup is interrupted In ublk_ctrl_end_recovery(), if wait_for_completion_interruptible() is interrupted by signal, queues aren't setup successfully yet, so we have to fail UBLK_CMD_END_USER_RECOVERY, otherwise kernel oops can be triggered.

MediumCVSS 5.5Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This is a local availability issue in the Linux kernel ublk block-device code. A low-privileged local user could trigger a kernel oops if recovery completes after interrupted queue setup. The main business risk is service disruption, not data theft or privilege escalation, based on the supplied CVSS vector.

Executive priority

Treat as moderate priority. Patch through normal kernel maintenance, faster on multi-user or untrusted workload hosts. The expected impact is denial of service through kernel crash behavior, not confirmed data compromise.

Technical view

The flaw is in ublk_ctrl_end_recovery(). If wait_for_completion_interruptible() is interrupted by a signal, queues may remain unset. The kernel must fail UBLK_CMD_END_USER_RECOVERY in that state; otherwise a kernel oops can occur. The supplied references are Linux stable fixes.

Likely exposure

Exposure is most likely on Linux systems using affected kernel versions with ublk available and local users able to reach the relevant recovery path. The source bundle names Linux 6.1, 6.1.43, 6.4.8, and 6.5 data but exact downstream distro exposure requires vendor confirmation.

Exploitation context

No active exploitation is stated in the source bundle, and the CVE is not marked KEV. The CVSS vector is local, low-complexity, low-privilege, no user interaction, with high availability impact and no stated confidentiality or integrity impact.

Researcher notes

Evidence supports a local kernel oops in ublk recovery when queue setup is interrupted. The bundle provides stable commit references but no exploit report, no CWE, and limited affected-version clarity. Validate against upstream and distribution-specific kernel changelogs.

Mitigation direction

  • Update to a kernel containing the referenced stable fixes.
  • Check your Linux distribution advisory for backported fixes and package versions.
  • Prioritize systems where untrusted local users can access ublk functionality.
  • If patching is delayed, review vendor guidance for temporary controls.

Validation and detection

  • Inventory kernel versions and distribution security backport status.
  • Confirm whether ublk is enabled or used on affected hosts.
  • Map local user access on systems exposing ublk functionality.
  • Verify installed kernels include the referenced stable fix commits or distro equivalents.
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-2023-53207 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
Medium
CVSS
5.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

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.

1CVSS vectors
3Timeline events
1ADP providers
4Source links

SSVC decision data

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

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.5CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H1.83.6CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

5.5Medium
CVSS 3.1 vector shape for CVE-2023-53207Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

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

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxc732a852b419fa057b53657e2daaf9433940391c, c732a852b419fa057b53657e2daaf9433940391c, c732a852b419fa057b53657e2daaf9433940391cunaffected
LinuxLinux6.1, 0, 6.1.43, 6.4.8, 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.