Re: [PATCH 4.19 079/276] x86/modules: Avoid breaking W^X while loading modules

2019-05-31 Thread Nadav Amit
> On May 31, 2019, at 3:37 AM, Pavel Machek wrote: > > Hi! > >> [ Upstream commit f2c65fb3221adc6b73b0549fc7ba892022db9797 ] >> >> When modules and BPF filters are loaded, there is a time window in >> which some memory is both writable and executable. An attacker that has >> already found

Re: [PATCH 4.19 079/276] x86/modules: Avoid breaking W^X while loading modules

2019-05-31 Thread Pavel Machek
Hi! > [ Upstream commit f2c65fb3221adc6b73b0549fc7ba892022db9797 ] > > When modules and BPF filters are loaded, there is a time window in > which some memory is both writable and executable. An attacker that has > already found another vulnerability (e.g., a dangling pointer) might be > able to

[PATCH 4.19 079/276] x86/modules: Avoid breaking W^X while loading modules

2019-05-29 Thread Greg Kroah-Hartman
[ Upstream commit f2c65fb3221adc6b73b0549fc7ba892022db9797 ] When modules and BPF filters are loaded, there is a time window in which some memory is both writable and executable. An attacker that has already found another vulnerability (e.g., a dangling pointer) might be able to exploit this