mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kuznet@ms2.inr.ac.ru
To: alan@lxorguk.UKuu.ORG.UK (Alan Cox)
Cc: linux-kernel@vger.kernel.org
Subject: Re: Local root exploit with kmod and modutils > 2.1.121
Date: Thu, 16 Nov 2000 20:05:05 +0300 (MSK)	[thread overview]
Message-ID: <200011161705.UAA03238@ms2.inr.ac.ru> (raw)
In-Reply-To: <E13wRWU-0007yG-00@the-village.bc.nu> from "Alan Cox" at Nov 16, 0 07:15:02 pm

Hello!

> > request_module has the same effect as running suid.  dev_load() can
> > take the interface name and pass it to modprobe unchanged and modprobe
> > does not verify its input, it trusts root/kernel.
> 
> Then dev_load is being called the wrong way. In older kernels we explicitly
> only did a dev_load with user passed names providing suser() was true.

It checks CAP_SYS_MODULE nowadays.

Which does not look good by the way, it is function of request_module(),
rather than of caller.

Alexey
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2000-11-16 17:35 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.21.0011131915240.19775-100000@ferret.lmh.ox.ac.uk>
2000-11-13 23:11 ` Keith Owens
2000-11-16 16:04   ` Alan Cox
2000-11-16 17:05     ` kuznet [this message]
2000-11-16 17:19       ` Alan Cox
2000-11-16 17:32         ` kuznet
2000-11-16 18:24           ` Alan Cox
2000-11-16 18:56             ` kuznet
2000-11-16 19:08               ` [PATCH] " Xavier Bestel
2000-11-16 20:24     ` Keith Owens
2000-11-16 21:45       ` Alan Cox
2000-11-14 20:31 Adam J. Richter
2000-11-14 22:50 ` Keith Owens
  -- strict thread matches above, loose matches on Subject: below --
2000-11-13 10:57 Keith Owens

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=200011161705.UAA03238@ms2.inr.ac.ru \
    --to=kuznet@ms2.inr.ac.ru \
    --cc=alan@lxorguk.UKuu.ORG.UK \
    --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®