LiveActive security incident?Get immediate response
CVE Record

CVE-2023-53413: USB: isp116x: fix memory leak with using debugfs_lookup()

In the Linux kernel, the following vulnerability has been resolved: USB: isp116x: fix memory leak with using debugfs_lookup() When calling debugfs_lookup() the result must have dput() called on it, otherwise the memory will leak over time. To make things simpler, just call debugfs_lookup_and_remove() instead which handles all of the logic at once.

MediumCVSS 5.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue is a memory leak in the USB isp116x driver. A local user could trigger repeated leaking over time, potentially exhausting memory and disrupting availability. The sources do not show data theft, integrity impact, or remote exploitation.

Executive priority

Treat as a routine availability-risk kernel update unless affected systems host untrusted local users or critical workloads. It is not currently evidenced as actively exploited, but memory-exhaustion bugs can still cause service disruption.

Technical view

The kernel fix replaces debugfs_lookup() usage with debugfs_lookup_and_remove() because lookup results require dput(); missing that release leaks memory. CVSS 3.1 is 5.5 with local attack vector, low complexity, low privileges, no user interaction, and high availability impact only.

Likely exposure

Exposure is most relevant to systems running affected Linux kernel versions with the isp116x USB driver code present or reachable. The bundle lists Linux as affected but does not identify distributions, kernel configurations, devices, or deployment prevalence.

Exploitation context

The source bundle marks KEV as false and provides no cited evidence of active exploitation. The scoring indicates local, low-privilege exploitation potential focused on availability through memory exhaustion, not confidentiality or integrity compromise.

Researcher notes

Evidence is limited to the CVE description, CVSS vector, affected version data, and kernel stable commit references. The bundle does not provide proof-of-concept details, distro backport status, or runtime prerequisites beyond the vulnerable Linux kernel component.

Mitigation direction

  • Apply a vendor kernel update that includes the referenced stable fixes.
  • Check Linux distribution advisories for CVE-2023-53413 applicability.
  • Prioritize internet-facing or multi-user systems where local users are untrusted.
  • Avoid inventing workarounds; follow kernel or distribution guidance.

Validation and detection

  • Inventory Linux kernel versions across managed hosts.
  • Confirm whether the isp116x driver is built, loaded, or packaged.
  • Verify patched kernels include one of the referenced stable commits.
  • Review monitoring for unexplained memory growth on relevant systems.
Prepared
Confidence
medium
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-53413 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
5Source 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-53413Attack 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
LinuxLinux7c7b971d71e754cdb46d7268749fa2f7064d6df3, 7c7b971d71e754cdb46d7268749fa2f7064d6df3, 7c7b971d71e754cdb46d7268749fa2f7064d6df3, 7c7b971d71e754cdb46d7268749fa2f7064d6df3unaffected
LinuxLinux5.13, 0, 5.15.100, 6.1.18, 6.2.5, 6.3affected
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.