Skip to main content
VulnerabilityPublished Updated

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

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in cb2e4a2f8f268d8fba6662f663a2e57846f14a8d : update Linux kernel when convenient.

Data as of 5 Nov 2026, 21:34 UTC

Severity
Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-05.

Patch
Available – fixed in cb2e4a2f8f268d8fba6662f663a2e57846f14a8d, 62dba28275a9a3104d4e33595c7b3328d4032d8d, 9f771816f14da6d6157a8c30069091abf6b566fb +5

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 Aug 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < cb2e4a2f8f268d8fba6662f663a2e57846f14a8d
Fixed in
  • cb2e4a2f8f268d8fba6662f663a2e57846f14a8d
LinuxLinuxAffected
  • ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 62dba28275a9a3104d4e33595c7b3328d4032d8d
Fixed in
  • 62dba28275a9a3104d4e33595c7b3328d4032d8d
LinuxLinuxAffected
  • ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 9f771816f14da6d6157a8c30069091abf6b566fb
Fixed in
  • 9f771816f14da6d6157a8c30069091abf6b566fb
LinuxLinuxAffected
  • ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 9e4dbeee56f614e3f1e166e5d0655a999ea185ef
Fixed in
  • 9e4dbeee56f614e3f1e166e5d0655a999ea185ef
LinuxLinuxAffected
  • ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 2fb37ab3226606cbfc9b2b6f9e301b0b735734c5
Fixed in
  • 2fb37ab3226606cbfc9b2b6f9e301b0b735734c5
LinuxLinuxAffected
  • ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 1fb9fb5a4b5cec2d56e26525ef8c519de858fa60
Fixed in
  • 1fb9fb5a4b5cec2d56e26525ef8c519de858fa60

Description

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.

References

Community reviews

Loading reviews…