CVE-2026-98626

bpf: Restrict CO-RE poisoning to relocatable instructions

Description

In the Linux kernel, the following vulnerability has been resolved: bpf: Restrict CO-RE poisoning to relocatable instructions CO-RE relocation records can name any instruction offset. When a relocation cannot be resolved, bpf_core_patch_insn() currently poisons its target before checking whether that instruction is a valid relocation target. Malformed metadata can therefore replace jumps, calls, exits, register-source arithmetic, or non-immediate loads instead of failing at the relocation step. Handle poisoning only after the instruction has passed the same class and operand-form checks used for a resolved relocation. Route invalid forms through the existing diagnostic and return a hard error. Keep poisoning supported instructions, including both halves of a plain ldimm64, so an unresolved relocation in dead code remains valid. Extend bpf_core_poison_insn() to poison both halves of ldimm64, and return its status directly from each validated instruction case. This avoids routing the success path through a common label and leaves the helper free to report errors. The shared relocation code applies this restriction to both libbpf and in-kernel CO-RE.

Key facts

Published
18 Oct 2026
Last changed
19 Oct 2026
Assigned by
Linux
EPSS
0.212% likely to be exploited in the next 30 days, higher than 11.556% of CVEs (scores for 18 Nov 2026)

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
LinuxLinux
  • Default status: unaffected
  • d7a252708dbc950ca2064310217e8b9f85846e2f up to but excluding a8c47e62d9aea2d47a09e06c1682c59c21b92449 (affected)
  • d7a252708dbc950ca2064310217e8b9f85846e2f up to but excluding d3219c229d16900cef936adad28633c98946e432 (affected)
  • d7a252708dbc950ca2064310217e8b9f85846e2f up to but excluding a0b79cdfcf34b53c85bac2d3cf022fc1342eeca0 (affected)
  • d7a252708dbc950ca2064310217e8b9f85846e2f up to but excluding f2a24101e89dd0804e717da7c1bd6af513698aa2 (affected)
  • d7a252708dbc950ca2064310217e8b9f85846e2f up to but excluding 2d7d04357c41aa49a5ac658fcc207439f2ad6456 (affected)
  • d7a252708dbc950ca2064310217e8b9f85846e2f up to but excluding 8e4cbcca1e0a2fc5e6c8edb68e0cf5f2587f9319 (affected)
  • d7a252708dbc950ca2064310217e8b9f85846e2f up to but excluding 394ae398337c5f87e567f6cd63b937fc2b2f6ddc (affected)
LinuxLinux
  • Default status: affected
  • 5.6 (affected)
  • 0 up to but excluding 5.6 (unaffected)
  • 5.15.222 up to and including 5.15.* (unaffected)
  • 6.1.189 up to and including 6.1.* (unaffected)
  • 6.6.158 up to and including 6.6.* (unaffected)
  • 6.12.112 up to and including 6.12.* (unaffected)
  • 6.18.55 up to and including 6.18.* (unaffected)
  • 7.2.9 up to and including 7.2.* (unaffected)
  • 7.3 up to and including * (unaffected)

Timeline

  1. 18 Oct 2026 Published

References