debugobjects: Don't call fill_pool() in early boot hardirq context
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 06e0ae988f6e3499785c407429953ade19c1096b · < 0d046ae106255cba5eb83b23f78ee93f3620247d| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
debugobjects: Don't call fill_pool() in early boot hardirq context
When booting a debug PREEMPT_RT kernel on an ARM64 system, a "inconsistent {HARDIRQ-ON-W} -> {IN-HARDIRQ-W} usage" lockdep warning message was reported to the console.
During early boot, interrupts are enabled before the scheduler is enabled. In this window (before SYSTEM_SCHEDULING is set) interrupts can fire and in the hard interrupt context handler attempt to fill the pool
This can lead to a deadlock when the interrupt occurred when the interrupt hits a region which holds a lock that is required to be taken in the allocation path.
Add a new can_fill_pool() helper and reorder the exception rule and forbid this scenario by excluding allocations from hard interrupt context.
From the CVE record · Linux
In a debug PREEMPT_RT Linux kernel on ARM64, debugobjects can attempt to fill its pool from hard interrupt context during early boot, before the scheduler is enabled. This can deadlock if the interrupt occurs while a lock needed by the allocation path is held. The input does not describe an attacker-controlled trigger, authentication requirement, or user interaction.
Engineers running debug PREEMPT_RT Linux kernels on ARM64 should check their systems; affected versions are not specified.