CVE-2024-49861

Description

In the Linux kernel, the following vulnerability has been resolved: bpf: Fix helper writes to read-only maps Lonial found an issue that despite user- and BPF-side frozen BPF map (like in case of .rodata), it was still possible to write into it from a BPF program side through specific helpers having ARG_PTR_TO_{LONG,INT} as arguments. In check_func_arg() when the argument is as mentioned, the meta->raw_mode is never set. Later, check_helper_mem_access(), under the case of PTR_TO_MAP_VALUE as register base type, it assumes BPF_READ for the subsequent call to check_map_access_type() and given the BPF map is read-only it succeeds. The helpers really need to be annotated as ARG_PTR_TO_{LONG,INT} | MEM_UNINIT when results are written into them as opposed to read out of them. The latter indicates that it's okay to pass a pointer to uninitialized memory as the memory is written to anyway. However, ARG_PTR_TO_{LONG,INT} is a special case of ARG_PTR_TO_FIXED_SIZE_MEM just with additional alignment requirement. So it is better to just get rid of the ARG_PTR_TO_{LONG,INT} special cases altogether and reuse the fixed size memory types. For this, add MEM_ALIGNED to additionally ensure alignment given these helpers write directly into the args via *<ptr> = val. The .arg*_size has been initialized reflecting the actual sizeof(*<ptr>). MEM_ALIGNED can only be used in combination with MEM_FIXED_SIZE annotated argument types, since in !MEM_FIXED_SIZE cases the verifier does not know the buffer size a priori and therefore cannot blindly write *<ptr> = val.

Gravité et risque d'exploitation

CVE-2024-49861 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.24 %, ce qui la place devant 14.1 % des CVE référencées.

Que faire ?

• Vérifiez si Linux (versions 6.12, <=6.1.*, <988e55abcf7fdb8fc9a76a7cf3f4e939a4d4fb3a, <=6.11.*, 6.10.13, 5.2, 0, 6.1.120, <1e75d25133158b525e0456876e9bcfd6b2993fd5, <2ed98ee02d1e08afee88f54baec39ea78dc8a23c, <=6.6.*, <32556ce93bc45c730829083cb60f95a2728ea48b, 6.6.54, <a2c8dc7e21803257e762b0bf067fd13e9c995da0, <=*, 57c3bb725a3dd97d960d7e1cd0845d88de53217f, 6.11.2, <=6.10.*, <5.2) 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

• https://git.kernel.org/stable/c/988e55abcf7fdb8fc9a76a7cf3f4e939a4d4fb3a
• https://git.kernel.org/stable/c/a2c8dc7e21803257e762b0bf067fd13e9c995da0
• https://git.kernel.org/stable/c/2ed98ee02d1e08afee88f54baec39ea78dc8a23c
• https://git.kernel.org/stable/c/1e75d25133158b525e0456876e9bcfd6b2993fd5
• https://git.kernel.org/stable/c/32556ce93bc45c730829083cb60f95a2728ea48b