CVE-2024-43835

Description

A flaw was found in the Linux kernel's virtio network driver (virtio_net). This vulnerability allows a local user to cause a Denial of Service (DoS) by triggering a system crash. The issue occurs because the driver incorrectly assumes it is operating within a network polling context during certain transmission operations, leading to internal kernel failures.

Statement

This vulnerability is rated as Moderate for Red Hat Enterprise Linux because exploitation requires local access within virtualized guest systems and is constrained to causing a denial of service. The flaw occurs in virtual guest instances operating the virtio network interface when transmit cleanup paths run outside of the standard softirq polling routine, such as during kernel netpoll operations. An unprivileged local attacker could trigger this condition to provoke a kernel warning or crash, but the vulnerability cannot be exploited remotely nor does it permit arbitrary code execution or data exposure.

Common Vulnerability Scoring System (CVSS) Score Details

Info alert:Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

The following CVSS metrics and score provided are preliminary and subject to review.

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score5.55.5N/A
Attack VectorLocalLocalN/A
Attack ComplexityLowLowN/A
Privileges RequiredLowLowN/A
User InteractionNoneNoneN/A
ScopeUnchangedUnchangedN/A
ConfidentialityNoneNoneN/A
Integrity ImpactNoneNoneN/A
Availability ImpactHighHighN/A

Vector

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

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

Understanding the Weakness (CWE)

Availability

Technical Impact: DoS: Resource Consumption (CPU)

Inconsistent locking discipline can lead to deadlock.

Integrity

Technical Impact: Modify Memory; Modify Application Data

This can lead to data or memory corruption.

Other

Technical Impact: Varies by Context; Unexpected State

This can lead to unexpected resource state changes and behaviors.

Frequently Asked Questions

Want to get errata notifications? Sign up here.