# CVE-2017-17807: Missing authorization in n/a

> A local attacker can bypass keyring write permissions to add keys, potentially leading to privilege escalation in the Linux kernel.

- **Severity:** Low 3.3 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 20 Dec 2017
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2017-17807, GHSA-vfg5-pf24-9v2v, UBUNTU-CVE-2017-17807

## What is CVE-2017-17807?

CVE-2017-17807 is a low-severity missing authorization vulnerability in Linux kernel, published on 20 Dec 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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 request_key() 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 construct_get_dest_keyring() in security/keys/request_key.c.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2017-17807?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2017-17807?

Apply the vendor's patch.

## Is CVE-2017-17807 being exploited?

There is no known exploitation of CVE-2017-17807 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-17807 and fix it if it is affected.

What it is: CVE-2017-17807 is a low-severity missing authorization vulnerability in Linux kernel, published on 20 Dec 2017. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-17807 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-17807/ (Markdown: https://insights.sbomify.com/CVE-2017-17807/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-17807
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-17807
- OSV: https://osv.dev/vulnerability/CVE-2017-17807

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-17807/
Summaries are generated and may contain mistakes; the official description above is the record.