🛡️ CVE-2023-53245 on Ubuntu — linux
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.
Distribution advisory
This page covers CVE-2023-53245 as tracked by Ubuntu, for the package linux. The fix is available in version 5.15.0-91.101; earlier versions remain affected.
How this vulnerability can be exploited
This issue can be reached with local access to the system, attack complexity is low, an attacker needs low-level privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality none, integrity none, availability high.
CVSS metrics in full
The score comes from this vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
- Attack vector: Local — a local account, shell or session on the host is needed.
- Attack complexity: Low — the attack works reliably, with no preparation.
- Privileges required: Low — an ordinary user account is enough.
- User interaction: None — nobody has to be tricked into anything.
- Scope: Unchanged — the damage stays inside the vulnerable component.
- Confidentiality impact: None.
- Integrity impact: None.
- Availability impact: High — total loss, or loss the attacker controls.
Affected software
UBUNTU-CVE-2023-53245 is recorded against 122 packages.
- linux (fixed in 5.15.0-91.101)
- linux-allwinner-5.19
- linux-aws (fixed in 5.15.0-1051.56)
- linux-aws-5.0
- linux-aws-5.11
- linux-aws-5.13
- linux-aws-5.15 (fixed in 5.15.0-1051.56~20.04.1)
- linux-aws-5.19
- linux-aws-5.3
- linux-aws-5.4 (fixed in 5.4.0-1116.126~18.04.1)
- linux-aws-5.8
- linux-aws-6.2
- linux-aws-6.5
- linux-aws-fips
- linux-aws-hwe
- linux-azure (fixed in 5.15.0-1053.61)
- linux-azure-4.15
- linux-azure-5.11
- linux-azure-5.13
- linux-azure-5.15 (fixed in 5.15.0-1053.61~20.04.1)
- linux-azure-5.19
- linux-azure-5.3
- linux-azure-5.4 (fixed in 5.4.0-1121.128~18.04.1)
- linux-azure-5.8
Show the remaining 98 packages
- linux-azure-6.11
- linux-azure-6.2
- linux-azure-6.5
- linux-azure-edge
- linux-azure-fde
- linux-azure-fde-5.19
- linux-azure-fde-6.2
- linux-azure-fips
- linux-bluefield
- linux-fips
- linux-gcp (fixed in 5.15.0-1048.56)
- linux-gcp-4.15
- linux-gcp-5.11
- linux-gcp-5.13
- linux-gcp-5.15 (fixed in 5.15.0-1048.56~20.04.1)
- linux-gcp-5.19
- linux-gcp-5.3
- linux-gcp-5.4 (fixed in 5.4.0-1120.129~18.04.1)
- linux-gcp-5.8
- linux-gcp-6.11
- linux-gcp-6.2
- linux-gcp-6.5
- linux-gcp-fips
- linux-gke (fixed in 5.15.0-1048.53)
- linux-gke-4.15
- linux-gke-5.15
- linux-gke-5.4
- linux-gkeop (fixed in 5.15.0-1034.40)
- linux-gkeop-5.15
- linux-gkeop-5.4
- linux-hwe
- linux-hwe-5.11
- linux-hwe-5.13
- linux-hwe-5.15 (fixed in 5.15.0-91.101~20.04.1)
- linux-hwe-5.19
- linux-hwe-5.4 (fixed in 5.4.0-169.187~18.04.1)
- linux-hwe-5.8
- linux-hwe-6.11
- linux-hwe-6.2
- linux-hwe-6.5
- linux-hwe-edge
- linux-ibm (fixed in 5.15.0-1044.47)
- linux-ibm-5.15 (fixed in 5.15.0-1044.47~20.04.1)
- linux-ibm-5.4 (fixed in 5.4.0-1063.68~18.04.1)
- linux-intel
- linux-intel-5.13
- linux-intel-iot-realtime (fixed in 5.15.0-1044.46)
- linux-intel-iotg (fixed in 5.15.0-1046.52)
- linux-intel-iotg-5.15 (fixed in 5.15.0-1046.52~20.04.1)
- linux-iot (fixed in 5.4.0-1028.29)
- linux-kvm (fixed in 5.15.0-1048.53)
- linux-lowlatency (fixed in 5.15.0-91.101)
- linux-lowlatency-hwe-5.15 (fixed in 5.15.0-91.101~20.04.1)
- linux-lowlatency-hwe-5.19
- linux-lowlatency-hwe-6.11
- linux-lowlatency-hwe-6.2
- linux-lowlatency-hwe-6.5
- linux-nvidia (fixed in 5.15.0-1042.42)
- linux-nvidia-6.2
- linux-nvidia-6.5
- linux-nvidia-tegra (fixed in 5.15.0-1020.20)
- linux-nvidia-tegra-5.15 (fixed in 5.15.0-1020.20~20.04.1)
- linux-nvidia-tegra-igx (fixed in 5.15.0-1007.7)
- linux-oem
- linux-oem-5.10
- linux-oem-5.13
- linux-oem-5.14
- linux-oem-5.17
- linux-oem-5.6
- linux-oem-6.0
- linux-oem-6.1
- linux-oem-6.11
- linux-oem-6.5
- linux-oem-6.8
- linux-oracle (fixed in 5.15.0-1049.55)
- linux-oracle-5.0
- linux-oracle-5.11
- linux-oracle-5.13
- linux-oracle-5.15 (fixed in 5.15.0-1049.55~20.04.1)
- linux-oracle-5.3
- linux-oracle-5.4 (fixed in 5.4.0-1115.124~18.04.1)
- linux-oracle-5.8
- linux-oracle-6.5
- linux-raspi (fixed in 5.15.0-1044.47)
- linux-raspi-5.4 (fixed in 5.4.0-1100.112~18.04.1)
- linux-raspi-realtime
- linux-raspi2
- linux-realtime
- linux-riscv
- linux-riscv-5.11
- linux-riscv-5.15 (fixed in 5.15.0-1047.51~20.04.1)
- linux-riscv-5.19
- linux-riscv-5.8
- linux-riscv-6.5
- linux-starfive-5.19
- linux-starfive-6.2
- linux-starfive-6.5
- linux-xilinx-zynqmp (fixed in 5.15.0-1027.31)
Timeline and source
Published on 15 September 2025 and last revised on 19 August 2026. No public exploit is currently recorded for this entry. Record sourced from OSV.
References
ubuntu.com (Report)
www.cve.org (Report)
git.kernel.org (Report)
git.kernel.org (Report)
git.kernel.org (Report)
git.kernel.org (Report)
git.kernel.org (Report)
git.kernel.org (Report)
git.kernel.org (Report)
git.kernel.org (Report)
git.kernel.org (Report)
Other advisories for this package
linux has other advisories on record. If you are patching this one, these are worth checking on the same host:
- DEBIAN-CVE-2022-4994 (published 30 Jul 2026)
- CVE-2026-35233 (4.4 Medium, published 1 May 2026)
- CVE-2026-21996 (3.3 Low, published 1 May 2026)
- CVE-2026-21991 (5.5 Medium, published 16 Mar 2026)
- CGA-mcwh-q4vm-9f29 (published 29 Jan 2026)
- CGA-w6xv-3fg4-grm5 (published 29 Jan 2026)
- CGA-7wmc-rrpx-535w (published 7 Jan 2026)
- CGA-5g29-pc3v-86pw (published 7 Jan 2026)
CVE-2023-53245 on other distributions
Each distribution ships its own build and its own fixed version. Pick the one you run:
Details
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Affected Packages
| Software | From version | Fixed in |
|---|---|---|
| linux | — | 5.15.0-91.101 |
| linux-allwinner-5.19 | — | — |
| linux-aws | — | 5.15.0-1051.56 |
| linux-aws-5.0 | — | — |
| linux-aws-5.11 | — | — |
| linux-aws-5.13 | — | — |
| linux-aws-5.15 | — | 5.15.0-1051.56~20.04.1 |
| linux-aws-5.19 | — | — |
| linux-aws-5.3 | — | — |
| linux-aws-5.4 | — | 5.4.0-1116.126~18.04.1 |
| linux-aws-5.8 | — | — |
| linux-aws-6.2 | — | — |
| linux-aws-6.5 | — | — |
| linux-aws-fips | — | — |
| linux-aws-hwe | — | — |
| linux-azure | — | 5.15.0-1053.61 |
| linux-azure-4.15 | — | — |
| linux-azure-5.11 | — | — |
| linux-azure-5.13 | — | — |
| linux-azure-5.15 | — | 5.15.0-1053.61~20.04.1 |
| linux-azure-5.19 | — | — |
| linux-azure-5.3 | — | — |
| linux-azure-5.4 | — | 5.4.0-1121.128~18.04.1 |
| linux-azure-5.8 | — | — |
| linux-azure-6.11 | — | — |
| linux-azure-6.2 | — | — |
| linux-azure-6.5 | — | — |
| linux-azure-edge | — | — |
| linux-azure-fde | — | — |
| linux-azure-fde-5.19 | — | — |
| linux-azure-fde-6.2 | — | — |
| linux-azure-fips | — | — |
| linux-bluefield | — | — |
| linux-fips | — | — |
| linux-gcp | — | 5.15.0-1048.56 |
| linux-gcp-4.15 | — | — |
| linux-gcp-5.11 | — | — |
| linux-gcp-5.13 | — | — |
| linux-gcp-5.15 | — | 5.15.0-1048.56~20.04.1 |
| linux-gcp-5.19 | — | — |
| linux-gcp-5.3 | — | — |
| linux-gcp-5.4 | — | 5.4.0-1120.129~18.04.1 |
| linux-gcp-5.8 | — | — |
| linux-gcp-6.11 | — | — |
| linux-gcp-6.2 | — | — |
| linux-gcp-6.5 | — | — |
| linux-gcp-fips | — | — |
| linux-gke | — | 5.15.0-1048.53 |
| linux-gke-4.15 | — | — |
| linux-gke-5.15 | — | — |
| linux-gke-5.4 | — | — |
| linux-gkeop | — | 5.15.0-1034.40 |
| linux-gkeop-5.15 | — | — |
| linux-gkeop-5.4 | — | — |
| linux-hwe | — | — |
| linux-hwe-5.11 | — | — |
| linux-hwe-5.13 | — | — |
| linux-hwe-5.15 | — | 5.15.0-91.101~20.04.1 |
| linux-hwe-5.19 | — | — |
| linux-hwe-5.4 | — | 5.4.0-169.187~18.04.1 |
| linux-hwe-5.8 | — | — |
| linux-hwe-6.11 | — | — |
| linux-hwe-6.2 | — | — |
| linux-hwe-6.5 | — | — |
| linux-hwe-edge | — | — |
| linux-ibm | — | 5.15.0-1044.47 |
| linux-ibm-5.15 | — | 5.15.0-1044.47~20.04.1 |
| linux-ibm-5.4 | — | 5.4.0-1063.68~18.04.1 |
| linux-intel | — | — |
| linux-intel-5.13 | — | — |
| linux-intel-iot-realtime | — | 5.15.0-1044.46 |
| linux-intel-iotg | — | 5.15.0-1046.52 |
| linux-intel-iotg-5.15 | — | 5.15.0-1046.52~20.04.1 |
| linux-iot | — | 5.4.0-1028.29 |
| linux-kvm | — | 5.15.0-1048.53 |
| linux-lowlatency | — | 5.15.0-91.101 |
| linux-lowlatency-hwe-5.15 | — | 5.15.0-91.101~20.04.1 |
| linux-lowlatency-hwe-5.19 | — | — |
| linux-lowlatency-hwe-6.11 | — | — |
| linux-lowlatency-hwe-6.2 | — | — |
| linux-lowlatency-hwe-6.5 | — | — |
| linux-nvidia | — | 5.15.0-1042.42 |
| linux-nvidia-6.2 | — | — |
| linux-nvidia-6.5 | — | — |
| linux-nvidia-tegra | — | 5.15.0-1020.20 |
| linux-nvidia-tegra-5.15 | — | 5.15.0-1020.20~20.04.1 |
| linux-nvidia-tegra-igx | — | 5.15.0-1007.7 |
| linux-oem | — | — |
| linux-oem-5.10 | — | — |
| linux-oem-5.13 | — | — |
| linux-oem-5.14 | — | — |
| linux-oem-5.17 | — | — |
| linux-oem-5.6 | — | — |
| linux-oem-6.0 | — | — |
| linux-oem-6.1 | — | — |
| linux-oem-6.11 | — | — |
| linux-oem-6.5 | — | — |
| linux-oem-6.8 | — | — |
| linux-oracle | — | 5.15.0-1049.55 |
| linux-oracle-5.0 | — | — |
| linux-oracle-5.11 | — | — |
| linux-oracle-5.13 | — | — |
| linux-oracle-5.15 | — | 5.15.0-1049.55~20.04.1 |
| linux-oracle-5.3 | — | — |
| linux-oracle-5.4 | — | 5.4.0-1115.124~18.04.1 |
| linux-oracle-5.8 | — | — |
| linux-oracle-6.5 | — | — |
| linux-raspi | — | 5.15.0-1044.47 |
| linux-raspi-5.4 | — | 5.4.0-1100.112~18.04.1 |
| linux-raspi-realtime | — | — |
| linux-raspi2 | — | — |
| linux-realtime | — | — |
| linux-riscv | — | — |
| linux-riscv-5.11 | — | — |
| linux-riscv-5.15 | — | 5.15.0-1047.51~20.04.1 |
| linux-riscv-5.19 | — | — |
| linux-riscv-5.8 | — | — |
| linux-riscv-6.5 | — | — |
| linux-starfive-5.19 | — | — |
| linux-starfive-6.2 | — | — |
| linux-starfive-6.5 | — | — |
| linux-xilinx-zynqmp | — | 5.15.0-1027.31 |
References
Similar Threats
- Unknown CGA-23jx-hhcx-m389
- Unknown CGA-2qp7-6757-fmgc
- Unknown CGA-2rj5-jc55-r267
- Unknown CGA-3m96-cwq8-6xmx
- Unknown CGA-3qj9-973w-fh9g
Vulnerability Monitoring
Track new vulnerabilities in linux
UBUNTU-CVE-2023-53245 is rated CVSS 5.5 Medium. BotEraser monitors your WordPress installation and notifies you when software you use appears in our vulnerability database.
Set Up Free Alerts →No credit card required · Results in minutes
ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.
