CVE-2025-37808: crypto: null - Use spin lock instead of mutex
Published May 8, 2025
·Updated
crypto: null - Use spin lock instead of mutex
Affected Software
11 affected componentsFixes available
Linux Linux kernel
Linux Linux kernel>=4.2<5.4.293
Linux Linux kernel>=5.5<5.10.237
Linux Linux kernel>=5.11<5.15.181
Linux Linux kernel>=5.16<6.1.136
Linux Linux kernel>=6.2<6.6.89
Linux Linux kernel>=6.7<6.12.26
Linux Linux kernel>=6.13<6.14.5
Debian Debian Linux=11.0
Microsoft azl3 kernel 6.6.85.1-4
Microsoft azl3 kernel 6.6.92.2-1
Remediation
Event History
May 8, 2025
CVE Published
via MITRE·06:26 AM
Data Sourced
via MITRE·06:26 AM
Description
Data Sourced
via NVD·07:15 AM
RemedyDescriptionSeverityAffected Software
Jul 11, 2025
Data Sourced
via Microsoft·07:00 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·07:00 AM
Affected Software
Updated
via Microsoft·07:00 AM
DescriptionSeverity
Frequently Asked Questions
1
What is the severity of CVE-2025-37808?
The severity of CVE-2025-37808 is classified as moderate due to potential denial of service risks.
2
How do I fix CVE-2025-37808?
To fix CVE-2025-37808, update your Linux kernel to the latest patch version where the vulnerability has been resolved.
3
What is affected by CVE-2025-37808?
CVE-2025-37808 affects the Linux kernel specifically in implementations using the null cipher algorithm.
4
What exploitation methods are possible with CVE-2025-37808?
Exploitation of CVE-2025-37808 could potentially allow an attacker to cause a denial of service due to improper locking mechanisms.
5
How can I determine if my system is vulnerable to CVE-2025-37808?
You can determine if your system is vulnerable to CVE-2025-37808 by checking the version of your Linux kernel against the patched versions.