CVE-2017-17807: Medium severity IBM Data Risk Manager vulnerability

Published Dec 8, 2017
·
Updated

Last updated 25 August 2025

Other sources

Linux Kernel could allow a local authenticated attacker to bypass security restrictions, caused by omitting an access-control check when adding a key to the current task's default request-key keyring in the KEYS subsystem. By using a sequence of specially-crafted system calls, an attacker could exploit this vulnerability to add keys to a keyring with only Search permission.

IBM

The KEYS subsystem in the Linux kernel before 4.14.6 omitted an access-control check when adding a key to the current task's "default request-key keyring" via the requestkey() system call, allowing a local user to use a sequence of crafted system calls to add keys to a keyring with only Search permission (not Write permission) to that keyring, related to constructgetdestkeyring() in security/keys/requestkey.c.

The KEYS subsystem in the Linux kernel omitted an access-control check when adding a key to the current task's "default request-key keyring" via the requestkey() system call, allowing a local user to use a sequence of crafted system calls to add keys to a keyring with only Search permission (not Write permission) to that keyring, related to constructgetdestkeyring() in security/keys/requestkey.c.

Upstream patch:

https://github.com/torvalds/linux/commit/4dca6ea1d9432052afb06baf2e3ae78188a4410b

Red Hat

The KEYS subsystem in the Linux kernel omitted an access-control check when writing a key to the current task's default keyring, allowing a local user to bypass security checks to the keyring. This compromises the validity of the keyring for those who rely on it.

Affected Software

7 affected componentsFixes available
redhat/kernel-rt<0:3.10.0-1127.rt56.1093.el7
0:3.10.0-1127.rt56.1093.el7
redhat/kernel<0:3.10.0-1127.el7
0:3.10.0-1127.el7
redhat/kernel<14.4.6
14.4.6
IBM Data Risk Manager<=2.0.6
Google Android
Linux Linux kernel<4.14.6
debian/linux
5.10.223-15.10.257-16.1.170-36.1.174-16.12.86-16.12.90-27.0.10-17.0.12-2

Event History

Dec 8, 2017
CVE Published
12:00 AM
Dec 20, 2017
CVE Published
via MITRE·11:00 PM
Data Sourced
via MITRE·11:00 PM
Description
Data Sourced
via NVD·11:29 PM
RemedyDescriptionSeverityWeaknessAffected Software
Jan 11, 2024
Data Sourced
via Launchpad·10:34 PM
Description
Aug 30, 2025
Data Sourced
via Ubuntu·04:18 AM
RemedyDescriptionSeverityAffected Software
Jun 13, 2026
Data Sourced
via Debian·10:26 AM
DescriptionAffected Software

Parent advisories

This vulnerability appears in the following advisories.

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-2017-17807?

CVE-2017-17807 is classified as a medium severity vulnerability.

2

How do I fix CVE-2017-17807?

To mitigate CVE-2017-17807, upgrade to the recommended kernels or apply the relevant patches provided by your vendor.

3

Who is affected by CVE-2017-17807?

CVE-2017-17807 affects users of specific versions of the Linux Kernel, Red Hat kernel packages, and IBM Data Risk Manager.

4

What kind of attack does CVE-2017-17807 enable?

CVE-2017-17807 allows a local authenticated attacker to bypass security restrictions through improper access controls.

5

What components are involved in CVE-2017-17807?

CVE-2017-17807 involves the KEYS subsystem of the Linux Kernel, particularly the request-key keyring.

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