CVE-2023-5178

Kernel: use after free in nvmet_tcp_free_crypto in nvme

HIGH

8.8

CVSS Score

Published: November 1, 2023 at 04:32 PM UTC

Updated: October 14, 2026 at 10:17 PM UTC

5 products affected across 3 vendorsLinux KernelEnterprise LinuxActive IQ Unified Manager

Using Red Hat Enterprise Linux 8 by Red Hat?

Get instant alerts when new vulnerabilities affect Red Hat Enterprise Linux 8 - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

HIGH8.8

Exploit prediction

EPSS 10%

Description

A use-after-free vulnerability was found in drivers/nvme/target/tcp.c` in `nvmet_tcp_free_crypto` due to a logical bug in the NVMe/TCP subsystem in the Linux kernel. This issue may allow a malicious user to cause a use-after-free and double-free problem, which may permit remote code execution or lead to local privilege escalation.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Linux Kernel · Linux

95%

All versions5.0 ≤ v < 5.4.2605.11 ≤ v < 5.15.1375.16 ≤ v < 6.1.605.5 ≤ v < 5.10.1996.2 ≤ v < 6.5.9

Affected range stops below 5.10.199, so it looks safe — our inference, not a vendor statement

Affected range stops below 5.15.137, so it looks safe — our inference, not a vendor statement

Affected range stops below 5.4.260, so it looks safe — our inference, not a vendor statement

Affected range stops below 6.1.60, so it looks safe — our inference, not a vendor statement

Affected range stops below 6.5.9, so it looks safe — our inference, not a vendor statement

Active IQ Unified Manager · NetAppnpm

95%

All versions

Solidfire & Hci Management Node · NetApp

95%

All versions

Solidfire & Hci Storage Node · NetApp

95%

All versions

Enterprise Linux · Red Hatrpm

95%

8.0 9.0

Vendor states this is fixed in 0:4.18.0-193.128.1.el8_2 (unaffected)

Vendor states this is fixed in 0:4.18.0-193.128.1.rt13.179.el8_2 (unaffected)

Vendor states this is fixed in 0:4.18.0-305.114.1.el8_4 (unaffected)

Vendor states this is fixed in 0:4.18.0-305.114.1.rt7.190.el8_4 (unaffected)

Vendor states this is fixed in 0:4.18.0-372.87.1.el8_6 (unaffected)

Vendor states this is fixed in 0:4.18.0-477.43.1.el8_8 (unaffected)

Vendor states this is fixed in 0:4.18.0-513.9.1.el8_9 (unaffected)

Vendor states this is fixed in 0:4.18.0-513.9.1.rt7.311.el8_9 (unaffected)

Vendor states this is fixed in 0:5.14.0-284.40.1.el9_2 (unaffected)

Vendor states this is fixed in 0:5.14.0-284.40.1.rt14.325.el9_2 (unaffected)

Vendor states this is fixed in 0:5.14.0-362.18.1.el9_3 (unaffected)

Vendor states this is fixed in 0:5.14.0-70.85.1.el9_0 (unaffected)

Vendor states this is fixed in 0:5.14.0-70.85.1.rt21.156.el9_0 (unaffected)

Vendor states this is fixed in 6 (unaffected)

Vendor states this is fixed in 7 (unaffected)

Vendor states this is fixed in 8 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references