Vulnary
← back to the feed
Critical· 9.8official fix available

CVE-2023-54184

A critical bug in the Linux kernel’s iSCSI target module can cause a use‑after‑free and a NULL pointer dereference when an iSCSI session is closed. The flaw could allow an attacker to crash the system or potentially execute arbitrary code. The kernel has already incorporated a fix that moves the cleanup of recovery entries before the session is freed.

publishedDec 30, 2025
last modifiedAug 4, 2026
sourcesNVD
severity · cvss
9.8
critical · how bad it is
exploitation · epss
<1%
8th percentile · chance of exploitation in 30 days
(ai-assisted) A model wrote this summary from the official data, so double-check it against the source before you act on it. Read the official advisory →
auto-deletes from the system
counting…on Sep 3, 2026

An official fix is available, so this entry is kept for 30 days and then removed automatically.

01

Who is affected

Linux kernel, specifically the iSCSI target (scsi: target: iscsit) module. Any system running a kernel version before the fix, such as older distributions that ship with an unpatched kernel, is affected.

02

Real-world impact

An attacker could crash the kernel or gain arbitrary code execution by triggering the use‑after‑free during an iSCSI session teardown, potentially compromising the entire system.

03

Why this severity

The CVSS score of 9.8 reflects the lack of authentication or user interaction required, the high impact on confidentiality, integrity, and availability, and the ease of exploitation through a remote iSCSI connection.

04

What to do about it

official fix available
recommended steps
  1. 01Upgrade your Linux kernel to a version that includes the fix.
  2. 02Reboot the system to load the new kernel.

NVD description indicates the kernel has resolved the issue.

05

Timeline

  1. Dec 30, 2025 · Dec 30, 2025
    Published
    Disclosed and added to the National Vulnerability Database.
  2. Aug 4, 2026 · 1d ago
    Advisory updated
    The NVD record was last revised.
  3. Aug 4, 2026 · 1d ago
    Official fix available
    A vendor patch or mitigation now exists — see the remediation steps above.
06

How it’s attacked

Attack vectorNetwork (remote)
Attack complexityLow
Privileges requiredNone
User interactionNone needed
ScopeUnchanged
Confidentiality impactHigh
Integrity impactHigh
Availability impactHigh
07

References & advisories

(ai-assisted) A model wrote this summary from the official data, so double-check it against the source before you act on it. Read the official advisory →