CVE-2026-92485
CVE CVE-2026-92485EUVD EUVD-2026-82106Published 2026-09-17T16:10:00.000ZLast changed 2026-09-18T17:55:25.000ZCVSS 7.8
What the advisory describes
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.
Source: EUVD (ENISA), in the words of the advisory.
Products the advisory names
These come from the advisory itself, not from any check we performed.
- Linux — Linux 6.6.2 <6.7; 6.1.72 <6.2; 2b5dcb31a19a2e0acd869b12c9db9b2d696ef544 <61aaa8782bec59ecffd22e030f54ef9351bcabf9; 6.7; 028480eaf2a1401e914a1fa1a4a21d877cf0ae30; patch: 0; 2b5dcb31a19a2e0acd869b12c9db9b2d696ef544 <48a0209d8da0d90a7b0a0db19d1ff88027b13781; 605c8d8f9966fcd2f0b858fabebe416fc83f2209; patch: 7.2.6; 6.5.12 <6.6; patch: 7.3-rc1; 8f873cc3f67f2257493063e57d0caf07ef889ee9
The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.
Carried in the product catalogue
An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.
- Linux — Linux
Does this concern one of your customers?
This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.
Try it for 28 daysPatchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.