# CVE-2025-6365: HobbesOSR Kitten pgtable.h set_pte_at resource consumption

> An attacker can cause resource consumption and denial of service in HobbesOSR Kitten via the set_pte_at function in the ARM64 page table library.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X`)
- **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:** 20 Jun 2025
- **Updated:** 23 Jun 2025
- **Also known as:** GHSA-37hg-4qwq-2g86

## What is CVE-2025-6365?

CVE-2025-6365 is a medium-severity denial of service vulnerability in HobbesOSR Kitten, published on 20 Jun 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability was found in HobbesOSR Kitten up to c4f8b7c3158983d1020af432be1b417b28686736 and classified as critical. Affected by this issue is the function set_pte_at in the library /include/arch-arm64/pgtable.h. The manipulation leads to resource consumption. Continious delivery with rolling releases is used by this product. Therefore, no version details of affected nor updated releases are available.

Weakness: CWE-835 (Loop with Unreachable Exit Condition), CWE-404 (Improper Resource Shutdown or Release), CWE-400 (Uncontrolled Resource Consumption)

## Which versions are affected by CVE-2025-6365?

It affects 1 product.


Products: Hobbesosr Kitten.

## How do I fix CVE-2025-6365?

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

## Is CVE-2025-6365 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-6365 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-6365 and fix it if it is affected.

What it is: CVE-2025-6365 is a medium-severity denial of service vulnerability in HobbesOSR Kitten, published on 20 Jun 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-6365 exists.

Affected product: HobbesOSR Kitten. 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-2025-6365/ (Markdown: https://insights.sbomify.com/CVE-2025-6365/index.md)
```

## Sources

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

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