nday
CVE-2025-39682

tls: fix handling of zero-length records on the rx_list

Linux / Kernel, Linux

CVE 공개 378일 후 KEV 등재. nday가 아직 패치 근거를 수집하지 않았습니다. 패치가 없다는 뜻은 아닙니다. PoC 출처 4곳 모두 미등재.

why these tags

nday derives these tags by fixed rules from the facts below; NVD, the CNA and other sources do not assign them. Vocabulary and rules: ~/tags.

remote, unauthenticated
AV:N, PR:N, UI:N in CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H (CVSS 3.1) from the CNA Linux
network
AV:N in CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H (CVSS 3.1) from the CNA Linux
no authentication required
PR:N in CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H (CVSS 3.1) from the CNA Linux
no user interaction
UI:N in CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H (CVSS 3.1) from the CNA Linux
Linux kernel
affected products in the CVE record: Linux · Kernel, Linux · LinuxCPE names NVD's analysts give as vulnerable: o:linux:linux_kernel
Siemens SIMATIC
CPE names NVD's analysts give as vulnerable: o:siemens:simatic_cn_4100_firmware
operating system
affected products in the CVE record: Linux · Kernel, Linux · LinuxCPE names NVD's analysts give as vulnerable: o:linux:linux_kernelthe product type of Linux kernel in nday's product registry
ICS / OT
CPE names NVD's analysts give as vulnerable: o:siemens:simatic_cn_4100_firmwarethe product type of Siemens SIMATIC in nday's product registry
현재 단계
KEV
공개
공개 → KEV 등재
T+378d KEV 시점은 날짜 단위
CVSS
9.8 CRITICAL v3.1
KEV 조치 기한
2026-09-21

생명주기

가로축 UTC. 점 = 분 단위, 넓은 막대 = 날짜만, 빈 표시 = 불명 또는 추정.
시점 알 수 없음
DIS공개
2025-09-05T17:20Z
PAT패치
아직 기록 없음
ANA분석
아직 기록 없음
POCPoC
아직 기록 없음
ITW악용
≤ 2026-09-18, KEV 기반 추정
KEVKEV
2026-09-18, 날짜만

요약

In the Linux kernel, the following vulnerability has been resolved:

tls: fix handling of zero-length records on the rx_list

Each recvmsg() call must process either - only contiguous DATA records (any number of them) - one non-DATA record

If the next record has different type than what has already been processed we break out of the main processing loop. If the record has already been decrypted (which may be the case for TLS 1.3 where we don't know type until decryption) we queue the pending record to the rx_list. Next recvmsg() will pick it up from there.

Queuing the skb to rx_list after zero-copy decrypt is not possible, since in that case we decrypted directly to the user space buffer, and we don't have an skb to queue (darg.skb points to the ciphertext skb for access to metadata like length).

Only data records are allowed zero-copy, and we break the processing loop after each non-data record. So we should never zero-copy and then find out that the record type has changed. The corner case we missed is when the initial record comes from rx_list, and it's zero length.

Original text of the CVE record (cvelist), shown as published.

Exploit conditions

What an attack needs, read from the CVSS vector.
Attack vector AV:N
Network: the attacker only needs to reach it over the network
Attack complexity AC:L
Low: no special conditions; the attacker can expect repeatable success
Privileges required PR:N
None: no account or authorization needed
User interaction UI:N
None: no action by anyone other than the attacker

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

CVSS 3.1 vector from the CVE record, scored by the CNA Linux.

이벤트 로그

+DISCVE 공개

CVE 레코드 공개(CNA: Linux). CVSS 9.8(치명적). CISA SSVC 평가상 악용 상태: active.

출처 cvelist · nday 일괄 수집 · 원본
{
  "id": 17647,
  "type": "disclosed",
  "source": "cvelist",
  "url": "https://www.cve.org/CVERecord?id=CVE-2025-39682",
  "occurred_at": "2025-09-05T17:20:48.657Z",
  "observed_at": "2026-11-12T15:01:53.938848Z",
  "is_backfill": true,
  "dedupe_key": "",
  "detail": {
    "kev": {
      "reference": "https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-39682",
      "date_added": "2026-09-18"
    },
    "cvss": {
      "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",
      "base_score": 9.8,
      "base_severity": "CRITICAL"
    },
    "ssvc": {
      "timestamp": "2026-09-19T03:56:25.358027Z",
      "automatable": "yes",
      "exploitation": "active",
      "technical_impact": "total"
    },
    "state": "PUBLISHED",
    "date_published": "2025-09-05T17:20:48.657Z",
    "assigner_short_name": "Linux"
  }
}
2026-09-18출처 제공, 날짜만
+KEVKEV 등재

CISA가 알려진 악용 취약점(KEV) 목록에 등재. 조치 기한: 2026-09-21, 침해 흔적 점검(forensic triage) 요구. 랜섬웨어 악용 여부: 알 수 없음.

출처 kev · nday 일괄 수집 · 원본
{
  "id": 66,
  "type": "kev_added",
  "source": "kev",
  "url": "https://www.cisa.gov/known-exploited-vulnerabilities-catalog",
  "occurred_at": "2026-09-18T00:00:00Z",
  "observed_at": "2026-11-12T13:53:00.018191Z",
  "is_backfill": true,
  "dedupe_key": "",
  "detail": {
    "cwes": [
      "CWE-754"
    ],
    "notes": "This vulnerability affects an open-source component, third-party library, protocol, or proprietary implementation that could be used by different products. For more information, please see: ; https://git.kernel.org/stable/c/2902c3ebcca52ca845c03182000e8d71d3a5196f; https://git.kernel.org/stable/c/c09dd3773b5950e9cfb6c9b9a5f6e36d06c62677; https://git.kernel.org/stable/c/3439c15ae91a517cf3c650ea15a8987699416ad9; https://git.kernel.org/stable/c/29c0ce3c8cdb6dc5d61139c937f34cb888a6f42e; https://git.kernel.org/stable/c/62708b9452f8eb77513115b17c4f8d1a22ebf843 ; BOD 26-04: https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk ; Forensics Triage Requirements: https://www.cisa.gov/news-events/directives/bod-26-04-implementation-guidance-prioritizing-security-updates-based-risk ; https://nvd.nist.gov/vuln/detail/CVE-2025-39682",
    "product": "Kernel",
    "due_date": "2026-09-21",
    "precision": "day",
    "date_added": "2026-09-18",
    "vendor_project": "Linux",
    "forensic_triage": "Yes",
    "required_action": "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.",
    "vulnerability_name": "Linux Kernel Improper Check for Unusual or Exceptional Conditions Vulnerability",
    "known_ransomware_campaign_use": "Unknown"
  }
}
≤ 2026-09-18추정, 직접 출처 없음
~ITW실제 공격 악용

악용 시작 시점을 밝힌 출처는 없습니다. KEV에 등재됐다는 것은 그 전에 이미 악용되고 있었다는 뜻이므로, 상한만 알 수 있습니다. CISA SSVC 평가상 악용 상태: active.

근거: kev 및 CISA SSVC 평가(cvelist)

Report an error

report an error or omission

Something on this page wrong or missing? Tell the editors; if they accept it, this page's revision log says so publicly. Upstream data is not changed.

연구자 논의

최근 7일간 연구자 0명이 언급

목록의 연구자가 X에서 이 CVE를 언급한 게시물입니다. 원문 그대로 보여 주며 nday는 검증하지 않습니다.

명단의 연구자가 X에서 이 CVE를 언급한 게시물은 아직 수집되지 않았습니다.

Discussion

0 comments

No comments yet.