7.5

CVE-2025-38524: linux Race Condition

CVSS: 7.5v3.1HighModified
AliasesUBUNTU-CVE-2025-38524DEBIAN-CVE-2025-38524
Published 16-08-2025Last modified 15-10-2026

Vulnerability summary

CVE-2025-38524 is a high (CVSS 7.5) Race Condition vulnerability in linux. EPSS estimates a 0.27% chance of exploitation in the next 30 days, higher than 18.7% of scored vulnerabilities.

Overall risk
30/100
0100
Medium · default modelHow is this calculated?
CVSS score
7.5/10
010
High · v3.1 (CVE.org)
EPSS score
0.27%
0%100%
Low · +0.01 pp in 30 days
KEVNot listedIn no KEV catalog
RansomwareNone recordedNo known use recorded
Public exploits0No public exploits recorded

Advisory lineage

Upstream 0 · Downstream 38 · Related 38

Timeline

  1. 16-08-2025
    PublishedVulnerability first disclosed.
  2. 15-10-2026
    Last modifiedVulnerability information updated.

Description

In the Linux kernel, the following vulnerability has been resolved: rxrpc: Fix recv-recv race of completed call If a call receives an event (such as incoming data), the call gets placed on the socket's queue and a thread in recvmsg can be awakened to go and process it. Once the thread has picked up the call off of the queue, further events will cause it to be requeued, and once the socket lock is dropped (recvmsg uses call->user_mutex to allow the socket to be used in parallel), a second thread can come in and its recvmsg can pop the call off the socket queue again. In such a case, the first thread will be receiving stuff from the call and the second thread will be blocked on call->user_mutex. The first thread can, at this point, process both the event that it picked call for and the event that the second thread picked the call for and may see the call terminate - in which case the call will be "released", decoupling the call from the user call ID assigned to it (RXRPC_USER_CALL_ID in the control message). The first thread will return okay, but then the second thread will wake up holding the user_mutex and, if it sees that the call has been released by the first thread, it will BUG thusly: kernel BUG at net/rxrpc/recvmsg.c:474! Fix this by just dequeuing the call and ignoring it if it is seen to be already released. We can't tell userspace about it anyway as the user call ID has become stale.

CVSS metrics

5 scores · 4 sources · 2 versions

EPSS trend

Probability

0.27%

Chance of exploitation in the next 30 days

Percentile

19%

Versus all other CVEs

30-day change

+0.01 pp

From 0.26% on 21-09-2026

21-09-202621-10-2026
EPSS score
0.27%

Known exploited

Compare KEV catalogs

Not in any of the 3 tracked catalogs.

Public exploits

0 found

No public exploits indexed.

Weaknesses

CWE · root cause

Affected systems

Ubuntu147 products
  • linuxAll versions (No fix recorded) | < 6.8.0-100.100
  • linux-allwinner-5.19All versions (No fix recorded)
  • linux-awsAll versions (No fix recorded) | < 6.8.0-1046.49
  • linux-aws-5.0All versions (No fix recorded)
  • linux-aws-5.11All versions (No fix recorded)
Linux2 products
  • linux≥ 248f219cb8bcbfbd7f132752d44afa2df7c241d1, < 4aed0eeca58e26d752bb08b293b8dc75c6820b23 | ≥ 248f219cb8bcbfbd7f132752d44afa2df7c241d1, < 7692bde890061797f3dece0148d7859e85c55778 | ≥ 248f219cb8bcbfbd7f132752d44afa2df7c241d1, < 839fe96c15209dc2255c064bb44b636efe04f032 | ≥ 248f219cb8bcbfbd7f132752d44afa2df7c241d1, < 6c75a97a32a5fa2060c3dd30207e63b6914b606d | ≥ 248f219cb8bcbfbd7f132752d44afa2df7c241d1, < 962fb1f651c2cf2083e0c3ef53ba69e3b96d3fbc | 4.9
  • linux_kernel≥ 4.9, < 6.6.100 | ≥ 6.7, < 6.12.40 | ≥ 6.13, < 6.15.8 | 6.16:rc1 | 6.16:rc2 | 6.16:rc3 | 6.16:rc4 | 6.16:rc5 | 6.16:rc6
Debian1 product
  • linuxAll versions (No fix recorded) | < 6.12.41-1 | < 6.16.3-1

3 vendors · 150 products

References

32 links
Show all 32 references