CVE-2026-93275: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-j5v2-xwxq-rp3v
Share
Published
Advisory Summary

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

CVE Identifier CVE-2026-93275
GHSA Identifier GHSA-j5v2-xwxq-rp3v
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-93275

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-93275, 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/x86/intel/pt: Fix stop/start with no update If pt_event_stop() is called without PERF_EF_UPDATE flag, then perf_aux_output_end() is not called. A subsequent call to pt_event_start() will call perf_aux_output_begin() again which violates the rule against nesting and triggers a WARNING in perf_aux_output_begin(). Originally, pt_event_stop() was never called without PERF_EF_UPDATE, because the only code paths to do so are from event overflow, and Intel PT does not do that. However the introduction of group throttling by commit 9734e25fbf5ae ("perf: Fix the throttle logic for a group") meant that an Intel PT event could be throttled if it was part of a group. Throttling calls PMU ->stop() / ->start() callbacks without flags. An example is when AUX area sampling is used. The following commands hit the issue: echo 10000 > /proc/sys/kernel/perf_event_max_sample_rate perf record -F32000 --aux-sample -e '{intel_pt//u,cycles:u}' \ -- bash -c 'for i in `seq 1 100000` ; do true ; done' Use PERF_HES_UPTODATE to track whether perf_aux_output_begin() and perf_aux_output_end() are balanced. A cleared PERF_HES_UPTODATE bit indicates that an AUX output context is still open. Amend pt_event_start() / pt_event_stop() accordingly so that begin/end stay balanced: - In non-snapshot mode, stop() always closes the buffer (the buffer may have run out of space, and that accounting is done by the update), so a following start() opens a fresh one as before. - In snapshot/overwrite mode, stop() without PERF_EF_UPDATE leaves the buffer open so that pt_event_snapshot_aux() can still copy from it, and start() then only re-enables tracing instead of calling perf_aux_output_begin() again. Note that pt_event_del() calls pt_event_stop() with PERF_EF_UPDATE flag set (as is required by the documentation), so a final call to perf_aux_output_end() is assured.

References

NVD — CVE-2026-93275 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-93275
git.kernel.org/stable/c/2e17bf3a46... WEB
https://git.kernel.org/stable/c/2e17bf3a469a41457a3bc31b1f8fd66b6ce94a6d
git.kernel.org/stable/c/304844b554... WEB
https://git.kernel.org/stable/c/304844b5545f444d523286da8228a1cbc46ffffa
git.kernel.org/stable/c/9b919fb551... WEB
https://git.kernel.org/stable/c/9b919fb5512f256e9e0604faf960b2bb98aab454
git.kernel.org/stable/c/cab5015ee3... WEB
https://git.kernel.org/stable/c/cab5015ee3f25f789b4a368f2abfa65536576b78

Frequently Asked Questions

What is CVE-2026-93275?
CVE-2026-93275 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-93275?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-93275?
CVE-2026-93275 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-93275?
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-j5v2-xwxq-rp3v",
  "modified" : "2026-09-24T18:31:25Z",
  "published" : "2026-09-24T18:31:25Z",
  "aliases" : [ "CVE-2026-93275" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nperf/x86/intel/pt: Fix stop/start with no update\n\nIf pt_event_stop() is called without PERF_EF_UPDATE flag, then\nperf_aux_output_end() is not called.  A subsequent call to pt_event_start()\nwill call perf_aux_output_begin() again which violates the rule against\nnesting and triggers a WARNING in perf_aux_output_begin().\n\nOriginally, pt_event_stop() was never called without PERF_EF_UPDATE,\nbecause the only code paths to do so are from event overflow, and Intel PT\ndoes not do that.\n\nHowever the introduction of group throttling by commit 9734e25fbf5ae\n(\"perf: Fix the throttle logic for a group\") meant that an Intel PT event\ncould be throttled if it was part of a group.  Throttling calls PMU\n ->stop() / ->start() callbacks without flags.\n\nAn example is when AUX area sampling is used. The following commands\nhit the issue:\n\n  echo 10000 > /proc/sys/kernel/perf_event_max_sample_rate\n\n  perf record -F32000 --aux-sample -e '{intel_pt//u,cycles:u}' \\\n  -- bash -c 'for i in `seq 1 100000` ; do true ; done'\n\nUse PERF_HES_UPTODATE to track whether perf_aux_output_begin() and\nperf_aux_output_end() are balanced.  A cleared PERF_HES_UPTODATE bit\nindicates that an AUX output context is still open.\n\nAmend pt_event_start() / pt_event_stop() accordingly so that begin/end\nstay balanced:\n\n - In non-snapshot mode, stop() always closes the buffer (the buffer may\n   have run out of space, and that accounting is done by the update), so\n   a following start() opens a fresh one as before.\n\n - In snapshot/overwrite mode, stop() without PERF_EF_UPDATE leaves the\n   buffer open so that pt_event_snapshot_aux() can still copy from it,\n   and start() then only re-enables tracing instead of calling\n   perf_aux_output_begin() again.\n\nNote that pt_event_del() calls pt_event_stop() with PERF_EF_UPDATE flag set\n(as is required by the documentation), so a final call to\nperf_aux_output_end() is assured.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-93275"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/2e17bf3a469a41457a3bc31b1f8fd66b6ce94a6d"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/304844b5545f444d523286da8228a1cbc46ffffa"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/9b919fb5512f256e9e0604faf960b2bb98aab454"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/cab5015ee3f25f789b4a368f2abfa65536576b78"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-24T16:17:24Z"
  }
}