soc: fsl: qbman: Use raw spinlock for cgr_lock
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 96f413f47677366e0ae03797409bfcc4151dbf9e · < 54d26adf64c04f186098b39dba86b86037084baa| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
soc: fsl: qbman: Use raw spinlock for cgr_lock
smp_call_function always runs its callback in hard IRQ context, even on PREEMPT_RT, where spinlocks can sleep. So we need to use a raw spinlock for cgr_lock to ensure we aren't waiting on a sleeping task.
Although this bug has existed for a while, it was not apparent until commit ef2a8d5478b9 ("net: dpaa: Adjust queue depth on rate change") which invokes smp_call_function_single via qman_update_cgr_safe every time a link goes up or down.
From the CVE record · Linux
The Linux kernel's FSL QBMan cgr_lock uses a spinlock that can sleep on PREEMPT_RT, even though its callback runs in hard IRQ context. After a queue-depth change, link-up or link-down events can trigger the affected path; the input does not describe an attacker access requirement or user interaction.
Check Linux kernel deployments using FSL QBMan with PREEMPT_RT; affected versions are not specified.