CVE-2025-39946

tls: make sure to abort the stream if headers are bogus

State
Published
Severity
9.8 Critical
Published
Oct 4, 2025
Updated
Aug 5, 2026
Reserved
Apr 16, 2025

Read the record on cve.org

Description

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

tls: make sure to abort the stream if headers are bogus

Normally we wait for the socket to buffer up the whole record before we service it. If the socket has a tiny buffer, however, we read out the data sooner, to prevent connection stalls. Make sure that we abort the connection when we find out late that the record is actually invalid. Retrying the parsing is fine in itself but since we copy some more data each time before we parse we can overflow the allocated skb space.

Constructing a scenario in which we're under pressure without enough data in the socket to parse the length upfront is quite hard. syzbot figured out a way to do this by serving us the header in small OOB sends, and then filling in the recvbuf with a large normal send.

Make sure that tls_rx_msg_size() aborts strp, if we reach an invalid record there's really no way to recover.

Scores

CVSSScoreVectorSource
3.19.8 CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HLinux

Weaknesses

The record names no weakness.

Affected Products

ProductVersions
LinuxLinux
  • 84c61fe1a75b4255df1e1e7c054c9e6d048da417 to before b36462146d86b1f22e594fe4dae611dffacfb203Affected
  • 84c61fe1a75b4255df1e1e7c054c9e6d048da417 to before 4cefe5be73886f383639fe0850bb72d5b568a7b9Affected
  • 84c61fe1a75b4255df1e1e7c054c9e6d048da417 to before 208640e6225cc929a05adbf79d1df558add3e231Affected
  • 84c61fe1a75b4255df1e1e7c054c9e6d048da417 to before 61ca2da5fb8f433ce8bbd1657c84a86272133e6bAffected
  • 84c61fe1a75b4255df1e1e7c054c9e6d048da417 to before 0aeb54ac4cd5cf8f60131b4d9ec0b6dc9c27b20dAffected
LinuxLinux
  • 6.0Affected
  • before 6.0Not affected
  • 6.1.154 through 6.1.*Not affected
  • 6.6.108 through 6.6.*Not affected
  • 6.12.49 through 6.12.*Not affected
  • 6.16.9 through 6.16.*Not affected
  • 6.17 and laterNot affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.