CVE-2025-21639: sctp: sysctl: rto_min/max: avoid using current->nsproxy
First published: Sun Jan 19 2025(Updated: )
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.
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Linux Kernel | ||
| Linux Kernel | >=3.13<6.1.125 | |
| Linux Kernel | >=6.2<6.6.72 | |
| Linux Kernel | >=6.7<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 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://git.kernel.org/stable/c/c8d179f3b1c1d60bf4484f50aa67b4c70f91bff9
- https://git.kernel.org/stable/c/246428bfb9e7db15c5cd08e1d0eca41b65af2b06
- https://git.kernel.org/stable/c/0f78f09466744589e420935e646ae78212a38290
- https://git.kernel.org/stable/c/4059507e34aa5fe0fa9fd5b2b5f0c8b26ab2d482
- https://git.kernel.org/stable/c/dc9d0e3cfd16f66fbf0862857c6b391c8613ca9f
- https://git.kernel.org/stable/c/c87f1f6ade56c711f8736901e330685b453e420e
- https://git.kernel.org/stable/c/9fc17b76fc70763780aa78b38fcf4742384044a5
Frequently Asked Questions
What is the severity of CVE-2025-21639?
The severity of CVE-2025-21639 is currently classified as moderate.
What does CVE-2025-21639 affect?
CVE-2025-21639 affects the Linux Kernel, specifically the sctp component.
How do I fix CVE-2025-21639?
To fix CVE-2025-21639, update your Linux Kernel to the latest version where the vulnerability is patched.
Is CVE-2025-21639 exploitable remotely?
CVE-2025-21639 is not considered remotely exploitable.
What version of the Linux Kernel contains the fix for CVE-2025-21639?
The fix for CVE-2025-21639 is included in stable releases following the commit addressing the vulnerability.
- agent/first-publish-date
- agent/type
- agent/title
- agent/author
- agent/description
- agent/source
- collector/epss-latest
- source/FIRST
- agent/epss
- collector/mitre-cve
- source/MITRE
- agent/references
- agent/guess-ai
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- agent/remedy
- agent/weakness
- agent/severity
- agent/softwarecombine
- agent/last-modified-date
- agent/event
- agent/tags
- collector/nvd-api
- source/NVD
- vendor/linux
- canonical/linux kernel
- version/linux kernel/3.13
- version/linux kernel/6.2
- version/linux kernel/6.7
- version/linux kernel/6.13-rc1
- version/linux kernel/6.13-rc2
- version/linux kernel/6.13-rc3
- version/linux kernel/6.13-rc4
- version/linux kernel/6.13-rc5
- version/linux kernel/6.13-rc6