Skip to main content

Linux CVE-2026-23376

| EUVDEUVD-2026-15366 MEDIUM
2026-03-25 Linux GHSA-36q5-3685-99hr
Linux Information Disclosure Red Hat
5.5
CVSS 3.1 · NVD
Share

Severity by source

NVD PRIMARY
5.5 MEDIUM
AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
SUSE
MEDIUM
qualitative
Red Hat
3.3 LOW
qualitative

Primary rating from NVD.

CVSS VectorNVD

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

Lifecycle Timeline

5
CVSS changed
Apr 24, 2026 - 16:22 NVD
5.5 (MEDIUM)
Patch released
Mar 31, 2026 - 21:13 nvd
Patch available
EUVD ID Assigned
Mar 25, 2026 - 10:45 euvd
EUVD-2026-15366
Analysis Generated
Mar 25, 2026 - 10:45 vuln.today
CVE Published
Mar 25, 2026 - 10:27 nvd
N/A

DescriptionCVE.org

In the Linux kernel, the following vulnerability has been resolved:

nvmet-fcloop: Check remoteport port_state before calling done callback

In nvme_fc_handle_ls_rqst_work, the lsrsp->done callback is only set when remoteport->port_state is FC_OBJSTATE_ONLINE. Otherwise, the nvme_fc_xmt_ls_rsp's LLDD call to lport->ops->xmt_ls_rsp is expected to fail and the nvme-fc transport layer itself will directly call nvme_fc_xmt_ls_rsp_free instead of relying on LLDD's done callback to free the lsrsp resources.

Update the fcloop_t2h_xmt_ls_rsp routine to check remoteport->port_state. If online, then lsrsp->done callback will free the lsrsp. Else, return -ENODEV to signal the nvme-fc transport to handle freeing lsrsp.

AnalysisAI

A resource management vulnerability exists in the Linux kernel's nvmet-fcloop NVMe-FC loopback driver where the lsrsp (LS response) callback is invoked without proper validation of the remote port state, potentially leading to use-after-free or double-free conditions. This affects Linux kernel implementations using nvmet-fcloop for NVMe-FC transport emulation across all versions prior to the patch commits (f30b95159a53e72529a9ca1667f11cd1970240a7, 31d3817bcd9e192b30abe3cf4b68f69d48864dd2, dd677d0598387ea623820ab2bd0e029c377445a3). An attacker with local kernel-level access or ability to trigger abnormal nvmet-fcloop state transitions could potentially cause information disclosure or denial of service through memory corruption.

Technical ContextAI

The vulnerability resides in the nvmet-fcloop module, which provides a loopback transport for NVMe-FC (Fibre Channel over Fabrics) protocol emulation in the Linux kernel nvme-target subsystem. The affected code path processes link service requests through nvme_fc_handle_ls_rqst_work. The root cause is a missing state validation check in the fcloop_t2h_xmt_ls_rsp routine before invoking the lsrsp->done callback. Specifically, when remoteport->port_state is not FC_OBJSTATE_ONLINE, the NVMe-FC transport layer expects LLDD (Low-Level Driver) operations to fail with an error code, allowing the transport to properly free resources via nvme_fc_xmt_ls_rsp_free. However, the fcloop driver was invoking the done callback regardless of port state, causing double-free conditions when both the callback and the transport layer attempt to free the same lsrsp resource. The CPE string (cpe:2.3:a:linux:linux:*:*:*:*:*:*:*:*) indicates all Linux kernel versions are potentially affected, though the vulnerability is specific to systems with nvmet-fcloop enabled.

RemediationAI

Apply the Linux kernel patches from the stable tree commits f30b95159a53e72529a9ca1667f11cd1970240a7, 31d3817bcd9e192b30abe3cf4b68f69d48864dd2, or dd677d0598387ea623820ab2bd0e029c377445a3 by upgrading to a patched kernel version (specific version depends on distribution and kernel branch). The primary fix adds remoteport->port_state validation in fcloop_t2h_xmt_ls_rsp to return -ENODEV when port state is not FC_OBJSTATE_ONLINE, ensuring the NVMe-FC transport layer handles resource cleanup instead of invoking the LLDD callback. For systems unable to immediately patch, disable nvmet-fcloop module (via modprobe blacklist or kernel build configuration) if not required for production workloads. Monitor official Linux kernel security advisories and distribution-specific security bulletins for stable release timelines. Users should reference kernel.org Git repository links for complete patch details and test in non-production environments before deployment.

Same technique Information Disclosure

View all
CVE-2013-2251 CRITICAL POC
9.8
CVE-2017-5638 CRITICAL POC
9.8
CVE-2025-24813 CRITICAL POC
9.8
CVE-2015-1701 HIGH POC
7.8
CVE-2017-0147 HIGH POC
7.5
CVE-2014-6324 HIGH POC
8.8
CVE-2023-7028 CRITICAL POC
10.0
CVE-2017-0213 HIGH POC
7.3

Vendor StatusVendor

Debian

linux
Release Status Fixed Version Urgency
bullseye not-affected - -
bullseye (security) fixed 5.10.251-1 -
bookworm not-affected - -
bookworm (security) fixed 6.1.164-1 -
trixie not-affected - -
trixie (security) fixed 6.12.74-2 -
forky, sid fixed 6.19.8-1 -
(unstable) fixed 6.19.8-1 -

SUSE

Severity: Medium
Product Status
SUSE Linux Enterprise Desktop 15 SP7 Fixed
SUSE Linux Enterprise Desktop 15 SP7 Fixed
SUSE Linux Enterprise High Availability Extension 15 SP7 Fixed
SUSE Linux Enterprise High Availability Extension 15 SP7 Fixed
SUSE Linux Enterprise High Performance Computing 15 SP7 Fixed

Share

CVE-2026-23376 vulnerability details – vuln.today
Back

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy