CVE-2025-38500
BaseFortify
Publication date: 2025-08-12
Last updated on: 2025-11-03
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | 6.1.153-1 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-416 | The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a use-after-free bug in the Linux kernel's xfrm interface related to the collect_md property. The collect_md property can only be set when the interface is created, but the function xfrmi_changelink() did not properly enforce this restriction. As a result, the system could erroneously place a special interface in internal kernel data structures twice, leading to a double free when the network namespace is torn down. This causes a kernel crash (oops) due to invalid memory operations.
How can this vulnerability impact me? :
This vulnerability can cause the Linux kernel to crash due to a double free error when network namespaces are cleaned up. This can lead to system instability, denial of service, or potential exploitation if an attacker can trigger the bug, affecting the availability and reliability of the system.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability manifests as a kernel BUG and oops related to xfrm interfaces when the collect_md property is improperly changed. Detection can be done by monitoring kernel logs for messages similar to the provided oops output, such as 'kernel BUG at net/core/dev.c:12029!' or 'Oops: invalid opcode'. You can check kernel logs using commands like 'dmesg | grep -i "kernel BUG"' or 'journalctl -k | grep -i oops'. There are no specific commands to detect the vulnerability directly, but monitoring for these kernel errors related to xfrm interfaces is recommended.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation involves updating the Linux kernel to a version where this vulnerability is fixed, as the issue is resolved by changing the check to use the xi from netdev_priv earlier in the function to prevent changes in xfrm collect_md interfaces. Until the update is applied, avoid changing the collect_md property on existing xfrm interfaces, as it should only be set on device creation. Monitoring and preventing calls to changelink on such interfaces can reduce the risk of triggering the bug.