CVE-2026-46306

HIGHPre-NVD 7.57.5—
EchelonGraph scoreHIGH confidence

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

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

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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(high)
EPSS
30.9%
KEV
Not listed

Published

June 8, 2026

Last Modified

June 14, 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

Vendor Advisories for CVE-2026-46306(2)

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

Data Freshness Timeline

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

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

Related CVEs(same vendor)

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 June 14, 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 30.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-46306?
CVE-2026-46306 has a CVSS v4.0 base score of 7.5 (CNA self-assessment; NVD's own analysis pending).
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

Explore the affected products and dependency analysis for 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.

Start Free Scan →Browse All CVEs