Vulnerability · Published May 27, 2026 · Assigned by Linux

CVE-2026-45949hwrng: core - use RCU and work_struct to fix race condition

Medium 4.7

In plain English

A medium-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 0% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS NVD)4.7Medium
Exploit odds (30 days)<0.1%top 99.6% of all CVEs
Exploited in the wildNo reportsnot in CISA KEV
Attack toolingNoneno public tooling known

Official description

In the Linux kernel, the following vulnerability has been resolved: hwrng: core - use RCU and work_struct to fix race condition Currently, hwrng_fill is not cleared until the hwrng_fillfn() thread exits. Since hwrng_unregister() reads hwrng_fill outside the rng_mutex lock, a concurrent hwrng_unregister() may call kthread_stop() again on the same task. Additionally, if hwrng_unregister() is called immediately after hwrng_register(), the stopped thread may have never been executed. Thus, hwrng_fill remains dirty even after hwrng_unregister() returns. In this case, subsequent calls to hwrng_register() will fail to start new threads, and hwrng_unregister() will call kthread_stop() on the same freed task. In both cases, a use-after-free occurs: refcount_t: addition on 0; use-after-free. WARNING: ... at lib/refcount.c:25 refcount_warn_saturate+0xec/0x1c0 Call Trace: kthread_stop+0x181/0x360 hwrng_unregister+0x288/0x380 virtrng_remove+0xe3/0x200 This patch fixes the race by protecting the global hwrng_fill pointer inside the rng_mutex lock, so that hwrng_fillfn() thread is stopped only once, and calls to kthread_run() and kthread_stop() are serialized with the lock held. To avoid deadlock in hwrng_fillfn() while being stopped with the lock held, we convert current_rng to RCU, so that get_current_rng() can read current_rng without holding the lock. To remove the lock from put_rng(), we also delay the actual cleanup into a work_struct. Since get_current_rng() no longer returns ERR_PTR values, the IS_ERR() checks are removed from its callers. With hwrng_fill protected by the rng_mutex lock, hwrng_fillfn() can no longer clear hwrng_fill itself. Therefore, if hwrng_fillfn() returns directly after current_rng is dropped, kthread_stop() would be called on a freed task_struct later. To fix this, hwrng_fillfn() calls schedule() now to keep the task alive until being stopped. The kthread_stop() call is also moved from hwrng_unregister() to drop_current_rng(), ensuring kthread_stop() is called on all possible paths where current_rng becomes NULL, so that the thread would not wait forever.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:12linuxno fix listedDEBIAN-CVE-2026-45949
Debian:13linux6.12.85-1DEBIAN-CVE-2026-45949
Debian:14linux6.18.14-1DEBIAN-CVE-2026-45949
Ubuntu:22.04:LTSlinuxno fix listedUBUNTU-CVE-2026-45949
Ubuntu:24.04:LTSlinuxno fix listedUBUNTU-CVE-2026-45949
Ubuntu:25.10linuxno fix listedUBUNTU-CVE-2026-45949
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2026-45949
Ubuntu:22.04:LTSlinux-awsno fix listedUBUNTU-CVE-2026-45949
Ubuntu:24.04:LTSlinux-awsno fix listedUBUNTU-CVE-2026-45949
Ubuntu:25.10linux-awsno fix listedUBUNTU-CVE-2026-45949
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2026-45949
Ubuntu:24.04:LTSlinux-aws-6.14no fix listedUBUNTU-CVE-2026-45949
Ubuntu:24.04:LTSlinux-aws-6.17no fix listedUBUNTU-CVE-2026-45949
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2026-45949
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2026-45949
Ubuntu:22.04:LTSlinux-aws-6.8no fix listedUBUNTU-CVE-2026-45949
Ubuntu:22.04:LTSlinux-azureno fix listedUBUNTU-CVE-2026-45949
Ubuntu:24.04:LTSlinux-azureno fix listedUBUNTU-CVE-2026-45949
Ubuntu:25.10linux-azureno fix listedUBUNTU-CVE-2026-45949
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2026-45949
Ubuntu:24.04:LTSlinux-azure-6.11no fix listedUBUNTU-CVE-2026-45949
Ubuntu:24.04:LTSlinux-azure-6.14no fix listedUBUNTU-CVE-2026-45949
Ubuntu:24.04:LTSlinux-azure-6.17no fix listedUBUNTU-CVE-2026-45949
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2026-45949
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2026-45949
Ubuntu:22.04:LTSlinux-azure-6.8no fix listedUBUNTU-CVE-2026-45949
Ubuntu:22.04:LTSlinux-azure-fdeno fix listedUBUNTU-CVE-2026-45949
Ubuntu:24.04:LTSlinux-azure-fdeno fix listedUBUNTU-CVE-2026-45949
Ubuntu:25.10linux-azure-fdeno fix listedUBUNTU-CVE-2026-45949
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2026-45949
Ubuntu:24.04:LTSlinux-azure-fde-6.14no fix listedUBUNTU-CVE-2026-45949
Ubuntu:24.04:LTSlinux-azure-fde-6.17no fix listedUBUNTU-CVE-2026-45949
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2026-45949
Ubuntu:22.04:LTSlinux-azure-fde-6.8no fix listedUBUNTU-CVE-2026-45949
Ubuntu:24.04:LTSlinux-azure-nvidiano fix listedUBUNTU-CVE-2026-45949
Ubuntu:24.04:LTSlinux-azure-nvidia-6.14no fix listedUBUNTU-CVE-2026-45949
Ubuntu:22.04:LTSlinux-gcpno fix listedUBUNTU-CVE-2026-45949
Ubuntu:24.04:LTSlinux-gcpno fix listedUBUNTU-CVE-2026-45949
Ubuntu:25.10linux-gcpno fix listedUBUNTU-CVE-2026-45949
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2026-45949
Ubuntu:24.04:LTSlinux-gcp-6.11no fix listedUBUNTU-CVE-2026-45949
Ubuntu:24.04:LTSlinux-gcp-6.14no fix listedUBUNTU-CVE-2026-45949
Ubuntu:24.04:LTSlinux-gcp-6.17no fix listedUBUNTU-CVE-2026-45949
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2026-45949
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2026-45949
Ubuntu:22.04:LTSlinux-gcp-6.8no fix listedUBUNTU-CVE-2026-45949
Ubuntu:22.04:LTSlinux-gkeno fix listedUBUNTU-CVE-2026-45949
Ubuntu:24.04:LTSlinux-gkeno fix listedUBUNTU-CVE-2026-45949
Ubuntu:22.04:LTSlinux-gkeopno fix listedUBUNTU-CVE-2026-45949
Ubuntu:24.04:LTSlinux-gkeopno fix listedUBUNTU-CVE-2026-45949
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2026-45949
Ubuntu:24.04:LTSlinux-hwe-6.11no fix listedUBUNTU-CVE-2026-45949
Ubuntu:24.04:LTSlinux-hwe-6.14no fix listedUBUNTU-CVE-2026-45949
Ubuntu:24.04:LTSlinux-hwe-6.17no fix listedUBUNTU-CVE-2026-45949
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2026-45949
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2026-45949
Ubuntu:22.04:LTSlinux-hwe-6.8no fix listedUBUNTU-CVE-2026-45949
Ubuntu:22.04:LTSlinux-ibmno fix listedUBUNTU-CVE-2026-45949
Ubuntu:24.04:LTSlinux-ibmno fix listedUBUNTU-CVE-2026-45949
Ubuntu:22.04:LTSlinux-ibm-6.8no fix listedUBUNTU-CVE-2026-45949
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2026-45949
Ubuntu:22.04:LTSlinux-intel-iotgno fix listedUBUNTU-CVE-2026-45949
Ubuntu:22.04:LTSlinux-kvmno fix listedUBUNTU-CVE-2026-45949
Ubuntu:22.04:LTSlinux-lowlatencyno fix listedUBUNTU-CVE-2026-45949
Ubuntu:24.04:LTSlinux-lowlatencyno fix listedUBUNTU-CVE-2026-45949
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2026-45949
Ubuntu:24.04:LTSlinux-lowlatency-hwe-6.11no fix listedUBUNTU-CVE-2026-45949
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2026-45949
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2026-45949
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.8no fix listedUBUNTU-CVE-2026-45949
Ubuntu:22.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2026-45949
Ubuntu:24.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2026-45949
Ubuntu:24.04:LTSlinux-nvidia-6.11no fix listedUBUNTU-CVE-2026-45949
Ubuntu:24.04:LTSlinux-nvidia-6.17no fix listedUBUNTU-CVE-2026-45949
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2026-45949
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2026-45949
Ubuntu:22.04:LTSlinux-nvidia-6.8no fix listedUBUNTU-CVE-2026-45949
Ubuntu:24.04:LTSlinux-nvidia-lowlatencyno fix listedUBUNTU-CVE-2026-45949
Ubuntu:22.04:LTSlinux-nvidia-tegrano fix listedUBUNTU-CVE-2026-45949
Ubuntu:24.04:LTSlinux-nvidia-tegrano fix listedUBUNTU-CVE-2026-45949
Ubuntu:22.04:LTSlinux-nvidia-tegra-igxno fix listedUBUNTU-CVE-2026-45949
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2026-45949
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2026-45949
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2026-45949
Ubuntu:24.04:LTSlinux-oem-6.11no fix listedUBUNTU-CVE-2026-45949
Ubuntu:24.04:LTSlinux-oem-6.14no fix listedUBUNTU-CVE-2026-45949
Ubuntu:24.04:LTSlinux-oem-6.17no fix listedUBUNTU-CVE-2026-45949
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2026-45949
Ubuntu:24.04:LTSlinux-oem-6.8no fix listedUBUNTU-CVE-2026-45949
Ubuntu:22.04:LTSlinux-oracleno fix listedUBUNTU-CVE-2026-45949
Ubuntu:24.04:LTSlinux-oracleno fix listedUBUNTU-CVE-2026-45949
Ubuntu:25.10linux-oracleno fix listedUBUNTU-CVE-2026-45949
Ubuntu:24.04:LTSlinux-oracle-6.14no fix listedUBUNTU-CVE-2026-45949
Ubuntu:24.04:LTSlinux-oracle-6.17no fix listedUBUNTU-CVE-2026-45949
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2026-45949
Ubuntu:22.04:LTSlinux-oracle-6.8no fix listedUBUNTU-CVE-2026-45949
Ubuntu:22.04:LTSlinux-raspino fix listedUBUNTU-CVE-2026-45949
Ubuntu:24.04:LTSlinux-raspino fix listedUBUNTU-CVE-2026-45949
Ubuntu:25.10linux-raspino fix listedUBUNTU-CVE-2026-45949
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2026-45949
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-45949
Ubuntu:24.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-45949
Ubuntu:25.10linux-realtimeno fix listedUBUNTU-CVE-2026-45949
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-45949
Ubuntu:24.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-45949
Ubuntu:25.10linux-riscvno fix listedUBUNTU-CVE-2026-45949
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2026-45949
Ubuntu:24.04:LTSlinux-riscv-6.14no fix listedUBUNTU-CVE-2026-45949
Ubuntu:24.04:LTSlinux-riscv-6.17no fix listedUBUNTU-CVE-2026-45949
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2026-45949
Ubuntu:22.04:LTSlinux-riscv-6.8no fix listedUBUNTU-CVE-2026-45949
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2026-45949
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2026-45949
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2026-45949
Ubuntu:24.04:LTSlinux-vmwareno fix listedUBUNTU-CVE-2026-45949
Ubuntu:24.04:LTSlinux-xilinxno fix listedUBUNTU-CVE-2026-45949
Ubuntu:22.04:LTSlinux-xilinx-zynqmpno fix listedUBUNTU-CVE-2026-45949

Affected products (as reported)

VendorProductVersions
Linux Linux be4000bc4644d027c519b6361f5ae3bbfc52c347 – before d60bd663b746f17fc01fdc44dd01642594176344be4000bc4644d027c519b6361f5ae3bbfc52c347 – before 1cde96d5d53b9105b48617afbc4682a83db4ff04be4000bc4644d027c519b6361f5ae3bbfc52c347 – before d5b7730f06994499632026c30e38e0317c4569e2be4000bc4644d027c519b6361f5ae3bbfc52c347 – before dcf416eb88eafe1e3c0f920a14bdffd10bc4d259be4000bc4644d027c519b6361f5ae3bbfc52c347 – before ad38f2cdfef9a2f2899c30cad269baec5bfd4a5dbe4000bc4644d027c519b6361f5ae3bbfc52c347 – before cc2f39d6ac48e6e3cb2d6240bc0d6df839dd0828
Linux Linux 3.17

References