# CVE-2011-1676: Denial of service in n/a

> Local attackers can corrupt the system mount table by repeatedly triggering failed mount attempts, potentially causing denial of service.

- **Severity:** Low 3.3 (`AV:L/AC:M/Au:N/C:P/I:P/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:** No
- **Published:** 10 Apr 2011
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-xgxp-wxpw-r9x6

## What is CVE-2011-1676?

CVE-2011-1676 is a low-severity denial of service vulnerability in n/a, published on 10 Apr 2011. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

mount in util-linux 2.19 and earlier does not remove the /etc/mtab.tmp file after a failed attempt to add a mount entry, which allows local users to trigger corruption of the /etc/mtab file via multiple invocations.

Weakness: CWE-264

## Which versions are affected by CVE-2011-1676?

It affects 1 product.


Products: Linux Util-Linux.

## How do I fix CVE-2011-1676?

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

## Is CVE-2011-1676 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2008-1926](https://insights.sbomify.com/CVE-2008-1926/): Other in n/a (high 7.5)
- [CVE-2011-1677](https://insights.sbomify.com/CVE-2011-1677/): Denial of service in n/a (medium 4.6)
- [CVE-2011-1675](https://insights.sbomify.com/CVE-2011-1675/): Denial of service in n/a (low 3.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-1676 and fix it if it is affected.

What it is: CVE-2011-1676 is a low-severity denial of service vulnerability in n/a, published on 10 Apr 2011. 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-2011-1676 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-2011-1676/ (Markdown: https://insights.sbomify.com/CVE-2011-1676/index.md)
```

## Sources

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

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