LiveActive security incident?Get immediate response
CVE Record

CVE-2026-23184: binder: fix UAF in binder_netlink_report()

In the Linux kernel, the following vulnerability has been resolved: binder: fix UAF in binder_netlink_report() Oneway transactions sent to frozen targets via binder_proc_transaction() return a BR_TRANSACTION_PENDING_FROZEN error but they are still treated as successful since the target is expected to thaw at some point. It is then not safe to access 't' after BR_TRANSACTION_PENDING_FROZEN errors as the transaction could have been consumed by the now thawed target. This is the case for binder_netlink_report() which derreferences 't' after a pending frozen error, as pointed out by the following KASAN report: ================================================================== BUG: KASAN: slab-use-after-free in binder_netlink_report.isra.0+0x694/0x6c8 Read of size 8 at addr ffff00000f98ba38 by task binder-util/522 CPU: 4 UID: 0 PID: 522 Comm: binder-util Not tainted 6.19.0-rc6-00015-gc03e9c42ae8f #1 PREEMPT Hardware name: linux,dummy-virt (DT) Call trace: binder_netlink_report.isra.0+0x694/0x6c8 binder_transaction+0x66e4/0x79b8 binder_thread_write+0xab4/0x4440 binder_ioctl+0x1fd4/0x2940 [...] Allocated by task 522: __kmalloc_cache_noprof+0x17c/0x50c binder_transaction+0x584/0x79b8 binder_thread_write+0xab4/0x4440 binder_ioctl+0x1fd4/0x2940 [...] Freed by task 488: kfree+0x1d0/0x420 binder_free_transaction+0x150/0x234 binder_thread_read+0x2d08/0x3ce4 binder_ioctl+0x488/0x2940 [...] ================================================================== Instead, make a transaction copy so the data can be safely accessed by binder_netlink_report() after a pending frozen error. While here, add a comment about not using t->buffer in binder_netlink_report().

HighCVSS 7.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A local user with limited privileges may trigger a Linux Binder kernel memory error and potentially compromise confidentiality, integrity, or system availability. The issue is serious where Binder is enabled and accessible, but the supplied evidence does not establish remote reachability or active exploitation.

Executive priority

Treat as a high-priority kernel update for systems exposing Binder to untrusted local workloads. It is not presently supported as an emergency internet-wide threat because exploitation requires local access and no active exploitation is documented. Use vendor package guidance to resolve version ambiguity.

Technical view

binder_netlink_report() can dereference a transaction after it has been consumed by a thawed target, causing a slab use-after-free. The fix copies the transaction before reporting so its data remains valid. The supplied CVSS 3.1 score is 7.8, with local access, low complexity, low privileges, and no user interaction.

Likely exposure

Exposure is limited to Linux systems running an affected kernel with the Binder subsystem present and usable by local processes. The bundle identifies versions 6.18, 6.18.10, and 6.19 as affected, but does not provide a sufficiently clear version range for broader conclusions.

Exploitation context

CISA KEV status is false, and the supplied sources provide no evidence of exploitation in the wild or a public exploit. KASAN reproduced the use-after-free during Binder transaction processing. Practical exploitability beyond that crash evidence is not established in the bundle.

Researcher notes

The vulnerable path follows BR_TRANSACTION_PENDING_FROZEN: the transaction remains logically successful and may be consumed after the target thaws, while binder_netlink_report() subsequently dereferences it. The patch preserves reportable transaction data through a copy and warns against using t->buffer. No CWE is supplied.

Mitigation direction

  • Apply a vendor-supported kernel containing the referenced upstream or stable fix.
  • Prioritize multi-user or untrusted-workload systems where local processes can access Binder.
  • If patching is delayed, consult distribution guidance for supported mitigations or corrected package versions.
  • Restrict local access and untrusted code execution where operationally feasible.

Validation and detection

  • Record the running kernel version and distribution package revision on each potentially exposed system.
  • Confirm whether Binder is configured, loaded, and accessible to local workloads.
  • Verify the installed kernel contains either referenced fixing commit or a documented vendor backport.
  • After updating, reboot into the corrected kernel and confirm the running version.
  • Review kernel logs for Binder-related KASAN reports, use-after-free warnings, or unexplained crashes.
Prepared
Confidence
medium
Sources
4

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-2026-23184 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
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

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

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.

1CVSS vectors
3Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2026-23184Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

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.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux63740349eba78f242bcbf60d5244d7f2b2600853, 63740349eba78f242bcbf60d5244d7f2b2600853unaffected
LinuxLinux6.18, 0, 6.18.10, 6.19affected
Weakness

CWE details

No CWE listed

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