Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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

Noroxi assessment

Priority: Monitor (action score 31/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.12% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 07e9e674b6146b1f6fc41b1f54b8968bf2802824, 131ec9046e1c8af101aebdaec4e8095e05f3312b, 2145c71a8044362e82e9923f001ba2aeb771b848.

Low priority for now. Upgrade to Linux Linux 07e9e674b6146b1f6fc41b1f54b8968bf2802824, 131ec9046e1c8af101aebdaec4e8095e05f3312b, 2145c71a8044362e82e9923f001ba2aeb771b848 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

HighCVSS 7.8 · v3.1—No exploit Fix available
Published
Apr 24, 2026
Updated
Jun 17, 2026
EPSS
0.1% · 2th percentile

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-31576

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernelbefore 6.6.136
  • linux linux kernel6.7 and later · before 6.12.83
  • linux linux kernel6.13 and later · before 6.18.24
  • linux linux kernel6.19 and later · before 6.19.14
  • linux linux kernel7.0 and later · before 7.0.1

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 4.4affected
    • 8bc4a9ed85046c214458c9e82aea75d2f46cfffd and later · before 87b9685cca91ed715c39ba544715832d26a7f4b4affected · git
    • 8bc4a9ed85046c214458c9e82aea75d2f46cfffd and later · before 131ec9046e1c8af101aebdaec4e8095e05f3312baffected · git
    • 8bc4a9ed85046c214458c9e82aea75d2f46cfffd and later · before 67fd62e3efdc9dce01f76d95a745212f4feb38e6affected · git
    • 8bc4a9ed85046c214458c9e82aea75d2f46cfffd and later · before 45cbaf5c7cdc5386d86377f0daf94a17a007fed0affected · git
    • 8bc4a9ed85046c214458c9e82aea75d2f46cfffd and later · before 98a0a81ce78020c2522e0046f49d200de9778cb9affected · git
    • 8bc4a9ed85046c214458c9e82aea75d2f46cfffd and later · before 07e9e674b6146b1f6fc41b1f54b8968bf2802824affected · git
    • 8bc4a9ed85046c214458c9e82aea75d2f46cfffd and later · before 2145c71a8044362e82e9923f001ba2aeb771b848affected · git
    • 8bc4a9ed85046c214458c9e82aea75d2f46cfffd and later · before fcd1d70792a35c8a97414fe429f48311e41269c2affected · git
    • 8bc4a9ed85046c214458c9e82aea75d2f46cfffd and later · before 3b7da2b4d0fe014eff181ed37e3bf832eb8ed258affected · git

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.176-16.1.176-1
Debian:13linuxbefore 6.12.85-16.12.85-1
Debian:14linuxbefore 6.19.14-16.19.14-1
openSUSE:Tumbleweedkernel-sourcebefore 7.0.3-1.17.0.3-1.1

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2026-31567Apr 24, 2026 · PM: sleep: Drop spurious WARN_ON() from pm_restore_gfp_mask()
    22Monitor
  • ← EarlierCVE-2026-31569Apr 24, 2026 · LoongArch: KVM: Handle the case that EIOINTC's coremap is empty
    29Monitor
  • Later →CVE-2026-31577Apr 24, 2026 · nilfs2: fix NULL i_assoc_inode dereference in nilfs_mdt_save_to_shadow_map
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux07e9e674b6146b1f6fc41b1f54b8968bf2802824Vendor (CNA)
Linux Linux131ec9046e1c8af101aebdaec4e8095e05f3312bVendor (CNA)
Linux Linux2145c71a8044362e82e9923f001ba2aeb771b848Vendor (CNA)
Linux Linux3b7da2b4d0fe014eff181ed37e3bf832eb8ed258Vendor (CNA)
Linux Linux45cbaf5c7cdc5386d86377f0daf94a17a007fed0Vendor (CNA)
Linux Linux67fd62e3efdc9dce01f76d95a745212f4feb38e6Vendor (CNA)
Linux Linux87b9685cca91ed715c39ba544715832d26a7f4b4Vendor (CNA)
Linux Linux98a0a81ce78020c2522e0046f49d200de9778cb9Vendor (CNA)
Linux Linuxfcd1d70792a35c8a97414fe429f48311e41269c2Vendor (CNA)
debian:linux6.1.176-1 · Debian:12Package registry (OSV)
opensuse:kernel-source7.0.3-1.1 · openSUSE:TumbleweedPackage registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

c
free(dev->buf);/* ... another thread is still running ... */process(dev->buf);

Fixed

c
lock(&dev->lock);free(dev->buf);dev->buf = NULL;unlock(&dev->lock);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records