Skip to main content
Mallory
UnratedVulnerability

CVE-2026-38264: Linux kernel nvme-tcp request list handling flaw

Updated 5 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS-Not scored
EPSS-30-day exploit probability
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-38264CWE-20

The provided content identifies CVE-2026-38264 as a Linux kernel vulnerability in the nvme-tcp subsystem, described by SUSE as "nvme-tcp: sanitize request list handling." It is referenced in cumulative SUSE kernel security advisories affecting products including SUSE Linux Enterprise Server 16.0, SUSE Linux Micro 6.2, SUSE Linux Micro Extras 6.2, and related package sets built from kernel version 6.12.0-160000.6.1. No further technical root-cause detail, vulnerable function name, trigger condition, or upstream commit information is provided in the supplied content beyond the fact that the fix sanitizes request list handling in nvme-tcp.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

The specific technical impact is not explicitly stated in the provided content. Based on the vendor context, this is a Linux kernel vulnerability in nvme-tcp request list handling that could affect systems running vulnerable kernel packages. Successful exploitation could plausibly lead to kernel instability, denial of service, or other kernel-level impact, but the exact impact is currently not available from the supplied material.

Mitigation

If you can’t patch tonight, do this now.

No specific workaround or temporary mitigation is provided in the supplied content. If immediate patching is not possible, reduce exposure of systems using the Linux kernel nvme-tcp functionality where operationally feasible, but the content does not provide an official mitigation. SUSE notes generally that some released updates may at times be only a partial fix.

Remediation

Patch, then assume compromise.

Apply the relevant SUSE kernel security updates that include the fix for CVE-2026-38264. The content references fixed package sets in advisories including SUSE-SU-2025:20994-1, SUSE-SU-2025:20996-1, SUSE-SU-2025:21074-1, SUSE-SU-2025:21139-1, SUSE-SU-2025:21179-1, and SUSE-SU-2026:20560-1, depending on product line. For affected SUSE Linux Micro 6.2 / Extras 6.2 and SLES 16.0 package sets, update to the released kernel builds based on version 6.12.0-160000.6.1 or the corresponding vendor-fixed package for the specific product and architecture.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

Frequently asked questions

Is CVE-2026-38264 exploited in the wild?
As of Jun 27, 2026, Mallory has no reports of CVE-2026-38264 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-38264?
As of Jun 27, 2026, Mallory has found no public exploit for CVE-2026-38264.
Is there a patch for CVE-2026-38264?
Apply the relevant SUSE kernel security updates that include the fix for CVE-2026-38264. The content references fixed package sets in advisories including SUSE-SU-2025:20994-1, SUSE-SU-2025:20996-1, SUSE-SU-2025:21074-1, SUSE-SU-2025:21139-1, SUSE-SU-2025:21179-1, and SUSE-SU-2026:20560-1, depending on product line.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.