mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Kang Chen <k.chen@smail.nju.edu.cn>
Cc: Dan Carpenter <error27@gmail.com>,
	Hans de Goede <hansg@kernel.org>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	Sakari Ailus <sakari.ailus@linux.intel.com>,
	Andy Shevchenko <andy@kernel.org>,
	Raushan Kumar <mitramaurya80@gmail.com>,
	Chelsy Ratnawat <chelsyratnawat2001@gmail.com>,
	linux-media <linux-media@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	linux-staging <linux-staging@lists.linux.dev>
Subject: Re: 回复：[PATCH] media: atomisp: reject short _DSM packages
Date: Tue, 3 Nov 2026 15:04:50 +0100	[thread overview]
Message-ID: <2026110339-joyfully-captivate-855b@gregkh> (raw)
In-Reply-To: <tencent_283392A22C260EB0040CD271@qq.com>

On Tue, Nov 03, 2026 at 09:13:16PM +0800, Kang Chen wrote:
> No. In the confidential computing (CVM) threat model, ACPI tables are
> controlled by the host and are untrusted; BadAML (CCS'25) shows malicious
> ACPI/AML can be used to attack the guest.&nbsp;
> And the kernel already validates many ACPI return values
> (e.g. types, package counts, bounds).

Are you sure that Linux supports that threat model at this point in
time?  And that this matters for this specific driver?  I doubt that
this media driver would ever be seriously considered for those types of
situations :)

thanks,

greg k-h

      parent reply	other threads:[~2026-11-03 14:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-03 11:41 [PATCH] " Kang Chen
2026-11-03 11:53 ` Andy Shevchenko
2026-11-03 12:58 ` Dan Carpenter
     [not found]   ` <tencent_283392A22C260EB0040CD271@qq.com>
2026-11-03 14:04     ` Greg Kroah-Hartman [this message]

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=2026110339-joyfully-captivate-855b@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=andy@kernel.org \
    --cc=chelsyratnawat2001@gmail.com \
    --cc=error27@gmail.com \
    --cc=hansg@kernel.org \
    --cc=k.chen@smail.nju.edu.cn \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=mchehab@kernel.org \
    --cc=mitramaurya80@gmail.com \
    --cc=sakari.ailus@linux.intel.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®