# CVE-2007-5908: Buffer overflow in the (1) sysfs_show_available_clocksources and (2) sysfs_show_current_clocksources functions in Linux kernel 2.6.23 and ea


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 9 Nov 2007
- **Updated:** 28 Nov 2007

## What is CVE-2007-5908?

CVE-2007-5908 is a vulnerability, published on 9 Nov 2007. 

### Official description

Buffer overflow in the (1) sysfs_show_available_clocksources and (2) sysfs_show_current_clocksources functions in Linux kernel 2.6.23 and earlier might allow local users to cause a denial of service or execute arbitrary code via crafted clock source names.  NOTE: follow-on analysis by Linux developers states that "There is no way for unprivileged users (or really even the root user) to add new clocksources.

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


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

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

## Is CVE-2007-5908 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2007-5908 is a vulnerability, published on 9 Nov 2007. 
Exploitation: There is no known exploitation of CVE-2007-5908 in the wild and no public exploit code.

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-5908/ (Markdown: https://insights.sbomify.com/CVE-2007-5908/index.md)
```

## Sources

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

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