CVE-2026-98626bpf: Restrict CO-RE poisoning to relocatable instructions
Updated under an hour ago ()
Does this affect you?
It affects Linux. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
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.
- CVSS
- Not yet scored
- Weakness (CWE)
- Not given
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Linux
- NVD analysis
- Received
- Record last updated
- Oct 18, 2026
- First seen by InfoSec Signals
- Oct 18, 2026
Affected products
Linux Linux linux:linux (from the name) | from d7a252708dbc950ca2064310217e8b9f85846e2f before a8c47e62d9aea2d47a09e06c1682c59c21b92449; from d7a252708dbc950ca2064310217e8b9f85846e2f before d3219c229d16900cef936adad28633c98946e432; from d7a252708dbc950ca2064310217e8b9f85846e2f before a0b79cdfcf34b53c85bac2d3cf022fc1342eeca0; from d7a252708dbc950ca2064310217e8b9f85846e2f before f2a24101e89dd0804e717da7c1bd6af513698aa2; from d7a252708dbc950ca2064310217e8b9f85846e2f before 2d7d04357c41aa49a5ac658fcc207439f2ad6456; from d7a252708dbc950ca2064310217e8b9f85846e2f before 8e4cbcca1e0a2fc5e6c8edb68e0cf5f2587f9319; from d7a252708dbc950ca2064310217e8b9f85846e2f before 394ae398337c5f87e567f6cd63b937fc2b2f6ddc | CNA record |
References
- https://git.kernel.org/stable/c/a8c47e62d9aea2d47a09e06c1682c59c21b92449
- https://git.kernel.org/stable/c/d3219c229d16900cef936adad28633c98946e432
- https://git.kernel.org/stable/c/a0b79cdfcf34b53c85bac2d3cf022fc1342eeca0
- https://git.kernel.org/stable/c/f2a24101e89dd0804e717da7c1bd6af513698aa2
- https://git.kernel.org/stable/c/2d7d04357c41aa49a5ac658fcc207439f2ad6456
- https://git.kernel.org/stable/c/8e4cbcca1e0a2fc5e6c8edb68e0cf5f2587f9319
- https://git.kernel.org/stable/c/394ae398337c5f87e567f6cd63b937fc2b2f6ddc
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.