Vulnerability · Published Aug 10, 2026 · Assigned by Linux

CVE-2026-68090debugobjects: Plug race against a concurrent OOM disable

Unrated

In plain English

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

Severity (CVSS )–Not rated
Exploit odds (30 days)0.2%top 92.7% 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: debugobjects: Plug race against a concurrent OOM disable syzbot reported a puzzling splat: WARNING: kernel/time/hrtimer.c:443 at stub_timer+0xa/0x20 stub_timer() is installed as timer callback function in hrtimer_fixup_assert_init(), which is invoked when debug_object_assert_init() can't find a shadow object. In that case debug objects emits a warning about it before invoking the fixup. Though the provided console log lacks this warning and instead has the following a few seconds before the splat: ODEBUG: Out of memory. ODEBUG disabled So the object was looked up in debug_object_assert_init() and the lookup failed due a concurrent out of memory situation which disabled debug objects and freed the shadow objects: debug_object_assert_init() if (!debug_objects_enabled) return; obj = alloc(); if (!obj) { // Out of memory debug_objects_enabled = false; free_objects(); obj = lookup_or_alloc(); // The lookup failed because the other side // removed the objects, so this returns // an error code as the object in question // is not statically initialized if (!IS_ERR_OR_NULL(obj)) return; if (!obj) { debug_oom(); return; } print(...) if (!debug_objects_enabled) return; fixup(...) The debug object splat is skipped because debug_objects_enabled is false, but the fixup callback is invoked unconditionally, which makes the timer disfunctional. This is only a problem in debug_object_assert_init() and debug_object_activate() as both have to handle statically initialized objects and therefore must handle the error pointer return case gracefully. All other places only handle the found/not found case and the NULL pointer return is a signal for OOM. Otherwise they get a valid shadow object. Plug the hole by checking whether debug objects are still enabled before invoking the print and fixup function in those two places.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:12linux6.1.180-1DEBIAN-CVE-2026-68090
Debian:13linux6.12.96-1DEBIAN-CVE-2026-68090
Debian:14linux7.1.4-1DEBIAN-CVE-2026-68090
Ubuntu:22.04:LTSlinux5.15.0-198.208UBUNTU-CVE-2026-68090
Ubuntu:24.04:LTSlinux6.8.0-147.147UBUNTU-CVE-2026-68090
Ubuntu:26.04:LTSlinux7.0.0-31.31UBUNTU-CVE-2026-68090
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2026-68090
Ubuntu:22.04:LTSlinux-aws5.15.0-1117.124UBUNTU-CVE-2026-68090
Ubuntu:24.04:LTSlinux-aws6.8.0-1067.70UBUNTU-CVE-2026-68090
Ubuntu:26.04:LTSlinux-aws7.0.0-1012.12UBUNTU-CVE-2026-68090
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2026-68090
Ubuntu:24.04:LTSlinux-aws-6.14no fix listedUBUNTU-CVE-2026-68090
Ubuntu:24.04:LTSlinux-aws-6.17no fix listedUBUNTU-CVE-2026-68090
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2026-68090
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2026-68090
Ubuntu:22.04:LTSlinux-aws-6.8no fix listedUBUNTU-CVE-2026-68090
Ubuntu:24.04:LTSlinux-aws-7.07.0.0-1012.12~24.04.1UBUNTU-CVE-2026-68090
Ubuntu:22.04:LTSlinux-azure5.15.0-1123.132UBUNTU-CVE-2026-68090
Ubuntu:24.04:LTSlinux-azure6.8.0-1071.79UBUNTU-CVE-2026-68090
Ubuntu:26.04:LTSlinux-azure7.0.0-1014.14UBUNTU-CVE-2026-68090
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2026-68090
Ubuntu:24.04:LTSlinux-azure-6.11no fix listedUBUNTU-CVE-2026-68090
Ubuntu:24.04:LTSlinux-azure-6.14no fix listedUBUNTU-CVE-2026-68090
Ubuntu:24.04:LTSlinux-azure-6.17no fix listedUBUNTU-CVE-2026-68090
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2026-68090
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2026-68090
Ubuntu:22.04:LTSlinux-azure-6.8no fix listedUBUNTU-CVE-2026-68090
Ubuntu:24.04:LTSlinux-azure-7.07.0.0-1014.14~24.04.1UBUNTU-CVE-2026-68090
Ubuntu:22.04:LTSlinux-azure-fde5.15.0-1122.131UBUNTU-CVE-2026-68090
Ubuntu:24.04:LTSlinux-azure-fde6.8.0-1069.76UBUNTU-CVE-2026-68090
Ubuntu:26.04:LTSlinux-azure-fde7.0.0-1013.13UBUNTU-CVE-2026-68090
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2026-68090
Ubuntu:24.04:LTSlinux-azure-fde-6.14no fix listedUBUNTU-CVE-2026-68090
Ubuntu:24.04:LTSlinux-azure-fde-6.17no fix listedUBUNTU-CVE-2026-68090
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2026-68090
Ubuntu:22.04:LTSlinux-azure-fde-6.8no fix listedUBUNTU-CVE-2026-68090
Ubuntu:24.04:LTSlinux-azure-fde-7.07.0.0-1013.13~24.04.1UBUNTU-CVE-2026-68090
Ubuntu:24.04:LTSlinux-azure-nvidiano fix listedUBUNTU-CVE-2026-68090
Ubuntu:24.04:LTSlinux-azure-nvidia-6.14no fix listedUBUNTU-CVE-2026-68090
Ubuntu:22.04:LTSlinux-gcp5.15.0-1118.128UBUNTU-CVE-2026-68090
Ubuntu:24.04:LTSlinux-gcp6.8.0-1071.79UBUNTU-CVE-2026-68090
Ubuntu:26.04:LTSlinux-gcp7.0.0-1011.11UBUNTU-CVE-2026-68090
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2026-68090
Ubuntu:24.04:LTSlinux-gcp-6.11no fix listedUBUNTU-CVE-2026-68090
Ubuntu:24.04:LTSlinux-gcp-6.14no fix listedUBUNTU-CVE-2026-68090
Ubuntu:24.04:LTSlinux-gcp-6.17no fix listedUBUNTU-CVE-2026-68090
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2026-68090
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2026-68090
Ubuntu:22.04:LTSlinux-gcp-6.8no fix listedUBUNTU-CVE-2026-68090
Ubuntu:24.04:LTSlinux-gcp-7.07.0.0-1011.11~24.04.1UBUNTU-CVE-2026-68090
Ubuntu:22.04:LTSlinux-gke5.15.0-1113.119UBUNTU-CVE-2026-68090
Ubuntu:24.04:LTSlinux-gke6.8.0-1066.74UBUNTU-CVE-2026-68090
Ubuntu:26.04:LTSlinux-gke7.0.0-1006.7UBUNTU-CVE-2026-68090
Ubuntu:22.04:LTSlinux-gkeop5.15.0-1100.108UBUNTU-CVE-2026-68090
Ubuntu:24.04:LTSlinux-gkeop6.8.0-1052.56UBUNTU-CVE-2026-68090
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2026-68090
Ubuntu:24.04:LTSlinux-hwe-6.11no fix listedUBUNTU-CVE-2026-68090
Ubuntu:24.04:LTSlinux-hwe-6.14no fix listedUBUNTU-CVE-2026-68090
Ubuntu:24.04:LTSlinux-hwe-6.17no fix listedUBUNTU-CVE-2026-68090
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2026-68090
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2026-68090
Ubuntu:22.04:LTSlinux-hwe-6.8no fix listedUBUNTU-CVE-2026-68090
Ubuntu:24.04:LTSlinux-hwe-7.07.0.0-31.31~24.04.1UBUNTU-CVE-2026-68090
Ubuntu:22.04:LTSlinux-ibm5.15.0-1111.115UBUNTU-CVE-2026-68090
Ubuntu:24.04:LTSlinux-ibm6.8.0-1067.68UBUNTU-CVE-2026-68090
Ubuntu:26.04:LTSlinux-ibm7.0.0-1013.13UBUNTU-CVE-2026-68090
Ubuntu:22.04:LTSlinux-ibm-6.8no fix listedUBUNTU-CVE-2026-68090
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2026-68090
Ubuntu:22.04:LTSlinux-intel-iotg5.15.0-1112.118UBUNTU-CVE-2026-68090
Ubuntu:22.04:LTSlinux-kvm5.15.0-1109.114UBUNTU-CVE-2026-68090
Ubuntu:22.04:LTSlinux-lowlatency5.15.0-195.205UBUNTU-CVE-2026-68090
Ubuntu:24.04:LTSlinux-lowlatency6.8.0-147.147.1UBUNTU-CVE-2026-68090
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2026-68090
Ubuntu:24.04:LTSlinux-lowlatency-hwe-6.11no fix listedUBUNTU-CVE-2026-68090
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2026-68090
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2026-68090
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.8no fix listedUBUNTU-CVE-2026-68090
Ubuntu:22.04:LTSlinux-nvidia5.15.0-1112.113UBUNTU-CVE-2026-68090
Ubuntu:24.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2026-68090
Ubuntu:26.04:LTSlinux-nvidia7.0.0-1018.18UBUNTU-CVE-2026-68090
Ubuntu:24.04:LTSlinux-nvidia-6.11no fix listedUBUNTU-CVE-2026-68090
Ubuntu:24.04:LTSlinux-nvidia-6.17no fix listedUBUNTU-CVE-2026-68090
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2026-68090
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2026-68090
Ubuntu:22.04:LTSlinux-nvidia-6.8no fix listedUBUNTU-CVE-2026-68090
Ubuntu:24.04:LTSlinux-nvidia-7.07.0.0-1018.18~24.04.1UBUNTU-CVE-2026-68090
Ubuntu:26.04:LTSlinux-nvidia-bos7.0.0-2018.18UBUNTU-CVE-2026-68090
Ubuntu:24.04:LTSlinux-nvidia-lowlatencyno fix listedUBUNTU-CVE-2026-68090
Ubuntu:22.04:LTSlinux-nvidia-tegra5.15.0-1070.72UBUNTU-CVE-2026-68090
Ubuntu:24.04:LTSlinux-nvidia-tegrano fix listedUBUNTU-CVE-2026-68090
Ubuntu:22.04:LTSlinux-nvidia-tegra-igx5.15.0-1059.59UBUNTU-CVE-2026-68090
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2026-68090
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2026-68090
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2026-68090
Ubuntu:24.04:LTSlinux-oem-6.11no fix listedUBUNTU-CVE-2026-68090
Ubuntu:24.04:LTSlinux-oem-6.14no fix listedUBUNTU-CVE-2026-68090
Ubuntu:24.04:LTSlinux-oem-6.17no fix listedUBUNTU-CVE-2026-68090
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2026-68090
Ubuntu:24.04:LTSlinux-oem-6.8no fix listedUBUNTU-CVE-2026-68090
Ubuntu:26.04:LTSlinux-oem-7.07.0.0-1013.13UBUNTU-CVE-2026-68090
Ubuntu:22.04:LTSlinux-oracle5.15.0-1114.120UBUNTU-CVE-2026-68090
Ubuntu:24.04:LTSlinux-oracle6.8.0-1064.67UBUNTU-CVE-2026-68090
Ubuntu:26.04:LTSlinux-oracle7.0.0-1011.11UBUNTU-CVE-2026-68090
Ubuntu:24.04:LTSlinux-oracle-6.14no fix listedUBUNTU-CVE-2026-68090
Ubuntu:24.04:LTSlinux-oracle-6.17no fix listedUBUNTU-CVE-2026-68090
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2026-68090
Ubuntu:22.04:LTSlinux-oracle-6.8no fix listedUBUNTU-CVE-2026-68090
Ubuntu:24.04:LTSlinux-oracle-7.07.0.0-1011.11~24.04.1UBUNTU-CVE-2026-68090
Ubuntu:22.04:LTSlinux-raspino fix listedUBUNTU-CVE-2026-68090
Ubuntu:24.04:LTSlinux-raspino fix listedUBUNTU-CVE-2026-68090
Ubuntu:26.04:LTSlinux-raspi7.0.0-1019.19UBUNTU-CVE-2026-68090
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2026-68090
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-68090
Ubuntu:24.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-68090
Ubuntu:26.04:LTSlinux-realtime7.0.0-31.31.1UBUNTU-CVE-2026-68090
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-68090
Ubuntu:24.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-68090
Ubuntu:26.04:LTSlinux-riscv7.0.0-31.31.1UBUNTU-CVE-2026-68090
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2026-68090
Ubuntu:24.04:LTSlinux-riscv-6.14no fix listedUBUNTU-CVE-2026-68090
Ubuntu:24.04:LTSlinux-riscv-6.17no fix listedUBUNTU-CVE-2026-68090
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2026-68090
Ubuntu:22.04:LTSlinux-riscv-6.8no fix listedUBUNTU-CVE-2026-68090
Ubuntu:24.04:LTSlinux-riscv-7.07.0.0-31.31.1~24.04.1UBUNTU-CVE-2026-68090
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2026-68090
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2026-68090
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2026-68090
Ubuntu:24.04:LTSlinux-vmware6.8.0-1008.8UBUNTU-CVE-2026-68090
Ubuntu:24.04:LTSlinux-xilinxno fix listedUBUNTU-CVE-2026-68090
Ubuntu:22.04:LTSlinux-xilinx-zynqmp5.15.0-1080.84UBUNTU-CVE-2026-68090

Affected products (as reported)

VendorProductVersions
Linux Linux b84d435cc228e87951f3bbabf6cc4a5f25d5fb16 – before 2d5e320b7ab9b25229ac4331541964a58b5e1d29b84d435cc228e87951f3bbabf6cc4a5f25d5fb16 – before 203a965bf2ab43130778d8214fb0c3c8c2d19cdfb84d435cc228e87951f3bbabf6cc4a5f25d5fb16 – before 23da32e88627e63e0864f59f4c63a2dc0ab851a3b84d435cc228e87951f3bbabf6cc4a5f25d5fb16 – before d663fbf28b2eebe665bb9cf828d7d528e5a8707eb84d435cc228e87951f3bbabf6cc4a5f25d5fb16 – before e2e255d07723c330dded8e576ce28a8d23a692ceb84d435cc228e87951f3bbabf6cc4a5f25d5fb16 – before c00164c9e7fa6145886ad666806cb5347895de5cb84d435cc228e87951f3bbabf6cc4a5f25d5fb16 – before 1f4f02b336c3be125c8fcf87df73db2e0e028b8bb84d435cc228e87951f3bbabf6cc4a5f25d5fb16 – before b81dde13cc163450dcb402dcc915ef13ba241e01
Linux Linux 3.3

References