CVE-2024-41066
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.
Predictions
Heuristic predictions, AS-IS, for prioritization only.
Mitigations
No mitigations published for this CVE yet.
The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or โ if you've already worked around this in production โ publish your fix to the community-verified tier.
โ Propose a mitigation on Community โ Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here withsource_tier=community-verified.
OS impact
| OS | Version | Status | Fixed in |
|---|---|---|---|
| rocky | 8 | fixed | |
| sles | affected | | |
| debian | bookworm | fixed | 6.1.106-1 |
| debian | bullseye | fixed | 0 |
| debian | forky | fixed | 6.9.11-1 |
| debian | sid | fixed | 6.9.11-1 |
| debian | trixie | fixed | 6.9.11-1 |
| almalinux | 8 | fixed | kernel-doc-4.18.0-553.27.1.el8_10.noarch.rpm |
References
- https://errata.rockylinux.org/RLSA-2024:8870
- https://errata.rockylinux.org/RLSA-2024:8856
- https://www.suse.com/security/cve/CVE-2024-41066.html
- https://security-tracker.debian.org/tracker/CVE-2024-41066
- https://access.redhat.com/errata/RHSA-2024:8856
- https://bugzilla.redhat.com/2266247
- https://bugzilla.redhat.com/2269183
- https://bugzilla.redhat.com/2275750
- https://bugzilla.redhat.com/2277168
- https://bugzilla.redhat.com/2278262
- https://bugzilla.redhat.com/2278350
- https://bugzilla.redhat.com/2278387
- https://bugzilla.redhat.com/2281284
- https://bugzilla.redhat.com/2281669
- https://bugzilla.redhat.com/2281817
- https://bugzilla.redhat.com/2293356
- https://bugzilla.redhat.com/2293402
- https://bugzilla.redhat.com/2293458
- https://bugzilla.redhat.com/2293459
- https://bugzilla.redhat.com/2297475
- https://bugzilla.redhat.com/2297508
- https://bugzilla.redhat.com/2297545
- https://bugzilla.redhat.com/2297567
- https://bugzilla.redhat.com/2297568
- https://bugzilla.redhat.com/2298109
Community-verified mitigations for this CVE will appear above when contributors publish them.
Verify integrity in audit chain (admin only). AS-IS.