CVE-2023-54012

Description

A flaw was found in the Linux kernel's networking subsystem. When updating configuration settings, such as disabling Large Receive Offload (LRO), on stacked virtual network interfaces like bonding or team devices, event notifications can trigger repeatedly between upper and lower interfaces. This unintended recursion results in a kernel stack overflow and system crash, allowing a local privileged user to cause a denial of service (DoS).

Statement

This is a network robustness issue caused by unintended recursion in NETDEV_FEAT_CHANGE notifications for stacked bonding/team interfaces. Under specific virtual topology setups it can lead to kernel stack overflow and system crash, resulting in a local denial-of-service. It does not allow memory corruption, privilege escalation, or code execution.

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.5N/A7.8
Attack VectorLocalN/ALocal
Attack ComplexityLowN/ALow
Privileges RequiredLowN/ALow
User InteractionNoneN/ANone
ScopeUnchangedN/AUnchanged
ConfidentialityNoneN/AHigh
Integrity ImpactNoneN/AHigh
Availability ImpactHighN/AHigh

Vector

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

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

Understanding the Weakness (CWE)

Availability

Technical Impact: DoS: Resource Consumption (CPU); DoS: Resource Consumption (Memory)

Resources including CPU, memory, and stack memory could be rapidly consumed or exhausted, eventually leading to an exit or crash.

Confidentiality

Technical Impact: Read Application Data

In some cases, an application's interpreter might kill a process or thread that appears to be consuming too many resources, such as with PHP's memory_limit setting. When the interpreter kills the process/thread, it might report an error containing detailed information such as the application's installation path.

Frequently Asked Questions

Want to get errata notifications? Sign up here.