Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2023-52609: binder: fix race between mmput() and do_exit()

Noroxi assessment

Priority: Monitor (action score 18/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.18% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
  • Fixed version: Linux Linux 252a2a5569eb9f8d16428872cc24dea1ac0bb097, 6696f76c32ff67fec26823fc2df46498e70d9bf3, 67f16bf2cc1698fd50e01ee8a2becc5a8e6d3a3e.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 252a2a5569eb9f8d16428872cc24dea1ac0bb097, 6696f76c32ff67fec26823fc2df46498e70d9bf3, 67f16bf2cc1698fd50e01ee8a2becc5a8e6d3a3e or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

MediumCVSS 4.7 · v3.1—No exploit Fix available
Published
Mar 18, 2024
Updated
Jun 17, 2026
EPSS
0.1% · 8th percentile

Report tools

JSON

Action score

18

Monitor

Low priority for now.

CVSS
18 / 40 · 4.7 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2023-52609

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel
debiandebian linux

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • debian debian linux10.0
  • linux linux kernel4.20 and later · before 5.4.268
  • linux linux kernel5.5 and later · before 5.10.209
  • linux linux kernel5.11 and later · before 5.15.148
  • linux linux kernel2.6.29 and later · before 4.19.306
  • linux linux kernel6.2 and later · before 6.6.14
  • linux linux kernel6.7 and later · before 6.7.2
  • linux linux kernel5.16 and later · before 6.1.75

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 2.6.29affected
    • 457b9a6f09f011ebcb9b52cc203a6331a6fc2de7 and later · before 95b1d336b0642198b56836b89908d07b9a0c9608affected · git
    • 457b9a6f09f011ebcb9b52cc203a6331a6fc2de7 and later · before 252a2a5569eb9f8d16428872cc24dea1ac0bb097affected · git
    • 457b9a6f09f011ebcb9b52cc203a6331a6fc2de7 and later · before 7e7a0d86542b0ea903006d3f42f33c4f7ead6918affected · git
    • 457b9a6f09f011ebcb9b52cc203a6331a6fc2de7 and later · before 98fee5bee97ad47b527a997d5786410430d1f0e9affected · git
    • 457b9a6f09f011ebcb9b52cc203a6331a6fc2de7 and later · before 6696f76c32ff67fec26823fc2df46498e70d9bf3affected · git
    • 457b9a6f09f011ebcb9b52cc203a6331a6fc2de7 and later · before 67f16bf2cc1698fd50e01ee8a2becc5a8e6d3a3eaffected · git
    • 457b9a6f09f011ebcb9b52cc203a6331a6fc2de7 and later · before 77d210e8db4d61d43b2d16df66b1ec46fad2ee01affected · git
    • 457b9a6f09f011ebcb9b52cc203a6331a6fc2de7 and later · before 9a9ab0d963621d9d12199df9817e66982582d5a5affected · git
    • before 2.6.29not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.76-16.1.76-1
Debian:13linuxbefore 6.6.15-16.6.15-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2021-47134Mar 15, 2024 · efi/fdt: fix panic when no valid fdt found
    22Monitor
  • ← EarlierCVE-2021-47135Mar 15, 2024 · mt76: mt7921: fix possible AOOB issue in mt7921_mcu_tx_rate_report
    31Monitor
  • Later →CVE-2023-52610Mar 18, 2024 · net/sched: act_ct: fix skb leak and crash on ooo frags
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux252a2a5569eb9f8d16428872cc24dea1ac0bb097Vendor (CNA)
Linux Linux6696f76c32ff67fec26823fc2df46498e70d9bf3Vendor (CNA)
Linux Linux67f16bf2cc1698fd50e01ee8a2becc5a8e6d3a3eVendor (CNA)
Linux Linux77d210e8db4d61d43b2d16df66b1ec46fad2ee01Vendor (CNA)
Linux Linux7e7a0d86542b0ea903006d3f42f33c4f7ead6918Vendor (CNA)
Linux Linux95b1d336b0642198b56836b89908d07b9a0c9608Vendor (CNA)
Linux Linux98fee5bee97ad47b527a997d5786410430d1f0e9Vendor (CNA)
Linux Linux9a9ab0d963621d9d12199df9817e66982582d5a5Vendor (CNA)
debian:linux6.1.76-1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
High
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

CWE-362 · Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')

CVSS vector

CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (9 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records