linux-kernel - Re: [PATCH] aio: fix mremap after fork null-deref

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 for Android: free password hash cracker in your pocket

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

Message-Id: <20230110143904.8f8c6c0f80aa01c938326446@linux-foundation.org>
Date:   Tue, 10 Jan 2023 14:39:04 -0800
From:   Andrew Morton <akpm@...ux-foundation.org>
To:     Seth Jenkins <sethjenkins@...gle.com>
Cc:     Alexander Viro <viro@...iv.linux.org.uk>,
        Benjamin LaHaise <bcrl@...ck.org>,
        linux-fsdevel@...r.kernel.org, linux-aio@...ck.org,
        linux-kernel@...r.kernel.org, Jann Horn <jannh@...gle.com>,
        Pavel Emelyanov <xemul@...allels.com>, stable@...r.kernel.org
Subject: Re: [PATCH] aio: fix mremap after fork null-deref

On Fri,  4 Nov 2022 17:25:19 -0400 Seth Jenkins <sethjenkins@...gle.com> wrote:

> Commit e4a0d3e720e7 ("aio: Make it possible to remap aio ring") introduced
> a null-deref if mremap is called on an old aio mapping after fork as
> mm->ioctx_table will be set to NULL.
> 

Is this a theoretical thing, or has this oops actually been observed?