Skip to content
TrackCVE
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • MCP serverPage
  • Data sourcesPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
Back

CVE-2022-49939

binder: fix UAF of ref->proc caused by race condition

High7.8EPSS 0.17%
Published
Updated
Reserved
Assigned by
Linux

Description

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

Timeline

  1. ID reserved

    By Linux

  2. · 48 days later

    Published

  3. · 14 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2022-49939, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Modified3.1High7.0CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.17% · top 93% of all CVEs (7 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Weakness

Affected products

  • Linux · Linux

    • affected 372e3147df7016ebeaa372939e8774a1292db558 – < 229f47603dd306bc0eb1a831439adb8e48bb0eae
    • affected 372e3147df7016ebeaa372939e8774a1292db558 – < 06e5b43ca4dab06a92bf4c2f33766e6fb11b880a
    • affected 372e3147df7016ebeaa372939e8774a1292db558 – < 30d0901b307f27d36b2655fb3048cf31ee0e89c0
    • affected 372e3147df7016ebeaa372939e8774a1292db558 – < 9629f2dfdb1dad294b468038ff8e161e94d0b609
    • affected 372e3147df7016ebeaa372939e8774a1292db558 – < c2a4b5dc8fa71af73bab704d0cac42ac39767ed6
    • affected 372e3147df7016ebeaa372939e8774a1292db558 – < 603a47f2ae56bf68288784d3c0a8c5b8e0a827ed
    • affected 372e3147df7016ebeaa372939e8774a1292db558 – < a0e44c64b6061dda7e00b7c458e4523e2331b739

  • Linux · Linux

    • affected 4.14
    • unaffected < 4.14
    • unaffected 4.14.293 – ≤ 4.14.*
    • unaffected 4.19.258 – ≤ 4.19.*
    • unaffected 5.4.213 – ≤ 5.4.*
    • unaffected 5.10.142 – ≤ 5.10.*
    • unaffected 5.15.66 – ≤ 5.15.*
    • unaffected 5.19.8 – ≤ 5.19.*
    • unaffected 6.0 – ≤ *

References (7)

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2022-49939 badge
[![CVE-2022-49939](https://trackcve.app/badge/CVE-2022-49939.svg)](https://trackcve.app/cve/CVE-2022-49939)

Record last updated .