CVE-2024-50169: vsock: Update rx_bytes on read_skb()
In the Linux kernel, the following vulnerability has been resolved:
vsock: Update rxbytes on readskb()
Make sure virtiotransportincrxpkt() and virtiotransportdecrxpkt() calls are balanced (i.e. virtiovsocksock::rxbytes doesn't lie) after vsocktransport::readskb().
While here, also inform the peer that we've freed up space and it has more credit.
Failing to update rxbytes after packet is dequeued leads to a warning on SOCKSTREAM recv():
[ 233.396654] rxqueue is empty, but rxbytes is non-zero [ 233.396702] WARNING: CPU: 11 PID: 40601 at net/vmwvsock/virtiotransportcommon.c:589
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.11.6-1 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.1.176-1Fixed in 6.1.190-1Fixed in 6.12.107-1Fixed in 6.12.115-2Fixed in 7.2.12-1Fixed in 7.2.15-1
Event History
Frequently Asked Questions
What is the severity of CVE-2024-50169?
The severity of CVE-2024-50169 is currently classified as moderate.
What systems are affected by CVE-2024-50169?
CVE-2024-50169 affects various versions of the Linux kernel between 6.4 and 6.6.59, as well as specific release candidates of version 6.12.
How do I fix CVE-2024-50169?
To fix CVE-2024-50169, you should update your Linux kernel to a version that includes the patch addressing this vulnerability.
What does CVE-2024-50169 specifically impact?
CVE-2024-50169 specifically impacts the handling of virtual socket operations in the Linux kernel, affecting the update of rx_bytes.
Is CVE-2024-50169 actively being exploited?
As of now, there have been no widespread reports of CVE-2024-50169 being actively exploited in the wild.