LiveActive security incident?Get immediate response
CVE Record

CVE-2023-53436: scsi: snic: Fix possible memory leak if device_add() fails

In the Linux kernel, the following vulnerability has been resolved: scsi: snic: Fix possible memory leak if device_add() fails If device_add() returns error, the name allocated by dev_set_name() needs be freed. As the comment of device_add() says, put_device() should be used to give up the reference in the error path. So fix this by calling put_device(), then the name can be freed in kobject_cleanp().

MediumCVSS 5.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-53436 is a Linux kernel memory leak in the snic SCSI driver error path. If adding a device fails, allocated naming memory may not be released. The business risk is primarily local availability impact, not data theft or remote compromise, based on the provided CVSS vector.

Executive priority

Treat as routine but timely kernel maintenance. Prioritize storage hosts and shared infrastructure where local availability loss would disrupt operations. No source provided evidence of remote exploitation, data exposure, or active attacks.

Technical view

The flaw is CWE-401 in the Linux kernel snic driver. When device_add() fails after dev_set_name(), the error path should call put_device() so cleanup frees the allocated name through kobject cleanup. CVSS 3.1 is 5.5 with local attack vector, low privileges, no confidentiality or integrity impact, and high availability impact.

Likely exposure

Exposure is most likely on Linux systems running affected kernel versions with the snic SCSI driver present or in use. The source bundle lists Linux as affected and provides multiple stable kernel commit references. Distribution packaging may change exact exposure, so validate through vendor kernel advisories.

Exploitation context

The provided sources do not show active exploitation, and KEV is false. The CVSS vector indicates local access with low privileges and no user interaction. Evidence supports a potential availability issue through memory leakage, but does not provide exploit status or practical trigger details.

Researcher notes

The fix is narrowly scoped to snic device-add failure cleanup. Assessment should focus on affected kernel lineage, distro backports, and whether the snic driver can be reached on deployed systems. Do not assume broader SCSI subsystem exposure without additional evidence.

Mitigation direction

  • Apply Linux kernel updates containing the referenced stable fixes.
  • Check your distribution advisory for exact fixed package versions.
  • Prioritize hosts using the snic SCSI driver or related storage hardware.
  • Use vendor guidance if kernel backport status is unclear.

Validation and detection

  • Inventory kernel versions across Linux hosts.
  • Identify systems where the snic SCSI driver is available or loaded.
  • Compare installed kernels with distribution fixed versions or referenced stable commits.
  • Confirm patched source handles device_add() failure with put_device().
Prepared
Confidence
high
Sources
6

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.

cwe · low confidence lookup

CWE-401: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-53436 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
9Source 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-53436Attack 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
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxc8806b6c9e824f47726f2a9b7fbbe7ebf19306fa, c8806b6c9e824f47726f2a9b7fbbe7ebf19306fa, c8806b6c9e824f47726f2a9b7fbbe7ebf19306fa, c8806b6c9e824f47726f2a9b7fbbe7ebf19306fa, c8806b6c9e824f47726f2a9b7fbbe7ebf19306fa, c8806b6c9e824f47726f2a9b7fbbe7ebf19306fa, c8806b6c9e824f47726f2a9b7fbbe7ebf19306fa, c8806b6c9e824f47726f2a9b7fbbe7ebf19306faunaffected
LinuxLinux4.2, 0, 4.14.323, 4.19.292, 5.4.254, 5.10.191, 5.15.127, 6.1.46, 6.4.11, 6.5affected
Weakness

CWE details

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

CWE-401 · source CWE mapping

Missing Release of Memory after Effective Lifetime

Missing Release of Memory after Effective Lifetime represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.