CVE-2025-39880
What it is
In the Linux kernel, the following vulnerability has been resolved: libceph: fix invalid accesses to ceph_connection_v1_info There is a place where generic code in messenger.c is reading and another place where it is writing to con->v1 union member without checking that the union member is active (i.e. msgr1 is in use). On 64-bit systems, con->v1.auth_retry overlaps with con->v2.out_iter, so such a read is almost guaranteed to return a bogus value instead of 0 when msgr2 is in use. This ends up being fairly benign because the side effect is just the invalidation of the authorizer and successive fetching of new tickets. con->v1.connect_seq overlaps with con->v2.conn_bufs and the fact that it's being written to can cause more serious consequences, but luckily it's not something that happens often.
At a glance
- Exploitability
- Can be exploited over the network without logging in. High risk of data exposure, data tampering, service disruption.
- Exploit odds
- 0.3% 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.3% in the next 30 days (EPSS).
- Severity: 9.8 CRITICAL (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.3% · EPSS, next 30 days
- Weakness
- CWE-704
- Record status
- Modified
Affected
- Linux Kernel < 5.15.194
- Linux Kernel < 6.1.153
- Linux Kernel < 6.6.107
- Linux Kernel < 6.12.48
- Linux Kernel < 6.16.8
- Linux Kernel 6.17
- Debian Linux 11.0
Attack profile CVSS 3.1 · 9.8
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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-39880.md and follow it. Check whether this project is affected by CVE-2025-39880. 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/23538cfbeed87159a5ac6c61e7a6de3d8d4486a8
- https://git.kernel.org/stable/c/35dbbc3dbf8bccb2d77c68444f42c1e6d2d27983
- https://git.kernel.org/stable/c/591ea9c30737663a471b2bb07b27ddde86b020d5
- https://git.kernel.org/stable/c/6bd8b56899be0b514945f639a89ccafb8f8dfaef
- https://git.kernel.org/stable/c/cdbc9836c7afadad68f374791738f118263c5371
- https://git.kernel.org/stable/c/ea12ab684f8ae8a6da11a22c78d94a79e2163096
References
- https://git.kernel.org/stable/c/23538cfbeed87159a5ac6c61e7a6de3d8d4486a8
- https://git.kernel.org/stable/c/35dbbc3dbf8bccb2d77c68444f42c1e6d2d27983
- https://git.kernel.org/stable/c/591ea9c30737663a471b2bb07b27ddde86b020d5
- https://git.kernel.org/stable/c/6bd8b56899be0b514945f639a89ccafb8f8dfaef
- https://git.kernel.org/stable/c/cdbc9836c7afadad68f374791738f118263c5371
- https://git.kernel.org/stable/c/ea12ab684f8ae8a6da11a22c78d94a79e2163096
- https://lists.debian.org/debian-lts-announce/2025/10/msg00008.html