Is itCheck something

No. CVE-2025-39682

A Linux Kernel bug is being used in attacks

Being used now

Yes. Attackers are using this right now.

What to do

Apply the vendor's update. If there is none, stop using it or cut it off from the internet.

Confirmed in attacks
Sep 18, 2026
Product
Linux Kernel
Attack likelihood, next 30 days
3.3%

Attack likelihood is EPSS, a daily estimate from FIRST.org of how likely this bug is to be used in attacks in the next 30 days.

The official description

Linux Kernel contains an improper check for unusual or exceptional conditions vulnerability in the TLS receive path which allows a zero-length record retrieved from the rx_list to bypass the intended recvmsg() record-type handling, potentially causing subsequent TLS records to be processed using incorrect zero-copy and queuing assumptions. The impacted product(s) could be end-of-life (EoL) and/or end-of-service (EoS). Users are advised to discontinue use and/or transition to a supported version.

For your tech helper

A read-only checklist for whoever helps you with your computer, or an AI assistant. Paste it into Claude, ChatGPT or a coding agent; it only looks and changes nothing.

Read-only check, change nothing, send nothing anywhere.
Is Linux Kernel (CVE-2025-39682) installed or running on this machine or in this project?
1. Find every copy and its version (apps, packages, containers, lockfiles).
2. Compare each version against the vendor's fixed version for CVE-2025-39682. Quote the vendor page you used.
3. Report a table: where, version, fixed version, status (exposed / fixed / not installed / unsure).
4. List the exact update steps, but do not run them.

Sources