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.
Published: 2026-08-10
Score: 5.5 Medium
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

A race condition occurs in the Linux kernel debug objects subsystem when an out‑of-memory event disables the debug objects feature while a timer callback is still in flight. In this scenario the callback runs unconditionally against a pointer that has been cleared, causing a kernel crash. The crash manifests only when debug objects are enabled and a concurrent OOM occurs; if triggered it can stop the system from responding, leading to a denial of service.

Affected Systems

All Linux kernel implementations that have not incorporated the commit that guards against this race. The CVE provides no explicit version list, so any kernel version before the patch is potentially affected.

Risk and Exploitability

The EPSS score is < 1% and the CVSS score of 5.5 indicates medium severity. Exploitation requires an internal race condition that occurs during a concurrent out‑of-memory event while debug objects are enabled; thus it is a local or privileged scenario with a narrow attack window. No public exploits have been reported, but because a kernel crash can be triggered, the impact is high. Given the complexity of reproducing the race, the overall risk is regarded as moderate.

Generated by OpenCVE AI on August 13, 2026 at 10:37 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Apply a kernel update that includes the commit adding null‑check guards before invoking print and fixup functions in debug_object_assert_init() and debug_object_activate()
  • If immediate update is not possible, disable the CONFIG_DEBUG_OBJECTS feature in the kernel configuration to eliminate the race trigger
  • Ensure no boot parameters enable debug objects; remove any debug_objects boot parameter usage from startup scripts

Generated by OpenCVE AI on August 13, 2026 at 10:37 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Thu, 13 Aug 2026 09:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-469

Wed, 12 Aug 2026 00:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-367
References
Metrics threat_severity

None

cvssV3_1

{'score': 5.5, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H'}

threat_severity

Low


Tue, 11 Aug 2026 03:30:00 +0000

Type Values Removed Values Added
First Time appeared Linux kernel
Vendors & Products Linux kernel

Mon, 10 Aug 2026 20:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-469

Mon, 10 Aug 2026 12:00:00 +0000

Type Values Removed Values Added
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.
Title debugobjects: Plug race against a concurrent OOM disable
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Kernel Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-08-17T04:58:38.177Z

Reserved: 2026-07-30T09:28:09.367Z

Link: CVE-2026-68090

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-08-10T12:17:21.717

Modified: 2026-08-17T05:18:08.173

Link: CVE-2026-68090

cve-icon Redhat

Severity : Low

Publid Date: 2026-08-10T00:00:00Z

Links: CVE-2026-68090 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-08-13T10:45:04Z

Weaknesses
  • CWE-367

    Time-of-check Time-of-use (TOCTOU) Race Condition