First published: Sun Jan 19 2025(Updated: )
In the Linux kernel, the following vulnerability has been resolved: mptcp: sysctl: blackhole timeout: avoid using current->nsproxy As mentioned in the previous commit, using the 'net' structure via 'current' is not recommended for different reasons: - Inconsistency: getting info from the reader's/writer's netns vs only from the opener's netns. - current->nsproxy can be NULL in some cases, resulting in an 'Oops' (null-ptr-deref), e.g. when the current task is exiting, as spotted by syzbot [1] using acct(2). The 'pernet' structure can be obtained from the table->data using container_of().
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Software | Affected Version | How to fix |
---|---|---|
Red Hat Kernel-devel | ||
Linux Kernel | >=6.12<6.12.10 | |
Linux Kernel | =6.13-rc1 | |
Linux Kernel | =6.13-rc2 | |
Linux Kernel | =6.13-rc3 | |
Linux Kernel | =6.13-rc4 | |
Linux Kernel | =6.13-rc5 | |
Linux Kernel | =6.13-rc6 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of CVE-2025-21641 has not been explicitly rated, but as it affects the Linux kernel, it may impact system stability and security.
To fix CVE-2025-21641, you should update your Linux kernel to a patched version that addresses this vulnerability.
CVE-2025-21641 affects various versions of the Linux kernel used in multiple distributions.
There is currently no public information indicating that CVE-2025-21641 is being actively exploited.
The potential consequences of CVE-2025-21641 include system instability and improper handling of networking features in the Linux kernel.