In the Linux kernel, the following vulnerability has been resolved: scsi: scsi_transport_fc: Widen FPIN pname walker counter to u32 An adjacent… (CVE-2026-63889)
In the Linux kernel, the following vulnerability has been resolved: scsi: scsi_transport_fc: Widen FPIN pname walker counter to u32 An adjacent Fibre Channel fabric actor that can deliver an FPIN ELS frame to an lpfc or qla2xxx Linux initiator can trigger a non-return in the generic FC transport. This is not a local userspace or IP network path; the attacker must be able to inject fabric traffic, for example as a compromised switch or fabric controller, or as a same-zone N_Port on a fabric that permits source spoofing. The Link-Integrity and Peer-Congestion FPIN walkers used a u8 loop counter against the 32-bit on-wire pname_count field, and did not bound pname_count by the descriptor body already validated by the TLV walker. A pname_count of 256 therefore wraps the counter and keeps the loop condition true indefinitely. Factor the shared pname_list[] walk into one helper, widen the counter to u32, and clamp pname_count against the entries that fit in the descriptor body before iterating.
AI Analysis
Technical Summary
The Linux kernel contained a vulnerability in the scsi_transport_fc component where the FPIN pname walker used a u8 loop counter against a 32-bit pname_count field without proper bounds checking. This allowed an attacker controlling adjacent Fibre Channel fabric traffic to trigger an infinite loop (non-return) in the generic FC transport by delivering an FPIN ELS frame with a crafted pname_count of 256, causing the counter to wrap and the loop condition to remain true indefinitely. The fix involved consolidating the pname_list walk into a single helper, widening the loop counter to u32, and clamping pname_count to the validated descriptor body size before iteration.
Potential Impact
An attacker capable of injecting Fibre Channel fabric traffic could cause a denial of service by triggering an infinite loop in the Linux kernel's FC transport layer, potentially impacting system stability. This is not exploitable via local userspace or IP network paths and requires privileged network conditions such as compromised fabric components or source spoofing within the same fabric zone.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to address this vulnerability by widening the FPIN pname walker counter and adding proper bounds checking. Users should update to the fixed Linux kernel version once available. Since this is not a cloud service, remediation depends on applying the official kernel patch. Patch status is not yet confirmed in this data; check the vendor advisory for current remediation guidance.
In the Linux kernel, the following vulnerability has been resolved: scsi: scsi_transport_fc: Widen FPIN pname walker counter to u32 An adjacent… (CVE-2026-63889)
Description
In the Linux kernel, the following vulnerability has been resolved: scsi: scsi_transport_fc: Widen FPIN pname walker counter to u32 An adjacent Fibre Channel fabric actor that can deliver an FPIN ELS frame to an lpfc or qla2xxx Linux initiator can trigger a non-return in the generic FC transport. This is not a local userspace or IP network path; the attacker must be able to inject fabric traffic, for example as a compromised switch or fabric controller, or as a same-zone N_Port on a fabric that permits source spoofing. The Link-Integrity and Peer-Congestion FPIN walkers used a u8 loop counter against the 32-bit on-wire pname_count field, and did not bound pname_count by the descriptor body already validated by the TLV walker. A pname_count of 256 therefore wraps the counter and keeps the loop condition true indefinitely. Factor the shared pname_list[] walk into one helper, widen the counter to u32, and clamp pname_count against the entries that fit in the descriptor body before iterating.
CVSS v3.1
Score 8.1high
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel contained a vulnerability in the scsi_transport_fc component where the FPIN pname walker used a u8 loop counter against a 32-bit pname_count field without proper bounds checking. This allowed an attacker controlling adjacent Fibre Channel fabric traffic to trigger an infinite loop (non-return) in the generic FC transport by delivering an FPIN ELS frame with a crafted pname_count of 256, causing the counter to wrap and the loop condition to remain true indefinitely. The fix involved consolidating the pname_list walk into a single helper, widening the loop counter to u32, and clamping pname_count to the validated descriptor body size before iteration.
Potential Impact
An attacker capable of injecting Fibre Channel fabric traffic could cause a denial of service by triggering an infinite loop in the Linux kernel's FC transport layer, potentially impacting system stability. This is not exploitable via local userspace or IP network paths and requires privileged network conditions such as compromised fabric components or source spoofing within the same fabric zone.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to address this vulnerability by widening the FPIN pname walker counter and adding proper bounds checking. Users should update to the fixed Linux kernel version once available. Since this is not a cloud service, remediation depends on applying the official kernel patch. Patch status is not yet confirmed in this data; check the vendor advisory for current remediation guidance.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-w68f-2wrj-q4g6
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-63889"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- 3.1
Threat ID: 6a5d27ab2a4a8d598912fc6d
Added to database: 07/19/2026, 19:38:19 UTC
Last enriched: 07/19/2026, 20:11:30 UTC
Last updated: 09/03/2026, 22:52:13 UTC
Views: 52
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.