CVE-2026-53003: pppoe: drop PFC frames

Published Jun 24, 2026
·
Updated

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 pppinput() 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 pppskbiscompressedproto() helper function to be used in both pppgeneric.c and pppoe.c to avoid open-coding.

Affected Software

9 affected componentsFixes available
The Linux Foundation Linux Kernel
Microsoft azl3 kernel 6.6.139.1-1<6.6.143.1-1
6.6.143.1-1
Linux Linux kernel>=5.0<5.10.258
Linux Linux kernel>=5.11<5.15.209
Linux Linux kernel>=5.16<6.1.175
Linux Linux kernel>=6.2<6.6.141
Linux Linux kernel>=6.7<6.12.91
Linux Linux kernel>=6.13<6.18.33
Linux Linux kernel>=6.19<7.0.10

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 6.6.143.1-1
  2. Configuration

    To reduce the attack surface, configure/patch PPPoE handling to drop PPPoE PFC frames, since PPPoE PFC is not accepted and can trigger misaligned network headers and unaligned access exceptions.

    Linux kernel PPPoE drop PPPoE Protocol Field Compression (PFC) frames = enabled

Event History

Jun 24, 2026
CVE Published
via MITRE·04:29 PM
Data Sourced
via MITRE·04:29 PM
DescriptionSeverity
Data Sourced
via NVD·05:17 PM
RemedyDescriptionSeverityAffected Software
Jun 27, 2026
Data Sourced
via Microsoft·08:12 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·08:12 AM
Affected Software
Updated
via Microsoft·08:12 AM
DescriptionSeverity
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-53003?

CVE-2026-53003 has a high severity rating of 7.5.

2

What is the risk associated with CVE-2026-53003?

The risk associated with CVE-2026-53003 is rated as 43.

3

How do I fix CVE-2026-53003?

The fix for CVE-2026-53003 involves updating to the latest version of the Linux kernel that resolves this vulnerability.

4

Which software is affected by CVE-2026-53003?

CVE-2026-53003 affects the Linux kernel and related systems managed by The Linux Foundation and Microsoft.

5

What does CVE-2026-53003 involve regarding PPPoE?

CVE-2026-53003 pertains to dropping Protocol Field Compression (PFC) frames in PPPoE sessions, as PFC is not recommended for use according to RFC 2516.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203