5.5
MEDIUM
CVE-2024-39506
Liquidio NULL Pointer Dereference Vulnerability
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.

INFO

Published Date :

July 12, 2024, 1:15 p.m.

Last Modified :

Aug. 28, 2024, 7:58 p.m.

Source :

416baaa9-dc9f-4396-8d5f-8c081fb06d67

Remotely Exploitable :

No

Impact Score :

3.6

Exploitability Score :

1.8
Affected Products

The following products are affected by CVE-2024-39506 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

ID Vendor Product Action
1 Linux linux_kernel

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2024-39506 vulnerability anywhere in the article.

The following table lists the changes that have been made to the CVE-2024-39506 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • Initial Analysis by [email protected]

    Aug. 28, 2024

    Action Type Old Value New Value
    Added CVSS V3.1 NIST AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
    Changed Reference Type https://git.kernel.org/stable/c/87d6bdc006f0cbf297a3b2ad6e40ede4c3ee5dc2 No Types Assigned https://git.kernel.org/stable/c/87d6bdc006f0cbf297a3b2ad6e40ede4c3ee5dc2 Patch
    Changed Reference Type https://git.kernel.org/stable/c/a6f4d0ec170a46b5f453cacf55dff5989b42bbfa No Types Assigned https://git.kernel.org/stable/c/a6f4d0ec170a46b5f453cacf55dff5989b42bbfa Patch
    Changed Reference Type https://git.kernel.org/stable/c/a86490a3712cc513113440a606a0e77130abd47c No Types Assigned https://git.kernel.org/stable/c/a86490a3712cc513113440a606a0e77130abd47c Patch
    Changed Reference Type https://git.kernel.org/stable/c/c44711b78608c98a3e6b49ce91678cd0917d5349 No Types Assigned https://git.kernel.org/stable/c/c44711b78608c98a3e6b49ce91678cd0917d5349 Patch
    Changed Reference Type https://git.kernel.org/stable/c/cbf18d8128a753cb632bef39470d19befd9c7347 No Types Assigned https://git.kernel.org/stable/c/cbf18d8128a753cb632bef39470d19befd9c7347 Patch
    Changed Reference Type https://git.kernel.org/stable/c/dcc7440f32c7a26b067aff6e7d931ec593024a79 No Types Assigned https://git.kernel.org/stable/c/dcc7440f32c7a26b067aff6e7d931ec593024a79 Patch
    Changed Reference Type https://git.kernel.org/stable/c/f1ab15a09492a5ae8ab1e2c35ba2cf9e150d25ee No Types Assigned https://git.kernel.org/stable/c/f1ab15a09492a5ae8ab1e2c35ba2cf9e150d25ee Patch
    Changed Reference Type https://git.kernel.org/stable/c/fd2b613bc4c508e55c1221c6595bb889812a4fea No Types Assigned https://git.kernel.org/stable/c/fd2b613bc4c508e55c1221c6595bb889812a4fea Patch
    Added CWE NIST CWE-476
    Added CPE Configuration OR *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 4.15 up to (excluding) 4.19.317 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 4.20 up to (excluding) 5.4.279 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.5 up to (excluding) 5.10.221 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.11 up to (excluding) 5.15.162 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.16 up to (excluding) 6.1.95 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.2 up to (excluding) 6.6.35 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.7 up to (excluding) 6.9.6 *cpe:2.3:o:linux:linux_kernel:6.10:rc1:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:6.10:rc2:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:6.10:rc3:*:*:*:*:*:*
  • CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67

    Jul. 12, 2024

    Action Type Old Value New Value
    Added 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.
    Added Reference kernel.org https://git.kernel.org/stable/c/87d6bdc006f0cbf297a3b2ad6e40ede4c3ee5dc2 [No types assigned]
    Added Reference kernel.org https://git.kernel.org/stable/c/dcc7440f32c7a26b067aff6e7d931ec593024a79 [No types assigned]
    Added Reference kernel.org https://git.kernel.org/stable/c/cbf18d8128a753cb632bef39470d19befd9c7347 [No types assigned]
    Added Reference kernel.org https://git.kernel.org/stable/c/a86490a3712cc513113440a606a0e77130abd47c [No types assigned]
    Added Reference kernel.org https://git.kernel.org/stable/c/f1ab15a09492a5ae8ab1e2c35ba2cf9e150d25ee [No types assigned]
    Added Reference kernel.org https://git.kernel.org/stable/c/fd2b613bc4c508e55c1221c6595bb889812a4fea [No types assigned]
    Added Reference kernel.org https://git.kernel.org/stable/c/a6f4d0ec170a46b5f453cacf55dff5989b42bbfa [No types assigned]
    Added Reference kernel.org https://git.kernel.org/stable/c/c44711b78608c98a3e6b49ce91678cd0917d5349 [No types assigned]
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.
CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorizes the common flaws or weaknesses that can lead to vulnerabilities. CVE-2024-39506 is associated with the following CWEs:

Common Attack Pattern Enumeration and Classification (CAPEC)

Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2024-39506 weaknesses.

CVSS31 - Vulnerability Scoring System
Attack Vector
Attack Complexity
Privileges Required
User Interaction
Scope
Confidentiality
Integrity
Availability