Skip to main content
VulnerabilityPublished Updated

CVE-2026-89564: Linux kernel · ip: orphan prefetched skbs before multicast forwarding

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · CVSS 7.8 High · fixed in f1281d4b99089fbaf0d3579bba62a814ebb4de4d : patch Linux kernel soon.

Data as of 26 Oct 2026, 13:47 UTC

CVSS 3.1 base score
7.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 3% 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 cannot 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 f1281d4b99089fbaf0d3579bba62a814ebb4de4d, e62aef7d6a5b27569bf540bbe11a9482117ff588, e36ce6e78fe3fc3c071a26750783b7ba081ce10d +2
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 Sep 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
  • ≥ cf7fbe660f2dbd738ab58aea8e9b0ca6ad232449, < f1281d4b99089fbaf0d3579bba62a814ebb4de4d
Fixed in
  • f1281d4b99089fbaf0d3579bba62a814ebb4de4d
LinuxLinuxAffected
  • ≥ cf7fbe660f2dbd738ab58aea8e9b0ca6ad232449, < e62aef7d6a5b27569bf540bbe11a9482117ff588
Fixed in
  • e62aef7d6a5b27569bf540bbe11a9482117ff588
LinuxLinuxAffected
  • ≥ cf7fbe660f2dbd738ab58aea8e9b0ca6ad232449, < e36ce6e78fe3fc3c071a26750783b7ba081ce10d
Fixed in
  • e36ce6e78fe3fc3c071a26750783b7ba081ce10d
LinuxLinuxAffected
  • ≥ cf7fbe660f2dbd738ab58aea8e9b0ca6ad232449, < a8af6fbac895f057c4b8ff8a2e3fb4c5827fe4ce
Fixed in
  • a8af6fbac895f057c4b8ff8a2e3fb4c5827fe4ce
LinuxLinuxAffected
  • ≥ cf7fbe660f2dbd738ab58aea8e9b0ca6ad232449, < 882212d317a7c16ab70d20656f6b1c42abada9f6
Fixed in
  • 882212d317a7c16ab70d20656f6b1c42abada9f6
LinuxLinuxAffected
  • =5.7
Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: ip: orphan prefetched skbs before multicast forwarding IPv4 and IPv6 input preserve an skb->sk association installed by bpf_sk_assign() so that local delivery can use the selected socket under RCU. Both address families can also prefetch a socket in UDP early demux. In both paths (BPF and UDP early demux) a reference is not guaranteed to be held on the socket. When a multicast packet is not locally deliverable, IPv6 hands the original skb to ip6_mr_input(). IPv4's ip_mr_input() similarly keeps the original skb when local delivery is not needed. Either path can put the skb on an unresolved multicast route queue or forward it after the receive-side RCU section ends. After the prefetched socket is destroyed, a later skb free invokes sock_pfree() and dereferences the stale skb->sk. Orphan the skb before each non-local multicast forwarding path. Local delivery retains the original skb; the existing skb_clone() calls provide multicast forwarding with a socket-free clone.

References

Community reviews

Loading reviews…