CVE-2026-53365: vsock/virtio: fix zerocopy completion for multi-skb sends
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
- CWE
- CWE-401
Report tools
Action score
22
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.
Is your version affected? Check itNoroxi 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 helpAffected 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.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_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.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:10 | kernel | before 6.12.0-211.64.1.el10_2 | 6.12.0-211.64.1.el10_2 |
| AlmaLinux:10 | kernel-64k | before 6.12.0-211.64.1.el10_2 | 6.12.0-211.64.1.el10_2 |
| AlmaLinux:10 | kernel-64k-core | before 6.12.0-211.64.1.el10_2 | 6.12.0-211.64.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug | before 6.12.0-211.64.1.el10_2 | 6.12.0-211.64.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-core | before 6.12.0-211.64.1.el10_2 | 6.12.0-211.64.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-devel | before 6.12.0-211.64.1.el10_2 | 6.12.0-211.64.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-devel-matched | before 6.12.0-211.64.1.el10_2 | 6.12.0-211.64.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-modules | before 6.12.0-211.64.1.el10_2 | 6.12.0-211.64.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-modules-core | before 6.12.0-211.64.1.el10_2 | 6.12.0-211.64.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-modules-extra | before 6.12.0-211.64.1.el10_2 | 6.12.0-211.64.1.el10_2 |
| AlmaLinux:10 | kernel-64k-devel | before 6.12.0-211.64.1.el10_2 | 6.12.0-211.64.1.el10_2 |
| AlmaLinux:10 | kernel-64k-devel-matched | before 6.12.0-211.64.1.el10_2 | 6.12.0-211.64.1.el10_2 |
| AlmaLinux:10 | kernel-64k-modules | before 6.12.0-211.64.1.el10_2 | 6.12.0-211.64.1.el10_2 |
| AlmaLinux:10 | kernel-64k-modules-core | before 6.12.0-211.64.1.el10_2 | 6.12.0-211.64.1.el10_2 |
| AlmaLinux:10 | kernel-64k-modules-extra | before 6.12.0-211.64.1.el10_2 | 6.12.0-211.64.1.el10_2 |
| AlmaLinux:10 | kernel-abi-stablelists | before 6.12.0-211.64.1.el10_2 | 6.12.0-211.64.1.el10_2 |
| AlmaLinux:10 | kernel-core | before 6.12.0-211.64.1.el10_2 | 6.12.0-211.64.1.el10_2 |
| AlmaLinux:10 | kernel-cross-headers | before 6.12.0-211.64.1.el10_2 | 6.12.0-211.64.1.el10_2 |
| AlmaLinux:10 | kernel-debug | before 6.12.0-211.64.1.el10_2 | 6.12.0-211.64.1.el10_2 |
| AlmaLinux:10 | kernel-debug-core | before 6.12.0-211.64.1.el10_2 | 6.12.0-211.64.1.el10_2 |
| AlmaLinux:10 | kernel-debug-devel | before 6.12.0-211.64.1.el10_2 | 6.12.0-211.64.1.el10_2 |
| AlmaLinux:10 | kernel-debug-devel-matched | before 6.12.0-211.64.1.el10_2 | 6.12.0-211.64.1.el10_2 |
| AlmaLinux:10 | kernel-debug-modules | before 6.12.0-211.64.1.el10_2 | 6.12.0-211.64.1.el10_2 |
| AlmaLinux:10 | kernel-debug-modules-core | before 6.12.0-211.64.1.el10_2 | 6.12.0-211.64.1.el10_2 |
+96
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- 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…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2026-53362Jul 4, 2026 · ipv6: account for fraggap on the paged allocation pathKEV61This 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 / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 293fe8f2d1b5ac464ca16a8eba09571bbbb34ba9 | Vendor (CNA) |
| Linux Linux | 76b995bc57bd90cb6e954e1966fbd8786da47f0d | Vendor (CNA) |
| Linux Linux | ae38d9179190a956e2a87a69ef1dd6f451b51c4d | Vendor (CNA) |
| Linux Linux | b3155f2b78db21e99256bcf7eb902f24ff6d5338 | Vendor (CNA) |
| almalinux:kernel | 5.14.0-687.56.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel | 6.12.0-211.64.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k | 5.14.0-687.56.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k | 6.12.0-211.64.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-core | 5.14.0-687.56.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-core | 6.12.0-211.64.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug | 5.14.0-687.56.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug | 6.12.0-211.64.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-core | 5.14.0-687.56.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-core | 6.12.0-211.64.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel | 5.14.0-687.56.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel | 6.12.0-211.64.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel-matched | 5.14.0-687.56.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel-matched | 6.12.0-211.64.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules | 5.14.0-687.56.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules | 6.12.0-211.64.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-core | 5.14.0-687.56.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-core | 6.12.0-211.64.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-extra | 5.14.0-687.56.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-extra | 6.12.0-211.64.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-devel | 5.14.0-687.56.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-devel | 6.12.0-211.64.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-devel-matched | 5.14.0-687.56.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-devel-matched | 6.12.0-211.64.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| debian:linux | 6.12.100-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.100-1~deb12u1 · Debian:12 | Package 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.
| Source | Kind | Date |
|---|---|---|
| Proof-of-concept repository on GitHub | 3 repositories | 2026-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.
- Published
- First PoC+31 d
- 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.
- TR-26-0550 · Jul 14, 2026(Linux Kernel Güvenlik Bildirimi)
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
Weakness class (CWE)
CWE-401 · Missing Release of Memory after Effective LifetimeCVSS 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.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.