CVE-2025-38359
s390/mm: Fix in_atomic() handling in do_secure_storage_access()
Reported by linux · Published July 25, 2025
In the Linux kernel, the following vulnerability has been resolved: s390/mm: Fix in_atomic() handling in do_secure_storage_access() Kernel user spaces accesses to not exported pages in atomic context incorrectly try to resolve the page fault. With debug options enabled call traces like this can be seen: BUG: sleeping function called from invalid context at kernel/locking/rwsem.c:1523 in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 419074, name: qemu-system-s39 preempt_count: 1, expected: 0 RCU nest depth: 0, expected: 0 INFO: lockdep is turned off. Preemption disabled at: [<00000383ea47cfa2>] copy_page_from_iter_atomic+0xa2/0x8a0 CPU: 12 UID: 0 PID: 419074 Comm: qemu-system-s39 Tainted: G W 6.16.0-20250531.rc0.git0.69b3a602feac.63.fc42.s390x+debug #1 PREEMPT Tainted: [W]=WARN Hardware name: IBM 3931 A01 703 (LPAR) Call Trace: [<00000383e990d282>] dump_stack_lvl+0xa2/0xe8 [<00000383e99bf152>] __might_resched+0x292/0x2d0 [<00000383eaa7c374>] down_read+0x34/0x2d0 [<00000383e99432f8>] do_secure_storage_access+0x108/0x360 [<00000383eaa724b0>] __do_pgm_check+0x130/0x220 [<00000383eaa842e4>] pgm_check_handler+0x114/0x160 [<00000383ea47d028>] copy_page_from_iter_atomic+0x128/0x8a0 ([<00000383ea47d016>] copy_page_from_iter_atomic+0x116/0x8a0) [<00000383e9c45eae>] generic_perform_write+0x16e/0x310 [<00000383e9eb87f4>] ext4_buffered_write_iter+0x84/0x160 [<00000383e9da0de4>] vfs_write+0x1c4/0x460 [<00000383e9da123c>] ksys_write+0x7c/0x100 [<00000383eaa7284e>] __do_syscall+0x15e/0x280 [<00000383eaa8417e>] system_call+0x6e/0x90 INFO: lockdep is turned off. It is not allowed to take the mmap_lock while in atomic context. Therefore handle such a secure storage access fault as if the accessed page is not mapped: the uaccess function will return -EFAULT, and the caller has to deal with this. Usually this means that the access is retried in process context, which allows to resolve the page fault (or in this case export the page).
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| linux-aws-6.12 | Chainguard | 6.12.80-r0 |
| linux-vmware-6.12 | Chainguard | 6.12.80-r0 |
| linux_kernel | linux | 6.15.5 |
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 084ea4d611a3d00ee3930400b262240e10895900, 084ea4d611a3d00ee3930400b262240e10895900, 084ea4d611a3d00ee3930400b262240e10895900 |
| Linux | Linux | 5.7, 0, 6.1.191 |
| chainguard | linux-aws-6.12 | 0 |
| chainguard | linux-vmware-6.12 | 0 |
| linux | linux_kernel | 5.7, 5.7, 5.7 |
| chainguard | linux-azure-6.12 | 0 |
| chainguard | linux-qemu-6.12 | 0 |
| chainguard | linux-gcp-6.12 | 0 |
| Linux | Linux | 6.12.114, 6.15.5, 6.16 |
Timeline
- Jul 25, 2025 CVE Published
- Jul 26, 2025 EPSS Score (30 in total, the first dated here)
- Oct 12, 2025 PoC Published (9 in total, the first dated here)
- Apr 29, 2026 Distribution Patch (171 in total, the first dated here)
- Apr 29, 2026 Security Advisory (187 in total, the first dated here)
- Jun 9, 2026 Coalition ESS Score
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2025-38359
vulnetix vdb fixes CVE-2025-38359
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2025-38359/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart