All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guennadi Liakhovetski <guennadi.liakhovetski@linux.intel.com>
To: alsa-devel@alsa-project.org
Subject: [alsa-devel] what's the kernel policy WRT firmware parsing security?
Date: Sun, 6 Oct 2019 12:47:15 +0200	[thread overview]
Message-ID: <20191006104715.GA14691@ubuntu> (raw)

Hi,

I decided to have a look at whether the ALSA topology parsing is bullet
proof against malformed topology files. It seems not quite to be the case.
At least I seem to have found a possibility of crashing the kernel by a
malformed topology file. I haven't tested it, so, maybe I'm wrong.

In principle, firmware files can only be written by root, and if you have
root access to the system, it's anyway doomed. Is this the approach and
we aren't really trying to make topology parsing 100% safe, or do we want
to fix any such possible parsing issues?

Thanks
Guennadi
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel

             reply	other threads:[~2019-10-06 10:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-06 10:47 Guennadi Liakhovetski [this message]
2019-10-06 14:10 ` [alsa-devel] what's the kernel policy WRT firmware parsing security? Jaroslav Kysela
2019-10-07 14:16   ` Guennadi Liakhovetski

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=20191006104715.GA14691@ubuntu \
    --to=guennadi.liakhovetski@linux.intel.com \
    --cc=alsa-devel@alsa-project.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.