# CVE-2025-38383: mm/vmalloc: fix data race in show_numa_info() > A data race in the Linux kernel's vmalloc subsystem can lead to inconsistent state during proc file reads, requiring a kernel patch. - **Severity:** Medium 4.7 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 25 Jul 2025 - **Updated:** 11 May 2026 - **Also known as:** ALSA-2026:1178, BELL-CVE-2025-38383, DEBIAN-CVE-2025-38383, GHSA-pqhv-fc7x-qjmr, RHSA-2026:1178, RLSA-2026:1178, UBUNTU-CVE-2025-38383 ## What is CVE-2025-38383? CVE-2025-38383 is a medium-severity vulnerability in Linux kernel, published on 25 Jul 2025. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description In the Linux kernel, the following vulnerability has been resolved: mm/vmalloc: fix data race in show_numa_info() The following data-race was found in show_numa_info(): ================================================================== BUG: KCSAN: data-race in vmalloc_info_show / vmalloc_info_show read to 0xffff88800971fe30 of 4 bytes by task 8289 on cpu 0: show_numa_info mm/vmalloc.c:4936 [inline] vmalloc_info_show+0x5a8/0x7e0 mm/vmalloc.c:5016 seq_read_iter+0x373/0xb40 fs/seq_file.c:230 proc_reg_read_iter+0x11e/0x170 fs/proc/inode.c:299 .... write to 0xffff88800971fe30 of 4 bytes by task 8287 on cpu 1: show_numa_info mm/vmalloc.c:4934 [inline] vmalloc_info_show+0x38f/0x7e0 mm/vmalloc.c:5016 seq_read_iter+0x373/0xb40 fs/seq_file.c:230 proc_reg_read_iter+0x11e/0x170 fs/proc/inode.c:299 .... value changed: 0x0000008f -> 0x00000000 ================================================================== According to this report,there is a read/write data-race because m->private is accessible to multiple CPUs. To fix this, instead of allocating the heap in proc_vmalloc_init() and passing the heap address to m->private, vmalloc_info_show() should allocate the heap. Weakness: CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization) ## Which versions are affected by CVE-2025-38383? It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `kernel-abi-stablelists` | AlmaLinux:10 | All versions | 6.12.0-124.29.1.el10_1 | | `kernel-doc` | AlmaLinux:10 | All versions | 6.12.0-124.29.1.el10_1 | | `kernel` | Red Hat:enterprise_linux:10.1 | All versions | 0:6.12.0-124.29.1.el10_1 | | `kernel-64k` | Red Hat:enterprise_linux:10.1 | All versions | 0:6.12.0-124.29.1.el10_1 | | `kernel-64k-core` | Red Hat:enterprise_linux:10.1 | All versions | 0:6.12.0-124.29.1.el10_1 | | `kernel-64k-debug` | Red Hat:enterprise_linux:10.1 | All versions | 0:6.12.0-124.29.1.el10_1 | | `kernel-64k-debug-core` | Red Hat:enterprise_linux:10.1 | All versions | 0:6.12.0-124.29.1.el10_1 | | `kernel-64k-debug-debuginfo` | Red Hat:enterprise_linux:10.1 | All versions | 0:6.12.0-124.29.1.el10_1 | | `kernel-64k-debug-devel` | Red Hat:enterprise_linux:10.1 | All versions | 0:6.12.0-124.29.1.el10_1 | | `kernel-64k-debug-devel-matched` | Red Hat:enterprise_linux:10.1 | All versions | 0:6.12.0-124.29.1.el10_1 | | `kernel-64k-debug-modules` | Red Hat:enterprise_linux:10.1 | All versions | 0:6.12.0-124.29.1.el10_1 | | `kernel-64k-debug-modules-core` | Red Hat:enterprise_linux:10.1 | All versions | 0:6.12.0-124.29.1.el10_1 | | `kernel-64k-debug-modules-extra` | Red Hat:enterprise_linux:10.1 | All versions | 0:6.12.0-124.29.1.el10_1 | | `kernel-64k-debuginfo` | Red Hat:enterprise_linux:10.1 | All versions | 0:6.12.0-124.29.1.el10_1 | | `kernel-64k-devel` | Red Hat:enterprise_linux:10.1 | All versions | 0:6.12.0-124.29.1.el10_1 | | `kernel-64k-devel-matched` | Red Hat:enterprise_linux:10.1 | All versions | 0:6.12.0-124.29.1.el10_1 | | `kernel-64k-modules` | Red Hat:enterprise_linux:10.1 | All versions | 0:6.12.0-124.29.1.el10_1 | | `kernel-64k-modules-core` | Red Hat:enterprise_linux:10.1 | All versions | 0:6.12.0-124.29.1.el10_1 | | `kernel-64k-modules-extra` | Red Hat:enterprise_linux:10.1 | All versions | 0:6.12.0-124.29.1.el10_1 | | `kernel-abi-stablelists` | Red Hat:enterprise_linux:10.1 | All versions | 0:6.12.0-124.29.1.el10_1 | | `kernel-core` | Red Hat:enterprise_linux:10.1 | All versions | 0:6.12.0-124.29.1.el10_1 | | `kernel-debug` | Red Hat:enterprise_linux:10.1 | All versions | 0:6.12.0-124.29.1.el10_1 | | `kernel-debug-core` | Red Hat:enterprise_linux:10.1 | All versions | 0:6.12.0-124.29.1.el10_1 | | `kernel-debug-debuginfo` | Red Hat:enterprise_linux:10.1 | All versions | 0:6.12.0-124.29.1.el10_1 | | `kernel-debug-devel` | Red Hat:enterprise_linux:10.1 | All versions | 0:6.12.0-124.29.1.el10_1 | | `kernel-debug-devel-matched` | Red Hat:enterprise_linux:10.1 | All versions | 0:6.12.0-124.29.1.el10_1 | | `kernel-debug-modules` | Red Hat:enterprise_linux:10.1 | All versions | 0:6.12.0-124.29.1.el10_1 | | `kernel-debug-modules-core` | Red Hat:enterprise_linux:10.1 | All versions | 0:6.12.0-124.29.1.el10_1 | | `kernel-debug-modules-extra` | Red Hat:enterprise_linux:10.1 | All versions | 0:6.12.0-124.29.1.el10_1 | | `kernel-debug-uki-virt` | Red Hat:enterprise_linux:10.1 | All versions | 0:6.12.0-124.29.1.el10_1 | | `kernel-debuginfo` | Red Hat:enterprise_linux:10.1 | All versions | 0:6.12.0-124.29.1.el10_1 | | `kernel-debuginfo-common-aarch64` | Red Hat:enterprise_linux:10.1 | All versions | 0:6.12.0-124.29.1.el10_1 | | `kernel-debuginfo-common-ppc64le` | Red Hat:enterprise_linux:10.1 | All versions | 0:6.12.0-124.29.1.el10_1 | | `kernel-debuginfo-common-s390x` | Red Hat:enterprise_linux:10.1 | All versions | 0:6.12.0-124.29.1.el10_1 | | `kernel-debuginfo-common-x86_64` | Red Hat:enterprise_linux:10.1 | All versions | 0:6.12.0-124.29.1.el10_1 | | `kernel-devel` | Red Hat:enterprise_linux:10.1 | All versions | 0:6.12.0-124.29.1.el10_1 | | `kernel-devel-matched` | Red Hat:enterprise_linux:10.1 | All versions | 0:6.12.0-124.29.1.el10_1 | | `kernel-doc` | Red Hat:enterprise_linux:10.1 | All versions | 0:6.12.0-124.29.1.el10_1 | | `kernel-modules` | Red Hat:enterprise_linux:10.1 | All versions | 0:6.12.0-124.29.1.el10_1 | | `kernel-modules-core` | Red Hat:enterprise_linux:10.1 | All versions | 0:6.12.0-124.29.1.el10_1 | Products: Linux kernel. ## How do I fix CVE-2025-38383? Apply the vendor's patch. ## Is CVE-2025-38383 being exploited? There is no known exploitation of CVE-2025-38383 in the wild and no public exploit code. ## Other vulnerabilities in Linux kernel - [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild) - [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild) - [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild) - [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild) - [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-38383 and fix it if it is affected. What it is: CVE-2025-38383 is a medium-severity vulnerability in Linux kernel, published on 25 Jul 2025. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2025-38383 in the wild and no public exploit code. Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2025-38383/ (Markdown: https://insights.sbomify.com/CVE-2025-38383/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-38383 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-38383 - OSV: https://osv.dev/vulnerability/CVE-2025-38383 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-38383/ Summaries are generated and may contain mistakes; the official description above is the record.