GPU VulnDB

Database/Kernel, userspace & hypervisor

Linux kernel skbuff: coalescing drops SKBFL_SHARED_FRAG, letting ESP decrypt in place over shared pages

CVSS 7.8CVE-2026-46300Kernel, userspace & hypervisorKnown exploitedcurated

Impact

skb_try_coalesce() moves paged fragments from one socket buffer to another but loses the SKBFL_SHARED_FRAG marker, so the destination skb no longer advertises that its pages are externally owned or page-cache backed. ESP input relies on skb_has_shared_frag() to decide whether it may skip skb_cow_data() and decrypt in place; with the marker gone it can write plaintext directly over pages that belong to the page cache or another owner. On a GPU node this is a host kernel memory-integrity bug in the receive path, reachable through ordinary TCP receive coalescing plus IPsec, and the fix lands in the host kernel rather than in anything a tenant controls. The record is scored local (AV:L, PR:L) with high confidentiality, integrity and availability impact, and it is listed in CISA KEV. The upstream commit series is public; no exploitation detail is in the record.

Who can reach it

Local, authenticated low-privilege context per the CVSS vector, on a host that terminates IPsec/ESP traffic and performs TCP receive coalescing. Not reachable unless the node actually processes ESP input; a GPU node with no IPsec termination is not exposed through this path.

What to do

Take the stable-kernel fix for your series (five backport commits are referenced) or the distribution kernel update - Red Hat has it queued for RHEL 8 and RHEL 10 streams including the NVIDIA-for-RHEL-10 kernel. A kernel fix of this kind cannot be hot-patched in place by an operator, so each node must be drained and rebooted onto the new kernel; schedule that against jobs that cannot be checkpointed. No vendor-stated mitigation short of patching appears in the record.

References

Related entries

All Kernel, userspace & hypervisor entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.