CVE-2026-98551: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-r5w5-qjwh-6pq3
Share
Published
Advisory Summary

CVE-2026-98551 is a security vulnerability vulnerability (General Security Weakness) affecting Software libraries in the Maven ecosystem. Remediation is available in the latest vendor maintenance releases.

CVE-2026-98551 at a Glance

CVE Identifier CVE-2026-98551
GHSA Identifier GHSA-r5w5-qjwh-6pq3
Severity N/A
CVSS v3.1 Base Score N/A
CWE Classification General Security Weakness
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

How to Fix CVE-2026-98551

To remediate this vulnerability, upgrade all affected Software dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

mvn dependency:tree

How to Check if You Are Affected

To determine whether your Java application is affected by CVE-2026-98551, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree

Analyze the terminal output to locate any version of Software in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.

Note: The mvn dependency:tree command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under General Security Weakness. In Software, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

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

NVD — CVE-2026-98551 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-98551
git.kernel.org/stable/c/24b620729e... WEB
https://git.kernel.org/stable/c/24b620729e53d978b3e425f55bc66efd3bab1f59
git.kernel.org/stable/c/c7de852194... WEB
https://git.kernel.org/stable/c/c7de8521947a521b766979ff5c09f66fe905a5bd

Frequently Asked Questions

What is CVE-2026-98551?
CVE-2026-98551 is a security vulnerability in Software classified as a security vulnerability vulnerability under General Security Weakness.
Which Software versions are affected?
Affected versions include releases prior to current release patches.
What version fixes CVE-2026-98551?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-98551?
CVE-2026-98551 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-98551?
Run the dependency tree command: 'mvn dependency:tree'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-r5w5-qjwh-6pq3",
  "modified" : "2026-10-18T18:31:54Z",
  "published" : "2026-10-18T18:31:54Z",
  "aliases" : [ "CVE-2026-98551" ],
  "details" : "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.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-98551"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/24b620729e53d978b3e425f55bc66efd3bab1f59"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/c7de8521947a521b766979ff5c09f66fe905a5bd"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-10-18T16:17:07Z"
  }
}