From: Rodolfo Giometti <giometti@enneenne.com>
To: Hungyu Lin <dennylin0707@gmail.com>
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] pps: require CAP_SYS_TIME to attach N_PPS ldisc
Date: Mon, 9 Nov 2026 10:28:46 +0100 [thread overview]
Message-ID: <43045fee-e8e8-4f42-a535-8354a53680e8@enneenne.com> (raw)
In-Reply-To: <20261107211753.75932-1-dennylin0707@gmail.com>
On 07/11/2026 22:17, Hungyu Lin wrote:
> Any unprivileged user can attach the N_PPS ldisc to a pty, and every
> attach registers a PPS source. At most PPS_MAX_SOURCES (256) sources can
> exist, so such a user can take all of them, after which registering a
> real PPS source fails with -EBUSY.
>
> Require CAP_SYS_TIME to attach N_PPS, the capability that PPS_SETPARAMS
> already needs to configure a source.
>
> Fixes: a0880df0ccde ("pps: serial clients support")
> Cc: stable@vger.kernel.org
Are you sure this is stable material? It changes what a user without
CAP_SYS_TIME can do, also on kernels already in the field.
> Signed-off-by: Hungyu Lin <dennylin0707@gmail.com>
> ---
> drivers/pps/clients/pps-ldisc.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/pps/clients/pps-ldisc.c b/drivers/pps/clients/pps-ldisc.c
> index fa5660f3c4b7..54678f20edd5 100644
> --- a/drivers/pps/clients/pps-ldisc.c
> +++ b/drivers/pps/clients/pps-ldisc.c
> @@ -46,6 +46,9 @@ static int pps_tty_open(struct tty_struct *tty)
> struct pps_device *pps;
> int ret;
>
> + if (!capable(CAP_SYS_TIME))
> + return -EPERM;
> +
Did you check whether this breaks existing setups? Today whoever can
open the serial port can attach N_PPS (e.g. ldattach run by a user in
the dialout group), and with this change they get -EPERM.
Also, is pps_tty_open() called only from TIOCSETD? If it can also be
called when the tty is reopened after a hangup (tty_reopen()?), the
check would be done against whoever reopens the tty, not against
whoever attached N_PPS. Did you consider that case?
As you say, the cheap way to take all the sources is a pty. But can
N_PPS on a pty ever report a pulse? If pps_tty_dcd_change() is never
called there, wouldn't refusing N_PPS on a pty be enough, leaving the
real serial ports as they are today?
> info.owner = THIS_MODULE;
> info.dev = NULL;
> snprintf(info.name, PPS_MAX_NAME_LEN, "%s%d", drv->driver_name, index);
> --
> 2.43.0
Ciao,
Rodolfo
--
GNU/Linux Solutions e-mail: giometti@enneenne.com
Linux Device Driver giometti@linux.it
Embedded Systems phone: +39 349 2432127
UNIX programming
prev parent reply other threads:[~2026-11-09 9:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-07 21:17 Hungyu Lin
2026-11-09 9:28 ` Rodolfo Giometti [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=43045fee-e8e8-4f42-a535-8354a53680e8@enneenne.com \
--to=giometti@enneenne.com \
--cc=akpm@linux-foundation.org \
--cc=dennylin0707@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
all inboxes | Powered by JetHome®