CVE-2021-47239

net: usb: fix possible use-after-free in smsc75xx_bind

HIGH

7.8

CVSS Score

Published: May 21, 2024 at 02:19 PM UTC

Updated: June 17, 2026 at 04:16 AM UTC

1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

HIGH7.8

Exploit prediction

EPSS 0.2%

SSVC

No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: net: usb: fix possible use-after-free in smsc75xx_bind The commit 46a8b29c6306 ("net: usb: fix memory leak in smsc75xx_bind") fails to clean up the work scheduled in smsc75xx_reset-> smsc75xx_set_multicast, which leads to use-after-free if the work is scheduled to start after the deallocation. In addition, this patch also removes a dangling pointer - dev->data[0]. This patch calls cancel_work_sync to cancel the scheduled work and set the dangling pointer to NULL.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Linux Kernel · Linux

95%

4.14.235 ≤ v < 4.14.2384.19.193 ≤ v < 4.19.1964.4.271 ≤ v < 4.4.2744.9.271 ≤ v < 4.9.2745.10.42 ≤ v < 5.10.465.12.9 ≤ v < 5.12.135.4.124 ≤ v < 5.4.128200dbfcad8011e50c3cec269ed7b980836eeb1fa22c840596af0c09068b6cf948616e6496e59e07f4.14.235 4.19.193 4.4.271 4.9.27146a8b29c6306d8bbfd92b614ef65a47c900d8e705.10.42 5.12.9 5.4.124635ac38b36255d3cfb8312cf7c471334f4d537e070c886ac93f87ae7214a0c69151a28a8075dd95b9e6a3eccb28779710cbbafc4f4258d92509c6d079e6b8c1ff9d997e1fa16cbd2d60739adf6dc1bbcb95fb96e6339e34694dd578fb6bde3575b01af17

Vendor states this is fixed in 14616c372a7be01a2fb8c56c9d8debd232b9e43d (fixed)

Vendor states this is fixed in 2fc8300c9cfa5167fcb5b1a2a07db6f53e82f59b (fixed)

Vendor states this is fixed in 4252bf6c2b245f47011098113d405ffad6ad5d5b (fixed)

Vendor states this is fixed in 56b786d86694e079d8aad9b314e015cd4ac02a3d (fixed)

Vendor states this is fixed in 570a52cf3e01d19f7fd1a251dfc52b0cd86c13cb (fixed)

Vendor states this is fixed in 64160d1741a3de5204d1a822e058e0b4cc526504 (fixed)

Vendor states this is fixed in 7cc8b2e05fcea6edd022d26e82091d781af8fd9b (fixed)

Vendor states this is fixed in c4e3be2e7742863e454ce31faf8fd0109c00050b (fixed)

Affected range stops below 4.14.238, so it looks safe — our inference, not a vendor statement

Affected range stops below 4.19.196, so it looks safe — our inference, not a vendor statement

Affected range stops below 4.4.274, so it looks safe — our inference, not a vendor statement

Affected range stops below 4.9.274, so it looks safe — our inference, not a vendor statement

Affected range stops below 5.10.46, so it looks safe — our inference, not a vendor statement

Affected range stops below 5.12.13, so it looks safe — our inference, not a vendor statement

Affected range stops below 5.4.128, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references