]> git.ipfire.org Git - thirdparty/kernel/stable.git/commitdiff
vt: prevent kernel-infoleak in con_font_get()
authorJeongjun Park <aha310510@gmail.com>
Thu, 10 Oct 2024 17:46:19 +0000 (02:46 +0900)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Fri, 8 Nov 2024 15:25:56 +0000 (16:25 +0100)
commit f956052e00de211b5c9ebaa1958366c23f82ee9e upstream.

font.data may not initialize all memory spaces depending on the implementation
of vc->vc_sw->con_font_get. This may cause info-leak, so to prevent this, it
is safest to modify it to initialize the allocated memory space to 0, and it
generally does not affect the overall performance of the system.

Cc: stable@vger.kernel.org
Reported-by: syzbot+955da2d57931604ee691@syzkaller.appspotmail.com
Fixes: 05e2600cb0a4 ("VT: Bump font size limitation to 64x128 pixels")
Signed-off-by: Jeongjun Park <aha310510@gmail.com>
Link: https://lore.kernel.org/r/20241010174619.59662-1-aha310510@gmail.com
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
drivers/tty/vt/vt.c

index 3dc2124bd02ae855a6afe0d5817dbe19391575a0..bd125ea5c51f47a6ae80e33400a889815c844cc5 100644 (file)
@@ -4594,7 +4594,7 @@ static int con_font_get(struct vc_data *vc, struct console_font_op *op)
        int c;
 
        if (op->data) {
-               font.data = kmalloc(max_font_size, GFP_KERNEL);
+               font.data = kzalloc(max_font_size, GFP_KERNEL);
                if (!font.data)
                        return -ENOMEM;
        } else