[Clarification] writes to kernel addresses that came from userspace
keescook at chromium.org
Sun Sep 12 14:47:10 EDT 2021
On Sun, Sep 12, 2021 at 06:20:30PM +0200, Len Baker wrote:
> I am taking a look to the issues in the Kernel Self Protection Project 
> and this one  (perform taint-tracking of writes to kernel addresses
> that came from userspace) take my attention. Reading the explanation does
> not make it clear to me where the flaw is.
> [extracted from the KSPP]
> It should be possible to perform taint tracking of addresses in the kernel
> to avoid flaws of the form:
> copy_from_user(object, src, ...);
> memcpy(object.address, something, ...);
> [end of extracted]
> My question is: Why is this scenario a flaw?
I likely didn't give enough context in the Issue tracker. It's not a
flaw on its own, but rather an example of an attack situation if a flaw
were present (e.g. having no sanity-check on "object.address" above).
> If I understand correctly, the copy_from_user() function copies n bytes of
> src (in user space address) to object (in kernel space address). I think
> that it is the correct way to act. Then, in kernel space the object is
> modified. So, I don't see the problem. Sorry if it is a trivial question
> but I can not figure it out on my own.
The trouble is that the address came from userspace and (in this
example) has no validation, etc.
This Issue is about developing methods to perform "taint tracking"
within the kernel to better catch cases where validation is missing.
There is some limited support for this via the "__user" annotation and
the "address spaces" checks that "sparse" does, but that's been rather
limited in scope. Having something more like smatch doing function-graph
analysis would be nice for static analysis, and even better would be
stuff like DataFlowSanitizer, which can do this at runtime.
Hopefully that makes things more clear! I'll go update the issue
>  https://github.com/KSPP/linux/issues
>  https://github.com/KSPP/linux/issues/126
More information about the Kernelnewbies