---
id: CVE-2026-90272
title: |-
  In the Linux kernel, the following vulnerability has been resolved:

  perf: arm_pmuv3: Zero initialize hw_id branch stack field

  PERF_SAMPLE_BRANCH_HW_INDEX is supported by BRBE so hw_id is passed to
  userspace, but it's never set by the B…
summary: |-
  In the Linux kernel, the following vulnerability has been resolved:

  perf: arm_pmuv3: Zero initialize hw_id branch stack field

  PERF_SAMPLE_BRANCH_HW_INDEX is supported by BRBE so hw_id is passed to
  userspace, but it's never set by the B…
severity: none
vendor: Linux
product: Linux
affected:
  - >-
    Linux >= 58074a0fce66c6c97b35ce8a28ed4e7b780f9a8f <
    57b72442c1672963fd51ab441ca1b71f6dc79b66
  - >-
    Linux >= 58074a0fce66c6c97b35ce8a28ed4e7b780f9a8f <
    988e11b69ef9d4034e19c64407030fa948580c3d
  - >-
    Linux >= 58074a0fce66c6c97b35ce8a28ed4e7b780f9a8f <
    7c3b63386c27bed8d59a4b4c283d02860420eb0a
  - Linux 6.17
published: '2026-09-17'
updated: '2026-09-17'
sourceUpdated: '2026-09-17T17:17:23.773'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-90272'
references:
  - url: 'https://git.kernel.org/stable/c/57b72442c1672963fd51ab441ca1b71f6dc79b66'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/7c3b63386c27bed8d59a4b4c283d02860420eb0a'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/988e11b69ef9d4034e19c64407030fa948580c3d'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
tags:
  - nvd
  - cve.org
ingestedAt: '2026-09-17T16:21:47.837Z'
epss: 0.00206
epssPercentile: 0.09468
---

## Overview

In the Linux kernel, the following vulnerability has been resolved:

perf: arm_pmuv3: Zero initialize hw_id branch stack field

PERF_SAMPLE_BRANCH_HW_INDEX is supported by BRBE so hw_id is passed to
userspace, but it's never set by the BRBE driver. Zero initialize it as
it should be according to the docs:

   * For the architectures whose raw branch records are
   * already stored in age order, the hw_idx should be 0.

It's probably too risky to remove PERF_SAMPLE_BRANCH_HW_INDEX from BRBE
now in case anyone is setting it and reading the value, but zero
initializing the whole struct also protects against the same issue with
new fields that are added in the future.

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.