CVE-2026-46306

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-06-08. a secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

flow_dissector: do not dissect PPPoE 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 flow dissector driver has assumed an uncompressed frame until the blamed commit.

During the review process of that commit [1], support for PFC is suggested. However, having a compressed (1-byte) protocol field means the subsequent PPP payload is shifted by one byte, causing 4-byte misalignment for the network header and an unaligned access exception on some architectures.

The exception can be reproduced by sending a PPPoE PFC frame to an ethernet interface of a MIPS board, with RPS enabled, even if no PPPoE session is active on that interface:

$ 0 : 00000000 80c40000 00000000 85144817 $ 4 : 00000008 00000100 80a75758 81dc9bb8 $ 8 : 00000010 8087ae2c 0000003d 00000000 $12 : 000000e0 00000039 00000000 00000000 $16 : 85043240 80a75758 81dc9bb8 00006488 $20 : 0000002f 00000007 85144810 80a70000 $24 : 81d1bda0 00000000 $28 : 81dc8000 81dc9aa8 00000000 805ead08 Hi : 00009d51 Lo : 2163358a epc : 805e91f0 __skb_flow_dissect+0x1b0/0x1b50 ra : 805ead08 __skb_get_hash_net+0x74/0x12c Status: 11000403 KERNEL EXL IE Cause : 40800010 (ExcCode 04) BadVA : 85144817 PrId : 0001992f (MIPS 1004Kc) Call Trace: [<805e91f0>] __skb_flow_dissect+0x1b0/0x1b50 [<805ead08>] __skb_get_hash_net+0x74/0x12c [<805ef330>] get_rps_cpu+0x1b8/0x3fc [<805fca70>] netif_receive_skb_list_internal+0x324/0x364 [<805fd120>] napi_complete_done+0x68/0x2a4 [<8058de5c>] mtk_napi_rx+0x228/0xfec [<805fd398>] __napi_poll+0x3c/0x1c4 [<805fd754>] napi_threaded_poll_loop+0x234/0x29c [<805fd848>] napi_threaded_poll+0x8c/0xb0 [<80053544>] kthread+0x104/0x12c [<80002bd8>] ret_from_kernel_thread+0x14/0x1c

Code: 02d51821 1060045b 00000000 <8c640000> 3084000f 2c820005 144001a2 00042080 8e220000

To reduce the attack surface and maintain performance, do not process PPPoE PFC frames.

[1] https://lore.kernel.org/r/[email protected]

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%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
37%
KEV
Not listed

Published

June 8, 2026

Last Modified

September 8, 2026

Advisory Details (8)

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

flow_dissector: do not dissect PPPoE PFC frames - kernel/git/stable/linux.git - Linux kernel stable tree

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

flow_dissector: do not dissect PPPoE PFC frames - kernel/git/stable/linux.git - Linux kernel stable tree

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

flow_dissector: do not dissect PPPoE PFC frames - kernel/git/stable/linux.git - Linux kernel stable tree

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

flow_dissector: do not dissect PPPoE PFC frames - kernel/git/stable/linux.git - Linux kernel stable tree

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

flow_dissector: do not dissect PPPoE PFC frames - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7c93f353eab4ea911e394630f07d72e040a729d8
generic

flow_dissector: do not dissect PPPoE PFC frames - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6044392d9cace3a3672b02c8bc7d38b502e51734
generic

flow_dissector: do not dissect PPPoE PFC frames - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/18ae9eacfc95cc715c0606b2c86e8aa8a86cf3e3
generic

flow_dissector: do not dissect PPPoE PFC frames - kernel/git/stable/linux.git - Linux kernel stable tree

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

Patch Availability(23)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-6.8 (6.8.0-136.136) @ noble2026-09-08ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1009.9) @ resolute2026-09-08ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-09-08ubuntu
ubuntulinux-tools-oracle-edge (6.8.0-1058.61~22.04.1) @ jammy2026-09-08ubuntu
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-28.28~24.04.1) @ noble2026-09-08ubuntu
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-09-08ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1064.72+fips1) @ noble2026-09-08ubuntu
ubuntulinux-tools-oracle-lts-24.04 (6.8.0-1058.61) @ noble2026-09-08ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1059.62.1) @ noble2026-09-08ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-09-08ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2050.52) @ noble2026-09-08ubuntu
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-28.28) @ resolute2026-09-08ubuntu
ubuntulinux-tools-aws-lts-24.04 (6.8.0-1061.64+1) @ noble2026-09-08ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1063.71) @ noble2026-09-08ubuntu
ubuntulinux-tools-azure-fde-lts-24.04 (6.8.0-1062.69) @ noble2026-09-08ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1063.71+fips2) @ noble2026-09-08ubuntu
ubuntulinux-tools-azure-fde-6.8 (6.8.0-1062.69~22.04.1) @ jammy2026-09-08ubuntu
ubuntulinux-tools-aws-fips-6.8 (6.8.0-1061.64+fips1) @ noble2026-09-08ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1033.34) @ noble2026-09-08ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16~24.04.1) @ noble2026-09-08ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-136.136~22.04.1) @ jammy2026-09-08ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-09-08ubuntu
ubuntulinux-tools-gcp-edge (7.0.0-1011.11~24.04.1) @ noble2026-09-08ubuntu

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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
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.88-1~bpo12+1 (21 versions)6.12.88-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.7-1~bpo13+1 (136 versions)7.0.7-1

Additional Vendor Advisories

(23)

Data Freshness Timeline

(refreshed 12× in last 7d / 78× 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 320 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-46306?
CVE-2026-46306 is a high vulnerability published on June 8, 2026. In the Linux kernel, the following vulnerability has been resolved: flow_dissector: do not dissect PPPoE 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 flow…
When was CVE-2026-46306 disclosed?
CVE-2026-46306 was first published in the National Vulnerability Database on June 8, 2026, with the most recent update on September 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46306 actively exploited?
CVE-2026-46306 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 63.1% of all scored CVEs.
What is the CVSS score of CVE-2026-46306?
CVE-2026-46306 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-46306?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46306, 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-46306

Explore →

Is Your Infrastructure Affected by CVE-2026-46306?

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