CVE-2025-39722: crypto: caam - Prevent crash on suspend with iMX8QM / iMX8ULP
In the Linux kernel, the following vulnerability has been resolved:
crypto: caam - Prevent crash on suspend with iMX8QM / iMX8ULP
Since the CAAM on these SoCs is managed by another ARM core, called the SECO (Security Controller) on iMX8QM and Secure Enclave on iMX8ULP, which also reserves access to register page 0 suspend operations cannot touch this page.
This is similar to when running OPTEE, where OPTEE will reserve page 0.
Track this situation using a new state variable nopage0, reflecting if page 0 is reserved elsewhere, either by other management cores in SoC or by OPTEE.
Replace the opteeen check in suspend/resume with the new check.
opteeen cannot go away as it's needed elsewhere to gate OPTEE specific situations.
Fixes the following splat at suspend:
Internal error: synchronous external abort: 0000000096000010 [#1] SMP Hardware name: Freescale i.MX8QXP ACU6C (DT) pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : readl+0x0/0x18 lr : rdreg32+0x18/0x3c sp : ffffffc08192ba20 x29: ffffffc08192ba20 x28: ffffff8025190000 x27: 0000000000000000 x26: ffffffc0808ae808 x25: ffffffc080922338 x24: ffffff8020e89090 x23: 0000000000000000 x22: ffffffc080922000 x21: ffffff8020e89010 x20: ffffffc080387ef8 x19: ffffff8020e89010 x18: 000000005d8000d5 x17: 0000000030f35963 x16: 000000008f785f3f x15: 000000003b8ef57c x14: 00000000c418aef8 x13: 00000000f5fea526 x12: 0000000000000001 x11: 0000000000000002 x10: 0000000000000001 x9 : 0000000000000000 x8 : ffffff8025190870 x7 : ffffff8021726880 x6 : 0000000000000002 x5 : ffffff80217268f0 x4 : ffffff8021726880 x3 : ffffffc081200000 x2 : 0000000000000001 x1 : ffffff8020e89010 x0 : ffffffc081200004 Call trace: readl+0x0/0x18 caamctrlsuspend+0x30/0xdc dpmruncallback.constprop.0+0x24/0x5c devicesuspend+0x170/0x2e8 dpmsuspend+0xa0/0x104 dpmsuspendstart+0x48/0x50 suspenddevicesandenter+0x7c/0x45c pmsuspend+0x148/0x160 statestore+0xb4/0xf8 kobjattrstore+0x14/0x24 sysfskfwrite+0x38/0x48 kernfsfopwriteiter+0xb4/0x178 vfswrite+0x118/0x178 ksyswrite+0x6c/0xd0 arm64syswrite+0x14/0x1c invokesyscall.constprop.0+0x64/0xb0 doel0svc+0x90/0xb0 el0svc+0x18/0x44 el0t64synchandler+0x88/0x124 el0t64sync+0x150/0x154 Code: 88dffc21 88dffc21 5ac00800 d65f03c0 (b9400000)
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.1.176-1Fixed in 6.1.190-1Fixed in 6.12.107-1Fixed in 6.12.113-1Fixed in 7.2.12-1Fixed in 7.2.13-1
Event History
Frequently Asked Questions
What is the severity of CVE-2025-39722?
CVE-2025-39722 is considered a moderate severity vulnerability affecting the Linux kernel.
How do I fix CVE-2025-39722?
To fix CVE-2025-39722, users should update the Linux kernel to the latest stable version.
What systems are affected by CVE-2025-39722?
CVE-2025-39722 affects devices using the Linux kernel with the CAAM management on iMX8QM and iMX8ULP SoCs.
What are the consequences of CVE-2025-39722?
Exploiting CVE-2025-39722 can result in a crash during system suspend operations on affected devices.
Is there a public exploit for CVE-2025-39722?
As of now, there are no publicly known exploits specifically targeting CVE-2025-39722.