Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-93050

Vulnerability in Linux kernel (CVE-2026-93050)

Summary

Vulnerability in Linux kernel (CVE-2026-93050). Risk of unauthorized operations or information disclosure.

Original description

The description as published by the source.

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.

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-93050 has been found in Linux kernel.
Risk of unauthorized operations or information disclosure.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Linux kernel CVE-2026-93050" on the vendor's site.

CVE-2026-93050 (Linux kernel)
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (unclassified) exists in Linux kernel.

📍 Affected scope

Check the vendor advisory for the affected versions of Linux kernel.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで Linux kernel を使っているサービスとバージョンを洗い出す。

  2. 2
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details