CVE-2025-21638: sctp: sysctl: auth_enable: avoid using current->nsproxy
First published: Sun Jan 19 2025(Updated: )
In the Linux kernel, the following vulnerability has been resolved: sctp: sysctl: auth_enable: 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, but that would increase the size of this fix, while 'sctp.ctl_sock' still needs to be retrieved from 'net' structure.
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Linux Kernel | ||
| Linux Kernel | >=3.10.41<3.11 | |
| Linux Kernel | >=3.12.20<3.13 | |
| Linux Kernel | >=3.14.5<5.4.290 | |
| Linux Kernel | >=5.5<5.10.234 | |
| Linux Kernel | >=5.11<5.15.177 | |
| Linux Kernel | >=5.16<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/10c869a52f266e40f548cc3c565d14930a5edafc
- https://git.kernel.org/stable/c/dc583e7e5f8515ca489c0df28e4362a70eade382
- https://git.kernel.org/stable/c/bd2a2939423566c654545fa3e96a656662a0af9e
- https://git.kernel.org/stable/c/1b67030d39f2b00f94ac1f0af11ba6657589e4d3
- https://git.kernel.org/stable/c/7ec30c54f339c640aa7e49d7e9f7bbed6bd42bf6
- https://git.kernel.org/stable/c/c184bc621e3cef03ac9ba81a50dda2dae6a21d36
- https://git.kernel.org/stable/c/15649fd5415eda664ef35780c2013adeb5d9c695
Frequently Asked Questions
What is the severity of CVE-2025-21638?
CVE-2025-21638 is considered a medium severity vulnerability in the Linux kernel.
How do I fix CVE-2025-21638?
To fix CVE-2025-21638, ensure your Linux kernel is updated to the latest patched version provided by your distribution.
What are the potential impacts of CVE-2025-21638?
CVE-2025-21638 may lead to inconsistencies in network processing due to improper use of the current context in the SCTP protocol.
Which versions of the Linux kernel are affected by CVE-2025-21638?
CVE-2025-21638 affects multiple versions of the Linux kernel prior to the fix being applied.
Is CVE-2025-21638 related to network security?
Yes, CVE-2025-21638 is related to network security as it involves the SCTP protocol management within the Linux kernel.
- agent/type
- agent/first-publish-date
- 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/severity
- agent/remedy
- agent/weakness
- agent/last-modified-date
- agent/softwarecombine
- agent/event
- agent/tags
- collector/nvd-api
- source/NVD
- vendor/linux
- canonical/linux kernel
- version/linux kernel/3.10.41
- version/linux kernel/3.12.20
- version/linux kernel/3.14.5
- version/linux kernel/5.5
- version/linux kernel/5.11
- version/linux kernel/5.16
- 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