From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Sasha Levin <sashal@kernel.org>,
deller@gmx.de, dri-devel@lists.freedesktop.org,
linux-fbdev@vger.kernel.org, mlbnkm1@gmail.com, simona@ffwll.ch,
Artem Dinaburg <artem@trailofbits.com>
Subject: Re: [6.18.y] Please pick three fbdev mode-sysfs fixes
Date: Sat, 21 Nov 2026 10:27:34 -0500 [thread overview]
Message-ID: <2026-11-21-1-daily-reply-0006@kernel.org> (raw)
In-Reply-To: <20261120201003.42046-1-artem@trailofbits.com>
> Please pick these fbdev fixes for 6.18.y, in this order:
>
> d15d51fb26e830af58f3f21964f1c09c239077ea (CVE-2026-80580)
> ("fbdev: bound mode sysfs output to the sysfs buffer")
> 95e647d2a5304a8fd11f1ba3c8502de700650131 (CVE-2026-80579)
> ("fbdev: clear fb_info->mode before deleting a videomode")
> 061db6b7a910b8378f3b2df64f8c0a3ddc6e85f2 (CVE-2026-80785)
> ("fbdev: serialize mode sysfs access with lock_fb_info()")
Queued for 6.18, thanks.
--
Thanks,
Sasha
prev parent reply other threads:[~2026-11-21 15:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-20 20:10 [6.18.y] Please pick three fbdev mode-sysfs fixes Artem Dinaburg
2026-11-21 15:27 ` Sasha Levin [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=2026-11-21-1-daily-reply-0006@kernel.org \
--to=sashal@kernel.org \
--cc=artem@trailofbits.com \
--cc=deller@gmx.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=mlbnkm1@gmail.com \
--cc=simona@ffwll.ch \
--cc=stable@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