In the Linux kernel, the following vulnerability has been resolved:
vhost/vsock: always initialize seqpacket_allow
There are two issues around seqpacket_allow:
1. seqpacket_allow is not initialized when socket is
created. Thus if features are never set, it will be
read uninitialized.
2. if VIRTIO_VSOCK_F_SEQPACKET is set and then cleared,
then seqpacket_allow will not be cleared appropriately
(existing apps I know about don't usually do this but
it's legal and there's no way to be sure no one relies
on this).
To fix:
- initialize seqpacket_allow after allocation
- set it unconditionally in set_features
References
Configurations
Configuration 1 (hide)
|
History
03 Sep 2024, 13:35
Type | Values Removed | Values Added |
---|---|---|
CWE | CWE-909 | |
CVSS |
v2 : v3 : |
v2 : unknown
v3 : 7.8 |
Summary |
|
|
First Time |
Linux linux Kernel
Linux |
|
CPE | cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | |
References | () https://git.kernel.org/stable/c/1e1fdcbdde3b7663e5d8faeb2245b9b151417d22 - Patch | |
References | () https://git.kernel.org/stable/c/3062cb100787a9ddf45de30004b962035cd497fb - Patch | |
References | () https://git.kernel.org/stable/c/30bd4593669443ac58515e23557dc8cef70d8582 - Patch | |
References | () https://git.kernel.org/stable/c/ea558f10fb05a6503c6e655a1b7d81fdf8e5924c - Patch | |
References | () https://git.kernel.org/stable/c/eab96e8716cbfc2834b54f71cc9501ad4eec963b - Patch |
21 Aug 2024, 01:15
Type | Values Removed | Values Added |
---|---|---|
New CVE |
Information
Published : 2024-08-21 01:15
Updated : 2024-09-03 13:35
NVD link : CVE-2024-43873
Mitre link : CVE-2024-43873
CVE.ORG link : CVE-2024-43873
JSON object : View
Products Affected
linux
- linux_kernel
CWE
CWE-909
Missing Initialization of Resource