Description
In the Linux kernel, the following vulnerability has been resolved:

pppoatm: ensure a writable skb header and linear data

In pppoatm_send(), LLC encapsulation checks whether there is sufficient
headroom for the 4-byte LLC header, but does not ensure that the skb header
is writable.

Normal transmit packets passing through ppp_start_xmit() have their header
unshared via skb_cow_head(). However, packets can also reach pppoatm_send()
via PPP channel bridging (PPPIOCBRIDGECHAN) without going through
ppp_start_xmit().

Use skb_cow_head() to ensure both sufficient headroom and a writable
header before pushing the LLC header.

While at it:
- Call pskb_may_pull(skb, 1) before inspecting skb->data[0] to prevent
out-of-bounds reads on zero-length or non-linear frames (e.g. from
bridging).
- Defer SC_COMP_PROT protocol compression until after pppoatm_may_send()
succeeds. This eliminates the temporary skb allocation on admission failure
and completely removes the fragile "undo" heuristic at the nospace label,
avoiding any risk of reading uninitialized headroom or performing an
unbalanced skb_push().
Published: 2026-10-06
Score: 7.0 High
EPSS: < 1% Very Low
KEV: No
Impact: Kernel crash or memory corruption
Action: Apply patch
AI Analysis

Impact

The vulnerability resides in the PPPoATM module of the Linux kernel. During the pppoatm_send() operation, a 4‑byte LLC header is added after a check that only ensures there is enough headroom. The function does not confirm that the socket buffer header is writable, which can result in an attempt to write data to a non‑writable region. This memory corruption could lead to a kernel crash. No reporting of remote code execution or privilege escalation is present in the description.

Affected Systems

All Linux kernel builds that include the PPPoATM feature are potentially vulnerable. The report does not specify a version range, so any kernel that implements this code path, particularly those that support PPPoATM bridging, may be affected. The known identifiers list only contains the generic Linux kernel entry.

Risk and Exploitability

The CVSS score is 7.0, the EPSS score is <1%, so the likelihood of exploitation is very low. Based on the description, it is inferred that a crafted PPP packet sent to a system with PPPoATM bridging could activate the code path and trigger the missing write‑on‑write check. The vulnerability is not listed in the CISA KEV catalog, indicating no known widespread exploitation. Operators should evaluate the risk based on their exposure to PPPoATM traffic.

Generated by OpenCVE AI on October 9, 2026 at 14:13 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade to a Linux kernel release that incorporates the pppoatm_send fix.
  • If upgrading is not immediately possible, disable the PPPoATM module or PPP channel bridging features that exercise the vulnerable code path.
  • Continuously monitor system logs for kernel panics or abnormal memory corruption events that may indicate exploitation attempts.

Generated by OpenCVE AI on October 9, 2026 at 14:13 UTC.

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
Debian DLA Debian DLA DLA-4841-1 linux security update
Debian DLA Debian DLA DLA-4850-1 linux-6.12 security update
Debian DSA Debian DSA DSA-6568-1 linux security update
Ubuntu USN Ubuntu USN USN-8961-1 Linux kernel vulnerabilities
History

Fri, 09 Oct 2026 12:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-125
References
Metrics threat_severity

None

cvssV3_1

{'score': 7.0, 'vector': 'CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H'}

threat_severity

Moderate


Tue, 06 Oct 2026 14:30:00 +0000

Type Values Removed Values Added
Weaknesses CWE-119

Tue, 06 Oct 2026 09:00:00 +0000

Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: pppoatm: ensure a writable skb header and linear data In pppoatm_send(), LLC encapsulation checks whether there is sufficient headroom for the 4-byte LLC header, but does not ensure that the skb header is writable. Normal transmit packets passing through ppp_start_xmit() have their header unshared via skb_cow_head(). However, packets can also reach pppoatm_send() via PPP channel bridging (PPPIOCBRIDGECHAN) without going through ppp_start_xmit(). Use skb_cow_head() to ensure both sufficient headroom and a writable header before pushing the LLC header. While at it: - Call pskb_may_pull(skb, 1) before inspecting skb->data[0] to prevent out-of-bounds reads on zero-length or non-linear frames (e.g. from bridging). - Defer SC_COMP_PROT protocol compression until after pppoatm_may_send() succeeds. This eliminates the temporary skb allocation on admission failure and completely removes the fragile "undo" heuristic at the nospace label, avoiding any risk of reading uninitialized headroom or performing an unbalanced skb_push().
Title pppoatm: ensure a writable skb header and linear data
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-10-19T09:16:58.585Z

Reserved: 2026-09-25T10:25:14.336Z

Link: CVE-2026-98287

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-10-06T09:18:18.880

Modified: 2026-10-19T10:18:30.283

Link: CVE-2026-98287

cve-icon Redhat

Severity : Moderate

Publid Date: 2026-10-06T00:00:00Z

Links: CVE-2026-98287 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-10-09T14:15:09Z

Weaknesses
  • CWE-119

    Improper Restriction of Operations within the Bounds of a Memory Buffer

  • CWE-125

    Out-of-bounds Read