LiveActive security incident?Get immediate response
CVE Record

CVE-2021-47360: binder: make sure fd closes complete

In the Linux kernel, the following vulnerability has been resolved: binder: make sure fd closes complete During BC_FREE_BUFFER processing, the BINDER_TYPE_FDA object cleanup may close 1 or more fds. The close operations are completed using the task work mechanism -- which means the thread needs to return to userspace or the file object may never be dereferenced -- which can lead to hung processes. Force the binder thread back to userspace if an fd is closed during BC_FREE_BUFFER handling.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This Linux kernel Binder bug can leave file-close cleanup unfinished during buffer release, causing processes to hang. The sources do not provide CVSS, CWE, or confirmed exploitation. Treat it as an availability risk for systems running affected Linux kernels where Binder is enabled or used.

Executive priority

Schedule remediation through normal kernel patching, with higher priority for systems where Binder is active and availability matters. There is no cited evidence of active exploitation, but process hangs can still affect service reliability.

Technical view

During BC_FREE_BUFFER handling, BINDER_TYPE_FDA cleanup may close file descriptors through task work. If the binder thread does not return to userspace, file objects may not be dereferenced, leading to hung processes. The fix forces the binder thread back to userspace when an fd is closed.

Likely exposure

Exposure is most likely on Linux systems using affected kernel versions with the Binder subsystem active. The source lists affected Linux kernel versions including 5.0, 5.4.150, 5.10.70, 5.14.9, and 5.15, but teams should verify distro backports.

Exploitation context

No source in the bundle states active exploitation, public weaponization, or CISA KEV inclusion. The described impact is process hangs from incomplete fd close handling, not data theft or privilege escalation in the provided evidence.

Researcher notes

The record is unusually sparse: no CVSS, CWE, exploit status, or workaround is provided. The core condition is fd cleanup during BC_FREE_BUFFER involving BINDER_TYPE_FDA and task work completion. Validate by code lineage or distro backport status, not version strings alone.

Mitigation direction

  • Upgrade to a kernel build containing the referenced stable fixes.
  • Check Linux distribution advisories for backported Binder fixes.
  • Prioritize systems where Binder is enabled or operationally required.
  • Monitor vendor guidance because no standalone workaround is named.

Validation and detection

  • Inventory running kernel versions across Linux hosts.
  • Confirm whether Binder support is enabled or used on affected systems.
  • Compare deployed kernel source or changelog against referenced stable commits.
  • Review logs and monitoring for unexplained Binder-related process hangs.
Prepared
Confidence
medium
Sources
6

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2021-47360 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
2ADP providers
5Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux80cd795630d6526ba729a089a435bf74a57af927, 80cd795630d6526ba729a089a435bf74a57af927, 80cd795630d6526ba729a089a435bf74a57af927, 80cd795630d6526ba729a089a435bf74a57af927, 27564d8d5d12d2ff197055346069c6bdbe08a8c2unaffected
LinuxLinux5.0, 0, 5.4.150, 5.10.70, 5.14.9, 5.15affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.