Skip to main content
VulnerabilityPublished Updated

CVE-2026-63993: Linux kernel · Use After Free

Affects Linux kernelSource CVE Database V5

0

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

Data as of 26 Oct 2026, 14:05 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 dc3bfa050f873371e745bdf478b1f5b738e5733d, a493efd4336cf19122ae0e4cbb3d31b32d70deea, 5303925e360527243b46a440a04667826bbc72b7 +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
  • ≥ 4cb47a8644cc9eb8ec81190a50e79e6530d0297f, < dc3bfa050f873371e745bdf478b1f5b738e5733d
Fixed in
  • dc3bfa050f873371e745bdf478b1f5b738e5733d
LinuxLinuxAffected
  • ≥ 4cb47a8644cc9eb8ec81190a50e79e6530d0297f, < a493efd4336cf19122ae0e4cbb3d31b32d70deea
Fixed in
  • a493efd4336cf19122ae0e4cbb3d31b32d70deea
LinuxLinuxAffected
  • ≥ 4cb47a8644cc9eb8ec81190a50e79e6530d0297f, < 5303925e360527243b46a440a04667826bbc72b7
Fixed in
  • 5303925e360527243b46a440a04667826bbc72b7
LinuxLinuxAffected
  • ≥ 4cb47a8644cc9eb8ec81190a50e79e6530d0297f, < 9257f56ac47ef1976bcd056cf986a9988eeec67a
Fixed in
  • 9257f56ac47ef1976bcd056cf986a9988eeec67a
LinuxLinuxAffected
  • ≥ 4cb47a8644cc9eb8ec81190a50e79e6530d0297f, < 609e63312c29aad18026a1d3222e123d4b6b0feb
Fixed in
  • 609e63312c29aad18026a1d3222e123d4b6b0feb
LinuxLinuxAffected
  • ≥ 4cb47a8644cc9eb8ec81190a50e79e6530d0297f, < 8d435d68d71fb875876b722f4136caf74f2f48bd
Fixed in
  • 8d435d68d71fb875876b722f4136caf74f2f48bd

Description

In the Linux kernel, the following vulnerability has been resolved: vxlan: do not reuse cached ip_hdr() value after skb_tunnel_check_pmtu() skb_tunnel_check_pmtu() can change skb->head. Reusing old_iph afer skb_tunnel_check_pmtu() can cause an UAF. Use instead ip_hdr(skb) as done in drivers/net/bareudp.c and drivers/net/geneve.c. Found by Sashiko.

References

Community reviews

Loading reviews…