Skip to content

Exposed unhashed kernel memory addresses with slub_debug kernel parameter #73

Description

@nbouchinet-anssi

Usualy hashed kernel memory addresses are exposed unhashed when the slub_debug kernel parameter or the CONFIG_SLUB_DEBUG_ON option are enabled since v5.14.
This is an issue for those who use the slub_debug command line option as a slub sanitizing security feature as recommended by CLIP OS or KSPP.

We should have a way to disable exposure of dumped memory chunks and unhashed kernel adresses when using slub_debug as a security option.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions