BlackTreeIndependent security intelligence

Full vulnerability report · 2026

CVE-2026-53365High confidence

vsock/virtio: fix zerocopy completion for multi-skb sends

Linux · Linux

5.5MediumCVSS 3.1

Recommended action

Within 7 days

Medium technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance.

Patch available

Distribution package intelligence

Ubuntu vendor package status

Canonical’s release and source-package findings are shown separately from local repository availability.

20 package states

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Ubuntu release	Source package	Vendor state	Fixed version	Evidence
Ubuntu 24.04 LTSnoble · standard archive	`linux`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical record ↗Source updated 4 Sept 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-aws`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical record ↗Source updated 4 Sept 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-azure`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical record ↗Source updated 4 Sept 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-azure-fde`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical record ↗Source updated 4 Sept 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-azure-nvidia`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical record ↗Source updated 4 Sept 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-gcp`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical record ↗Source updated 4 Sept 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-gke`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical record ↗Source updated 4 Sept 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-gkeop`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical record ↗Source updated 4 Sept 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-ibm`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical record ↗Source updated 4 Sept 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-lowlatency`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical record ↗Source updated 4 Sept 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-nvidia`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical record ↗Source updated 4 Sept 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-nvidia-lowlatency`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical record ↗Source updated 4 Sept 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-nvidia-tegra`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical record ↗Source updated 4 Sept 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-oem-6.11`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical record ↗Source updated 4 Sept 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-oracle`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical record ↗Source updated 4 Sept 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-raspi`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical record ↗Source updated 4 Sept 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-raspi-realtime`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical record ↗Source updated 4 Sept 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-realtime`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical record ↗Source updated 4 Sept 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-riscv`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical record ↗Source updated 4 Sept 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-xilinx`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical record ↗Source updated 4 Sept 2026

Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current

CVE-2026-53365 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: vsock/virtio: fix zerocopy completion for multi-skb sends

184 known affected

The vendor explicitly identifies these products as affected by this CVE.

kernel as a component of Red Hat Enterprise Linux 10
kernel-64k as a component of Red Hat Enterprise Linux 10
kernel-64k-core as a component of Red Hat Enterprise Linux 10
kernel-64k-debug as a component of Red Hat Enterprise Linux 10
kernel-64k-debug-core as a component of Red Hat Enterprise Linux 10
kernel-64k-debug-devel as a component of Red Hat Enterprise Linux 10
kernel-64k-debug-devel-matched as a component of Red Hat Enterprise Linux 10
kernel-64k-debug-modules as a component of Red Hat Enterprise Linux 10
kernel-64k-debug-modules-core as a component of Red Hat Enterprise Linux 10
kernel-64k-debug-modules-extra as a component of Red Hat Enterprise Linux 10
kernel-64k-devel as a component of Red Hat Enterprise Linux 10
kernel-64k-devel-matched as a component of Red Hat Enterprise Linux 10

Summary: A flaw was found in the Linux kernel's `vsock/virtio` component. This vulnerability occurs during zerocopy completion for large messages fragmented into multiple socket kernel buffers (skbs). An issue in how user arguments (uargs) are handled for these buffers can lead to pinned user pages not being properly tracked or released. This prevents the kernel from notifying userspace when these memory pages are safe to reuse, potentially leading to memory leaks or data corruption if pages are prematurely reallocated. This issue could lead to local privilege escalation.
Remediation: The vulnerable code path is only reachable when using virtio-vsock with zerocopy transmit on virtual machines using the vhost-vsock or virtio-vsock transport. Systems that do not use VM socket communication (AF_VSOCK) are not affected. To prevent the vulnerable code path from being reached, the vhost_vsock kernel module can be unloaded and blacklisted if vsock functionality is not required: ``` modprobe -r vhost_vsock echo "blacklist vhost_vsock" > /etc/modprobe.d/vsock-blacklist.conf ``` Systems that rely on VM-to-host socket communication (e.g., QEMU guest agent communication) cannot use this mitigation and should prioritize applying the kernel fix.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current

ENISA EUVD identifier

EUVD-2026-43513

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state: Present in the current official mapping
Known exploitation: Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score: Not supplied in the stored EUVD record
Advisory evidence: No linked advisory details stored yet

Recommended actionWithin 7 days

Medium technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance.

Patch available

What, why and how

In the Linux kernel, the following vulnerability has been resolved: vsock/virtio: fix zerocopy completion for multi-skb sends When a large message is fragmented into multiple skbs, the zerocopy uarg is only allocated and attached to the last skb in the loop. Non-final skbs carry pinned user pages with no completion tracking, so the kernel has no way to notify userspace when those pages are safe to reuse. If the loop breaks early the uarg is never allocated at all, leaking pinned pages with no completion notification. Fix this by following the approach used by TCP: allocate the zerocopy uarg (if not provided by the caller) before the send loop and attach it to every skb via skb_zcopy_set(), which takes a reference per skb. Each skb's completion properly decrements the refcount, and the notification only fires after the last skb is freed. On failure, if no data was sent, the uarg is cleanly aborted via net_zcopy_put_abort(). This issue was initially discovered by sashiko while reviewing commit 1cb36e252211 ("vsock/virtio: fix MSG_ZEROCOPY pinned-pages accounting") but was pre-existing.

What

Why

The product does not release or incorrectly releases a resource before it is made available for re-use.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

Why

The product does not release or incorrectly releases a resource before it is made available for re-use.

How

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation

Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.

No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material

Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.

Reference recorded

CISA Vulnrichment records proof-of-concept exploitation in its SSVC data. BlackTree has not independently executed or validated exploit material.

Likely attack path: local access → Improper Resource Shutdown or Release → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface: Local
Privileges required: Low: a basic authenticated account is required
User interaction: None
Attack complexity: Low: no specialised conditions are recorded
Security boundary: Unchanged: impact remains within the vulnerable component's security authority
Weakness ? CWE means Common Weakness Enumeration: a standard category for the underlying weakness.: CWE-404 ↗
CWE-404: Improper Resource Shutdown or Release. The product does not release or incorrectly releases a resource before it is made available for re-use.
CVSS vector ? CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land: The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.

CWE-404Public exploit reference

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

ENISA EUVD · EUVD-2026-43513Official EUVD mapping

0 linked advisory records.

Official EUVD record

BSI · German · WID-SEC-W-2026-2313Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service

Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen.

Official advisory

CERT-FR · French · CERTFR-2026-AVI-1066Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-53321 Référence CVE CVE-2026-53322 https://www.cve.org/CVERecord?id=CVE-2026-53322 Référence CVE CVE-2026-53323 https://www.cve.org/CVERecord?id=CVE-2026-53323 Référence CVE CVE-2026-53324 https://www.cve.org/CVERecord?id=CVE-2026-53324 Référence CVE CVE-2026-53357 https://www.cve.org/CVERecord?id=CVE-2026-53357 Référence CVE CVE-2026-53358 https://www.cve.org/CVERecord?id=CVE-2026-53358 Référence CVE CVE-2026-53359 https://www.cve.org/CVERecord?id=CVE-2026-53359 Référence CVE CVE-2026-53360 https://www.cve.org/CVERecord?id=CVE-2026-53360 Référence CVE CVE-2026-53364 https://www.cve.org/CVERecord?id=CVE-2026-53364 Référence CVE CVE-2026-53365 https://www.cve.org/CVERecord?id=CVE-2026-53365 Référence CVE CVE-2026-53367 https://www.cve.org/CVERecord?id=CVE-2026-53367 Référence CVE CVE-2026-53368 https://www.cve.org/CVERecord?id=CVE-2026-53368 Référence CVE CVE-2026-53369 https://www.cve.org/CVERecord?id=CVE-2026-53369 Référence CVE CVE-2026-53370 https://www.cve.org/CVERecord?id=CVE-2026-53370 Référence CVE CVE-2026-53371 https://www.cve.org/CVERecord?id=CVE-2026-53371 Référence CVE CVE-2026-53372 https://www.cve.org/CVERecord?id=CVE-2026-53372 Référence CVE CVE-2026-53373 https://www.cve.org/CVERecord?id=CVE-2026-53373 Référence CVE CVE-2026-53374 https://www.cve.org/CVERecord?id=

Official advisory

CERT-FR · French · CERTFR-2026-AVI-1031Multiples vulnérabilités dans le noyau Linux de Debian LTS

d?id=CVE-2026-43216 Référence CVE CVE-2026-45944 https://www.cve.org/CVERecord?id=CVE-2026-45944 Référence CVE CVE-2026-46093 https://www.cve.org/CVERecord?id=CVE-2026-46093 Référence CVE CVE-2026-46135 https://www.cve.org/CVERecord?id=CVE-2026-46135 Référence CVE CVE-2026-53005 https://www.cve.org/CVERecord?id=CVE-2026-53005 Référence CVE CVE-2026-53027 https://www.cve.org/CVERecord?id=CVE-2026-53027 Référence CVE CVE-2026-53226 https://www.cve.org/CVERecord?id=CVE-2026-53226 Référence CVE CVE-2026-53260 https://www.cve.org/CVERecord?id=CVE-2026-53260 Référence CVE CVE-2026-53332 https://www.cve.org/CVERecord?id=CVE-2026-53332 Référence CVE CVE-2026-53365 https://www.cve.org/CVERecord?id=CVE-2026-53365 Référence CVE CVE-2026-53392 https://www.cve.org/CVERecord?id=CVE-2026-53392 Référence CVE CVE-2026-53393 https://www.cve.org/CVERecord?id=CVE-2026-53393 Référence CVE CVE-2026-53399 https://www.cve.org/CVERecord?id=CVE-2026-53399 Référence CVE CVE-2026-53400 https://www.cve.org/CVERecord?id=CVE-2026-53400 Référence CVE CVE-2026-53402 https://www.cve.org/CVERecord?id=CVE-2026-53402 Référence CVE CVE-2026-63797 https://www.cve.org/CVERecord?id=CVE-2026-63797 Référence CVE CVE-2026-63806 https://www.cve.org/CVERecord?id=CVE-2026-63806 Référence CVE CVE-2026-63810 https://www.cve.org/CVERecord?id=

Official advisory

CERT-FR · French · CERTFR-2026-AVI-0981Multiples vulnérabilités dans le noyau Linux de Debian

de Debian. Elles permettent à un attaquant de provoquer une élévation de privilèges, une atteinte à l'intégrité des données et un déni de service. Solutions Se référer au bulletin de sécurité de l'éditeur pour l'obtention des correctifs (cf. section Documentation). Documentation Bulletin de sécurité Debian msg00316 du 31 juillet 2026 https://lists.debian.org/debian-security-announce/2026/msg00316.html Référence CVE CVE-2026-45944 https://www.cve.org/CVERecord?id=CVE-2026-45944 Référence CVE CVE-2026-53005 https://www.cve.org/CVERecord?id=CVE-2026-53005 Référence CVE CVE-2026-53260 https://www.cve.org/CVERecord?id=CVE-2026-53260 Référence CVE CVE-2026-53365 https://www.cve.org/CVERecord?id=CVE-2026-53365 Référence CVE CVE-2026-63970 https://www.cve.org/CVERecord?id=CVE-2026-63970 Référence CVE CVE-2026-64192 https://www.cve.org/CVERecord?id=CVE-2026-64192 Référence CVE CVE-2026-64206 https://www.cve.org/CVERecord?id=CVE-2026-64206 Référence CVE CVE-2026-64227 https://www.cve.org/CVERecord?id=CVE-2026-64227 Référence CVE CVE-2026-64286 https://www.cve.org/CVERecord?id=CVE-2026-64286 Référence CVE CVE-2026-64287 https://www.cve.org/CVERecord?id=CVE-2026-64287 Référence CVE CVE-2026-64307 https://www.cve.org/CVERecord?id=CVE-2026-64307 Référence CVE CVE-2026-64341 https://www.cve.org/CVERecord?id=

Official advisory

CERT-FR · French · CERTFR-2026-AVI-0954Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-53321 Référence CVE CVE-2026-53322 https://www.cve.org/CVERecord?id=CVE-2026-53322 Référence CVE CVE-2026-53323 https://www.cve.org/CVERecord?id=CVE-2026-53323 Référence CVE CVE-2026-53324 https://www.cve.org/CVERecord?id=CVE-2026-53324 Référence CVE CVE-2026-53354 https://www.cve.org/CVERecord?id=CVE-2026-53354 Référence CVE CVE-2026-53357 https://www.cve.org/CVERecord?id=CVE-2026-53357 Référence CVE CVE-2026-53358 https://www.cve.org/CVERecord?id=CVE-2026-53358 Référence CVE CVE-2026-53360 https://www.cve.org/CVERecord?id=CVE-2026-53360 Référence CVE CVE-2026-53364 https://www.cve.org/CVERecord?id=CVE-2026-53364 Référence CVE CVE-2026-53365 https://www.cve.org/CVERecord?id=CVE-2026-53365 Référence CVE CVE-2026-53367 https://www.cve.org/CVERecord?id=CVE-2026-53367 Référence CVE CVE-2026-53368 https://www.cve.org/CVERecord?id=CVE-2026-53368 Référence CVE CVE-2026-53369 https://www.cve.org/CVERecord?id=CVE-2026-53369 Référence CVE CVE-2026-53370 https://www.cve.org/CVERecord?id=CVE-2026-53370 Référence CVE CVE-2026-53371 https://www.cve.org/CVERecord?id=CVE-2026-53371 Référence CVE CVE-2026-53372 https://www.cve.org/CVERecord?id=CVE-2026-53372 Référence CVE CVE-2026-53373 https://www.cve.org/CVERecord?id=CVE-2026-53373 Référence CVE CVE-2026-53374 https://www.cve.org/CVERecord?id=

Official advisory

CERT-FR · French · CERTFR-2026-AVI-0926Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-53321 Référence CVE CVE-2026-53322 https://www.cve.org/CVERecord?id=CVE-2026-53322 Référence CVE CVE-2026-53323 https://www.cve.org/CVERecord?id=CVE-2026-53323 Référence CVE CVE-2026-53324 https://www.cve.org/CVERecord?id=CVE-2026-53324 Référence CVE CVE-2026-53354 https://www.cve.org/CVERecord?id=CVE-2026-53354 Référence CVE CVE-2026-53357 https://www.cve.org/CVERecord?id=CVE-2026-53357 Référence CVE CVE-2026-53358 https://www.cve.org/CVERecord?id=CVE-2026-53358 Référence CVE CVE-2026-53360 https://www.cve.org/CVERecord?id=CVE-2026-53360 Référence CVE CVE-2026-53364 https://www.cve.org/CVERecord?id=CVE-2026-53364 Référence CVE CVE-2026-53365 https://www.cve.org/CVERecord?id=CVE-2026-53365 Référence CVE CVE-2026-53367 https://www.cve.org/CVERecord?id=CVE-2026-53367 Référence CVE CVE-2026-53368 https://www.cve.org/CVERecord?id=CVE-2026-53368 Référence CVE CVE-2026-53369 https://www.cve.org/CVERecord?id=CVE-2026-53369 Référence CVE CVE-2026-53370 https://www.cve.org/CVERecord?id=CVE-2026-53370 Référence CVE CVE-2026-53371 https://www.cve.org/CVERecord?id=CVE-2026-53371 Référence CVE CVE-2026-53372 https://www.cve.org/CVERecord?id=CVE-2026-53372 Référence CVE CVE-2026-53373 https://www.cve.org/CVERecord?id=CVE-2026-53373 Référence CVE CVE-2026-53374 https://www.cve.org/CVERecord?id=

Official advisory

Patch and workaround

Operational remediation based on structured source evidence.

Status ? Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.: Patch available
Affected: kernel as a component of Red Hat Enterprise Linux 10; kernel-64k as a component of Red Hat Enterprise Linux 10; kernel-64k-core as a component of Red Hat Enterprise Linux 10; kernel-64k-debug as a component of Red Hat Enterprise Linux 10; kernel-64k-debug-core as a component of Red Hat Enterprise Linux 10; kernel-64k-debug-devel as a component of Red Hat Enterprise Linux 10; kernel-64k-debug-devel-matched as a component of Red Hat Enterprise Linux 10; kernel-64k-debug-modules as a component of Red Hat Enterprise Linux 10; kernel-64k-debug-modules-core as a component of Red Hat Enterprise Linux 10; kernel-64k-debug-modules-extra as a component of Red Hat Enterprise Linux 10; kernel-64k-devel as a component of Red Hat Enterprise Linux 10; kernel-64k-devel-matched as a component of Red Hat Enterprise Linux 10; kernel-64k-modules as a component of Red Hat Enterprise Linux 10; kernel-64k-modules-core as a component of Red Hat Enterprise Linux 10; kernel-64k-modules-extra as a component of Red Hat Enterprise Linux 10; kernel-abi-stablelists as a component of Red Hat Enterprise Linux 10; kernel-core as a component of Red Hat Enterprise Linux 10; kernel-debug as a component of Red Hat Enterprise Linux 10; kernel-debug-core as a component of Red Hat Enterprise Linux 10; kernel-debug-devel as a component of Red Hat Enterprise Linux 10; kernel-debug-devel-matched as a component of Red Hat Enterprise Linux 10; kernel-debug-modules as a component of Red Hat Enterprise Linux 10; kernel-debug-modules-core as a component of Red Hat Enterprise Linux 10; kernel-debug-modules-extra as a component of Red Hat Enterprise Linux 10; kernel-debug-uki-virt as a component of Red Hat Enterprise Linux 10; kernel-devel as a component of Red Hat Enterprise Linux 10; kernel-devel-matched as a component of Red Hat Enterprise Linux 10; kernel-doc as a component of Red Hat Enterprise Linux 10; kernel-modules as a component of Red Hat Enterprise Linux 10; kernel-modules-core as a component of Red Hat Enterprise Linux 10; and 154 more
Fixed: < 6.7; 6.12.97 ≤ 6.12.*; 6.18.34 ≤ 6.18.*; 7.0.11 ≤ 7.0.*; 7.1 ≤ *
Action: Review the linked authoritative reference and apply the recorded fixed release appropriate to the affected product branch.
Workaround: The vulnerable code path is only reachable when using virtio-vsock with zerocopy transmit on virtual machines using the vhost-vsock or virtio-vsock transport. Systems that do not use VM socket communication (AF_VSOCK) are not affected. To prevent the vulnerable code path from being reached, the vhost_vsock kernel module can be unloaded and blacklisted if vsock functionality is not required: ``` modprobe -r vhost_vsock echo "blacklist vhost_vsock" > /etc/modprobe.d/vsock-blacklist.conf ``` Systems that rely on VM-to-host socket communication (e.g., QEMU guest agent communication) cannot use this mitigation and should prioritize applying the kernel fix.

Evidence and provenance

Published 13 Jul 2026 · Last source change 18 Aug 2026, 13:29 UTC · CWE-404 · Improper Resource Shutdown or Release

CVE recordCVE.org · 5.2

CVSS sourceNIST NVD

EPSS source

The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.

FIRST · tracked since 2026-08-14

European sourceENISA EUVD · EUVD-2026-43513

Product sourceVendor CSAF · Red Hat Product Security

Remediation sourceVendor CSAF · Red Hat Product Security

CWE sourceCISA ADP

NVD statusNVD modified after enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates →

25 Aug 2026, 10:48 UTC
Vendor guidanceAuthoritative vendor guidance changed from authoritative remediation link to authoritative remediation link.
Before
authoritative remediation link
After
authoritative remediation link
Red Hat Product Security ↗
25 Aug 2026, 10:48 UTC
Remediation statusRemediation status changed from Awaiting fix to Mitigation available.
Before
Awaiting fix
After
Mitigation available
Red Hat Product Security ↗
18 Aug 2026, 13:29 UTC
Public exploit evidencePublic exploit evidence changed from Public exploit reference to Public exploit reference.
Before
Public exploit reference
After
Public exploit reference
CVE.org ↗
18 Aug 2026, 13:29 UTC
Public exploit evidencePublic exploit evidence changed from Public exploit reference to Public exploit reference.
Before
Public exploit reference
After
Public exploit reference
134c704f-9b21-4f2e-91b3-4a467353bcc0 ↗
18 Aug 2026, 03:55 UTC
Public exploit evidencePublic exploit evidence changed from No public exploit to Public exploit reference.
Before
No public exploit
After
Public exploit reference
CVE.org ↗

2026-07-13CVE published

2026-08-18Fixed release or patch reference recorded

ENISA EUVD · EUVD-2026-43513↗Vendor CSAF · Red Hat Product Security↗CISA Vulnrichment SSVC evidence↗Patch or update reference↗Patch or update reference↗Patch or update reference↗CVE authority or vendor reference↗Official CVE record (CNA and ADP data)↗NVD record↗

Technical terms and abbreviations used in this report

CVE: Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS: Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS: Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE: Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA: CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP: Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD: National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT: A computer security incident response team that publishes warnings or coordinates incident response.
PoC: Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF: Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL: Living off the land: abuse of legitimate tools or system functions during an attack.

vsock/virtio: fix zerocopy completion for multi-skb sends

National CERT insights ?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

EUVD-2026-43513

What, why and how

Exploit reality and attack path

Official authority intelligence

Patch and workaround

Evidence and provenance

National CERT insights
?
CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.