{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-90272 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-90272 is a vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-90272 and fix it if it is affected.\n\nWhat it is: CVE-2026-90272 is a vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-90272 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-90272/ (Markdown: https://insights.sbomify.com/CVE-2026-90272/index.md)","id":"CVE-2026-90272","markdown":"https://insights.sbomify.com/CVE-2026-90272/index.md","name":"CVE-2026-90272","record":{"aliases":["BELL-CVE-2026-90272","DEBIAN-CVE-2026-90272","GHSA-8j89-gr3p-jpp8","UBUNTU-CVE-2026-90272"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"A local attacker can read uninitialized kernel memory via the ARM PMU branch stack interface, potentially exposing sensitive data.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nperf: arm_pmuv3: Zero initialize hw_id branch stack field\n\nPERF_SAMPLE_BRANCH_HW_INDEX is supported by BRBE so hw_id is passed to\nuserspace, but it's never set by the BRBE driver. Zero initialize it as\nit should be according to the docs:\n\n   * For the architectures whose raw branch records are\n   * already stored in age order, the hw_idx should be 0.\n\nIt's probably too risky to remove PERF_SAMPLE_BRANCH_HW_INDEX from BRBE\nnow in case anyone is setting it and reading the value, but zero\ninitializing the whole struct also protects against the same issue with\nnew fields that are added in the future.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"perf: arm_pmuv3: Zero initialize hw_id branch stack field","id":"CVE-2026-90272","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"coresight: etm4x: missing cscfg_csdev_disable_active_config() in perf enable","id":"CVE-2026-90273"},"packages":[],"prev":{"headline":"arm_mpam: Fix a NULL pointer dereference on unbinding after an error interrupt","id":"CVE-2026-90271"},"products":["Linux"],"published":"2026-09-17","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"A local attacker can read uninitialized kernel memory via the ARM PMU branch stack interface, potentially exposing sensitive data.","url":"https://insights.sbomify.com/CVE-2026-90272/"}