linux-kernel - RE: [char-misc-next] mei: hbm: fix client dma reply status

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <SA1PR11MB58255A9F7420254F869218D6F2449@SA1PR11MB5825.namprd11.prod.outlook.com>
Date:   Wed, 29 Dec 2021 16:09:21 +0000
From:   "Grumbach, Emmanuel" <emmanuel.grumbach@...el.com>
To:     "Winkler, Tomas" <tomas.winkler@...el.com>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>
CC:     "Usyskin, Alexander" <alexander.usyskin@...el.com>,
        "Lubart, Vitaly" <vitaly.lubart@...el.com>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "stable@...r.kernel.org" <stable@...r.kernel.org>
Subject: RE: [char-misc-next] mei: hbm: fix client dma reply status

> 
> From: Alexander Usyskin <alexander.usyskin@...el.com>
> 
> Don't blindly copy status value received from the firmware into internal client
> status field, It may be positive and ERR_PTR(ret) will translate it into an
> invalid address and the caller will crash.
> 
> Put the error code into the client status on failure.
> 
> Fixes: 369aea845951 ("mei: implement client dma setup.")
> Reported-by: Emmanuel Grumbach <emmanuel.grumbach@...el.com>
> Cc: <stable@...r.kernel.org> # v5.11+
> Acked-by: Tomas Winkler <tomas.winkler@...el.com>
> Signed-off-by: Alexander Usyskin <alexander.usyskin@...el.com>
> Signed-off-by: Tomas Winkler <tomas.winkler@...el.com>
> 

Tested-by: : Emmanuel Grumbach <emmanuel.grumbach@...el.com>