CVE-2026-24675
Use-After-Free Vulnerability in FreeRDP libusb_udev_select_interface
Publication date: 2026-02-09
Last updated on: 2026-02-10
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| freerdp | freerdp | to 3.22.0 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-416 | The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in FreeRDP, a free implementation of the Remote Desktop Protocol. Before version 3.22.0, the function urb_select_interface could free the device's MS configuration on error, but subsequent code would still attempt to access (dereference) this freed memory. This leads to a use-after-free condition in the libusb_udev_select_interface function, which can cause unexpected behavior or crashes. The issue was fixed in version 3.22.0.
How can this vulnerability impact me? :
A use-after-free vulnerability can lead to memory corruption, which attackers might exploit to execute arbitrary code, cause application crashes, or trigger denial of service conditions. Since this vulnerability occurs in FreeRDP, it could potentially allow remote attackers to compromise systems using vulnerable versions of FreeRDP by exploiting this flaw.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
The vulnerability in FreeRDP is fixed in version 3.22.0. To mitigate this vulnerability, you should upgrade FreeRDP to version 3.22.0 or later.