CVE-2026-98626: kernel: bpf: Restrict CO-RE poisoning to relocatable instructions | OX.Radar
Breaking: Ruby2Shell - Ruby Memory Corruption Flaws Expose Applications to Remote Code Execution
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2026-98626

kernel: bpf: Restrict CO-RE poisoning to relocatable instructions

Overview

Published
18 Oct 2026
Modified
19 Oct 2026
Medium CVE
0 Registry packages
157 OS packages
7 Linux distributions
Yes Fix available

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.

Source: OX vulnerability database

Severity

4.4 · MEDIUM

CVSS 3.1 base score, scored by redhat.

Attack vector
Local
Attack complexity
Low
Privileges required
High
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H

Affected packages · 0

No registry package. This ID affects operating system packages only.

Operating systems · 87 fixes

Azure Linux 1 release · 1 package

fixed 1
kernel
Azure Linux fixes for CVE-2026-98626
ReleasePackageFixed in
3.0 kernel 0:6.6.159.1-1.azl3

Oracle Linux 2 releases · 2 packages

fixed 3
bpftool kernel-uek
Oracle Linux fixes for CVE-2026-98626
ReleasePackageFixed in
8 bpftool +13 5.15.0-326.222.4.el8uek
9 bpftool +2 5.15.0-326.222.4.el9uek
9 kernel-uek +34 6.12.0-208.112.5.el9uek

Photon OS 1 release · 1 package

fixed 1
bpftool
Photon OS fixes for CVE-2026-98626
ReleasePackageFixed in
5.0 bpftool +10 6.12.112-1.ph5

amazon linux 1 release · 4 packages

fixed 4
kernel-livepatch-6-1-189-236-399 bpftool bpftool6-12 bpftool6-18
amazon linux fixes for CVE-2026-98626
ReleasePackageFixed in
2023 kernel-livepatch-6-1-189-236-399 +2 1:1.0-0.amzn2023
2023 bpftool +17 1:6.1.189-236.399.amzn2023
2023 bpftool6-12 +16 1:6.12.113-138.209.amzn2023
2023 bpftool6-18 +17 1:6.18.56-125.164.amzn2023

debian 4 releases · 2 packages

affected 1 fixed 4
linux linux-6-12
debian fixes for CVE-2026-98626
ReleasePackageFixed in
11 linux affected
12 linux 6.1.190-1
12 linux-6-12 6.12.113-1~deb12u1
13 linux 6.12.113-1
14 linux 7.2.9-1

echo 1 release · 1 package

fixed 1
linux
echo fixes for CVE-2026-98626
ReleasePackageFixed in
linux 6.12.113-1

ubuntu 4 releases · 49 packages

fixed 69 affected 3
linux-nvidia-tegra-5-15 linux-ibm-5-15 linux-riscv-5-15 linux-intel-iotg-5-15 linux-oracle-5-15 linux-aws-5-15 +43
ubuntu fixes for CVE-2026-98626
ReleasePackageFixed in
20.04-ESM linux-nvidia-tegra-5-15 5.15.0-1070.72~20.04.1
20.04-ESM linux-ibm-5-15 5.15.0-1113.117~20.04.1
20.04-ESM linux-riscv-5-15 5.15.0-1113.117~20.04.2
20.04-ESM linux-intel-iotg-5-15 5.15.0-1114.120~20.04.1
20.04-ESM linux-oracle-5-15 5.15.0-1116.122~20.04.1
20.04-ESM linux-aws-5-15 5.15.0-1119.126~20.04.1

66 more rows

References

Show all 31 references

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.