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.
References
Configurations
Configuration 1 (hide)
|
History
No history.
Information
Published : 2025-01-31 12:15
Updated : 2025-11-03 21:19
NVD link : CVE-2025-21666
Mitre link : CVE-2025-21666
CVE.ORG link : CVE-2025-21666
JSON object : View
Products Affected
linux
- linux_kernel
CWE
CWE-476
NULL Pointer Dereference
