CVE-2026-53003
Last modified
CVE-2026-53003 is a high-severity vulnerability rated 7.5/10 on the CVSS scale. 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. EPSS estimates a 0.51% chance of exploitation in the next 30 days.
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.
Metrics
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| 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 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-53003?
How severe is CVE-2026-53003?
How do I fix CVE-2026-53003?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-52998In the Linux kernel, the following vulnerability has been re…7.5
- CVE-2026-52999In the Linux kernel, the following vulnerability has been re…9.1
- CVE-2026-5300Unauthenticated functionality in CoolerControl/coolercontro…9.1
- CVE-2026-53000In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-53001In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53002In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-53004In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-53005In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-53006In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-53007In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53008In the Linux kernel, the following vulnerability has been re…4.7
- CVE-2026-53009In the Linux kernel, the following vulnerability has been re…7.8
Are you affected by CVE-2026-53003?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
