{"cve":"CVE-2026-98551","nvd":{"published":"2026-10-18T16:17:07.167","modified":"2026-10-19T10:19:11.363","status":"Received","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nperf/core: Fill branch entries with a single assignment\n\nperf_clear_branch_entry_bitfields() clears the bitfields of struct\nperf_branch_entry one by one and leaves from/to alone, since callers\noverwrite those straight away. The list has to be kept in sync with the\nstruct by hand and has already fallen behind: new_type and priv were\nadded to perf_branch_entry and never added here.\n\nOnly BRBE writes those two, and neither for every record.\nbrbe_set_perf_entry_type() leaves new_type alone for a branch type it\ndoes not recognise, and priv is not set for source-only records.\narm_pmuv3.c allocates the per-CPU branch stack with kmalloc(), so such a\nrecord reaches userspace with whatever the slot held: uninitialised\nkmalloc() data on the first pass over the buffer, the previous record's\nvalues after that. Nothing under arch/x86/events/ writes either field,\nso only arm64 is affected.\n\nAssign the whole entry at each site instead. Everything not named is\nthen zero, and there is no list to keep in sync. The bitfields add up to\nexactly 64 bits, so the struct has no padding to leave undefined.\n\nperf_clear_branch_entry_bitfields() has no callers left, so remove it.\nperf_entry_from_brbe_regset() assigns an empty literal instead, since it\nfills from/to conditionally. PERF_BR_SPEC_NA is 0, so dropping the\nexplicit spec assignment changes nothing.","cvss_v4":null,"cvss_v3":null,"cwes":[],"references":["https://git.kernel.org/stable/c/24b620729e53d978b3e425f55bc66efd3bab1f59","https://git.kernel.org/stable/c/c7de8521947a521b766979ff5c09f66fe905a5bd"],"products":[],"source":"nvd","synced_at":"2026-10-19T23:00:53.604569364+00:00"},"epss":{"cve":"CVE-2026-98551","score":0.00189,"percentile":0.08468,"date":"2026-10-25"},"kev":null,"osv":[],"attribution":["This product uses the NVD API but is not endorsed or certified by the NVD.","EPSS scores: FIRST Exploit Prediction Scoring System, https://www.first.org/epss","Known exploited vulnerabilities: CISA Known Exploited Vulnerabilities Catalog, https://www.cisa.gov/known-exploited-vulnerabilities-catalog","Package advisories: OSV (https://osv.dev), from the GitHub Advisory Database, PyPA, Go, RustSec and other ecosystem databases, under CC-BY 4.0 or CC0","CVE records: the CVE Program's CVE List (https://www.cve.org), under its terms of use (https://www.cve.org/Legal/TermsOfUse). CVE is a registered trademark of The MITRE Corporation; this product is not affiliated with the CVE Program."]}