CVE-2026-98626bpf: Restrict CO-RE poisoning to relocatable instructions
- —Not scoredno CVSS score yet
- 0.21%Exploitation in 30 daysEPSS · top 88% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Linux
- 23 days later
· 23 days later
Published
- 1 day later
· 1 day later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.21% · top 88% of all CVEs (17 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected d7a252708dbc950ca2064310217e8b9f85846e2f – < a8c47e62d9aea2d47a09e06c1682c59c21b92449
- affected d7a252708dbc950ca2064310217e8b9f85846e2f – < d3219c229d16900cef936adad28633c98946e432
- affected d7a252708dbc950ca2064310217e8b9f85846e2f – < a0b79cdfcf34b53c85bac2d3cf022fc1342eeca0
- affected d7a252708dbc950ca2064310217e8b9f85846e2f – < f2a24101e89dd0804e717da7c1bd6af513698aa2
- affected d7a252708dbc950ca2064310217e8b9f85846e2f – < 2d7d04357c41aa49a5ac658fcc207439f2ad6456
- affected d7a252708dbc950ca2064310217e8b9f85846e2f – < 8e4cbcca1e0a2fc5e6c8edb68e0cf5f2587f9319
- affected d7a252708dbc950ca2064310217e8b9f85846e2f – < 394ae398337c5f87e567f6cd63b937fc2b2f6ddc
- affected 5.6
- unaffected < 5.6
- unaffected 5.15.222 – ≤ 5.15.*
- unaffected 6.1.189 – ≤ 6.1.*
- unaffected 6.6.158 – ≤ 6.6.*
- unaffected 6.12.112 – ≤ 6.12.*
- unaffected 6.18.55 – ≤ 6.18.*
- unaffected 7.2.9 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References7
- https://git.kernel.org/stable/c/a8c47e62d9aea2d47a09e06c1682c59c21b92449 (opens in a new tab)
- https://git.kernel.org/stable/c/d3219c229d16900cef936adad28633c98946e432 (opens in a new tab)
- https://git.kernel.org/stable/c/a0b79cdfcf34b53c85bac2d3cf022fc1342eeca0 (opens in a new tab)
- https://git.kernel.org/stable/c/f2a24101e89dd0804e717da7c1bd6af513698aa2 (opens in a new tab)
- https://git.kernel.org/stable/c/2d7d04357c41aa49a5ac658fcc207439f2ad6456 (opens in a new tab)
- https://git.kernel.org/stable/c/8e4cbcca1e0a2fc5e6c8edb68e0cf5f2587f9319 (opens in a new tab)
- https://git.kernel.org/stable/c/394ae398337c5f87e567f6cd63b937fc2b2f6ddc (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-103540 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-98626)Record last updated .