7.8
CVE-2025-38212
- EPSS 0.15%
- Veröffentlicht 04.07.2025 13:37:30
- Zuletzt bearbeitet 12.05.2026 13:16:44
- Quelle 416baaa9-dc9f-4396-8d5f-8c081f
- CVE-Watchlists
- Unerledigt
ipc: fix to protect IPCS lookups using RCU
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().
Daten sind bereitgestellt durch National Vulnerability Database (NVD)
Linux ≫ Linux Kernel Version >= 3.1 < 5.4.295
Linux ≫ Linux Kernel Version >= 5.5 < 5.10.239
Linux ≫ Linux Kernel Version >= 5.11 < 5.15.186
Linux ≫ Linux Kernel Version >= 5.16 < 6.1.142
Linux ≫ Linux Kernel Version >= 6.2 < 6.6.95
Linux ≫ Linux Kernel Version >= 6.7 < 6.12.35
Linux ≫ Linux Kernel Version >= 6.13 < 6.15.4
Debian ≫ Debian Linux Version11.0
VulnDex Vulnerability Enrichment
| Typ | Quelle | Score | Percentile |
|---|---|---|---|
| EPSS | FIRST.org | 0.15% | 0.047 |
| Quelle | Base Score | Exploit Score | Impact Score | Vector String |
|---|---|---|---|---|
| nvd@nist.gov | 7.8 | 1.8 | 5.9 |
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
|
CWE-416 Use After Free
The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.
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
https://lists.debian.org/debian-lts-announce/2025/10/msg00007.html
https://lists.debian.org/debian-lts-announce/2025/10/msg00008.html
https://cert-portal.siemens.com/productcert/html/ssa-082556.html