CVE-2026-90339: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-qfw2-5x2v-5xgv
Share
Published
Advisory Summary

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

CVE Identifier CVE-2026-90339
GHSA Identifier GHSA-qfw2-5x2v-5xgv
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-90339

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-90339, 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: powerpc/syscall: Fix syscall skip handling for seccomp and ptrace After enabling GENERIC_ENTRY on PowerPC, syscall_enter_from_user_mode() returns -1 as a sentinel to signal that seccomp or ptrace has intercepted the syscall and already set a return value via syscall_set_return_value(). system_call_exception() was not handling this sentinel, and since -1UL is >= NR_syscalls, the code fell into the out-of-range path and returned -ENOSYS, overwriting the errno already placed in regs->gpr[3]. The naive fix of checking r0 == -1L before the NR_syscalls bounds check is ambiguous: a user legitimately calling syscall(-1) also produces r0 == -1L, and a tracer intercepting such a call would have its injected return value silently discarded. Fix this by introducing a thread flag that is set whenever syscall_set_return_value() explicitly updates the return value. In system_call_exception(), check and clear this flag before dispatching the syscall, and return the preset value directly when it is present. This ensures that an explicitly supplied return value always suppresses syscall execution, regardless of the syscall number. This handles all seccomp actions correctly: - SECCOMP_RET_ERRNO, SECCOMP_RET_TRACE (no tracer), SECCOMP_RET_USER_NOTIF: all call syscall_set_return_value(), flag is set, injected value returned. - SECCOMP_RET_TRAP, SECCOMP_RET_KILL: call syscall_rollback() and deliver a signal; flag is not set, but the process is dying so the return value is irrelevant. The fix covers both ppc32 and ppc64 with no #ifdefs.

References

NVD — CVE-2026-90339 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-90339
git.kernel.org/stable/c/19b54740e2... WEB
https://git.kernel.org/stable/c/19b54740e2e1102c7d48553d9e0347c1f6af22b0
git.kernel.org/stable/c/69cb2be898... WEB
https://git.kernel.org/stable/c/69cb2be898be6d5826cacd1a628f6945a24480b6

Frequently Asked Questions

What is CVE-2026-90339?
CVE-2026-90339 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-90339?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-90339?
CVE-2026-90339 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-90339?
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-qfw2-5x2v-5xgv",
  "modified" : "2026-09-17T18:32:01Z",
  "published" : "2026-09-17T18:32:01Z",
  "aliases" : [ "CVE-2026-90339" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\npowerpc/syscall: Fix syscall skip handling for seccomp and ptrace\n\nAfter enabling GENERIC_ENTRY on PowerPC, syscall_enter_from_user_mode()\nreturns -1 as a sentinel to signal that seccomp or ptrace has intercepted\nthe syscall and already set a return value via syscall_set_return_value().\nsystem_call_exception() was not handling this sentinel, and since -1UL\nis >= NR_syscalls, the code fell into the out-of-range path and returned\n-ENOSYS, overwriting the errno already placed in regs->gpr[3].\n\nThe naive fix of checking r0 == -1L before the NR_syscalls bounds check\nis ambiguous: a user legitimately calling syscall(-1) also produces r0 ==\n-1L, and a tracer intercepting such a call would have its injected return\nvalue silently discarded.\n\nFix this by introducing a thread flag that is set whenever\nsyscall_set_return_value() explicitly updates the return value. In\nsystem_call_exception(), check and clear this flag before dispatching\nthe syscall, and return the preset value directly when it is present.\nThis ensures that an explicitly supplied return value always suppresses\nsyscall execution, regardless of the syscall number.\n\nThis handles all seccomp actions correctly:\n\n  - SECCOMP_RET_ERRNO, SECCOMP_RET_TRACE (no tracer), SECCOMP_RET_USER_NOTIF:\n    all call syscall_set_return_value(), flag is set, injected value returned.\n  - SECCOMP_RET_TRAP, SECCOMP_RET_KILL: call syscall_rollback() and deliver\n    a signal; flag is not set, but the process is dying so the return value\n    is irrelevant.\n\nThe fix covers both ppc32 and ppc64 with no #ifdefs.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-90339"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/19b54740e2e1102c7d48553d9e0347c1f6af22b0"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/69cb2be898be6d5826cacd1a628f6945a24480b6"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-17T17:17:32Z"
  }
}