CVE-2026-92485: bpf: Fix WARNING in bpf_tracing_link_release
Noroxi assessment
Priority: Monitor (action score 31/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).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 094f0a895cf97a993d06d5dc4c12e7cb7da845a5, 1757598b3804f7cb35b5b5e02558f6d8b9c2f254, 48a0209d8da0d90a7b0a0db19d1ff88027b13781.
Low priority for now. Upgrade to Linux Linux 094f0a895cf97a993d06d5dc4c12e7cb7da845a5, 1757598b3804f7cb35b5b5e02558f6d8b9c2f254, 48a0209d8da0d90a7b0a0db19d1ff88027b13781 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: Fix WARNING in bpf_tracing_link_release The trampoline could be corrupted by the blindly 'tr->flags = BPF_TRAMP_F_TAIL_CALL_CTX' in verifier. 1. A fexit attached to a tail_call_reachable prog. 'tr->flags' became 'BPF_TRAMP_F_CALL_ORIG | BPF_TRAMP_F_TAIL_CALL_CTX'. And, the trampoline would poke the target prog's nop insn using jmp insn instead of call insn. 2. Another fexit loaded with the same tail_call_reachable prog target. 'tr->flags' became 'BPF_TRAMP_F_TAIL_CALL_CTX'. 3. Close the first fexit link. Due to no BPF_TRAMP_F_CALL_ORIG in 'tr->flags', the trampoline will fail to restore the prog's nop insn using call insn. [ 3.410719] WARNING: kernel/bpf/syscall.c:3551 at bpf_tracing_link_release+0x53/0x60, CPU#1: test_progs/98 ... [ 3.428793] bpf_link_free+0x58/0x130 [ 3.429293] bpf_link_release+0x23/0x30 Fix the warning by updating 'tr->flags' with '|=' and lock.
- Published
- Sep 17, 2026
- Updated
- Oct 30, 2026
- EPSS
- 0.1% · 7th percentile
- CWE
- —
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
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
- 028480eaf2a1401e914a1fa1a4a21d877cf0ae30, 6.7affected
- 605c8d8f9966fcd2f0b858fabebe416fc83f2209 and later · before 1757598b3804f7cb35b5b5e02558f6d8b9c2f254affected · git
- 8f873cc3f67f2257493063e57d0caf07ef889ee9 and later · before a5c6316052f0ff1467221ecf2996cbab0a496b1eaffected · git
- 2b5dcb31a19a2e0acd869b12c9db9b2d696ef544 and later · before d02035c5eb4955616efc5c6dbe3d98f19d798cb2affected · git
- 2b5dcb31a19a2e0acd869b12c9db9b2d696ef544 and later · before 094f0a895cf97a993d06d5dc4c12e7cb7da845a5affected · git
- 2b5dcb31a19a2e0acd869b12c9db9b2d696ef544 and later · before 48a0209d8da0d90a7b0a0db19d1ff88027b13781affected · git
- 2b5dcb31a19a2e0acd869b12c9db9b2d696ef544 and later · before 61aaa8782bec59ecffd22e030f54ef9351bcabf9affected · git
- 6.1.72 and later · before 6.1.191affected · semver
- 6.6.2 and later · before 6.6.160affected · semver
- 6.5.12 and later · before 6.6affected · 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 | from 0 | — |
| Debian:13 | linux | before 6.12.115-2 | 6.12.115-2 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.6-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-92483Sep 17, 2026 · liveupdate: Remember FLB retrieve() status0Monitor
- ← EarlierCVE-2026-92484Sep 17, 2026 · cxl/region: Fix use-after-free in find_pos_and_ways() error path0Monitor
- Later →CVE-2026-92486Sep 17, 2026 · bpf: Fix CFI mismatch in task work callback0Monitor
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 | 094f0a895cf97a993d06d5dc4c12e7cb7da845a5 | Vendor (CNA) |
| Linux Linux | 1757598b3804f7cb35b5b5e02558f6d8b9c2f254 | Vendor (CNA) |
| Linux Linux | 48a0209d8da0d90a7b0a0db19d1ff88027b13781 | Vendor (CNA) |
| Linux Linux | 6.1.191 | Vendor (CNA) |
| Linux Linux | 6.6 | Vendor (CNA) |
| Linux Linux | 6.6.160 | Vendor (CNA) |
| Linux Linux | 61aaa8782bec59ecffd22e030f54ef9351bcabf9 | Vendor (CNA) |
| Linux Linux | a5c6316052f0ff1467221ecf2996cbab0a496b1e | Vendor (CNA) |
| Linux Linux | d02035c5eb4955616efc5c6dbe3d98f19d798cb2 | Vendor (CNA) |
| debian:linux | 6.12.115-2 · Debian:13 | Package registry (OSV) |
| debian:linux | 7.2.6-1 · Debian:14 | 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).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
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 (5 more)Show less
- git.kernel.org/stable/c/1757598b3804f7cb35b5b5e02558f6d8b9c2f254
- git.kernel.org/stable/c/48a0209d8da0d90a7b0a0db19d1ff88027b13781
- git.kernel.org/stable/c/61aaa8782bec59ecffd22e030f54ef9351bcabf9
- git.kernel.org/stable/c/a5c6316052f0ff1467221ecf2996cbab0a496b1e
- git.kernel.org/stable/c/d02035c5eb4955616efc5c6dbe3d98f19d798cb2
Vendor advisories and official records. Exploit/PoC links are deliberately left out.