Linux Kernel up to 7.0.6 flow_dissector infinite loop

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
4.6$0-$5k0.00

Summaryinfo

A vulnerability classified as critical has been found in Linux Kernel up to 6.1.174/6.6.139/6.12.87/6.18.29/7.0.6. This impacts an unknown function of the component flow_dissector. This manipulation causes infinite loop. This vulnerability is registered as CVE-2026-46306. No exploit is available. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability classified as critical was found in Linux Kernel up to 6.1.174/6.6.139/6.12.87/6.18.29/7.0.6. Affected by this vulnerability is some unknown processing of the component flow_dissector. The manipulation with an unknown input leads to a infinite loop vulnerability. The CWE definition for the vulnerability is CWE-835. The product contains an iteration or loop with an exit condition that cannot be reached, i.e., an infinite loop. As an impact it is known to affect availability. The summary by CVE is:

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: [] __skb_flow_dissect+0x1b0/0x1b50 [] __skb_get_hash_net+0x74/0x12c [] get_rps_cpu+0x1b8/0x3fc [] netif_receive_skb_list_internal+0x324/0x364 [] napi_complete_done+0x68/0x2a4 [] mtk_napi_rx+0x228/0xfec [] __napi_poll+0x3c/0x1c4 [] napi_threaded_poll_loop+0x234/0x29c [] napi_threaded_poll+0x8c/0xb0 [] kthread+0x104/0x12c [] ret_from_kernel_thread+0x14/0x1c Code: 02d51821 1060045b 00000000 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]

It is possible to read the advisory at git.kernel.org. This vulnerability is known as CVE-2026-46306 since 05/13/2026. The exploitation appears to be difficult. The technical details are unknown and an exploit is not publicly available.

Upgrading to version 6.1.175, 6.6.140, 6.12.88, 6.18.30, 7.0.7 or 7.1-rc1 eliminates this vulnerability. Applying the patch e7c811ca372d53c2be7d01a1614e71fae1054836/abc5bc84e0f2edc7ea2d437afa6ef3fe1fc43200/18ae9eacfc95cc715c0606b2c86e8aa8a86cf3e3/db104b0d8a7856397c0469d83a4289adf7c54863/6044392d9cace3a3672b02c8bc7d38b502e51734/0d00b9015069712944934bab09eaa6c542143049/7c93f353eab4ea911e394630f07d72e040a729d8/d6c19b31a3c1d519fabdcf0aa239e6b6109b9473 is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 4.8
VulDB Meta Temp Score: 4.6

VulDB Base Score: 4.8
VulDB Temp Score: 4.6
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Infinite loop
CWE: CWE-835 / CWE-404
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
Remote: Partially

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 6.1.175/6.6.140/6.12.88/6.18.30/7.0.7/7.1-rc1
Patch: e7c811ca372d53c2be7d01a1614e71fae1054836/abc5bc84e0f2edc7ea2d437afa6ef3fe1fc43200/18ae9eacfc95cc715c0606b2c86e8aa8a86cf3e3/db104b0d8a7856397c0469d83a4289adf7c54863/6044392d9cace3a3672b02c8bc7d38b502e51734/0d00b9015069712944934bab09eaa6c542143049/7c93f353eab4ea911e394630f07d72e040a729d8/d6c19b31a3c1d519fabdcf0aa239e6b6109b9473

Timelineinfo

05/13/2026 CVE reserved
06/08/2026 +26 days Advisory disclosed
06/08/2026 +0 days VulDB entry created
06/08/2026 +0 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-46306 (🔒)
GCVE (CVE): GCVE-0-2026-46306
GCVE (VulDB): GCVE-100-369235

Entryinfo

Created: 06/08/2026 20:11
Changes: 06/08/2026 20:11 (58)
Complete: 🔍
Cache ID: 216::103

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Do you want to use VulDB in your project?

Use the official API to access entries easily!