CVE-2026-98151: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-6969-2pr3-9qx5
Share
Published
Advisory Summary

CVE-2026-98151 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-98151 at a Glance

CVE Identifier CVE-2026-98151
GHSA Identifier GHSA-6969-2pr3-9qx5
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-98151

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-98151, 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: bpf: Fix REG INVARIANTS VIOLATION on speculative pointer arithmetic Take the following unprivileged program as an example: r0 = bpf_map_lookup_elem(...) /* PTR_TO_MAP_VALUE, offset 0 */ ... 14: r0 += r1 /* r1 is a bounded scalar */ 15: r9 = r0 Loading it triggers a verifier warning from reg_bounds_sanity_check(): verifier bug: REG INVARIANTS VIOLATION (alu): const subreg tnum out of sync with range bounds r64={.base=0x0, .size=0x0} r32={.base=0x0, .size=0xffffffff} var_off=(0x0, 0x0) What happens: 1. Processing insn 14 (r0 += r1) in adjust_ptr_min_max_vals(), the new offset is computed into dst_reg's var_off and 32/64-bit ranges. 2. Because pointer registers do not track 32-bit subregister bounds, __mark_reg32_unbounded() first sets r32 to the full range; r32 is re-derived from the offset at the end of the function by reg_bounds_sync(). 3. On the unprivileged path, sanitize_ptr_alu() is called and, via sanitize_speculative_path() -> push_stack(), snapshots the current register state and schedules the next instruction (insn 15) to be verified directly as a speculative path. 4. That snapshot is taken between step 2 and the final reg_bounds_sync(): at this point dst_reg's var_off still holds the (const) original offset while r32 has just been blanked to the full range, i.e. the two are out of sync. When the speculative path later verifies insn 15 (r9 = r0), the inconsistent state reaches reg_bounds_sanity_check() and trips the warning. var_off and the 32-bit range must always be consistent. There are two ways to keep the snapshot consistent: 1. sync var_off and r32 before the snapshot so they match, or 2. leave r32 at its original (already consistent) value and blank it only after the snapshot. The whole point of sanitize_ptr_alu() is to insert a harmless masking sequence that keeps the access in bounds under speculation, so the state it snapshots should faithfully represent that. Take approach 2: move __mark_reg32_unbounded() to after sanitize_ptr_alu(), so the speculative snapshot keeps the pointer's original, consistent r32. The non-speculative path is unchanged: r32 is still blanked before the offset is applied and re-derived by reg_bounds_sync().

References

NVD — CVE-2026-98151 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-98151
git.kernel.org/stable/c/150aeba624... WEB
https://git.kernel.org/stable/c/150aeba624e8b7cac51c39440d7e8e1fd11de9a0
git.kernel.org/stable/c/21a681526c... WEB
https://git.kernel.org/stable/c/21a681526c715aebb4f918b8c131583442d1b3d8
git.kernel.org/stable/c/9f9477ae73... WEB
https://git.kernel.org/stable/c/9f9477ae73de9c5a28e8ab7000d8097b078faee4
git.kernel.org/stable/c/d623a4a58b... WEB
https://git.kernel.org/stable/c/d623a4a58bb238443505d5c2949d1182dcfc26b6

Frequently Asked Questions

What is CVE-2026-98151?
CVE-2026-98151 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-98151?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-98151?
CVE-2026-98151 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-98151?
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-6969-2pr3-9qx5",
  "modified" : "2026-09-25T12:31:38Z",
  "published" : "2026-09-25T12:31:38Z",
  "aliases" : [ "CVE-2026-98151" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Fix REG INVARIANTS VIOLATION on speculative pointer arithmetic\n\nTake the following unprivileged program as an example:\n\n\tr0 = bpf_map_lookup_elem(...)\t/* PTR_TO_MAP_VALUE, offset 0 */\n\t...\n\t14: r0 += r1\t\t\t/* r1 is a bounded scalar */\n\t15: r9 = r0\n\nLoading it triggers a verifier warning from reg_bounds_sanity_check():\n\n\tverifier bug: REG INVARIANTS VIOLATION (alu): const subreg tnum out\n\tof sync with range bounds r64={.base=0x0, .size=0x0}\n\tr32={.base=0x0, .size=0xffffffff} var_off=(0x0, 0x0)\n\nWhat happens:\n\n1. Processing insn 14 (r0 += r1) in adjust_ptr_min_max_vals(), the new\n   offset is computed into dst_reg's var_off and 32/64-bit ranges.\n\n2. Because pointer registers do not track 32-bit subregister bounds,\n   __mark_reg32_unbounded() first sets r32 to the full range; r32 is\n   re-derived from the offset at the end of the function by\n   reg_bounds_sync().\n\n3. On the unprivileged path, sanitize_ptr_alu() is called and, via\n   sanitize_speculative_path() -> push_stack(), snapshots the current\n   register state and schedules the next instruction (insn 15) to be\n   verified directly as a speculative path.\n\n4. That snapshot is taken between step 2 and the final reg_bounds_sync():\n   at this point dst_reg's var_off still holds the (const) original\n   offset while r32 has just been blanked to the full range, i.e. the two\n   are out of sync. When the speculative path later verifies insn 15\n   (r9 = r0), the inconsistent state reaches reg_bounds_sanity_check() and\n   trips the warning.\n\nvar_off and the 32-bit range must always be consistent. There are two\nways to keep the snapshot consistent:\n\n  1. sync var_off and r32 before the snapshot so they match, or\n  2. leave r32 at its original (already consistent) value and blank it\n     only after the snapshot.\n\nThe whole point of sanitize_ptr_alu() is to insert a harmless masking\nsequence that keeps the access in bounds under speculation, so the state\nit snapshots should faithfully represent that. Take approach 2: move\n__mark_reg32_unbounded() to after sanitize_ptr_alu(), so the speculative\nsnapshot keeps the pointer's original, consistent r32. The non-speculative\npath is unchanged: r32 is still blanked before the offset is applied and\nre-derived by reg_bounds_sync().",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-98151"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/150aeba624e8b7cac51c39440d7e8e1fd11de9a0"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/21a681526c715aebb4f918b8c131583442d1b3d8"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/9f9477ae73de9c5a28e8ab7000d8097b078faee4"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/d623a4a58bb238443505d5c2949d1182dcfc26b6"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-25T11:17:46Z"
  }
}