LiveActive security incident?Get immediate response
CVE Record

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

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.

HighCVSS 7.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A Linux performance-monitoring driver may trust unsupported Arm CMN hardware layouts. Newer or unexpected hardware can exceed the driver's size assumptions, causing kernel memory corruption. A successful local attack could compromise data, system integrity, or availability, but exposure is limited to systems using the relevant Arm CMN hardware and driver.

Executive priority

Treat as a high-priority kernel update for affected Arm infrastructure, especially shared or locally accessible systems. First establish whether Arm CMN hardware and the driver are present; systems without that combination are unlikely to be exposed based on the supplied description.

Technical view

The perf/arm-cmn driver accepted unknown CMN models or revisions while relying on fixed maximum sizes and object counts. An unsupported configuration could exceed those assumptions and cause array overflows in kernel context. The correction rejects hardware configurations that do not match supported models, revisions, and node types.

Likely exposure

Likely exposure is concentrated on affected Linux kernels running Arm systems with the perf/arm-cmn driver and unsupported CMN models or revisions. The supplied version data is ambiguous and mixes releases with commit identifiers, so administrators should confirm exposure through their Linux distributor or kernel vendor.

Exploitation context

CVSS 3.1 rates this 7.8 with local access, low complexity, low privileges, and no user interaction. Potential impact is high across confidentiality, integrity, and availability. The bundle reports no KEV listing and provides no evidence of active exploitation or a public exploit.

Researcher notes

The root concern is kernel array overflow from unsupported hardware dimensions, but no CWE is assigned. The bundle does not identify a demonstrated trigger path, exploit, or branch-by-branch fix mapping. Its version lists contain duplicates and mixed release and commit formats, so exact affected-version conclusions require vendor confirmation.

Mitigation direction

  • Apply a vendor kernel update containing the applicable referenced stable fix.
  • Confirm the update rejects unsupported Arm CMN models and revisions.
  • If updating is delayed, consult the vendor for supported risk-reduction measures.
  • Prioritize exposed multi-user Arm systems where low-privileged local access is possible.

Validation and detection

  • Inventory Arm systems using the perf/arm-cmn driver.
  • Record kernel releases, distributor package versions, and relevant CMN hardware revisions.
  • Check vendor advisories for branch-specific affected and fixed versions.
  • Verify the installed kernel includes the applicable stable fix or vendor backport.
  • Confirm unsupported CMN configurations are rejected rather than initialized.
Prepared
Confidence
medium
Sources
8

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2026-43150 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
0ADP providers
7Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2026-43150Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux28fa550a49e818d6445e787f584759b1bf21d9d4, 7819e05a0dceac20c5ff78ec9b252faf3b76b824, 7819e05a0dceac20c5ff78ec9b252faf3b76b824, 7819e05a0dceac20c5ff78ec9b252faf3b76b824, 7819e05a0dceac20c5ff78ec9b252faf3b76b824, 7819e05a0dceac20c5ff78ec9b252faf3b76b824, 6.1.63unaffected
LinuxLinux6.5, 0, 6.1.165, 6.6.128, 6.12.75, 6.18.16, 6.19.6, 7.0affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.