CVE-2026-63970

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-19. the CNA's CVSS baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
Trending — 4 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

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

vsock/virtio: bind uarg before filling zerocopy skb

virtio_transport_send_pkt_info() allocates or reuses the zerocopy uarg before entering the send loop, but virtio_transport_alloc_skb() still fills the skb before it inherits that uarg. When fixed-buffer vectored zerocopy hits MAX_SKB_FRAGS, io_sg_from_iter() may partially attach managed frags and return -EMSGSIZE. The rollback path call kfree_skb() to free an skb that carries SKBFL_MANAGED_FRAG_REFS but no uarg, so skb_release_data() falls through to ordinary frag unref.

Pass the uarg into virtio_transport_alloc_skb() and bind it immediately before virtio_transport_fill_skb(). This keeps control or no-payload skbs untouched while ensuring success and rollback share one lifetime rule.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
7%
KEV
Not listed

Published

July 19, 2026

Last Modified

August 5, 2026

Advisory Details (3)

Auto-updated Jul 21, 2026
No patch confirmed yet.
generic

vsock/virtio: bind uarg before filling zerocopy skb - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b62e2b2b4a50953ca952f3cd3f77dd62dc50fd5d
generic

vsock/virtio: bind uarg before filling zerocopy skb - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5d317573f1d48e76cce5fb6250452b6e4102e0fb
generic

vsock/virtio: bind uarg before filling zerocopy skb - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1e584c304cfb94a759417130b1fc6d30b30c4cce

Vendor Advisories for CVE-2026-63970(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(5)

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.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux-6.126.12.100-1~deb12u1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.96-1 (31 versions)6.12.100-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (139 versions)7.0.12-1

All Vendor Advisories

(5)

Data Freshness Timeline

(refreshed 33× in last 7d / 174× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 223 total refreshes for this CVE.

  1. 2026-08-30 02:54 UTCEG score recompute
  2. 2026-08-30 02:54 UTCVendor advisory
  3. 2026-08-30 02:54 UTCGHSA enrichment
  4. 2026-08-30 01:22 UTCEPSS rescore
  5. 2026-08-28 21:42 UTCEPSS rescore
  6. 2026-08-27 22:44 UTCEG score recompute
  7. 2026-08-27 22:44 UTCVendor advisory
  8. 2026-08-27 22:44 UTCGHSA enrichment
  9. 2026-08-27 14:25 UTCEPSS rescore
  10. 2026-08-27 11:53 UTCVendor advisory
  11. 2026-08-27 11:52 UTCGHSA enrichment
  12. 2026-08-26 22:25 UTCEG score recompute
  13. 2026-08-26 22:25 UTCVendor advisory
  14. 2026-08-26 22:25 UTCGHSA enrichment
  15. 2026-08-26 14:46 UTCEPSS rescore
  16. 2026-08-26 07:54 UTCVendor advisory
  17. 2026-08-26 07:54 UTCGHSA enrichment
  18. 2026-08-25 20:56 UTCEG score recompute
  19. 2026-08-25 20:56 UTCVendor advisory
  20. 2026-08-25 20:55 UTCGHSA enrichment
  21. 2026-08-25 13:49 UTCEPSS rescore
  22. 2026-08-25 09:59 UTCVendor advisory
  23. 2026-08-25 09:59 UTCGHSA enrichment
  24. 2026-08-24 23:07 UTCEG score recompute
  25. 2026-08-24 23:07 UTCVendor advisory
Show 75 more
  1. 2026-08-24 23:07 UTCGHSA enrichment
  2. 2026-08-24 12:15 UTCEG score recompute
  3. 2026-08-24 12:15 UTCVendor advisory
  4. 2026-08-24 12:15 UTCGHSA enrichment
  5. 2026-08-24 01:02 UTCVendor advisory
  6. 2026-08-24 01:02 UTCGHSA enrichment
  7. 2026-08-23 14:09 UTCVendor advisory
  8. 2026-08-23 14:09 UTCGHSA enrichment
  9. 2026-08-23 03:14 UTCEG score recompute
  10. 2026-08-23 03:14 UTCVendor advisory
  11. 2026-08-23 03:14 UTCGHSA enrichment
  12. 2026-08-23 00:19 UTCEPSS rescore
  13. 2026-08-22 16:22 UTCVendor advisory
  14. 2026-08-22 16:22 UTCGHSA enrichment
  15. 2026-08-22 05:30 UTCEG score recompute
  16. 2026-08-22 05:30 UTCVendor advisory
  17. 2026-08-22 05:30 UTCGHSA enrichment
  18. 2026-08-21 23:49 UTCEPSS rescore
  19. 2026-08-21 18:38 UTCVendor advisory
  20. 2026-08-21 18:38 UTCGHSA enrichment
  21. 2026-08-21 07:46 UTCEG score recompute
  22. 2026-08-21 07:46 UTCVendor advisory
  23. 2026-08-21 07:46 UTCGHSA enrichment
  24. 2026-08-20 22:55 UTCEPSS rescore
  25. 2026-08-20 20:53 UTCVendor advisory
  26. 2026-08-20 20:53 UTCGHSA enrichment
  27. 2026-08-20 10:01 UTCVendor advisory
  28. 2026-08-20 10:01 UTCGHSA enrichment
  29. 2026-08-19 23:09 UTCEG score recompute
  30. 2026-08-19 23:09 UTCVendor advisory
  31. 2026-08-19 23:09 UTCGHSA enrichment
  32. 2026-08-19 17:04 UTCEPSS rescore
  33. 2026-08-19 07:18 UTCVendor advisory
  34. 2026-08-19 07:18 UTCGHSA enrichment
  35. 2026-08-18 20:22 UTCEG score recompute
  36. 2026-08-18 20:22 UTCVendor advisory
  37. 2026-08-18 20:22 UTCGHSA enrichment
  38. 2026-08-18 13:48 UTCEPSS rescore
  39. 2026-08-18 09:24 UTCVendor advisory
  40. 2026-08-18 09:24 UTCGHSA enrichment
  41. 2026-08-17 21:10 UTCEG score recompute
  42. 2026-08-17 21:10 UTCVendor advisory
  43. 2026-08-17 21:09 UTCGHSA enrichment
  44. 2026-08-17 13:47 UTCEPSS rescore
  45. 2026-08-17 07:55 UTCVendor advisory
  46. 2026-08-17 07:55 UTCGHSA enrichment
  47. 2026-08-16 21:04 UTCEG score recompute
  48. 2026-08-16 21:04 UTCVendor advisory
  49. 2026-08-16 21:04 UTCGHSA enrichment
  50. 2026-08-16 14:56 UTCEPSS rescore
  51. 2026-08-16 10:11 UTCEG score recompute
  52. 2026-08-16 10:11 UTCVendor advisory
  53. 2026-08-16 10:11 UTCGHSA enrichment
  54. 2026-08-15 23:20 UTCVendor advisory
  55. 2026-08-15 23:20 UTCGHSA enrichment
  56. 2026-08-15 12:28 UTCVendor advisory
  57. 2026-08-15 12:28 UTCGHSA enrichment
  58. 2026-08-15 01:35 UTCEG score recompute
  59. 2026-08-15 01:35 UTCVendor advisory
  60. 2026-08-15 01:35 UTCGHSA enrichment
  61. 2026-08-15 01:30 UTCEPSS rescore
  62. 2026-08-14 14:43 UTCVendor advisory
  63. 2026-08-14 14:43 UTCGHSA enrichment
  64. 2026-08-14 03:51 UTCEG score recompute
  65. 2026-08-14 03:51 UTCVendor advisory
  66. 2026-08-14 03:51 UTCGHSA enrichment
  67. 2026-08-13 22:00 UTCEPSS rescore
  68. 2026-08-13 16:59 UTCVendor advisory
  69. 2026-08-13 16:59 UTCGHSA enrichment
  70. 2026-08-13 06:08 UTCVendor advisory
  71. 2026-08-13 06:08 UTCGHSA enrichment
  72. 2026-08-12 19:16 UTCEG score recompute
  73. 2026-08-12 19:16 UTCVendor advisory
  74. 2026-08-12 19:16 UTCGHSA enrichment
  75. 2026-08-12 13:51 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-63970?
CVE-2026-63970 is a high vulnerability published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: vsock/virtio: bind uarg before filling zerocopy skb virtiotransportsendpktinfo() allocates or reuses the zerocopy uarg before entering the send loop, but virtiotransportalloc_skb() still fills the skb before it inherits that uarg.…
When was CVE-2026-63970 disclosed?
CVE-2026-63970 was first published in the National Vulnerability Database on July 19, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-63970 actively exploited?
CVE-2026-63970 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 92.9% of all scored CVEs.
What is the CVSS score of CVE-2026-63970?
CVE-2026-63970 has a CVSS v4.0 base score of 7.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-63970?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-63970, 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-2026-63970

Explore →

Is Your Infrastructure Affected by CVE-2026-63970?

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