CVE-2024-50138: bpf: Use raw_spinlock_t in ringbuf
Published Nov 5, 2024
·Updated
bpf: Use rawspinlockt in ringbuf
Affected Software
9 affected componentsFixes available
Linux Linux kernel>=5.8<6.1.115
Linux Linux kernel>=6.2<6.11.6
Linux Linux kernel=6.12-rc1
Linux Linux kernel=6.12-rc2
Linux Linux kernel=6.12-rc3
debian/linux<=5.10.223-1, <=5.10.234-1
6.1.129-16.1.135-16.12.25-1
debian/linux-6.1
6.1.129-1~deb11u1
Microsoft azl3 kernel 6.6.92.2-1
Microsoft azl3 kernel 6.6.85.1-1
Remediation
Event History
Nov 5, 2024
CVE Published
via MITRE·05:11 PM
Data Sourced
via MITRE·05:11 PM
Description
Data Sourced
via NVD·06:15 PM
RemedyDescriptionSeverityAffected Software
May 3, 2025
Data Sourced
via Ubuntu·01:06 AM
RemedyDescriptionSeverityAffected Software
Sep 4, 2025
Data Sourced
via Microsoft·03:04 AM
DescriptionSeverityWeaknessAffected Software
Updated
via Microsoft·03:04 AM
SeverityAffected Software
Updated
via Microsoft·03:04 AM
Description
Frequently Asked Questions
1
What is the severity of CVE-2024-50138?
CVE-2024-50138 is classified as a moderate severity vulnerability.
2
How do I fix CVE-2024-50138?
To fix CVE-2024-50138, users should upgrade to the latest patched version of the Linux kernel.
3
What software versions are affected by CVE-2024-50138?
CVE-2024-50138 affects Linux kernel versions from 5.8 to 6.1.115 and between 6.2 to 6.11.6, as well as 6.12-rc1, 6.12-rc2, and 6.12-rc3.
4
What is the nature of the vulnerability in CVE-2024-50138?
CVE-2024-50138 is related to the use of spinlock_t in a context that disables preemption, potentially causing sleep in atomic warnings.
5
Who can be impacted by CVE-2024-50138?
Users running the affected versions of the Linux kernel could be impacted by CVE-2024-50138.