{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-80974 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-80974 is a memory corruption vulnerability in Linux, published on 11 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-80974 and fix it if it is affected.\n\nWhat it is: CVE-2026-80974 is a memory corruption vulnerability in Linux, published on 11 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-80974 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-80974/ (Markdown: https://insights.sbomify.com/CVE-2026-80974/index.md)","id":"CVE-2026-80974","markdown":"https://insights.sbomify.com/CVE-2026-80974/index.md","name":"CVE-2026-80974","record":{"aliases":["AZL-100436","BELL-CVE-2026-80974","DEBIAN-CVE-2026-80974","GHSA-hjr6-6hh3-pw85","UBUNTU-CVE-2026-80974"],"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 SM501 MFD driver during device removal 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\nmfd: sm501: Fix potential memory leaks during remove\n\nThe memory allocated for struct sm501_devdata in sm501_pci_probe() and\nsm501_plat_probe() is not freed by the corresponding remove functions\nsm501_pci_remove() and sm501_plat_remove(). Fix that by adding a call to\nkfree().","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":"mfd: sm501: Fix potential memory leaks during remove","id":"CVE-2026-80974","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"mfd: qnap-mcu: keep the reply buffer alive past a command timeout","id":"CVE-2026-80975"},"packages":[],"prev":{"headline":"ALSA: 6fire: bound the MIDI event length from the device","id":"CVE-2026-80973"},"products":["Linux"],"published":"2026-09-11","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-21","vendors":["Linux"]},"summary":"A memory leak in the SM501 MFD driver during device removal can lead to resource exhaustion and denial of service.","url":"https://insights.sbomify.com/CVE-2026-80974/"}