linux-kernel - Re: [1/2] cxl: Fix off by one error allowing subsequent mmap page to be accessed

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]

Date:	Wed,  8 Jul 2015 20:54:07 +1000 (AEST)
From:	Michael Ellerman <mpe@...erman.id.au>
To:	Ian Munsie <imunsie@....ibm.com>
Cc:	mikey <mikey@...ling.org>, Matt Ochs <mrochs@...ibm.com>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	stable@...r.kernel.org, linuxppc-dev <linuxppc-dev@...abs.org>,
	Ian Munsie <imunsie@....ibm.com>
Subject: Re: [1/2] cxl: Fix off by one error allowing subsequent mmap page to be accessed

On Tue, 2015-07-07 at 05:45:45 UTC, Ian Munsie wrote:
> From: Ian Munsie <imunsie@....ibm.com>
> 
> It was discovered that if a process mmaped their problem state area they
> were able to access one page more than expected, potentially allowing
> them to access the problem state area of an unrelated process.
> 
> This was due to a simple off by one error in the mmap fault handler
> introduced in 0712dc7e73e59d79bcead5d5520acf4e9e917e87 ("cxl: Fix issues
> when unmapping contexts"), which is fixed in this patch.
> 
> Cc: stable@...r.kernel.org
> Fixes: 0712dc7e73e5 ("cxl: Fix issues when unmapping contexts")
> Signed-off-by: Ian Munsie <imunsie@....ibm.com>

Applied to powerpc fixes, thanks.

https://git.kernel.org/cgit/linux/kernel/git/powerpc/linux.git/commit/?h=fixes&id=10a5894f2dedd8a26b3132497445b314c0d952c4

cheers
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/