CVE-2026-93050: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-7qcc-hqrm-qfrj
Share
Published
Advisory Summary

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

CVE Identifier CVE-2026-93050
GHSA Identifier GHSA-7qcc-hqrm-qfrj
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-93050

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-93050, 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: ipack: ipoctal: fix UAF, null-ptr-deref, and use-after-free in cleanup on remove Three issues arise when the device is removed while a tty session is still active: 1. UAF of struct ipoctal: the remove callback frees ipoctal via kfree() while tty ops may still access it. Fix by introducing kref-based lifetime management — kref is taken in install() when a tty is opened and released in cleanup() when the tty is finally destroyed; remove() uses kref_put() instead of kfree(). 2. NULL dereference in ipoctal_write_tty(): __ipoctal_remove() frees xmit_buf via tty_port_free_xmit_buf() while a userspace process may still hold the tty fd and call write(). Fix by checking for NULL xmit_buf in ipoctal_write_tty(). 3. UAF in ipoctal_cleanup(): ipack_put_carrier(ipoctal->dev) dereferences ipoctal->dev after the ipack_device has been freed by ipack_device_del(). Fix by caching ipoctal->carrier_owner during probe() and calling module_put() on the cached pointer directly in cleanup(), avoiding any access to ipoctal->dev. Also introduce a "removed" flag in struct ipoctal, set at the start of __ipoctal_remove(), and checked in every tty op that accesses hardware resources (port_activate, write_tty, set_termios, hangup, shutdown). This prevents page faults when devm_ioremap() regions are unmapped after remove() returns.

References

NVD — CVE-2026-93050 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-93050
git.kernel.org/stable/c/1a3258e105... WEB
https://git.kernel.org/stable/c/1a3258e105f711538201bdd2ac2a05b11554eabc
git.kernel.org/stable/c/4a6518be31... WEB
https://git.kernel.org/stable/c/4a6518be316029650301f2a5e8f0def229b895d9
git.kernel.org/stable/c/a4613140f0... WEB
https://git.kernel.org/stable/c/a4613140f01bd0fb9980e2746ed9aaa65a29b5d6
git.kernel.org/stable/c/ab5f5b27a3... WEB
https://git.kernel.org/stable/c/ab5f5b27a340004b92252c6a5f23bf1c6cf3b02a
git.kernel.org/stable/c/b6b5d64cb1... WEB
https://git.kernel.org/stable/c/b6b5d64cb161a28347d64dc3168a636c4abb68d5
git.kernel.org/stable/c/c92ef8fd83... WEB
https://git.kernel.org/stable/c/c92ef8fd834521f0b788e0511976c689fe57c63c

Frequently Asked Questions

What is CVE-2026-93050?
CVE-2026-93050 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-93050?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-93050?
CVE-2026-93050 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-93050?
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-7qcc-hqrm-qfrj",
  "modified" : "2026-09-17T18:32:08Z",
  "published" : "2026-09-17T18:32:08Z",
  "aliases" : [ "CVE-2026-93050" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nipack: ipoctal: fix UAF, null-ptr-deref, and use-after-free in cleanup on remove\n\nThree issues arise when the device is removed while a tty session is\nstill active:\n\n1. UAF of struct ipoctal: the remove callback frees ipoctal via\n   kfree() while tty ops may still access it.  Fix by introducing\n   kref-based lifetime management — kref is taken in install() when\n   a tty is opened and released in cleanup() when the tty is finally\n   destroyed; remove() uses kref_put() instead of kfree().\n\n2. NULL dereference in ipoctal_write_tty(): __ipoctal_remove()\n   frees xmit_buf via tty_port_free_xmit_buf() while a userspace\n   process may still hold the tty fd and call write().  Fix by\n   checking for NULL xmit_buf in ipoctal_write_tty().\n\n3. UAF in ipoctal_cleanup(): ipack_put_carrier(ipoctal->dev)\n   dereferences ipoctal->dev after the ipack_device has been freed\n   by ipack_device_del().  Fix by caching ipoctal->carrier_owner\n   during probe() and calling module_put() on the cached pointer\n   directly in cleanup(), avoiding any access to ipoctal->dev.\n\nAlso introduce a \"removed\" flag in struct ipoctal, set at the start\nof __ipoctal_remove(), and checked in every tty op that accesses\nhardware resources (port_activate, write_tty, set_termios, hangup,\nshutdown).  This prevents page faults when devm_ioremap() regions\nare unmapped after remove() returns.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-93050"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/1a3258e105f711538201bdd2ac2a05b11554eabc"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/4a6518be316029650301f2a5e8f0def229b895d9"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/a4613140f01bd0fb9980e2746ed9aaa65a29b5d6"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/ab5f5b27a340004b92252c6a5f23bf1c6cf3b02a"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/b6b5d64cb161a28347d64dc3168a636c4abb68d5"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/c92ef8fd834521f0b788e0511976c689fe57c63c"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-17T17:17:58Z"
  }
}