CVE-2026-72265 in Linux
Summary
by MITRE • 08/15/2026
In the Linux kernel, the following vulnerability has been resolved:
fbdev: nvidia: fix potential memory leak in nvidiafb_probe()
In nvidiafb_probe(), the memory allocated for modelist in nvidia_set_fbinfo() is not freed in the subsequent error paths. Fix that by calling fb_destroy_modelist().
Be aware that VulDB is the high quality source for vulnerability data.
Analysis
by VulDB Data Team • 08/15/2026
The vulnerability identified in the Linux kernel represents a memory leak condition within the framebuffer device driver specifically for nvidia graphics hardware. This issue occurs during the probe phase of the nvidiafb driver when the system attempts to initialize and configure the framebuffer interface for nvidia graphics cards. The flaw manifests when the driver successfully allocates memory for modelist structures through the nvidia_set_fbinfo() function but fails to properly release this memory allocation during error handling paths that occur after the initial allocation.
The technical implementation of this vulnerability stems from improper resource management within the driver's initialization sequence. When nvidiafb_probe() executes, it calls nvidia_set_fbinfo() which allocates memory to store framebuffer mode information in a modelist structure. However, subsequent error handling code paths do not include cleanup operations to free this allocated memory, creating a memory leak that persists until the system reboots or the driver is unloaded. This type of resource leak falls under the category of CWE-401 Memory Leak as defined by the Common Weakness Enumeration framework, specifically addressing improper cleanup of dynamically allocated resources.
The operational impact of this vulnerability extends beyond simple memory consumption issues. While individual memory leaks may seem minor, in systems running continuously or with multiple graphics devices, these accumulated leaks can degrade system performance over time. The leak occurs during driver initialization which typically happens at boot time or when the driver module is loaded, meaning that each occurrence contributes to reduced available memory for other system processes and applications. In embedded systems or resource-constrained environments, this could potentially lead to system instability or performance degradation that impacts user experience.
The fix implemented addresses this vulnerability by ensuring proper cleanup of allocated resources through the explicit invocation of fb_destroy_modelist() function call in all error paths following the initial modelist allocation. This remediation aligns with standard software development practices for resource management and follows the principle of least privilege and proper resource cleanup. The solution demonstrates adherence to defensive programming techniques where every allocation has a corresponding deallocation, preventing resource exhaustion scenarios that could affect system stability. From an attack surface perspective, while this particular vulnerability does not introduce direct execution flaws or privilege escalation capabilities, it represents a potential denial-of-service vector through memory exhaustion, which could be leveraged by malicious actors seeking to destabilize systems running affected kernel versions. The fix ensures compliance with ATT&CK framework's resource exhaustion techniques mitigation by preventing improper memory management that could contribute to system instability and performance degradation.