{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-93050 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-93050 is an use after free vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-93050 and fix it if it is affected.\n\nWhat it is: CVE-2026-93050 is an use after free vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-93050 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-93050/ (Markdown: https://insights.sbomify.com/CVE-2026-93050/index.md)","id":"CVE-2026-93050","markdown":"https://insights.sbomify.com/CVE-2026-93050/index.md","name":"CVE-2026-93050","record":{"aliases":["AZL-102318","BELL-CVE-2026-93050","DEBIAN-CVE-2026-93050","GHSA-7qcc-hqrm-qfrj","UBUNTU-CVE-2026-93050"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["privilege_escalation","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel driver","requires_auth":"low_privilege","summary":"Local attackers can trigger use-after-free and null pointer dereference in the ipoctal driver during device removal, potentially leading to privilege escalation or system crash.","user_interaction":"not_required","vuln_class":"use_after_free"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"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-\u003edev)\n   dereferences ipoctal-\u003edev after the ipack_device has been freed\n   by ipack_device_del().  Fix by caching ipoctal-\u003ecarrier_owner\n   during probe() and calling module_put() on the cached pointer\n   directly in cleanup(), avoiding any access to ipoctal-\u003edev.\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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"ipack: ipoctal: fix UAF, null-ptr-deref, and use-after-free in cleanup on remove","id":"CVE-2026-93050","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"use_after_free","year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"misc: ad525x_dpot: use driver core groups for sysfs files","id":"CVE-2026-93051"},"packages":[],"prev":{"headline":"mtd: mtdswap: Avoid freeing registered blktrans device twice","id":"CVE-2026-93049"},"products":["Linux"],"published":"2026-09-17","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"Local attackers can trigger use-after-free and null pointer dereference in the ipoctal driver during device removal, potentially leading to privilege escalation or system crash.","url":"https://insights.sbomify.com/CVE-2026-93050/"}