Vulnerability · Published Apr 24, 2026 · Assigned by Linux
CVE-2026-31576media: hackrf: fix to not free memory after the device is registered in hackrf_probe()
High 7.8
In plain English
A high-severity security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.1% (higher than 2% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.
Official 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.
Affected packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian:12 | linux | 6.1.176-1 | DEBIAN-CVE-2026-31576 |
| Debian:13 | linux | 6.12.85-1 | DEBIAN-CVE-2026-31576 |
| Debian:14 | linux | 6.19.14-1 | DEBIAN-CVE-2026-31576 |
| Ubuntu:22.04:LTS | linux | 5.15.0-186.196 | UBUNTU-CVE-2026-31576 |
| Ubuntu:24.04:LTS | linux | 6.8.0-136.136 | UBUNTU-CVE-2026-31576 |
| Ubuntu:25.10 | linux | no fix listed | UBUNTU-CVE-2026-31576 |
| Ubuntu:26.04:LTS | linux | 7.0.0-27.27 | USN-8488-1 |
| Ubuntu:26.04:LTS | linux | 7.0.0-27.27 | UBUNTU-CVE-2026-31576 |
| Ubuntu:22.04:LTS | linux-allwinner-5.19 | no fix listed | UBUNTU-CVE-2026-31576 |
| Ubuntu:22.04:LTS | linux-aws | 5.15.0-1112.119 | UBUNTU-CVE-2026-31576 |
| Ubuntu:24.04:LTS | linux-aws | 6.8.0-1061.64 | UBUNTU-CVE-2026-31576 |
| Ubuntu:25.10 | linux-aws | no fix listed | UBUNTU-CVE-2026-31576 |
| Ubuntu:26.04:LTS | linux-aws | 7.0.0-1008.8 | UBUNTU-CVE-2026-31576 |
| Ubuntu:26.04:LTS | linux-aws | 7.0.0-1008.8 | USN-8488-1 |
| Ubuntu:22.04:LTS | linux-aws-5.19 | no fix listed | UBUNTU-CVE-2026-31576 |
| Ubuntu:24.04:LTS | linux-aws-6.14 | no fix listed | UBUNTU-CVE-2026-31576 |
| Ubuntu:24.04:LTS | linux-aws-6.17 | no fix listed | UBUNTU-CVE-2026-31576 |
| Ubuntu:22.04:LTS | linux-aws-6.2 | no fix listed | UBUNTU-CVE-2026-31576 |
| Ubuntu:22.04:LTS | linux-aws-6.5 | no fix listed | UBUNTU-CVE-2026-31576 |
| Ubuntu:22.04:LTS | linux-aws-6.8 | 6.8.0-1061.64~22.04.1 | UBUNTU-CVE-2026-31576 |
| Ubuntu:22.04:LTS | linux-azure | 5.15.0-1117.126 | UBUNTU-CVE-2026-31576 |
| Ubuntu:24.04:LTS | linux-azure | 6.8.0-1063.71 | UBUNTU-CVE-2026-31576 |
| Ubuntu:25.10 | linux-azure | no fix listed | UBUNTU-CVE-2026-31576 |
| Ubuntu:26.04:LTS | linux-azure | 7.0.0-1010.10 | UBUNTU-CVE-2026-31576 |
| Ubuntu:26.04:LTS | linux-azure | 7.0.0-1010.10 | USN-8603-1 |
| Ubuntu:22.04:LTS | linux-azure-5.19 | no fix listed | UBUNTU-CVE-2026-31576 |
| Ubuntu:24.04:LTS | linux-azure-6.11 | no fix listed | UBUNTU-CVE-2026-31576 |
| Ubuntu:24.04:LTS | linux-azure-6.14 | no fix listed | UBUNTU-CVE-2026-31576 |
| Ubuntu:24.04:LTS | linux-azure-6.17 | no fix listed | UBUNTU-CVE-2026-31576 |
| Ubuntu:22.04:LTS | linux-azure-6.2 | no fix listed | UBUNTU-CVE-2026-31576 |
| Ubuntu:22.04:LTS | linux-azure-6.5 | no fix listed | UBUNTU-CVE-2026-31576 |
| Ubuntu:22.04:LTS | linux-azure-6.8 | 6.8.0-1063.71~22.04.1 | UBUNTU-CVE-2026-31576 |
| Ubuntu:22.04:LTS | linux-azure-fde | 5.15.0-1117.126 | UBUNTU-CVE-2026-31576 |
| Ubuntu:24.04:LTS | linux-azure-fde | 6.8.0-1062.69 | UBUNTU-CVE-2026-31576 |
| Ubuntu:25.10 | linux-azure-fde | no fix listed | UBUNTU-CVE-2026-31576 |
| Ubuntu:26.04:LTS | linux-azure-fde | 7.0.0-1009.9 | USN-8603-1 |
| Ubuntu:26.04:LTS | linux-azure-fde | 7.0.0-1009.9 | UBUNTU-CVE-2026-31576 |
| Ubuntu:22.04:LTS | linux-azure-fde-5.19 | no fix listed | UBUNTU-CVE-2026-31576 |
| Ubuntu:24.04:LTS | linux-azure-fde-6.14 | no fix listed | UBUNTU-CVE-2026-31576 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.2 | no fix listed | UBUNTU-CVE-2026-31576 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.8 | 6.8.0-1062.69~22.04.1 | UBUNTU-CVE-2026-31576 |
| Ubuntu:24.04:LTS | linux-azure-nvidia | no fix listed | UBUNTU-CVE-2026-31576 |
| Ubuntu:24.04:LTS | linux-azure-nvidia-6.14 | no fix listed | UBUNTU-CVE-2026-31576 |
| Ubuntu:22.04:LTS | linux-gcp | 5.15.0-1112.122 | UBUNTU-CVE-2026-31576 |
| Ubuntu:24.04:LTS | linux-gcp | 6.8.0-1064.72 | UBUNTU-CVE-2026-31576 |
| Ubuntu:25.10 | linux-gcp | no fix listed | UBUNTU-CVE-2026-31576 |
| Ubuntu:26.04:LTS | linux-gcp | 7.0.0-1007.7 | UBUNTU-CVE-2026-31576 |
| Ubuntu:26.04:LTS | linux-gcp | 7.0.0-1007.7 | USN-8488-1 |
| Ubuntu:22.04:LTS | linux-gcp-5.19 | no fix listed | UBUNTU-CVE-2026-31576 |
| Ubuntu:24.04:LTS | linux-gcp-6.11 | no fix listed | UBUNTU-CVE-2026-31576 |
| Ubuntu:24.04:LTS | linux-gcp-6.14 | no fix listed | UBUNTU-CVE-2026-31576 |
| Ubuntu:24.04:LTS | linux-gcp-6.17 | no fix listed | UBUNTU-CVE-2026-31576 |
| Ubuntu:22.04:LTS | linux-gcp-6.2 | no fix listed | UBUNTU-CVE-2026-31576 |
| Ubuntu:22.04:LTS | linux-gcp-6.5 | no fix listed | UBUNTU-CVE-2026-31576 |
| Ubuntu:22.04:LTS | linux-gcp-6.8 | 6.8.0-1064.72~22.04.1 | UBUNTU-CVE-2026-31576 |
| Ubuntu:22.04:LTS | linux-gke | 5.15.0-1108.114 | UBUNTU-CVE-2026-31576 |
| Ubuntu:24.04:LTS | linux-gke | 6.8.0-1059.67 | UBUNTU-CVE-2026-31576 |
| Ubuntu:22.04:LTS | linux-gkeop | 5.15.0-1095.103 | UBUNTU-CVE-2026-31576 |
| Ubuntu:24.04:LTS | linux-gkeop | 6.8.0-1046.50 | UBUNTU-CVE-2026-31576 |
| Ubuntu:22.04:LTS | linux-hwe-5.19 | no fix listed | UBUNTU-CVE-2026-31576 |
| Ubuntu:24.04:LTS | linux-hwe-6.11 | no fix listed | UBUNTU-CVE-2026-31576 |
| Ubuntu:24.04:LTS | linux-hwe-6.14 | no fix listed | UBUNTU-CVE-2026-31576 |
| Ubuntu:24.04:LTS | linux-hwe-6.17 | no fix listed | UBUNTU-CVE-2026-31576 |
| Ubuntu:22.04:LTS | linux-hwe-6.2 | no fix listed | UBUNTU-CVE-2026-31576 |
| Ubuntu:22.04:LTS | linux-hwe-6.5 | no fix listed | UBUNTU-CVE-2026-31576 |
| Ubuntu:22.04:LTS | linux-hwe-6.8 | 6.8.0-136.136~22.04.1 | UBUNTU-CVE-2026-31576 |
| Ubuntu:24.04:LTS | linux-hwe-7.0 | 7.0.0-28.28~24.04.1 | USN-8569-1 |
| Ubuntu:24.04:LTS | linux-hwe-7.0 | 7.0.0-28.28~24.04.1 | UBUNTU-CVE-2026-31576 |
| Ubuntu:22.04:LTS | linux-ibm | 5.15.0-1106.110 | UBUNTU-CVE-2026-31576 |
| Ubuntu:24.04:LTS | linux-ibm | 6.8.0-1061.62 | UBUNTU-CVE-2026-31576 |
| Ubuntu:26.04:LTS | linux-ibm | 7.0.0-1009.9 | USN-8488-1 |
| Ubuntu:26.04:LTS | linux-ibm | 7.0.0-1009.9 | UBUNTU-CVE-2026-31576 |
| Ubuntu:22.04:LTS | linux-ibm-6.8 | 6.8.0-1061.62~22.04.1 | UBUNTU-CVE-2026-31576 |
| Ubuntu:22.04:LTS | linux-intel-iot-realtime | no fix listed | UBUNTU-CVE-2026-31576 |
| Ubuntu:22.04:LTS | linux-intel-iotg | 5.15.0-1107.113 | UBUNTU-CVE-2026-31576 |
| Ubuntu:22.04:LTS | linux-kvm | 5.15.0-1104.109 | UBUNTU-CVE-2026-31576 |
| Ubuntu:22.04:LTS | linux-lowlatency | 5.15.0-184.194 | UBUNTU-CVE-2026-31576 |
| Ubuntu:24.04:LTS | linux-lowlatency | 6.8.0-136.136.2 | UBUNTU-CVE-2026-31576 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-5.19 | no fix listed | UBUNTU-CVE-2026-31576 |
| Ubuntu:24.04:LTS | linux-lowlatency-hwe-6.11 | no fix listed | UBUNTU-CVE-2026-31576 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.2 | no fix listed | UBUNTU-CVE-2026-31576 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.5 | no fix listed | UBUNTU-CVE-2026-31576 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.8 | 6.8.0-136.136.2~22.04.1 | UBUNTU-CVE-2026-31576 |
| Ubuntu:22.04:LTS | linux-nvidia | 5.15.0-1107.108 | UBUNTU-CVE-2026-31576 |
| Ubuntu:24.04:LTS | linux-nvidia | 6.8.0-1059.62 | UBUNTU-CVE-2026-31576 |
| Ubuntu:26.04:LTS | linux-nvidia | 7.0.0-1013.13 | USN-8507-1 |
| Ubuntu:26.04:LTS | linux-nvidia | 7.0.0-1013.13 | UBUNTU-CVE-2026-31576 |
| Ubuntu:24.04:LTS | linux-nvidia-6.11 | no fix listed | UBUNTU-CVE-2026-31576 |
| Ubuntu:24.04:LTS | linux-nvidia-6.17 | no fix listed | UBUNTU-CVE-2026-31576 |
| Ubuntu:22.04:LTS | linux-nvidia-6.2 | no fix listed | UBUNTU-CVE-2026-31576 |
| Ubuntu:22.04:LTS | linux-nvidia-6.5 | no fix listed | UBUNTU-CVE-2026-31576 |
| Ubuntu:22.04:LTS | linux-nvidia-6.8 | 6.8.0-1059.62~22.04.1 | UBUNTU-CVE-2026-31576 |
| Ubuntu:24.04:LTS | linux-nvidia-lowlatency | 6.8.0-1059.62.1 | UBUNTU-CVE-2026-31576 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra | 5.15.0-1064.66 | UBUNTU-CVE-2026-31576 |
| Ubuntu:24.04:LTS | linux-nvidia-tegra | 6.8.0-1030.31 | UBUNTU-CVE-2026-31576 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra-igx | 5.15.0-1053.53 | UBUNTU-CVE-2026-31576 |
| Ubuntu:22.04:LTS | linux-oem-5.17 | no fix listed | UBUNTU-CVE-2026-31576 |
| Ubuntu:22.04:LTS | linux-oem-6.0 | no fix listed | UBUNTU-CVE-2026-31576 |
| Ubuntu:22.04:LTS | linux-oem-6.1 | no fix listed | UBUNTU-CVE-2026-31576 |
| Ubuntu:24.04:LTS | linux-oem-6.11 | no fix listed | UBUNTU-CVE-2026-31576 |
| Ubuntu:24.04:LTS | linux-oem-6.14 | no fix listed | UBUNTU-CVE-2026-31576 |
| Ubuntu:24.04:LTS | linux-oem-6.17 | no fix listed | UBUNTU-CVE-2026-31576 |
| Ubuntu:22.04:LTS | linux-oem-6.5 | no fix listed | UBUNTU-CVE-2026-31576 |
| Ubuntu:24.04:LTS | linux-oem-6.8 | no fix listed | UBUNTU-CVE-2026-31576 |
| Ubuntu:22.04:LTS | linux-oracle | 5.15.0-1109.115 | UBUNTU-CVE-2026-31576 |
| Ubuntu:24.04:LTS | linux-oracle | 6.8.0-1058.61 | UBUNTU-CVE-2026-31576 |
| Ubuntu:25.10 | linux-oracle | no fix listed | UBUNTU-CVE-2026-31576 |
| Ubuntu:26.04:LTS | linux-oracle | 7.0.0-1007.7 | USN-8488-1 |
| Ubuntu:26.04:LTS | linux-oracle | 7.0.0-1007.7 | UBUNTU-CVE-2026-31576 |
| Ubuntu:24.04:LTS | linux-oracle-6.14 | no fix listed | UBUNTU-CVE-2026-31576 |
| Ubuntu:24.04:LTS | linux-oracle-6.17 | no fix listed | UBUNTU-CVE-2026-31576 |
| Ubuntu:22.04:LTS | linux-oracle-6.5 | no fix listed | UBUNTU-CVE-2026-31576 |
| Ubuntu:22.04:LTS | linux-oracle-6.8 | 6.8.0-1058.61~22.04.1 | UBUNTU-CVE-2026-31576 |
| Ubuntu:22.04:LTS | linux-raspi | 5.15.0-1106.109 | UBUNTU-CVE-2026-31576 |
| Ubuntu:24.04:LTS | linux-raspi | 6.8.0-1061.65 | UBUNTU-CVE-2026-31576 |
| Ubuntu:25.10 | linux-raspi | no fix listed | UBUNTU-CVE-2026-31576 |
| Ubuntu:26.04:LTS | linux-raspi | 7.0.0-1014.14 | USN-8488-2 |
| Ubuntu:26.04:LTS | linux-raspi | 7.0.0-1014.14 | UBUNTU-CVE-2026-31576 |
| Ubuntu:24.04:LTS | linux-raspi-realtime | no fix listed | UBUNTU-CVE-2026-31576 |
| Ubuntu:22.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2026-31576 |
| Ubuntu:24.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2026-31576 |
| Ubuntu:25.10 | linux-realtime | no fix listed | UBUNTU-CVE-2026-31576 |
| Ubuntu:26.04:LTS | linux-realtime | 7.0.0-27.27.1 | UBUNTU-CVE-2026-31576 |
| Ubuntu:26.04:LTS | linux-realtime | 7.0.0-27.27.1 | USN-8488-1 |
| Ubuntu:22.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2026-31576 |
| Ubuntu:24.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2026-31576 |
| Ubuntu:25.10 | linux-riscv | no fix listed | UBUNTU-CVE-2026-31576 |
| Ubuntu:26.04:LTS | linux-riscv | 7.0.0-27.27.1 | UBUNTU-CVE-2026-31576 |
| Ubuntu:22.04:LTS | linux-riscv-5.19 | no fix listed | UBUNTU-CVE-2026-31576 |
| Ubuntu:24.04:LTS | linux-riscv-6.14 | no fix listed | UBUNTU-CVE-2026-31576 |
| Ubuntu:24.04:LTS | linux-riscv-6.17 | no fix listed | UBUNTU-CVE-2026-31576 |
| Ubuntu:22.04:LTS | linux-riscv-6.5 | no fix listed | UBUNTU-CVE-2026-31576 |
| Ubuntu:22.04:LTS | linux-riscv-6.8 | 6.8.0-136.136~22.04.3 | UBUNTU-CVE-2026-31576 |
| Ubuntu:22.04:LTS | linux-starfive-5.19 | no fix listed | UBUNTU-CVE-2026-31576 |
| Ubuntu:22.04:LTS | linux-starfive-6.2 | no fix listed | UBUNTU-CVE-2026-31576 |
| Ubuntu:22.04:LTS | linux-starfive-6.5 | no fix listed | UBUNTU-CVE-2026-31576 |
| Ubuntu:24.04:LTS | linux-vmware | 6.8.0-1008.8 | UBUNTU-CVE-2026-31576 |
| Ubuntu:24.04:LTS | linux-xilinx | 6.8.0-1033.34 | UBUNTU-CVE-2026-31576 |
| Ubuntu:22.04:LTS | linux-xilinx-zynqmp | 5.15.0-1075.79 | UBUNTU-CVE-2026-31576 |
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 8bc4a9ed85046c214458c9e82aea75d2f46cfffd – before 87b9685cca91ed715c39ba544715832d26a7f4b48bc4a9ed85046c214458c9e82aea75d2f46cfffd – before 131ec9046e1c8af101aebdaec4e8095e05f3312b8bc4a9ed85046c214458c9e82aea75d2f46cfffd – before 67fd62e3efdc9dce01f76d95a745212f4feb38e68bc4a9ed85046c214458c9e82aea75d2f46cfffd – before 45cbaf5c7cdc5386d86377f0daf94a17a007fed08bc4a9ed85046c214458c9e82aea75d2f46cfffd – before 98a0a81ce78020c2522e0046f49d200de9778cb98bc4a9ed85046c214458c9e82aea75d2f46cfffd – before 07e9e674b6146b1f6fc41b1f54b8968bf28028248bc4a9ed85046c214458c9e82aea75d2f46cfffd – before 2145c71a8044362e82e9923f001ba2aeb771b8488bc4a9ed85046c214458c9e82aea75d2f46cfffd – before fcd1d70792a35c8a97414fe429f48311e41269c2 |
| Linux | Linux | 4.4 |
References
- https://git.kernel.org/stable/c/87b9685cca91ed715c39ba544715832d26a7f4b4
- https://git.kernel.org/stable/c/131ec9046e1c8af101aebdaec4e8095e05f3312b
- https://git.kernel.org/stable/c/67fd62e3efdc9dce01f76d95a745212f4feb38e6
- https://git.kernel.org/stable/c/45cbaf5c7cdc5386d86377f0daf94a17a007fed0
- https://git.kernel.org/stable/c/98a0a81ce78020c2522e0046f49d200de9778cb9
- https://git.kernel.org/stable/c/07e9e674b6146b1f6fc41b1f54b8968bf2802824
- https://git.kernel.org/stable/c/2145c71a8044362e82e9923f001ba2aeb771b848
- https://git.kernel.org/stable/c/fcd1d70792a35c8a97414fe429f48311e41269c2
- https://git.kernel.org/stable/c/3b7da2b4d0fe014eff181ed37e3bf832eb8ed258