{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-93127 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-93127 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-93127 and fix it if it is affected.\n\nWhat it is: CVE-2026-93127 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-93127 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-93127/ (Markdown: https://insights.sbomify.com/CVE-2026-93127/index.md)","id":"CVE-2026-93127","markdown":"https://insights.sbomify.com/CVE-2026-93127/index.md","name":"CVE-2026-93127","record":{"aliases":["DEBIAN-CVE-2026-93127","GHSA-6crf-588f-8r2f","UBUNTU-CVE-2026-93127"],"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 BPF","requires_auth":"low_privilege","summary":"A flaw in the Linux kernel BPF verifier allows out-of-bounds memory access due to incorrect scalar ID handling during sign-extending loads, potentially enabling privilege escalation.","user_interaction":"not_required","vuln_class":"memory_corruption"},"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\nbpf: Drop scalar id on sign-extending narrowing stack fills\n\nWhen a spilled scalar is filled back with a sign-extending narrowing load\n(BPF_MEMSX), check_stack_read_fixed_off() copies the spilled register\nincluding its scalar id, but coerce_reg_to_size_sx() then sign-extends the\nfilled register's value. If the same slot is also filled with a plain\nzero-extending load (BPF_MEM), both destination registers share the id yet\nhold different values. A later 'if \u003czext-reg\u003e == const' then refines the\nsign-extended register through sync_linked_regs() to a value it does not\nhave at runtime (e.g. the verifier believes 0x80000000 while the register\nis 0xffffffff80000000), which can be turned into an out-of-bounds access.\n\nDrop the shared scalar id at the sign-extension site in check_mem_access()\nwhen sign extension actually changes the value, mirroring the BPF_MOVSX\nhandling in check_alu_op() (no_sext = reg_umax \u003c 2^(size*8-1)).","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":"bpf: Drop scalar id on sign-extending narrowing stack fills","id":"CVE-2026-93127","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"platform/x86: lg-laptop: Fix LED resource handling","id":"CVE-2026-93128"},"packages":[],"prev":{"headline":"remoteproc: qcom_q6v5_adsp: Fix reference leak for device node","id":"CVE-2026-93126"},"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 flaw in the Linux kernel BPF verifier allows out-of-bounds memory access due to incorrect scalar ID handling during sign-extending loads, potentially enabling privilege escalation.","url":"https://insights.sbomify.com/CVE-2026-93127/"}