{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-92483 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-92483 is an use after free 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-92483 and fix it if it is affected.\n\nWhat it is: CVE-2026-92483 is an use after free 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-92483 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-92483/ (Markdown: https://insights.sbomify.com/CVE-2026-92483/index.md)","id":"CVE-2026-92483","markdown":"https://insights.sbomify.com/CVE-2026-92483/index.md","name":"CVE-2026-92483","record":{"aliases":["DEBIAN-CVE-2026-92483","GHSA-ppch-xf6h-8vx5","UBUNTU-CVE-2026-92483"],"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 local attacker can trigger a use-after-free in the Linux kernel liveupdate module by retrying a failed file retrieval, potentially leading to code execution or privilege escalation.","user_interaction":"not_required","vuln_class":"use_after_free"},"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\nliveupdate: Remember FLB retrieve() status\n\nLUO keeps track of successful retrieve attempts on an FLB. It does so\nto avoid multiple retrievals of the same FLB. Multiple retrievals cause\nproblems because once the FLB is retrieved, the serialized data\nstructures are likely freed and the FLB is likely in a very different\nstate from what the code expects.\n\nAll this works well when retrieve succeeds. When it fails,\nluo_flb_retrieve_one() returns the error immediately, without ever\nstoring anywhere that a retrieve was attempted or what its error code\nwas. If the user attempts to retrieve another file registered with the\nsame FLB, LUO will attempt to call the FLB's retrieve() callback again.\n\nThe retry is problematic for much of the same reasons listed above. The\nFLB is likely in a very different state than what the retrieve logic\nnormally expects (e.g. some KHO pages may have already been restored and\nfreed).\n\nThere is no sane way of attempting the retrieve again. Remember the\nerror retrieve returned and directly return it on a retry.\n\nThis is done by changing the retrieved bool to a retrieve_status\ninteger. A value of 0 means retrieve was never attempted, a positive\nvalue means it succeeded, and a negative value means it failed and the\nerror code is the value.\n\nThis is similar to commit f85b1c6af5bc (\"liveupdate: luo_file: remember\nretrieve() status\") which did the same for LUO files.","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":"liveupdate: Remember FLB retrieve() status","id":"CVE-2026-92483","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"use_after_free","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"cxl/region: Fix use-after-free in find_pos_and_ways() error path","id":"CVE-2026-92484"},"packages":[],"prev":{"headline":"pinctrl: mediatek: use devm_gpiochip_add_data() for GPIO chip","id":"CVE-2026-92482"},"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 local attacker can trigger a use-after-free in the Linux kernel liveupdate module by retrying a failed file retrieval, potentially leading to code execution or privilege escalation.","url":"https://insights.sbomify.com/CVE-2026-92483/"}