{"id":69585,"date":"2025-09-05T23:32:19","date_gmt":"2025-09-05T20:02:19","guid":{"rendered":"https:\/\/afaghhosting.net\/blog\/cve-2025-39722-crypto-caam-prevent-crash-on-suspend-with-imx8qm-imx8ulp\/"},"modified":"2025-09-05T23:32:19","modified_gmt":"2025-09-05T20:02:19","slug":"cve-2025-39722-crypto-caam-prevent-crash-on-suspend-with-imx8qm-imx8ulp","status":"publish","type":"post","link":"https:\/\/afaghhosting.net\/blog\/cve-2025-39722-crypto-caam-prevent-crash-on-suspend-with-imx8qm-imx8ulp\/","title":{"rendered":"CVE-2025-39722 &#8211; crypto: caam &#8211; Prevent crash on suspend with iMX8QM \/ iMX8ULP"},"content":{"rendered":"<p><strong>CVE ID : <\/strong>CVE-2025-39722<br \/>\n<br \/>\n<strong>Published : <\/strong> Sept. 5, 2025, 6:15 p.m. | 1\u00a0hour ago<br \/>\n<br \/>\n<strong>Description : <\/strong>In the Linux kernel, the following vulnerability has been resolved:<\/p>\n<p>crypto: caam &#8211; Prevent crash on suspend with iMX8QM \/ iMX8ULP<\/p>\n<p>Since the CAAM on these SoCs is managed by another ARM core, called the<br \/>\nSECO (Security Controller) on iMX8QM and Secure Enclave on iMX8ULP, which<br \/>\nalso reserves access to register page 0 suspend operations cannot touch<br \/>\nthis page.<\/p>\n<p>This is similar to when running OPTEE, where OPTEE will reserve page 0.<\/p>\n<p>Track this situation using a new state variable no_page0, reflecting if<br \/>\npage 0 is reserved elsewhere, either by other management cores in SoC or<br \/>\nby OPTEE.<\/p>\n<p>Replace the optee_en check in suspend\/resume with the new check.<\/p>\n<p>optee_en cannot go away as it&#8217;s needed elsewhere to gate OPTEE specific<br \/>\nsituations.<\/p>\n<p>Fixes the following splat at suspend:<\/p>\n<p>    Internal error: synchronous external abort: 0000000096000010 [#1] SMP<br \/>\n    Hardware name: Freescale i.MX8QXP ACU6C (DT)<br \/>\n    pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=&#8211;)<br \/>\n    pc : readl+0x0\/0x18<br \/>\n    lr : rd_reg32+0x18\/0x3c<br \/>\n    sp : ffffffc08192ba20<br \/>\n    x29: ffffffc08192ba20 x28: ffffff8025190000 x27: 0000000000000000<br \/>\n    x26: ffffffc0808ae808 x25: ffffffc080922338 x24: ffffff8020e89090<br \/>\n    x23: 0000000000000000 x22: ffffffc080922000 x21: ffffff8020e89010<br \/>\n    x20: ffffffc080387ef8 x19: ffffff8020e89010 x18: 000000005d8000d5<br \/>\n    x17: 0000000030f35963 x16: 000000008f785f3f x15: 000000003b8ef57c<br \/>\n    x14: 00000000c418aef8 x13: 00000000f5fea526 x12: 0000000000000001<br \/>\n    x11: 0000000000000002 x10: 0000000000000001 x9 : 0000000000000000<br \/>\n    x8 : ffffff8025190870 x7 : ffffff8021726880 x6 : 0000000000000002<br \/>\n    x5 : ffffff80217268f0 x4 : ffffff8021726880 x3 : ffffffc081200000<br \/>\n    x2 : 0000000000000001 x1 : ffffff8020e89010 x0 : ffffffc081200004<br \/>\n    Call trace:<br \/>\n     readl+0x0\/0x18<br \/>\n     caam_ctrl_suspend+0x30\/0xdc<br \/>\n     dpm_run_callback.constprop.0+0x24\/0x5c<br \/>\n     device_suspend+0x170\/0x2e8<br \/>\n     dpm_suspend+0xa0\/0x104<br \/>\n     dpm_suspend_start+0x48\/0x50<br \/>\n     suspend_devices_and_enter+0x7c\/0x45c<br \/>\n     pm_suspend+0x148\/0x160<br \/>\n     state_store+0xb4\/0xf8<br \/>\n     kobj_attr_store+0x14\/0x24<br \/>\n     sysfs_kf_write+0x38\/0x48<br \/>\n     kernfs_fop_write_iter+0xb4\/0x178<br \/>\n     vfs_write+0x118\/0x178<br \/>\n     ksys_write+0x6c\/0xd0<br \/>\n     __arm64_sys_write+0x14\/0x1c<br \/>\n     invoke_syscall.constprop.0+0x64\/0xb0<br \/>\n     do_el0_svc+0x90\/0xb0<br \/>\n     el0_svc+0x18\/0x44<br \/>\n     el0t_64_sync_handler+0x88\/0x124<br \/>\n     el0t_64_sync+0x150\/0x154<br \/>\n    Code: 88dffc21 88dffc21 5ac00800 d65f03c0 (b9400000)<br \/>\n<br \/>\n<strong>Severity:<\/strong> 0.0 | NA<br \/>\n<br \/>\nVisit the link for more details, such as CVSS details, affected products, timeline, and more&#8230;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>CVE ID : CVE-2025-39722 Published : Sept. 5, 2025, 6:15 p.m. | 1\u00a0hour ago Description : In the Linux kernel, the following vulnerability has been resolved: crypto: caam &#8211; 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 &hellip;<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[26],"tags":[],"class_list":["post-69585","post","type-post","status-publish","format-standard","hentry","category-vulnerability"],"_links":{"self":[{"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/posts\/69585","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/comments?post=69585"}],"version-history":[{"count":0,"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/posts\/69585\/revisions"}],"wp:attachment":[{"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/media?parent=69585"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/categories?post=69585"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/tags?post=69585"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}