CVE-2026-63890

UNRATEDCVSS · not yet scoredTrending — 3 sources updated this week
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS v2: Exploit: None knownExposed: 0

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

scsi: fcoe: Reject FIP descriptors with zero fip_dlen in CVL walker

drivers/scsi/fcoe/fcoe_ctlr.c::fcoe_ctlr_recv_clr_vlink() advanced the descriptor cursor by an attacker-supplied fip_dlen without ever requiring dlen >= sizeof(struct fip_desc) in the default branch. The named descriptor cases (FIP_DT_MAC, FIP_DT_NAME, FIP_DT_VN_ID) checked their per-type minimum lengths, but a FIP_DT_NON_CRITICAL descriptor (fip_dtype >= 128, which the standard requires receivers to silently ignore) skipped that check entirely.

An unauthenticated L2 peer on the FCoE control VLAN could hang fcoe_ctlr_recv_work on an fcoe, qedf, or bnx2fc initiator indefinitely by emitting one FIP CVL frame whose single descriptor had fip_dtype == FIP_DT_NON_CRITICAL and fip_dlen == 0: the cursor advanced zero bytes per iteration and the loop condition rlen >= sizeof(*desc) stayed true forever, blocking every subsequent FIP frame on that controller.

Tighten the outer dlen guard to also reject dlen < sizeof(struct fip_desc), so a malformed descriptor whose length cannot even cover the descriptor header is rejected before the switch. This is the same lower-bound the named cases already apply and is the minimum scope that closes the loop.

CVSS v3
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
EG Risk
EPSS PROB
0%
EPSS %ILE
12%
KEV
Not listed

Published

July 19, 2026

Last Modified

July 27, 2026

Vendor Advisories for CVE-2026-63890(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(5)

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (54 versions)5.10.259-1
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)6.1.176-1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)6.12.94-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (138 versions)7.0.12-1

All Vendor Advisories

(5)

Data Freshness Timeline

(refreshed 9× in last 7d / 45× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-30 01:22 UTCEPSS rescore
  2. 2026-08-28 21:42 UTCEPSS rescore
  3. 2026-08-27 23:21 UTCVendor advisory
  4. 2026-08-27 23:21 UTCGHSA enrichment
  5. 2026-08-27 14:25 UTCEPSS rescore
  6. 2026-08-26 14:46 UTCEPSS rescore
  7. 2026-08-25 13:49 UTCEPSS rescore
  8. 2026-08-25 03:13 UTCVendor advisory
  9. 2026-08-25 03:12 UTCGHSA enrichment
  10. 2026-08-23 00:19 UTCEPSS rescore
  11. 2026-08-22 07:05 UTCVendor advisory
  12. 2026-08-22 07:05 UTCGHSA enrichment
  13. 2026-08-21 23:49 UTCEPSS rescore
  14. 2026-08-20 22:55 UTCEPSS rescore
  15. 2026-08-19 17:04 UTCEPSS rescore
  16. 2026-08-19 10:54 UTCVendor advisory
  17. 2026-08-19 10:54 UTCGHSA enrichment
  18. 2026-08-18 13:48 UTCEPSS rescore
  19. 2026-08-17 13:47 UTCEPSS rescore
  20. 2026-08-16 14:56 UTCEPSS rescore
  21. 2026-08-16 14:45 UTCVendor advisory
  22. 2026-08-16 14:45 UTCGHSA enrichment
  23. 2026-08-15 01:30 UTCEPSS rescore
  24. 2026-08-13 22:00 UTCEPSS rescore
  25. 2026-08-13 18:37 UTCVendor advisory
Show 51 more
  1. 2026-08-13 18:37 UTCGHSA enrichment
  2. 2026-08-12 13:51 UTCEPSS rescore
  3. 2026-08-11 00:00 UTCEPSS rescore
  4. 2026-08-10 22:30 UTCVendor advisory
  5. 2026-08-10 22:30 UTCGHSA enrichment
  6. 2026-08-09 13:47 UTCEPSS rescore
  7. 2026-08-08 16:37 UTCEPSS rescore
  8. 2026-08-08 02:22 UTCVendor advisory
  9. 2026-08-08 02:22 UTCGHSA enrichment
  10. 2026-08-06 13:47 UTCEPSS rescore
  11. 2026-08-05 19:17 UTCEPSS rescore
  12. 2026-08-05 19:17 UTCEPSS rescore
  13. 2026-08-05 06:15 UTCGHSA enrichment
  14. 2026-08-04 15:10 UTCEPSS rescore
  15. 2026-08-04 10:39 UTCEPSS rescore
  16. 2026-08-03 10:36 UTCEPSS rescore
  17. 2026-08-02 10:07 UTCVendor advisory
  18. 2026-08-02 10:07 UTCGHSA enrichment
  19. 2026-08-02 02:27 UTCEPSS rescore
  20. 2026-08-01 04:16 UTCEPSS rescore
  21. 2026-07-30 16:28 UTCEPSS rescore
  22. 2026-07-30 13:59 UTCEG score recompute
  23. 2026-07-30 13:59 UTCVendor advisory
  24. 2026-07-30 13:59 UTCGHSA enrichment
  25. 2026-07-30 01:30 UTCEPSS rescore
  26. 2026-07-30 01:30 UTCEPSS rescore
  27. 2026-07-28 15:37 UTCEPSS rescore
  28. 2026-07-27 17:51 UTCGHSA enrichment
  29. 2026-07-27 14:14 UTCEPSS rescore
  30. 2026-07-26 14:54 UTCEPSS rescore
  31. 2026-07-26 14:54 UTCEPSS rescore
  32. 2026-07-26 11:01 UTCEG score recompute
  33. 2026-07-26 11:01 UTCVendor advisory
  34. 2026-07-26 11:01 UTCGHSA enrichment
  35. 2026-07-25 14:18 UTCEPSS rescore
  36. 2026-07-25 14:18 UTCEPSS rescore
  37. 2026-07-24 14:18 UTCEPSS rescore
  38. 2026-07-24 14:18 UTCEPSS rescore
  39. 2026-07-23 14:18 UTCEPSS rescore
  40. 2026-07-23 14:18 UTCEPSS rescore
  41. 2026-07-23 03:22 UTCEG score recompute
  42. 2026-07-22 14:08 UTCEPSS rescore
  43. 2026-07-22 14:08 UTCEPSS rescore
  44. 2026-07-21 15:25 UTCEPSS rescore
  45. 2026-07-21 15:25 UTCEPSS rescore
  46. 2026-07-20 17:38 UTCEG score recompute
  47. 2026-07-20 17:38 UTCGHSA enrichment
  48. 2026-07-20 17:08 UTCEPSS rescore
  49. 2026-07-19 17:49 UTCNVD update
  50. 2026-07-19 15:24 UTCEG score recompute
  51. 2026-07-19 15:19 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-63890?
CVE-2026-63890 is a publicly disclosed vulnerability published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: scsi: fcoe: Reject FIP descriptors with zero fip_dlen in CVL walker drivers/scsi/fcoe/fcoectlr.c::fcoectlrrecvclr_vlink() advanced the descriptor cursor by an attacker-supplied fip_dlen without ever requiring dlen >= sizeof(struct…
When was CVE-2026-63890 disclosed?
CVE-2026-63890 was first published in the National Vulnerability Database on July 19, 2026, with the most recent update on July 27, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-63890 actively exploited?
CVE-2026-63890 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 87.7% of all scored CVEs.
How do I remediate CVE-2026-63890?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-63890, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-63890

Explore →

Is Your Infrastructure Affected by CVE-2026-63890?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.