Skip to main content
VulnerabilityPublished

CVE-2026-63992: Linux kernel · tunnels: do not assume transport header in iptunnel_pmtud_check_icmp()

Source GCVE Database

0
Authoritative record:CVE-2026-63992· Critical 9.1

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

Data as of 26 Oct 2026, 15:59 UTC

CVSS 3.1 base score
9.1Critical
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.
Patch
Available – fixed in e917d0c69f01af2bb4fbea2b66d560a53b3ac7ec, cb549df9ce4ee15c9d5b19ddab12cf2128e4313c, c7b7ec3e69e673c0d6b57f74d21da50c485c598e +5
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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, < e917d0c69f01af2bb4fbea2b66d560a53b3ac7ec
Fixed in
  • e917d0c69f01af2bb4fbea2b66d560a53b3ac7ec
LinuxLinuxAffected
  • ≥ 4cb47a8644cc9eb8ec81190a50e79e6530d0297f, < cb549df9ce4ee15c9d5b19ddab12cf2128e4313c
Fixed in
  • cb549df9ce4ee15c9d5b19ddab12cf2128e4313c
LinuxLinuxAffected
  • ≥ 4cb47a8644cc9eb8ec81190a50e79e6530d0297f, < c7b7ec3e69e673c0d6b57f74d21da50c485c598e
Fixed in
  • c7b7ec3e69e673c0d6b57f74d21da50c485c598e
LinuxLinuxAffected
  • ≥ 4cb47a8644cc9eb8ec81190a50e79e6530d0297f, < a096b6e34f602950af9a2b0856cd93a5f4c276d7
Fixed in
  • a096b6e34f602950af9a2b0856cd93a5f4c276d7
LinuxLinuxAffected
  • ≥ 4cb47a8644cc9eb8ec81190a50e79e6530d0297f, < 509323077ef79a26ba0c60bb556e45c12c398b2d
Fixed in
  • 509323077ef79a26ba0c60bb556e45c12c398b2d
LinuxLinuxAffected
  • ≥ 4cb47a8644cc9eb8ec81190a50e79e6530d0297f, < 43368636c663cff6e59dde93cf4b8e43ac28eb93
Fixed in
  • 43368636c663cff6e59dde93cf4b8e43ac28eb93

AI-suggested

A fix has been implemented in the Linux kernel to address this vulnerability. Users should apply the official kernel updates that include this patch. Since this is a kernel-level issue, updating to the patched kernel version is the recommended remediation.

Description

In the Linux kernel, the following vulnerability has been resolved: tunnels: do not assume transport header in iptunnel_pmtud_check_icmp() In some cases, iptunnel_pmtud_check_icmp() can be called while skb transport header is not set. This triggers an out-of-bound access, because (typeof(skb->transport_header))~0U is 65535. Access the icmp header based on IPv4 network header, after making sure icmp->type is present in skb linear part. Note that iptunnel_pmtud_check_icmpv6()) is fine.

References

Community reviews

Loading reviews…