cbcvebase.
CVE-2026-64007
published 2026-07-19

CVE-2026-64007: In the Linux kernel, the following vulnerability has been resolved: netfilter: synproxy: refresh tcphdr after skb_ensure_writable synproxy_tstamp_adjust()…

PriorityP355critical9.8CVSS 3.1
AVNACLPRNUINSUCHIHAH
EPSS
0.51%
42.0th percentile
In the Linux kernel, the following vulnerability has been resolved: netfilter: synproxy: refresh tcphdr after skb_ensure_writable synproxy_tstamp_adjust() rewrites the TCP timestamp option in place and then patches the TCP checksum via inet_proto_csum_replace4() on the caller-supplied tcphdr pointer. Both ipv4_synproxy_hook() and ipv6_synproxy_hook() obtain that pointer with skb_header_pointer() before calling in, so it may either alias skb->head directly or point at the caller's on-stack _tcph buffer. Between obtaining the pointer and using it, the function calls skb_ensure_writable(skb, optend), which on a cloned or non-linear skb invokes pskb_expand_head() and frees the old skb->head. After that point the cached th is stale: caller (ipv[46]_synproxy_hook) th = skb_header_pointer(skb, ..., &_tcph) synproxy_tstamp_adjust(skb, protoff, th, ...) skb_ensure_writable(skb, optend) pskb_expand_head() /* kfree(old skb->head) */ ... inet_proto_csum_replace4(&th->check, ...) /* writes into freed head, or into the caller's stack copy leaving the on-wire checksum stale */ The option bytes are written through skb->data and are fine; only the checksum update goes through th and so lands in the wrong place. The result is either a write into freed slab memory or a packet leaving with a checksum that does not match its payload. Fix by re-deriving th from skb->data + protoff immediately after skb_ensure_writable() succeeds, so the subsequent checksum update targets the linear, writable header.

Affected

53 ranges· showing 25
VendorProductVersion rangeFixed in
linuxlinux——
linuxlinux>= 48b1de4c110a7afa4b85862f6c75af817db26fad < 9902a1058992de5d95656b64a3bd95c077f7ba2c9902a1058992de5d95656b64a3bd95c077f7ba2c
linuxlinux>= 48b1de4c110a7afa4b85862f6c75af817db26fad < d3019c61799adc21811af4b521f11f3dc77f8e04d3019c61799adc21811af4b521f11f3dc77f8e04
linuxlinux>= 48b1de4c110a7afa4b85862f6c75af817db26fad < dd206819f210522579010d889d45a9530bb494bcdd206819f210522579010d889d45a9530bb494bc
linuxlinux>= 48b1de4c110a7afa4b85862f6c75af817db26fad < af2c22ccb1f621aff487ff47a040e38e058541e7af2c22ccb1f621aff487ff47a040e38e058541e7
linuxlinux>= 48b1de4c110a7afa4b85862f6c75af817db26fad < c7f945f7da097245a2f8ed7775ce48421047ee96c7f945f7da097245a2f8ed7775ce48421047ee96
linuxlinux>= 48b1de4c110a7afa4b85862f6c75af817db26fad < f0fea2b6d5453a11ad11713bbf37561b9b3a7edff0fea2b6d5453a11ad11713bbf37561b9b3a7edf
linuxlinux>= 48b1de4c110a7afa4b85862f6c75af817db26fad < a91887a5b6ee4b98dfbf1db657ed2b879430149ea91887a5b6ee4b98dfbf1db657ed2b879430149e
linuxlinux>= 48b1de4c110a7afa4b85862f6c75af817db26fad < 92170e6afe927ab2792a3f71902845789c8e31b192170e6afe927ab2792a3f71902845789c8e31b1
ubuntulinux——
ubuntulinux-aws——
ubuntulinux-aws-6.8——
ubuntulinux-aws-fips——
ubuntulinux-azure——
ubuntulinux-azure-6.8——
ubuntulinux-azure-7.0——
ubuntulinux-azure-fde——
ubuntulinux-azure-fde-6.8——
ubuntulinux-azure-fips——
ubuntulinux-fips——
ubuntulinux-gcp——
ubuntulinux-gcp-5.15——
ubuntulinux-gcp-6.8——
ubuntulinux-gcp-7.0——
ubuntulinux-gcp-fips——

CVSS provenance

nvdv3.19.8CRITICALCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
vendor_redhat9.8CRITICAL
vendor_ubuntu9.4CRITICAL
Stop checking back — get the weekly exploitation signal.

Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.