CVE-2024-35819: soc: fsl: qbman: Use raw spinlock for cgr_lock
In the Linux kernel, the following vulnerability has been resolved:
soc: fsl: qbman: Use raw spinlock for cgrlock
smpcallfunction always runs its callback in hard IRQ context, even on PREEMPTRT, where spinlocks can sleep. So we need to use a raw spinlock for cgrlock 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 smpcallfunctionsingle via qmanupdatecgrsafe every time a link goes up or down.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2024-35819?
CVE-2024-35819 is classified as a medium severity vulnerability in the Linux kernel.
How do I fix CVE-2024-35819?
To fix CVE-2024-35819, you should update to the patched versions of the Linux kernel such as 5.10.223-1, 5.10.226-1, 6.1.119-1, 6.1.123-1, 6.12.10-1, or 6.12.11-1.
Which Linux distributions are affected by CVE-2024-35819?
CVE-2024-35819 affects Debian-based Linux distributions that utilize the specified vulnerable Linux kernel versions.
Is CVE-2024-35819 exploitable remotely?
CVE-2024-35819 is not considered remotely exploitable as it requires certain conditions in the kernel execution context.
What components of the Linux kernel are impacted by CVE-2024-35819?
CVE-2024-35819 specifically impacts the soc:fsl:qbman component due to incorrect usage of spinlocks in the Linux kernel.