Security readout for executives and security teams
Plain-English summary
A race condition in the Linux kernel Binder subsystem can access memory after it has been freed. A low-privileged local user could potentially crash the system or compromise kernel confidentiality and integrity. The issue is rated high severity, but the supplied sources do not establish active exploitation.
Executive priority
Treat this as a high-priority kernel update for systems exposing Binder to untrusted local users. It is less urgent for systems without Binder or without realistic local access, subject to vendor confirmation. There is no supplied evidence of active exploitation, so prioritize based on exposure rather than assuming an ongoing campaign.
Technical view
binder_add_freeze_work() temporarily releases proc->inner_lock while changing lock order. binder_node_release() can then free the current node before its lock is acquired, causing a CWE-416 use-after-free. The fix retains a temporary node reference across the unlocked interval. CVSS 3.1 is 7.8 with local, low-privilege access and no user interaction.
Likely exposure
Exposure requires an affected Linux kernel with the Binder functionality available to a low-privileged local user. Network-only attackers are not directly covered by the supplied CVSS vector. The supplied version data points to Linux 6.12-era builds, but its exact range boundaries are insufficiently clear; confirm applicability with the kernel or distribution vendor.
Exploitation context
The supplied record is not listed in CISA KEV and provides no evidence of exploitation in the wild. Successful abuse requires local low-privileged access and interaction with the vulnerable Binder path. The demonstrated failure was a KASAN-detected slab use-after-free; reliable security impact beyond that is not documented in the bundle.
Researcher notes
The central condition is a lifetime race caused by releasing proc->inner_lock before acquiring node->lock. The remediation adds a temporary reference so the node remains alive. The source bundle contains ambiguous affected-version formatting, so commit ancestry or vendor advisories should determine exposure. A crash signature alone would not establish malicious exploitation.
Mitigation direction
- Install a vendor kernel update that incorporates the cited Binder fixes.
- Confirm the applicable fixed release or backport with your Linux distribution vendor.
- Prioritize systems where untrusted local users can access Binder functionality.
- Restrict unnecessary local access as a temporary compensating control.
Validation and detection
- Inventory kernel versions and vendor patch levels on systems using Binder.
- Confirm whether vendor kernels contain either cited fixing commit or an equivalent backport.
- Determine whether Binder is enabled and accessible to low-privileged local users.
- Review kernel logs for crashes or memory errors involving Binder paths.
- Run vendor-supported regression testing after updating the kernel.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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.
CWE-416: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2024-56556 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- 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
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.
SSVC decision data
CVSS vector scores
2 official scoresWe 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.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9LinuxCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
7.8HighVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Base CVSS 3.1 score
7.8HighVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/stable/c/38fbefeb2c140b581ed7de8117a5c90d6dd89c22CVE reference, Linux
- https://git.kernel.org/stable/c/dc8aea47b928cc153b591b3558829ce42f685074CVE reference, Linux
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Use After Free
Use After Free represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.