Menu

Star on GitHub · 3.2k

CVE-2026-72128

In the Linux kernel, the following vulnerability has been resolved: nvmet: fix refcount leak in nvmet_sq_create() In nvmet_sq_create(), a reference on the ctrl is taken via kref_get_unless_zero()…

Published Aug 15, 2026EPSS 0.21%

Overview

CVE-2026-72128 is a known-severity vulnerability. It was published on August 15, 2026.

Technical description

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

nvmet: fix refcount leak in nvmet_sq_create()

In nvmet_sq_create(), a reference on the ctrl is taken

via kref_get_unless_zero() before calling nvmet_check_sqid().

If nvmet_check_sqid() fails, the function returns the error

directly without releasing the reference, leading to a leak.

Fix this by jumping to the "ctrl_put" label, which already

performs the necessary nvmet_ctrl_put(ctrl). This ensures the

reference is properly released on this error path.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2026-72128?

CVE-2026-72128 is a known-severity vulnerability. It was published on August 15, 2026.

How severe is CVE-2026-72128?

CVSS score information is not yet available for this vulnerability. Check back as the CVE record is updated by NVD analysts.

How do I fix or remediate CVE-2026-72128?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-72128?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-72128 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.