Bug 1177263

Use the following template to for the 'fedpkg update' request to submit an
update for this issue as it contains the top-level parent bug(s) as well as
this tracking bug.  This will ensure that all associated bugs get updated
when new packages are pushed to stable.

=====

# bugfix, security, enhancement, newpackage (required)
type=security

# testing, stable
request=testing

# Bug numbers: 1234,9876
bugs=1177260,1177263

# Description of your update
notes=Security fix for CVE-2014-9419

# Enable request automation based on the stable/unstable karma thresholds
autokarma=True
stable_karma=3
unstable_karma=-3

# Automatically close bugs when this marked as stable
close_bugs=True

# Suggest that users restart after update
suggest_reboot=False

======

Additionally, you may opt to use the bodhi update submission link instead:

https://admin.fedoraproject.org/updates/new/?type_=security&bugs=1177260,1177263

Fedora kernels don't seem to be affected.

===
# cat /etc/redhat-release 
Fedora release 21 (Twenty One)
#
# uname -r
3.17.4-301.fc21.i686+PAE
#
#cc -xc -o estest estest.c 
# ./estest 
Allocated GDT index 7
[OK]    ES was preserved
---

$ cat /etc/redhat-release 
Fedora release 21 (Twenty One)
$ 
$ uname -r
3.17.7-300.fc21.x86_64
$
$ cc -xc -o estest estest.c 
$ cc -xc -o gsbasetest gsbasetest.c 
$ 
$ ./estest 
estest: set_thread_area: Function not implemented
$ 
$ ./gsbasetest 
[OK]    ARCH_SET_GS worked
[OK]    Writing 0 to gs worked
[FAIL]  gsbase was corrupted
$
==

(In reply to Prasad J Pandit from comment #2)
> Fedora kernels don't seem to be affected.

Not sure why that is, but the patch is queued for stable anyway so I went ahead and grabbed it.  Added to Fedora git.

(In reply to Prasad J Pandit from comment #2)
> $ cc -xc -o estest estest.c 

FWIW, this is a 32-bit issue, you have to compile with -m32...

But I am not sure, whether this fixes anything for kernels < 3.14 (before kASLR was merged). The commit message is poor.

(In reply to Josh Boyer from comment #3)
> (In reply to Prasad J Pandit from comment #2)
> > Fedora kernels don't seem to be affected.
> 
> Not sure why that is, but the patch is queued for stable anyway

It is questionable. Andi Kleen objected to my, 3.12, version. So I FWDed to Greg and I am unsure ATM whether the kernels < 3.14 will be released with the patch.

(In reply to Jiri Slaby from comment #5)
> (In reply to Josh Boyer from comment #3)
> > (In reply to Prasad J Pandit from comment #2)
> > > Fedora kernels don't seem to be affected.
> > 
> > Not sure why that is, but the patch is queued for stable anyway
> 
> It is questionable. Andi Kleen objected to my, 3.12, version. So I FWDed to
> Greg and I am unsure ATM whether the kernels < 3.14 will be released with
> the patch.

Yes, I noticed that.  Thanks thought.

For Fedora, we no longer have any releases that are older then the 3.17.y stable series so that specific thing isn't relevant.  However, I'll keep an eye on the upstream thread and see if anything else comes from that.

kernel-3.17.8-300.fc21 has been submitted as an update for Fedora 21.
https://admin.fedoraproject.org/updates/kernel-3.17.8-300.fc21

kernel-3.17.8-200.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/kernel-3.17.8-200.fc20

Package kernel-3.17.8-200.fc20:
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing kernel-3.17.8-200.fc20'
as soon as you are able to, then reboot.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2015-0515/kernel-3.17.8-200.fc20
then log in and leave karma (feedback).

kernel-3.17.8-300.fc21 has been pushed to the Fedora 21 stable repository.  If problems still persist, please make note of it in this bug report.

kernel-3.17.8-200.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.