mptcp: sysctl: blackhole timeout: avoid using current->nsproxy
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 4c74fbdc5ab95b13945be01e6065940b68222db7 and Kernel 92cf7a51bdae24a32c592adcdd59a773ae149289.
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().
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.12, >=27069e7cb3d1cea9377069266acf19b9cc5ad0ae <4c74fbdc5ab95b13945be01e6065940b68222db7, >=27069e7cb3d1cea9377069266acf19b9cc5ad0ae <92cf7a51bdae24a32c592adcdd59a773ae149289 | 4c74fbdc5ab95b13945be01e6065940b68222db7, 92cf7a51bdae24a32c592adcdd59a773ae149289 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket