Answer in brief
CVE-2025-71272 records a Unknown severity vulnerability in most: core: fix resource leak in most_register_interface error paths. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=723de0f9171eeb49a3ae98cae82ebbbb992b3a7c <82f42a13e3d7a07a950ee4fa2d4c74843a3e7ace || >=723de0f9171eeb49a3ae98cae82ebbbb992b3a7c <a49028a796d7b94f8e3ab9bd34b18f36be235459 || >=723de0f9171eeb49a3ae98cae82ebbbb992b3a7c <af0b99b2214a10554adb5b868240d23af6e64e71 || >=723de0f9171eeb49a3ae98cae82ebbbb992b3a7c <2f483f3817fb0e4209ac5de928778b1da0cc8574 || >=723de0f9171eeb49a3ae98cae82ebbbb992b3a7c <1f4c9d8a1021281750c6cda126d6f8a40cc24e71 | 82f42a13e3d7a07a950ee4fa2d4c74843a3e7ace, a49028a796d7b94f8e3ab9bd34b18f36be235459, af0b99b2214a10554adb5b868240d23af6e64e71, 2f483f3817fb0e4209ac5de928778b1da0cc8574, 1f4c9d8a1021281750c6cda126d6f8a40cc24e71 |
| Linux/Linuxgeneric | 5.6 | Not reported |
Published upstream
May 6, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 21, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 21, 2026
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.
Quoted source text, attributed separately from HOL analysis.