{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-68178 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-68178 is a high-severity use after free vulnerability in Linux, published on 10 Aug 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-68178 and fix it if it is affected.\n\nWhat it is: CVE-2026-68178 is a high-severity use after free vulnerability in Linux, published on 10 Aug 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-68178 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-68178/ (Markdown: https://insights.sbomify.com/CVE-2026-68178/index.md)","id":"CVE-2026-68178","markdown":"https://insights.sbomify.com/CVE-2026-68178/index.md","name":"CVE-2026-68178","record":{"aliases":["BELL-CVE-2026-68178","DEBIAN-CVE-2026-68178","GHSA-785r-497w-84xv","UBUNTU-CVE-2026-68178"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"An attacker with an open file descriptor can trigger a use-after-free by unloading the NSM kernel module, potentially leading to code execution or privilege escalation.","user_interaction":"not_required","vuln_class":"use_after_free"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":7.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-416","name":"Use After Free"}],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nmisc: nsm: pin the module while the device is open\n\nmisc_open() installs a misc driver's file operations with fops_get(),\nwhich pins file_operations::owner before replacing the file's f_op.  The\nNSM misc device leaves nsm_dev_fops.owner unset, so opening /dev/nsm does\nnot take a module reference on the nsm driver.\n\nIf the driver is built as a module, an open file descriptor can therefore\nsurvive rmmod of the module that provides its ioctl callbacks.  A later\nioctl through that descriptor can call into unloaded module text.\n\nSet nsm_dev_fops.owner to THIS_MODULE so the misc core holds the module\nwhile any /dev/nsm file descriptor is open, matching the lifetime\nexpectation for the installed file operations.","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":"misc: nsm: pin the module while the device is open","id":"CVE-2026-68178","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"use_after_free","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"misc: nsm: only unlock nsm_dev on post-lock error paths","id":"CVE-2026-68179"},"packages":[],"prev":{"headline":"tracing: Delay module ref count for \"enable_event\" trigger","id":"CVE-2026-68177"},"products":["Linux"],"published":"2026-08-10","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"An attacker with an open file descriptor can trigger a use-after-free by unloading the NSM kernel module, potentially leading to code execution or privilege escalation.","url":"https://insights.sbomify.com/CVE-2026-68178/"}