Linux Kernel up to 6.1.100/6.6.41/6.9.10 ibmvnic memory leak

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.5 | $0-$5k | 0.00 |
Summary
A vulnerability categorized as critical has been discovered in Linux Kernel up to 6.1.100/6.6.41/6.9.10. Affected by this issue is some unknown functionality of the component ibmvnic. The manipulation results in memory leak. This vulnerability was named CVE-2024-41066. There is no available exploit. It is advisable to upgrade the affected component.
Details
A vulnerability, which was classified as critical, was found in Linux Kernel up to 6.1.100/6.6.41/6.9.10. Affected is an unknown functionality of the component ibmvnic. The manipulation with an unknown input leads to a memory leak vulnerability. CWE is classifying the issue as CWE-401. The product does not sufficiently track and release allocated memory after it has been used, which slowly consumes remaining memory. This is going to have an impact on availability. CVE summarizes:
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=, skb=, 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.
The advisory is available at git.kernel.org. This vulnerability is traded as CVE-2024-41066 since 07/12/2024. The technical details are unknown and an exploit is not available.
The vulnerability scanner Nessus provides a plugin with the ID 209099 (RHEL 9 : kernel (RHSA-2024:8157)), which helps to determine the existence of the flaw in a target environment.
Upgrading to version 6.1.101, 6.6.42 or 6.9.11 eliminates this vulnerability. Applying the patch 16ad1557cae5/267c61c4afed/e7b75def33ea/0983d288caf9 is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.
The vulnerability is also documented in the databases at Tenable (209099) and CERT Bund (WID-SEC-2024-1722). If you want to get best quality of vulnerability data, you may have to visit VulDB.
Affected
- Debian Linux
- Amazon Linux 2
- Red Hat Enterprise Linux
- Ubuntu Linux
- SUSE Linux
- IBM InfoSphere Guardium
- Oracle Linux
- NetApp FAS
- NetApp ActiveIQ Unified Manager
- Siemens SIMATIC S7
- Oracle VM
- IBM Security Guardium
- RESF Rocky Linux
- Broadcom Brocade SANnav
- Dell PowerScale
- Open Source Linux Kernel
- IBM QRadar SIEM
- Dell integrated Dell Remote Access Controller
- Dell Avamar
- IBM Storage Scale
- IBM Spectrum Protect Plus
- Juniper Junos Space
- IBM Storage Scale System
- SolarWinds Security Event Manager
- Dell PowerProtect Data Domain
- Dell PowerProtect Data Domain Management Center
- Dell PowerProtect Data Domain OS
Product
Type
Vendor
Name
Version
- 6.0
- 6.1.100
- 6.6.0
- 6.6.1
- 6.6.2
- 6.6.3
- 6.6.4
- 6.6.5
- 6.6.6
- 6.6.7
- 6.6.8
- 6.6.9
- 6.6.10
- 6.6.11
- 6.6.12
- 6.6.13
- 6.6.14
- 6.6.15
- 6.6.16
- 6.6.17
- 6.6.18
- 6.6.19
- 6.6.20
- 6.6.21
- 6.6.22
- 6.6.23
- 6.6.24
- 6.6.25
- 6.6.26
- 6.6.27
- 6.6.28
- 6.6.29
- 6.6.30
- 6.6.31
- 6.6.32
- 6.6.33
- 6.6.34
- 6.6.35
- 6.6.36
- 6.6.37
- 6.6.38
- 6.6.39
- 6.6.40
- 6.6.41
- 6.9.0
- 6.9.1
- 6.9.2
- 6.9.3
- 6.9.4
- 6.9.5
- 6.9.6
- 6.9.7
- 6.9.8
- 6.9.9
- 6.9.10
License
Website
- Vendor: https://www.kernel.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.6VulDB Meta Temp Score: 5.5
VulDB Base Score: 5.7
VulDB Temp Score: 5.5
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.5
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Memory leakCWE: CWE-401 / CWE-404
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: Partially
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 209099
Nessus Name: RHEL 9 : kernel (RHSA-2024:8157)
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Kernel 6.1.101/6.6.42/6.9.11
Patch: 16ad1557cae5/267c61c4afed/e7b75def33ea/0983d288caf9
Timeline
07/12/2024 🔍07/29/2024 🔍
07/29/2024 🔍
09/02/2025 🔍
Sources
Vendor: kernel.orgAdvisory: git.kernel.org
Status: Confirmed
CVE: CVE-2024-41066 (🔍)
GCVE (CVE): GCVE-0-2024-41066
GCVE (VulDB): GCVE-100-272658
CERT Bund: WID-SEC-2024-1722 - Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff
Entry
Created: 07/29/2024 17:34Updated: 09/02/2025 03:13
Changes: 07/29/2024 17:34 (58), 09/11/2024 07:18 (12), 10/16/2024 13:43 (2), 07/15/2025 16:03 (7), 07/19/2025 00:00 (1), 09/02/2025 03:13 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.