Skip to main content
VulnerabilityPublished Updated

CVE-2026-53006: Linux kernel · ipv6: fix possible UAF in icmpv6_rcv()

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical · fixed in f996edd7615e686ada141b7f3395025729ff8ccb : 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.3% chance of exploitation in 30 days – higher than 33% 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 f996edd7615e686ada141b7f3395025729ff8ccb, aff0f28f5be803de2452ce702631c021fcd9ce8a, 0069813e6ca9309eca78022bcb3aeb1e9ef90a12 +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 24 Jun 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
  • ≥ 4b3418fba0fe819197e3359d5ddbef84ba2c59de, < f996edd7615e686ada141b7f3395025729ff8ccb
Fixed in
  • f996edd7615e686ada141b7f3395025729ff8ccb
LinuxLinuxAffected
  • ≥ 4b3418fba0fe819197e3359d5ddbef84ba2c59de, < aff0f28f5be803de2452ce702631c021fcd9ce8a
Fixed in
  • aff0f28f5be803de2452ce702631c021fcd9ce8a
LinuxLinuxAffected
  • ≥ 4b3418fba0fe819197e3359d5ddbef84ba2c59de, < 0069813e6ca9309eca78022bcb3aeb1e9ef90a12
Fixed in
  • 0069813e6ca9309eca78022bcb3aeb1e9ef90a12
LinuxLinuxAffected
  • ≥ 4b3418fba0fe819197e3359d5ddbef84ba2c59de, < 085e31a811ef234ef8c3e219c4636dfebfe7e10f
Fixed in
  • 085e31a811ef234ef8c3e219c4636dfebfe7e10f
LinuxLinuxAffected
  • ≥ 4b3418fba0fe819197e3359d5ddbef84ba2c59de, < 38bdbc897c0d83a3e2b925a51b69420f1feba29a
Fixed in
  • 38bdbc897c0d83a3e2b925a51b69420f1feba29a
LinuxLinuxAffected
  • ≥ 4b3418fba0fe819197e3359d5ddbef84ba2c59de, < 7c66b368c6ff453f99cb39d84af93e908e51eef2
Fixed in
  • 7c66b368c6ff453f99cb39d84af93e908e51eef2

Description

In the Linux kernel, the following vulnerability has been resolved: ipv6: fix possible UAF in icmpv6_rcv() Caching saddr and daddr before pskb_pull() is problematic since skb->head can change. Remove these temporary variables: - We only access &ipv6_hdr(skb)->saddr and &ipv6_hdr(skb)->daddr when net_dbg_ratelimited() is called in the slow path. - Avoid potential future misuse after pskb_pull() call.

References

Community reviews

Loading reviews…