[kernel-hardening] [PATCH 4/6] Protectable Memory

From
Igor Stoppa <hidden>
Date
2018-01-26 12:28:11
Also in
linux-mm, lkml
Reply to
Jerome Glisse, 2018-01-25
On 25/01/18 17:38, Jerome Glisse wrote:
On Thu, Jan 25, 2018 at 10:14:28AM -0500, Boris Lukashev wrote:
quoted
On Thu, Jan 25, 2018 at 6:59 AM, Igor Stoppa [off-list ref] wrote:
[...]
quoted
DMA/physmap access coupled with a knowledge of which virtual mappings
are in the physical space should be enough for an attacker to bypass
the gating mechanism this work imposes. Not trivial, but not
impossible. Since there's no way to prevent that sort of access in
current hardware (especially something like a NIC or GPU working
independently of the CPU altogether)
[...]
I am not saying that this can not happen but that we are trying our best
to avoid it.
How about an opt-in verification, similar to what proposed by Boris
Lukashev?

When reading back the data, one could access the pointer directly and
bypass the verification, or could use a function that explicitly checks
the integrity of the data.

Starting from an unprotected kmalloc allocation, even just turning the
data into R/O is an improvement, but if one can afford the overhead of
performing the verification, why not?

It would still be better if the service was provided by the library,
instead than implemented by individual users, I think.

--
igor
--
To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Thread (44 messages) 44 messages, 11 authors, last reply 2018-02-21
Keyboard shortcuts
hback out one level
jnext message in thread / next series-diff position
kprevious message in thread / previous series-diff position
ldrill in
Escclose help / fold thread tree
?toggle this help