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

CVE-2026-98724 is fixed in linux on 1 platform by DEBIAN-CVE-2026-98724 (version 7.2.10-1), released October 19, 2026. It is not reported as exploited. Patch Radar priority: Routine.

- Web page: https://patchblox.com/security/cve/CVE-2026-98724
- Priority: Routine
- CVSS: n/a
- EPSS: 0.0020
- CISA KEV: not listed
- Exploited (vendor report): no
- Publicly disclosed: no
- Published: Oct 18, 2026
- Vendor advisory: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-98724

## 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.

## Where it's fixed

| Platform | Product | Fixed in | Fix | Released |
|---|---|---|---|---|
| Linux | linux Debian 14 | 7.2.10-1 | [DEBIAN-CVE-2026-98724](https://patchblox.com/security/data/fix/linux/debian-cve-2026-98724.md) | Oct 19, 2026 |

---

Data as of 2026-11-08T13:06:02Z UTC. Source: Patchblox Patch Radar (https://patchblox.com/security/patch-radar). Patchblox finds out-of-date software on Windows, macOS and Linux and updates it through release rings: https://patchblox.com/demo

Free to use with attribution: show "Data: Patchblox Patch Radar" with a link to https://patchblox.com/security/patch-radar. Terms, including what needs a written agreement: https://patchblox.com/security/patch-radar/use-the-data

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.