CVE-2024-43873

HIGHNVD 7.87.8—

7.8

In the Linux kernel, the following vulnerability has been resolved:

vhost/vsock: always initialize seqpacket_allow

There are two issues around seqpacket_allow:

seqpacket_allow is not initialized when socket is

created. Thus if features are never set, it will be read uninitialized.

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

CVSS v3: 7.8
EG Score: 7.8(medium)
EPSS: 7.0%
KEV: Not listed

Published

August 21, 2024

Last Modified

November 3, 2025

References (6)

416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/1e1fdcbdde3b7663e5d8faeb2245b9b151417d22
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/3062cb100787a9ddf45de30004b962035cd497fb
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/30bd4593669443ac58515e23557dc8cef70d8582
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/ea558f10fb05a6503c6e655a1b7d81fdf8e5924c
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/eab96e8716cbfc2834b54f71cc9501ad4eec963b
af854a3a-2127-422b-91ae-364da2661108https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html

Patch Availability(11)

Vendor / Ecosystem	Fixed in / Patch	Released	Source
ubuntu	linux-virtual-hwe-20.04-edge (5.15.0.125.135~20.04.1) @ focal	2026-05-23	ubuntu
ubuntu	linux-tools-aws-lts-22.04 (5.15.0.1072.72) @ jammy	2026-05-23	ubuntu
ubuntu	linux-tools-intel-iotg (5.15.0.1067.67) @ jammy	2026-05-23	ubuntu
ubuntu	linux-tools-azure-lts-22.04 (5.15.0.1075.73) @ jammy	2026-05-23	ubuntu
ubuntu	linux-tools-oracle-edge (6.8.0-1017.18~22.04.1) @ jammy	2026-05-23	ubuntu
ubuntu	linux-tools-azure (6.8.0-1020.23) @ noble	2026-05-23	ubuntu
ubuntu	linux-tools-nvidia-lowlatency-64k (6.8.0-1019.21.1) @ noble	2026-05-23	ubuntu
ubuntu	linux-tools-azure-edge (5.15.0.1078.87~20.04.1) @ focal	2026-05-23	ubuntu
ubuntu	linux-virtual-hwe-22.04-edge (6.8.0-50.51~22.04.1) @ jammy	2026-05-23	ubuntu
ubuntu	linux-tools-gkeop-6.8 (6.8.0-1002.4) @ noble	2026-05-23	ubuntu
redhat	kernel-0:5.14.0-570.12.1.el9_6	2025-05-13	redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

CWE-909

All Vendor Advisories

(12)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 14× in last 7d / 17× in last 30d)

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-05-31 22:30 UTCepss_batch
2026-05-31 22:30 UTCepss_batch
2026-05-31 00:16 UTCepss_batch
2026-05-31 00:15 UTCepss_batch
2026-05-29 13:43 UTCepss_batch
2026-05-28 13:44 UTCepss_batch
2026-05-28 13:44 UTCepss_batch
2026-05-27 13:40 UTCepss_batch
2026-05-27 13:40 UTCepss_batch
2026-05-26 13:43 UTCepss_batch
2026-05-26 13:43 UTCepss_batch
2026-05-26 07:18 UTCepss_batch
2026-05-26 07:18 UTCepss_batch
2026-05-26 07:18 UTCepss_batch
2026-05-23 12:22 UTCEG score recompute
2026-05-23 12:22 UTCVendor advisory
2026-05-23 12:22 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2024-43873?

CVE-2024-43873 is a high vulnerability published on August 21, 2024. 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…

When was CVE-2024-43873 disclosed?

CVE-2024-43873 was first published in the National Vulnerability Database on August 21, 2024, with the most recent update on November 3, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2024-43873 actively exploited?

CVE-2024-43873 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 7.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

What is the CVSS score of CVE-2024-43873?

CVE-2024-43873 has a CVSS v3 base score of 7.8 (NVD).

How do I remediate CVE-2024-43873?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-43873, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-43873

Explore →

Is Your Infrastructure Affected by CVE-2024-43873?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs