Kernel panic via stale FCoE transport entry
Published Sep 18, 2025 · Updated Sep 18, 2025
Use-after-free in the Linux kernel FCoE driver allows local users to crash the kernel by reloading the FCoE module after initialization fails. If fcoe_if_init() fails, fcoe_init() frees fcoe_sw_transport without detaching it from the fcoe_transports list, leaving a stale entry. Triggering the panic requires an FCoE initialization failure followed by module reinsertion, and the reported consequence is host outage only.
Summary
What happened
Use-after-free in the Linux kernel FCoE driver allows local users to crash the kernel by reloading the FCoE module after initialization fails. If fcoe_if_init() fails, fcoe_init() frees fcoe_sw_transport without detaching it from the fcoe_transports list, leaving a stale entry. Triggering the panic requires an FCoE initialization failure followed by module reinsertion, and the reported consequence is host outage only.
The record
- CVE
- CVE-2022-50414
- Published
- Sep 18, 2025
- Updated
- Sep 18, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 18, 2025CVE publishedPublication date reported by the CVE source.
- Sep 18, 2025Record 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.39
- Affected versionversion=78a582463c1e3a262aeaf2a291e06a93a7b34212 <09a60f908d8b6497f618113b7c3c31267dc90911
- Affected versionversion=78a582463c1e3a262aeaf2a291e06a93a7b34212 <1dc499c615aa87dc46a3f2d1f91d2d358e55f3e3
- Affected versionversion=78a582463c1e3a262aeaf2a291e06a93a7b34212 <22e8c7a56bb1cd2ed0beaaccb34282ac9cbbe27e
- Affected versionversion=78a582463c1e3a262aeaf2a291e06a93a7b34212 <4155658cee394b22b24c6d64e49247bf26d95b92
- Affected versionversion=78a582463c1e3a262aeaf2a291e06a93a7b34212 <aef82d16be5a353d913163f26fc4385e296be2b8
- Affected versionversion=78a582463c1e3a262aeaf2a291e06a93a7b34212 <b5cc59470df64f26ad397dbb71cbf130cf489edf
- Affected versionversion=78a582463c1e3a262aeaf2a291e06a93a7b34212 <be5f1a82ad6056db22c86005dc4cac22a20deeef
- Affected versionversion=78a582463c1e3a262aeaf2a291e06a93a7b34212 <cf74d1197c0e3d2f353faa333e9e2847c73713f1
- Affected versionversion=78a582463c1e3a262aeaf2a291e06a93a7b34212 <d581303d6f8d4139513105d73dd65f26c6707160
What conditions does exploitation require?
What is affected?
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