Commit 52b111e
committed
executor: disable /dev/[k]?mem access through CAP_SYS_RAWIO
Currently, syz-kconf disables CONFIG_DEVMEM and CONFIG_DEVKMEM but on
some setups, these nodes might be needed by various system daemons. To
allow these daemons to work while fuzzing, we need to re-enable those
CONFIGs.
On the other hand, we really don't want fuzzing to break the machine by
accessing these nodes. Since their access is guarded by a capability, we
can have syz-executor drop that capability as part of the shared
"drop_caps()" logic. That capability has a slightly larger scope than
guarding /dev/mem and /dev/kmem but it seems to me that the rest is all
equally risky and could break the system in all sorts of unexpected way
so dropping the capability seems to be the right thing to do anyway.1 parent bf27483 commit 52b111e
2 files changed
+6
-9
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
190 | 190 | | |
191 | 191 | | |
192 | 192 | | |
193 | | - | |
194 | | - | |
195 | | - | |
196 | | - | |
197 | | - | |
198 | | - | |
199 | | - | |
200 | | - | |
201 | 193 | | |
202 | 194 | | |
203 | 195 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
4166 | 4166 | | |
4167 | 4167 | | |
4168 | 4168 | | |
4169 | | - | |
| 4169 | + | |
| 4170 | + | |
| 4171 | + | |
| 4172 | + | |
| 4173 | + | |
| 4174 | + | |
4170 | 4175 | | |
4171 | 4176 | | |
4172 | 4177 | | |
| |||
0 commit comments