
We prove that fault resolution—the response to page faults, capability violations, and domain termination events—contains no component that is intrinsically privileged. Fault detection requires hardware privilege, but fault resolution does not. Using a formal model of capability-enforced systems, we separate fault handling into detection, which must occur at hardware privilege level 0, and resolution, which can be performed entirely by unprivileged domains holding appropriate authority tokens. We show that all resolution actions reduce to capability-checked memory operations or IPC, and thus do not require ring 0 execution. This yields a fault delegation theorem: the kernel’s role in fault handling can be reduced to O(1), policy-free detection and notification, with all resolution policy migrating to untrusted components without loss of correctness or security. We discuss a prototype implementation on x86-64 hardware and show how this result composes with the NullKernel architecture, in which the kernel is stripped of all policy decisions. This is an exploratory preprint; the model and proofs are under active refinement and feedback is welcome.
Computer security, fault handling, kernel architecture, Operating systems
Computer security, fault handling, kernel architecture, Operating systems
| selected citations These citations are derived from selected sources. This is an alternative to the "Influence" indicator, which also reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically). | 0 | |
| popularity This indicator reflects the "current" impact/attention (the "hype") of an article in the research community at large, based on the underlying citation network. | Average | |
| influence This indicator reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically). | Average | |
| impulse This indicator reflects the initial momentum of an article directly after its publication, based on the underlying citation network. | Average |
