CVE-2025-39673

Description

A flaw was found in the Linux kernel's Point-to-Point Protocol (PPP) component. Due to a race condition during forwarding path resolution, the kernel can attempt to access freed memory or a null pointer when network channels are disconnected concurrently. An attacker could exploit this timing vulnerability on systems utilizing PPP forwarding to trigger a kernel crash, resulting in a denial of service (DoS).

Statement

A race in ppp_fill_forward_path() could access an empty/freed list entry or a NULL pch->chan when resolving the forwarding path, leading to a kernel crash. The fix converts channel list operations to RCU (list_first_or_null_rcu, list_add_tail_rcu, list_del_rcu + synchronize_net()) and guards pch->chan with READ_ONCE(). Impact is limited to remote denial of service on systems using PPP/PPPoE forwarding.

Mitigation

To mitigate this issue, prevent module ppp_generic from being loaded. Please see https://access.redhat.com/solutions/41278 for how to blacklist a kernel module to prevent it from loading automatically.

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.94.79.8
Attack VectorNetworkLocalNetwork
Attack ComplexityHighHighLow
Privileges RequiredNoneLowNone
User InteractionNoneNoneNone
ScopeUnchangedUnchangedUnchanged
ConfidentialityNoneNoneHigh
Integrity ImpactNoneNoneHigh
Availability ImpactHighHighHigh

Vector

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

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

cve.org: CVSS:3.1/AV:N/AC:L/PR:N/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); DoS: Resource Consumption (Other)

When a race condition makes it possible to bypass a resource cleanup routine or trigger multiple initialization routines, it may lead to resource exhaustion.

Availability

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

When a race condition allows multiple control flows to access a resource simultaneously, it might lead the product(s) into unexpected states, possibly resulting in a crash.

Confidentiality,Integrity

Technical Impact: Read Files or Directories; Read Application Data

When a race condition is combined with predictable resource names and loose permissions, it may be possible for an attacker to overwrite or access confidential data (CWE-59).

Access Control

Technical Impact: Execute Unauthorized Code or Commands; Gain Privileges or Assume Identity; Bypass Protection Mechanism

This can have security implications when the expected synchronization is in security-critical code, such as recording whether a user is authenticated or modifying important state information that should not be influenced by an outsider.

Frequently Asked Questions

Want to get errata notifications? Sign up here.