CVE-2022-49939
published 2025-06-18CVE-2022-49939: In the Linux kernel, the following vulnerability has been resolved: binder: fix UAF of ref->proc caused by race condition A transaction of type…
PriorityP430high7CVSS 3.1
AVLACHPRLUINSUCHIHAH
EPSS
0.13%
3.1th percentile
In the Linux kernel, the following vulnerability has been resolved:
binder: fix UAF of ref->proc caused by race condition
A transaction of type BINDER_TYPE_WEAK_HANDLE can fail to increment the
reference for a node. In this case, the target proc normally releases
the failed reference upon close as expected. However, if the target is
dying in parallel the call will race with binder_deferred_release(), so
the target could have released all of its references by now leaving the
cleanup of the new failed reference unhandled.
The transaction then ends and the target proc gets released making the
ref->proc now a dangling pointer. Later on, ref->node is closed and we
attempt to take spin_lock(&ref->proc->inner_lock), which leads to the
use-after-free bug reported below. Let's fix this by cleaning up the
failed reference on the spot instead of relying on the target to do so.
BUG: KASAN: use-after-free in _raw_spin_lock+0xa8/0x150
Write of size 4 at addr ffff5ca207094238 by task kworker/1:0/590
CPU: 1 PID: 590 Comm: kworker/1:0 Not tainted 5.19.0-rc8 #10
Hardware name: linux,dummy-virt (DT)
Workqueue: events binder_deferred_func
Call trace:
dump_backtrace.part.0+0x1d0/0x1e0
show_stack+0x18/0x70
dump_stack_lvl+0x68/0x84
print_report+0x2e4/0x61c
kasan_report+0xa4/0x110
kasan_check_range+0xfc/0x1a4
__kasan_check_write+0x3c/0x50
_raw_spin_lock+0xa8/0x150
binder_deferred_func+0x5e0/0x9b0
process_one_work+0x38c/0x5f0
worker_thread+0x9c/0x694
kthread+0x188/0x190
ret_from_fork+0x10/0x20
Affected
20 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 5.19.11-1 (bookworm) | linux 5.19.11-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | >= 372e3147df7016ebeaa372939e8774a1292db558 < 229f47603dd306bc0eb1a831439adb8e48bb0eae | 229f47603dd306bc0eb1a831439adb8e48bb0eae |
| linux | linux | >= 372e3147df7016ebeaa372939e8774a1292db558 < 06e5b43ca4dab06a92bf4c2f33766e6fb11b880a | 06e5b43ca4dab06a92bf4c2f33766e6fb11b880a |
| linux | linux | >= 372e3147df7016ebeaa372939e8774a1292db558 < 30d0901b307f27d36b2655fb3048cf31ee0e89c0 | 30d0901b307f27d36b2655fb3048cf31ee0e89c0 |
| linux | linux | >= 372e3147df7016ebeaa372939e8774a1292db558 < 9629f2dfdb1dad294b468038ff8e161e94d0b609 | 9629f2dfdb1dad294b468038ff8e161e94d0b609 |
| linux | linux | >= 372e3147df7016ebeaa372939e8774a1292db558 < c2a4b5dc8fa71af73bab704d0cac42ac39767ed6 | c2a4b5dc8fa71af73bab704d0cac42ac39767ed6 |
| linux | linux | >= 372e3147df7016ebeaa372939e8774a1292db558 < 603a47f2ae56bf68288784d3c0a8c5b8e0a827ed | 603a47f2ae56bf68288784d3c0a8c5b8e0a827ed |
| linux | linux | >= 372e3147df7016ebeaa372939e8774a1292db558 < a0e44c64b6061dda7e00b7c458e4523e2331b739 | a0e44c64b6061dda7e00b7c458e4523e2331b739 |
| linux | linux_kernel | < 4.14.293 | 4.14.293 |
| linux | linux_kernel | — | — |
| linux | linux_kernel | >= 0 < 5.10.148-1 | 5.10.148-1 |
| linux | linux_kernel | >= 0 < 5.19.11-1 | 5.19.11-1 |
| linux | linux_kernel | >= 0 < 5.19.11-1 | 5.19.11-1 |
| linux | linux_kernel | >= 0 < 5.19.11-1 | 5.19.11-1 |
| linux | linux_kernel | >= 4.15 < 4.19.258 | 4.19.258 |
| linux | linux_kernel | >= 4.20 < 5.4.213 | 5.4.213 |
| linux | linux_kernel | >= 5.11 < 5.15.66 | 5.15.66 |
| linux | linux_kernel | >= 5.16 < 5.19.8 | 5.19.8 |
| linux | linux_kernel | >= 5.5 < 5.10.142 | 5.10.142 |
CVSS provenance
nvdv3.17.0HIGHCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
osv7.0HIGH
vendor_debian7.0HIGH
vendor_redhat7.0HIGH
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
GHSA-6q3v-9ww3-wjw7: In the Linux kernel, the following vulnerability has been resolved:
binder: fix UAF of ref->proc caused by race condition
A transaction of type BIND
ghsa_unreviewed·2025-06-18
CVE-2022-49939 [HIGH] CWE-362 GHSA-6q3v-9ww3-wjw7: In the Linux kernel, the following vulnerability has been resolved:
binder: fix UAF of ref->proc caused by race condition
A transaction of type BIND
In the Linux kernel, the following vulnerability has been resolved:
binder: fix UAF of ref->proc caused by race condition
A transaction of type BINDER_TYPE_WEAK_HANDLE can fail to increment the
reference for a node. In this case, the target proc normally releases
the failed reference upon close as expected. However, if the target is
dying in parallel the call will race with binder_deferred_release(), so
the target could have released all of its references by now leaving the
cleanup of the new failed reference unhandled.
The transaction then ends and the target proc gets released making the
ref->proc now a dangling pointer. Later on, ref->node is closed and we
attempt to take spin_lock(&ref->proc->inner_lock), which leads to the
use-after-free bug reported below. Let's fix this by cleani
OSV
CVE-2022-49939: In the Linux kernel, the following vulnerability has been resolved: binder: fix UAF of ref->proc caused by race condition A transaction of type BINDER
osv·2025-06-18·CVSS 7.0
CVE-2022-49939 [HIGH] CVE-2022-49939: In the Linux kernel, the following vulnerability has been resolved: binder: fix UAF of ref->proc caused by race condition A transaction of type BINDER
In the Linux kernel, the following vulnerability has been resolved: binder: fix UAF of ref->proc caused by race condition A transaction of type BINDER_TYPE_WEAK_HANDLE can fail to increment the reference for a node. In this case, the target proc normally releases the failed reference upon close as expected. However, if the target is dying in parallel the call will race with binder_deferred_release(), so the target could have released all of its references by now leaving the cleanup of the new failed reference unhandled. The transaction then ends and the target proc gets released making the ref->proc now a dangling pointer. Later on, ref->node is closed and we attempt to take spin_lock(&ref->proc->inner_lock), which leads to the use-after-free bug reported below. Let's fix this by cleaning
Red Hat
kernel: binder: fix UAF of ref->proc caused by race condition
vendor_redhat·2025-06-18·CVSS 7.0
CVE-2022-49939 [HIGH] kernel: binder: fix UAF of ref->proc caused by race condition
kernel: binder: fix UAF of ref->proc caused by race condition
In the Linux kernel, the following vulnerability has been resolved:
binder: fix UAF of ref->proc caused by race condition
A transaction of type BINDER_TYPE_WEAK_HANDLE can fail to increment the
reference for a node. In this case, the target proc normally releases
the failed reference upon close as expected. However, if the target is
dying in parallel the call will race with binder_deferred_release(), so
the target could have released all of its references by now leaving the
cleanup of the new failed reference unhandled.
The transaction then ends and the target proc gets released making the
ref->proc now a dangling pointer. Later on, ref->node is closed and we
attempt to take spin_lock(&ref->proc->inner_lock), which leads to the
Debian
CVE-2022-49939: linux - In the Linux kernel, the following vulnerability has been resolved: binder: fix...
vendor_debian·2022·CVSS 7.0
CVE-2022-49939 [HIGH] CVE-2022-49939: linux - In the Linux kernel, the following vulnerability has been resolved: binder: fix...
In the Linux kernel, the following vulnerability has been resolved: binder: fix UAF of ref->proc caused by race condition A transaction of type BINDER_TYPE_WEAK_HANDLE can fail to increment the reference for a node. In this case, the target proc normally releases the failed reference upon close as expected. However, if the target is dying in parallel the call will race with binder_deferred_release(), so the target could have released all of its references by now leaving the cleanup of the new failed reference unhandled. The transaction then ends and the target proc gets released making the ref->proc now a dangling pointer. Later on, ref->node is closed and we attempt to take spin_lock(&ref->proc->inner_lock), which leads to the use-after-free bug reported below. Let's fix this by cleaning
No detection rules found.
No public exploits indexed.
https://git.kernel.org/stable/c/06e5b43ca4dab06a92bf4c2f33766e6fb11b880ahttps://git.kernel.org/stable/c/229f47603dd306bc0eb1a831439adb8e48bb0eaehttps://git.kernel.org/stable/c/30d0901b307f27d36b2655fb3048cf31ee0e89c0https://git.kernel.org/stable/c/603a47f2ae56bf68288784d3c0a8c5b8e0a827edhttps://git.kernel.org/stable/c/9629f2dfdb1dad294b468038ff8e161e94d0b609https://git.kernel.org/stable/c/a0e44c64b6061dda7e00b7c458e4523e2331b739https://git.kernel.org/stable/c/c2a4b5dc8fa71af73bab704d0cac42ac39767ed6
2025-06-18
Published