Menu

Star on GitHub · 3.2k

CVE-2026-68345

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 ga…

Published Aug 10, 2026EPSS 0.20%

Overview

CVE-2026-68345 is a known-severity vulnerability. It was published on August 10, 2026.

Technical 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.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2026-68345?

CVE-2026-68345 is a known-severity vulnerability. It was published on August 10, 2026.

How severe is CVE-2026-68345?

CVSS score information is not yet available for this vulnerability. Check back as the CVE record is updated by NVD analysts.

How do I fix or remediate CVE-2026-68345?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-68345?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-68345 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.