CVE-2025-21641
published 2025-01-19CVE-2025-21641: In the Linux kernel, the following vulnerability has been resolved: mptcp: sysctl: blackhole timeout: avoid using current->nsproxy As mentioned in the previous…
PriorityP419medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.17%
6.8th percentile
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
8 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 6.12.10-1 (forky) | linux 6.12.10-1 (forky) |
| linux | linux | — | — |
| linux | linux | >= 27069e7cb3d1cea9377069266acf19b9cc5ad0ae < 4c74fbdc5ab95b13945be01e6065940b68222db7 | 4c74fbdc5ab95b13945be01e6065940b68222db7 |
| linux | linux | >= 27069e7cb3d1cea9377069266acf19b9cc5ad0ae < 92cf7a51bdae24a32c592adcdd59a773ae149289 | 92cf7a51bdae24a32c592adcdd59a773ae149289 |
| linux | linux_kernel | — | — |
| linux | linux_kernel | >= 0 < 6.12.10-1 | 6.12.10-1 |
| linux | linux_kernel | >= 0 < 6.12.10-1 | 6.12.10-1 |
| linux | linux_kernel | >= 6.12 < 6.12.10 | 6.12.10 |
CVSS provenance
nvdv3.15.5MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
osv5.5MEDIUM
vendor_debian5.5LOW
vendor_redhat5.5MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
GHSA-74ff-8pv9-crm9: In the Linux kernel, the following vulnerability has been resolved:
mptcp: sysctl: blackhole timeout: avoid using current->nsproxy
As mentioned in t
ghsa_unreviewed·2025-01-19
CVE-2025-21641 [MEDIUM] CWE-476 GHSA-74ff-8pv9-crm9: In the Linux kernel, the following vulnerability has been resolved:
mptcp: sysctl: blackhole timeout: avoid using current->nsproxy
As mentioned in t
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().
OSV
CVE-2025-21641: In the Linux kernel, the following vulnerability has been resolved: mptcp: sysctl: blackhole timeout: avoid using current->nsproxy As mentioned in the
osv·2025-01-19·CVSS 5.5
CVE-2025-21641 [MEDIUM] CVE-2025-21641: In the Linux kernel, the following vulnerability has been resolved: mptcp: sysctl: blackhole timeout: avoid using current->nsproxy As mentioned in the
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().
Red Hat
kernel: mptcp: sysctl: blackhole timeout: avoid using current->nsproxy
vendor_redhat·2025-01-19·CVSS 5.5
CVE-2025-21641 [MEDIUM] CWE-476 kernel: mptcp: sysctl: blackhole timeout: avoid using current->nsproxy
kernel: mptcp: sysctl: blackhole timeout: avoid using current->nsproxy
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().
Package: kernel (Red Hat Enterprise Linux 10) - Fix deferred
Package: kernel (Red Hat Enterprise Linux 6) - Not affected
Package: k
Debian
CVE-2025-21641: linux - In the Linux kernel, the following vulnerability has been resolved: mptcp: sysc...
vendor_debian·2025·CVSS 5.5
CVE-2025-21641 [MEDIUM] CVE-2025-21641: linux - In the Linux kernel, the following vulnerability has been resolved: mptcp: sysc...
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().
Scope: local
bookworm: resolved
bullseye: resolved
forky: resolved (fixed in 6.12.10-1)
sid: resolved (fixed in 6.12.10-1)
trixie: resolved (fixed in 6.12.10-1)
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
2025-01-19
Published