# CVE-2015-0199: Memory corruption in n/a

> Local attackers can cause a denial of service via memory corruption in the IBM GPFS mmfslinux kernel module through unspecified ioctl calls.

- **Severity:** Medium 4.9 (`AV:L/AC:L/Au:N/C:N/I:N/A:C`)
- **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:** No
- **Published:** 24 Mar 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-mxgq-v86p-xg2p

## What is CVE-2015-0199?

CVE-2015-0199 is a medium-severity memory corruption vulnerability in n/a, published on 24 Mar 2015. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The mmfslinux kernel module in IBM General Parallel File System (GPFS) 3.4 before 3.4.0.32, 3.5 before 3.5.0.24, and 4.1 before 4.1.0.7 allows local users to cause a denial of service (memory corruption) via unspecified character-device ioctl calls.

Weakness: CWE-399

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

It affects 1 product.


Products: Ibm General Parallel File System.

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

No fix has been published for CVE-2015-0199 yet. Limit exposure of the affected software until one is available.

## Is CVE-2015-0199 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2015-0198](https://insights.sbomify.com/CVE-2015-0198/): Auth bypass in n/a (critical 10.0)
- [CVE-2018-1431](https://insights.sbomify.com/CVE-2018-1431/): Privilege escalation in Spectrum Scale (high 7.4)
- [CVE-2016-6115](https://insights.sbomify.com/CVE-2016-6115/): Memory corruption in Spectrum Scale (high 7.2)
- [CVE-2015-4974](https://insights.sbomify.com/CVE-2015-4974/): Privilege escalation in n/a (high 7.2)
- [CVE-2015-0197](https://insights.sbomify.com/CVE-2015-0197/): Privilege escalation in n/a (high 7.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2015-0199 is a medium-severity memory corruption vulnerability in n/a, published on 24 Mar 2015. 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-2015-0199 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-0199/ (Markdown: https://insights.sbomify.com/CVE-2015-0199/index.md)
```

## Sources

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

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