From: Storm Dragon <stormdragon2976@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Bug with /dev/vcs* devices
Date: Sun, 19 Feb 2023 16:21:46 -0500 [thread overview]
Message-ID: <Y/KS6vdql2pIsCiI@hotmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2096 bytes --]
Howdy,
This is my first time ever submitting a kernel bug, so I apologize if this is the wrong place. As per the instructions I found, I first filed a bug in Arch Linux:
https://bugs.archlinux.org/task/77575
I will add the contents of the response here:
For the record, here are the 2 associated mailing list threads [1][2].
The reason why it affects both LTS and current linux is because it appears a security patch was applied to both trees to fix a UAF (use after free) bug.
If that patch is problematic, you should report it upstream to the kernel folks. Maybe even email the patch author directly. It's this patch [3]. Please let us
know what you find out.
[1] https://lists.archlinux.org/archives/list/arch-general%40lists.archlinux.org/thread/EOSHIVGUZLNAD7BPHSUGOXFYSAFWDYH7/
[2] https://lists.archlinux.org/archives/list/arch-general%40lists.archlinux.org/thread/S6R6UDUMX2LWL4HJ74MFNYOES45UBFLF/
[3] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/tty/vt/vc_screen.c?h=v5.15.94&id=fc9e27f3ba083534b8bbf72ab0f5c810ffdc7d18
----------End Response ----------
Methods for reproducing the bug are included in the link to the bug above. But I will include one of them here as well. As root:
[root@mjollnir ~]# cat /dev/vcsa1
cat: /dev/vcsa1: No such device or address
The contents is displayed very briefly before the No such device or address error.
Thank you,
Storm
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2023-02-19 21:21 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-19 21:21 Storm Dragon [this message]
2023-02-19 22:11 ` Bug with /dev/vcs* devices Randy Dunlap
2023-02-19 23:13 ` Storm Dragon
2023-02-20 6:46 ` [PATCH] vc_screen: don't clobber return value in vcs_read linux
2023-02-20 11:48 ` Jiri Slaby
2023-02-20 16:34 ` Thomas Weißschuh
2023-02-21 13:30 ` George Kennedy
2023-02-21 13:49 ` Thomas Weißschuh
2023-02-21 13:50 ` Greg Kroah-Hartman
2023-02-27 14:20 ` Linux regression tracking (Thorsten Leemhuis)
2023-02-27 19:59 ` George Kennedy
2023-02-28 5:38 ` Linux regression tracking (Thorsten Leemhuis)
2023-02-20 16:06 ` Storm Dragon
2023-03-03 21:12 ` Thomas Weißschuh
2023-03-03 21:46 ` Storm Dragon
2023-03-03 23:25 ` Thomas Weißschuh
2023-03-04 3:30 ` Storm Dragon
2023-03-04 3:42 ` Storm Dragon
2023-03-04 19:58 ` Storm Dragon
2023-03-04 22:33 ` Thomas Weißschuh
2023-03-10 21:32 ` Thomas Weißschuh
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=Y/KS6vdql2pIsCiI@hotmail.com \
--to=stormdragon2976@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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