From: Gen Zhang <blackgod016...@gmail.com>

[ Upstream commit 84ecc2f6eb1cb12e6d44818f94fa49b50f06e6ac ]

In function con_insert_unipair(), when allocation for p2 and p1[n]
fails, ENOMEM is returned, but previously allocated p1 is not freed,
remains as leaking memory. Thus we should free p1 as well when this
allocation fails.

Signed-off-by: Gen Zhang <blackgod016...@gmail.com>
Reviewed-by: Kees Cook <keesc...@chromium.org>
Signed-off-by: Greg Kroah-Hartman <gre...@linuxfoundation.org>
Signed-off-by: Sasha Levin <sas...@kernel.org>
---
 drivers/tty/vt/consolemap.c | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/drivers/tty/vt/consolemap.c b/drivers/tty/vt/consolemap.c
index 7c7ada0b3ea0..814d1b7967ae 100644
--- a/drivers/tty/vt/consolemap.c
+++ b/drivers/tty/vt/consolemap.c
@@ -489,7 +489,11 @@ con_insert_unipair(struct uni_pagedir *p, u_short unicode, 
u_short fontpos)
        p2 = p1[n = (unicode >> 6) & 0x1f];
        if (!p2) {
                p2 = p1[n] = kmalloc_array(64, sizeof(u16), GFP_KERNEL);
-               if (!p2) return -ENOMEM;
+               if (!p2) {
+                       kfree(p1);
+                       p->uni_pgdir[n] = NULL;
+                       return -ENOMEM;
+               }
                memset(p2, 0xff, 64*sizeof(u16)); /* No glyphs for the 
characters (yet) */
        }
 
-- 
2.20.1

Reply via email to