Description
In the Linux kernel, the following vulnerability has been resolved: most: core: fix resource leak in most_register_interface error paths The function most_register_interface() did not correctly release resources if it failed early (before registering the device). In these cases, it returned an error code immediately, leaking the memory allocated for the interface. Fix this by initializing the device early via device_initialize() and calling put_device() on all error paths. The most_register_interface() is expected to call put_device() on error which frees the resources allocated in the caller. The put_device() either calls release_mdev() or dim2_release(), depending on the caller. Switch to using device_add() instead of device_register() to handle the split initialization.
Affected products
linux: linux kernel
References5
- git.kernel.org/stable/c/1f4c9d8a1021281750c6cda126d6f8a40cc24e71 Patch
- git.kernel.org/stable/c/2f483f3817fb0e4209ac5de928778b1da0cc8574 Patch
- git.kernel.org/stable/c/a49028a796d7b94f8e3ab9bd34b18f36be235459 Patch
- git.kernel.org/stable/c/af0b99b2214a10554adb5b868240d23af6e64e71 Patch
- git.kernel.org/stable/c/82f42a13e3d7a07a950ee4fa2d4c74843a3e7ace
Metrics
- CVSS 3.1
-
5.5
MEDIUM
Score source: NVD
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H - EPSS — exploit probability
- 0% percentile: 5 · as of 13 November 2026
- CWE
- CWE-401
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.