CVE-2026-74667

Description

A flaw was found in the Linux kernel's networking packet handling. Specifically, the packet_parse_headers() function does not consistently reset the Media Access Control (MAC) header for certain packet types on the PACKET_QDISC_BYPASS path. This can lead to an unset MAC header, causing a driver to perform an out-of-bounds read when processing network frames. This memory corruption vulnerability could result in system instability or a denial of service.

Statement

A moderate severity flaw was found in the Linux kernel's packet socket (AF_PACKET) transmit path, affecting the kernel and kernel-rt packages in Red Hat Enterprise Linux 8, 9, and 10 as well as Red Hat In-Vehicle OS. The packet_parse_headers() function resets the skb MAC header only for a SOCK_RAW frame whose socket did not bind a protocol; protocol-bound SOCK_RAW sockets, SOCK_DGRAM frames, and the legacy SOCK_PACKET path therefore leave skb->mac_header unset. Frames sent through the regular __dev_queue_xmit() path are not affected because it resets the MAC header unconditionally, but frames sent on the PACKET_QDISC_BYPASS path through dev_direct_xmit() reach the driver's ndo_start_xmit() with the MAC header unset. A local attacker able to transmit frames through a packet socket (SOCK_RAW requires CAP_NET_RAW, while SOCK_DGRAM does not) could exploit this so that a driver reading eth_hdr(skb) on transmit dereferences memory roughly 64 KiB past the start of the socket buffer, an out-of-bounds read that can crash the system and cause a denial of service. Red Hat Enterprise Linux 7 is not affected because the vulnerable code is not present in that release. The fix is currently deferred on the affected Red Hat Enterprise Linux and Red Hat In-Vehicle OS streams; given the Moderate rating and the local, availability-only nature of the flaw, the residual risk is a local denial of service by an attacker with packet-socket transmit access. Red Hat rates this flaw Moderate (CVSS 3.1 score 5.5, AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H), which differs from the upstream CVEORG rating of Important (7.8 with high confidentiality and integrity impact); no path to information disclosure or privilege escalation has been established beyond the out-of-bounds read and the resulting crash.

Mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

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)

Confidentiality

Technical Impact: Read Memory

If the uninitialized pointer is used in a read operation, it might not point to a valid memory location. An attacker might be able to read sensitive portions of memory.

Availability

Technical Impact: DoS: Crash, Exit, or Restart

If the uninitialized pointer references a memory location that is not accessible to the product, or points to a location that is "malformed" (such as NULL) or larger than expected by a read or write operation, then a crash may occur.

Integrity,Confidentiality,Availability

Technical Impact: Execute Unauthorized Code or Commands

If the uninitialized pointer is used in a function call, or points to unexpected data in a write operation, then code execution may be possible. If the uninitialized pointer is used as a function call, then arbitrary functions could be invoked.

Frequently Asked Questions

Want to get errata notifications? Sign up here.