medium
5.5
CWE
401
Advisory Published
Updated

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

First published: Mon Jul 29 2024(Updated: )

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.

Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67 416baaa9-dc9f-4396-8d5f-8c081fb06d67

Affected SoftwareAffected VersionHow to fix
redhat/kernel<6.1.101
6.1.101
redhat/kernel<6.6.42
6.6.42
redhat/kernel<6.9.11
6.9.11
redhat/kernel<6.10
6.10
Linux Kernel<6.1.101
Linux Kernel>=6.2<6.6.42
Linux Kernel>=6.7<6.9.11
Linux Kernel=6.10-rc1
Linux Kernel=6.10-rc2
Linux Kernel=6.10-rc3
Linux Kernel=6.10-rc4
Linux Kernel=6.10-rc5
debian/linux<=5.10.223-1<=5.10.226-1
6.1.123-1
6.1.128-1
6.12.12-1
6.12.13-1
debian/linux-6.1
6.1.119-1~deb11u1

Remedy

https://git.kernel.org/stable/c/0983d288caf984de0202c66641577b739caad561

Remedy

https://git.kernel.org/stable/c/16ad1557cae582e79bb82dddd612d9bdfaa11d4c

Remedy

https://git.kernel.org/stable/c/267c61c4afed0ff9a2e83462abad3f41d8ca1f06

Remedy

https://git.kernel.org/stable/c/e7b75def33eae61ddaad6cb616c517dc3882eb2a

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Read MoreStart Free Trial

Reference Links

Frequently Asked Questions

  • What is the severity of CVE-2024-41066?

    CVE-2024-41066 is classified as a moderate severity vulnerability affecting the Linux kernel.

  • How do I fix CVE-2024-41066?

    To resolve CVE-2024-41066, update the Linux kernel to version 6.1.101 or later, specifically to versions like 6.6.42, 6.9.11, or 6.10.

  • Which Linux kernel versions are affected by CVE-2024-41066?

    CVE-2024-41066 impacts Linux kernel versions below 6.1.101, 6.6.42, 6.9.11, and 6.10.

  • Is CVE-2024-41066 exploitable?

    Exploitation of CVE-2024-41066 could potentially lead to a denial of service or memory corruption issues.

  • What software packages are related to CVE-2024-41066?

    CVE-2024-41066 affects the Red Hat kernel, Debian Linux, and the Linux kernel in general.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203