{"answers":{"affected":"It affects 3 products.","exploited":"Yes. Attackers have exploited CVE-2025-39964 in the wild since at least 18 Sep 2026.","fix":"Apply the vendor's patch. US federal agencies must fix it by 21 Sep 2026.","what":"CVE-2025-39964 is a high-severity vulnerability in Linux kernel, published on 13 Oct 2025. 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-2025-39964 and fix it if it is affected.\n\nWhat it is: CVE-2025-39964 is a high-severity vulnerability in Linux kernel, published on 13 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: Yes. Attackers have exploited CVE-2025-39964 in the wild since at least 18 Sep 2026.\n\nAffected product: Linux kernel. 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-2025-39964/ (Markdown: https://insights.sbomify.com/CVE-2025-39964/index.md)","id":"CVE-2025-39964","markdown":"https://insights.sbomify.com/CVE-2025-39964/index.md","name":"CVE-2025-39964","record":{"aliases":["AZL-68460","AZL-76437","BELL-CVE-2025-39964","DEBIAN-CVE-2025-39964","GHSA-wr5g-mfhw-rpfj","ROOT-OS-DEBIAN-11-CVE-2025-39964","ROOT-OS-DEBIAN-12-CVE-2025-39964","ROOT-OS-DEBIAN-13-CVE-2025-39964","ROOT-OS-UBUNTU-2204-CVE-2025-39964","ROOT-OS-UBUNTU-2404-CVE-2025-39964","UBUNTU-CVE-2025-39964"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["data_modify","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"Concurrent writes to an af_alg socket can cause data interleaving and internal state inconsistencies, potentially leading to data corruption or denial of service.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[{"product":"linux_kernel","vendor":"linux"},{"product":"simatic_s7-1500_cpu_1518-4_pn\\/dp_mfp_firmware","vendor":"siemens"},{"product":"simatic_s7-1500_cpu_1518f-4_pn\\/dp_mfp_firmware","vendor":"siemens"}],"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":[{"id":"CWE-362","name":"Concurrent Execution using Shared Resource with Improper Synchronization"}],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: af_alg - Disallow concurrent writes in af_alg_sendmsg\n\nIssuing two writes to the same af_alg socket is bogus as the\ndata will be interleaved in an unpredictable fashion.  Furthermore,\nconcurrent writes may create inconsistencies in the internal\nsocket state.\n\nDisallow this by adding a new ctx-\u003ewrite field that indiciates\nexclusive ownership for writing.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2025-11-13","github_poc":2,"max_poc_stars":3,"metasploit":0,"nuclei":0,"refs":[{"date":"2025-11-13T13:07:19Z","kind":"github_poc","ref":"https://github.com/n1k0oowang/CVE-2025-39964_EXP","stars":3,"title":"CVE-2025-39964 EXP"},{"date":"2026-09-20T05:55:14Z","kind":"github_poc","ref":"https://github.com/suominen/CVE-2025-39964","stars":0,"title":"Tracking CVE-2025-39964, the Linux kernel AF_ALG concurrent-write race"}],"tier":"exploited"},"has_fix":true,"headline":"Linux Kernel Race Condition","id":"CVE-2025-39964","indexable":true,"kev":{"dateAdded":"2026-09-18","dueDate":"2026-09-21","knownRansomwareCampaignUse":"Unknown","product":"Kernel","requiredAction":"Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.","vendorProject":"Linux","vulnerabilityName":"Linux Kernel Race Condition Vulnerability"},"kind":"cve","links":{"ecosystem":null,"product":"linux:linux_kernel","products":["linux:linux_kernel"],"type":"race_condition","year":"2025"},"n_packages":0,"n_references":7,"next":{"headline":"xfrm: xfrm_alloc_spi shouldn't use 0 as SPI","id":"CVE-2025-39965"},"packages":[],"prev":{"headline":"io_uring: fix incorrect io_kiocb reference in io_link_skb","id":"CVE-2025-39963"},"products":["Linux"],"published":"2025-10-13","related":[{"cvss_score":8.8,"headline":"Linux Kernel Out-of-Bounds Write","id":"CVE-2026-53266","kev_date_added":"2026-09-18","published":"2026-06-25"},{"cvss_score":8.8,"headline":"Linux Kernel Improper Input Validation","id":"CVE-2013-6282","kev_date_added":"2022-09-15","published":"2013-11-19"},{"cvss_score":8.4,"headline":"Linux Kernel Heap-Based Buffer Overflow","id":"CVE-2022-0185","kev_date_added":"2024-08-21","published":"2022-02-11"},{"cvss_score":8.4,"headline":"Linux Kernel Privilege Escalation","id":"CVE-2013-2094","kev_date_added":"2022-09-15","published":"2013-05-14"},{"cvss_score":7.8,"headline":"Linux Kernel Unspecified","id":"CVE-2026-53362","kev_date_added":"2026-08-27","published":"2026-07-04"},{"cvss_score":7.8,"headline":"Linux Kernel Missing Initialization of a Variable","id":"CVE-2026-46300","kev_date_added":"2026-10-28","published":"2026-05-23"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"open","licence":"CC0 1.0","name":"CISA KEV"},{"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":"active","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-10-15","vendors":["Linux"]},"summary":"Concurrent writes to an af_alg socket can cause data interleaving and internal state inconsistencies, potentially leading to data corruption or denial of service.","url":"https://insights.sbomify.com/CVE-2025-39964/"}