Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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

MediumCVSS 5.5 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.14% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 048ebc9a28fb918ee635dd4b2fcf4248eb6e4050, 1678408d08f31a694d5150a56796dd04c9710b22, 175544ad48cbf56affeef2a679c6a4d4fb1e2881.

Low priority for now. Upgrade to Linux Linux 048ebc9a28fb918ee635dd4b2fcf4248eb6e4050, 1678408d08f31a694d5150a56796dd04c9710b22, 175544ad48cbf56affeef2a679c6a4d4fb1e2881 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

Published
Sep 15, 2025
Updated
Jun 17, 2026
EPSS
0.1% · 4th percentile

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2023-53245

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 4.13affected
    • 3930d7309807ba0bfa460dfa9ed68d5560347dd2 and later · before cd87f4df9865a53807001ed12c0f0420b14ececdaffected · git
    • 3930d7309807ba0bfa460dfa9ed68d5560347dd2 and later · before 311db605e07f0d4fc0cc7ddb74f1e5692ea2f469affected · git
    • 3930d7309807ba0bfa460dfa9ed68d5560347dd2 and later · before 048ebc9a28fb918ee635dd4b2fcf4248eb6e4050affected · git
    • 3930d7309807ba0bfa460dfa9ed68d5560347dd2 and later · before 1678408d08f31a694d5150a56796dd04c9710b22affected · git
    • 3930d7309807ba0bfa460dfa9ed68d5560347dd2 and later · before 7a792b3d888aab2c65389f9f4f9f2f6c000b1a0daffected · git
    • 3930d7309807ba0bfa460dfa9ed68d5560347dd2 and later · before ed70fa5629a8b992a5372d7044d1db1f8fa6de29affected · git
    • 3930d7309807ba0bfa460dfa9ed68d5560347dd2 and later · before 763c06565055ae373fe7f89c11e1447bd1ded264affected · git
    • 3930d7309807ba0bfa460dfa9ed68d5560347dd2 and later · before 175544ad48cbf56affeef2a679c6a4d4fb1e2881affected · git
    • before 4.13not affected · semver
Affected versions · NVD (8)

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel4.13 and later · before 4.14.323
  • linux linux kernel4.15 and later · before 4.19.292
  • linux linux kernel4.20 and later · before 5.4.254
  • linux linux kernel5.5 and later · before 5.10.191
  • linux linux kernel5.11 and later · before 5.15.127
  • linux linux kernel5.16 and later · before 6.1.46
  • linux linux kernel6.2 and later · before 6.4.11
  • linux linux kernel6.5

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.52-16.1.52-1
Debian:13linuxbefore 6.4.11-16.4.11-1
Red Hat:rhel_eus:8.6::baseosbpftoolbefore 0:4.18.0-372.75.1.el8_60:4.18.0-372.75.1.el8_6
Red Hat:rhel_eus:8.6::baseoskernelbefore 0:4.18.0-372.75.1.el8_60:4.18.0-372.75.1.el8_6
Red Hat:rhel_eus:8.6::baseoskernel-abi-stablelistsbefore 0:4.18.0-372.75.1.el8_60:4.18.0-372.75.1.el8_6
Red Hat:rhel_eus:8.6::baseoskernel-corebefore 0:4.18.0-372.75.1.el8_60:4.18.0-372.75.1.el8_6
Red Hat:rhel_eus:8.6::baseoskernel-debugbefore 0:4.18.0-372.75.1.el8_60:4.18.0-372.75.1.el8_6
Red Hat:rhel_eus:8.6::baseoskernel-debug-corebefore 0:4.18.0-372.75.1.el8_60:4.18.0-372.75.1.el8_6
Red Hat:rhel_eus:8.6::baseoskernel-debug-develbefore 0:4.18.0-372.75.1.el8_60:4.18.0-372.75.1.el8_6
Red Hat:rhel_eus:8.6::baseoskernel-debug-modulesbefore 0:4.18.0-372.75.1.el8_60:4.18.0-372.75.1.el8_6
Red Hat:rhel_eus:8.6::baseoskernel-debug-modules-extrabefore 0:4.18.0-372.75.1.el8_60:4.18.0-372.75.1.el8_6
Red Hat:rhel_eus:8.6::baseoskernel-debuginfo-common-aarch64before 0:4.18.0-372.75.1.el8_60:4.18.0-372.75.1.el8_6
Red Hat:rhel_eus:8.6::baseoskernel-debuginfo-common-ppc64lebefore 0:4.18.0-372.75.1.el8_60:4.18.0-372.75.1.el8_6
Red Hat:rhel_eus:8.6::baseoskernel-debuginfo-common-s390xbefore 0:4.18.0-372.75.1.el8_60:4.18.0-372.75.1.el8_6
Red Hat:rhel_eus:8.6::baseoskernel-docbefore 0:4.18.0-372.75.1.el8_60:4.18.0-372.75.1.el8_6
Red Hat:rhel_eus:8.6::baseoskernel-modulesbefore 0:4.18.0-372.75.1.el8_60:4.18.0-372.75.1.el8_6
Red Hat:rhel_eus:8.6::baseoskernel-modules-extrabefore 0:4.18.0-372.75.1.el8_60:4.18.0-372.75.1.el8_6
Red Hat:rhel_eus:8.6::baseoskernel-toolsbefore 0:4.18.0-372.75.1.el8_60:4.18.0-372.75.1.el8_6
Red Hat:rhel_eus:8.6::baseoskernel-tools-libsbefore 0:4.18.0-372.75.1.el8_60:4.18.0-372.75.1.el8_6
Red Hat:rhel_eus:8.6::baseoskernel-zfcpdumpbefore 0:4.18.0-372.75.1.el8_60:4.18.0-372.75.1.el8_6
Red Hat:rhel_eus:8.6::baseoskernel-zfcpdump-corebefore 0:4.18.0-372.75.1.el8_60:4.18.0-372.75.1.el8_6
Red Hat:rhel_eus:8.6::baseoskernel-zfcpdump-debuginfobefore 0:4.18.0-372.75.1.el8_60:4.18.0-372.75.1.el8_6
Red Hat:rhel_eus:8.6::baseoskernel-zfcpdump-develbefore 0:4.18.0-372.75.1.el8_60:4.18.0-372.75.1.el8_6
Red Hat:rhel_eus:8.6::baseoskernel-zfcpdump-modulesbefore 0:4.18.0-372.75.1.el8_60:4.18.0-372.75.1.el8_6

+49

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2023-53243Sep 15, 2025 · btrfs: add handling for RAID1C23/DUP to btrfs_reduce_alloc_profile
    22Monitor
  • ← EarlierCVE-2023-53244Sep 15, 2025 · media: pci: tw68: Fix null-ptr-deref bug in buf prepare and finish
    22Monitor
  • Later →CVE-2023-53246Sep 15, 2025 · cifs: fix DFS traversal oops without CONFIG_CIFS_DFS_UPCALL
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux048ebc9a28fb918ee635dd4b2fcf4248eb6e4050Vendor (CNA)
Linux Linux1678408d08f31a694d5150a56796dd04c9710b22Vendor (CNA)
Linux Linux175544ad48cbf56affeef2a679c6a4d4fb1e2881Vendor (CNA)
Linux Linux311db605e07f0d4fc0cc7ddb74f1e5692ea2f469Vendor (CNA)
Linux Linux763c06565055ae373fe7f89c11e1447bd1ded264Vendor (CNA)
Linux Linux7a792b3d888aab2c65389f9f4f9f2f6c000b1a0dVendor (CNA)
Linux Linuxcd87f4df9865a53807001ed12c0f0420b14ececdVendor (CNA)
Linux Linuxed70fa5629a8b992a5372d7044d1db1f8fa6de29Vendor (CNA)
debian:linux6.1.52-1 · Debian:12Package registry (OSV)
red hat:bpftool-debuginfo0:5.14.0-70.75.1.el9_0 · Red Hat:rhel_eus:9.0::appstreamPackage registry (OSV)
red hat:kernel-debug-debuginfo0:5.14.0-70.75.1.el9_0 · Red Hat:rhel_eus:9.0::appstreamPackage registry (OSV)
red hat:kernel-debug-devel0:5.14.0-70.75.1.el9_0 · Red Hat:rhel_eus:9.0::appstreamPackage registry (OSV)
red hat:kernel-debug-devel-matched0:5.14.0-70.75.1.el9_0 · Red Hat:rhel_eus:9.0::appstreamPackage registry (OSV)
red hat:kernel-debuginfo0:5.14.0-70.75.1.el9_0 · Red Hat:rhel_eus:9.0::appstreamPackage registry (OSV)
red hat:kernel-debuginfo-common-aarch640:5.14.0-70.75.1.el9_0 · Red Hat:rhel_eus:9.0::appstreamPackage registry (OSV)
red hat:kernel-debuginfo-common-ppc64le0:5.14.0-70.75.1.el9_0 · Red Hat:rhel_eus:9.0::appstreamPackage registry (OSV)
red hat:kernel-debuginfo-common-s390x0:5.14.0-70.75.1.el9_0 · Red Hat:rhel_eus:9.0::appstreamPackage registry (OSV)
red hat:kernel-debuginfo-common-x86_640:5.14.0-70.75.1.el9_0 · Red Hat:rhel_eus:9.0::appstreamPackage registry (OSV)
red hat:kernel-devel0:5.14.0-70.75.1.el9_0 · Red Hat:rhel_eus:9.0::appstreamPackage registry (OSV)
red hat:kernel-devel-matched0:5.14.0-70.75.1.el9_0 · Red Hat:rhel_eus:9.0::appstreamPackage registry (OSV)
red hat:kernel-doc0:5.14.0-70.75.1.el9_0 · Red Hat:rhel_eus:9.0::appstreamPackage registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

CWE-476 · NULL Pointer Dereference

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

References

Show all references (7 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records