CVE-2026-93138

Vulnérabilité élevée dans Linux (Linux)

CVSS 7.8 · Élevée
EPSS 0.2%
Linux•Linux•Versions : <=6.1.*, <2892f3f44bf865c8fb6b6c0960edec4cc91806ee, <=6.12.*, <92863e678070f57c17c868e4bfa2441a5c61ad2b, 5.15.221, <e18a10b39c994f04e1ebd7f8fc042bb1ca8ad053, 5.10.270, 0, <a7fe72d780122eb934536f1719abad445f6afdf7, 6.1.188, 6.18.52, <eaf302628a78806f66d8224d6ba03fb4d5025de4, <=5.10.*, <=6.6.*, <f32a4a40bc635be25d6816da4bd91e9e58c31bf3, 6.6.157, 7.2.6, 8580ac9404f6240668a026785d7d8856f0530409, <5.5, <=6.18.*, 5.5, 6.12.110, <=7.2.*, <86d11c594d60b255b526fa5260f669463fb1a063, <978524ecfc1c539282df5858de1eec20748c6f74, <=*, <=5.15.*, 7.3

Description

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.

Gravité et risque d'exploitation

CVE-2026-93138 obtient un score CVSS de 7.8/10, soit une gravité élevée. Selon le modèle EPSS, la probabilité qu'elle soit exploitée dans les 30 prochains jours est de 0.18 %, ce qui la place devant 6.7 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <=6.1.*, <2892f3f44bf865c8fb6b6c0960edec4cc91806ee, <=6.12.*, <92863e678070f57c17c868e4bfa2441a5c61ad2b, 5.15.221, <e18a10b39c994f04e1ebd7f8fc042bb1ca8ad053, 5.10.270, 0, <a7fe72d780122eb934536f1719abad445f6afdf7, 6.1.188, 6.18.52, <eaf302628a78806f66d8224d6ba03fb4d5025de4, <=5.10.*, <=6.6.*, <f32a4a40bc635be25d6816da4bd91e9e58c31bf3, 6.6.157, 7.2.6, 8580ac9404f6240668a026785d7d8856f0530409, <5.5, <=6.18.*, 5.5, 6.12.110, <=7.2.*, <86d11c594d60b255b526fa5260f669463fb1a063, <978524ecfc1c539282df5858de1eec20748c6f74, <=*, <=5.15.*, 7.3) est présent sur votre parc.
  • Appliquez le correctif ou la version corrigée indiqués dans les références de l'éditeur.
  • À défaut de correctif, limitez l'exposition (filtrage réseau, désactivation du composant).
  • Automatisez la détection : les agents CVE Heimdall (gratuits, open source) corrèlent l'inventaire de vos serveurs avec la base CVE.

Références