Skip to content
CVE Tracker
  • 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-2023-52609

binder: fix race between mmput() and do_exit()

Medium4.7EPSS 0.18%
Published
Updated
Reserved
Assigned by
Linux

Description

In the Linux kernel, the following vulnerability has been resolved: binder: fix race between mmput() and do_exit() Task A calls binder_update_page_range() to allocate and insert pages on a remote address space from Task B. For this, Task A pins the remote mm via mmget_not_zero() first. This can race with Task B do_exit() and the final mmput() refcount decrement will come from Task A. Task A | Task B ------------------+------------------ mmget_not_zero() | | do_exit() | exit_mm() | mmput() mmput() | exit_mmap() | remove_vma() | fput() | In this case, the work of ____fput() from Task B is queued up in Task A as TWA_RESUME. So in theory, Task A returns to userspace and the cleanup work gets executed. However, Task A instead sleep, waiting for a reply from Task B that never comes (it's dead). This means the binder_deferred_release() is blocked until an unrelated binder event forces Task A to go back to userspace. All the associated death notifications will also be delayed until then. In order to fix this use mmput_async() that will schedule the work in the corresponding mm->async_put_work WQ instead of Task A.

Scores

CVSS scores of CVE-2023-52609, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium4.7CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.18% · top 92% of all CVEs (7 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

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

Weakness

Affected products

  • Linux · Linux

    • affected 457b9a6f09f011ebcb9b52cc203a6331a6fc2de7 – < 95b1d336b0642198b56836b89908d07b9a0c9608
    • affected 457b9a6f09f011ebcb9b52cc203a6331a6fc2de7 – < 252a2a5569eb9f8d16428872cc24dea1ac0bb097
    • affected 457b9a6f09f011ebcb9b52cc203a6331a6fc2de7 – < 7e7a0d86542b0ea903006d3f42f33c4f7ead6918
    • affected 457b9a6f09f011ebcb9b52cc203a6331a6fc2de7 – < 98fee5bee97ad47b527a997d5786410430d1f0e9
    • affected 457b9a6f09f011ebcb9b52cc203a6331a6fc2de7 – < 6696f76c32ff67fec26823fc2df46498e70d9bf3
    • affected 457b9a6f09f011ebcb9b52cc203a6331a6fc2de7 – < 67f16bf2cc1698fd50e01ee8a2becc5a8e6d3a3e
    • affected 457b9a6f09f011ebcb9b52cc203a6331a6fc2de7 – < 77d210e8db4d61d43b2d16df66b1ec46fad2ee01
    • affected 457b9a6f09f011ebcb9b52cc203a6331a6fc2de7 – < 9a9ab0d963621d9d12199df9817e66982582d5a5
  • Linux · Linux

    • affected 2.6.29
    • unaffected < 2.6.29
    • unaffected 4.19.306 – ≤ 4.19.*
    • unaffected 5.4.268 – ≤ 5.4.*
    • unaffected 5.10.209 – ≤ 5.10.*
    • unaffected 5.15.148 – ≤ 5.15.*
    • unaffected 6.1.75 – ≤ 6.1.*
    • unaffected 6.6.14 – ≤ 6.6.*
    • unaffected 6.7.2 – ≤ 6.7.*
    • unaffected 6.8 – ≤ *

References (10)

Sources

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

Badge for a README or a ticket

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

Record last updated .