7.5

CVE-2024-41066: ibmvnic: Add tx check to prevent skb leak

Modified
AliasesUBUNTU-CVE-2024-41066DEBIAN-CVE-2024-41066
Published 29-07-2024Last modified 05-08-2026

Vulnerability summary

CVE-2024-41066 is a high (CVSS 7.5) vulnerability in linux. EPSS estimates a 0.53% chance of exploitation in the next 30 days, higher than 45% of scored vulnerabilities.

Priority
Prioritisesevere

Severe, CVSS 7.5 (CVE.org); no exploitation reported by the 5 checked sources; EPSS 1% (FIRST, 03-11-2026)

Source freshness unavailable

How is this decided?
CVSS score
7.5/10
010
High · v3.1 (CVE.org)
EPSS score
0.53%
0%100%
Low · 0.00 pp in 30 days
KEVNot listedNot listed by any tracked catalog.
RansomwareNot flaggedNo ransomware use recorded.
Public exploits0No public exploits recorded

Advisory lineage

Upstream 0 · Downstream 59 · Related 51
DLA-4008-1MGASA-2024-0277MGASA-2024-0278RHSA-2024:8157RHSA-2024:8158RHSA-2024:8856

Timeline

  1. 29-07-2024
    PublishedVulnerability first disclosed.
  2. 05-08-2026
    Last modifiedVulnerability information updated.

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.

CVSS metrics

5 scores · 4 sources · 2 versions

EPSS trend

Probability

0.53%

Chance of exploitation in the next 30 days

Percentile

45%

Versus all other CVEs

30-day change

No change 0.00 pp

From 0.53% on 04-10-2026

04-10-202603-11-2026

Known exploited

Compare KEV catalogs
CISA KEV

Not in the CISA KEV catalog.

ENISA CNW

Not in the ENISA CNW catalog.

CIRCL

Not in the CIRCL catalog.

Public exploits

0 found

No public exploits indexed.

Weaknesses

CWE · root cause

Affected systems

Version check

Known conditions: network-reachable, no authentication, no user interaction (CVSS vector). Other conditions: not stated in public data.

Ubuntu129 products
  • linux< 4.4.0-263.297 | < 4.15.0-233.245 | < 5.4.0-208.228 | < 5.15.0-133.144 | < 6.8.0-48.48
  • linux-allwinner-5.19All versions (No fix recorded)
  • linux-aws< 4.4.0-1140.146 | < 4.4.0-1178.193 | < 4.15.0-1177.190 | < 5.4.0-1140.150 | < 5.15.0-1078.85 | < 6.8.0-1018.20
  • linux-aws-5.0All versions (No fix recorded)
  • linux-aws-5.11All versions (No fix recorded)
Linux2 products
  • linux≥ 65d6470d139a6c1655fccb5cbacbeaba8e8ad2f8, < 16ad1557cae582e79bb82dddd612d9bdfaa11d4c | ≥ 65d6470d139a6c1655fccb5cbacbeaba8e8ad2f8, < 267c61c4afed0ff9a2e83462abad3f41d8ca1f06 | ≥ 65d6470d139a6c1655fccb5cbacbeaba8e8ad2f8, < e7b75def33eae61ddaad6cb616c517dc3882eb2a | ≥ 65d6470d139a6c1655fccb5cbacbeaba8e8ad2f8, < 0983d288caf984de0202c66641577b739caad561 | 1a64564eee05128f773930649edfdd50cbe80656 | 5142c39253385702a4de8f897027e1d76fc333de | ≥ 5.12.17, < 5.13 | ≥ 5.13.2, < 5.14 | 5.14
  • linux_kernel< 6.1.101 | ≥ 6.2, < 6.6.42 | ≥ 6.7, < 6.9.11 | 6.10:rc1 | 6.10:rc2 | 6.10:rc3 | 6.10:rc4 | 6.10:rc5
Debian1 product
  • linux< 6.1.106-1 | < 6.9.11-1

3 vendors · 132 products

References

49 links
Show all 49 references