CVE-2026-98158
Description
A flaw was found in the Linux kernel's Point-to-Point Protocol asynchronous (ppp_async) driver. When handling corrupted network frames, the driver improperly reuses packet buffers without preserving the required memory headroom. A connected peer can exploit this flaw by sending a sequence of crafted network frames, triggering an out-of-bounds memory read and a system crash, resulting in a Denial of Service (DoS).
Statement
A moderate denial-of-service vulnerability was found in the Linux kernel's Point-to-Point Protocol asynchronous (ppp_async) driver, affecting the Red Hat Enterprise Linux kernel and kernel-rt, Red Hat In-Vehicle OS, and OpenShift (RHEL CoreOS) kernels. On the frame-error path, ppp_async's process_input_packet() resets a reused socket buffer's headroom to zero instead of preserving the NET_SKB_PAD headroom that dev_alloc_skb() guarantees, so the next frame is reassembled into a buffer with no headroom at all. A peer on an established PPP asynchronous link can exploit this by sending a frame with a bad FCS followed by a crafted frame, which causes the two-byte PPP filter direction tag pushed in ppp_receive_nonmp_frame() to be written before the start of the buffer and triggers an skb_under_panic that crashes the kernel. When CCP compression is enabled, ppp_decompress_frame() can also read out of bounds before the start of the buffer for the same reason. The verified consequence is a system-wide denial of service; no confidentiality or integrity impact has been demonstrated. Red Hat rates the impact of this flaw as moderate because exploitation requires the ability to exchange traffic as a peer on a configured PPP asynchronous link on the affected system and because only availability is affected. Red Hat Enterprise Linux 6 is not affected because the vulnerable code is not present in that release. Given the moderate impact rating and the constrained exposure, fixes for the affected products are currently deferred; the residual risk is that an attacker able to act as a peer on an established PPP asynchronous link can crash an affected system.
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 Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 5.5 | N/A | N/A |
| Attack Vector | Local | N/A | N/A |
| Attack Complexity | Low | N/A | N/A |
| Privileges Required | Low | N/A | N/A |
| User Interaction | None | N/A | N/A |
| Scope | Unchanged | N/A | N/A |
| Confidentiality | None | N/A | N/A |
| Integrity Impact | None | N/A | N/A |
| Availability Impact | High | N/A | N/A |
Vector
Red Hat: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Understanding the Weakness (CWE)
Integrity,Availability
Technical Impact: Modify Memory; DoS: Crash, Exit, or Restart
Out of bounds memory access will very likely result in the corruption of relevant memory, and perhaps instructions, possibly leading to a crash.
Integrity,Confidentiality,Availability,Access Control,Other
Technical Impact: Execute Unauthorized Code or Commands; Modify Memory; Bypass Protection Mechanism; Other
If the corrupted memory can be effectively controlled, it may be possible to execute arbitrary code. If the corrupted memory is data rather than instructions, the system will continue to function with improper changes, possibly in violation of an implicit or explicit policy. The consequences would only be limited by how the affected data is used, such as an adjacent memory location that is used to specify whether the user has special privileges.
Access Control,Other
Technical Impact: Bypass Protection Mechanism; Other
When the consequence is arbitrary code execution, this can often be used to subvert any other security service.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.