CVE-2026-53003

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-06-24. the CNA's CVSS baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
38(Track)
EG Risk 38/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation1% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
41%
KEV
Not listed

Published

June 24, 2026

Last Modified

August 5, 2026

Advisory Details (8)

Auto-updated Jun 28, 2026
No patch confirmed yet.
generic

pppoe: drop PFC frames - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/fcca1df05322bb04e344dd1178b54b76a08eb7c3
generic

pppoe: drop PFC frames - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/cc1ff87bce1ccd38410ab10960f576dcd17db679
generic

pppoe: drop PFC frames - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/cb3beef35ab5e0c1afca9fd7648c6ae499786377
generic

pppoe: drop PFC frames - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ba758fdf1399f310b30098b6faa3fd043de47dd2
generic

pppoe: drop PFC frames - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8a5e840babc5c0fbd10c73728a13192347771ec6
generic

pppoe: drop PFC frames - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/49e41b60ccd1bdbe9e218420f716dd5f9a2f9c71
generic

pppoe: drop PFC frames - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2b5c3c040d020e3ab3b9a8887031202d96843b1e
generic

pppoe: drop PFC frames - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0cab5d077dd1efd2bd1a47271acc35894f945b4f

Vendor Advisories for CVE-2026-53003(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(30)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-28.28) @ resolute2026-08-30ubuntu
ubuntulinux-virtual-6.8 (6.8.0-136.136) @ noble2026-08-30ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1009.9) @ resolute2026-08-30ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2050.52) @ noble2026-08-30ubuntu
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-28.28~24.04.1) @ noble2026-08-30ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1064.72+fips1) @ noble2026-08-30ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.15.0-1075 (5.15.0-1075.79) @ jammy2026-08-30ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1064.66~20.04.1) @ focal2026-08-30ubuntu
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-08-30ubuntu
ubuntulinux-tools-oracle-lts-24.04 (6.8.0-1058.61) @ noble2026-08-30ubuntu
ubuntulinux-tools-oracle-edge (6.8.0-1058.61~22.04.1) @ jammy2026-08-30ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1059.62.1) @ noble2026-08-30ubuntu
ubuntulinux-tools-nvidia-lowlatency-5.15 (5.15.0.1107.107) @ jammy2026-08-30ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1064.64) @ jammy2026-08-30ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-08-30ubuntu
ubuntulinux-tools-aws-lts-24.04 (6.8.0-1061.64+1) @ noble2026-08-30ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1063.71) @ noble2026-08-30ubuntu
ubuntulinux-tools-azure-fde-lts-24.04 (6.8.0-1062.69) @ noble2026-08-30ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1063.71+fips2) @ noble2026-08-30ubuntu
ubuntulinux-tools-azure-fde-6.8 (6.8.0-1062.69~22.04.1) @ jammy2026-08-30ubuntu
ubuntulinux-tools-oracle-lts-22.04 (5.15.0.1109.105) @ jammy2026-08-30ubuntu
ubuntulinux-tools-azure-fde-lts-22.04 (5.15.0.1117.126) @ jammy2026-08-30ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-08-30ubuntu
ubuntulinux-tools-aws-edge (6.8.0-1061.64~22.04.1) @ jammy2026-08-30ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1033.34) @ noble2026-08-30ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-136.136~22.04.1) @ jammy2026-08-30ubuntu
ubuntulinux-tools-azure-fips-5.15 (5.15.0.1117.102) @ jammy2026-08-30ubuntu
ubuntulinux-tools-oracle-edge (5.15.0.1109.115~20.04.1) @ focal2026-08-30ubuntu
ubuntulinux-tools-intel-iot-realtime-5.15 (5.15.0.1104.108) @ jammy2026-08-30ubuntu
ubuntulinux-tools-intel-iotg-5.15 (5.15.0.1107.106) @ jammy2026-08-30ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (54 versions)5.10.259-1—
linux-6.16.1.106-3~deb11u1 ... 6.1.174-1~deb11u1 (20 versions)6.1.176-1~deb11u1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)6.1.176-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)6.12.94-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (140 versions)7.0.10-1—

Additional Vendor Advisories

(24)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 5× in last 7d / 87× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 284 total refreshes for this CVE.

  1. 2026-09-11 14:53 UTCEPSS rescore
  2. 2026-09-10 09:35 UTCEPSS rescore
  3. 2026-09-08 22:01 UTCEPSS rescore
  4. 2026-09-07 16:01 UTCEPSS rescore
  5. 2026-09-06 13:47 UTCEPSS rescore
  6. 2026-09-04 05:06 UTCEPSS rescore
  7. 2026-09-02 14:12 UTCEPSS rescore
  8. 2026-09-01 13:54 UTCEPSS rescore
  9. 2026-09-01 04:40 UTCEPSS rescore
  10. 2026-08-30 20:09 UTCEG score recompute
  11. 2026-08-30 20:09 UTCVendor advisory
  12. 2026-08-30 20:09 UTCGHSA enrichment
  13. 2026-08-30 19:17 UTCEPSS rescore
  14. 2026-08-30 01:22 UTCEPSS rescore
  15. 2026-08-28 21:41 UTCEPSS rescore
  16. 2026-08-28 04:46 UTCEG score recompute
  17. 2026-08-28 04:46 UTCVendor advisory
  18. 2026-08-28 04:46 UTCGHSA enrichment
  19. 2026-08-27 14:25 UTCEPSS rescore
  20. 2026-08-26 14:46 UTCEPSS rescore
  21. 2026-08-25 13:49 UTCEPSS rescore
  22. 2026-08-25 01:29 UTCEG score recompute
  23. 2026-08-25 01:29 UTCVendor advisory
  24. 2026-08-25 01:29 UTCGHSA enrichment
  25. 2026-08-24 13:42 UTCEG score recompute
Show 75 more
  1. 2026-08-24 13:42 UTCVendor advisory
  2. 2026-08-24 13:42 UTCGHSA enrichment
  3. 2026-08-24 00:22 UTCVendor advisory
  4. 2026-08-24 00:21 UTCGHSA enrichment
  5. 2026-08-23 12:38 UTCVendor advisory
  6. 2026-08-23 12:38 UTCGHSA enrichment
  7. 2026-08-23 00:56 UTCEG score recompute
  8. 2026-08-23 00:56 UTCVendor advisory
  9. 2026-08-23 00:55 UTCGHSA enrichment
  10. 2026-08-23 00:19 UTCEPSS rescore
  11. 2026-08-22 13:05 UTCEG score recompute
  12. 2026-08-22 13:05 UTCVendor advisory
  13. 2026-08-22 13:04 UTCGHSA enrichment
  14. 2026-08-21 23:49 UTCEPSS rescore
  15. 2026-08-21 19:08 UTCVendor advisory
  16. 2026-08-21 19:07 UTCGHSA enrichment
  17. 2026-08-21 07:17 UTCEG score recompute
  18. 2026-08-21 07:17 UTCVendor advisory
  19. 2026-08-21 07:16 UTCGHSA enrichment
  20. 2026-08-20 22:55 UTCEPSS rescore
  21. 2026-08-20 19:11 UTCVendor advisory
  22. 2026-08-20 19:11 UTCGHSA enrichment
  23. 2026-08-20 07:29 UTCEG score recompute
  24. 2026-08-20 07:29 UTCVendor advisory
  25. 2026-08-20 07:28 UTCGHSA enrichment
  26. 2026-08-19 17:04 UTCEPSS rescore
  27. 2026-08-19 14:16 UTCVendor advisory
  28. 2026-08-19 14:15 UTCGHSA enrichment
  29. 2026-08-19 02:10 UTCEG score recompute
  30. 2026-08-19 02:10 UTCVendor advisory
  31. 2026-08-19 02:10 UTCGHSA enrichment
  32. 2026-08-18 13:48 UTCEPSS rescore
  33. 2026-08-17 13:47 UTCEPSS rescore
  34. 2026-08-17 07:51 UTCVendor advisory
  35. 2026-08-17 07:51 UTCGHSA enrichment
  36. 2026-08-16 20:08 UTCEG score recompute
  37. 2026-08-16 20:08 UTCVendor advisory
  38. 2026-08-16 20:08 UTCGHSA enrichment
  39. 2026-08-16 14:56 UTCEPSS rescore
  40. 2026-08-16 08:25 UTCEG score recompute
  41. 2026-08-16 08:25 UTCVendor advisory
  42. 2026-08-16 08:25 UTCGHSA enrichment
  43. 2026-08-16 02:14 UTCEPSS rescore
  44. 2026-08-15 20:43 UTCVendor advisory
  45. 2026-08-15 20:43 UTCGHSA enrichment
  46. 2026-08-15 08:40 UTCEG score recompute
  47. 2026-08-15 08:40 UTCVendor advisory
  48. 2026-08-15 08:40 UTCGHSA enrichment
  49. 2026-08-15 01:30 UTCEPSS rescore
  50. 2026-08-14 20:10 UTCVendor advisory
  51. 2026-08-14 20:10 UTCGHSA enrichment
  52. 2026-08-14 08:28 UTCEG score recompute
  53. 2026-08-14 08:28 UTCVendor advisory
  54. 2026-08-14 08:28 UTCGHSA enrichment
  55. 2026-08-13 22:00 UTCEPSS rescore
  56. 2026-08-13 20:45 UTCVendor advisory
  57. 2026-08-13 20:45 UTCGHSA enrichment
  58. 2026-08-13 08:55 UTCVendor advisory
  59. 2026-08-13 08:55 UTCGHSA enrichment
  60. 2026-08-12 21:13 UTCEG score recompute
  61. 2026-08-12 21:13 UTCVendor advisory
  62. 2026-08-12 21:13 UTCGHSA enrichment
  63. 2026-08-12 13:51 UTCEPSS rescore
  64. 2026-08-12 09:31 UTCVendor advisory
  65. 2026-08-12 09:31 UTCGHSA enrichment
  66. 2026-08-11 21:48 UTCEG score recompute
  67. 2026-08-11 21:48 UTCVendor advisory
  68. 2026-08-11 21:48 UTCGHSA enrichment
  69. 2026-08-11 10:06 UTCEG score recompute
  70. 2026-08-11 10:06 UTCVendor advisory
  71. 2026-08-11 10:06 UTCGHSA enrichment
  72. 2026-08-11 00:00 UTCEPSS rescore
  73. 2026-08-10 22:24 UTCVendor advisory
  74. 2026-08-10 22:24 UTCGHSA enrichment
  75. 2026-08-10 10:39 UTCVendor advisory

Frequently asked(5)

What is CVE-2026-53003?
CVE-2026-53003 is a high vulnerability published on June 24, 2026. 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…
When was CVE-2026-53003 disclosed?
CVE-2026-53003 was first published in the National Vulnerability Database on June 24, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53003 actively exploited?
CVE-2026-53003 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 58.7% of all scored CVEs.
What is the CVSS score of CVE-2026-53003?
CVE-2026-53003 has a CVSS v4.0 base score of 7.5 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-53003?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53003, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-53003

Explore →

Is Your Infrastructure Affected by CVE-2026-53003?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs