First published: Fri Jan 31 2025(Updated: )
In the Linux kernel, the following vulnerability has been resolved: vsock: prevent null-ptr-deref in vsock_*[has_data|has_space] Recent reports have shown how we sometimes call vsock_*_has_data() when a vsock socket has been de-assigned from a transport (see attached links), but we shouldn't. Previous commits should have solved the real problems, but we may have more in the future, so to avoid null-ptr-deref, we can return 0 (no space, no data available) but with a warning. This way the code should continue to run in a nearly consistent state and have a warning that allows us to debug future problems.
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Software | Affected Version | How to fix |
---|---|---|
Linux Kernel | ||
Linux Kernel | >=5.5<5.15.177 | |
Linux Kernel | >=5.16<6.1.127 | |
Linux Kernel | >=6.2<6.6.74 | |
Linux Kernel | >=6.7<6.12.11 | |
Linux Kernel | =6.13-rc1 | |
Linux Kernel | =6.13-rc2 | |
Linux Kernel | =6.13-rc3 | |
Linux Kernel | =6.13-rc4 | |
Linux Kernel | =6.13-rc5 | |
Linux Kernel | =6.13-rc6 | |
Linux Kernel | =6.13-rc7 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2025-21666 is classified as a moderate severity vulnerability.
To fix CVE-2025-21666, you should update your Linux kernel to the latest stable version that resolves this issue.
CVE-2025-21666 affects Linux kernel versions from 5.5 up to 6.13-rc7.
CVE-2025-21666 addresses a null pointer dereference in the vsock_*[has_data|has_space] functions.
Exploitation of CVE-2025-21666 typically requires local access to the affected system.