Skip to content

Restrict processes from modifying their own memory mappings#332

Merged
adrelanos merged 1 commit intoKicksecure:masterfrom
raja-grewal:limit_full_force
Dec 3, 2025
Merged

Restrict processes from modifying their own memory mappings#332
adrelanos merged 1 commit intoKicksecure:masterfrom
raja-grewal:limit_full_force

Conversation

@raja-grewal
Copy link
Contributor

This pull request restrict processes from modifying their own memory mappings unless actively done via ptrace() in order to limit self-modification which can trigger exploits.

As per suggested in #330.

Note that this can be futher hardened by never allowing overrides using proc_mem.force_override=never instead.

Changes

Set the proc_mem.force_override=ptrace kernel boot parameter.

Mandatory Checklist

  • Legal agreements accepted. By contributing to this organisation, you acknowledge you have read, understood, and agree to be bound by these these agreements:

Terms of Service, Privacy Policy, Cookie Policy, E-Sign Consent, DMCA, Imprint

Optional Checklist

The following items are optional but might be requested in certain cases.

  • I have tested it locally
  • I have reviewed and updated any documentation if relevant
  • I am providing new code and test(s) for it

@ArrayBolt3
Copy link
Contributor

This seems good. It can break some JIT compilers, but maybe it's rare enough we can live with that. I'll merge it for now, we can revert later if mass havoc occurs.

@ArrayBolt3
Copy link
Contributor

Merged into my arraybolt3/trixie branch.

@adrelanos adrelanos merged commit 2b2d30a into Kicksecure:master Dec 3, 2025
@raja-grewal raja-grewal deleted the limit_full_force branch December 11, 2025 01:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants