# CVE-2026-98724: nvmet: pci-epf: reject too-short SGL segments

> A host-controlled SGL length in the Linux kernel NVMe PCI endpoint driver causes an out-of-bounds read, potentially leading to kernel panic or code execution.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** BELL-CVE-2026-98724, DEBIAN-CVE-2026-98724, GHSA-hhpp-pj9h-fh67, UBUNTU-CVE-2026-98724

## What is CVE-2026-98724?

CVE-2026-98724 is a memory corruption vulnerability in Linux, published on 18 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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

nvmet: pci-epf: reject too-short SGL segments

The host controls an SGL segment's length. A nonzero length smaller than
one SGL descriptor makes nr_descs zero, so
nvmet_pci_epf_get_sgl_segment() reads the type byte of sgls[-1] outside
the allocated buffer. If that byte contains a segment descriptor type,
the function also copies the preceding 16 bytes and returns a negative
descriptor count.

The read was reproduced in 3/3 KASAN boots with only the host transfer
mocked by a KUnit test:

  BUG: KASAN: slab-out-of-bounds in nvmet_pci_epf_get_sgl_segment
  Read of size 1 by task kunit_try_catch
  Call Trace:
   nvmet_pci_epf_get_sgl_segment
   nvmet_pci_epf_short_sgl_test
  Kernel panic - not syncing: KASAN: panic_on_warn set ...

Reject segments that cannot hold one descriptor before allocating or
transferring their contents.

## Which versions are affected by CVE-2026-98724?


## How do I fix CVE-2026-98724?

Apply the vendor's patch.

## Is CVE-2026-98724 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-98724 and fix it if it is affected.

What it is: CVE-2026-98724 is a memory corruption vulnerability in Linux, published on 18 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-98724 in the wild and no public exploit code.

Affected product: Linux. 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-2026-98724/ (Markdown: https://insights.sbomify.com/CVE-2026-98724/index.md)
```

## Sources

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

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