CVE-2026-68090debugobjects: Plug race against a concurrent OOM disable
- —Not scoredno CVSS score yet
- 0.18%Exploitation in 30 daysEPSS · top 93% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Linux
- 11 days later
· 11 days later
Published
- 7 days later
· 7 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.18% · top 93% of all CVEs (14 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected b84d435cc228e87951f3bbabf6cc4a5f25d5fb16 – < 2d5e320b7ab9b25229ac4331541964a58b5e1d29
- affected b84d435cc228e87951f3bbabf6cc4a5f25d5fb16 – < 203a965bf2ab43130778d8214fb0c3c8c2d19cdf
- affected b84d435cc228e87951f3bbabf6cc4a5f25d5fb16 – < 23da32e88627e63e0864f59f4c63a2dc0ab851a3
- affected b84d435cc228e87951f3bbabf6cc4a5f25d5fb16 – < d663fbf28b2eebe665bb9cf828d7d528e5a8707e
- affected b84d435cc228e87951f3bbabf6cc4a5f25d5fb16 – < e2e255d07723c330dded8e576ce28a8d23a692ce
- affected b84d435cc228e87951f3bbabf6cc4a5f25d5fb16 – < c00164c9e7fa6145886ad666806cb5347895de5c
- affected b84d435cc228e87951f3bbabf6cc4a5f25d5fb16 – < 1f4f02b336c3be125c8fcf87df73db2e0e028b8b
- affected b84d435cc228e87951f3bbabf6cc4a5f25d5fb16 – < b81dde13cc163450dcb402dcc915ef13ba241e01
- affected 3.3
- unaffected < 3.3
- unaffected 5.10.261 – ≤ 5.10.*
- unaffected 5.15.212 – ≤ 5.15.*
- unaffected 6.1.178 – ≤ 6.1.*
- unaffected 6.6.145 – ≤ 6.6.*
- unaffected 6.12.96 – ≤ 6.12.*
- unaffected 6.18.39 – ≤ 6.18.*
- unaffected 7.1.4 – ≤ 7.1.*
- unaffected 7.2 – ≤ *
References
References8
- https://git.kernel.org/stable/c/2d5e320b7ab9b25229ac4331541964a58b5e1d29 (opens in a new tab)
- https://git.kernel.org/stable/c/203a965bf2ab43130778d8214fb0c3c8c2d19cdf (opens in a new tab)
- https://git.kernel.org/stable/c/23da32e88627e63e0864f59f4c63a2dc0ab851a3 (opens in a new tab)
- https://git.kernel.org/stable/c/d663fbf28b2eebe665bb9cf828d7d528e5a8707e (opens in a new tab)
- https://git.kernel.org/stable/c/e2e255d07723c330dded8e576ce28a8d23a692ce (opens in a new tab)
- https://git.kernel.org/stable/c/c00164c9e7fa6145886ad666806cb5347895de5c (opens in a new tab)
- https://git.kernel.org/stable/c/1f4f02b336c3be125c8fcf87df73db2e0e028b8b (opens in a new tab)
- https://git.kernel.org/stable/c/b81dde13cc163450dcb402dcc915ef13ba241e01 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-55271 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-68090)Record last updated .