LiveActive security incident?Get immediate response
CVE Record

CVE-2023-53521: scsi: ses: Fix slab-out-of-bounds in ses_intf_remove()

In the Linux kernel, the following vulnerability has been resolved: scsi: ses: Fix slab-out-of-bounds in ses_intf_remove() A fix for: BUG: KASAN: slab-out-of-bounds in ses_intf_remove+0x23f/0x270 [ses] Read of size 8 at addr ffff88a10d32e5d8 by task rmmod/12013 When edev->components is zero, accessing edev->component[0] members is wrong.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue is a bounds-checking bug in the SCSI Enclosure Services driver. When an enclosure reports zero components, removal logic may still read component zero, causing an out-of-bounds kernel memory access. The public bundle does not provide CVSS, confirmed impact beyond the bug report, or exploitation evidence.

Executive priority

Treat as a targeted kernel maintenance item until vendor severity is available. Prioritize systems where storage enclosure management is used, but do not escalate as actively exploited based on the supplied evidence.

Technical view

The flaw is in ses_intf_remove() in the kernel SES SCSI driver. The fixed condition prevents reading edev->component[0] when edev->components is zero. The report cites a KASAN slab-out-of-bounds read during rmmod. Stable kernel commit references are provided, but distro mapping is not included.

Likely exposure

Exposure is most likely on Linux systems using the SES SCSI enclosure driver, especially storage servers or systems with enclosure-management hardware. The source bundle lists Linux kernel versions and stable fixes, but does not map exposure to specific distributions, appliances, or default configurations.

Exploitation context

The bundle shows no CISA KEV listing and no cited evidence of active exploitation. The observed trigger is kernel module removal with a zero-component enclosure object. No public exploit path or attacker prerequisites are established in the provided sources.

Researcher notes

Key evidence is a KASAN out-of-bounds read caused by accessing component[0] when components equals zero. Impact, exploitability, and attacker control are not described. Analysis should focus on fixed commits, affected kernel ranges, and downstream distro backports.

Mitigation direction

  • Review vendor or distribution kernel advisories for CVE-2023-53521 applicability.
  • Update to a kernel build containing the referenced stable SES fixes.
  • Prioritize storage hosts using SCSI enclosure management or SES modules.
  • If patching is delayed, follow vendor guidance for reducing SES driver exposure.

Validation and detection

  • Inventory Linux kernel versions on storage and server fleets.
  • Check whether the ses kernel module is present or loaded.
  • Compare running kernels against vendor-fixed releases for this CVE.
  • Review kernel logs for KASAN or slab-out-of-bounds SES messages.
Prepared
Confidence
medium
Sources
10

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-53521 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
9Source 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.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux9927c68864e9c39cc317b4f559309ba29e642168, 9927c68864e9c39cc317b4f559309ba29e642168, 9927c68864e9c39cc317b4f559309ba29e642168, 9927c68864e9c39cc317b4f559309ba29e642168, 9927c68864e9c39cc317b4f559309ba29e642168, 9927c68864e9c39cc317b4f559309ba29e642168, 9927c68864e9c39cc317b4f559309ba29e642168, 9927c68864e9c39cc317b4f559309ba29e642168unaffected
LinuxLinux2.6.25, 0, 4.14.308, 4.19.276, 5.4.235, 5.10.173, 5.15.99, 6.1.16, 6.2.3, 6.3affected
Weakness

CWE details

No CWE listed

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