CVE-2024-57843: virtio-net: fix overflow inside virtnet_rq_alloc

Published Jan 11, 2025
·
Updated

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

5 affected componentsFixes available
Linux Kernel
debian/linux<=5.10.223-1, <=5.10.234-1, <=6.1.129-1, <=6.1.135-1
6.12.25-1
Linux Linux kernel<6.6.66
Linux Linux kernel>=6.7<6.12.5
Microsoft cbl2 kernel 5.15.186.1-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 6.12.25-1

Event History

Jan 11, 2025
CVE Published
via MITRE·02:30 PM
Data Sourced
via MITRE·02:30 PM
DescriptionSeverity
Data Sourced
via Red Hat·03:01 PM
DescriptionSeverityAffected Software
Data Sourced
via NVD·03:15 PM
Description
Data Sourced
via NVD·03:15 PM
RemedySeverityWeaknessAffected Software
Mar 27, 2025
Data Sourced
via Launchpad·06:48 PM
Description
May 2, 2025
Data Sourced
via Ubuntu·06:56 PM
RemedyDescriptionSeverityAffected Software
Sep 27, 2025
Data Sourced
via Microsoft·01:02 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·01:02 AM
Affected Software
Updated
via Microsoft·01:02 AM
DescriptionSeverity
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2024-57843?

The severity of CVE-2024-57843 is classified as medium.

2

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.

3

What systems are affected by CVE-2024-57843?

CVE-2024-57843 affects systems running specific versions of the Linux Kernel that utilize virtio-net.

4

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.

5

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.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203