CVE-2026-63912: Linux kernel · xfrm: esp: restore combined single-frag length gate
Affects Linux kernelSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical · fixed in dfa0d7b0ff1eb6b2c416b8fdb9b4f2cefba57a40 : patch Linux kernel as a priority.
Data as of 26 Oct 2026, 13:47 UTC
- EPSS
- 0.7% chance of exploitation in 30 days – higher than 53% 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 dfa0d7b0ff1eb6b2c416b8fdb9b4f2cefba57a40, c093468aea8277f77272a4f199b2e15e19cabb59, b84091ceddc9f133229dceab3ccc930bf27f9cba +11
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 19 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
Description
In the Linux kernel, the following vulnerability has been resolved: xfrm: esp: restore combined single-frag length gate The ESP out-of-place fast path appends the trailer in esp_output_head() before esp_output_tail() allocates the destination page frag. The head-side gate currently checks skb->data_len and tailen separately, but the tail code allocates a single destination frag from the combined post-trailer skb->data_len. Reject the page-frag fast path when the combined aligned length exceeds a page. Otherwise skb_page_frag_refill() may fall back to a single page while the destination sg still spans the combined skb->data_len. Restore this combined-length page gate for both IPv4 and IPv6.
References
- git.kernel.org/stable/c/566295735530ee513326049b0540f32ec050bf2e (opens in a new tab)
- git.kernel.org/stable/c/5d7ab86e2b6bc23054616bf6ac562013bf60af8c (opens in a new tab)
- git.kernel.org/stable/c/36519e3d941fc99d3b52c134dbaf311f987a4708 (opens in a new tab)
- git.kernel.org/stable/c/322e48187e0245ab2fff6fec2220b0cae677dbec (opens in a new tab)
- git.kernel.org/stable/c/b84091ceddc9f133229dceab3ccc930bf27f9cba (opens in a new tab)
- git.kernel.org/stable/c/c093468aea8277f77272a4f199b2e15e19cabb59 (opens in a new tab)
- git.kernel.org/stable/c/65f3b3fc2347b89fe21db1e92c7681368415f095 (opens in a new tab)
- git.kernel.org/stable/c/dfa0d7b0ff1eb6b2c416b8fdb9b4f2cefba57a40 (opens in a new tab)