From: Krzysztof Kozlowski <krzk@kernel.org>
To: Jiri Slaby <jirislaby@kernel.org>, Luka <luka.2016.cs@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org
Subject: Re: [Bug] WARNING in vt_do_diacrit in Linux Kernel v6.14
Date: Wed, 9 Jul 2025 09:07:25 +0200 [thread overview]
Message-ID: <b88b5d86-21dc-428c-a514-9030ffd494a1@kernel.org> (raw)
In-Reply-To: <3dfadb7b-fc5f-4165-a5ad-c3802585805e@kernel.org>
On 08/07/2025 10:46, Jiri Slaby wrote:
> 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.
Jiri,
Don't waste time. It's AI generated spam. Same as before.
Best regards,
Krzysztof
prev parent reply other threads:[~2025-07-09 7:07 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
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 [this message]
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=b88b5d86-21dc-428c-a514-9030ffd494a1@kernel.org \
--to=krzk@kernel.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