CVE-2025-38112
BaseFortify
Publication date: 2025-07-03
Last updated on: 2025-12-17
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | From 4.17 (inc) to 5.10.239 (exc) |
| linux | linux_kernel | From 5.11 (inc) to 5.15.186 (exc) |
| linux | linux_kernel | From 5.16 (inc) to 6.1.142 (exc) |
| linux | linux_kernel | From 6.2 (inc) to 6.6.94 (exc) |
| linux | linux_kernel | From 6.7 (inc) to 6.12.34 (exc) |
| linux | linux_kernel | From 6.13 (inc) to 6.15.3 (exc) |
| linux | linux_kernel | 6.16 |
| debian | debian_linux | 11.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-367 | The product checks the state of a resource before using that resource, but the resource's state can change between the check and the use in a way that invalidates the results of the check. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a Time-Of-Check to Time-Of-Use (TOCTOU) race condition in the Linux kernel's sk_is_readable() function. The function pointer sk_prot->sock_is_readable can become NULL after an initial check due to changes in the socket's state when it is removed from a sockmap. This race condition can lead to a null pointer dereference, causing potential kernel instability or crashes.
How can this vulnerability impact me? :
The vulnerability can cause a null pointer dereference in the Linux kernel, which may lead to kernel crashes or instability. This can result in denial of service or system disruption on affected systems.