Skip to main content
VulnerabilityPublished Updated

CVE-2025-71272: Linux kernel · most: core: fix resource leak in most_register_interface error paths

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · fixed in af0b99b2214a10554adb5b868240d23af6e64e71 : update Linux kernel when convenient.

Data as of 26 Oct 2026, 14:18 UTC

Severity
Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS
0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in af0b99b2214a10554adb5b868240d23af6e64e71, a49028a796d7b94f8e3ab9bd34b18f36be235459, 82f42a13e3d7a07a950ee4fa2d4c74843a3e7ace +2

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 723de0f9171eeb49a3ae98cae82ebbbb992b3a7c, < af0b99b2214a10554adb5b868240d23af6e64e71
Fixed in
  • af0b99b2214a10554adb5b868240d23af6e64e71
LinuxLinuxAffected
  • ≥ 723de0f9171eeb49a3ae98cae82ebbbb992b3a7c, < a49028a796d7b94f8e3ab9bd34b18f36be235459
Fixed in
  • a49028a796d7b94f8e3ab9bd34b18f36be235459
LinuxLinuxAffected
  • ≥ 723de0f9171eeb49a3ae98cae82ebbbb992b3a7c, < 82f42a13e3d7a07a950ee4fa2d4c74843a3e7ace
Fixed in
  • 82f42a13e3d7a07a950ee4fa2d4c74843a3e7ace
LinuxLinuxAffected
  • ≥ 723de0f9171eeb49a3ae98cae82ebbbb992b3a7c, < 2f483f3817fb0e4209ac5de928778b1da0cc8574
Fixed in
  • 2f483f3817fb0e4209ac5de928778b1da0cc8574
LinuxLinuxAffected
  • ≥ 723de0f9171eeb49a3ae98cae82ebbbb992b3a7c, < 1f4c9d8a1021281750c6cda126d6f8a40cc24e71
Fixed in
  • 1f4c9d8a1021281750c6cda126d6f8a40cc24e71
LinuxLinuxAffected
  • =5.6
Fixed in–

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.

References

Community reviews

Loading reviews…