shmfd/mmap: restrict maxprot with MAP_SHARED + F_SEAL_WRITE
ClosedPublic
Actions

Authored by kevans on Dec 30 2019, 10:58 PM.

Tags

None

Referenced Files

	Unknown Object (File)
	Mon, Oct 20, 10:53 AM

	Unknown Object (File)
	Tue, Oct 14, 7:31 PM

	Unknown Object (File)
	Tue, Oct 14, 7:31 PM

	Unknown Object (File)
	Tue, Oct 14, 7:31 PM

	Unknown Object (File)
	Tue, Oct 14, 8:42 AM

	Unknown Object (File)
	Sun, Oct 12, 7:25 AM

	Unknown Object (File)
	Sat, Oct 11, 7:08 AM

	Unknown Object (File)
	Mon, Sep 22, 7:51 PM

View All 92 Files

Subscribers

imp

Details

Reviewers

kib
trasz

Commits

rS356371: shmfd/mmap: restrict maxprot with MAP_SHARED + F_SEAL_WRITE

Summary

If a write seal is set on a shared mapping, we must exclude VM_PROT_WRITE as the fd is effectively read-only. This was discovered by running devel/linux-ltp, which mmap's with acceptable protections specified then attempts to raise to PROT_READ|PROT_WRITE with mprotect(2), which we allowed.