# CVE-2026-68345: arm_mpam: guard MBWU state before adding it to garbage

> A null pointer dereference in the Linux kernel's arm_mpam driver allows local attackers to cause a denial of service.

- **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:** 10 Aug 2026
- **Updated:** 17 Aug 2026
- **Also known as:** DEBIAN-CVE-2026-68345, GHSA-62gj-qm4m-4rg3, UBUNTU-CVE-2026-68345

## What is CVE-2026-68345?

CVE-2026-68345 is a vulnerability in Linux, published on 10 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:

arm_mpam: guard MBWU state before adding it to garbage

__destroy_component_cfg() adds each RIS mbwu_state object to the MPAM
garbage list when destroying component configuration.

However, mbwu_state is allocated per RIS and only for RISes with MBWU
monitors. A component can therefore have comp->cfg allocated while some
RISes still have ris->mbwu_state set to NULL.

Passing a NULL mbwu_state to add_to_garbage() dereferences the NULL
pointer inside the macro.

Skip RISes that do not have an mbwu_state object before adding them to
the garbage list.

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


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

Apply the vendor's patch.

## Is CVE-2026-68345 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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