sched_setaffinity: Validate user memory before reading CPU mask#2145
Merged
francescolavra merged 1 commit intomasterfrom Mar 9, 2026
Merged
sched_setaffinity: Validate user memory before reading CPU mask#2145francescolavra merged 1 commit intomasterfrom
francescolavra merged 1 commit intomasterfrom
Conversation
niklasfemerstrand
approved these changes
Mar 3, 2026
If the CPU mask pointer supplied as argument to sched_setaffinity() is not verified to belong to user memory, a program could pass an arbitrary address and determine from the syscall return value whether that address is mapped as kernel memory, thus defeating KASLR. Add a call to validate_user_memory() before accessing the CPU mask pointer, and to avoid a double validation replace the copy_from_user() call with a direct memory copy.
960e2b8 to
ef2e387
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
If the CPU mask pointer supplied as argument to sched_setaffinity() is not verified to belong to user memory, a program could pass an arbitrary address and determine from the syscall return value whether that address is mapped as kernel memory, thus defeating KASLR.
Add a call to validate_user_memory() before accessing the CPU mask pointer, and to avoid a double validation replace the copy_from_user() call with a direct memory copy.
Issue reported and fix suggested by Niklas Femerstrand (@niklasfemerstrand).