CVE-2024-50145: octeon_ep: Add SKB allocation failures handling in __octep_oq_process_rx()
In the Linux kernel, the following vulnerability has been resolved:
octeonep: Add SKB allocation failures handling in octepoqprocessrx()
buildskb() returns NULL in case of a memory allocation failure so handle it inside octepoqprocessrx() to avoid NULL pointer dereference.
octepoqprocessrx() is called during NAPI polling by the driver. If skb allocation fails, keep on pulling packets out of the Rx DMA queue: we shouldn't break the polling immediately and thus falsely indicate to the octepnapipoll() that the Rx pressure is going down. As there is no associated skb in this case, don't process the packets and don't push them up the network stack - they are skipped.
Helper function is implemented to unmmap/flush all the fragment buffers used by the dropped packet. 'allocfailures' counter is incremented to mark the skb allocation error in driver statistics.
Found by Linux Verification Center (linuxtesting.org) with SVACE.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 5.10.223-1Fixed in 5.10.234-1Fixed in 6.1.129-1Fixed in 6.1.135-1Fixed in 6.12.22-1Fixed in 6.12.25-1 - Upgrade
Upgrade
debian/linux-6.1to a version that resolves this vulnerability.Fixed in 6.1.129-1~deb11u1
Event History
Frequently Asked Questions
What is the severity of CVE-2024-50145?
CVE-2024-50145 is categorized as a moderate severity vulnerability due to potential NULL pointer dereference issues.
How do I fix CVE-2024-50145?
To resolve CVE-2024-50145, it is recommended to update to a patched version of the Linux kernel that addresses the SKB allocation handling.
Which Linux kernel versions are affected by CVE-2024-50145?
CVE-2024-50145 affects Linux kernel versions between 5.19 and 6.1.115, as well as several others up to and including 6.12-rc4.
What are the risks of not patching CVE-2024-50145?
Not patching CVE-2024-50145 may lead to application crashes or denial of service due to NULL pointer dereference vulnerabilities.
Is there a workaround for CVE-2024-50145 until I can patch?
While a specific workaround for CVE-2024-50145 is not detailed, minimizing exposure to impacted kernel versions may reduce risk.