CVE-2026-63830
CVE CVE-2026-63830EUVD EUVD-2026-45496Published 2026-07-19T12:02:23.000ZLast changed 2026-08-05T12:36:13.000ZCVSS 9.4
What the advisory describes
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.
Source: EUVD (ENISA), in the words of the advisory.
Products the advisory names
These come from the advisory itself, not from any check we performed.
- Linux — Linux d3b18ad31f93d0b6bae105c679018a1ba7daa9ca <31a110642b5fb5e61940cbcfb503445ac4f28017; patch: 5.10.261; patch: 6.18.38; d3b18ad31f93d0b6bae105c679018a1ba7daa9ca <1acdd14c0990dd1cd4b6534f00366d2e6dfce05f; patch: 0; d3b18ad31f93d0b6bae105c679018a1ba7daa9ca <21ed9540a8e1906dfcbc1bb82ba9b4de4fa4bd6d; patch: 5.15.212; patch: 6.1.177; 4.20; d3b18ad31f93d0b6bae105c679018a1ba7daa9ca <0eb4c16c4adb262763bda870a8ed38a1a9dec7ec; d3b18ad31f93d0b6bae105c679018a1ba7daa9ca <f126eed589eec6f201405abbc398844042ef6d57; patch: 7.2-rc1; d3b18ad31f93d0b6bae105c679018a1ba7daa9ca <d22cc92bc41290e5783a72375e0843d9435f6001; patch: 7.1.3; patch: 6.6.144; d3b18ad31f93d0b6bae105c679018a1ba7daa9ca <9bb86d8184b37503816150c4a6ad3c17dfdbe827; d3b18ad31f93d0b6bae105c679018a1ba7daa9ca <406e8a651a7b854c41fecd5117bb282b3a6c2c6b; patch: 6.12.95
The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.
Carried in the product catalogue
An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.
- Linux — Linux
Does this concern one of your customers?
This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.
Try it for 28 daysPatchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.