CVE-2025-21637: sctp: sysctl: udp_port: avoid using current->nsproxy

Published Jan 19, 2025
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

sctp: sysctl: udpport: 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 containerof().

Note that table->data could also be used directly, but that would increase the size of this fix, while 'sctp.ctlsock' still needs to be retrieved from 'net' structure.

Other sources

This CVE was automatically created from a reference found in an email or other text. If you are reading this, then this CVE entry is probably erroneous, since this text should be replaced by the official CVE description automatically.

Launchpad

Affected Software

17 affected componentsFixes available
Linux Linux kernel
Linux Linux kernel>=5.11<5.15.177
Linux Linux kernel>=5.16<6.1.125
Linux Linux kernel>=6.2<6.6.72
Linux Linux kernel>=6.7<6.12.10
Linux Linux kernel=6.13-rc1
Linux Linux kernel=6.13-rc2
Linux Linux kernel=6.13-rc3
Linux Linux kernel=6.13-rc4
Linux Linux kernel=6.13-rc5
Linux Linux kernel=6.13-rc6
debian/linux
5.10.223-15.10.234-16.1.129-16.1.135-16.12.27-1
debian/linux-6.1
6.1.129-1~deb11u1
Microsoft cbl2 kernel 5.15.180.1-1<5.15.180.1-1
5.15.180.1-1
Microsoft cbl2 kernel 5.15.176.3-3<5.15.180.1-1
5.15.180.1-1
Microsoft azl3 kernel 6.6.64.2-9<6.6.78.1-3
6.6.78.1-3
Microsoft azl3 kernel 6.6.78.1-3<6.6.78.1-3
6.6.78.1-3

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 5.10.223-1Fixed in 5.10.234-1Fixed in 6.1.129-1Fixed in 6.1.135-1Fixed in 6.12.27-1
  2. Upgrade

    Upgrade debian/linux-6.1 to a version that resolves this vulnerability.

    Fixed in 6.1.129-1~deb11u1
  3. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 5.15.180.1-1
  4. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 6.6.78.1-3

Event History

Jan 19, 2025
CVE Published
via MITRE·10:17 AM
Data Sourced
via MITRE·10:17 AM
DescriptionSeverity
Data Sourced
via NVD·11:15 AM
RemedyDescriptionSeverityWeaknessAffected Software
Mar 14, 2025
Data Sourced
via Microsoft·07:00 AM
DescriptionSeverityWeaknessAffected Software
Updated
via Microsoft·07:00 AM
SeverityAffected Software
Updated
via Microsoft·07:00 AM
Affected Software
Updated
via Microsoft·07:00 AM
DescriptionSeverity
Mar 27, 2025
Data Sourced
via Launchpad·06:49 PM
Description
May 6, 2025
Data Sourced
via Ubuntu·06:57 PM
RemedyDescriptionSeverityAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2025-21637?

CVE-2025-21637 is classified as a moderate severity vulnerability.

2

How do I fix CVE-2025-21637?

To fix CVE-2025-21637, upgrade to the patched version of the Linux kernel as specified in the latest updates.

3

What are the potential consequences of CVE-2025-21637?

Exploitation of CVE-2025-21637 may lead to unexpected behavior in the Linux kernel, potentially affecting system stability.

4

Which versions of the Linux kernel are affected by CVE-2025-21637?

CVE-2025-21637 affects various versions of the Linux kernel prior to the fix being applied.

5

Is CVE-2025-21637 specific to certain Linux distributions?

CVE-2025-21637 can potentially affect all distributions using the vulnerable versions of the Linux kernel.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203