CVE-2025-38546: Linux kernel · atm: clip: Fix memory leak of struct clip_vcc.
Affects Linux kernelSource GCVE Database
Not known to be exploited · CVSS 5.5 Medium · fixed in 5.15.0-1092.99~20.04.1 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 5.15.0-1092.99~20.04.1, 5.15.0-1096.105~20.04.1, 5.15.0-1092.101~20.04.1 +58
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 16 Aug 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Patches and advisories
- ubuntu.com/security/notices/USN-7879-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7879-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7880-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7879-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-7879-4 (opens in a new tab)
- ubuntu.com/security/notices/USN-7934-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8028-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8028-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-8031-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8028-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-8028-4 (opens in a new tab)
- ubuntu.com/security/notices/USN-8028-5 (opens in a new tab)
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 25.10linux-azure-fdepkg:deb/ubuntu/linux-azure-fde?arch=source&distro=questingOther threats | Affected
| Fixed in– |
Ubuntu 24.04 LTSlinuxpkg:deb/ubuntu/linux?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-awspkg:deb/ubuntu/linux-aws?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-aws-6.14pkg:deb/ubuntu/linux-aws-6.14?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-azurepkg:deb/ubuntu/linux-azure?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-azure-6.11pkg:deb/ubuntu/linux-azure-6.11?arch=source&distro=nobleOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
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
- ubuntu.com/security/CVE-2025-38546 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2025-38546 (opens in a new tab)
- git.kernel.org/linus/62dba28275a9a3104d4e33595c7b3328d4032d8d (opens in a new tab)
- git.kernel.org/stable/c/0c17ff462d98c997d707ee5cf4e4a9b1b52b9d90 (opens in a new tab)
- git.kernel.org/stable/c/1c075e88d5859a2c6b43b27e0e46fb281cef8039 (opens in a new tab)
- git.kernel.org/stable/c/1fb9fb5a4b5cec2d56e26525ef8c519de858fa60 (opens in a new tab)
- git.kernel.org/stable/c/2fb37ab3226606cbfc9b2b6f9e301b0b735734c5 (opens in a new tab)
- git.kernel.org/stable/c/62dba28275a9a3104d4e33595c7b3328d4032d8d (opens in a new tab)
- git.kernel.org/stable/c/9e4dbeee56f614e3f1e166e5d0655a999ea185ef (opens in a new tab)
- git.kernel.org/stable/c/9f771816f14da6d6157a8c30069091abf6b566fb (opens in a new tab)
- git.kernel.org/stable/c/cb2e4a2f8f268d8fba6662f663a2e57846f14a8d (opens in a new tab)
- ubuntu.com/security/notices/USN-7879-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7879-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7880-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7879-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-7879-4 (opens in a new tab)
- ubuntu.com/security/notices/USN-7934-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8028-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8028-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-8031-1 (opens in a new tab)