Skip to content

Place syscall table in read-only memory #1409

@georgeklees

Description

@georgeklees

Right now, syscall registration is dynamic, with the init() functions for various executive subsystems registering their own syscalls. While it may make the code a bit cleaner, it is also a fairly important security problem. A kernel vulnerability that allows arbitrary write access could allow an attacker to put internal kernel functions in the syscall table, and gain kernel ROP or bypass security checks. In order to prevent this kind of attack, the syscall table needs to be made read-only and statically declared at compile time.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions