FCoE controller hang via zero-length descriptor
Published Jul 19, 2026 · Updated Jul 19, 2026
Improper input validation in Linux Kernel allows remote attackers to hang FCoE controller processing via a malformed FIP CVL frame. In fcoe_ctlr_recv_clr_vlink(), the default descriptor case advances its cursor by untrusted fip_dlen without rejecting a value smaller than the descriptor header, so a zero length leaves the loop position unchanged. Access requires an unauthenticated Layer 2 peer on the FCoE control VLAN; one frame can indefinitely block later FIP frames on the affected controller.
Summary
What happened
Improper input validation in Linux Kernel allows remote attackers to hang FCoE controller processing via a malformed FIP CVL frame. In fcoe_ctlr_recv_clr_vlink(), the default descriptor case advances its cursor by untrusted fip_dlen without rejecting a value smaller than the descriptor header, so a zero length leaves the loop position unchanged. Access requires an unauthenticated Layer 2 peer on the FCoE control VLAN; one frame can indefinitely block later FIP frames on the affected controller.
The record
- CVE
- CVE-2026-63890
- Published
- Jul 19, 2026
- Updated
- Jul 19, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- T1499
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 19, 2026CVE publishedPublication date reported by the CVE source.
- Jul 19, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.6.30
- Affected versionversion=97c8389d54b9665c38105ea72a428a44b97ff2f6 <0e3c6e5a8fc15a74dfb1e0c1df9f1da73600a81a
- Affected versionversion=97c8389d54b9665c38105ea72a428a44b97ff2f6 <14dd80a20a72ce334adcc2d67402360527065948
- Affected versionversion=97c8389d54b9665c38105ea72a428a44b97ff2f6 <549859a1131052b07dff11a448e9f3221a40f260
- Affected versionversion=97c8389d54b9665c38105ea72a428a44b97ff2f6 <80a0cd307205236ca28aa49bc553f58edcb9bf3a
- Affected versionversion=97c8389d54b9665c38105ea72a428a44b97ff2f6 <9eed1bd59937e6828b00d2f2dfef631d964f3636
- Affected versionversion=97c8389d54b9665c38105ea72a428a44b97ff2f6 <d179949d2175d2857d1c3a275a22bea58bcc5d36
- Affected versionversion=97c8389d54b9665c38105ea72a428a44b97ff2f6 <d537d29d51c8b808469e5adacf3e5a0092700738
- Affected versionversion=97c8389d54b9665c38105ea72a428a44b97ff2f6 <fda976f7390bb5d1e9b84ef11ebb17323038e0c6
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo