{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-90178 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-90178 is a 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-90178 and fix it if it is affected.\n\nWhat it is: CVE-2026-90178 is a 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-90178 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-90178/ (Markdown: https://insights.sbomify.com/CVE-2026-90178/index.md)","id":"CVE-2026-90178","markdown":"https://insights.sbomify.com/CVE-2026-90178/index.md","name":"CVE-2026-90178","record":{"aliases":["BELL-CVE-2026-90178","DEBIAN-CVE-2026-90178","GHSA-r39r-j9pr-wc8x","UBUNTU-CVE-2026-90178"],"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 memory leak in the Linux kernel coretemp driver on CPUs without PTS support can lead 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":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nhwmon: (coretemp) Fix core_data leak on CPUs without PTS\n\npdata-\u003ecore_data is allocated in init_temp_data() when the first core\ntemp_data of a package is created, but it is only released from\ndestroy_temp_data(), and only in the branch that handles the package\ntemp_data.\n\nPackage temp_data is created solely when the CPU supports\nX86_FEATURE_PTS. On a CPU without it, coretemp_cpu_online() never calls\ncoretemp_add_core() with pkg_flag set, so pdata-\u003epkg_data stays NULL.\ncoretemp_cpu_offline() then skips the removal of the package interface,\ndestroy_temp_data() is never called for package data, and the array is\nstill allocated when coretemp_device_remove() frees the platform data\nthat pointed at it.\n\nRelease the array in coretemp_device_remove(). destroy_temp_data() sets\npdata-\u003ecore_data to NULL when it frees it, so the added kfree() is a\nno-op on CPUs that do have PTS.\n\nTested on an Intel Core i5-1135G7. The driver was instrumented to log\nevery allocation and release of pdata-\u003ecore_data, and the PTS check in\ncoretemp_cpu_online() was patched out to emulate a CPU without package\nthermal support. Without this change the array was allocated and never\nreleased, and coretemp_device_remove() still saw a non-NULL pointer.\nWith it the array is released and the pointer accounting balances. On an\nunmodified build the release still happens via the package temp_data and\nthe added kfree() sees NULL, with no slab warnings over repeated module\nload and unload cycles.","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":"hwmon: (coretemp) Fix core_data leak on CPUs without PTS","id":"CVE-2026-90178","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"apparmor: fix deadlock in complain-mode change_hat","id":"CVE-2026-90179"},"packages":[],"prev":{"headline":"bpf: Check pointer type for all atomic RMW paths","id":"CVE-2026-90177"},"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 memory leak in the Linux kernel coretemp driver on CPUs without PTS support can lead to resource exhaustion and denial of service.","url":"https://insights.sbomify.com/CVE-2026-90178/"}