CVE-2024-35819: soc: fsl: qbman: Use raw spinlock for cgr_lock
First published: Fri May 17 2024(Updated: )
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.
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67 416baaa9-dc9f-4396-8d5f-8c081fb06d67
| Affected Software | Affected Version | How to fix |
|---|---|---|
| debian/linux | 5.10.223-1 5.10.226-1 6.1.123-1 6.1.119-1 6.12.10-1 6.12.11-1 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://git.kernel.org/stable/c/2b3fede8225133671ce837c0d284804aa3bc7a02
- https://git.kernel.org/stable/c/32edca2f03a6cc42c650ddc3ad83d086e3f365d1
- https://git.kernel.org/stable/c/54d26adf64c04f186098b39dba86b86037084baa
- https://git.kernel.org/stable/c/9a3ca8292ce9fdcce122706c28c3f07bc857fe5e
- https://git.kernel.org/stable/c/cd53a8ae5aacb4ecd25088486dea1cd02e74b506
- https://git.kernel.org/stable/c/d6b5aac451c9cc12e43ab7308e0e2ddc52c62c14
- https://git.kernel.org/stable/c/f39d36b7540cf0088ed7ce2de2794f2aa237f6df
- https://git.kernel.org/stable/c/fbec4e7fed89b579f2483041fabf9650fb0dd6bc
- https://git.kernel.org/stable/c/ff50716b7d5b7985979a5b21163cd79fb3d21d59
- https://launchpad.net/bugs/cve/CVE-2024-35819
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-35819
- https://nvd.nist.gov/vuln/detail/CVE-2024-35819
- https://security-tracker.debian.org/tracker/CVE-2024-35819
- https://ubuntu.com/security/CVE-2024-35819
- https://lists.debian.org/debian-lts-announce/2024/06/msg00017.html
- https://lists.debian.org/debian-lts-announce/2024/06/msg00020.html
- https://git.kernel.org/linus/fbec4e7fed89b579f2483041fabf9650fb0dd6bc
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.
- agent/title
- agent/severity
- agent/type
- collector/epss-latest
- source/FIRST
- agent/epss
- agent/remedy
- agent/first-publish-date
- collector/launchpad-cve
- source/Launchpad
- agent/author
- collector/nvd-api
- source/NVD
- collector/usn-cve
- source/Ubuntu
- collector/nvd-cve
- collector/mitre-cve
- source/MITRE
- agent/description
- agent/event
- agent/last-modified-date
- agent/references
- agent/trending
- agent/source
- agent/tags
- agent/softwarecombine
- collector/security-tracker-debian
- source/Debian
- package-manager/debian