Vulnerability · Published Sep 15, 2025 · Assigned by Linux

CVE-2023-53245scsi: storvsc: Fix handling of virtual Fibre Channel timeouts

Medium 5.5

In plain English

A medium-severity null pointer dereference in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.1% (higher than 4% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS 3.1)5.5Medium
Exploit odds (30 days)0.1%top 95.9% of all CVEs
Exploited in the wildNo reportsCISA SSVC: none
Attack toolingNoneno public tooling known

Official 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.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:12linux6.1.52-1DEBIAN-CVE-2023-53245
Debian:13linux6.4.11-1DEBIAN-CVE-2023-53245
Debian:14linux6.4.11-1DEBIAN-CVE-2023-53245
Ubuntu:22.04:LTSlinux5.15.0-91.101UBUNTU-CVE-2023-53245
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2023-53245
Ubuntu:22.04:LTSlinux-aws5.15.0-1051.56UBUNTU-CVE-2023-53245
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2023-53245
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2023-53245
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2023-53245
Ubuntu:22.04:LTSlinux-azure5.15.0-1053.61UBUNTU-CVE-2023-53245
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2023-53245
Ubuntu:24.04:LTSlinux-azure-6.11no fix listedUBUNTU-CVE-2023-53245
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2023-53245
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2023-53245
Ubuntu:22.04:LTSlinux-azure-fde5.15.0-1053.61.1UBUNTU-CVE-2023-53245
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2023-53245
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2023-53245
Ubuntu:22.04:LTSlinux-gcp5.15.0-1048.56UBUNTU-CVE-2023-53245
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2023-53245
Ubuntu:24.04:LTSlinux-gcp-6.11no fix listedUBUNTU-CVE-2023-53245
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2023-53245
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2023-53245
Ubuntu:22.04:LTSlinux-gke5.15.0-1048.53UBUNTU-CVE-2023-53245
Ubuntu:22.04:LTSlinux-gkeop5.15.0-1034.40UBUNTU-CVE-2023-53245
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2023-53245
Ubuntu:24.04:LTSlinux-hwe-6.11no fix listedUBUNTU-CVE-2023-53245
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2023-53245
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2023-53245
Ubuntu:22.04:LTSlinux-ibm5.15.0-1044.47UBUNTU-CVE-2023-53245
Ubuntu:24.04:LTSlinux-intelno fix listedUBUNTU-CVE-2023-53245
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2023-53245
Ubuntu:22.04:LTSlinux-intel-iotg5.15.0-1046.52UBUNTU-CVE-2023-53245
Ubuntu:22.04:LTSlinux-kvm5.15.0-1048.53UBUNTU-CVE-2023-53245
Ubuntu:22.04:LTSlinux-lowlatency5.15.0-91.101UBUNTU-CVE-2023-53245
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2023-53245
Ubuntu:24.04:LTSlinux-lowlatency-hwe-6.11no fix listedUBUNTU-CVE-2023-53245
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2023-53245
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2023-53245
Ubuntu:22.04:LTSlinux-nvidia5.15.0-1042.42UBUNTU-CVE-2023-53245
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2023-53245
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2023-53245
Ubuntu:22.04:LTSlinux-nvidia-tegra5.15.0-1020.20UBUNTU-CVE-2023-53245
Ubuntu:22.04:LTSlinux-nvidia-tegra-igx5.15.0-1007.7UBUNTU-CVE-2023-53245
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2023-53245
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2023-53245
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2023-53245
Ubuntu:24.04:LTSlinux-oem-6.11no fix listedUBUNTU-CVE-2023-53245
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2023-53245
Ubuntu:24.04:LTSlinux-oem-6.8no fix listedUBUNTU-CVE-2023-53245
Ubuntu:22.04:LTSlinux-oracle5.15.0-1049.55UBUNTU-CVE-2023-53245
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2023-53245
Ubuntu:22.04:LTSlinux-raspi5.15.0-1044.47UBUNTU-CVE-2023-53245
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2023-53245
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2023-53245
Ubuntu:24.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2023-53245
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2023-53245
Ubuntu:24.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2023-53245
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2023-53245
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2023-53245
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2023-53245
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2023-53245
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2023-53245
Ubuntu:22.04:LTSlinux-xilinx-zynqmp5.15.0-1027.31UBUNTU-CVE-2023-53245

Affected products (as reported)

VendorProductVersions
Linux Linux 3930d7309807ba0bfa460dfa9ed68d5560347dd2 – before cd87f4df9865a53807001ed12c0f0420b14ececd3930d7309807ba0bfa460dfa9ed68d5560347dd2 – before 311db605e07f0d4fc0cc7ddb74f1e5692ea2f4693930d7309807ba0bfa460dfa9ed68d5560347dd2 – before 048ebc9a28fb918ee635dd4b2fcf4248eb6e40503930d7309807ba0bfa460dfa9ed68d5560347dd2 – before 1678408d08f31a694d5150a56796dd04c9710b223930d7309807ba0bfa460dfa9ed68d5560347dd2 – before 7a792b3d888aab2c65389f9f4f9f2f6c000b1a0d3930d7309807ba0bfa460dfa9ed68d5560347dd2 – before ed70fa5629a8b992a5372d7044d1db1f8fa6de293930d7309807ba0bfa460dfa9ed68d5560347dd2 – before 763c06565055ae373fe7f89c11e1447bd1ded2643930d7309807ba0bfa460dfa9ed68d5560347dd2 – before 175544ad48cbf56affeef2a679c6a4d4fb1e2881
Linux Linux 4.13

Weakness: CWE-476 · Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

References