{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-93142 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-93142 is a 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-93142 and fix it if it is affected.\n\nWhat it is: CVE-2026-93142 is a 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-93142 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-93142/ (Markdown: https://insights.sbomify.com/CVE-2026-93142/index.md)","id":"CVE-2026-93142","markdown":"https://insights.sbomify.com/CVE-2026-93142/index.md","name":"CVE-2026-93142","record":{"aliases":["AZL-102708","BELL-CVE-2026-93142","DEBIAN-CVE-2026-93142","GHSA-hm78-cgjx-c8pf","UBUNTU-CVE-2026-93142"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel driver","requires_auth":"none","summary":"A null pointer dereference in the Linux kernel rcar thermal driver probe function can cause a system crash, requiring a kernel patch.","user_interaction":"not_required","vuln_class":"null_dereference"},"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\nthermal/drivers/rcar: Fix error checking in probe()\n\nThis code accidentally calls thermal_zone_device_enable() before checking\nwhether thermal_zone_device_register_with_trips() failed.  Move the call\nuntil later to avoid an error pointer dereference of \"priv-\u003ezone\".\n\nThe driver works differently depending on if we are using OF thermal or\nnot.  We use thermal_add_hwmon_sysfs() if we are using OF thermal and\ncall thermal_zone_device_enable() if not.  We can share same error check\nfor if either of these fail.\n\nMoving the thermal_zone_device_enable() call is a bit cleaner as well.\nThe original code used a three step process to cleanup:\n1. Call thermal_zone_device_unregister() to cleanup.\n2. Set priv-\u003ezone to an error pointer to preserve the error code.\n3. Set priv-\u003ezone to NULL to avoid a second call to\n   thermal_zone_device_unregister() in the rcar_thermal_remove()\n   function.\n\nNow we can just do a direct goto error_unregister and rcar_thermal_remove()\nhandles the cleanup properly.","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":"thermal/drivers/rcar: Fix error checking in probe()","id":"CVE-2026-93142","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"staging: media: ipu7: fix pm_runtime refcount leak in ipu7_resume()","id":"CVE-2026-93143"},"packages":[],"prev":{"headline":"usb: gadget: r8a66597: avoid double free of ep0_req in probe error path","id":"CVE-2026-93141"},"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":"A null pointer dereference in the Linux kernel rcar thermal driver probe function can cause a system crash, requiring a kernel patch.","url":"https://insights.sbomify.com/CVE-2026-93142/"}