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)
	Tue, Apr 16, 4:58 PM

	Unknown Object (File)
	Tue, Apr 16, 3:44 PM

	Unknown Object (File)
	Tue, Apr 16, 3:43 PM

	Unknown Object (File)
	Tue, Apr 16, 2:27 PM

	Unknown Object (File)
	Tue, Apr 16, 2:05 PM

	Unknown Object (File)
	Tue, Apr 16, 12:09 PM

	Unknown Object (File)
	Tue, Apr 16, 9:08 AM

	Unknown Object (File)
	Feb 28 2024, 1:48 PM

View All 31 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.