Files
systemd/src/test
Christian Brauner 9b62fd169e Extend W^X memory protection mechanism for RestrictFileSystemAccess (#43511)
Currently `RestrictFileSystemAccess` isn't trying hard enough to enforce
W^X and thus there are still places where an executable and writable
mapping can be created:

* `/proc/<pid>/mem` `FOLL_FORCE` writes
* `PTRACE_POKE{TEXT,DATA}` `FOLL_FORCE` writes
* `MAP_PRIVATE | MAP_EXECUTABLE` memory mappings

Let's block all of these mechanisms. Do note that
`RestrictFileSystemAccess` is still in very active development and also
cannot meaningfully be used on general purpose distros and systems.

Signed-off-by: Christian Brauner (Amutable) <brauner@kernel.org>
2026-09-01 07:12:13 +02:00
..
2025-05-21 10:49:42 +02:00
2025-05-21 10:49:42 +02:00
2025-05-21 10:49:42 +02:00
2025-05-21 10:49:42 +02:00
2025-05-21 10:49:42 +02:00
2026-06-05 04:42:14 +09:00
2025-05-21 10:49:42 +02:00
2025-05-21 10:49:42 +02:00
2025-05-21 10:49:42 +02:00
2025-05-21 10:49:42 +02:00
2025-05-21 10:49:42 +02:00
2025-05-21 10:49:42 +02:00
2025-05-21 10:49:42 +02:00
2026-01-05 21:29:52 +09:00
2025-05-21 10:49:42 +02:00
2025-05-21 10:49:42 +02:00
2025-05-21 10:49:42 +02:00
2026-07-15 12:12:40 +02:00
2025-04-30 09:30:51 +02:00
2025-05-21 10:49:42 +02:00
2025-05-21 10:49:42 +02:00
2025-08-20 16:17:11 +09:00
2025-09-05 15:14:49 +02:00
2025-09-24 15:45:28 +02:00
2025-05-21 10:49:42 +02:00
2025-05-21 10:49:42 +02:00
2026-06-17 13:11:15 +01:00
2026-04-11 14:58:34 +02:00
2025-05-21 10:49:42 +02:00
2025-04-30 09:30:51 +02:00
2026-02-19 15:08:20 +01:00
2025-07-26 05:00:02 +09:00
2025-05-21 10:49:42 +02:00
2025-05-21 10:49:42 +02:00
2025-05-21 10:49:42 +02:00
2025-05-21 10:49:42 +02:00
2025-05-21 10:49:42 +02:00
2025-05-21 10:49:42 +02:00
2026-08-13 13:21:28 -05:00
2025-05-21 10:49:42 +02:00
2025-05-21 10:49:42 +02:00
2025-05-21 10:49:42 +02:00
2025-05-21 10:49:42 +02:00
2026-07-13 15:39:17 +02:00
2026-08-20 15:30:20 +02:00
2025-05-21 10:49:42 +02:00
2025-05-21 10:49:42 +02:00
2025-05-21 10:49:42 +02:00