Linux Kernel up to 6.4.10 fc_eh_timed_out null pointer dereference

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
5.5$0-$5k0.00

Summaryinfo

A vulnerability, which was classified as critical, was found in Linux Kernel up to 6.4.10. This affects the function fc_eh_timed_out. The manipulation results in null pointer dereference. This vulnerability was named CVE-2023-53245. There is no available exploit. You should upgrade the affected component.

Detailsinfo

A vulnerability classified as critical has been found in Linux Kernel up to 6.4.10. Affected is the function fc_eh_timed_out. The manipulation with an unknown input leads to a null pointer dereference vulnerability. CWE is classifying the issue as CWE-476. A NULL pointer dereference occurs when the application dereferences a pointer that it expects to be valid, but is NULL, typically causing a crash or exit. This is going to have an impact on availability. CVE summarizes:

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.

The advisory is available at git.kernel.org. This vulnerability is traded as CVE-2023-53245 since 09/15/2025. Technical details are known, but there is no available exploit.

The vulnerability scanner Nessus provides a plugin with the ID 281815 (Amazon Linux 2 : kernel, --advisory ALAS2KERNEL-5.4-2025-116 (ALASKERNEL-5.4-2025-116)), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 4.14.323, 4.19.292, 5.4.254, 5.10.191, 5.15.127, 6.1.46 or 6.4.11 eliminates this vulnerability. Applying the patch cd87f4df9865a53807001ed12c0f0420b14ececd/311db605e07f0d4fc0cc7ddb74f1e5692ea2f469/048ebc9a28fb918ee635dd4b2fcf4248eb6e4050/1678408d08f31a694d5150a56796dd04c9710b22/7a792b3d888aab2c65389f9f4f9f2f6c000b1a0d/ed70fa5629a8b992a5372d7044d1db1f8fa6de29/763c06565055ae373fe7f89c11e1447bd1ded264/175544ad48cbf56affeef2a679c6a4d4fb1e2881 is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the databases at Tenable (281815) and CERT Bund (WID-SEC-2025-2053). If you want to get best quality of vulnerability data, you may have to visit VulDB.

Affected

  • Debian Linux
  • Amazon Linux 2
  • Red Hat Enterprise Linux
  • Ubuntu Linux
  • SUSE Linux
  • Oracle Linux
  • IBM QRadar SIEM
  • SUSE openSUSE
  • Open Source Linux Kernel
  • RESF Rocky Linux
  • Dell Secure Connect Gateway
  • F5 F5OS

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.6
VulDB Meta Temp Score: 5.5

VulDB Base Score: 5.7
VulDB Temp Score: 5.5
VulDB Vector: 🔒
VulDB Reliability: 🔍

NVD Base Score: 5.5
NVD Vector: 🔒

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Null pointer dereference
CWE: CWE-476 / CWE-404
CAPEC: 🔒
ATT&CK: 🔒

Physical: Partially
Local: Yes
Remote: Partially

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 281815
Nessus Name: Amazon Linux 2 : kernel, --advisory ALAS2KERNEL-5.4-2025-116 (ALASKERNEL-5.4-2025-116)

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 4.14.323/4.19.292/5.4.254/5.10.191/5.15.127/6.1.46/6.4.11
Patch: cd87f4df9865a53807001ed12c0f0420b14ececd/311db605e07f0d4fc0cc7ddb74f1e5692ea2f469/048ebc9a28fb918ee635dd4b2fcf4248eb6e4050/1678408d08f31a694d5150a56796dd04c9710b22/7a792b3d888aab2c65389f9f4f9f2f6c000b1a0d/ed70fa5629a8b992a5372d7044d1db1f8fa6de29/763c06565055ae373fe7f89c11e1447bd1ded264/175544ad48cbf56affeef2a679c6a4d4fb1e2881

Timelineinfo

09/15/2025 Advisory disclosed
09/15/2025 +0 days CVE reserved
09/15/2025 +0 days VulDB entry created
01/11/2026 +118 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2023-53245 (🔒)
GCVE (CVE): GCVE-0-2023-53245
GCVE (VulDB): GCVE-100-324018
CERT Bund: WID-SEC-2025-2053 - Linux Kernel: Mehrere Schwachstellen

Entryinfo

Created: 09/15/2025 17:01
Updated: 01/11/2026 07:42
Changes: 09/15/2025 17:01 (58), 12/04/2025 01:42 (10), 12/29/2025 05:52 (7), 01/06/2026 12:32 (2), 01/11/2026 07:42 (1)
Complete: 🔍
Cache ID: 216::103

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Are you interested in using VulDB?

Download the whitepaper to learn more about our service!