CVE-2025-37808 json
crypto: null - Use spin lock instead of mutex
published 2025-05-08 18 mo ago modified 2026-11-05 3 d ago also EUVD-2025-13983
- cvss
- 5.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 11%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
crypto: null - Use spin lock instead of mutex
As the null algorithm may be freed in softirq context through af_alg, use spin locks instead of mutexes to protect the default null algorithm.
Patch / fix
- Linux Linux 5.4.293, 5.10.237, 5.15.181, 6.1.136, 6.6.89, 6.12.26, 6.14.5, 6.15
- linux Debian 12 6.1.137-1
- linux Debian 14, Debian 13 6.12.27-1
debian advisories DEBIAN-CVE-2025-37808
- linux Ubuntu 22.04 LTS 5.15.0-144.157
- linux Ubuntu 24.04 LTS 6.8.0-100.100
- linux-aws Ubuntu 22.04 LTS 5.15.0-1088.95
- linux-aws Ubuntu 24.04 LTS 6.8.0-1046.49
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1087.96
- linux-gcp Ubuntu 24.04 LTS 6.8.0-1047.50
- linux-gke Ubuntu 22.04 LTS 5.15.0-1085.91
- linux-gke Ubuntu 24.04 LTS 6.8.0-1043.48
ubuntu advisories UBUNTU-CVE-2025-37808
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- git.kernel.org/stable/c/f7a5a5c8e1ec16a4b2041398abe95de0e14572ef commit
- git.kernel.org/stable/c/e307c54ac8198bf09652c72603ba6e6d97798410 commit
- git.kernel.org/stable/c/1dd4a8561d85dea545cf93f56efc48df8176e218 commit
- git.kernel.org/stable/c/e27244cbe10658a66b8775be7f0acc4ad2f618d6 commit
- git.kernel.org/stable/c/1b66a5920b7fc7cc6251192a3fcad115b6d75dd5 commit
- git.kernel.org/stable/c/0486de3c1b8223138dcc614846bd76364f758de6 commit
- git.kernel.org/stable/c/8cf2945512a8c0ef74ddd5b5a4f6b6a2fb1a4efb commit
- git.kernel.org/stable/c/dcc47a028c24e793ce6d6efebfef1a1e92f80297 commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2025-37808 updated cvss 4.4
kernel: crypto: null - Use spin lock instead of mutex
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 moreaffected: no fix planned “Out of support scope”
-
Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernelaffected: no fix available “Fix deferred”
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 3 d ago
Exploit prediction
0.21% chance of exploitation in the next 30 days, higher than 11% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
Affected products
- Linux Linux
Classification
- Technology feeds
References
-
git.kernel.org
/stable/c/f7a5a5c8e1ec16a4b2041398abe95de0e14572ef
patch
-
git.kernel.org
/stable/c/e307c54ac8198bf09652c72603ba6e6d97798410
patch
-
git.kernel.org
/stable/c/1dd4a8561d85dea545cf93f56efc48df8176e218
patch
-
git.kernel.org
/stable/c/e27244cbe10658a66b8775be7f0acc4ad2f618d6
patch
-
git.kernel.org
/stable/c/1b66a5920b7fc7cc6251192a3fcad115b6d75dd5
patch
-
git.kernel.org
/stable/c/0486de3c1b8223138dcc614846bd76364f758de6
patch
-
git.kernel.org
/stable/c/8cf2945512a8c0ef74ddd5b5a4f6b6a2fb1a4efb
patch
-
git.kernel.org
/stable/c/dcc47a028c24e793ce6d6efebfef1a1e92f80297
patch
-
lists.debian.org
/debian-lts-announce/2025/05/msg00045.html
mailing-list
-
lists.debian.org
/debian-lts-announce/2025/05/msg00030.html
mailing-list
Sources
- CVE List CVE-2025-37808
- NVD CVE-2025-37808
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.