lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Sun, 8 Nov 2009 18:01:57 +0100
From:	Pavel Machek <>
To:	"Eric W. Biederman" <>
Cc:	Miklos Szeredi <>,,,,,,,,,,,,
Subject: Re: [PATCH v2 resend] vfs: new O_NODE open flag


> > The only really weird case Alan spotted is device nodes, where the
> > actual device registered to a major/minor pair changes over time,
> > possibly allowing a re-open to access a device it otherwise was not
> > meant to.  BTW if the device number reuse happens really quickly, this
> > could even be a race for a plain open.  Real solution might actually
> > be in udev: when deregistering a device, change mode bits to all-zero
> > before removing the device node.
> Devices nodes specifically were the case I was thinking of.
> Changing the mode bits to all-zero at the final unlink would be a lot
> more reliable and certain in the kernel.

Does it really close the race completely?

					udev sets 660
open does permission checks
					device disappears
					chmod 000
					new device appears
					udev chmods 600
open returns new device


(cesky, pictures)
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists