[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3dfadb7b-fc5f-4165-a5ad-c3802585805e@kernel.org>
Date: Tue, 8 Jul 2025 10:46:34 +0200
From: Jiri Slaby <jirislaby@...nel.org>
To: Luka <luka.2016.cs@...il.com>
Cc: linux-kernel@...r.kernel.org, linux-serial@...r.kernel.org
Subject: Re: [Bug] WARNING in vt_do_diacrit in Linux Kernel v6.14
On 08. 07. 25, 9:21, Luka wrote:
> Dear Linux Kernel Maintainers,
>
> I hope this message finds you well.
>
> I am writing to report a potential vulnerability I encountered during
> testing of the Linux Kernel version v6.14.
>
> Git Commit: 38fec10eb60d687e30c8c6b5420d86e8149f7557 (tag: v6.14)
>
> Bug Location: drivers/tty/vt/keyboard.c
>
> Bug report: https://pastebin.com/yuVJpati
>
> Complete log: https://pastebin.com/qKnipvvK
>
> Entire kernel config: https://pastebin.com/MRWGr3nv
>
> Root Cause Analysis:
> The vt_do_diacrit() function in the virtual terminal subsystem
> performs a write to a user-space pointer via __put_user_4() without
> ensuring that the destination address is mapped and accessible.
> Under conditions such as memory allocation failure or page table
> unavailability, this leads to a fault during execution of the mov
> %eax, (%rcx) instruction.
Which is exactly how it should behave, right? If #PF, then it jumps to
__put_user_handle_exception and returns EFAULT.
regards,
--
js
suse labs
Powered by blists - more mailing lists