CVE-2023-53245scsi: storvsc: Fix handling of virtual Fibre Channel timeouts
- 5.5MediumCVSS base score
- 0.15%Exploitation in 30 daysEPSS · top 95% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: scsi: storvsc: Fix handling of virtual Fibre Channel timeouts Hyper-V provides the ability to connect Fibre Channel LUNs to the host system and present them in a guest VM as a SCSI device. I/O to the vFC device is handled by the storvsc driver. The storvsc driver includes a partial integration with the FC transport implemented in the generic portion of the Linux SCSI subsystem so that FC attributes can be displayed in /sys. However, the partial integration means that some aspects of vFC don't work properly. Unfortunately, a full and correct integration isn't practical because of limitations in what Hyper-V provides to the guest. In particular, in the context of Hyper-V storvsc, the FC transport timeout function fc_eh_timed_out() causes a kernel panic because it can't find the rport and dereferences a NULL pointer. The original patch that added the call from storvsc_eh_timed_out() to fc_eh_timed_out() is faulty in this regard. In many cases a timeout is due to a transient condition, so the situation can be improved by just continuing to wait like with other I/O requests issued by storvsc, and avoiding the guaranteed panic. For a permanent failure, continuing to wait may result in a hung thread instead of a panic, which again may be better. So fix the panic by removing the storvsc call to fc_eh_timed_out(). This allows storvsc to keep waiting for a response. The change has been tested by users who experienced a panic in fc_eh_timed_out() due to transient timeouts, and it solves their problem. In the future we may want to deprecate the vFC functionality in storvsc since it can't be fully fixed. But it has current users for whom it is working well enough, so it should probably stay for a while longer.
Timeline
ID reserved
By Linux
Published
- 8 months later
· 8 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| CISA-ADPADP (enrichment) | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
| NVDNVD · Modified | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.15% · top 95% of all CVEs (18 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Affected products
- affected 3930d7309807ba0bfa460dfa9ed68d5560347dd2 – < cd87f4df9865a53807001ed12c0f0420b14ececd
- affected 3930d7309807ba0bfa460dfa9ed68d5560347dd2 – < 311db605e07f0d4fc0cc7ddb74f1e5692ea2f469
- affected 3930d7309807ba0bfa460dfa9ed68d5560347dd2 – < 048ebc9a28fb918ee635dd4b2fcf4248eb6e4050
- affected 3930d7309807ba0bfa460dfa9ed68d5560347dd2 – < 1678408d08f31a694d5150a56796dd04c9710b22
- affected 3930d7309807ba0bfa460dfa9ed68d5560347dd2 – < 7a792b3d888aab2c65389f9f4f9f2f6c000b1a0d
- affected 3930d7309807ba0bfa460dfa9ed68d5560347dd2 – < ed70fa5629a8b992a5372d7044d1db1f8fa6de29
- affected 3930d7309807ba0bfa460dfa9ed68d5560347dd2 – < 763c06565055ae373fe7f89c11e1447bd1ded264
- affected 3930d7309807ba0bfa460dfa9ed68d5560347dd2 – < 175544ad48cbf56affeef2a679c6a4d4fb1e2881
- affected 4.13
- unaffected < 4.13
- unaffected 4.14.323 – ≤ 4.14.*
- unaffected 4.19.292 – ≤ 4.19.*
- unaffected 5.4.254 – ≤ 5.4.*
- unaffected 5.10.191 – ≤ 5.10.*
- unaffected 5.15.127 – ≤ 5.15.*
- unaffected 6.1.46 – ≤ 6.1.*
- unaffected 6.4.11 – ≤ 6.4.*
- unaffected 6.5 – ≤ *
References
References8
- https://git.kernel.org/stable/c/cd87f4df9865a53807001ed12c0f0420b14ececd (opens in a new tab)
- https://git.kernel.org/stable/c/311db605e07f0d4fc0cc7ddb74f1e5692ea2f469 (opens in a new tab)
- https://git.kernel.org/stable/c/048ebc9a28fb918ee635dd4b2fcf4248eb6e4050 (opens in a new tab)
- https://git.kernel.org/stable/c/1678408d08f31a694d5150a56796dd04c9710b22 (opens in a new tab)
- https://git.kernel.org/stable/c/7a792b3d888aab2c65389f9f4f9f2f6c000b1a0d (opens in a new tab)
- https://git.kernel.org/stable/c/ed70fa5629a8b992a5372d7044d1db1f8fa6de29 (opens in a new tab)
- https://git.kernel.org/stable/c/763c06565055ae373fe7f89c11e1447bd1ded264 (opens in a new tab)
- https://git.kernel.org/stable/c/175544ad48cbf56affeef2a679c6a4d4fb1e2881 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2023-59839 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2023-53245)Record last updated .