Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-31576media: hackrf: fix to not free memory after the device is registered in hackrf_probe()

Description

In the Linux kernel, the following vulnerability has been resolved: media: hackrf: fix to not free memory after the device is registered in hackrf_probe() In hackrf driver, the following race condition occurs: ``` CPU0 CPU1 hackrf_probe() kzalloc(); // alloc hackrf_dev .... v4l2_device_register(); .... fd = sys_open("/path/to/dev"); // open hackrf fd .... v4l2_device_unregister(); .... kfree(); // free hackrf_dev .... sys_ioctl(fd, ...); v4l2_ioctl(); video_is_registered() // UAF!! .... sys_close(fd); v4l2_release() // UAF!! hackrf_video_release() kfree(); // DFB!! ``` When a V4L2 or video device is unregistered, the device node is removed so new open() calls are blocked. However, file descriptors that are already open-and any in-flight I/O-do not terminate immediately; they remain valid until the last reference is dropped and the driver's release() is invoked. Therefore, freeing device memory on the error path after hackrf_probe() has registered dev it will lead to a race to use-after-free vuln, since those already-open handles haven't been released yet. And since release() free memory too, race to use-after-free and double-free vuln occur. To prevent this, if device is registered from probe(), it should be modified to free memory only through release() rather than calling kfree() directly.

Timeline

  1. ID reserved

    By Linux

  2. · 46 days later

    Published

  3. · 51 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-31576, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.13% · top 98% of all CVEs (17 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected 8bc4a9ed85046c214458c9e82aea75d2f46cfffd – < 87b9685cca91ed715c39ba544715832d26a7f4b4
    • affected 8bc4a9ed85046c214458c9e82aea75d2f46cfffd – < 131ec9046e1c8af101aebdaec4e8095e05f3312b
    • affected 8bc4a9ed85046c214458c9e82aea75d2f46cfffd – < 67fd62e3efdc9dce01f76d95a745212f4feb38e6
    • affected 8bc4a9ed85046c214458c9e82aea75d2f46cfffd – < 45cbaf5c7cdc5386d86377f0daf94a17a007fed0
    • affected 8bc4a9ed85046c214458c9e82aea75d2f46cfffd – < 98a0a81ce78020c2522e0046f49d200de9778cb9
    • affected 8bc4a9ed85046c214458c9e82aea75d2f46cfffd – < 07e9e674b6146b1f6fc41b1f54b8968bf2802824
    • affected 8bc4a9ed85046c214458c9e82aea75d2f46cfffd – < 2145c71a8044362e82e9923f001ba2aeb771b848
    • affected 8bc4a9ed85046c214458c9e82aea75d2f46cfffd – < fcd1d70792a35c8a97414fe429f48311e41269c2
    • affected 8bc4a9ed85046c214458c9e82aea75d2f46cfffd – < 3b7da2b4d0fe014eff181ed37e3bf832eb8ed258
  • Linux · Linux

    • affected 4.4
    • unaffected < 4.4
    • unaffected 5.10.258 – ≤ 5.10.*
    • unaffected 5.15.209 – ≤ 5.15.*
    • unaffected 6.1.175 – ≤ 6.1.*
    • unaffected 6.6.136 – ≤ 6.6.*
    • unaffected 6.12.83 – ≤ 6.12.*
    • unaffected 6.18.24 – ≤ 6.18.*
    • unaffected 6.19.14 – ≤ 6.19.*
    • unaffected 7.0.1 – ≤ 7.0.*
    • unaffected 7.1 – ≤ *

References

References9

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-31576 badge
[![CVE-2026-31576](https://cveledger.app/badge/CVE-2026-31576.svg)](https://cveledger.app/cve/CVE-2026-31576)

Record last updated .