Vulnerability · Published Sep 11, 2026 · Assigned by Linux
CVE-2026-89675nfsd: fix UAF in async copy cancel and shutdown
Critical 9.8
In plain English
A critical-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.4% (higher than 39% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.
Official description
In the Linux kernel, the following vulnerability has been resolved: nfsd: fix UAF in async copy cancel and shutdown An async copy could be freed or used after free while a teardown caller (OFFLOAD_CANCEL, nfsd4_shutdown_copy, nfsd4_cancel_copy_by_sb) raced the copy kthread: - find_async_copy() bumped copy->refcount but left the copy on clp->async_copies, so the reaper's cleanup_async_copy() could run release_copy_files() concurrently with a cancel/shutdown caller. Both put and NULL nf_src/nf_dst without a common lock, double-putting the nfsd_file and freeing it early. - nfsd4_do_async_copy() set NFSD4_COPY_F_STOPPED before its final uses of the copy (nfsd_update_cmtime_attr() on copy->nf_dst, nfsd4_send_cb_offload()). nfsd4_stop_copy() treats a set STOPPED bit as "kthread done, skip kthread_stop()", so a teardown caller ran release_copy_files() -- which puts and NULLs nf_dst -- while the kthread still dereferenced it (NULL/UAF). - copy->copy_task was never pinned. The one-shot kthread self-reaps on return, so kthread_stop()'s get_task_struct() could touch a freed task_struct. - co_cb is embedded in the copy, but nfsd4_send_cb_offload() held a reference only on the client, so a concurrent teardown could free the copy while the CB_OFFLOAD callback was in flight. Fix the teardown lifetime as a whole: - find_async_copy() unlinks the copy (clear cp_clp, list_del_init) under async_lock; the cancel, shutdown, and sb-cancel paths drop the list-membership reference via nfs4_put_copy() after nfsd4_stop_copy(). Drop the now-redundant list_del fixup from cleanup_async_copy(). - Because unlinking hides the copy from the reaper, its cleanup_async_copy() can no longer remove the copy's s2s_cp_stateids entry; the cancel/shutdown/sb-cancel paths now call nfs4_free_copy_state() themselves (while cp_clp is still valid) so the entry does not dangle at freed memory for the laundromat and manage_cpntf_state() to dereference. - Give the kthread its own reference, taken in nfsd4_copy() before wake_up_process() and dropped at the end of nfsd4_do_async_copy(); call wake_up_process() before list_add(). - Pin the task_struct with get_task_struct() in nfsd4_copy(), released in nfs4_put_copy(), so kthread_stop() is safe whenever the kthread exits. Set NFSD4_COPY_F_STOPPED only in nfsd4_stop_copy(), which now always kthread_stop()s before release_copy_files(); completion is still reported via NFSD4_COPY_F_COMPLETED, so nfsd4_has_active_async_copies() is unaffected. Each teardown caller removes the copy from clp->async_copies first, so kthread_stop() runs exactly once. - Take a copy reference in nfsd4_send_cb_offload(), dropped in nfsd4_cb_offload_release(). The kthread still holds its own reference there, so the refcount_inc() cannot race the final free. - Read cp_clp with smp_load_acquire() to pair with the unordered set_bit()/clear_bit() writers (Documentation/atomic_bitops.rst).
Affected packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| AlmaLinux:10 | kernel | 6.12.0-211.64.1.el10_2 | ALSA-2026:77690 |
| AlmaLinux:10 | kernel-64k | 6.12.0-211.64.1.el10_2 | ALSA-2026:77690 |
| AlmaLinux:10 | kernel-64k-core | 6.12.0-211.64.1.el10_2 | ALSA-2026:77690 |
| AlmaLinux:10 | kernel-64k-debug | 6.12.0-211.64.1.el10_2 | ALSA-2026:77690 |
| AlmaLinux:10 | kernel-64k-debug-core | 6.12.0-211.64.1.el10_2 | ALSA-2026:77690 |
| AlmaLinux:10 | kernel-64k-debug-devel | 6.12.0-211.64.1.el10_2 | ALSA-2026:77690 |
| AlmaLinux:10 | kernel-64k-debug-devel-matched | 6.12.0-211.64.1.el10_2 | ALSA-2026:77690 |
| AlmaLinux:10 | kernel-64k-debug-modules | 6.12.0-211.64.1.el10_2 | ALSA-2026:77690 |
| AlmaLinux:10 | kernel-64k-debug-modules-core | 6.12.0-211.64.1.el10_2 | ALSA-2026:77690 |
| AlmaLinux:10 | kernel-64k-debug-modules-extra | 6.12.0-211.64.1.el10_2 | ALSA-2026:77690 |
| AlmaLinux:10 | kernel-64k-devel | 6.12.0-211.64.1.el10_2 | ALSA-2026:77690 |
| AlmaLinux:10 | kernel-64k-devel-matched | 6.12.0-211.64.1.el10_2 | ALSA-2026:77690 |
| AlmaLinux:10 | kernel-64k-modules | 6.12.0-211.64.1.el10_2 | ALSA-2026:77690 |
| AlmaLinux:10 | kernel-64k-modules-core | 6.12.0-211.64.1.el10_2 | ALSA-2026:77690 |
| AlmaLinux:10 | kernel-64k-modules-extra | 6.12.0-211.64.1.el10_2 | ALSA-2026:77690 |
| AlmaLinux:10 | kernel-abi-stablelists | 6.12.0-211.64.1.el10_2 | ALSA-2026:77690 |
| AlmaLinux:10 | kernel-core | 6.12.0-211.64.1.el10_2 | ALSA-2026:77690 |
| AlmaLinux:10 | kernel-cross-headers | 6.12.0-211.64.1.el10_2 | ALSA-2026:77690 |
| AlmaLinux:10 | kernel-debug | 6.12.0-211.64.1.el10_2 | ALSA-2026:77690 |
| AlmaLinux:10 | kernel-debug-core | 6.12.0-211.64.1.el10_2 | ALSA-2026:77690 |
| AlmaLinux:10 | kernel-debug-devel | 6.12.0-211.64.1.el10_2 | ALSA-2026:77690 |
| AlmaLinux:10 | kernel-debug-devel-matched | 6.12.0-211.64.1.el10_2 | ALSA-2026:77690 |
| AlmaLinux:10 | kernel-debug-modules | 6.12.0-211.64.1.el10_2 | ALSA-2026:77690 |
| AlmaLinux:10 | kernel-debug-modules-core | 6.12.0-211.64.1.el10_2 | ALSA-2026:77690 |
| AlmaLinux:10 | kernel-debug-modules-extra | 6.12.0-211.64.1.el10_2 | ALSA-2026:77690 |
| AlmaLinux:10 | kernel-debug-uki-virt | 6.12.0-211.64.1.el10_2 | ALSA-2026:77690 |
| AlmaLinux:10 | kernel-devel | 6.12.0-211.64.1.el10_2 | ALSA-2026:77690 |
| AlmaLinux:10 | kernel-devel-matched | 6.12.0-211.64.1.el10_2 | ALSA-2026:77690 |
| AlmaLinux:10 | kernel-doc | 6.12.0-211.64.1.el10_2 | ALSA-2026:77690 |
| AlmaLinux:10 | kernel-headers | 6.12.0-211.64.1.el10_2 | ALSA-2026:77690 |
| AlmaLinux:10 | kernel-modules | 6.12.0-211.64.1.el10_2 | ALSA-2026:77690 |
| AlmaLinux:10 | kernel-modules-core | 6.12.0-211.64.1.el10_2 | ALSA-2026:77690 |
| AlmaLinux:10 | kernel-modules-extra | 6.12.0-211.64.1.el10_2 | ALSA-2026:77690 |
| AlmaLinux:10 | kernel-modules-extra-matched | 6.12.0-211.64.1.el10_2 | ALSA-2026:77690 |
| AlmaLinux:10 | kernel-rt | 6.12.0-211.64.1.el10_2 | ALSA-2026:77690 |
| AlmaLinux:10 | kernel-rt-64k | 6.12.0-211.64.1.el10_2 | ALSA-2026:77690 |
| AlmaLinux:10 | kernel-rt-64k-core | 6.12.0-211.64.1.el10_2 | ALSA-2026:77690 |
| AlmaLinux:10 | kernel-rt-64k-debug | 6.12.0-211.64.1.el10_2 | ALSA-2026:77690 |
| AlmaLinux:10 | kernel-rt-64k-debug-core | 6.12.0-211.64.1.el10_2 | ALSA-2026:77690 |
| AlmaLinux:10 | kernel-rt-64k-debug-devel | 6.12.0-211.64.1.el10_2 | ALSA-2026:77690 |
| AlmaLinux:10 | kernel-rt-64k-debug-modules | 6.12.0-211.64.1.el10_2 | ALSA-2026:77690 |
| AlmaLinux:10 | kernel-rt-64k-debug-modules-core | 6.12.0-211.64.1.el10_2 | ALSA-2026:77690 |
| AlmaLinux:10 | kernel-rt-64k-debug-modules-extra | 6.12.0-211.64.1.el10_2 | ALSA-2026:77690 |
| AlmaLinux:10 | kernel-rt-64k-devel | 6.12.0-211.64.1.el10_2 | ALSA-2026:77690 |
| AlmaLinux:10 | kernel-rt-64k-modules | 6.12.0-211.64.1.el10_2 | ALSA-2026:77690 |
| AlmaLinux:10 | kernel-rt-64k-modules-core | 6.12.0-211.64.1.el10_2 | ALSA-2026:77690 |
| AlmaLinux:10 | kernel-rt-64k-modules-extra | 6.12.0-211.64.1.el10_2 | ALSA-2026:77690 |
| AlmaLinux:10 | kernel-rt-core | 6.12.0-211.64.1.el10_2 | ALSA-2026:77690 |
| AlmaLinux:10 | kernel-rt-debug | 6.12.0-211.64.1.el10_2 | ALSA-2026:77690 |
| AlmaLinux:10 | kernel-rt-debug-core | 6.12.0-211.64.1.el10_2 | ALSA-2026:77690 |
| AlmaLinux:10 | kernel-rt-debug-devel | 6.12.0-211.64.1.el10_2 | ALSA-2026:77690 |
| AlmaLinux:10 | kernel-rt-debug-modules | 6.12.0-211.64.1.el10_2 | ALSA-2026:77690 |
| AlmaLinux:10 | kernel-rt-debug-modules-core | 6.12.0-211.64.1.el10_2 | ALSA-2026:77690 |
| AlmaLinux:10 | kernel-rt-debug-modules-extra | 6.12.0-211.64.1.el10_2 | ALSA-2026:77690 |
| AlmaLinux:10 | kernel-rt-devel | 6.12.0-211.64.1.el10_2 | ALSA-2026:77690 |
| AlmaLinux:10 | kernel-rt-modules | 6.12.0-211.64.1.el10_2 | ALSA-2026:77690 |
| AlmaLinux:10 | kernel-rt-modules-core | 6.12.0-211.64.1.el10_2 | ALSA-2026:77690 |
| AlmaLinux:10 | kernel-rt-modules-extra | 6.12.0-211.64.1.el10_2 | ALSA-2026:77690 |
| AlmaLinux:10 | kernel-tools | 6.12.0-211.64.1.el10_2 | ALSA-2026:77690 |
| AlmaLinux:10 | kernel-tools-libs | 6.12.0-211.64.1.el10_2 | ALSA-2026:77690 |
| AlmaLinux:10 | kernel-tools-libs-devel | 6.12.0-211.64.1.el10_2 | ALSA-2026:77690 |
| AlmaLinux:10 | kernel-uki-virt | 6.12.0-211.64.1.el10_2 | ALSA-2026:77690 |
| AlmaLinux:10 | kernel-uki-virt-addons | 6.12.0-211.64.1.el10_2 | ALSA-2026:77690 |
| AlmaLinux:10 | kernel-zfcpdump | 6.12.0-211.64.1.el10_2 | ALSA-2026:77690 |
| AlmaLinux:10 | kernel-zfcpdump-core | 6.12.0-211.64.1.el10_2 | ALSA-2026:77690 |
| AlmaLinux:10 | kernel-zfcpdump-devel | 6.12.0-211.64.1.el10_2 | ALSA-2026:77690 |
| AlmaLinux:10 | kernel-zfcpdump-devel-matched | 6.12.0-211.64.1.el10_2 | ALSA-2026:77690 |
| AlmaLinux:10 | kernel-zfcpdump-modules | 6.12.0-211.64.1.el10_2 | ALSA-2026:77690 |
| AlmaLinux:10 | kernel-zfcpdump-modules-core | 6.12.0-211.64.1.el10_2 | ALSA-2026:77690 |
| AlmaLinux:10 | kernel-zfcpdump-modules-extra | 6.12.0-211.64.1.el10_2 | ALSA-2026:77690 |
| AlmaLinux:10 | libperf | 6.12.0-211.64.1.el10_2 | ALSA-2026:77690 |
| AlmaLinux:10 | perf | 6.12.0-211.64.1.el10_2 | ALSA-2026:77690 |
| AlmaLinux:10 | python3-perf | 6.12.0-211.64.1.el10_2 | ALSA-2026:77690 |
| AlmaLinux:10 | rtla | 6.12.0-211.64.1.el10_2 | ALSA-2026:77690 |
| AlmaLinux:10 | rv | 6.12.0-211.64.1.el10_2 | ALSA-2026:77690 |
| Debian:12 | linux | no fix listed | DEBIAN-CVE-2026-89675 |
| Debian:13 | linux | no fix listed | DEBIAN-CVE-2026-89675 |
| Debian:14 | linux | 7.2.6-1 | DEBIAN-CVE-2026-89675 |
| Rocky Linux:10 | kernel | 0:6.12.0-211.64.1.el10_2 | RLSA-2026:77690 |
| Ubuntu:22.04:LTS | linux | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:24.04:LTS | linux | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:26.04:LTS | linux | 7.0.0-42.42 | UBUNTU-CVE-2026-89675 |
| Ubuntu:22.04:LTS | linux-allwinner-5.19 | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:22.04:LTS | linux-aws | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:24.04:LTS | linux-aws | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:26.04:LTS | linux-aws | 7.0.0-1016.17 | UBUNTU-CVE-2026-89675 |
| Ubuntu:22.04:LTS | linux-aws-5.19 | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:24.04:LTS | linux-aws-6.14 | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:24.04:LTS | linux-aws-6.17 | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:22.04:LTS | linux-aws-6.2 | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:22.04:LTS | linux-aws-6.5 | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:22.04:LTS | linux-aws-6.8 | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:24.04:LTS | linux-aws-7.0 | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:22.04:LTS | linux-azure | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:24.04:LTS | linux-azure | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:26.04:LTS | linux-azure | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:22.04:LTS | linux-azure-5.19 | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:24.04:LTS | linux-azure-6.11 | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:24.04:LTS | linux-azure-6.14 | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:24.04:LTS | linux-azure-6.17 | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:22.04:LTS | linux-azure-6.2 | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:22.04:LTS | linux-azure-6.5 | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:22.04:LTS | linux-azure-6.8 | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:24.04:LTS | linux-azure-7.0 | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:22.04:LTS | linux-azure-fde | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:24.04:LTS | linux-azure-fde | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:26.04:LTS | linux-azure-fde | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:22.04:LTS | linux-azure-fde-5.19 | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:24.04:LTS | linux-azure-fde-6.14 | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:24.04:LTS | linux-azure-fde-6.17 | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.2 | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.8 | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:24.04:LTS | linux-azure-fde-7.0 | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:24.04:LTS | linux-azure-nvidia | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:24.04:LTS | linux-azure-nvidia-6.14 | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:22.04:LTS | linux-gcp | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:24.04:LTS | linux-gcp | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:26.04:LTS | linux-gcp | 7.0.0-1016.18 | UBUNTU-CVE-2026-89675 |
| Ubuntu:22.04:LTS | linux-gcp-5.19 | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:24.04:LTS | linux-gcp-6.11 | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:24.04:LTS | linux-gcp-6.14 | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:24.04:LTS | linux-gcp-6.17 | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:22.04:LTS | linux-gcp-6.2 | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:22.04:LTS | linux-gcp-6.5 | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:22.04:LTS | linux-gcp-6.8 | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:24.04:LTS | linux-gcp-7.0 | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:22.04:LTS | linux-gke | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:24.04:LTS | linux-gke | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:26.04:LTS | linux-gke | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:22.04:LTS | linux-gkeop | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:24.04:LTS | linux-gkeop | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:22.04:LTS | linux-hwe-5.19 | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:24.04:LTS | linux-hwe-6.11 | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:24.04:LTS | linux-hwe-6.14 | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:24.04:LTS | linux-hwe-6.17 | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:22.04:LTS | linux-hwe-6.2 | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:22.04:LTS | linux-hwe-6.5 | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:22.04:LTS | linux-hwe-6.8 | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:24.04:LTS | linux-hwe-7.0 | 7.0.0-42.42~24.04.1 | UBUNTU-CVE-2026-89675 |
| Ubuntu:22.04:LTS | linux-ibm | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:24.04:LTS | linux-ibm | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:26.04:LTS | linux-ibm | 7.0.0-1017.17 | UBUNTU-CVE-2026-89675 |
| Ubuntu:22.04:LTS | linux-ibm-6.8 | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:22.04:LTS | linux-intel-iot-realtime | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:22.04:LTS | linux-intel-iotg | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:22.04:LTS | linux-kvm | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:22.04:LTS | linux-lowlatency | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:24.04:LTS | linux-lowlatency | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-5.19 | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:24.04:LTS | linux-lowlatency-hwe-6.11 | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.2 | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.5 | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.8 | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:22.04:LTS | linux-nvidia | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:24.04:LTS | linux-nvidia | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:26.04:LTS | linux-nvidia | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:24.04:LTS | linux-nvidia-6.11 | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:24.04:LTS | linux-nvidia-6.17 | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:22.04:LTS | linux-nvidia-6.2 | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:22.04:LTS | linux-nvidia-6.5 | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:22.04:LTS | linux-nvidia-6.8 | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:24.04:LTS | linux-nvidia-7.0 | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:26.04:LTS | linux-nvidia-bos | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:24.04:LTS | linux-nvidia-lowlatency | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:24.04:LTS | linux-nvidia-tegra | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra-igx | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:22.04:LTS | linux-oem-5.17 | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:22.04:LTS | linux-oem-6.0 | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:22.04:LTS | linux-oem-6.1 | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:24.04:LTS | linux-oem-6.11 | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:24.04:LTS | linux-oem-6.14 | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:24.04:LTS | linux-oem-6.17 | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:22.04:LTS | linux-oem-6.5 | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:24.04:LTS | linux-oem-6.8 | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:26.04:LTS | linux-oem-7.0 | 7.0.0-1017.17 | UBUNTU-CVE-2026-89675 |
| Ubuntu:22.04:LTS | linux-oracle | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:24.04:LTS | linux-oracle | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:26.04:LTS | linux-oracle | 7.0.0-1015.16 | UBUNTU-CVE-2026-89675 |
| Ubuntu:24.04:LTS | linux-oracle-6.14 | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:24.04:LTS | linux-oracle-6.17 | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:22.04:LTS | linux-oracle-6.5 | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:22.04:LTS | linux-oracle-6.8 | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:24.04:LTS | linux-oracle-7.0 | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:22.04:LTS | linux-raspi | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:24.04:LTS | linux-raspi | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:26.04:LTS | linux-raspi | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:24.04:LTS | linux-raspi-realtime | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:22.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:24.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:26.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:22.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:24.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:26.04:LTS | linux-riscv | 7.0.0-42.42.1 | UBUNTU-CVE-2026-89675 |
| Ubuntu:22.04:LTS | linux-riscv-5.19 | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:24.04:LTS | linux-riscv-6.14 | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:24.04:LTS | linux-riscv-6.17 | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:22.04:LTS | linux-riscv-6.5 | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:22.04:LTS | linux-riscv-6.8 | no fix listed | UBUNTU-CVE-2026-89675 |
| Ubuntu:24.04:LTS | linux-riscv-7.0 | 7.0.0-42.42.1~24.04.1 | UBUNTU-CVE-2026-89675 |
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | e0639dc5805a9d4faaa2c07ad98fa853b9529dd3 – before 9031493ef7369d5c59c4bacc96f0c85965f09a98e0639dc5805a9d4faaa2c07ad98fa853b9529dd3 – before a385cf5e016b748babf94cc664e43a26e17db117e0639dc5805a9d4faaa2c07ad98fa853b9529dd3 – before 62c0f6eaf050bb9284c1f9cac6ed1770092e6b95 |
| Linux | Linux | 4.20 |