Microsoft · media: hackrf: fix to not free memory after the device is registered in hackrf_probe()
Affects MicrosoftSource GCVE Database
Not known to be exploited.
Data as of 27 Oct 2026, 00:09 UTC
Rated by Threat Radar · No CVSS score from NVD or the CNA
Exploitation evidence
Disclosed: evidence found.
CVE published 2 Apr 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
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Microsoft Security Response Center Microsoft | Affected
| Fixed in– |
Description
This vulnerability involves a flaw in the hackrf device driver where memory is freed after the device is registered in the hackrf_probe() function. The issue affects specific versions 2.0 and 3.0 of the Microsoft product. No CVSS score or detailed impact information is provided, and there is no indication of exploitation in the wild or available patches.