CVE-2026-53003

pppoe: drop PFC frames

HIGH
7.5
CVSS Score
Published: June 24, 2026 at 04:29 PM UTC
Updated: October 19, 2026 at 08:18 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.5
Exploit prediction
EPSS 0.7%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: pppoe: drop PFC frames RFC 2516 Section 7 states that Protocol Field Compression (PFC) is NOT RECOMMENDED for PPPoE. In practice, pppd does not support negotiating PFC for PPPoE sessions, and the current PPPoE driver assumes an uncompressed (2-byte) protocol field. However, the generic PPP layer function ppp_input() is not aware of the negotiation result, and still accepts PFC frames. If a peer with a broken implementation or an attacker sends a frame with a compressed (1-byte) protocol field, the subsequent PPP payload is shifted by one byte. This causes the network header to be 4-byte misaligned, which may trigger unaligned access exceptions on some architectures. To reduce the attack surface, drop PPPoE PFC frames. Introduce ppp_skb_is_compressed_proto() helper function to be used in both ppp_generic.c and pppoe.c to avoid open-coding.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.0 ≤ v < 5.10.2585.11 ≤ v < 5.15.2095.16 ≤ v < 6.1.1756.13 ≤ v < 6.18.336.19 ≤ v < 7.0.106.2 ≤ v < 6.6.1416.7 ≤ v < 6.12.915.07fb1b8ca8fa1ee34ffc328f17f78da68c7cc04e6
Vendor states this is fixed in 0cab5d077dd1efd2bd1a47271acc35894f945b4f (fixed)
Vendor states this is fixed in 2b5c3c040d020e3ab3b9a8887031202d96843b1e (fixed)
Vendor states this is fixed in 49e41b60ccd1bdbe9e218420f716dd5f9a2f9c71 (fixed)
Vendor states this is fixed in 8a5e840babc5c0fbd10c73728a13192347771ec6 (fixed)
Vendor states this is fixed in ba758fdf1399f310b30098b6faa3fd043de47dd2 (fixed)
Vendor states this is fixed in cb3beef35ab5e0c1afca9fd7648c6ae499786377 (fixed)
Vendor states this is fixed in cc1ff87bce1ccd38410ab10960f576dcd17db679 (fixed)
Vendor states this is fixed in fcca1df05322bb04e344dd1178b54b76a08eb7c3 (fixed)
Vendor states this is fixed in 5.0 (unaffected)
Vendor states this is fixed in 5.10.258 (unaffected)
Vendor states this is fixed in 5.15.209 (unaffected)
Vendor states this is fixed in 6.1.175 (unaffected)
Vendor states this is fixed in 6.12.91 (unaffected)
Vendor states this is fixed in 6.18.33 (unaffected)
Vendor states this is fixed in 6.6.141 (unaffected)
Vendor states this is fixed in 7.0.10 (unaffected)
Vendor states this is fixed in 7.1 (unaffected)

SSVC — Action Prioritization

SSVCNo known exploitAutomatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.5HIGHLinux
Vector?

Quick Info

StatusMODIFIED
CWE
NVD-CWE-noinfoCWE-20

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card