# CVE-2015-5224: Race condition in n/a

> Remote attackers can exploit a race condition in the mkostemp function to cause file name collisions, potentially leading to further attacks.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 23 Aug 2017
- **Updated:** 4 Dec 2025
- **Also known as:** DEBIAN-CVE-2015-5224, GHSA-g2jw-fqx3-5mwq, MGASA-2015-0352

## What is CVE-2015-5224?

CVE-2015-5224 is a critical vulnerability in n/a, published on 23 Aug 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The mkostemp function in login-utils in util-linux when used incorrectly allows remote attackers to cause file name collision and possibly other attacks.

Weakness: CWE-377 (DEPRECATED: Insecure Temporary File)

## Which versions are affected by CVE-2015-5224?

It affects 1 product.


Products: Kernel Util-Linux.

## How do I fix CVE-2015-5224?

Apply the vendor's patch.

## Is CVE-2015-5224 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-7738](https://insights.sbomify.com/CVE-2018-7738/): Command injection in n/a (high 7.8)
- [CVE-2016-2779](https://insights.sbomify.com/CVE-2016-2779/): Privilege escalation in n/a (high 7.8)
- [CVE-2026-13595](https://insights.sbomify.com/CVE-2026-13595/): Util-linux: util-linux: heap use-after-free in libblkid nested partition probing (medium 6.8)
- [CVE-2020-21583](https://insights.sbomify.com/CVE-2020-21583/): Command injection in n/a (medium 6.7)
- [CVE-2022-0563](https://insights.sbomify.com/CVE-2022-0563/): Information disclosure in util-linux (medium 5.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-5224 and fix it if it is affected.

What it is: CVE-2015-5224 is a critical vulnerability in n/a, published on 23 Aug 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2015-5224 in the wild and no public exploit code.

Affected product: n/a. 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-2015-5224/ (Markdown: https://insights.sbomify.com/CVE-2015-5224/index.md)
```

## Sources

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

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