Vulnerability-Lookup

GHSA-HG9W-RXWP-FW28

Vulnerability from github – Published: 2026-02-14 18:30 – Updated: 2026-03-18 15:30

Details

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().

Severity

7.8 (High)


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

Show details on source website

JSON

To clipboard

{
  "affected": [],
  "aliases": [
    "CVE-2026-23184"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-416"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-02-14T17:15:56Z",
    "severity": "HIGH"
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nbinder: fix UAF in binder_netlink_report()\n\nOneway transactions sent to frozen targets via binder_proc_transaction()\nreturn a BR_TRANSACTION_PENDING_FROZEN error but they are still treated\nas successful since the target is expected to thaw at some point. It is\nthen not safe to access \u0027t\u0027 after BR_TRANSACTION_PENDING_FROZEN errors\nas the transaction could have been consumed by the now thawed target.\n\nThis is the case for binder_netlink_report() which derreferences \u0027t\u0027\nafter a pending frozen error, as pointed out by the following KASAN\nreport:\n\n  ==================================================================\n  BUG: KASAN: slab-use-after-free in binder_netlink_report.isra.0+0x694/0x6c8\n  Read of size 8 at addr ffff00000f98ba38 by task binder-util/522\n\n  CPU: 4 UID: 0 PID: 522 Comm: binder-util Not tainted 6.19.0-rc6-00015-gc03e9c42ae8f #1 PREEMPT\n  Hardware name: linux,dummy-virt (DT)\n  Call trace:\n   binder_netlink_report.isra.0+0x694/0x6c8\n   binder_transaction+0x66e4/0x79b8\n   binder_thread_write+0xab4/0x4440\n   binder_ioctl+0x1fd4/0x2940\n   [...]\n\n  Allocated by task 522:\n   __kmalloc_cache_noprof+0x17c/0x50c\n   binder_transaction+0x584/0x79b8\n   binder_thread_write+0xab4/0x4440\n   binder_ioctl+0x1fd4/0x2940\n   [...]\n\n  Freed by task 488:\n   kfree+0x1d0/0x420\n   binder_free_transaction+0x150/0x234\n   binder_thread_read+0x2d08/0x3ce4\n   binder_ioctl+0x488/0x2940\n   [...]\n  ==================================================================\n\nInstead, make a transaction copy so the data can be safely accessed by\nbinder_netlink_report() after a pending frozen error. While here, add a\ncomment about not using t-\u003ebuffer in binder_netlink_report().",
  "id": "GHSA-hg9w-rxwp-fw28",
  "modified": "2026-03-18T15:30:41Z",
  "published": "2026-02-14T18:30:16Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-23184"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/5e8a3d01544282e50d887d76f30d1496a0a53562"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/a6050dedb6f1cc23e518e3a132ab74a0aad6df90"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
      "type": "CVSS_V3"
    }
  ]
}

CVE-2026-23184 (GCVE-0-2026-23184)

Vulnerability from cvelistv5 – Published: 2026-02-14 16:27 – Updated: 2026-08-05 12:20

Title

binder: fix UAF in binder_netlink_report()

Summary

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().

Severity

7.8 (High)


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

Assigner

Linux mitre root

References

2 references

URL	Tags
https://git.kernel.org/stable/c/a6050dedb6f1cc23e…
https://git.kernel.org/stable/c/5e8a3d01544282e50…

Impacted products

2 products

Vendor	Product	Version
Linux	Linux	Affected: 63740349eba78f242bcbf60d5244d7f2b2600853 , < a6050dedb6f1cc23e518e3a132ab74a0aad6df90 (git) Affected: 63740349eba78f242bcbf60d5244d7f2b2600853 , < 5e8a3d01544282e50d887d76f30d1496a0a53562 (git)
Linux	Linux	Affected: 6.18 Unaffected: 0 , < 6.18 (semver) Unaffected: 6.18.10 , ≤ 6.18.* (semver) Unaffected: 6.19 , ≤ * (original_commit_for_fix)

Show details on NVD website

JSON

To clipboard

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "drivers/android/binder.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "a6050dedb6f1cc23e518e3a132ab74a0aad6df90",
              "status": "affected",
              "version": "63740349eba78f242bcbf60d5244d7f2b2600853",
              "versionType": "git"
            },
            {
              "lessThan": "5e8a3d01544282e50d887d76f30d1496a0a53562",
              "status": "affected",
              "version": "63740349eba78f242bcbf60d5244d7f2b2600853",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "drivers/android/binder.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "6.18"
            },
            {
              "lessThan": "6.18",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.18.*",
              "status": "unaffected",
              "version": "6.18.10",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "6.19",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.18.10",
                  "versionStartIncluding": "6.18",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.19",
                  "versionStartIncluding": "6.18",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nbinder: fix UAF in binder_netlink_report()\n\nOneway transactions sent to frozen targets via binder_proc_transaction()\nreturn a BR_TRANSACTION_PENDING_FROZEN error but they are still treated\nas successful since the target is expected to thaw at some point. It is\nthen not safe to access \u0027t\u0027 after BR_TRANSACTION_PENDING_FROZEN errors\nas the transaction could have been consumed by the now thawed target.\n\nThis is the case for binder_netlink_report() which derreferences \u0027t\u0027\nafter a pending frozen error, as pointed out by the following KASAN\nreport:\n\n  ==================================================================\n  BUG: KASAN: slab-use-after-free in binder_netlink_report.isra.0+0x694/0x6c8\n  Read of size 8 at addr ffff00000f98ba38 by task binder-util/522\n\n  CPU: 4 UID: 0 PID: 522 Comm: binder-util Not tainted 6.19.0-rc6-00015-gc03e9c42ae8f #1 PREEMPT\n  Hardware name: linux,dummy-virt (DT)\n  Call trace:\n   binder_netlink_report.isra.0+0x694/0x6c8\n   binder_transaction+0x66e4/0x79b8\n   binder_thread_write+0xab4/0x4440\n   binder_ioctl+0x1fd4/0x2940\n   [...]\n\n  Allocated by task 522:\n   __kmalloc_cache_noprof+0x17c/0x50c\n   binder_transaction+0x584/0x79b8\n   binder_thread_write+0xab4/0x4440\n   binder_ioctl+0x1fd4/0x2940\n   [...]\n\n  Freed by task 488:\n   kfree+0x1d0/0x420\n   binder_free_transaction+0x150/0x234\n   binder_thread_read+0x2d08/0x3ce4\n   binder_ioctl+0x488/0x2940\n   [...]\n  ==================================================================\n\nInstead, make a transaction copy so the data can be safely accessed by\nbinder_netlink_report() after a pending frozen error. While here, add a\ncomment about not using t-\u003ebuffer in binder_netlink_report()."
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "baseScore": 7.8,
            "baseSeverity": "HIGH",
            "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
            "version": "3.1"
          },
          "scenarios": [
            {
              "lang": "en",
              "value": "AV:L - Binder is accessed via /dev/binder device file through ioctl(BINDER_WRITE_READ), requiring local system access. It is not reachable over the network.\nAC:L - The attacker controls both sides of the race: they freeze the target via BINDER_FREEZE (no privilege check), send the oneway transaction, then thaw the target to trigger the free. This makes the race reliably triggerable.\nPR:L - Any unprivileged process that can open /dev/binder can trigger this. On Android, any app has binder access. No special capabilities or root privileges are required.\nUI:N - No user interaction is needed. The attacker can trigger the entire sequence (freeze, send transaction, thaw) programmatically without any victim action.\nS:U - This is a standard kernel UAF exploitable for privilege escalation within the same security authority (kernel). No VM escape or sandbox boundary crossing is involved.\nC:H - The UAF allows reading freed kernel heap memory. With heap spraying to control the freed object\u0027s contents, an attacker can achieve arbitrary kernel memory reads.\nI:H - The UAF enables heap spraying the freed binder_transaction object, giving the attacker write primitives and control flow hijacking capability in the kernel.\nA:H - As demonstrated by the KASAN report, accessing freed memory causes a kernel crash. The UAF reliably triggers a kernel oops/panic."
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-08-05T12:20:31.428Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/a6050dedb6f1cc23e518e3a132ab74a0aad6df90"
        },
        {
          "url": "https://git.kernel.org/stable/c/5e8a3d01544282e50d887d76f30d1496a0a53562"
        }
      ],
      "title": "binder: fix UAF in binder_netlink_report()",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2026-23184",
    "datePublished": "2026-02-14T16:27:14.167Z",
    "dateReserved": "2026-01-13T15:37:45.984Z",
    "dateUpdated": "2026-08-05T12:20:31.428Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

Sightings

Author	Source	Type	Date	Other

Nomenclature

Seen: The vulnerability was mentioned, discussed, or observed by the user.
Confirmed: The vulnerability has been validated from an analyst's perspective.
Published Proof of Concept: A public proof of concept is available for this vulnerability.
Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
Not confirmed: The user expressed doubt about the validity of the vulnerability.
Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base model, served locally by ML-Gateway. They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.

Related by attack behaviour

Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.

Action not permitted

GHSA-HG9W-RXWP-FW28

CVE-2026-23184 (GCVE-0-2026-23184)

Tags

Sightings

Nomenclature

Related by attack behaviour