{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-90107 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-90107 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-90107 and fix it if it is affected.\n\nWhat it is: CVE-2026-90107 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-90107 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-90107/ (Markdown: https://insights.sbomify.com/CVE-2026-90107/index.md)","id":"CVE-2026-90107","markdown":"https://insights.sbomify.com/CVE-2026-90107/index.md","name":"CVE-2026-90107","record":{"aliases":["AZL-102797","BELL-CVE-2026-90107","DEBIAN-CVE-2026-90107","GHSA-mw8r-cvfc-f297","UBUNTU-CVE-2026-90107"],"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 via crafted network messages, 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 pending qentry in smc_llc_flow_stop() before memset\n\nsmc_llc_flow_stop() resets a flow struct with a blind memset:\n\n\tspin_lock_bh(\u0026lgr-\u003ellc_flow_lock);\n\tmemset(flow, 0, sizeof(*flow));\n\tflow-\u003etype = SMC_LLC_FLOW_NONE;\n\tspin_unlock_bh(\u0026lgr-\u003ellc_flow_lock);\n\nIf flow-\u003eqentry is non-NULL at this point the pointer is overwritten without the\nallocation being freed, leaking one kmalloc object.\n\nA late-arriving duplicate CONFIRM_LINK or ADD_LINK_CONT message can set\nflow-\u003eqentry after the legitimate message has been consumed by the waiter via\nsmc_llc_flow_qentry_clr() (which NULLs the pointer but leaves flow-\u003etype\nnon-zero) but before the flow completes and smc_llc_flow_stop() runs.  In that\nwindow the duplicate is stashed into flow-\u003eqentry, and then lost when\nsmc_llc_flow_stop() zeros the struct.\n\nCall smc_llc_flow_qentry_del() inside the lock before the memset.\nsmc_llc_flow_qentry_del() already checks flow-\u003eqentry before freeing, so the\nnormal case where no entry is pending 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 pending qentry in smc_llc_flow_stop() before memset","id":"CVE-2026-90107","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"net/smc: free stashed qentry before overwrite in REQ_ADD_LINK to ADD_LINK transition","id":"CVE-2026-90108"},"packages":[],"prev":{"headline":"net: bridge: arp/nd proxy: fix reading neigh ha","id":"CVE-2026-90106"},"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 via crafted network messages, causing denial of service.","url":"https://insights.sbomify.com/CVE-2026-90107/"}