Lucene search

K
vulnrichmentLinuxVULNRICHMENT:CVE-2024-39506
HistoryJul 12, 2024 - 12:20 p.m.

CVE-2024-39506 liquidio: Adjust a NULL pointer handling path in lio_vf_rep_copy_packet

2024-07-1212:20:38
Linux
github.com
3
vulnerability resolution
linux kernel
null pointer handling
lio_vf_rep_copy_packet
skb_add_rx_frag
liquidio
svace
linux verification center

AI Score

6.8

Confidence

Low

SSVC

Exploitation

none

Automatable

no

Technical Impact

partial

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.

AI Score

6.8

Confidence

Low

SSVC

Exploitation

none

Automatable

no

Technical Impact

partial