CVE-2025-40355
BaseFortify
Publication date: 2025-12-16
Last updated on: 2025-12-18
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | 6.17.1 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-UNKNOWN |
Attack-Flow Graph
AI Powered Q&A
How can this vulnerability be detected on my network or system? Can you suggest some commands?
You can detect this vulnerability by monitoring your system logs for the specific warning message generated by the vulnerability: "WARNING: CPU: ... __dev_change_net_namespace". Checking the kernel logs (e.g., using 'dmesg' or 'journalctl -k') for this warning can help identify if the issue is occurring. For example, run 'dmesg | grep __dev_change_net_namespace' or 'journalctl -k | grep __dev_change_net_namespace' to find relevant warnings.
What immediate steps should I take to mitigate this vulnerability?
The immediate mitigation step is to update the Linux kernel to a version that includes the fix for this vulnerability, which involves checking visibility before changing group attribute ownership in sysfs. Until the update is applied, monitoring for the warning messages and avoiding operations that trigger __dev_change_net_namespace may reduce exposure.
Can you explain this vulnerability to me?
This vulnerability in the Linux kernel involves the sysfs interface where the function __dev_change_net_namespace() can trigger a warning (WARN_ON()) when it attempts to change the ownership of a file that is not visible. This happens because the code does not check the visibility of the sysfs attribute before changing its group ownership. The issue was fixed by adding a check using is_visible() before modifying the attribute ownership.
How can this vulnerability impact me? :
This vulnerability can cause the Linux kernel to hit warnings (WARN_ON()) during operations that change network namespace ownership of sysfs files. This could potentially lead to instability or unexpected behavior in the kernel, affecting system reliability or causing crashes when certain sysfs attributes are manipulated.