Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

Description

In the Linux kernel, the following vulnerability has been resolved: sctp: sysctl: udp_port: 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.

Timeline

  1. ID reserved

    By Linux

  2. · 21 days later

    Published

  3. · 19 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2025-21637, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.1CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
CISA-ADPADP (enrichment)3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.21% · top 88% of all CVEs (16 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.1.

Affected products

  • Linux · Linux

    • affected 046c052b475e7119b6a30e3483e2888fc606a2f8 – < 0a0966312ac3eedd7f5f2a766ed4702df39a9a65
    • affected 046c052b475e7119b6a30e3483e2888fc606a2f8 – < e919197fb8616331f5dc81e4c3cc3d12769cb725
    • affected 046c052b475e7119b6a30e3483e2888fc606a2f8 – < 55627918febdf9d71107a1e68d1528dc591c9a15
    • affected 046c052b475e7119b6a30e3483e2888fc606a2f8 – < 5b77d73f3be5102720fb685b9e6900e3500e1096
    • affected 046c052b475e7119b6a30e3483e2888fc606a2f8 – < c10377bbc1972d858eaf0ab366a311b39f8ef1b6
  • Linux · Linux

    • affected 5.11
    • unaffected < 5.11
    • unaffected 5.15.177 – ≤ 5.15.*
    • unaffected 6.1.125 – ≤ 6.1.*
    • unaffected 6.6.72 – ≤ 6.6.*
    • unaffected 6.12.10 – ≤ 6.12.*
    • unaffected 6.13 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-21637 badge
[![CVE-2025-21637](https://cveledger.app/badge/CVE-2025-21637.svg)](https://cveledger.app/cve/CVE-2025-21637)

Record last updated .