LiveActive security incident?Get immediate response
CVE Record

CVE-2024-43873: vhost/vsock: always initialize seqpacket_allow

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

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2024-43873 is a Linux kernel vhost/vsock bug where a setting for sequenced-packet support may be read before being initialized or not cleared correctly. The public sources do not describe observed attacks or business impact, so treat this as a kernel maintenance issue for virtualized Linux environments.

Executive priority

Handle through normal kernel patch governance unless local exposure to vhost/vsock is high or vendor advisories rate it more severely. There is no cited evidence of active exploitation, but kernel bugs can have broad operational reach.

Technical view

The flaw is in vhost/vsock handling of seqpacket_allow. The kernel could read the field uninitialized when features were never set, or leave it enabled after VIRTIO_VSOCK_F_SEQPACKET was cleared. The fix initializes seqpacket_allow after allocation and updates it unconditionally in set_features.

Likely exposure

Exposure is most likely on Linux systems using affected kernel versions with vhost/vsock or virtio-vsock functionality in virtualized environments. The source data lists Linux kernel affected versions but does not provide distribution-specific exposure details beyond a Debian LTS advisory.

Exploitation context

The source bundle does not show CISA KEV listing, active exploitation, public exploit use, or a CVSS score. Exploitability and impact are not fully described in the cited sources, so avoid assuming remote exploitation, privilege escalation, or data exposure without vendor confirmation.

Researcher notes

The core issue is state initialization and feature toggling consistency for seqpacket_allow. The public record lacks impact classification, CVSS, CWE, and exploit context. Validation should focus on kernel branch, vendor backports, and whether vsock paths are reachable in the environment.

Mitigation direction

  • Apply vendor kernel updates that include the referenced stable Linux fixes.
  • For Debian LTS systems, review the cited Debian LTS advisory and update accordingly.
  • Prioritize systems running workloads that depend on vhost/vsock or virtio-vsock.
  • If immediate patching is blocked, check vendor guidance for supported configuration mitigations.

Validation and detection

  • Inventory Linux kernel versions across virtualization hosts and guests.
  • Confirm whether vhost/vsock or virtio-vsock functionality is enabled or used.
  • Verify installed kernels include the stable commits referenced for this CVE.
  • Check distribution advisories for backported fixes using vendor package versions.
Prepared
Confidence
medium
Sources
8

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2024-43873 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
2ADP providers
7Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxced7b713711fdd8f99d8d04dc53451441d194c60, ced7b713711fdd8f99d8d04dc53451441d194c60, ced7b713711fdd8f99d8d04dc53451441d194c60, ced7b713711fdd8f99d8d04dc53451441d194c60, ced7b713711fdd8f99d8d04dc53451441d194c60unaffected
LinuxLinux5.14, 0, 5.15.165, 6.1.103, 6.6.44, 6.10.3, 6.11affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.