All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 74532] New: Sanitize all freed GPU memory
Date: Tue, 04 Feb 2014 19:21:28 +0000	[thread overview]
Message-ID: <bug-74532-502@http.bugs.freedesktop.org/> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1584 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=74532

          Priority: medium
            Bug ID: 74532
          Keywords: security
          Assignee: dri-devel@lists.freedesktop.org
           Summary: Sanitize all freed GPU memory
          Severity: normal
    Classification: Unclassified
                OS: Linux (All)
          Reporter: nikoli@gmx.us
          Hardware: All
            Status: NEW
           Version: unspecified
         Component: General
           Product: DRI

X11 applications are able to get and display in human readable form parts of
closed applications, see:
https://github.com/mpv-player/mpv/issues/521

It means applications like skype can silently send much more data, then you
expect, even when you run them as separate user.

Asked about this security problem in #gentoo-hardened, #radeon and #dri-devel,
summarizing:

0) Currently GPU memory is not sanitized by kernel, nothing enforces and
ensures its sanitizing.

1) https://grsecurity.net Linux kernel patches add ability to sanitize all
freed memory, but they do not affect GPU memory:
https://en.wikibooks.org/wiki/Grsecurity/Appendix/Grsecurity_and_PaX_Configuration_Options#Sanitize_all_freed_memory

2) The only secure place to clean memory is kernel, because if application or X
server crashes, memory will not be erased.

3) Some applications possibly will work slower, so better make sanitizing
configurable by adding build and run time kernel options.

4) Most likely this problem affects opencl too.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 3162 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2014-02-04 19:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-04 19:21 bugzilla-daemon [this message]
2019-10-14 13:20 ` [Bug 74532] Sanitize all freed GPU memory bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-74532-502@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.