{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-90108 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-90108 is a memory corruption vulnerability in Linux, published on 17 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-90108 and fix it if it is affected.\n\nWhat it is: CVE-2026-90108 is a memory corruption vulnerability in Linux, published on 17 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-90108 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-90108/ (Markdown: https://insights.sbomify.com/CVE-2026-90108/index.md)","id":"CVE-2026-90108","markdown":"https://insights.sbomify.com/CVE-2026-90108/index.md","name":"CVE-2026-90108","record":{"aliases":["AZL-102848","BELL-CVE-2026-90108","DEBIAN-CVE-2026-90108","GHSA-6x7f-mrc2-297f","UBUNTU-CVE-2026-90108"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Linux kernel","requires_auth":"none","summary":"A memory leak in the Linux kernel SMC protocol allows remote attackers to exhaust kernel memory, causing 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\nnet/smc: free stashed qentry before overwrite in REQ_ADD_LINK to ADD_LINK transition\n\nWhen smc_llc_event_handler() transitions the local LLC flow from\nSMC_LLC_FLOW_REQ_ADD_LINK to SMC_LLC_FLOW_ADD_LINK on arrival of an ADD_LINK\nrequest, it calls smc_llc_flow_qentry_set() unconditionally:\n\n\tif (lgr-\u003ellc_flow_lcl.type == SMC_LLC_FLOW_REQ_ADD_LINK) {\n\t\tlgr-\u003ellc_flow_lcl.type = SMC_LLC_FLOW_ADD_LINK;\n\t\tsmc_llc_flow_qentry_set(\u0026lgr-\u003ellc_flow_lcl, qentry);\n\t\t...\n\t}\n\nA CONFIRM_LINK or ADD_LINK_CONT arriving while flow-\u003etype is\nSMC_LLC_FLOW_REQ_ADD_LINK is stashed into flow-\u003eqentry via the\nSMC_LLC_CONFIRM_LINK / SMC_LLC_ADD_LINK_CONT handler (which stores into\nflow-\u003eqentry for any non-NONE flow type).  When the subsequent ADD_LINK\narrives, the REQ_ADD_LINK branch overwrites flow-\u003eqentry with the new pointer\nwithout first freeing the stashed allocation, leaking one kmalloc object.\n\nThe stashed entry has no consumer: smc_llc_wait() is only called from\nllc_add_link_work, which is not yet scheduled while the flow type remains\nREQ_ADD_LINK.  No waiter is sleeping on llc_msg_waiter at this point.\nIt is safe to unconditionally free any stashed qentry before\nthe overwrite.\n\nCall smc_llc_flow_qentry_del() before smc_llc_flow_qentry_set() in the\nREQ_ADD_LINK branch.  smc_llc_flow_qentry_del() already checks flow-\u003eqentry\nbefore freeing, so the normal path where no entry is stashed is a no-op.","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":"net/smc: free stashed qentry before overwrite in REQ_ADD_LINK to ADD_LINK transition","id":"CVE-2026-90108","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"net: sched: fix 32-bit backlog wrap in gred, bfifo and plug enqueue","id":"CVE-2026-90109"},"packages":[],"prev":{"headline":"net/smc: free pending qentry in smc_llc_flow_stop() before memset","id":"CVE-2026-90107"},"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 memory leak in the Linux kernel SMC protocol allows remote attackers to exhaust kernel memory, causing denial of service.","url":"https://insights.sbomify.com/CVE-2026-90108/"}