# CVE-2023-52454: nvmet-tcp: Fix a kernel panic when host sends an invalid H2C PDU length

> A remote attacker can cause a kernel panic and denial of service by sending an invalid H2C PDU length to the nvmet-tcp module.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 23 Feb 2024
- **Updated:** 5 Aug 2026
- **Also known as:** BELL-CVE-2023-52454, DEBIAN-CVE-2023-52454, GHSA-f594-3jwf-g74j, UBUNTU-CVE-2023-52454

## What is CVE-2023-52454?

CVE-2023-52454 is a high-severity vulnerability in Linux kernel, published on 23 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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

nvmet-tcp: Fix a kernel panic when host sends an invalid H2C PDU length

If the host sends an H2CData command with an invalid DATAL,
the kernel may crash in nvmet_tcp_build_pdu_iovec().

Unable to handle kernel NULL pointer dereference at
virtual address 0000000000000000
lr : nvmet_tcp_io_work+0x6ac/0x718 [nvmet_tcp]
Call trace:
  process_one_work+0x174/0x3c8
  worker_thread+0x2d0/0x3e8
  kthread+0x104/0x110

Fix the bug by raising a fatal error if DATAL isn't coherent
with the packet size.
Also, the PDU length should never exceed the MAXH2CDATA parameter which
has been communicated to the host in nvmet_tcp_handle_icreq().

Weakness: CWE-476 (NULL Pointer Dereference)

## Which versions are affected by CVE-2023-52454?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2023-52454?

Apply the vendor's patch.

## Is CVE-2023-52454 being exploited?

There is no known exploitation of CVE-2023-52454 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-52454 and fix it if it is affected.

What it is: CVE-2023-52454 is a high-severity vulnerability in Linux kernel, published on 23 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-52454 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-52454/ (Markdown: https://insights.sbomify.com/CVE-2023-52454/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-52454
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-52454
- OSV: https://osv.dev/vulnerability/CVE-2023-52454

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-52454/
Summaries are generated and may contain mistakes; the official description above is the record.