CVE-2026-93138
CVE CVE-2026-93138EUVD EUVD-2026-82246Published 2026-09-17T16:11:38.000ZLast changed 2026-09-18T17:56:10.000ZCVSS 7.8
What the advisory describes
In the Linux kernel, the following vulnerability has been resolved: bpf: Fix vmlinux BTF prep race in bpf_get_btf_vmlinux bpf_get_btf_vmlinux() lazily parses the vmlinux BTF under the bpf_verifier_lock, but publishes the result through a plain store and re-checks it through a plain lockless load. Nothing orders the stores initializing the struct btf inside btf_parse_vmlinux() against the store publishing the pointer: On a weakly ordered arch, a concurrent first-time caller taking the lockless fast path could in principle observe the pointer before the parsed contents are visible. The mutex_unlock() does not help such a reader given it only synchronizes with a later acquisition of the same lock. Thus, publish the pointer with smp_store_release() and read it on the fast path with smp_load_acquire(). Acquire semantics are needed rather than a dependency-ordered READ_ONCE(): btf_parse_vmlinux() also populates globals outside the returned object (e.g. bpf_ctx_convert.t). An address dependency would only order accesses performed through the pointer and not cover other globals.
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 patch: 6.18.52; 8580ac9404f6240668a026785d7d8856f0530409 <f32a4a40bc635be25d6816da4bd91e9e58c31bf3; 8580ac9404f6240668a026785d7d8856f0530409 <86d11c594d60b255b526fa5260f669463fb1a063; 8580ac9404f6240668a026785d7d8856f0530409 <2892f3f44bf865c8fb6b6c0960edec4cc91806ee; 8580ac9404f6240668a026785d7d8856f0530409 <92863e678070f57c17c868e4bfa2441a5c61ad2b; 8580ac9404f6240668a026785d7d8856f0530409 <978524ecfc1c539282df5858de1eec20748c6f74; patch: 0; patch: 6.1.188; 8580ac9404f6240668a026785d7d8856f0530409 <e18a10b39c994f04e1ebd7f8fc042bb1ca8ad053; 5.5; 8580ac9404f6240668a026785d7d8856f0530409 <eaf302628a78806f66d8224d6ba03fb4d5025de4; patch: 5.10.270; patch: 6.12.110; 8580ac9404f6240668a026785d7d8856f0530409 <a7fe72d780122eb934536f1719abad445f6afdf7; patch: 7.3-rc1; patch: 7.2.6; patch: 5.15.221; patch: 6.6.157
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.