Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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

MediumCVSS 5.5 · v3.1—Proof of concept Fix available

Noroxi assessment

Priority: Monitor (action score 22/100)

  • Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.19% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 293fe8f2d1b5ac464ca16a8eba09571bbbb34ba9, 76b995bc57bd90cb6e954e1966fbd8786da47f0d, ae38d9179190a956e2a87a69ef1dd6f451b51c4d.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 293fe8f2d1b5ac464ca16a8eba09571bbbb34ba9, 76b995bc57bd90cb6e954e1966fbd8786da47f0d, ae38d9179190a956e2a87a69ef1dd6f451b51c4d or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

Published
Jul 13, 2026
Updated
Aug 18, 2026
EPSS
0.1% · 9th percentile

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
proof of concept
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • Proof of concept exists, no weaponized module
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-53365

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 6.7affected
    • 581512a6dc939ef122e49336626ae159f3b8a345 and later · before 293fe8f2d1b5ac464ca16a8eba09571bbbb34ba9affected · git
    • 581512a6dc939ef122e49336626ae159f3b8a345 and later · before 76b995bc57bd90cb6e954e1966fbd8786da47f0daffected · git
    • 581512a6dc939ef122e49336626ae159f3b8a345 and later · before b3155f2b78db21e99256bcf7eb902f24ff6d5338affected · git
    • 581512a6dc939ef122e49336626ae159f3b8a345 and later · before ae38d9179190a956e2a87a69ef1dd6f451b51c4daffected · git
    • before 6.7not affected · semver
    • 6.12.97 and later · up to and including 6.12.*not affected · semver
    • 6.18.34 and later · up to and including 6.18.*not affected · semver
    • 7.0.11 and later · up to and including 7.0.*not affected · semver
    • 7.1 and laternot affected · original_commit_for_fix

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel6.7 and later · before 6.18.34
  • linux linux kernel6.19 and later · before 7.0.11
  • linux linux kernel7.1

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:10kernelbefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-64kbefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-64k-corebefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-64k-debugbefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-64k-debug-corebefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-64k-debug-develbefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-64k-debug-devel-matchedbefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-64k-debug-modulesbefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-corebefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-extrabefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-64k-develbefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-64k-devel-matchedbefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-64k-modulesbefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-64k-modules-corebefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-64k-modules-extrabefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-abi-stablelistsbefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-corebefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-cross-headersbefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-debugbefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-debug-corebefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-debug-develbefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-debug-devel-matchedbefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-debug-modulesbefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-debug-modules-corebefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2

+96

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2026-53362Jul 4, 2026 · ipv6: account for fraggap on the paged allocation pathKEV
    61This week
  • ← EarlierCVE-2026-53363Jul 10, 2026 · xfrm: iptfs: preserve shared-frag marker in iptfs_consume_frags()
    39Monitor
  • Later →CVE-2026-53364Jul 13, 2026 · Bluetooth: hci_conn: Fix memory leak in hci_le_big_terminate()
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux293fe8f2d1b5ac464ca16a8eba09571bbbb34ba9Vendor (CNA)
Linux Linux76b995bc57bd90cb6e954e1966fbd8786da47f0dVendor (CNA)
Linux Linuxae38d9179190a956e2a87a69ef1dd6f451b51c4dVendor (CNA)
Linux Linuxb3155f2b78db21e99256bcf7eb902f24ff6d5338Vendor (CNA)
almalinux:kernel5.14.0-687.56.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel6.12.0-211.64.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k5.14.0-687.56.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k6.12.0-211.64.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-core5.14.0-687.56.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-core6.12.0-211.64.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug5.14.0-687.56.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug6.12.0-211.64.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-core5.14.0-687.56.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-core6.12.0-211.64.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-devel5.14.0-687.56.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel6.12.0-211.64.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched5.14.0-687.56.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched6.12.0-211.64.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules5.14.0-687.56.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules6.12.0-211.64.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules-core5.14.0-687.56.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-core6.12.0-211.64.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra5.14.0-687.56.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra6.12.0-211.64.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-devel5.14.0-687.56.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel6.12.0-211.64.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-devel-matched5.14.0-687.56.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel-matched6.12.0-211.64.1.el10_2 · AlmaLinux:10Package registry (OSV)
debian:linux6.12.100-1 · Debian:13Package registry (OSV)
debian:linux-6.126.12.100-1~deb12u1 · Debian:12Package registry (OSV)

+24

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

  • Proof-of-concept repository on GitHub ×3

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Proof-of-concept repository on GitHub3 repositories2026-08-14 → 2026-10-16

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. Published
  2. First PoC+31 d
  3. TodayNov 16, 2026+126 d

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

CVSS vector

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

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

References

All records