Heimdall Security Logo

CVE-2025-38502

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

CVSS 7.8 · Élevée
EPSS 0.2%
Linux•Linux•Versions : <=6.1.*, <=6.12.*, <=6.16.*, 6.17, 0, 5.15.192, <abad3d0bad72a52137e0c350c59542d75ae4f513, 6.12.46, <c1c74584b9b4043c52e41fec415226e582d266a3, <=6.6.*, 6.16.1, <7acfa07c585e3d7a64654d38f0a5c762877d0b9b, 6.6.105, 5.9, <5.9, 6.1.151, <=*, 7d9c3427894fe70d1347b4820476bf37736d2ff0, <19341d5c59e8c7e8528e40f8663e99d67810473c, <=5.15.*, <41688d1fc5d163a6c2c0e95c0419e2cb31a44648, <66da7cee78590259b400e51a70622ccd41da7bb2

Description

In the Linux kernel, the following vulnerability has been resolved: bpf: Fix oob access in cgroup local storage Lonial reported that an out-of-bounds access in cgroup local storage can be crafted via tail calls. Given two programs each utilizing a cgroup local storage with a different value size, and one program doing a tail call into the other. The verifier will validate each of the indivial programs just fine. However, in the runtime context the bpf_cg_run_ctx holds an bpf_prog_array_item which contains the BPF program as well as any cgroup local storage flavor the program uses. Helpers such as bpf_get_local_storage() pick this up from the runtime context: ctx = container_of(current->bpf_ctx, struct bpf_cg_run_ctx, run_ctx); storage = ctx->prog_item->cgroup_storage[stype]; if (stype == BPF_CGROUP_STORAGE_SHARED) ptr = &READ_ONCE(storage->buf)->data[0]; else ptr = this_cpu_ptr(storage->percpu_buf); For the second program which was called from the originally attached one, this means bpf_get_local_storage() will pick up the former program's map, not its own. With mismatching sizes, this can result in an unintended out-of-bounds access. To fix this issue, we need to extend bpf_map_owner with an array of storage_cookie[] to match on i) the exact maps from the original program if the second program was using bpf_get_local_storage(), or ii) allow the tail call combination if the second program was not using any of the cgroup local storage maps.

Gravité et risque d'exploitation

CVE-2025-38502 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.9 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <=6.1.*, <=6.12.*, <=6.16.*, 6.17, 0, 5.15.192, <abad3d0bad72a52137e0c350c59542d75ae4f513, 6.12.46, <c1c74584b9b4043c52e41fec415226e582d266a3, <=6.6.*, 6.16.1, <7acfa07c585e3d7a64654d38f0a5c762877d0b9b, 6.6.105, 5.9, <5.9, 6.1.151, <=*, 7d9c3427894fe70d1347b4820476bf37736d2ff0, <19341d5c59e8c7e8528e40f8663e99d67810473c, <=5.15.*, <41688d1fc5d163a6c2c0e95c0419e2cb31a44648, <66da7cee78590259b400e51a70622ccd41da7bb2) 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

Rechercher une autre CVE