CVE-2025-38190
What it is
In the Linux kernel, the following vulnerability has been resolved: atm: Revert atm_account_tx() if copy_from_iter_full() fails. In vcc_sendmsg(), we account skb->truesize to sk->sk_wmem_alloc by atm_account_tx(). It is expected to be reverted by atm_pop_raw() later called by vcc->dev->ops->send(vcc, skb). However, vcc_sendmsg() misses the same revert when copy_from_iter_full() fails, and then we will leak a socket. Let's factorise the revert part as atm_return_tx() and call it in the failure path. Note that the corresponding sk_wmem_alloc operation can be found in alloc_tx() as of the blamed commit. $ git blame -L:alloc_tx net/atm/common.c c55fa3cccbc2c~
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of service disruption.
- Exploit odds
- 0.2% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.2% in the next 30 days (EPSS).
- Severity: 5.5 MEDIUM (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.2% · EPSS, next 30 days
- Record status
- Analyzed
Affected
- Linux Kernel < 5.4.295
- Linux Kernel < 5.10.239
- Linux Kernel < 5.15.186
- Linux Kernel < 6.1.142
- Linux Kernel < 6.6.95
- Linux Kernel < 6.12.35
- Linux Kernel < 6.15.4
- Linux Kernel 2.6.12
Attack profile CVSS 3.1 · 5.5
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2025-38190.md and follow it. Check whether this project is affected by CVE-2025-38190. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/2252c539c43f9a1431a7e8b34e3c18e9dd77a96d
- https://git.kernel.org/stable/c/287b4f085d2ca3375cf1ee672af27410c64777e8
- https://git.kernel.org/stable/c/3902205eadf35db59dbc2186c2a98b9e6182efa5
- https://git.kernel.org/stable/c/3d828519bd69bfcaabdd942a872679617ef06739
- https://git.kernel.org/stable/c/5e0d00992118e234ebf29d5145c1cc920342777e
- https://git.kernel.org/stable/c/7851263998d4269125fd6cb3fdbfc7c6db853859
- https://git.kernel.org/stable/c/7d6bc28cfe5c8e3a279b4b4bdeed6698b2702685
- https://git.kernel.org/stable/c/c12430edd92fd49a4800b0f3fb395b50cb16bcc1
References
- https://git.kernel.org/stable/c/2252c539c43f9a1431a7e8b34e3c18e9dd77a96d
- https://git.kernel.org/stable/c/287b4f085d2ca3375cf1ee672af27410c64777e8
- https://git.kernel.org/stable/c/3902205eadf35db59dbc2186c2a98b9e6182efa5
- https://git.kernel.org/stable/c/3d828519bd69bfcaabdd942a872679617ef06739
- https://git.kernel.org/stable/c/5e0d00992118e234ebf29d5145c1cc920342777e
- https://git.kernel.org/stable/c/7851263998d4269125fd6cb3fdbfc7c6db853859
- https://git.kernel.org/stable/c/7d6bc28cfe5c8e3a279b4b4bdeed6698b2702685
- https://git.kernel.org/stable/c/c12430edd92fd49a4800b0f3fb395b50cb16bcc1
- https://lists.debian.org/debian-lts-announce/2025/10/msg00007.html
- https://lists.debian.org/debian-lts-announce/2025/10/msg00008.html