CVE-2026-98626: bpf: Restrict CO-RE poisoning to relocatable instructions
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.21% (FIRST EPSS).
- Fixed version: Linux Linux 2d7d04357c41aa49a5ac658fcc207439f2ad6456, 394ae398337c5f87e567f6cd63b937fc2b2f6ddc, 8e4cbcca1e0a2fc5e6c8edb68e0cf5f2587f9319; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.159.1-1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 2d7d04357c41aa49a5ac658fcc207439f2ad6456, 394ae398337c5f87e567f6cd63b937fc2b2f6ddc, 8e4cbcca1e0a2fc5e6c8edb68e0cf5f2587f9319; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.159.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Oct 18, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.2% · 11th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.6affected
- d7a252708dbc950ca2064310217e8b9f85846e2f and later · before a8c47e62d9aea2d47a09e06c1682c59c21b92449affected · git
- d7a252708dbc950ca2064310217e8b9f85846e2f and later · before d3219c229d16900cef936adad28633c98946e432affected · git
- d7a252708dbc950ca2064310217e8b9f85846e2f and later · before a0b79cdfcf34b53c85bac2d3cf022fc1342eeca0affected · git
- d7a252708dbc950ca2064310217e8b9f85846e2f and later · before f2a24101e89dd0804e717da7c1bd6af513698aa2affected · git
- d7a252708dbc950ca2064310217e8b9f85846e2f and later · before 2d7d04357c41aa49a5ac658fcc207439f2ad6456affected · git
- d7a252708dbc950ca2064310217e8b9f85846e2f and later · before 8e4cbcca1e0a2fc5e6c8edb68e0cf5f2587f9319affected · git
- d7a252708dbc950ca2064310217e8b9f85846e2f and later · before 394ae398337c5f87e567f6cd63b937fc2b2f6ddcaffected · git
- before 5.6not affected · semver
- 5.15.222 and later · up to and including 5.15.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.190-1 | 6.1.190-1 |
| Debian:12 | linux-6.12 | before 6.12.113-1~deb12u1 | 6.12.113-1~deb12u1 |
| Debian:13 | linux | before 6.12.113-1 | 6.12.113-1 |
| Debian:14 | linux | before 7.2.9-1 | 7.2.9-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-98624Oct 18, 2026 · netfilter: nfnetlink_queue: hold nfnl mutex in event notifier0Monitor
- ← EarlierCVE-2026-98625Oct 18, 2026 · netfilter: flowtable: publish HW_DEAD after worker is done0Monitor
- Later →CVE-2026-98627Oct 18, 2026 · bpf: Preserve packet pointer class displacement in regsafe()0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 2d7d04357c41aa49a5ac658fcc207439f2ad6456 | Vendor (CNA) |
| Linux Linux | 394ae398337c5f87e567f6cd63b937fc2b2f6ddc | Vendor (CNA) |
| Linux Linux | 8e4cbcca1e0a2fc5e6c8edb68e0cf5f2587f9319 | Vendor (CNA) |
| Linux Linux | a0b79cdfcf34b53c85bac2d3cf022fc1342eeca0 | Vendor (CNA) |
| Linux Linux | a8c47e62d9aea2d47a09e06c1682c59c21b92449 | Vendor (CNA) |
| Linux Linux | d3219c229d16900cef936adad28633c98946e432 | Vendor (CNA) |
| Linux Linux | f2a24101e89dd0804e717da7c1bd6af513698aa2 | Vendor (CNA) |
| azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | 6.6.159.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.190-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.113-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- Fix recordedsame day
- TodayNov 7, 2026+20 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-1351 · Oct 19, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Exploit maturity— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- git.kernel.org/stable/c/394ae398337c5f87e567f6cd63b937fc2b2f6ddc
- git.kernel.org/stable/c/8e4cbcca1e0a2fc5e6c8edb68e0cf5f2587f9319
- git.kernel.org/stable/c/a0b79cdfcf34b53c85bac2d3cf022fc1342eeca0
- git.kernel.org/stable/c/a8c47e62d9aea2d47a09e06c1682c59c21b92449
- git.kernel.org/stable/c/d3219c229d16900cef936adad28633c98946e432
- git.kernel.org/stable/c/f2a24101e89dd0804e717da7c1bd6af513698aa2
Vendor advisories and official records. Exploit/PoC links are deliberately left out.