Sign inStart freeBook a demo

What is CVE-2025-39682?A critical-severity flaw criminals are using now.

Critical severityKnown exploited3 affected products
The short answer

CVE-2025-39682 is a critical-severity flaw (CVSS 9.8) in Linux kernel, published on 5 September 2025. It is on the list of flaws known to be exploited, so criminals are already using it. The latest forecast puts its chance of use in the next 30 days at 2.9%. If you run an affected version, patch it first.

Check if it affects you →How to fix it

Published 5 September 2025. Record last updated 7 October 2026. We keep this page's data up to date.

What it does

What is CVE-2025-39682? In plain terms.

It can be attacked from anywhere on the internet without logging in, and nobody has to click anything. If it works, the attacker can read data, change data and take it offline.

The official description

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.

What kind of flaw is it?

  • CWE-754Improper Check for Unusual or Exceptional Conditions
CVSS 3.1 scoreCritical · 9.8

How an attack on it works

Read straight from its severity rating, translated out of the shorthand.

  • Where an attacker can beAnywhere on the internet
  • How hard it is to pull offEasy: no special conditions
  • Login needed firstNo login needed
  • Does someone have to clickNo, nobody has to do anything
  • What an attacker getsCan read data, change data and take it offline

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

Exploitation

Is CVE-2025-39682 being exploited? Yes.

Attackers are already using it. It is on the government list of flaws known to be exploited, and the latest forecast puts the chance of it being used in the next 30 days at 2.9%.

Known to be exploitedYesOn the government list of exploited flaws
Chance of use in the next 30 days2.9%Its EPSS score, from the latest forecast

Timeline

  1. Published
  2. Added to the known-exploited list
  3. Record last updated
How Precursor Intelligence ranks it
89out of 100Critical

CVE-2025-39682 scores 89. Action: Emergency patch.

We keep the score of every published flaw up to date as the evidence changes. Four things go into the score, and evidence that criminals are actually using it counts most. In order:

  • Evidence it is being exploitedBiggest factor
  • How severe it isStrong factor
  • How widely exposed it isSmaller factor
  • Threat activity around itSmaller factor

85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score.

When CVE-2025-39682 matches software you track, it lands in your list with its score and the reasons behind it.

See your own ranked list →
Affected products

Who is affected by CVE-2025-39682? 3 products.

The published record lists 3 products from 3 vendors. Versions are shown as published: "6.0 to before 6.1.149" means from 6.0 up to, but not including, 6.1.149. If you run one of these, check your version, then go to the fix below.

Remediation

How do I fix CVE-2025-39682? Four steps.

  1. Check whether you run itCompare your versions with the affected products above. Not sure what you run? Precursor Intelligence can work it out from your public website, or you can pick it from a list.
  2. Apply the vendor’s fixInstall the update named in the vendor’s advisory. We’ve put the advisories and patch notes first in the list.
  3. If you can’t patch todayFollow any mitigation the vendor publishes, and limit who can reach the affected system from the internet until the update is in.
  4. Check it wasn’t used before you patchedBecause criminals are already using this flaw, look for signs of a break-in on affected systems using the vendor’s guidance.

References

8 links
Precursor Intelligence

Does CVE-2025-39682 affect you? We'll keep checking.

Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.

  1. Tell us what you runPick your software from a list, or let us work it out from your website.
  2. We match it to every flawOver 400,000 published flaws, checked against your list.
  3. Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
  4. Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Start free →Book a demo

Free plan, no card needed. Nothing to install.

FAQ

Common questions, answered plainly.

Something else? Talk to the team →

CVE-2025-39682 is a critical-severity flaw in Linux kernel, published on 5 September 2025. It can be attacked from anywhere on the internet without logging in, and nobody has to click anything. If it works, the attacker can read data, change data and take it offline.

It scores 9.8 out of 10 on the CVSS severity scale, which is critical. Our risk score for CVE-2025-39682 is 89 out of 100, which is Critical. Its action is "Emergency patch". Attackers are using this flaw today. If you run an affected version, it goes to the top of your list.

Attackers are already using it. It is on the government list of flaws known to be exploited, and the latest forecast puts the chance of it being used in the next 30 days at 2.9%.

For Linux kernel: 6.0 to before 6.1.149, 6.2 to before 6.6.103, 6.7 to before 6.12.44, 6.13 to before 6.16.4, 6.17-rc1, 6.17-rc2. The record lists 3 products in all, each with its versions, under "Who is affected" on this page.

Install the update the vendor names in its advisory, linked first under "How do I fix" on this page. If you can't patch today, follow the vendor's mitigation and limit who can reach the affected system from the internet. Because criminals are already using it, also check affected systems for signs of a break-in.

Keep exploring