CVE-2026-98551 (GCVE-0-2026-98551)
Vulnerability from cvelistv5
Published
2026-10-18 15:18
Modified
2026-10-19 09:21
Severity ?
VLAI Severity ?
EPSS score ?
Summary
In the Linux kernel, the following vulnerability has been resolved:
perf/core: Fill branch entries with a single assignment
perf_clear_branch_entry_bitfields() clears the bitfields of struct
perf_branch_entry one by one and leaves from/to alone, since callers
overwrite those straight away. The list has to be kept in sync with the
struct by hand and has already fallen behind: new_type and priv were
added to perf_branch_entry and never added here.
Only BRBE writes those two, and neither for every record.
brbe_set_perf_entry_type() leaves new_type alone for a branch type it
does not recognise, and priv is not set for source-only records.
arm_pmuv3.c allocates the per-CPU branch stack with kmalloc(), so such a
record reaches userspace with whatever the slot held: uninitialised
kmalloc() data on the first pass over the buffer, the previous record's
values after that. Nothing under arch/x86/events/ writes either field,
so only arm64 is affected.
Assign the whole entry at each site instead. Everything not named is
then zero, and there is no list to keep in sync. The bitfields add up to
exactly 64 bits, so the struct has no padding to leave undefined.
perf_clear_branch_entry_bitfields() has no callers left, so remove it.
perf_entry_from_brbe_regset() assigns an empty literal instead, since it
fills from/to conditionally. PERF_BR_SPEC_NA is 0, so dropping the
explicit spec assignment changes nothing.
References
Impacted products
{
"containers": {
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"arch/x86/events/amd/brs.c",
"arch/x86/events/amd/lbr.c",
"arch/x86/events/intel/lbr.c",
"drivers/perf/arm_brbe.c",
"include/linux/perf_event.h"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "c7de8521947a521b766979ff5c09f66fe905a5bd",
"status": "affected",
"version": "b190bc4ac9e6d9763b61654c5a0c085ff77d7a09",
"versionType": "git"
},
{
"lessThan": "24b620729e53d978b3e425f55bc66efd3bab1f59",
"status": "affected",
"version": "b190bc4ac9e6d9763b61654c5a0c085ff77d7a09",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"arch/x86/events/amd/brs.c",
"arch/x86/events/amd/lbr.c",
"arch/x86/events/intel/lbr.c",
"drivers/perf/arm_brbe.c",
"include/linux/perf_event.h"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "6.1"
},
{
"lessThan": "6.1",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "7.2.*",
"status": "unaffected",
"version": "7.2.9",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.3",
"versionType": "original_commit_for_fix"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.2.9",
"versionStartIncluding": "6.1",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.3",
"versionStartIncluding": "6.1",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "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\u0027s\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."
}
],
"providerMetadata": {
"dateUpdated": "2026-10-19T09:21:34.288Z",
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"shortName": "Linux"
},
"references": [
{
"url": "https://git.kernel.org/stable/c/c7de8521947a521b766979ff5c09f66fe905a5bd"
},
{
"url": "https://git.kernel.org/stable/c/24b620729e53d978b3e425f55bc66efd3bab1f59"
}
],
"title": "perf/core: Fill branch entries with a single assignment",
"x_generator": {
"engine": "bippy-1.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"assignerShortName": "Linux",
"cveId": "CVE-2026-98551",
"datePublished": "2026-10-18T15:18:19.008Z",
"dateReserved": "2026-09-25T10:25:14.356Z",
"dateUpdated": "2026-10-19T09:21:34.288Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
Loading…
Loading…
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.
Loading…
Loading…