5.5
MEDIUM
CVE-2024-41066
"IBMvnic skb Leak Prevention"
Description

In the Linux kernel, the following vulnerability has been resolved: ibmvnic: Add tx check to prevent skb leak Below is a summary of how the driver stores a reference to an skb during transmit: tx_buff[free_map[consumer_index]]->skb = new_skb; free_map[consumer_index] = IBMVNIC_INVALID_MAP; consumer_index ++; Where variable data looks like this: free_map == [4, IBMVNIC_INVALID_MAP, IBMVNIC_INVALID_MAP, 0, 3] consumer_index^ tx_buff == [skb=null, skb=<ptr>, skb=<ptr>, skb=null, skb=null] The driver has checks to ensure that free_map[consumer_index] pointed to a valid index but there was no check to ensure that this index pointed to an unused/null skb address. So, if, by some chance, our free_map and tx_buff lists become out of sync then we were previously risking an skb memory leak. This could then cause tcp congestion control to stop sending packets, eventually leading to ETIMEDOUT. Therefore, add a conditional to ensure that the skb address is null. If not then warn the user (because this is still a bug that should be patched) and free the old pointer to prevent memleak/tcp problems.

INFO

Published Date :

July 29, 2024, 3:15 p.m.

Last Modified :

Nov. 21, 2024, 9:32 a.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-41066 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
: Total Affected Vendor : 1 | Products : 1
References to Advisories, Solutions, and Tools

Here, you will find a curated list of external links that provide in-depth information, practical solutions, and valuable tools related to CVE-2024-41066.

URL Resource
https://git.kernel.org/stable/c/0983d288caf984de0202c66641577b739caad561 Patch
https://git.kernel.org/stable/c/16ad1557cae582e79bb82dddd612d9bdfaa11d4c Patch
https://git.kernel.org/stable/c/267c61c4afed0ff9a2e83462abad3f41d8ca1f06 Patch
https://git.kernel.org/stable/c/e7b75def33eae61ddaad6cb616c517dc3882eb2a Patch
https://git.kernel.org/stable/c/0983d288caf984de0202c66641577b739caad561 Patch
https://git.kernel.org/stable/c/16ad1557cae582e79bb82dddd612d9bdfaa11d4c Patch
https://git.kernel.org/stable/c/267c61c4afed0ff9a2e83462abad3f41d8ca1f06 Patch
https://git.kernel.org/stable/c/e7b75def33eae61ddaad6cb616c517dc3882eb2a Patch

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-41066 vulnerability anywhere in the article.

The following table lists the changes that have been made to the CVE-2024-41066 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.

  • CVE Modified by af854a3a-2127-422b-91ae-364da2661108

    Nov. 21, 2024

    Action Type Old Value New Value
    Added Reference https://git.kernel.org/stable/c/0983d288caf984de0202c66641577b739caad561
    Added Reference https://git.kernel.org/stable/c/16ad1557cae582e79bb82dddd612d9bdfaa11d4c
    Added Reference https://git.kernel.org/stable/c/267c61c4afed0ff9a2e83462abad3f41d8ca1f06
    Added Reference https://git.kernel.org/stable/c/e7b75def33eae61ddaad6cb616c517dc3882eb2a
  • Initial Analysis by [email protected]

    Sep. 10, 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/0983d288caf984de0202c66641577b739caad561 No Types Assigned https://git.kernel.org/stable/c/0983d288caf984de0202c66641577b739caad561 Patch
    Changed Reference Type https://git.kernel.org/stable/c/16ad1557cae582e79bb82dddd612d9bdfaa11d4c No Types Assigned https://git.kernel.org/stable/c/16ad1557cae582e79bb82dddd612d9bdfaa11d4c Patch
    Changed Reference Type https://git.kernel.org/stable/c/267c61c4afed0ff9a2e83462abad3f41d8ca1f06 No Types Assigned https://git.kernel.org/stable/c/267c61c4afed0ff9a2e83462abad3f41d8ca1f06 Patch
    Changed Reference Type https://git.kernel.org/stable/c/e7b75def33eae61ddaad6cb616c517dc3882eb2a No Types Assigned https://git.kernel.org/stable/c/e7b75def33eae61ddaad6cb616c517dc3882eb2a Patch
    Added CWE NIST CWE-401
    Added CPE Configuration OR *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions up to (excluding) 6.1.101 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.2 up to (excluding) 6.6.42 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.7 up to (excluding) 6.9.11 *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:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:6.10:rc4:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:6.10:rc5:*:*:*:*:*:*
  • CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67

    Jul. 29, 2024

    Action Type Old Value New Value
    Added Description In the Linux kernel, the following vulnerability has been resolved: ibmvnic: Add tx check to prevent skb leak Below is a summary of how the driver stores a reference to an skb during transmit: tx_buff[free_map[consumer_index]]->skb = new_skb; free_map[consumer_index] = IBMVNIC_INVALID_MAP; consumer_index ++; Where variable data looks like this: free_map == [4, IBMVNIC_INVALID_MAP, IBMVNIC_INVALID_MAP, 0, 3] consumer_index^ tx_buff == [skb=null, skb=<ptr>, skb=<ptr>, skb=null, skb=null] The driver has checks to ensure that free_map[consumer_index] pointed to a valid index but there was no check to ensure that this index pointed to an unused/null skb address. So, if, by some chance, our free_map and tx_buff lists become out of sync then we were previously risking an skb memory leak. This could then cause tcp congestion control to stop sending packets, eventually leading to ETIMEDOUT. Therefore, add a conditional to ensure that the skb address is null. If not then warn the user (because this is still a bug that should be patched) and free the old pointer to prevent memleak/tcp problems.
    Added Reference kernel.org https://git.kernel.org/stable/c/16ad1557cae582e79bb82dddd612d9bdfaa11d4c [No types assigned]
    Added Reference kernel.org https://git.kernel.org/stable/c/267c61c4afed0ff9a2e83462abad3f41d8ca1f06 [No types assigned]
    Added Reference kernel.org https://git.kernel.org/stable/c/e7b75def33eae61ddaad6cb616c517dc3882eb2a [No types assigned]
    Added Reference kernel.org https://git.kernel.org/stable/c/0983d288caf984de0202c66641577b739caad561 [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-41066 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-41066 weaknesses.

CVSS31 - Vulnerability Scoring System
Attack Vector
Attack Complexity
Privileges Required
User Interaction
Scope
Confidentiality
Integrity
Availability
:
© cvefeed.io
Latest DB Update: May. 12, 2025 15:21