CVE-2024-39506

Description

In the Linux kernel, the following vulnerability has been resolved: liquidio: Adjust a NULL pointer handling path in lio_vf_rep_copy_packet In lio_vf_rep_copy_packet() pg_info->page is compared to a NULL value, but then it is unconditionally passed to skb_add_rx_frag() which looks strange and could lead to null pointer dereference. lio_vf_rep_copy_packet() call trace looks like: octeon_droq_process_packets octeon_droq_fast_process_packets octeon_droq_dispatch_pkt octeon_create_recv_info ...search in the dispatch_list... ->disp_fn(rdisp->rinfo, ...) lio_vf_rep_pkt_recv(struct octeon_recv_info *recv_info, ...) In this path there is no code which sets pg_info->page to NULL. So this check looks unneeded and doesn't solve potential problem. But I guess the author had reason to add a check and I have no such card and can't do real test. In addition, the code in the function liquidio_push_packet() in liquidio/lio_core.c does exactly the same. Based on this, I consider the most acceptable compromise solution to adjust this issue by moving skb_add_rx_frag() into conditional scope. Found by Linux Verification Center (linuxtesting.org) with SVACE.

Gravité et risque d'exploitation

CVE-2024-39506 obtient un score CVSS de 0.0/10, soit une gravité non évaluée. Selon le modèle EPSS, la probabilité qu'elle soit exploitée dans les 30 prochains jours est de 0.29 %, ce qui la place devant 20.2 % des CVE référencées.

Que faire ?

• Vérifiez si Linux (versions <=6.1.*, <c44711b78608c98a3e6b49ce91678cd0917d5349, 5.4.279, 6.10, 6.1.95, <a86490a3712cc513113440a606a0e77130abd47c, 0, 6.9.6, <a6f4d0ec170a46b5f453cacf55dff5989b42bbfa, <cbf18d8128a753cb632bef39470d19befd9c7347, 6.6.35, <=5.10.*, <=6.6.*, <fd2b613bc4c508e55c1221c6595bb889812a4fea, <=6.9.*, 5.15.162, <=5.4.*, <=4.19.*, 5.10.221, 1f233f327913f3dee0602cba9c64df1903772b55, <=*, <=5.15.*, 4.19.317, <f1ab15a09492a5ae8ab1e2c35ba2cf9e150d25ee, <4.15, <87d6bdc006f0cbf297a3b2ad6e40ede4c3ee5dc2, 4.15, <dcc7440f32c7a26b067aff6e7d931ec593024a79) 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/87d6bdc006f0cbf297a3b2ad6e40ede4c3ee5dc2
• https://git.kernel.org/stable/c/dcc7440f32c7a26b067aff6e7d931ec593024a79
• https://git.kernel.org/stable/c/cbf18d8128a753cb632bef39470d19befd9c7347
• https://git.kernel.org/stable/c/a86490a3712cc513113440a606a0e77130abd47c
• https://git.kernel.org/stable/c/f1ab15a09492a5ae8ab1e2c35ba2cf9e150d25ee
• https://git.kernel.org/stable/c/fd2b613bc4c508e55c1221c6595bb889812a4fea
• https://git.kernel.org/stable/c/a6f4d0ec170a46b5f453cacf55dff5989b42bbfa
• https://git.kernel.org/stable/c/c44711b78608c98a3e6b49ce91678cd0917d5349