CVE-2025-71154: Linux kernel · Memory Leak
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in db2244c580540306d60ce783ed340190720cd429 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 14:18 UTC
Rated by Threat Radar · No CVSS score from NVD or the CNA
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 3% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers cannot reliably automate steps 1–4 of the kill chain
- Technical impact
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2026-06-10.
- Patch
- Available – fixed in db2244c580540306d60ce783ed340190720cd429, a4e2442d3c48355a84463342f397134f149936d7, 151403e903840c9cf06754097b6732c14f26c532 +4
Exploitation evidence
Disclosed: evidence found.
CVE published 23 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
Description
In the Linux kernel, the following vulnerability has been resolved: net: usb: rtl8150: fix memory leak on usb_submit_urb() failure In async_set_registers(), when usb_submit_urb() fails, the allocated async_req structure and URB are not freed, causing a memory leak. The completion callback async_set_reg_cb() is responsible for freeing these allocations, but it is only called after the URB is successfully submitted and completes (successfully or with error). If submission fails, the callback never runs and the memory is leaked. Fix this by freeing both the URB and the request structure in the error path when usb_submit_urb() fails.
References
- git.kernel.org/stable/c/a4e2442d3c48355a84463342f397134f149936d7 (opens in a new tab)
- git.kernel.org/stable/c/2f966186b99550e3c665dbfb87b8314e30acea02 (opens in a new tab)
- git.kernel.org/stable/c/db2244c580540306d60ce783ed340190720cd429 (opens in a new tab)
- git.kernel.org/stable/c/4bd4ea3eb326608ffc296db12c105f92dc2f2190 (opens in a new tab)
- git.kernel.org/stable/c/6492ad6439ff1a479fc94dc6052df3628faed8b6 (opens in a new tab)
- git.kernel.org/stable/c/151403e903840c9cf06754097b6732c14f26c532 (opens in a new tab)
- git.kernel.org/stable/c/12cab1191d9890097171156d06bfa8d31f1e39c8 (opens in a new tab)