7.8
HIGH
CVE-2024-43873
Linux Kernel Vhost vsock Sequence Packet Allow Vulnerability
Description

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

INFO

Published Date :

Aug. 21, 2024, 1:15 a.m.

Last Modified :

Sept. 3, 2024, 1:35 p.m.

Source :

416baaa9-dc9f-4396-8d5f-8c081fb06d67

Remotely Exploitable :

No

Impact Score :

5.9

Exploitability Score :

1.8
Affected Products

The following products are affected by CVE-2024-43873 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

ID Vendor Product Action
1 Linux linux_kernel

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2024-43873 vulnerability anywhere in the article.

The following table lists the changes that have been made to the CVE-2024-43873 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • Initial Analysis by [email protected]

    Sep. 03, 2024

    Action Type Old Value New Value
    Added CVSS V3.1 NIST AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
    Changed Reference Type https://git.kernel.org/stable/c/1e1fdcbdde3b7663e5d8faeb2245b9b151417d22 No Types Assigned https://git.kernel.org/stable/c/1e1fdcbdde3b7663e5d8faeb2245b9b151417d22 Patch
    Changed Reference Type https://git.kernel.org/stable/c/3062cb100787a9ddf45de30004b962035cd497fb No Types Assigned https://git.kernel.org/stable/c/3062cb100787a9ddf45de30004b962035cd497fb Patch
    Changed Reference Type https://git.kernel.org/stable/c/30bd4593669443ac58515e23557dc8cef70d8582 No Types Assigned https://git.kernel.org/stable/c/30bd4593669443ac58515e23557dc8cef70d8582 Patch
    Changed Reference Type https://git.kernel.org/stable/c/ea558f10fb05a6503c6e655a1b7d81fdf8e5924c No Types Assigned https://git.kernel.org/stable/c/ea558f10fb05a6503c6e655a1b7d81fdf8e5924c Patch
    Changed Reference Type https://git.kernel.org/stable/c/eab96e8716cbfc2834b54f71cc9501ad4eec963b No Types Assigned https://git.kernel.org/stable/c/eab96e8716cbfc2834b54f71cc9501ad4eec963b Patch
    Added CWE NIST CWE-909
    Added CPE Configuration OR *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.14 up to (excluding) 5.15.165 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.16 up to (excluding) 6.1.103 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.2 up to (excluding) 6.6.44 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.7 up to (excluding) 6.10.3
  • CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67

    Aug. 21, 2024

    Action Type Old Value New Value
    Added Description 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
    Added Reference kernel.org https://git.kernel.org/stable/c/ea558f10fb05a6503c6e655a1b7d81fdf8e5924c [No types assigned]
    Added Reference kernel.org https://git.kernel.org/stable/c/3062cb100787a9ddf45de30004b962035cd497fb [No types assigned]
    Added Reference kernel.org https://git.kernel.org/stable/c/30bd4593669443ac58515e23557dc8cef70d8582 [No types assigned]
    Added Reference kernel.org https://git.kernel.org/stable/c/eab96e8716cbfc2834b54f71cc9501ad4eec963b [No types assigned]
    Added Reference kernel.org https://git.kernel.org/stable/c/1e1fdcbdde3b7663e5d8faeb2245b9b151417d22 [No types assigned]
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.
CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorizes the common flaws or weaknesses that can lead to vulnerabilities. CVE-2024-43873 is associated with the following CWEs:

Common Attack Pattern Enumeration and Classification (CAPEC)

Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2024-43873 weaknesses.

CVSS31 - Vulnerability Scoring System
Attack Vector
Attack Complexity
Privileges Required
User Interaction
Scope
Confidentiality
Integrity
Availability