CVE-2017-17807: Medium severity IBM Data Risk Manager vulnerability
Last updated 4 July 2026
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
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
redhat/kernel-rtto a version that resolves this vulnerability.Fixed in 0:3.10.0-1127.rt56.1093.el7 - Upgrade
Upgrade
redhat/kernelto a version that resolves this vulnerability.Fixed in 0:3.10.0-1127.el7 - Upgrade
Upgrade
redhat/kernelto a version that resolves this vulnerability.Fixed in 14.4.6 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 5.10.223-1Fixed in 5.10.259-1Fixed in 6.1.176-1Fixed in 6.1.177-1Fixed in 6.12.94-1Fixed in 6.12.95-1Fixed in 7.1.3-1Fixed in 7.1.4-1 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 4.14.6 - Compensating control
For kernels where the KEYS subsystem omits the access-control check when adding keys to the current task's default request-key keyring via the request_key() system call (construct_get_dest_keyring() in security/keys/request_key.c), reduce exposure by limiting local authenticated users who can call request_key() (e.g., restrict access to accounts/interactive sessions that could exploit the issue).
Event History
Parent advisories
This vulnerability appears in the following advisories.
Frequently Asked Questions
What is the severity of CVE-2017-17807?
CVE-2017-17807 is classified as a medium severity vulnerability.
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.
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.
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.
What components are involved in CVE-2017-17807?
CVE-2017-17807 involves the KEYS subsystem of the Linux Kernel, particularly the request-key keyring.