Description
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().
References (2)
Core 2
Core References
Mailing List, Patch
https://git.kernel.org/stable/c/4c74fbdc5ab95b13945be01e6065940b68222db7
Mailing List, Patch
https://git.kernel.org/stable/c/92cf7a51bdae24a32c592adcdd59a773ae149289
Scores
CVSS v3
5.5
EPSS
0.0017
EPSS Percentile
6.8%
Attack Vector
LOCAL
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
CISA SSVC
Vulnrichment
Exploitation
none
Automatable
no
Technical Impact
partial
Details
CWE
CWE-476
Status
published
Products (9)
linux/Kernel
6.12.0 - 6.12.10linux
Linux/Linux
< 6.12
Linux/Linux
27069e7cb3d1cea9377069266acf19b9cc5ad0ae - 4c74fbdc5ab95b13945be01e6065940b68222db7
Linux/Linux
27069e7cb3d1cea9377069266acf19b9cc5ad0ae - 92cf7a51bdae24a32c592adcdd59a773ae149289
Linux/Linux
6.12
Linux/Linux
6.12.10 - 6.12.*
Linux/Linux
6.13
linux/linux_kernel
6.13 rc1 (6 CPE variants)
linux/linux_kernel
6.12 - 6.12.10
Published
Jan 19, 2025
Tracked Since
Feb 18, 2026