From: Greg KH <gregkh@linuxfoundation.org>
To: Luka <luka.2016.cs@gmail.com>
Cc: Jiri Slaby <jirislaby@kernel.org>,
linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org
Subject: Re: [Bug] WARNING in vt_do_diacrit in Linux Kernel v6.14
Date: Tue, 8 Jul 2025 09:49:01 +0200 [thread overview]
Message-ID: <2025070805-stoning-overeager-39f1@gregkh> (raw)
In-Reply-To: <CALm_T+2AUcGgb+ukfGg5a3=ibQzRe93gHAzjh6XUubCePk=Mig@mail.gmail.com>
On Tue, Jul 08, 2025 at 03:21:36PM +0800, 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.
Where? I see calls to put_user() happening in that function, and the
return value is properly checked. What lines exactly show the issue?
> Under conditions such as memory allocation failure or page table
> unavailability, this leads to a fault during execution of the mov
> %eax, (%rcx) instruction.
Again, a normal call to put_user() should be catching this. Are you
sure you are looking at the latest kernel tree?
> At present, I have not yet obtained a minimal reproducer for this
> issue. However, I am actively working on reproducing it, and I will
> promptly share any additional findings or a working reproducer as soon
> as it becomes available.
Please do.
thanks,
greg k-h
next prev parent reply other threads:[~2025-07-08 7:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-08 7:21 [Bug] WARNING in vt_do_diacrit in Linux Kernel v6.14 Luka
2025-07-08 7:49 ` Greg KH [this message]
2025-07-09 7:07 ` Krzysztof Kozlowski
2025-07-09 10:15 ` Greg KH
2025-07-08 8:46 ` Jiri Slaby
2025-07-09 7:07 ` Krzysztof Kozlowski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2025070805-stoning-overeager-39f1@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=luka.2016.cs@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox