Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Fri,  9 Jan 2015 11:18:53 -0500 (EST)
Subject: Re: PIE bypass using VDSO ASLR weakness - Linux kernel

Hash: SHA1

>> Given that ASLR is not effective in VDSO and comes down to 11 quality bits
>> as per pax test making return-to-vdso feasible even for PIE binary, whether
>> this should be considered as a bug and CVE be assigned?

> Yes, we can proceed to CVE assignment. The more recent discussion
> hasn't been on oss-security with, for example:

> This apparently mentions both the original discovery:
>    The current algorithm is buggy: the vdso has about a 50%
>    probability of being at the very end of a PMD.

Use CVE-2014-9585 for this vulnerability, which corresponds to a
portion of the above bc3b94c31d65e761ddfe150d02932c65971b74e2 patch.

(not yet available at
> and a second discovery that was made separately:
>    The current algorithm also has a decent chance of failing outright
>    due to incorrect handling of the case where the top of the stack is
>    near the top of its PMD.
> Here, our question, for anyone, is: is there a security impact from
> the "failing outright" outcome? Or is there only a performance impact
> (e.g., any correctly written application will continue to work, but
> will not benefit from any vDSO functionality)?

We haven't seen any responses. There is currently no CVE ID for this
"incorrect handling of the case where the top of the stack is near the
top of its PMD" issue. This incorrect-handling issue is not within the
scope of CVE-2014-9585.

- -- 
CVE assignment team, MITRE CVE Numbering Authority
M/S M300
202 Burlington Road, Bedford, MA 01730 USA
[ PGP key available through ]
Version: GnuPG v1.4.14 (SunOS)


Powered by blists - more mailing lists

Please check out the Open Source Software Security Wiki, which is counterpart to this mailing list.

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.