qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: John Snow <jsnow@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>,
	"P J P" <ppandit@redhat.com>,
	"QEMU Developers" <qemu-devel@nongnu.org>
Cc: Bugs SysSec <bugs-syssec@rub.de>,
	Prasad J Pandit <pjp@fedoraproject.org>,
	Qemu-block <qemu-block@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] ide: ahci: add check to avoid null dereference (CVE-2019-12067)
Date: Thu, 8 Aug 2019 19:11:36 -0400	[thread overview]
Message-ID: <d29f92ac-86db-e54c-0b56-a5d95926ca2f@redhat.com> (raw)
In-Reply-To: <91ce6c32-a08c-1e92-36fe-c925f0422c97@redhat.com>



On 8/8/19 5:11 AM, Philippe Mathieu-Daudé wrote:
> Hi Prasad,
> 
> On 8/8/19 8:56 AM, P J P wrote:
>> From: Prasad J Pandit <pjp@fedoraproject.org>
>>
>> AHCI emulator while committing DMA buffer in ahci_commit_buf()
>> may do a NULL dereference if the command header 'ad->cur_cmd'
>> is null. Add check to avoid it.
>>
>> Reported-by: Bugs SysSec <bugs-syssec@rub.de>
>> Signed-off-by: Prasad J Pandit <pjp@fedoraproject.org>
>> ---
>>  hw/ide/ahci.c | 6 ++++--
>>  1 file changed, 4 insertions(+), 2 deletions(-)
>>
>> diff --git a/hw/ide/ahci.c b/hw/ide/ahci.c
>> index 00ba422a48..9fff94075b 100644
>> --- a/hw/ide/ahci.c
>> +++ b/hw/ide/ahci.c
>> @@ -1458,8 +1458,10 @@ static void ahci_commit_buf(IDEDMA *dma, uint32_t tx_bytes)
>>  {
>>      AHCIDevice *ad = DO_UPCAST(AHCIDevice, dma, dma);
>>  
>> -    tx_bytes += le32_to_cpu(ad->cur_cmd->status);
>> -    ad->cur_cmd->status = cpu_to_le32(tx_bytes);
>> +    if (ad->cur_cmd) {
> 
> My 2 cents, John will correct me:
> 
> This is not a valid condition, so an assert() might be more appropriate
> here.
> 
> Why is dma_buf_commit() being called with a null command? This check
> should go elsewhere to avoid the call.
> 

Yes, something else is broken.

Can you please give a reproducer or more detailed report so I can fix
this properly?

This likely is just adding a whole host of new undefined problems
waiting to happen by adding an if (...), so while it's not nice to have
a host assert() it's probably better than taking the state machine off
the rails and seeing what else breaks.

>> +        tx_bytes += le32_to_cpu(ad->cur_cmd->status);
>> +        ad->cur_cmd->status = cpu_to_le32(tx_bytes);
>> +    }
>>  }
>>  
>>  static int ahci_dma_rw_buf(IDEDMA *dma, int is_write)
>>


      reply	other threads:[~2019-08-08 23:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-08  6:56 [Qemu-devel] [PATCH] ide: ahci: add check to avoid null dereference (CVE-2019-12067) P J P
2019-08-08  9:11 ` Philippe Mathieu-Daudé
2019-08-08 23:11   ` John Snow [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=d29f92ac-86db-e54c-0b56-a5d95926ca2f@redhat.com \
    --to=jsnow@redhat.com \
    --cc=bugs-syssec@rub.de \
    --cc=philmd@redhat.com \
    --cc=pjp@fedoraproject.org \
    --cc=ppandit@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).