Skip to main content

Linux CVE-2026-98287

| EUVDEUVD-2026-93215
2026-10-06 Linux GHSA-m2p4-c77r-p2c7
View
Monitor Track and reassess. Why: No CVSS yet + weak signal (CWE or non-zero EPSS).
Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisCVE.org

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

Affected VersionsENISA

Linux patch: 6.1.189
Linux 4cf476ced45d7f12df30a68e833b263e7a2202d1 <8e66c5969acd859ba72fb0a7fa895623fc1b3769
Linux 5.11
Linux patch: 7.3-rc4
Linux 4cf476ced45d7f12df30a68e833b263e7a2202d1 <ffc448eb54f5ba80d4212c1e870cdb92b0f709fa
Linux 4cf476ced45d7f12df30a68e833b263e7a2202d1 <208ccc4d08b1897451e9ba01c016bf93ff107966
Linux patch: 6.6.158
Linux patch: 6.12.112
Linux patch: 7.2.8
Linux 4cf476ced45d7f12df30a68e833b263e7a2202d1 <ecc7253683a3c55caa868ce0ee530fcb0044bd3c
Linux patch: 5.15.222
Linux patch: 6.18.54
Linux 4cf476ced45d7f12df30a68e833b263e7a2202d1 <30992fe39e65589ed8e000425e088fa74994b811
Linux 4cf476ced45d7f12df30a68e833b263e7a2202d1 <e6cd1bba7d113c15c00ac63671213a096fe4d686
Linux patch: 0
Linux 4cf476ced45d7f12df30a68e833b263e7a2202d1 <e2f5529b0016db7d34f411408607f5cf395a542e

Affected Packages

euvd linux no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Know when the next one hits your stack

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Lifecycle Timeline

2
Patch available
Oct 06, 2026 - 10:02 EUVD
CVE Published
Oct 06, 2026 - 08:45 cve.org
UNKNOWN (no severity yet)

Threat Intelligence Overview

EPSS Score
0.2%
Top 93% exploitable
Threat Intel
1
1 sources
Data Quality
3 sources
Confidence: Low

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity Not scored yet
CISA KEV No
Public POC No
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
No CVSS yet + weak signal (CWE or non-zero EPSS)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

Attack Technique

A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy