DEBIAN-CVE-2025-21639
In the Linux kernel, the following vulnerability has been resolved: sctp: sysctl: rto_min/max: avoid using current->nsproxy As mentioned in a previous commit of this series, 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 'net' structure can be obtained from the table->data using container_of(). Note that table->data could also be used directly, as this is the only member needed from the 'net' structure, but that would increase the size of this fix, to use '*data' everywhere 'net->sctp.rto_min/max' is used.
Risk Scores
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Debian:13 | linux | 0, 0 |
| Debian:14 | linux | 0, 0 |
| Debian:11 | linux-6.1 | 6.1.112-1, 6.1.106-3, 6.1.106-3 |
| Debian:11 | linux | 5.10.223-1, *, 5.10.106-1 |
| Debian:12 | linux | 6.1.55-1, 6.1.66-1, 6.1.69-1 |
Timeline
- Jan 19, 2025 CVE Published
- Apr 28, 2026 CVE Updated