FKIE_CVE-2026-23184
Vulnerability from fkie_nvd - Published: 2026-02-14 17:15 - Updated: 2026-02-18 17:52
Severity ?
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().
References
Impacted products
| Vendor | Product | Version |
|---|
{
"cveTags": [],
"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()."
},
{
"lang": "es",
"value": "En el kernel de Linux, la siguiente vulnerabilidad ha sido resuelta:\n\nbinder: corregir UAF en binder_netlink_report()\n\nLas transacciones unidireccionales enviadas a objetivos congelados a trav\u00e9s de binder_proc_transaction() devuelven un error BR_TRANSACTION_PENDING_FROZEN pero a\u00fan se tratan como exitosas ya que se espera que el objetivo se descongele en alg\u00fan momento. Por lo tanto, no es seguro acceder a \u0027t\u0027 despu\u00e9s de errores BR_TRANSACTION_PENDING_FROZEN, ya que la transacci\u00f3n podr\u00eda haber sido consumida por el objetivo ahora descongelado.\n\nEste es el caso de binder_netlink_report() que desreferencia \u0027t\u0027 despu\u00e9s de un error de congelaci\u00f3n pendiente, como lo se\u00f1ala el siguiente informe KASAN:\n\n ==================================================================\n ERROR: KASAN: uso despu\u00e9s de liberaci\u00f3n de slab en binder_netlink_report.isra.0+0x694/0x6c8\n Lectura de tama\u00f1o 8 en la direcci\u00f3n ffff00000f98ba38 por la tarea binder-util/522\n\n CPU: 4 UID: 0 PID: 522 Comm: binder-util No contaminado 6.19.0-rc6-00015-gc03e9c42ae8f #1 PREEMPT\n Nombre del hardware: linux,dummy-virt (DT)\n Rastro de llamada:\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 Asignado por la tarea 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 Liberado por la tarea 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\nEn su lugar, haga una copia de la transacci\u00f3n para que los datos puedan ser accedidos de forma segura por binder_netlink_report() despu\u00e9s de un error de congelaci\u00f3n pendiente. Ya que estamos, a\u00f1ada un comentario sobre no usar t-\u0026gt;buffer en binder_netlink_report()."
}
],
"id": "CVE-2026-23184",
"lastModified": "2026-02-18T17:52:22.253",
"metrics": {},
"published": "2026-02-14T17:15:56.167",
"references": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/5e8a3d01544282e50d887d76f30d1496a0a53562"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/a6050dedb6f1cc23e518e3a132ab74a0aad6df90"
}
],
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"vulnStatus": "Awaiting Analysis"
}
Loading…
Loading…
Sightings
| Author | Source | Type | Date |
|---|
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.
Loading…
Loading…