Skip to main content
VulnerabilityPublished Updated

CVE-2026-64007: Linux kernel · netfilter: synproxy: refresh tcphdr after skb_ensure_writable

Affects Linux kernelSource CVE Database V5

0

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

Data as of 26 Oct 2026, 13:07 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 43% 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 f0fea2b6d5453a11ad11713bbf37561b9b3a7edf, dd206819f210522579010d889d45a9530bb494bc, d3019c61799adc21811af4b521f11f3dc77f8e04 +5
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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
  • ≥ 48b1de4c110a7afa4b85862f6c75af817db26fad, < f0fea2b6d5453a11ad11713bbf37561b9b3a7edf
Fixed in
  • f0fea2b6d5453a11ad11713bbf37561b9b3a7edf
LinuxLinuxAffected
  • ≥ 48b1de4c110a7afa4b85862f6c75af817db26fad, < dd206819f210522579010d889d45a9530bb494bc
Fixed in
  • dd206819f210522579010d889d45a9530bb494bc
LinuxLinuxAffected
  • ≥ 48b1de4c110a7afa4b85862f6c75af817db26fad, < d3019c61799adc21811af4b521f11f3dc77f8e04
Fixed in
  • d3019c61799adc21811af4b521f11f3dc77f8e04
LinuxLinuxAffected
  • ≥ 48b1de4c110a7afa4b85862f6c75af817db26fad, < c7f945f7da097245a2f8ed7775ce48421047ee96
Fixed in
  • c7f945f7da097245a2f8ed7775ce48421047ee96
LinuxLinuxAffected
  • ≥ 48b1de4c110a7afa4b85862f6c75af817db26fad, < af2c22ccb1f621aff487ff47a040e38e058541e7
Fixed in
  • af2c22ccb1f621aff487ff47a040e38e058541e7
LinuxLinuxAffected
  • ≥ 48b1de4c110a7afa4b85862f6c75af817db26fad, < a91887a5b6ee4b98dfbf1db657ed2b879430149e
Fixed in
  • a91887a5b6ee4b98dfbf1db657ed2b879430149e

Description

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.

References

Community reviews

Loading reviews…