CVE-2025-38018
BaseFortify
Publication date: 2025-06-18
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 6.0 (inc) to 6.1.140 (exc) |
| linux | linux_kernel | From 6.2 (inc) to 6.6.92 (exc) |
| linux | linux_kernel | From 6.7 (inc) to 6.12.30 (exc) |
| linux | linux_kernel | From 6.13 (inc) to 6.14.8 (exc) |
| linux | linux_kernel | 6.15 |
| linux | linux_kernel | 6.15 |
| linux | linux_kernel | 6.15 |
| linux | linux_kernel | 6.15 |
| linux | linux_kernel | 6.15 |
| linux | linux_kernel | 6.15 |
| debian | debian_linux | 11.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-476 | The product dereferences a pointer that it expects to be valid but is NULL. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability in the Linux kernel occurs when the function alloc_page fails, leading to a kernel panic due to a NULL pointer dereference. Specifically, the frag_list pointer is set to NULL improperly, which causes issues in subsequent calls to tls_strp_check_queue_ok and tls_strp_read_sock. The root cause is that full_len is not reset in tls_strp_flush_anchor_copy(), causing the receive path to continue handling a partial record even though the receive queue has been detached from the fragment list. This results in a kernel NULL pointer dereference and a system crash.
How can this vulnerability impact me? :
This vulnerability can cause a kernel panic, which leads to a system crash and potential denial of service. Systems running the affected Linux kernel may become unstable or unavailable when this flaw is triggered, impacting reliability and uptime.