- Vulnerability/
- CVE-2024-57843
CVE-2024-57843: virtio-net: fix overflow inside virtnet_rq_alloc
First published: Sat Jan 11 2025(Updated: )
In the Linux kernel, the following vulnerability has been resolved: virtio-net: fix overflow inside virtnet_rq_alloc When the frag just got a page, then may lead to regression on VM. Specially if the sysctl net.core.high_order_alloc_disable 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 virtnet_rq_dma takes up 16 bytes at the beginning of a new frag. When the frag size is larger than PAGE_SIZE, everything is fine. However, if the frag is only one page and the total size of the buffer and virtnet_rq_dma is larger than one page, an overflow may occur. The commit f9dac92ba908 ("virtio_ring: enable premapped mode whatever use_dma_api") 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.
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Red Hat Kernel-devel | ||
| debian/linux | <=5.10.223-1<=5.10.234-1<=6.1.129-1<=6.1.128-1 | 6.12.20-1 6.12.21-1 |
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.
Reference Links
- https://git.kernel.org/stable/c/67a11de8965c2ab19e215fb6651d44847e068614
- https://git.kernel.org/stable/c/6aacd1484468361d1d04badfe75f264fa5314864
- https://git.kernel.org/stable/c/a8f7d6963768b114ec9644ff0148dde4c104e84b
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-57843
- https://nvd.nist.gov/vuln/detail/CVE-2024-57843
- https://launchpad.net/bugs/cve/CVE-2024-57843
- https://security-tracker.debian.org/tracker/CVE-2024-57843
- https://ubuntu.com/security/CVE-2024-57843
- https://git.kernel.org/linus/6aacd1484468361d1d04badfe75f264fa5314864
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.
- agent/severity
- agent/title
- agent/type
- agent/first-publish-date
- collector/nvd-api
- source/NVD
- agent/author
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/guess-ai
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- collector/usn-cve
- source/Ubuntu
- collector/nvd-cve
- collector/launchpad-cve
- source/Launchpad
- agent/description
- agent/references
- agent/source
- agent/softwarecombine
- agent/tags
- agent/event
- collector/security-tracker-debian
- source/Debian
- vendor/linux
- canonical/red hat kernel-devel
- package-manager/debian