CVE-2026-98075: bpf: reject BPF_PSEUDO_FUNC reference to the main program
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.17% (FIRST EPSS).
- Fixed version: Linux Linux 118212417ba0120d99f84154799f8880f07411f4, 314c8caa9cb64ad60c5b969fe9a3e2dcdccf156f, 374b2c5561db80fcdd7cdce44af37a49416f61c7; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.158.1-1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 118212417ba0120d99f84154799f8880f07411f4, 314c8caa9cb64ad60c5b969fe9a3e2dcdccf156f, 374b2c5561db80fcdd7cdce44af37a49416f61c7; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.158.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: reject BPF_PSEUDO_FUNC reference to the main program fixups.c:jit_subprogs() rewrites BPF_PSEUDO_FUNC loads to contain real function addresses. This function is invoked from bpf_jit_subprogs() only when env->subprog_cnt > 1. Meaning that for any program like below: int main(void *ctx) { void *ptr = main; ... bpf_timer_set_callback(..., ptr); ... } The 'ptr' won't be ever converted to contain an address. In combination with e.g. bpf_timer_set_callback() this would lead to a function call at a bogus address. Instead of complicating the implementation, just assume that no useful program needs main to be a sync or async callback and reject BPF_PSEUDO_FUNC loads for the main subprogram.
- Published
- Sep 25, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 6th 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.1%
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.13affected
- 69c087ba6225b574afb6e505b72cb75242a3d844 and later · before c74750dca96f40a1adb9d334f5a3152f44b270c3affected · git
- 69c087ba6225b574afb6e505b72cb75242a3d844 and later · before 314c8caa9cb64ad60c5b969fe9a3e2dcdccf156faffected · git
- 69c087ba6225b574afb6e505b72cb75242a3d844 and later · before 8cb75f7ada25b1cf25f2f74dec3ba649b9064a09affected · git
- 69c087ba6225b574afb6e505b72cb75242a3d844 and later · before 118212417ba0120d99f84154799f8880f07411f4affected · git
- 69c087ba6225b574afb6e505b72cb75242a3d844 and later · before d6c39774ae093c9f7009cc4ae918f18fc1af7ae7affected · git
- 69c087ba6225b574afb6e505b72cb75242a3d844 and later · before 92f0bd0e2b632c6565ac2214a4d7d2ed37e5b9f6affected · git
- 69c087ba6225b574afb6e505b72cb75242a3d844 and later · before 374b2c5561db80fcdd7cdce44af37a49416f61c7affected · git
- before 5.13not 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.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.2.7-1 | 7.2.7-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-98073Sep 25, 2026 · net: Remove conflicting altnames for dying netns in __dev_change_net_namespace().31Monitor
- ← EarlierCVE-2026-98074Sep 25, 2026 · bonding: do not clear curr_active_slave prematurely when releasing all slaves0Monitor
- Later →CVE-2026-98076Sep 25, 2026 · tracing/probes: Fix use-after-free on field name/type of events with multiple probes0Monitor
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 | 118212417ba0120d99f84154799f8880f07411f4 | Vendor (CNA) |
| Linux Linux | 314c8caa9cb64ad60c5b969fe9a3e2dcdccf156f | Vendor (CNA) |
| Linux Linux | 374b2c5561db80fcdd7cdce44af37a49416f61c7 | Vendor (CNA) |
| Linux Linux | 8cb75f7ada25b1cf25f2f74dec3ba649b9064a09 | Vendor (CNA) |
| Linux Linux | 92f0bd0e2b632c6565ac2214a4d7d2ed37e5b9f6 | Vendor (CNA) |
| Linux Linux | c74750dca96f40a1adb9d334f5a3152f44b270c3 | Vendor (CNA) |
| Linux Linux | d6c39774ae093c9f7009cc4ae918f18fc1af7ae7 | Vendor (CNA) |
| azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | 6.6.158.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.190-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-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.
No dated events beyond publication.
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-1184 · Sep 28, 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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- git.kernel.org/stable/c/314c8caa9cb64ad60c5b969fe9a3e2dcdccf156f
- git.kernel.org/stable/c/374b2c5561db80fcdd7cdce44af37a49416f61c7
- git.kernel.org/stable/c/8cb75f7ada25b1cf25f2f74dec3ba649b9064a09
- git.kernel.org/stable/c/92f0bd0e2b632c6565ac2214a4d7d2ed37e5b9f6
- git.kernel.org/stable/c/c74750dca96f40a1adb9d334f5a3152f44b270c3
- git.kernel.org/stable/c/d6c39774ae093c9f7009cc4ae918f18fc1af7ae7
Vendor advisories and official records. Exploit/PoC links are deliberately left out.