Skip to main content
VulnerabilityPublished Updated

CVE-2026-63830: Linux kernel · net: skmsg: preserve sg.copy across SG transforms

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · CVSS 9.4 Critical · fixed in f126eed589eec6f201405abbc398844042ef6d57 : patch Linux kernel as a priority.

Data as of 26 Oct 2026, 11:54 UTC

CVSS 3.1 base score
9.4Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 38% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers can reliably automate steps 1–4 of the kill chain
Technical impact
Total control over the software or total information disclosure

CISA SSVC assessment, 2026-10-16.

Patch
Available – fixed in f126eed589eec6f201405abbc398844042ef6d57, d22cc92bc41290e5783a72375e0843d9435f6001, 406e8a651a7b854c41fecd5117bb282b3a6c2c6b +5
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ d3b18ad31f93d0b6bae105c679018a1ba7daa9ca, < f126eed589eec6f201405abbc398844042ef6d57
Fixed in
  • f126eed589eec6f201405abbc398844042ef6d57
LinuxLinuxAffected
  • ≥ d3b18ad31f93d0b6bae105c679018a1ba7daa9ca, < d22cc92bc41290e5783a72375e0843d9435f6001
Fixed in
  • d22cc92bc41290e5783a72375e0843d9435f6001
LinuxLinuxAffected
  • ≥ d3b18ad31f93d0b6bae105c679018a1ba7daa9ca, < 406e8a651a7b854c41fecd5117bb282b3a6c2c6b
Fixed in
  • 406e8a651a7b854c41fecd5117bb282b3a6c2c6b
LinuxLinuxAffected
  • ≥ d3b18ad31f93d0b6bae105c679018a1ba7daa9ca, < 31a110642b5fb5e61940cbcfb503445ac4f28017
Fixed in
  • 31a110642b5fb5e61940cbcfb503445ac4f28017
LinuxLinuxAffected
  • ≥ d3b18ad31f93d0b6bae105c679018a1ba7daa9ca, < 21ed9540a8e1906dfcbc1bb82ba9b4de4fa4bd6d
Fixed in
  • 21ed9540a8e1906dfcbc1bb82ba9b4de4fa4bd6d
LinuxLinuxAffected
  • ≥ d3b18ad31f93d0b6bae105c679018a1ba7daa9ca, < 9bb86d8184b37503816150c4a6ad3c17dfdbe827
Fixed in
  • 9bb86d8184b37503816150c4a6ad3c17dfdbe827

Description

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.

References

Community reviews

Loading reviews…