# CVE-2007-2654: Race condition in n/a

> Local attackers can exploit a race condition in xfs_fsr to read or overwrite arbitrary files on XFS filesystems.

- **Severity:** Medium 4.4 (`AV:L/AC:M/Au:N/C:P/I:P/A:P`)
- **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:** 14 May 2007
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2007-2654, GHSA-9gpj-6mg9-3q6q

## What is CVE-2007-2654?

CVE-2007-2654 is a medium-severity vulnerability in Suse Suse Linux, published on 14 May 2007. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

xfs_fsr in xfsdump creates a .fsr temporary directory with insecure permissions, which allows local users to read or overwrite arbitrary files on xfs filesystems.

Weakness: CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization)

## Which versions are affected by CVE-2007-2654?

It affects 7 products.


Products: Suse Opensuse, Suse Suse Linux, Suse Suse Linux Openexchange Server, Suse Suse Linux School Server, Suse Suse Linux Standard Server, Suse Suse Open Enterprise Server, Xfsdump Xfsdump.

## How do I fix CVE-2007-2654?

Apply the vendor's patch.

## Is CVE-2007-2654 being exploited?

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

## Other vulnerabilities in Suse Suse Linux

- [CVE-2011-0469](https://insights.sbomify.com/CVE-2011-0469/): Code injection in openSUSE (critical 9.8)
- [CVE-2010-0230](https://insights.sbomify.com/CVE-2010-0230/): Misconfiguration in n/a (high 7.5)
- [CVE-2008-3067](https://insights.sbomify.com/CVE-2008-3067/): Information disclosure in n/a (low 2.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-2654 and fix it if it is affected.

What it is: CVE-2007-2654 is a medium-severity vulnerability in Suse Suse Linux, published on 14 May 2007. 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-2007-2654 in the wild and no public exploit code.

Affected product: Suse Suse Linux. 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-2007-2654/ (Markdown: https://insights.sbomify.com/CVE-2007-2654/index.md)
```

## Sources

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

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