{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-80928 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-80928 is a high-severity use after free 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-80928 and fix it if it is affected.\n\nWhat it is: CVE-2026-80928 is a high-severity use after free 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-80928 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-80928/ (Markdown: https://insights.sbomify.com/CVE-2026-80928/index.md)","id":"CVE-2026-80928","markdown":"https://insights.sbomify.com/CVE-2026-80928/index.md","name":"CVE-2026-80928","record":{"aliases":["AZL-100172","BELL-CVE-2026-80928","DEBIAN-CVE-2026-80928","GHSA-pw4j-jrv7-fq3m","UBUNTU-CVE-2026-80928"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"A use-after-free vulnerability in the Linux kernel's SMACK security module allows attackers to potentially execute code or escalate privileges via a race condition.","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":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nsmack: fix cred UAF in smack_file_send_sigiotask()\n\nWhen inspecting the credentials of another task, objective credentials\n(-\u003ereal_cred, accessed with __task_cred()) must always be used.\n\nAccessing -\u003ecred on a non-current task is forbidden unless that task is\nbeing created or destroyed; a task is allowed to change its own -\u003ecred\npointer with no synchronization, and changing -\u003ecred should only affect the\ncurrent syscall.\n\nsmack_file_send_sigiotask() was accessing both sets of credentials: First\ntsk-\u003ecred, then __task_cred(tsk).\n\nFix it, always access the objective credentials here.\n\nI have tested that this bug can lead to a KASAN-reported UAF of struct cred\nin smack_file_send_sigiotask(), and that this fix prevents the race.","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":"smack: fix cred UAF in smack_file_send_sigiotask()","id":"CVE-2026-80928","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"use_after_free","year":"2026"},"n_packages":0,"n_references":7,"next":{"headline":"sysctl: move the \"cad_pid\" entry from pid_table[] to kern_reboot_table[]","id":"CVE-2026-80929"},"packages":[],"prev":{"headline":"timekeeping: Check the return value of tk_get_aux_ts64 in __do_adjtimex()","id":"CVE-2026-80927"},"products":["Linux"],"published":"2026-09-11","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 use-after-free vulnerability in the Linux kernel's SMACK security module allows attackers to potentially execute code or escalate privileges via a race condition.","url":"https://insights.sbomify.com/CVE-2026-80928/"}