CVE-2024-57843: virtio-net: fix overflow inside virtnet_rq_alloc
In the Linux kernel, the following vulnerability has been resolved:
virtio-net: fix overflow inside virtnetrqalloc
When the frag just got a page, then may lead to regression on VM. Specially if the sysctl net.core.highorderallocdisable value is 1, then the frag always get a page when do refill.
Which could see reliable crashes or scp failure (scp a file 100M in size to VM).
The issue is that the virtnetrqdma takes up 16 bytes at the beginning of a new frag. When the frag size is larger than PAGESIZE, everything is fine. However, if the frag is only one page and the total size of the buffer and virtnetrqdma is larger than one page, an overflow may occur.
The commit f9dac92ba908 ("virtioring: enable premapped mode whatever usedmaapi") introduced this problem. And we reverted some commits to fix this in last linux version. Now we try to enable it and fix this bug directly.
Here, when the frag size is not enough, we reduce the buffer len to fix this problem.
Other sources
This CVE was automatically created from a reference found in an email or other text. If you are reading this, then this CVE entry is probably erroneous, since this text should be replaced by the official CVE description automatically.
— Launchpad
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.12.25-1
Event History
Frequently Asked Questions
What is the severity of CVE-2024-57843?
The severity of CVE-2024-57843 is classified as medium.
How do I fix CVE-2024-57843?
To fix CVE-2024-57843, you should update to the latest version of the Linux Kernel where the vulnerability has been resolved.
What systems are affected by CVE-2024-57843?
CVE-2024-57843 affects systems running specific versions of the Linux Kernel that utilize virtio-net.
What is the impact of CVE-2024-57843?
The impact of CVE-2024-57843 may lead to a regression on virtual machines under certain configurations.
Is there a workaround for CVE-2024-57843?
A possible workaround for CVE-2024-57843 could involve adjusting the sysctl net.core.high_order_alloc_disable setting.