CVEvulnerability
CVE-2026-23380
5.5 MEDIUM
Official page ↗
- Status
- Analyzed
- Published
- 2026-03-25
- Last modified
- 2026-06-17
- Assigner
- 416baaa9-dc9f-4396-8d5f-8c081fb06d67
- CVSS 3.1 ([email protected])
- 5.5 MEDIUM — CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
- Weaknesses
- CWE-617
Description
In the Linux kernel, the following vulnerability has been resolved:
tracing: Fix WARN_ON in tracing_buffers_mmap_close
When a process forks, the child process copies the parent's VMAs but the
user_mapped reference count is not incremented. As a result, when both the
parent and child processes exit, tracing_buffers_mmap_close() is called
twice. On the second call, user_mapped is already 0, causing the function to
return -ENODEV and triggering a WARN_ON.
Normally, this isn't an issue as the memory is mapped with VM_DONTCOPY set.
But this is only a hint, and the application can call
madvise(MADVISE_DOFORK) which resets the VM_DONTCOPY flag. When the
application does that, it can trigger this issue on fork.
Fix it by incrementing the user_mapped reference count without re-mapping
the pages in the VMA's open callback.
Affected configurations
• linux linux kernel (>= 6.10.1 < 6.12.77)
• linux linux kernel (>= 6.13 < 6.18.17)
• linux linux kernel (>= 6.19 < 6.19.7)
• linux linux kernel 6.10
• linux linux kernel 7.0
Related
Weakness · CWE (1)
- CWE-617 Reachable Assertion weakness
References
- https://git.kernel.org/stable/c/91f3e8d84c89918769e71393f839c9fefadc2580 Patch
- https://git.kernel.org/stable/c/b0f269ba6fefe9e3cb9feedcf78fcd0b633800c0 Patch
- https://git.kernel.org/stable/c/cdd96641b64297a2db42676f051362b76280a58b Patch
- https://git.kernel.org/stable/c/e39bb9e02b68942f8e9359d2a3efe7d37ae6be0e Patch