debugobjects: Plug race against a concurrent OOM disable
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ b84d435cc228e87951f3bbabf6cc4a5f25d5fb16 · < c00164c9e7fa6145886ad666806cb5347895de5c| No fix yet |
| Linux Linux |
|
|
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:
From the CVE record · Linux
A race between debug object checks and an out-of-memory event that disables debug objects can invoke a timer fixup after its shadow object is freed, leaving the timer dysfunctional. The input does not describe an attacker-controlled path, authentication requirement, or user interaction.
Engineers running Linux kernels with debug objects enabled should check their affected versions; no version range is provided.