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)
	Sat, May 9, 6:25 PM

	Unknown Object (File)
	Wed, May 6, 2:08 PM

	Unknown Object (File)
	Wed, May 6, 2:08 PM

	Unknown Object (File)
	Sat, Apr 18, 3:55 PM

	Unknown Object (File)
	Sat, Apr 18, 3:54 PM

	Unknown Object (File)
	Wed, Apr 15, 1:52 PM

	Unknown Object (File)
	Wed, Apr 15, 10:47 AM

	Unknown Object (File)
	Mar 25 2026, 7:25 AM

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