CVE-2014-9529: Race Condition

Published Jan 7, 2015
·
Updated

It was reported [1] that the Linux kernel suffered from a flaw when doing key garbage collection. The patch [1] describes the issue as:

""" When a key is being garbage collected, it's key->user would get put before the ->destroy() callback is called, where the key is removed from it's respective tracking structures.

This leaves a key hanging in a semi-invalid state which leaves a window open for a different task to try an access key->user. An example is findkeyringbyname() which would dereference key->user for a key that is in the process of being garbage collected (where key->user was freed but ->destroy() wasn't called yet - so it's still present in the linked list).

"""

An unprivileged local user could use this flaw to crash the system.

[1] http://marc.info/?l=linux-kernel&m=141986398232547&w=2

Other sources

Race condition in the keygcunusedkeys function in security/keys/gc.c in the Linux kernel through 3.18.2 allows local users to cause a denial of service (memory corruption or panic) or possibly have unspecified other impact via keyctl commands that trigger access to a key structure member during garbage collection of a key.

Launchpad

Affected Software

41 affected componentsFixes available
Linux Linux kernel<3.2.67
Linux Linux kernel>=3.3<3.4.107
Linux Linux kernel>=3.5<3.10.67
Linux Linux kernel>=3.11<=3.12.37
Linux Linux kernel>=3.13<=3.14.31
Linux Linux kernel>=3.15<3.16.35
Linux Linux kernel>=3.17<3.18.5
redhat Enterprise Linux Desktop=6.0
redhat Enterprise Linux Desktop=7.0
redhat Enterprise Linux Server=6.0
redhat Enterprise Linux Server=7.0
redhat Enterprise Linux Server Aus=6.6
redhat Enterprise Linux Server Aus=7.3
redhat Enterprise Linux Server Aus=7.4
redhat Enterprise Linux Server Aus=7.6
redhat Enterprise Linux Server Aus=7.7
redhat Enterprise Linux Server Eus=6.6
redhat Enterprise Linux Server Eus=7.1
redhat Enterprise Linux Server Eus=7.2
redhat Enterprise Linux Server Eus=7.3
redhat Enterprise Linux Server Eus=7.4
redhat Enterprise Linux Server Eus=7.5
redhat Enterprise Linux Server Eus=7.6
redhat Enterprise Linux Server Eus=7.7
redhat Enterprise Linux Server Tus=6.6
redhat Enterprise Linux Server Tus=7.3
redhat Enterprise Linux Server Tus=7.6
redhat Enterprise Linux Server Tus=7.7
redhat Enterprise Linux Workstation=6.0
redhat Enterprise Linux Workstation=7.0
openSUSE openSUSE=13.1
Fedoraproject Fedora=20
Fedoraproject Fedora=21
Debian Debian Linux=7.0
Debian Debian Linux=8.0
Canonical Ubuntu Linux=10.04
Canonical Ubuntu Linux=12.04
Canonical Ubuntu Linux=14.04
Canonical Ubuntu Linux=14.10
Linux Linux kernel<=3.18.2
debian/linux
5.10.223-15.10.234-16.1.129-16.1.135-16.12.25-1

Event History

Jan 7, 2015
Data Sourced
via Red Hat·03:29 PM
DescriptionSeverityAffected Software
Jan 9, 2015
CVE Published
via MITRE·09:00 PM
Data Sourced
via MITRE·09:00 PM
Description
Jan 11, 2024
Data Sourced
via Launchpad·10:08 PM
Description
Sep 16, 2024
Data Sourced
via Ubuntu·01:05 AM
RemedyDescriptionSeverityAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2014-9529?

CVE-2014-9529 has a medium severity rating due to its potential impact on system integrity during key garbage collection.

2

How do I fix CVE-2014-9529?

To fix CVE-2014-9529, update to a patched version of the Linux kernel, specifically version 5.10.223-1 or later.

3

Which versions of the Linux kernel are affected by CVE-2014-9529?

CVE-2014-9529 affects Linux kernel versions up to 3.18.2, including various version ranges between 3.2.67 and 3.18.x.

4

Is CVE-2014-9529 specific to any Linux distributions?

Yes, CVE-2014-9529 impacts multiple distributions including Red Hat, Debian, and Ubuntu with specific version ranges.

5

What are the potential consequences of CVE-2014-9529 if left unpatched?

If CVE-2014-9529 is left unpatched, it may allow unauthorized access to sensitive information or system compromise during key management operations.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203