LiveActive security incident?Get immediate response
CVE Record

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 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.

CriticalCVSS 9.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

A Linux virtio-net receive-buffer bug can write beyond a one-page allocation, causing reliable virtual-machine crashes or failed large file transfers under reported conditions. The supplied CVSS rating is 9.8, but the available description demonstrates operational disruption rather than confirmed remote compromise or data theft.

Executive priority

Treat as an urgent reliability and availability issue for affected virtualized Linux workloads. Accelerate kernel patching where virtio-net is present, while avoiding unsupported claims of active attacks or demonstrated data compromise.

Technical view

virtnet_rq_alloc may allocate a one-page fragment without enough room for both the receive buffer and the 16-byte virtnet_rq_dma metadata. The resulting overflow was introduced by commit f9dac92ba908. The stable fixes reduce buffer length when fragment space is insufficient.

Likely exposure

Exposure is limited to Linux systems using virtio-net on affected kernel revisions. The bundle lists 6.6, 6.6.66, 6.12.5, and 6.13, but does not clearly express complete version ranges. Reproduction is reportedly more reliable when net.core.high_order_alloc_disable equals 1.

Exploitation context

The source bundle does not establish active exploitation, and the CVE is not listed as KEV. Reported outcomes are virtual-machine crashes and failed SCP transfers. Although the supplied CVSS vector claims network-accessible, unauthenticated compromise of confidentiality, integrity, and availability, those broader impacts are not demonstrated in the description.

Researcher notes

The technical account supports an allocation overflow in the receive path and reproducible crashes. It does not explain how network input provides attacker control sufficient for the full CVSS confidentiality and integrity impacts. Exact affected-range semantics are also incomplete in the supplied bundle; validate against distribution advisories and stable-branch commit ancestry.

Mitigation direction

  • Update to a vendor-supported kernel containing the applicable cited stable fix.
  • Confirm the vendor package maps to the correct fix for its maintained kernel branch.
  • Prioritize affected virtual machines performing sustained or high-volume network transfers.
  • Consult Linux distribution guidance if fixed package availability or affected ranges remain unclear.

Validation and detection

  • Inventory Linux virtual machines, kernel versions, and use of virtio-net interfaces.
  • Check vendor changelogs for inclusion of the applicable cited stable commit.
  • Record net.core.high_order_alloc_disable as an exposure and reproducibility factor.
  • Review kernel logs for virtio-net crashes and investigate unexplained large-transfer failures.
  • Perform approved network regression testing in a non-production environment after updating.
Prepared
Confidence
medium
Sources
5

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2024-57843 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2024-57843Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux295525e29a5b5694a6e96864f0c1365f79639863, 295525e29a5b5694a6e96864f0c1365f79639863, 295525e29a5b5694a6e96864f0c1365f79639863unaffected
LinuxLinux6.6, 0, 6.6.66, 6.12.5, 6.13affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.