CVE-2025-71272
What it is
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.
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of service disruption.
- Exploit odds
- 0.2% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.2% in the next 30 days (EPSS).
- Severity: 5.5 MEDIUM (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.2% · EPSS, next 30 days
- Weakness
- CWE-401
- Record status
- Modified
Affected
- Linux Kernel < 6.12.75
- Linux Kernel < 6.18.16
- Linux Kernel < 6.19.6
Attack profile CVSS 3.1 · 5.5
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2025-71272.md and follow it. Check whether this project is affected by CVE-2025-71272. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/1f4c9d8a1021281750c6cda126d6f8a40cc24e71
- https://git.kernel.org/stable/c/2f483f3817fb0e4209ac5de928778b1da0cc8574
- https://git.kernel.org/stable/c/a49028a796d7b94f8e3ab9bd34b18f36be235459
- https://git.kernel.org/stable/c/af0b99b2214a10554adb5b868240d23af6e64e71
References
- https://git.kernel.org/stable/c/1f4c9d8a1021281750c6cda126d6f8a40cc24e71
- https://git.kernel.org/stable/c/2f483f3817fb0e4209ac5de928778b1da0cc8574
- https://git.kernel.org/stable/c/82f42a13e3d7a07a950ee4fa2d4c74843a3e7ace
- https://git.kernel.org/stable/c/a49028a796d7b94f8e3ab9bd34b18f36be235459
- https://git.kernel.org/stable/c/af0b99b2214a10554adb5b868240d23af6e64e71