LiveActive security incident?Get immediate response
CVE Record

CVE-2023-53330: caif: fix memory leak in cfctrl_linkup_request()

In the Linux kernel, the following vulnerability has been resolved: caif: fix memory leak in cfctrl_linkup_request() When linktype is unknown or kzalloc failed in cfctrl_linkup_request(), pkt is not released. Add release process to error path.

MediumCVSS 5.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-53330 is a Linux kernel memory leak in the CAIF networking code. A local, low-privileged actor could trigger kernel memory loss that may affect system availability. The cited sources do not report data theft, integrity impact, or active exploitation.

Executive priority

Treat this as routine but real availability risk. It should enter normal kernel patch cycles, with faster action on multi-user systems, shared workload hosts, and environments where local privilege boundaries matter.

Technical view

The issue is in cfctrl_linkup_request() in the Linux kernel CAIF subsystem. On an unknown link type or kzalloc failure, pkt was not released, causing a CWE-401 memory leak. The CVSS vector is local, low complexity, low privilege, no user interaction, availability-only impact.

Likely exposure

Exposure is most likely on Linux systems running affected kernels where the CAIF subsystem is present or enabled. The source lists Linux kernel versions and stable commits, but does not identify specific distributions, appliances, or cloud images.

Exploitation context

CISA KEV status is false in the provided bundle. No cited source states active exploitation. The CVSS vector requires local access with low privileges, so remote unauthenticated exploitation is not supported by the provided evidence.

Researcher notes

Evidence supports a memory leak fix in Linux CAIF error handling, not code execution or privilege escalation. The affected-version data in the bundle is broad and commit-oriented, so distribution-level exposure should be validated through vendor kernel mapping.

Mitigation direction

  • Update affected Linux kernels through the relevant vendor or distribution channel.
  • Confirm the deployed kernel includes the referenced stable fix for cfctrl_linkup_request().
  • Prioritize systems where untrusted local users or workloads can run code.
  • If patching is delayed, check vendor guidance; sources do not name a workaround.

Validation and detection

  • Inventory Linux kernel versions across servers, endpoints, containers hosts, and appliances.
  • Compare deployed kernels with vendor advisories or the referenced stable commits.
  • Check whether CAIF support is built, loaded, or relevant in your environment.
  • After updating, verify the running kernel is the patched version.
Prepared
Confidence
high
Sources
10

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-53330 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-53330Attack 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
LinuxLinuxb482cd2053e3b90a7b33a78c63cdb6badf2ec383, b482cd2053e3b90a7b33a78c63cdb6badf2ec383, b482cd2053e3b90a7b33a78c63cdb6badf2ec383, b482cd2053e3b90a7b33a78c63cdb6badf2ec383, b482cd2053e3b90a7b33a78c63cdb6badf2ec383, b482cd2053e3b90a7b33a78c63cdb6badf2ec383, b482cd2053e3b90a7b33a78c63cdb6badf2ec383, b482cd2053e3b90a7b33a78c63cdb6badf2ec383unaffected
LinuxLinux2.6.35, 0, 4.14.303, 4.19.270, 5.4.229, 5.10.163, 5.15.87, 6.0.19, 6.1.5, 6.2affected
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.