Answer in brief
CVE-2024-41066 records a Unknown severity vulnerability in ibmvnic: Add tx check to prevent skb leak. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=65d6470d139a6c1655fccb5cbacbeaba8e8ad2f8 <16ad1557cae582e79bb82dddd612d9bdfaa11d4c || >=65d6470d139a6c1655fccb5cbacbeaba8e8ad2f8 <267c61c4afed0ff9a2e83462abad3f41d8ca1f06 || >=65d6470d139a6c1655fccb5cbacbeaba8e8ad2f8 <e7b75def33eae61ddaad6cb616c517dc3882eb2a || >=65d6470d139a6c1655fccb5cbacbeaba8e8ad2f8 <0983d288caf984de0202c66641577b739caad561 || 1a64564eee05128f773930649edfdd50cbe80656 || 5142c39253385702a4de8f897027e1d76fc333de || >=5.12.17 <5.13 || >=5.13.2 <5.14 | 16ad1557cae582e79bb82dddd612d9bdfaa11d4c, 267c61c4afed0ff9a2e83462abad3f41d8ca1f06, e7b75def33eae61ddaad6cb616c517dc3882eb2a, 0983d288caf984de0202c66641577b739caad561, 5.13, 5.14 |
| Linux/Linuxgeneric | 5.14 | Not reported |
Published upstream
Jul 29, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2024-41066 records a Unknown severity vulnerability in ibmvnic: Add tx check to prevent skb leak. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=65d6470d139a6c1655fccb5cbacbeaba8e8ad2f8 <16ad1557cae582e79bb82dddd612d9bdfaa11d4c || >=65d6470d139a6c1655fccb5cbacbeaba8e8ad2f8 <267c61c4afed0ff9a2e83462abad3f41d8ca1f06 || >=65d6470d139a6c1655fccb5cbacbeaba8e8ad2f8 <e7b75def33eae61ddaad6cb616c517dc3882eb2a || >=65d6470d139a6c1655fccb5cbacbeaba8e8ad2f8 <0983d288caf984de0202c66641577b739caad561 || 1a64564eee05128f773930649edfdd50cbe80656 || 5142c39253385702a4de8f897027e1d76fc333de || >=5.12.17 <5.13 || >=5.13.2 <5.14 | 16ad1557cae582e79bb82dddd612d9bdfaa11d4c, 267c61c4afed0ff9a2e83462abad3f41d8ca1f06, e7b75def33eae61ddaad6cb616c517dc3882eb2a, 0983d288caf984de0202c66641577b739caad561, 5.13, 5.14 |
| Linux/Linuxgeneric | 5.14 | Not reported |
Published upstream
Jul 29, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.