CVE-2022-49845

Description

A flaw was found in the Linux kernel's Controller Area Network (CAN) J1939 subsystem. A local attacker with permission to create J1939 sockets can cause a Denial of Service (DoS) and crash the system. This issue occurs in the j1939_send_one() function due to a missing initialization of CAN frame header fields when preparing network buffers. Accessing these uninitialized data elements during transmission leads to unexpected kernel behavior and instability.

Statement

This vulnerability is rated as having a Moderate severity because exploitation requires local access to create CAN J1939 sockets, restricting the blast radius to a localized denial of service rather than remote code execution. The CAN SAE J1939 protocol subsystem is not loaded or used by default in typical Red Hat Enterprise Linux environments. Consequently, systems are only exposed if CAN networking interfaces and J1939 sockets are actively configured and utilized.

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

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score5.55.55.5
Attack VectorLocalLocalLocal
Attack ComplexityLowLowLow
Privileges RequiredLowLowLow
User InteractionNoneNoneNone
ScopeUnchangedUnchangedUnchanged
ConfidentialityNoneNoneNone
Integrity ImpactNoneNoneNone
Availability ImpactHighHighHigh

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

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

Understanding the Weakness (CWE)

Confidentiality

Technical Impact: Read Memory; Read Application Data

When reusing a resource such as memory or a program variable, the original contents may not have been cleared before it is sent to an untrusted party.

Availability

Technical Impact: DoS: Crash, Exit, or Restart; DoS: Instability

The uninitialized resource may contain values that cause program flow to change in ways that the programmer did not intend, possibly leading to a crash.

Other

Technical Impact: Unexpected State; Varies by Context

The consequences vary depending on the type of resource and how it is used within the product.

Frequently Asked Questions

Want to get errata notifications? Sign up here.