PatchSiren cyber security CVE debrief
CVE-2026-74386 Linux CVE debrief
A vulnerability in the Linux kernel's nvmet-tcp module can lead to a page fragment cache leak in error paths, potentially causing memory exhaustion over time if connections are repeatedly opened and closed. This issue arises when a connection is closed during the allocation process, and the error handling does not adequately drain the page fragment cache. As a result, a page leak occurs each time a connection fails during allocation, which could lead to memory exhaustion over time if connections are repeatedly opened and closed.
- Vendor
- Linux
- Product
- Unknown
- CVSS
- Unknown
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-08-15
- Original CVE updated
- 2026-10-30
- Advisory published
- 2026-08-15
- Advisory updated
- 2026-10-30
Who should care
Linux kernel administrators and security teams should assess exposure and prioritize patching or mitigating this vulnerability to prevent potential memory exhaustion. They should review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance. Additionally, they should plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.
Why it matters
Linux kernel administrators should assess exposure and prioritize patching or mitigating CVE-2026-74386 to prevent potential memory exhaustion.
- Memory exhaustion over time if connections are repeatedly opened and closed
- Potential for denial-of-service due to memory exhaustion
Technical summary
The Linux kernel's nvmet-tcp module has a vulnerability that can lead to a page fragment cache leak in error paths. This occurs when a connection is closed during the allocation process, and the error handling does not drain the page fragment cache. This can result in a page leak each time a connection fails during allocation, potentially leading to memory exhaustion over time if connections are repeatedly opened and closed.
Defensive priority
Linux kernel administrators should assess exposure and prioritize patching or mitigating this vulnerability to prevent potential memory exhaustion.
Recommended defensive actions
- Assess exposure of Linux kernel systems to this vulnerability
- Prioritize patching or mitigating the vulnerability
- Monitor for potential memory exhaustion issues
- Review compensating controls for exposed systems while remediation is scheduled and verified
- Check relevant monitoring, detection, and logs for exposed assets that need extra review
- Track exceptions, retest remediated assets, and close the item only after evidence is documented
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
Evidence notes
The CVE record and NVD entry provide details on the vulnerability, but the scope of affected systems and exploitation attempts are unknown. Linux kernel administrators and security teams should assess exposure and prioritize patching or mitigating this vulnerability to prevent potential memory exhaustion. The vulnerability is resolved in the Linux kernel through the fix: nvmet-tcp: fix page fragment cache leak in error path.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-74386 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-74386
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-74386 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-74386
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/4dae393956093c807212918fd91a8fc70df15338
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/5fbe83a374f09561a0f0c1f4aa021501ffd681eb
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/a43a9abc1ebf663f0aa56a729106f68dd9c77da6
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/aadb8eb9006e192c51b499860f40765de7d55680
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/ba3209704b3cd46961e4e081af5c52a780785648
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/fc11e3f0daaadb6e600a86e54b089d4662d0a464
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.