CVE-2026-97952
Received Received - Intake

Memory Leak in Linux Kernel sunvdc Driver

Vulnerability report for CVE-2026-97952, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-09-25

Last updated on: 2026-10-03

Assigner: kernel.org

Description

In the Linux kernel, the following vulnerability has been resolved: sunvdc: unmap LDC cookies when the descriptor send fails __send_request() maps the request's pages into the LDC channel's map table (ldc_map_sg()), fills in the descriptor and marks it VIO_DESC_READY before ringing the doorbell via __vdc_tx_trigger(). When the trigger fails, the error path only prints a message: the descriptor stays READY and the cookies are never unmapped. The mapping is normally released in vdc_end_one() when the peer completes the descriptor - but a descriptor whose doorbell was never sent will never complete, and since dr->prod is not advanced on failure, the reset path (vdc_requeue_inflight(), which walks [cons, prod)) never visits it either. The map table entries are leaked permanently. Since commit a11f6ca9aef9 ("sunvdc: Do not spin in an infinite loop when vio_ldc_send() returns EAGAIN") trigger failures occur in practice under load, so every resulting I/O error also leaks one request's worth of entries from the fixed-size (8192 entries per channel) map table. Because the allocator hands out contiguous ranges, fragmentation makes large multi-segment requests fail first as the table drains, until ldc_map_sg() fails permanently and the disk is dead until reboot. It also makes any retry-based recovery unusable: requeuing the request on -EAGAIN remaps the pages on every attempt, overwriting desc->cookies and orphaning the previous mapping, so the table drains at the retry rate. This is the memory exhaustion observed when the requeue approach was first tested in October 2025. Roll back on failure: unmap the cookies, mark the descriptor FREE again and clear the request entry. If the trigger failed with -ENOTCONN, __vdc_tx_trigger() has already reset the port, which tears down and reallocates both the dring and the LDC channel including its map table - nothing to roll back, and the stale descriptor must not be touched.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-09-25
Last Modified
2026-10-03
Generated
2026-10-15
AI Q&A
2026-09-25
EPSS Evaluated
2026-10-14
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
linux linux_kernel *

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This is a memory leak vulnerability in the Linux kernel's sunvdc driver. When sending data fails, the driver does not properly clean up memory mappings, causing permanent resource leaks in the LDC channel's map table. This leads to table exhaustion and disk failure under load.

Detection Guidance

This vulnerability is specific to the Linux kernel's sunvdc driver and involves memory leaks in LDC channel map tables. Detection requires checking for I/O errors, disk failures, or kernel logs indicating sunvdc-related issues under load. Monitor for 'ldc_map_sg' failures or 'map table entries leaked' messages in kernel logs.

Impact Analysis

It can cause system instability by exhausting kernel memory for disk I/O operations, leading to disk failures that require reboot to recover. Under heavy load, I/O errors may occur as the map table fills up, eventually making the disk unusable until reboot.

Compliance Impact

This vulnerability primarily causes memory leaks and system instability in the Linux kernel's sunvdc driver, leading to potential denial of service or data corruption. It does not directly impact compliance with GDPR or HIPAA, as those standards focus on data protection, privacy, and security controls rather than kernel-level memory management issues.

Mitigation Strategies

Apply the kernel patch that resolves this issue. If immediate patching is not possible, avoid high I/O load on affected systems and monitor for disk failures. Rebooting the system may temporarily resolve symptoms but does not fix the underlying issue.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-97952. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart