BaselineWatch
Desk

CVE-2026-98626

unscored Published

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.

Fix

Microsoft's update · Important

  • Release Notes — azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 · build 6.6.159.1-1

From the 2026-Oct release note of Microsoft's Security Update Guide, revised 2026-10-29.

Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.

Change history 2

  1. StatusReceived → PublishedNVD modified 2026-10-19 09:22
  2. First seenunscoredNVD modified 2026-10-19 10:19

Affected (CPE criteria) 0

NVD has not attached CPE configurations yet.

References 7