{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-68376 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-68376 is a high-severity memory corruption vulnerability in Linux, published on 10 Aug 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-68376 and fix it if it is affected.\n\nWhat it is: CVE-2026-68376 is a high-severity memory corruption vulnerability in Linux, published on 10 Aug 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-68376 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-68376/ (Markdown: https://insights.sbomify.com/CVE-2026-68376/index.md)","id":"CVE-2026-68376","markdown":"https://insights.sbomify.com/CVE-2026-68376/index.md","name":"CVE-2026-68376","record":{"aliases":["BELL-CVE-2026-68376","DEBIAN-CVE-2026-68376","GHSA-55hr-9mvf-6m8f","UBUNTU-CVE-2026-68376"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Linux kernel SCTP","requires_auth":"none","summary":"A buffer overflow in the Linux kernel SCTP implementation allows attackers to corrupt memory, potentially leading to code execution or system crashes.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":8.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"}],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nsctp: fix auth_hmacs array size in struct sctp_cookie\n\nThe auth_hmacs array in struct sctp_cookie is supposed to store a complete\nSCTP_AUTH_HMAC_ALGO parameter, which consists of a struct sctp_paramhdr\nfollowed by N HMAC identifiers.\n\nHowever, the array size was calculated using an extra 2 bytes instead of\nsizeof(struct sctp_paramhdr), which is 4 bytes. When four HMAC identifiers\nare configured, the HMAC-ALGO parameter stored in the endpoint is larger\nthan the auth_hmacs buffer in the cookie.\n\nAs a result, sctp_association_init() copies beyond the end of auth_hmacs\nwhen initializing the association, corrupting the adjacent auth_chunks\nfield. This can lead to an invalid HMAC identifier being accepted and later\ncause an out-of-bounds read in sctp_auth_get_hmac().\n\nFix the array size calculation by including the full SCTP parameter header\nsize.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2026-09-22","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-09-22T11:06:25Z","kind":"github_poc","ref":"https://github.com/gagaltotal/CVE-2026-68376-Ubuntu-7.0.0-30-Poc","stars":0,"title":"CVE-2026-68376 - Ubuntu Kernel 7.0.0-30"}],"tier":"poc_unverified"},"has_fix":true,"headline":"sctp: fix auth_hmacs array size in struct sctp_cookie","id":"CVE-2026-68376","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/sched: act_tunnel_key: Defer dst_release to RCU callback","id":"CVE-2026-68377"},"packages":[],"prev":{"headline":"bnxt_en: Handle partially initialized auxiliary devices","id":"CVE-2026-68375"},"products":["Linux"],"published":"2026-08-10","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"A buffer overflow in the Linux kernel SCTP implementation allows attackers to corrupt memory, potentially leading to code execution or system crashes.","url":"https://insights.sbomify.com/CVE-2026-68376/"}