# CVE-2017-5967: Information disclosure in n/a

> Local attackers can discover real process IDs by reading /proc/timer_list when CONFIG_TIMER_STATS is enabled, bypassing PID namespace isolation.

- **Severity:** Medium 4.0 (`CVSS:3.0/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 Feb 2017
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2017-5967, GHSA-3vpq-g4qh-42g9, UBUNTU-CVE-2017-5967

## What is CVE-2017-5967?

CVE-2017-5967 is a medium-severity vulnerability in Linux kernel, published on 14 Feb 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The time subsystem in the Linux kernel through 4.9.9, when CONFIG_TIMER_STATS is enabled, allows local users to discover real PID values (as distinguished from PID values inside a PID namespace) by reading the /proc/timer_list file, related to the print_timer function in kernel/time/timer_list.c and the __timer_stats_timer_set_start_info function in kernel/time/timer.c.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Linux kernel.

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

Apply the vendor's patch.

## Is CVE-2017-5967 being exploited?

There is no known exploitation of CVE-2017-5967 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-5967 and fix it if it is affected.

What it is: CVE-2017-5967 is a medium-severity vulnerability in Linux kernel, published on 14 Feb 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-5967 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-5967/ (Markdown: https://insights.sbomify.com/CVE-2017-5967/index.md)
```

## Sources

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

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