CVE-2024-41066: Linux kernel · ibmvnic: Add tx check to prevent skb leak
Affects Linux kernelSource GCVE Database
Not known to be exploited · CVSS 7.5 High · fixed in 4.4.0-1140.146 : patch Linux kernel soon.
Data as of 26 Oct 2026, 23:28 UTC
- Patch
- Available – fixed in 4.4.0-1140.146, 4.15.0-1185.200~14.04.1, 4.4.0-263.297~14.04.1 +99
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 29 Jul 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Patches and advisories
- ubuntu.com/security/notices/USN-7089-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7090-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7089-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7089-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-7095-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7089-4 (opens in a new tab)
- ubuntu.com/security/notices/USN-7089-5 (opens in a new tab)
- ubuntu.com/security/notices/USN-7089-6 (opens in a new tab)
- ubuntu.com/security/notices/USN-7089-7 (opens in a new tab)
- ubuntu.com/security/notices/USN-7156-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7233-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7233-2 (opens in a new tab)
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 24.04 LTSlinuxpkg:deb/ubuntu/linux?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-awspkg:deb/ubuntu/linux-aws?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-azurepkg:deb/ubuntu/linux-azure?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-gcppkg:deb/ubuntu/linux-gcp?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-gkepkg:deb/ubuntu/linux-gke?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-gkeoppkg:deb/ubuntu/linux-gkeop?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
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.
References
- ubuntu.com/security/CVE-2024-41066 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2024-41066 (opens in a new tab)
- git.kernel.org/linus/0983d288caf984de0202c66641577b739caad561 (opens in a new tab)
- git.kernel.org/stable/c/16ad1557cae582e79bb82dddd612d9bdfaa11d4c (opens in a new tab)
- git.kernel.org/stable/c/267c61c4afed0ff9a2e83462abad3f41d8ca1f06 (opens in a new tab)
- git.kernel.org/stable/c/e7b75def33eae61ddaad6cb616c517dc3882eb2a (opens in a new tab)
- git.kernel.org/stable/c/0983d288caf984de0202c66641577b739caad561 (opens in a new tab)
- ubuntu.com/security/notices/USN-7089-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7090-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7089-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7089-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-7095-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7089-4 (opens in a new tab)
- ubuntu.com/security/notices/USN-7089-5 (opens in a new tab)
- ubuntu.com/security/notices/USN-7089-6 (opens in a new tab)
- ubuntu.com/security/notices/USN-7089-7 (opens in a new tab)
- ubuntu.com/security/notices/USN-7156-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7233-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7233-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7233-3 (opens in a new tab)