VDB

CVE-2025-38256

CVE-2025-38256 PUBLISHED

io_uring/rsrc: fix folio unpinning

Reported by linux · Published July 9, 2025

In the Linux kernel, the following vulnerability has been resolved: io_uring/rsrc: fix folio unpinning syzbot complains about an unmapping failure: [ 108.070381][ T14] kernel BUG at mm/gup.c:71! [ 108.070502][ T14] Internal error: Oops - BUG: 00000000f2000800 [#1] SMP [ 108.123672][ T14] Hardware name: QEMU KVM Virtual Machine, BIOS edk2-20250221-8.fc42 02/21/2025 [ 108.127458][ T14] Workqueue: iou_exit io_ring_exit_work [ 108.174205][ T14] Call trace: [ 108.175649][ T14] sanity_check_pinned_pages+0x7cc/0x7d0 (P) [ 108.178138][ T14] unpin_user_page+0x80/0x10c [ 108.180189][ T14] io_release_ubuf+0x84/0xf8 [ 108.182196][ T14] io_free_rsrc_node+0x250/0x57c [ 108.184345][ T14] io_rsrc_data_free+0x148/0x298 [ 108.186493][ T14] io_sqe_buffers_unregister+0x84/0xa0 [ 108.188991][ T14] io_ring_ctx_free+0x48/0x480 [ 108.191057][ T14] io_ring_exit_work+0x764/0x7d8 [ 108.193207][ T14] process_one_work+0x7e8/0x155c [ 108.195431][ T14] worker_thread+0x958/0xed8 [ 108.197561][ T14] kthread+0x5fc/0x75c [ 108.199362][ T14] ret_from_fork+0x10/0x20 We can pin a tail page of a folio, but then io_uring will try to unpin the head page of the folio. While it should be fine in terms of keeping the page actually alive, mm folks say it's wrong and triggers a debug warning. Use unpin_user_folio() instead of unpin_user_page*. [axboe: adapt to current tree, massage commit message]

EPSS 0.17% · 6.3th percentile

Fixed versions

Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.

PackageEcosystemFixed in
kernel6.12-tools-develAmazon Linux1:6.12.37-61.105.amzn2023
bpftool6.12Amazon Linux1:6.12.37-61.105.amzn2023
kernel6.12-modules-extra-commonAmazon Linux1:6.12.37-61.105.amzn2023
kernel6.12-develAmazon Linux1:6.12.37-61.105.amzn2023
kernel6.12-toolsAmazon Linux1:6.12.37-61.105.amzn2023
kernel6.12-libbpfAmazon Linux1:6.12.37-61.105.amzn2023
kernel6.12-headersAmazon Linux1:6.12.37-61.105.amzn2023
linux_kernellinux6.15.5, 6.12.36

Risk scores

EPSS Score
0.17%
6.3th percentile

Affected products

VendorProductVersions
LinuxLinuxa8edbb424b1391b077407c75d8f5d2ede77aa70d, a8edbb424b1391b077407c75d8f5d2ede77aa70d, a8edbb424b1391b077407c75d8f5d2ede77aa70d
LinuxLinux6.12, 0, 6.12.36
amazon:2023kernel6.12-tools-devel0
amazon:2023bpftool6.120
amazon:2023kernel6.12-modules-extra-common0
amazon:2023kernel6.12-devel0
amazon:2023kernel6.12-tools0
amazon:2023kernel6.12-libbpf0
amazon:2023kernel6.12-headers0
linuxlinux_kernel6.12, 6.12, 6.12
amazon:2023kernel6.12-libbpf-devel0
amazon:2023kernel6.120
amazon:2023kernel6.12-modules-extra0
amazon:2023kernel-livepatch-6.12.37-61.1050
LinuxLinux*, 6.16, *
amazon:2023perf6.120
amazon:2023kernel6.12-libbpf-static0
amazon:2023python3-perf6.120

Timeline

  • Jul 8, 2025 CVE Published
  • Jul 9, 2025 EPSS Score (30 in total, the first dated here)
  • Oct 12, 2025 PoC Published (10 in total, the first dated here)
  • Apr 29, 2026 Distribution Patch (116 in total, the first dated here)
  • Apr 29, 2026 Security Advisory (123 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-38256
vulnetix vdb fixes CVE-2025-38256

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-38256/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

References

Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›