LiveActive security incident?Get immediate response
CVE Record

CVE-2025-38546: atm: clip: Fix memory leak of struct clip_vcc.

In the Linux kernel, the following vulnerability has been resolved: atm: clip: Fix memory leak of struct clip_vcc. ioctl(ATMARP_MKIP) allocates struct clip_vcc and set it to vcc->user_back. The code assumes that vcc_destroy_socket() passes NULL skb to vcc->push() when the socket is close()d, and then clip_push() frees clip_vcc. However, ioctl(ATMARPD_CTRL) sets NULL to vcc->push() in atm_init_atmarp(), resulting in memory leak. Let's serialise two ioctl() by lock_sock() and check vcc->push() in atm_init_atmarp() to prevent memleak.

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

Security readout for executives and security teams

Plain-English summary

CVE-2025-38546 is a Linux kernel memory leak in the ATM CLIP networking code. A specific ioctl sequence can leave allocated kernel memory unreleased. The main business risk is resource exhaustion or instability on systems exposing this legacy networking path, not confirmed remote compromise.

Executive priority

Treat as a targeted kernel maintenance item, not an emergency from current evidence. Patch through normal kernel update cycles, with faster handling for multi-user systems, exposed appliances, or environments using uncommon ATM networking support.

Technical view

The bug is in Linux kernel atm/clip handling. ATMARP_MKIP allocates struct clip_vcc through vcc->user_back, while ATMARPD_CTRL can clear vcc->push in atm_init_atmarp(), preventing the expected close-time free path. The fix serializes the ioctls with lock_sock() and checks vcc->push.

Likely exposure

Exposure appears limited to Linux systems with ATM CLIP support present and reachable by users or services able to invoke the relevant ATM ioctls. The source bundle does not identify affected distributions beyond Linux and Debian LTS advisories.

Exploitation context

The provided sources do not show active exploitation, public exploit code, or KEV listing. The described impact is a memory leak caused by ioctl interaction, so likely abuse would require local or otherwise authorized access to the affected kernel interface.

Researcher notes

Evidence is limited to the CVE description, Linux stable commits, and Debian LTS references. No CVSS, CWE, exploit status, or detailed distribution matrix is provided. Avoid assuming broad internet exposure without confirming ATM ioctl reachability and local kernel configuration.

Mitigation direction

  • Apply Linux kernel or distribution updates containing the referenced stable fixes.
  • Review Debian LTS advisories if running Debian-derived systems.
  • Prioritize systems where ATM or CLIP kernel functionality is enabled.
  • If patching is delayed, check vendor guidance for supported temporary controls.

Validation and detection

  • Inventory Linux kernel versions across servers, appliances, and images.
  • Check whether vendor kernels include fixes for CVE-2025-38546.
  • Identify systems with ATM/CLIP support enabled or loadable.
  • Confirm updated hosts rebooted into the fixed kernel.
Prepared
Confidence
medium
Sources
12

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-2025-38546 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
1ADP providers
11Source 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.

ADP provider summaries

CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2unaffected
LinuxLinux2.6.12, 0, 5.4.296, 5.10.240, 5.15.189, 6.1.146, 6.6.99, 6.12.39, 6.15.7, 6.16affected
Weakness

CWE details

No CWE listed

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