CVE-2025-39682（linux linux kernel）の深刻度・悪用状況・対象バージョン

9.8 緊急（CVSS 3.x）　悪用確認済み（CISA KEV）　EPSS 取得中…
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

概要

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.

実際の攻撃で悪用されています。 CISA KEV への追加日: 2026-09-18。対象製品を使っている場合は最優先で対策してください。
CISA の要求対応: 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.

影響を受ける製品

ベンダー製品対象バージョン
linuxlinux_kernel≥ 6.0 かつ < 6.1.149
linuxlinux_kernel≥ 6.2 かつ < 6.6.103
linuxlinux_kernel≥ 6.7 かつ < 6.12.44
linuxlinux_kernel≥ 6.13 かつ < 6.16.4
linuxlinux_kernel6.17
linuxlinux_kernel6.17
debiandebian_linux11.0
siemenssimatic_cn_4100_firmware< 5.0

基本情報

公開日
2025-09-05
最終更新
2026-10-19
NVD の状態
Analyzed
弱点の種類
CWE-754

対策の進め方

  1. 上の表で、使っている製品とバージョンが対象か確認します。
  2. ベンダーの公式アドバイザリ（下の参考情報の「Vendor Advisory」「Patch」）で修正版・回避策を確認します。
  3. 悪用が確認されているため、パッチ適用までの間もアクセス制限・侵害の痕跡確認を検討します。
  4. 日本語の情報は JVN iPedia で CVE-2025-39682 を検索 できます。

参考情報

データ出典: NIST NVD、CISA KEV、FIRST EPSS。翻訳は参考情報で、正確性は原文を優先してください。