lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Tue, 30 Sep 2014 14:31:47 -0700 From: Kamal Mostafa <kamal@...onical.com> To: linux-kernel@...r.kernel.org, stable@...r.kernel.org, kernel-team@...ts.ubuntu.com Cc: David Howells <dhowells@...hat.com>, shemming@...cade.com, paulmck@...ux.vnet.ibm.com, James Morris <james.l.morris@...cle.com>, Kamal Mostafa <kamal@...onical.com> Subject: [PATCH 3.13 102/103] KEYS: Fix use-after-free in assoc_array_gc() 3.13.11.8 -stable review patch. If anyone has any objections, please let me know. ------------------ From: David Howells <dhowells@...hat.com> commit 27419604f51a97d497853f14142c1059d46eb597 upstream. An edit script should be considered inaccessible by a function once it has called assoc_array_apply_edit() or assoc_array_cancel_edit(). However, assoc_array_gc() is accessing the edit script just after the gc_complete: label. Reported-by: Andreea-Cristina Bernat <bernat.ada@...il.com> Signed-off-by: David Howells <dhowells@...hat.com> Reviewed-by: Andreea-Cristina Bernat <bernat.ada@...il.com> cc: shemming@...cade.com cc: paulmck@...ux.vnet.ibm.com Signed-off-by: James Morris <james.l.morris@...cle.com> Signed-off-by: Kamal Mostafa <kamal@...onical.com> --- lib/assoc_array.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/lib/assoc_array.c b/lib/assoc_array.c index 76ae279..f9524b8 100644 --- a/lib/assoc_array.c +++ b/lib/assoc_array.c @@ -1737,7 +1737,7 @@ ascend_old_tree: gc_complete: edit->set[0].to = new_root; assoc_array_apply_edit(edit); - edit->array->nr_leaves_on_tree = nr_leaves_on_tree; + array->nr_leaves_on_tree = nr_leaves_on_tree; return 0; enomem: -- 1.9.1 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists