CVE-2026-31576 — media: hackrf: fix to not free memory after the device is registered in hackrf_probe()
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+1
- Technical severity (high)+6
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux, Linux Linux Kernel).
- Apply the fixed version or the patch documented under Remediation.
- Search available logs for exploit probes matching the vulnerability class (memory corruption), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ 8bc4a9ed85046c214458c9e82aea75d2f46cfffd and < 87b9685cca91ed715c39ba544715832d26a7f4b4≥ 8bc4a9ed85046c214458c9e82aea75d2f46cfffd and < 131ec9046e1c8af101aebdaec4e8095e05f3312b≥ 8bc4a9ed85046c214458c9e82aea75d2f46cfffd and < 67fd62e3efdc9dce01f76d95a745212f4feb38e6≥ 8bc4a9ed85046c214458c9e82aea75d2f46cfffd and < 45cbaf5c7cdc5386d86377f0daf94a17a007fed0≥ 8bc4a9ed85046c214458c9e82aea75d2f46cfffd and < 98a0a81ce78020c2522e0046f49d200de9778cb9≥ 8bc4a9ed85046c214458c9e82aea75d2f46cfffd and < 07e9e674b6146b1f6fc41b1f54b8968bf2802824≥ 8bc4a9ed85046c214458c9e82aea75d2f46cfffd and < 2145c71a8044362e82e9923f001ba2aeb771b848≥ 8bc4a9ed85046c214458c9e82aea75d2f46cfffd and < fcd1d70792a35c8a97414fe429f48311e41269c2 and 2 more≥ 8bc4a9ed85046c214458c9e82aea75d2f46cfffd and < 3b7da2b4d0fe014eff181ed37e3bf832eb8ed258version 4.4 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
| Linux | Linux Kernel | < 6.6.136≥ 6.7 and < 6.12.83≥ 6.13 and < 6.18.24≥ 6.19 and < 6.19.14≥ 7.0 and < 7.0.1 | Vulnerable | NIST National Vulnerability Database |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 7.8 | CVSS 3.1 | High | 1.8 | 5.9 | nvd@nist.gov via NIST National Vulnerability Database |
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (score shown at the top: nvd@nist.gov) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
EPSS over time FIRST
Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.17%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
- Correlate service crashes/restarts with inbound traffic; repeated crashes may indicate attempts.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · linux/linux
- Record published
- Fix documented
- CVSS changed · 7.8
- Source status changed · → Modified
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
9 on the record
- git.kernel.org/stable/c/2145c71a8044362e82e9923f001ba2aeb771b848
- git.kernel.org/stable/c/3b7da2b4d0fe014eff181ed37e3bf832eb8ed258
- git.kernel.org/stable/c/98a0a81ce78020c2522e0046f49d200de9778cb9
- git.kernel.org/stable/c/45cbaf5c7cdc5386d86377f0daf94a17a007fed0
- git.kernel.org/stable/c/07e9e674b6146b1f6fc41b1f54b8968bf2802824
- git.kernel.org/stable/c/fcd1d70792a35c8a97414fe429f48311e41269c2
- git.kernel.org/stable/c/87b9685cca91ed715c39ba544715832d26a7f4b4
- git.kernel.org/stable/c/131ec9046e1c8af101aebdaec4e8095e05f3312b
- git.kernel.org/stable/c/67fd62e3efdc9dce01f76d95a745212f4feb38e6
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 9h
- Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 9h
- Unknown CVE-2026-98431 RDMA/uverbs: Fix mmap_lock/disassociation_lock circular dependency 1d
- Unknown CVE-2026-98430 RDMA/efa: Keep admin queues alive while IRQ is registered 1d
- Unknown CVE-2026-98429 RDMA/efa: Keep EQ resources alive while IRQ is registered 1d
- Unknown CVE-2026-98428 ALSA: usb: 6fire: Avoid embedded URBs 1d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CISA SSVC assessment.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-31576 is "media: hackrf: fix to not free memory after the device is registered in hackrf_probe()", rated High. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.8 describes technical severity. EPSS 0.17% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.