# CVE-2025-68737: arm64/pageattr: Propagate return value from __change_memory_common

> Failure to propagate errors in arm64 page attribute changes can bypass rodata security protections, allowing potential memory corruption or privilege escalation.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Dec 2025
- **Updated:** 11 May 2026
- **Also known as:** BELL-CVE-2025-68737, GHSA-ww8h-qfvw-pj5m, UBUNTU-CVE-2025-68737

## What is CVE-2025-68737?

CVE-2025-68737 is a vulnerability in Linux, published on 24 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

arm64/pageattr: Propagate return value from __change_memory_common

The rodata=on security measure requires that any code path which does
vmalloc -> set_memory_ro/set_memory_rox must protect the linear map alias
too. Therefore, if such a call fails, we must abort set_memory_* and caller
must take appropriate action; currently we are suppressing the error, and
there is a real chance of such an error arising post commit a166563e7ec3
("arm64: mm: support large block mapping when rodata=full"). Therefore,
propagate any error to the caller.

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


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

Apply the vendor's patch.

## Is CVE-2025-68737 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-68737 is a vulnerability in Linux, published on 24 Dec 2025. 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-2025-68737 in the wild and no public exploit code.

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

## Sources

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

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