{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-92504 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-92504 is a high-severity memory corruption 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-92504 and fix it if it is affected.\n\nWhat it is: CVE-2026-92504 is a high-severity memory corruption 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-92504 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-92504/ (Markdown: https://insights.sbomify.com/CVE-2026-92504/index.md)","id":"CVE-2026-92504","markdown":"https://insights.sbomify.com/CVE-2026-92504/index.md","name":"CVE-2026-92504","record":{"aliases":["AZL-101945","BELL-CVE-2026-92504","DEBIAN-CVE-2026-92504","GHSA-jr28-r3rj-w85q","UBUNTU-CVE-2026-92504"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel thermal driver","requires_auth":"low_privilege","summary":"A memory leak in the Intel int3400 thermal driver occurs when probe operations fail, potentially leading to resource exhaustion and denial of service.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":7,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nthermal: intel: int3400: clean up ODVP on probe failures\n\nevaluate_odvp() creates per-ODVP sysfs files before the thermal zone\nand later probe resources are registered. The current unwind path only\ncalls cleanup_odvp() from the late sysfs failure path, so failures after\nevaluate_odvp() but before that label, including\nthermal_tripless_zone_device_register() failures, leave the ODVP files\nand storage behind.\n\nMove the ODVP cleanup to the common ART/TRT unwind path so every failure\nafter evaluate_odvp() releases the ODVP state. Also clear the cached\nODVP pointers in cleanup_odvp(), because evaluate_odvp() can already call\nit for partial setup failures while probe continues.","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: intel: int3400: clean up ODVP on probe failures","id":"CVE-2026-92504","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"iommu/amd: Fix undefined behavior in devid_write debugfs function","id":"CVE-2026-92505"},"packages":[],"prev":{"headline":"ext4: fix ABBA deadlock in ext4_xattr_inode_cache_find()","id":"CVE-2026-92503"},"products":["Linux"],"published":"2026-09-17","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"A memory leak in the Intel int3400 thermal driver occurs when probe operations fail, potentially leading to resource exhaustion and denial of service.","url":"https://insights.sbomify.com/CVE-2026-92504/"}