dbcve.org
Linux KernelOperating system · Linux

CVE-2024-43873

HIGH · 7.8 CVSS v3.1 Published 2024-08-21
Fix available
A fix is available. Upgrade to 5.15.165 / 6.1.103 or later.
See remediation →
80/100
Remediation priority · High
Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis

A detailed technical summary for this CVE is being prepared.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Linux KernelOperating system
Affected:>= 5.14, < 5.15.165>= 5.16, < 6.1.103>= 6.2, < 6.6.44>= 6.7, < 6.10.3

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 5.15.165 / 6.1.103 / 6.6.44 or later
Fixed in 5.15.1656.1.1036.6.44
Vendor patch git.kernel.org →
Recommended fix High confidence

Kernel version 5.15.165+ (for 5.15 branch), 6.1.103+ (for 6.1 branch), 6.6.44+ (for 6.6 branch), or 6.10.3+ (for 6.10 branch) - choose the appropriate version based on the current kernel branch

  1. 1. Identify the current running kernel version using 'uname -r'
  2. 2. Determine which kernel branch (5.15.x, 6.1.x, 6.6.x, or 6.7+/6.10.x) the system is running
  3. 3. For systems on 5.14.x to 5.15.x branch: upgrade to kernel version 5.15.165 or later
  4. 4. For systems on 5.16.x to 6.1.x branch: upgrade to kernel version 6.1.103 or later
  5. 5. For systems on 6.2.x to 6.6.x branch: upgrade to kernel version 6.6.44 or later
  6. 6. For systems on 6.7.x to 6.10.x branch: upgrade to kernel version 6.10.3 or later
  7. 7. Reboot the system to load the updated kernel
  8. 8. Verify the fix is applied by checking 'git log --oneline' for commit 1e1fdcbdde3b7663e5d8faeb2245b9b151417d22 in the new kernel source or by confirming the seqpacket_allow initialization in the vhost/vsock module
Caveat Kernel upgrades may introduce compatibility changes with proprietary drivers or specific hardware configurations; ensure dependent kernel modules are compatible with the new version

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-43873 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-43873 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data