scsi: storvsc: Fix handling of virtual Fibre Channel timeouts
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
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 4.14.323, 4.19.292, 5.10.191, 5.15.127, 5.4.254, 6.1.46, 6.4.11
- CVEs
- CVE-2023-53245
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 7 Nov 2026, 03:22 UTC · Revision 1
Source evidence
scsi: storvsc: Fix handling of virtual Fibre Channel timeouts
core-osv · Original sourcePublished 15 Sept 2025, 14:46 UTC
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
osv:CVE-2023-53245
Kernel
Fixed versions: 4.14.323, 4.19.292, 5.4.254, 5.10.191, 5.15.127, 6.1.46, 6.4.11
Complete source record
{
"id": "9afd89c0383c0c4b71f1d8641125a1256ce9f42b1941f2399c2ab1b192b5b7ac",
"url": "https://osv.dev/vulnerability/CVE-2023-53245",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "scsi: storvsc: Fix handling of virtual Fibre Channel timeouts",
"summary": "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",
"evidence": "osv:CVE-2023-53245",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "4.14.323",
"evidence": "/affected/1/ranges"
},
{
"value": "4.19.292",
"evidence": "/affected/1/ranges"
},
{
"value": "5.4.254",
"evidence": "/affected/1/ranges"
},
{
"value": "5.10.191",
"evidence": "/affected/1/ranges"
},
{
"value": "5.15.127",
"evidence": "/affected/1/ranges"
},
{
"value": "6.1.46",
"evidence": "/affected/1/ranges"
},
{
"value": "6.4.11",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "medium",
"structured": {
"id": "CVE-2023-53245",
"aliases": [
"CVE-2023-53245"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "3930d7309807ba0bfa460dfa9ed68d5560347dd2"
},
{
"fixed": "cd87f4df9865a53807001ed12c0f0420b14ececd"
},
{
"fixed": "311db605e07f0d4fc0cc7ddb74f1e5692ea2f469"
},
{
"fixed": "048ebc9a28fb918ee635dd4b2fcf4248eb6e4050"
},
{
"fixed": "1678408d08f31a694d5150a56796dd04c9710b22"
},
{
"fixed": "7a792b3d888aab2c65389f9f4f9f2f6c000b1a0d"
},
{
"fixed": "ed70fa5629a8b992a5372d7044d1db1f8fa6de29"
},
{
"fixed": "763c06565055ae373fe7f89c11e1447bd1ded264"
},
{
"fixed": "175544ad48cbf56affeef2a679c6a4d4fb1e2881"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2023-53245.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "4.13.0"
},
{
"fixed": "4.14.323"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "4.15.0"
},
{
"fixed": "4.19.292"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "4.20.0"
},
{
"fixed": "5.4.254"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.5.0"
},
{
"fixed": "5.10.191"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.11.0"
},
{
"fixed": "5.15.127"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.16.0"
},
{
"fixed": "6.1.46"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.2.0"
},
{
"fixed": "6.4.11"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2023-53245.json"
}
}
],
"modified": "2026-10-28T02:30:49.652711483Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/048ebc9a28fb918ee635dd4b2fcf4248eb6e4050",
"https://git.kernel.org/stable/c/1678408d08f31a694d5150a56796dd04c9710b22",
"https://git.kernel.org/stable/c/175544ad48cbf56affeef2a679c6a4d4fb1e2881",
"https://git.kernel.org/stable/c/311db605e07f0d4fc0cc7ddb74f1e5692ea2f469",
"https://git.kernel.org/stable/c/763c06565055ae373fe7f89c11e1447bd1ded264",
"https://git.kernel.org/stable/c/7a792b3d888aab2c65389f9f4f9f2f6c000b1a0d",
"https://git.kernel.org/stable/c/cd87f4df9865a53807001ed12c0f0420b14ececd",
"https://git.kernel.org/stable/c/ed70fa5629a8b992a5372d7044d1db1f8fa6de29",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2023/53xxx/CVE-2023-53245.json",
"https://nvd.nist.gov/vuln/detail/CVE-2023-53245",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2023/53xxx/CVE-2023-53245.json"
}
},
"related_cves": [
{
"value": "CVE-2023-53245",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 517717,
"published_at": "2025-09-15T14:46:14.28+00:00"
}