CVE-2026-98745: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-75wv-m6h4-9m7c
Share
Published
Advisory Summary

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

CVE Identifier CVE-2026-98745
GHSA Identifier GHSA-75wv-m6h4-9m7c
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-98745

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-98745, 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: arm64/fpsimd: signal: Forbid non-streaming SVE payload on SME-only systems When system_supports_sme() is true but system_supports_sve() is false, restoring a specifically crafted SVE signal context can result in the task erroneously having non-streaming SVE state. Subsequent attempts to manipulate the task's FPSIMD/SVE/SME state can result in a variety of problems, including fatal EL1 UNDEFs. In such configurations, the kernel always creates an SVE signal context when delivering a signal, and this can only be in one of two states: (1) SVE_SIG_FLAG_SM is set, and an SVE payload is present containing streaming mode SVE state. The recorded VL is the task's live streaming VL. (2) SVE_SIG_FLAG_SM is clear, and an SVE payload is not present. The FPSIMD context contains the non-streaming mode FPSIMD state. The recorded VL is 0. Currently restore_sve_fpsimd_context() correctly rejects cases where SVE_SIG_FLAG_SM is set and an SVE payload is not present, but fails to reject cases where SVE_SIG_FLAG_SM is clear and an SVE payload is present. Consequently, restore_sve_fpsimd_context() can place the task in a state where it has non-streaming SVE state even when this is not supported by HW. For example, this can cause a later EL1 UNDEF when the kernel attempts to restore the task's ZCR_EL1 value: | # ./sme-sigcontext-to-sve | Internal error: Oops - Undefined instruction: 0000000002000000 [#1] SMP | Modules linked in: | CPU: 0 UID: 0 PID: 131 Comm: sme-sigcontext- Not tainted 7.3.0-rc1 #1 PREEMPT | Hardware name: linux,dummy-virt (DT) | pstate: 61402009 (nZCv daif +PAN -UAO -TCO +DIT -SSBS BTYPE=--) | pc : fpsimd_restore_current_state+0x258/0x458 | lr : exit_to_user_mode_loop+0xb8/0x188 | sp : ffff80008056be40 | x29: ffff80008056be40 x28: fff00000c1670000 x27: 0000000000000000 | x26: 0000000000000000 x25: 0000000000000000 x24: 0000000000000000 | x23: ffff80008056bec0 x22: 0000000000000008 x21: 0000000000000040 | x20: 0000000000000081 x19: 0000000008800010 x18: 0000000000000000 | x17: 0000fffffd412570 x16: 0000000000001000 x15: 0000fffffd4123b0 | x14: 0000fffffd412780 x13: 0000fffffd412be8 x12: 0000000047435300 | x11: 0000fffffd412570 x10: 0000000000000000 x9 : 0000000045585401 | x8 : fff00000c18a6c44 x7 : 0000000000000000 x6 : 0000000000000002 | x5 : 0000000000000002 x4 : ffff800080568000 x3 : 0000000000000001 | x2 : 0000000008800010 x1 : fff00000c1670000 x0 : 0000000008800000 | Call trace: | fpsimd_restore_current_state+0x258/0x458 (P) | exit_to_user_mode_loop+0xb8/0x188 | el0_svc+0x1cc/0x1d0 | el0t_64_sync_handler+0xa0/0xe4 | el0t_64_sync+0x198/0x19c | Code: d5384101 f9400020 53175c03 36b80de0 (d5381202) | ---[ end trace 0000000000000000 ]--- | Kernel panic - not syncing: Oops - Undefined instruction: Fatal exception in interrupt | Kernel Offset: 0x291fb1000000 from 0xffff800080000000 | PHYS_OFFSET: 0x40000000 | CPU features: 0x0,00000000,0052802f,ffb88f43,3afcf73f | Memory Limit: none Rework restore_sve_fpsimd_context() to reject cases where SVE_SIG_FLAG_SM is clear and an SVE payload is not present. As parse_user_sigframe() rejects SVE signal frames when neither SVE nor SME are supported, it isn't necessary for restore_sve_fpsimd_context() to handle the case where neither are supported.

References

NVD — CVE-2026-98745 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-98745
git.kernel.org/stable/c/2bce6f006c... WEB
https://git.kernel.org/stable/c/2bce6f006cfe0b60e8249fd8d51396d99355cba3
git.kernel.org/stable/c/88c1c61155... WEB
https://git.kernel.org/stable/c/88c1c611552b24658eb61244086691c02be2013b
git.kernel.org/stable/c/e060d9069b... WEB
https://git.kernel.org/stable/c/e060d9069b49fe55f38057dfe592068014652671
git.kernel.org/stable/c/f2338929c7... WEB
https://git.kernel.org/stable/c/f2338929c7663859c0c74dd6fef2c0245066f845

Frequently Asked Questions

What is CVE-2026-98745?
CVE-2026-98745 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-98745?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-98745?
CVE-2026-98745 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-98745?
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-75wv-m6h4-9m7c",
  "modified" : "2026-10-18T18:32:02Z",
  "published" : "2026-10-18T18:32:02Z",
  "aliases" : [ "CVE-2026-98745" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\narm64/fpsimd: signal: Forbid non-streaming SVE payload on SME-only systems\n\nWhen system_supports_sme() is true but system_supports_sve() is false,\nrestoring a specifically crafted SVE signal context can result in the\ntask erroneously having non-streaming SVE state. Subsequent attempts to\nmanipulate the task's FPSIMD/SVE/SME state can result in a variety of\nproblems, including fatal EL1 UNDEFs.\n\nIn such configurations, the kernel always creates an SVE signal context\nwhen delivering a signal, and this can only be in one of two states:\n\n(1) SVE_SIG_FLAG_SM is set, and an SVE payload is present containing\n    streaming mode SVE state. The recorded VL is the task's live\n    streaming VL.\n\n(2) SVE_SIG_FLAG_SM is clear, and an SVE payload is not present. The\n    FPSIMD context contains the non-streaming mode FPSIMD state. The\n    recorded VL is 0.\n\nCurrently restore_sve_fpsimd_context() correctly rejects cases where\nSVE_SIG_FLAG_SM is set and an SVE payload is not present, but fails to\nreject cases where SVE_SIG_FLAG_SM is clear and an SVE payload is\npresent. Consequently, restore_sve_fpsimd_context() can place the task\nin a state where it has non-streaming SVE state even when this is not\nsupported by HW.\n\nFor example, this can cause a later EL1 UNDEF when the kernel attempts to\nrestore the task's ZCR_EL1 value:\n\n| # ./sme-sigcontext-to-sve\n| Internal error: Oops - Undefined instruction: 0000000002000000 [#1]  SMP\n| Modules linked in:\n| CPU: 0 UID: 0 PID: 131 Comm: sme-sigcontext- Not tainted 7.3.0-rc1 #1 PREEMPT\n| Hardware name: linux,dummy-virt (DT)\n| pstate: 61402009 (nZCv daif +PAN -UAO -TCO +DIT -SSBS BTYPE=--)\n| pc : fpsimd_restore_current_state+0x258/0x458\n| lr : exit_to_user_mode_loop+0xb8/0x188\n| sp : ffff80008056be40\n| x29: ffff80008056be40 x28: fff00000c1670000 x27: 0000000000000000\n| x26: 0000000000000000 x25: 0000000000000000 x24: 0000000000000000\n| x23: ffff80008056bec0 x22: 0000000000000008 x21: 0000000000000040\n| x20: 0000000000000081 x19: 0000000008800010 x18: 0000000000000000\n| x17: 0000fffffd412570 x16: 0000000000001000 x15: 0000fffffd4123b0\n| x14: 0000fffffd412780 x13: 0000fffffd412be8 x12: 0000000047435300\n| x11: 0000fffffd412570 x10: 0000000000000000 x9 : 0000000045585401\n| x8 : fff00000c18a6c44 x7 : 0000000000000000 x6 : 0000000000000002\n| x5 : 0000000000000002 x4 : ffff800080568000 x3 : 0000000000000001\n| x2 : 0000000008800010 x1 : fff00000c1670000 x0 : 0000000008800000\n| Call trace:\n|  fpsimd_restore_current_state+0x258/0x458 (P)\n|  exit_to_user_mode_loop+0xb8/0x188\n|  el0_svc+0x1cc/0x1d0\n|  el0t_64_sync_handler+0xa0/0xe4\n|  el0t_64_sync+0x198/0x19c\n| Code: d5384101 f9400020 53175c03 36b80de0 (d5381202)\n| ---[ end trace 0000000000000000 ]---\n| Kernel panic - not syncing: Oops - Undefined instruction: Fatal exception in interrupt\n| Kernel Offset: 0x291fb1000000 from 0xffff800080000000\n| PHYS_OFFSET: 0x40000000\n| CPU features: 0x0,00000000,0052802f,ffb88f43,3afcf73f\n| Memory Limit: none\n\nRework restore_sve_fpsimd_context() to reject cases where\nSVE_SIG_FLAG_SM is clear and an SVE payload is not present. As\nparse_user_sigframe() rejects SVE signal frames when neither SVE nor SME\nare supported, it isn't necessary for restore_sve_fpsimd_context() to\nhandle the case where neither are supported.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-98745"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/2bce6f006cfe0b60e8249fd8d51396d99355cba3"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/88c1c611552b24658eb61244086691c02be2013b"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/e060d9069b49fe55f38057dfe592068014652671"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/f2338929c7663859c0c74dd6fef2c0245066f845"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-10-18T16:17:28Z"
  }
}