CVE-2026-63830

CRITICALPre-NVD 9.49.4
EchelonGraph scoreMEDIUM confidence

Score 9.4 from GitHub Security Advisory (severity: CRITICAL) published 2026-07-19. a secondary CVSS source baseline 9.4; sources differ by 0.0.

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

A fix is available — apply it.

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

net: skmsg: preserve sg.copy across SG transforms

The sk_msg sg.copy bitmap is part of the scatterlist entry ownership state. A set bit tells sk_msg_compute_data_pointers() not to expose the entry through writable BPF ctx->data. This protects entries backed by pages that are not private to the sk_msg, such as splice-backed file page-cache pages.

Several sk_msg transform paths move, copy, split, or compact msg->sg.data[] entries without moving the matching sg.copy bit. This can make an externally backed entry arrive at a new slot with a clear copy bit. A later SK_MSG verdict can then expose sg_virt(sge) as writable ctx->data and BPF stores can modify the original page cache.

Keep sg.copy synchronized with sg.data[] whenever entries are transferred, shifted, split, or copied into a new sk_msg. Clear the bit when an entry is replaced by a newly allocated private page or freed. This covers the BPF pull/push/pop helpers, sk_msg_shift_left/right(), sk_msg_xfer(), and tls_split_open_record(), including the partial tail entry created during TLS open-record splitting.

CVSS v3
9.4
EG Score
9.4(medium)
EG Risk
47(Track)
EG Risk 47/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
Severity94% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
31%
KEV
Not listed

Published

July 19, 2026

Last Modified

August 17, 2026

Advisory Details (8)

Auto-updated Sep 5, 2026
No patch confirmed yet.
generic

net: skmsg: preserve sg.copy across SG transforms - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: skmsg: preserve sg.copy across SG transforms - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: skmsg: preserve sg.copy across SG transforms - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9bb86d8184b37503816150c4a6ad3c17dfdbe827
generic

net: skmsg: preserve sg.copy across SG transforms - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/406e8a651a7b854c41fecd5117bb282b3a6c2c6b
generic

net: skmsg: preserve sg.copy across SG transforms - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/31a110642b5fb5e61940cbcfb503445ac4f28017
generic

net: skmsg: preserve sg.copy across SG transforms - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/21ed9540a8e1906dfcbc1bb82ba9b4de4fa4bd6d
generic

net: skmsg: preserve sg.copy across SG transforms - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1acdd14c0990dd1cd4b6534f00366d2e6dfce05f
generic

net: skmsg: preserve sg.copy across SG transforms - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0eb4c16c4adb262763bda870a8ed38a1a9dec7ec

Vendor Advisories for CVE-2026-63830(2)

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

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-31.31) @ resolute2026-09-11ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1013.13) @ resolute2026-09-11ubuntu
ubuntulinux-tools-gcp-edge (7.0.0-1011.11~24.04.1) @ noble2026-09-11ubuntu

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

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (55 versions)5.10.262-1
linux-6.16.1.106-3~deb11u1 ... 6.1.176-1~deb11u1 (21 versions)6.1.177-1~deb11u1
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (54 versions)6.1.177-1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.95-1~bpo12+1 (29 versions)6.12.95-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (156 versions)7.1.3-1

Additional Vendor Advisories

(3)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 24× in last 7d / 218× 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 559 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-63830?
CVE-2026-63830 is a critical vulnerability published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: net: skmsg: preserve sg.copy across SG transforms The sk_msg sg.copy bitmap is part of the scatterlist entry ownership state. A set bit tells skmsgcomputedatapointers() not to expose the entry through writable BPF ctx->data. This…
When was CVE-2026-63830 disclosed?
CVE-2026-63830 was first published in the National Vulnerability Database on July 19, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-63830 actively exploited?
CVE-2026-63830 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 69.4% of all scored CVEs.
What is the CVSS score of CVE-2026-63830?
CVE-2026-63830 has a CVSS v3 base score of 9.4 (NVD).
How do I remediate CVE-2026-63830?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-63830, 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-63830

Explore →

Is Your Infrastructure Affected by CVE-2026-63830?

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