{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-93263 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-93263 is a vulnerability in Linux, published on 24 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-93263 and fix it if it is affected.\n\nWhat it is: CVE-2026-93263 is a vulnerability in Linux, published on 24 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-93263 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-93263/ (Markdown: https://insights.sbomify.com/CVE-2026-93263/index.md)","id":"CVE-2026-93263","markdown":"https://insights.sbomify.com/CVE-2026-93263/index.md","name":"CVE-2026-93263","record":{"aliases":["DEBIAN-CVE-2026-93263","GHSA-vqxw-79f6-p4wm","UBUNTU-CVE-2026-93263"],"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 missing zero-initialization in the Linux kernel ESWIN clock driver causes a null pointer dereference, leading to a system crash.","user_interaction":"not_required","vuln_class":"null_dereference"},"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\nclk: eswin: Zero-initialize stack-allocated clk_init_data\n\neswin_clk_register_pll() and eswin_register_clkdiv() declare a struct\nclk_init_data on the stack and only initialize some of its fields\n(parent_data respectively parent_hws). clk_core_populate_parent_map()\nchecks parent_names first and parent_data second before falling back\nto parent_hws, so leftover stack garbage in the uninitialized fields\nhijacks parent resolution and the clk core dereferences a bogus\npointer:\n\n  Unable to handle kernel NULL pointer dereference at virtual address 000000000000000c\n  Oops [#1]\n  epc : __clk_register+0x31a/0x7f0\n  [\u003cffffffff805dc774\u003e] __clk_register+0x31a/0x7f0\n  [\u003cffffffff805dcd76\u003e] devm_clk_hw_register+0x2a/0x94\n  [\u003cffffffff805e319a\u003e] eswin_register_clkdiv+0x80/0xd0\n  [\u003cffffffff805e34a0\u003e] eswin_clk_register_clks+0x162/0x1a0\n  [\u003cffffffff805e3736\u003e] eic7700_clk_probe+0x146/0x180\n  [\u003cffffffff8065d23c\u003e] platform_probe+0x3c/0x7a\n\nObserved on EIC7700 hardware (with the driver backported to a 6.17\ntree); whether the bug triggers depends entirely on what the stack\nhappens to contain when the registration helpers run.\n\nZero-initialize both structures.","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":"clk: eswin: Zero-initialize stack-allocated clk_init_data","id":"CVE-2026-93263","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"RDMA/efa: Fix PBL chunk length computation","id":"CVE-2026-93264"},"packages":[],"prev":{"headline":"md/raid5-ppl: fix use-after-free in ppl_do_flush()","id":"CVE-2026-93262"},"products":["Linux"],"published":"2026-09-24","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 missing zero-initialization in the Linux kernel ESWIN clock driver causes a null pointer dereference, leading to a system crash.","url":"https://insights.sbomify.com/CVE-2026-93263/"}