# CVE-2026-72453: regcache: Do not overwrite error code when finalizing cache after error

> A Linux kernel bug in regcache initialization can cause NULL pointer dereferences and system crashes when cache population fails.

- **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:** 15 Aug 2026
- **Updated:** 26 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-72453, GHSA-cv9g-v92m-34rj, UBUNTU-CVE-2026-72453

## What is CVE-2026-72453?

CVE-2026-72453 is a vulnerability in Linux, published on 15 Aug 2026. 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:

regcache: Do not overwrite error code when finalizing cache after error

During regcache initialization, if an error occurs in the
cache_ops->populate callback, and if cache operations include an exit
callback, the error code from populate() is overwritten with the return
value from exit(). This hides the error condition from the caller of
regcache_init(), and can cause NULL pointer dereferences when the regcache
is later accessed.

## Which versions are affected by CVE-2026-72453?


## How do I fix CVE-2026-72453?

Apply the vendor's patch.

## Is CVE-2026-72453 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-72453 and fix it if it is affected.

What it is: CVE-2026-72453 is a vulnerability in Linux, published on 15 Aug 2026. 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-2026-72453 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-2026-72453/ (Markdown: https://insights.sbomify.com/CVE-2026-72453/index.md)
```

## Sources

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

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