VDB

CVE-2025-38100

CVE-2025-38100 PUBLISHED

x86/iopl: Cure TIF_IO_BITMAP inconsistencies

Reported by linux · Published July 3, 2025

In the Linux kernel, the following vulnerability has been resolved: x86/iopl: Cure TIF_IO_BITMAP inconsistencies io_bitmap_exit() is invoked from exit_thread() when a task exists or when a fork fails. In the latter case the exit_thread() cleans up resources which were allocated during fork(). io_bitmap_exit() invokes task_update_io_bitmap(), which in turn ends up in tss_update_io_bitmap(). tss_update_io_bitmap() operates on the current task. If current has TIF_IO_BITMAP set, but no bitmap installed, tss_update_io_bitmap() crashes with a NULL pointer dereference. There are two issues, which lead to that problem: 1) io_bitmap_exit() should not invoke task_update_io_bitmap() when the task, which is cleaned up, is not the current task. That's a clear indicator for a cleanup after a failed fork(). 2) A task should not have TIF_IO_BITMAP set and neither a bitmap installed nor IOPL emulation level 3 activated. This happens when a kernel thread is created in the context of a user space thread, which has TIF_IO_BITMAP set as the thread flags are copied and the IO bitmap pointer is cleared. Other than in the failed fork() case this has no impact because kernel threads including IO workers never return to user space and therefore never invoke tss_update_io_bitmap(). Cure this by adding the missing cleanups and checks: 1) Prevent io_bitmap_exit() to invoke task_update_io_bitmap() if the to be cleaned up task is not the current task. 2) Clear TIF_IO_BITMAP in copy_thread() unconditionally. For user space forks it is set later, when the IO bitmap is inherited in io_bitmap_share(). For paranoia sake, add a warning into tss_update_io_bitmap() to catch the case, when that code is invoked with inconsistent state.

Fixed versions

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

PackageEcosystemFixed in
python3-perf6.12Amazon Linux6.12.35-55.103.amzn2023
kernel6.12-modules-extraAmazon Linux6.12.35-55.103.amzn2023
bpftoolAmazon Linux6.12.35-55.103.amzn2023
kernel-toolsAmazon Linux6.12.35-55.103.amzn2023
LinuxLinuxd64b7b05a827f98d068f412969eef65489b0cf03, b3b3b6366dc8eb5b22edba9adc4bff3cdacfd64c, aa5ce1485562f20235b4c759eee5ab0c41d2c220, 8b68e978718f14fdcb080c2a7791c52a0d09bc6d, 73cfcc8445585b8af7e18be3c9246b851fdf336c, 2dace5e016c991424a3dc6e83b1ae5dca8992d08, 2cfcbe1554c119402e7382de974c26b0549899fe

Affected products

VendorProductVersions
LinuxLinuxea5f1cd7ab494f65f50f338299eabb40ad6a1767, ea5f1cd7ab494f65f50f338299eabb40ad6a1767, ea5f1cd7ab494f65f50f338299eabb40ad6a1767
LinuxLinux5.5, 0, 5.10.239
amazon:2023python3-perf6.120
amazon:2023kernel6.12-modules-extra0
SiemensSIMATIC S7-1500 CPU 1518F-4 PN/DP MFP3.1.5
amazon:2023bpftool0
amazon:2023kernel-tools0
LinuxLinux6.16, *, *
amazon:2023kernel-libbpf0
amazon:2023kernel-tools-devel0
linuxlinux_kernel5.5, 5.5, 5.5
amazon:2023kernel-headers0
amazon:2023kernel-livepatch-6.12.35-55.1030
amazon:2023kernel-devel0
amazon:2023kernel-libbpf-devel0
amazon:2023kernel-libbpf-static0
SiemensSIPLUS S7-1500 CPU 1518-4 PN/DP MFP3.1.5
amazon:2023perf6.120
SiemensSIMATIC S7-1500 CPU 1518-4 PN/DP MFP3.1.5
amazon:2023kernel6.120

…and 1 more

Timeline

  • Jul 2, 2025 CVE Published
  • Jul 3, 2025 EPSS Score (30 in total, the first dated here)
  • Oct 12, 2025 PoC Published (7 in total, the first dated here)
  • Nov 17, 2025 CVE Updated
  • Mar 29, 2026 Distribution Patch (224 in total, the first dated here)
  • Mar 29, 2026 Security Advisory (238 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-38100
vulnetix vdb fixes CVE-2025-38100

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

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

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