{"answers":{"affected":"It affects 3 products.","exploited":"Yes. Attackers have exploited CVE-2025-39682 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-39682 is a critical denial of service vulnerability in Debian Debian Linux, published on 5 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-39682 and fix it if it is affected.\n\nWhat it is: CVE-2025-39682 is a critical denial of service vulnerability in Debian Debian Linux, published on 5 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: Yes. Attackers have exploited CVE-2025-39682 in the wild since at least 18 Sep 2026.\n\nAffected product: Debian Debian 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-2025-39682/ (Markdown: https://insights.sbomify.com/CVE-2025-39682/index.md)","id":"CVE-2025-39682","markdown":"https://insights.sbomify.com/CVE-2025-39682/index.md","name":"CVE-2025-39682","record":{"aliases":["A-440544511","ASB-A-440544511","AZL-67001","BELL-CVE-2025-39682","DEBIAN-CVE-2025-39682","GHSA-v2pf-75pf-9c5h","ROOT-OS-DEBIAN-12-CVE-2025-39682","ROOT-OS-DEBIAN-13-CVE-2025-39682","ROOT-OS-UBUNTU-2404-CVE-2025-39682","UBUNTU-CVE-2025-39682"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Linux kernel TLS","requires_auth":"none","summary":"A flaw in Linux kernel TLS handling of zero-length records can cause a denial of service by breaking the receive message processing loop.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[{"product":"debian_linux","vendor":"debian"},{"product":"linux_kernel","vendor":"linux"},{"product":"simatic_cn_4100_firmware","vendor":"siemens"}],"cvss":{"score":9.8,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-754","name":"Improper Check for Unusual or Exceptional Conditions"}],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\ntls: fix handling of zero-length records on the rx_list\n\nEach recvmsg() call must process either\n - only contiguous DATA records (any number of them)\n - one non-DATA record\n\nIf the next record has different type than what has already been\nprocessed we break out of the main processing loop. If the record\nhas already been decrypted (which may be the case for TLS 1.3 where\nwe don't know type until decryption) we queue the pending record\nto the rx_list. Next recvmsg() will pick it up from there.\n\nQueuing the skb to rx_list after zero-copy decrypt is not possible,\nsince in that case we decrypted directly to the user space buffer,\nand we don't have an skb to queue (darg.skb points to the ciphertext\nskb for access to metadata like length).\n\nOnly data records are allowed zero-copy, and we break the processing\nloop after each non-data record. So we should never zero-copy and\nthen find out that the record type has changed. The corner case\nwe missed is when the initial record comes from rx_list, and it's\nzero length.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2025-10-14","github_poc":2,"max_poc_stars":6,"metasploit":0,"nuclei":0,"refs":[{"date":"2025-10-14T07:59:03Z","kind":"github_poc","ref":"https://github.com/khoatran107/cve-2025-39682","stars":6,"title":"A variant of CVE-2024-58239"},{"date":"2026-09-20T05:58:09Z","kind":"github_poc","ref":"https://github.com/suominen/CVE-2025-39682","stars":0,"title":"Tracking CVE-2025-39682, the Linux kernel kTLS zero-length record use-after-free"}],"tier":"exploited"},"has_fix":true,"headline":"Linux Kernel Improper Check for Unusual or Exceptional Conditions","id":"CVE-2025-39682","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 Improper Check for Unusual or Exceptional Conditions Vulnerability"},"kind":"cve","links":{"ecosystem":null,"product":"debian:debian_linux","products":["debian:debian_linux","linux:linux_kernel"],"type":"denial_of_service","year":"2025"},"n_packages":0,"n_references":5,"next":{"headline":"tracing: Limit access to parser-\u003ebuffer when trace_get_user failed","id":"CVE-2025-39683"},"packages":[],"prev":{"headline":"x86/cpu/hygon: Add missing resctrl_cpu_detect() in bsp_init helper","id":"CVE-2025-39681"},"products":["Linux"],"published":"2025-09-05","related":[{"cvss_score":10,"headline":"ProFTPD Improper Access Control","id":"CVE-2015-3306","kev_date_added":"2026-10-08","published":"2015-05-18"},{"cvss_score":9.9,"headline":"RoundCube Webmail Deserialization of Untrusted Data","id":"CVE-2025-49113","kev_date_added":"2026-02-20","published":"2025-06-02"},{"cvss_score":9.8,"headline":"GNU InetUtils Argument Injection","id":"CVE-2026-24061","kev_date_added":"2026-01-26","published":"2026-01-21"},{"cvss_score":9.8,"headline":"Mozilla Firefox Use-After-Free","id":"CVE-2024-9680","kev_date_added":"2024-10-15","published":"2024-10-09"},{"cvss_score":9.8,"headline":"RARLAB UnRAR Directory Traversal","id":"CVE-2022-30333","kev_date_added":"2022-08-09","published":"2022-05-09"},{"cvss_score":9.8,"headline":"Roundcube Webmail SQL Injection","id":"CVE-2021-44026","kev_date_added":"2023-06-22","published":"2021-11-19"}],"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":"yes","exploitation":"active","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-10-07","vendors":["Linux"]},"summary":"A flaw in Linux kernel TLS handling of zero-length records can cause a denial of service by breaking the receive message processing loop.","url":"https://insights.sbomify.com/CVE-2025-39682/"}