Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-97587perf: RISC-V: store available counter mask as bitmap

Description

In the Linux kernel, the following vulnerability has been resolved: perf: RISC-V: store available counter mask as bitmap The available-counter mask was a single unsigned long, but iteration uses RISCV_MAX_COUNTERS, which is 64. On RV32 that reads past the object. Filling with an unsigned-long bit at index 32 and above is also wrong. Use DECLARE_BITMAP and set_bit/bitmap helpers. Walk each bitmap word into CFG_MATCH when checking events, when allocating an index, and when stopping all counters. Set the counter base to i times BITS_PER_LONG. Share the CFG_MATCH ecall through a small helper so the 32-bit argument split is not duplicated. On qemu-system-riscv32 the probe bitmap has bits above XLEN set, so the first word alone is not enough. [[email protected]: updated to apply; fixed checkpatch.pl issues]

Timeline

  1. ID reserved

    By Linux

  2. · 1 day later

    Published

  3. · 35 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.21% · top 89% of all CVEs (12 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected e9991434596f5373dfd75857b445eb92a9253c56 – < 433249a4de52ecda40ffa9c466cec1312e62826f
    • affected e9991434596f5373dfd75857b445eb92a9253c56 – < 5a1b6379eed5b13eac0228b605b0bed988e547e9
    • affected e9991434596f5373dfd75857b445eb92a9253c56 – < 143668c424772979a45118dc9cc9c2c13a35f41d
    • affected e9991434596f5373dfd75857b445eb92a9253c56 – < 9bec7beaed074bcae4181fde9ff9dfbe4e7b0957
    • affected e9991434596f5373dfd75857b445eb92a9253c56 – < e5481db31f4654e9a1254d5d467d9b1ff2f8b1cb
    • affected e9991434596f5373dfd75857b445eb92a9253c56 – < 6809da6e9c08ccc9a09cb0a48c61471679274aaa
  • Linux · Linux

    • affected 5.18
    • unaffected < 5.18
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.111 – ≤ 6.12.*
    • unaffected 6.18.53 – ≤ 6.18.*
    • unaffected 7.2.7 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-97587 badge
[![CVE-2026-97587](https://cveledger.app/badge/CVE-2026-97587.svg)](https://cveledger.app/cve/CVE-2026-97587)

Record last updated .