CVE-2026-97942: Software Security Vulnerability Vulnerability

UNKNOWN

Advisory Identifier: GHSA-g4fw-gv65-xh5g

Published 2026-09-25

Advisory Summary

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

CVE Identifier CVE-2026-97942

GHSA Identifier GHSA-g4fw-gv65-xh5g

Severity N/A

CVSS v3.1 Base Score N/A

CWE Classification General Security Weakness

Affected Product Software

Package Ecosystem Maven

Published Date 2026-09-25

Last Updated 2026-09-25

How to Fix CVE-2026-97942

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-97942, 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: x86/alternatives: Exclude text poking against change_page_attr() From time to time, the following BUG can be observed in the x86 alternatives patching code [0]: > kernel BUG at arch/x86/kernel/alternative.c:2576! > Oops: invalid opcode: 0000 [#1] SMP NOPTI > CPU: 0 UID: 0 PID: 355 Comm: (udev-worker) Not tainted 7.1.3-1-default #1 PREEMPT(full) openSUSE Tumbleweed 8c1795b03ec64f997e57a8ad38b1161e3b98da64 > Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS unknown 02/02/2022 > RIP: 0010:__text_poke+0x2aa/0x450 > Call Trace: > <TASK> > smp_text_poke_batch_finish+0x2a7/0x320 > __static_call_transform+0xb7/0x220 > arch_static_call_transform+0x5b/0xb0 > __static_call_init+0xe9/0x270 > static_call_module_notify+0x11f/0x150 > notifier_call_chain+0x61/0xe0 > blocking_notifier_call_chain_robust+0x63/0xc0 > load_module+0x1c92/0x20c0 > init_module_from_file+0xd8/0x140 > idempotent_init_module+0x100/0x2f0 > __x64_sys_finit_module+0x71/0xe0 > do_syscall_64+0xe1/0x610 > entry_SYSCALL_64_after_hwframe+0x76/0x7e which matches the following BUG_ON() in alternative.c: /* * If something went wrong, crash and burn since recovery paths are not * implemented. */ BUG_ON(!pages[0] || (cross_page_boundary && !pages[1])); This can happen if vmalloc_to_page() fails, for any reason. Such can happen if text poking races with CPA, which can possibly result in the collapsing of page tables (or breaking of PMD hugepages). It is not a problem for most users of vmalloc_to_page() (they solely own the vmalloc'd range) but, when CONFIG_ARCH_HAS_EXECMEM_ROX=y, various modules own a single execmem vmalloc range, and can call set_memory_*() in parallel on it. This can happen to race against __text_poke and cause havoc in vmalloc_to_page(). Fix it by excluding against CPA using the init_mm mmap read lock. [ dhansen: Fix up SoB ordering. The actual code flow here was: Pedro=>Lorenzo=>Mike=>Me which is reflected in the SoB chain now. I *believe* Mike simply picked up Lorenzo's update to Pedro's post from the Link ]

References

NVD — CVE-2026-97942 NVD

https://nvd.nist.gov/vuln/detail/CVE-2026-97942

git.kernel.org/stable/c/1587d3394e... WEB

https://git.kernel.org/stable/c/1587d3394e254639cc36516256031334095e6ef3

git.kernel.org/stable/c/281e6f536f... WEB

https://git.kernel.org/stable/c/281e6f536f2f3f95d91938c5bd7ba9bcb4c1049d

git.kernel.org/stable/c/89c60435b9... WEB

https://git.kernel.org/stable/c/89c60435b90d32ab5e3a39da3ae73d463d07debe

Frequently Asked Questions

What is CVE-2026-97942?

CVE-2026-97942 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-97942?

Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.

What CWE is associated with CVE-2026-97942?

CVE-2026-97942 is classified under General Security Weakness.

How can I check Maven dependencies for CVE-2026-97942?

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-g4fw-gv65-xh5g",
  "modified" : "2026-09-25T12:31:29Z",
  "published" : "2026-09-25T12:31:29Z",
  "aliases" : [ "CVE-2026-97942" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nx86/alternatives: Exclude text poking against change_page_attr()\n\nFrom time to time, the following BUG can be observed\nin the x86 alternatives patching code [0]:\n\n  > kernel BUG at arch/x86/kernel/alternative.c:2576!\n  > Oops: invalid opcode: 0000 [#1] SMP NOPTI\n  > CPU: 0 UID: 0 PID: 355 Comm: (udev-worker) Not tainted 7.1.3-1-default #1 PREEMPT(full) openSUSE Tumbleweed  8c1795b03ec64f997e57a8ad38b1161e3b98da64\n  > Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS unknown 02/02/2022\n  > RIP: 0010:__text_poke+0x2aa/0x450\n  > Call Trace:\n  >  <TASK>\n  >  smp_text_poke_batch_finish+0x2a7/0x320\n  >  __static_call_transform+0xb7/0x220\n  >  arch_static_call_transform+0x5b/0xb0\n  >  __static_call_init+0xe9/0x270\n  >  static_call_module_notify+0x11f/0x150\n  >  notifier_call_chain+0x61/0xe0\n  >  blocking_notifier_call_chain_robust+0x63/0xc0\n  >  load_module+0x1c92/0x20c0\n  >  init_module_from_file+0xd8/0x140\n  >  idempotent_init_module+0x100/0x2f0\n  >  __x64_sys_finit_module+0x71/0xe0\n  >  do_syscall_64+0xe1/0x610\n  >  entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\nwhich matches the following BUG_ON() in alternative.c:\n\n\t/*\n\t * If something went wrong, crash and burn since recovery paths are not\n\t * implemented.\n\t */\n\tBUG_ON(!pages[0] || (cross_page_boundary && !pages[1]));\n\nThis can happen if vmalloc_to_page() fails, for any reason. Such can happen\nif text poking races with CPA, which can possibly result in the collapsing\nof page tables (or breaking of PMD hugepages). It is not a problem for most\nusers of vmalloc_to_page() (they solely own the vmalloc'd range) but, when\nCONFIG_ARCH_HAS_EXECMEM_ROX=y, various modules own a single execmem vmalloc\nrange, and can call set_memory_*() in parallel on it. This can happen to\nrace against __text_poke and cause havoc in vmalloc_to_page().\n\nFix it by excluding against CPA using the init_mm mmap read lock.\n\n[ dhansen: Fix up SoB ordering. The actual code flow here was:\n\t   Pedro=>Lorenzo=>Mike=>Me which is reflected in the SoB chain\n\t   now. I *believe* Mike simply picked up Lorenzo's update to\n\t   Pedro's post from the Link ]",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-97942"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/1587d3394e254639cc36516256031334095e6ef3"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/281e6f536f2f3f95d91938c5bd7ba9bcb4c1049d"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/89c60435b90d32ab5e3a39da3ae73d463d07debe"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-25T11:17:21Z"
  }
}

Advisory Metadata

Source ID: GHSA-g4fw-gv65-xh5g
Schema Version: 1.4.0
Published: 2026-09-25 12:31
Last Modified: 2026-09-25 12:31
Database Record File: advisories/unreviewed/2026/09/GHSA-g4fw-gv65-xh5g/GHSA-g4fw-gv65-xh5g.json