CVE-2024-50164
Vulnérabilité élevée dans Linux (Linux)
Description
In the Linux kernel, the following vulnerability has been resolved: bpf: Fix overloading of MEM_UNINIT's meaning Lonial reported an issue in the BPF verifier where check_mem_size_reg() has the following code: if (!tnum_is_const(reg->var_off)) /* For unprivileged variable accesses, disable raw * mode so that the program is required to * initialize all the memory that the helper could * just partially fill up. */ meta = NULL; This means that writes are not checked when the register containing the size of the passed buffer has not a fixed size. Through this bug, a BPF program can write to a map which is marked as read-only, for example, .rodata global maps. The problem is that MEM_UNINIT's initial meaning that "the passed buffer to the BPF helper does not need to be initialized" which was added back in commit 435faee1aae9 ("bpf, verifier: add ARG_PTR_TO_RAW_STACK type") got overloaded over time with "the passed buffer is being written to". The problem however is that checks such as the above which were added later via 06c1c049721a ("bpf: allow helpers access to variable memory") set meta to NULL in order force the user to always initialize the passed buffer to the helper. Due to the current double meaning of MEM_UNINIT, this bypasses verifier write checks to the memory (not boundary checks though) and only assumes the latter memory is read instead. Fix this by reverting MEM_UNINIT back to its original meaning, and having MEM_WRITE as an annotation to BPF helpers in order to then trigger the BPF verifier checks for writing to memory. Some notes: check_arg_pair_ok() ensures that for ARG_CONST_SIZE{,_OR_ZERO} we can access fn->arg_type[arg - 1] since it must contain a preceding ARG_PTR_TO_MEM. For check_mem_reg() the meta argument can be removed altogether since we do check both BPF_READ and BPF_WRITE. Same for the equivalent check_kfunc_mem_size_reg().
Gravité et risque d'exploitation
CVE-2024-50164 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.21 %, ce qui la place devant 11.0 % des CVE référencées.
Que faire ?
- Vérifiez si Linux (versions 6.12, <=6.1.*, 5d0bba8232bf22ce13747cbfc8f696318ff01a50, <8ea607330a39184f51737c6ae706db7fdca7628e, <=6.11.*, 5.15.45, 0, <54bc31682660810af1bed7ca7a19f182df8d3df8, 5.19, 97e6d7dab1ca4648821c790a2b7913d6d5d549db, 70674d11d14eeecad90be4b409a22b902112ba32, <43f4df339a4d375bedcad29a61ae6f0ee7a048f8, <5.18, <=6.6.*, bfe25df63048edd4ceaf78a2fc755d5e2befc978, 6.11.6, 5.18.2, <5.16, a08d942ecbf46e23a192093f6983cb1d779f4fa8, <5.19, 717c39718dbc4f7ebcbb7b625fb11851cd9007fe, 5.17.13, <=*, 6099a6c8a749a5c8d5f8b4c4342022a92072a02b, 6.6.59, 6.1.125, <48068ccaea957469f1adf78dfd2c1c9a7e18f0fe) 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.