SECUFOCUSNOW
Home›CVE index›CVE-2026-46306
Review reviewHigh

CVE-2026-46306

Linux Linux, linux kernel

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 netwo...

CVSS
7.5
EPSS
0.39%
31.7% percentile
CISA KEV
Not listed
Published
2026.06.09
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.39%
Technical severityCVSS 7.5

Vulnerability overview

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 netwo...

Affected product and versions

Product
Linux Linux, linux kernel
Affected versions
>= 10f665b52a75df6eb26ddebbbc072ee264183731 < e7c811ca372d53c2be7d01a1614e71fae1054836, >= d7e541e86122d21f71eb71c5dfa7fb1eb6623fe8 < abc5bc84e0f2edc7ea2d437afa6ef3fe1fc43200, >= 46126db9c86110e5fc1e369b9bb89735ddefdae4 < 18ae9eacfc95cc715c0606b2c86e8aa8a86cf3e3, >= 46126db9c86110e5fc1e369b9bb89735ddefdae4 < db104b0d8a7856397c0469d83a4289adf7c54863, >= 46126db9c86110e5fc1e369b9bb89735ddefdae4 < 6044392d9cace3a3672b02c8bc7d38b502e51734, >= 46126db9c86110e5fc1e369b9bb89735ddefdae4 < 0d00b9015069712944934bab09eaa6c542143049, >= 46126db9c86110e5fc1e369b9bb89735ddefdae4 < 7c93f353eab4ea911e394630f07d72e040a729d8, >= 46126db9c86110e5fc1e369b9bb89735ddefdae4 < d6c19b31a3c1d519fabdcf0aa239e6b6109b9473, >= 6.0, >= 6.0 < 6.1.175, >= 6.2 < 6.6.140, >= 6.7 < 6.12.88, >= 6.13 < 6.18.30, >= 6.19 < 7.0.7
Fixed versions
6.1.175, 6.6.140, 6.12.88, 6.18.30, 7.0.7

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux Linux, linux kernel and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
CWE
Not available