Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2025-21640: sctp: sysctl: cookie_hmac_alg: avoid using current->nsproxy

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.23% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 03ca51faba2b017bf6c90e139434c4117d0afcdc, 3cd0659deb9c03535fd61839e91d4d4d3e51ac71, 5599b212d2f4466e1832a94e9932684aaa364587; azl3 kernel 6.6.64.2-9 on Azure Linux 3.0 6.6.78.1-3; azl3 kernel 6.6.78.1-3 on Azure Linux 3.0 6.6.78.1-3.

Low priority for now. Upgrade to Linux Linux 03ca51faba2b017bf6c90e139434c4117d0afcdc, 3cd0659deb9c03535fd61839e91d4d4d3e51ac71, 5599b212d2f4466e1832a94e9932684aaa364587; azl3 kernel 6.6.64.2-9 on Azure Linux 3.0 6.6.78.1-3; azl3 kernel 6.6.78.1-3 on Azure Linux 3.0 6.6.78.1-3 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

In the Linux kernel, the following vulnerability has been resolved: sctp: sysctl: cookie_hmac_alg: 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.sctp_hmac_alg' is used.

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Jan 19, 2025
Updated
Oct 15, 2026
EPSS
0.2% · 14th percentile

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
5.5
CNA · Linux
7.1
1.6 point gap

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2025-21640

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel3.8 and later · before 6.1.125
  • linux linux kernel6.2 and later · before 6.6.72
  • linux linux kernel6.7 and later · before 6.12.10
  • linux linux kernel6.13

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 3.8affected
    • 3c68198e75111a905ac2412be12bf7b29099729b and later · before 5599b212d2f4466e1832a94e9932684aaa364587affected · git
    • 3c68198e75111a905ac2412be12bf7b29099729b and later · before 03ca51faba2b017bf6c90e139434c4117d0afcdcaffected · git
    • 3c68198e75111a905ac2412be12bf7b29099729b and later · before 86ddf8118123cb58a0fb8724cad6979c4069065baffected · git
    • 3c68198e75111a905ac2412be12bf7b29099729b and later · before 3cd0659deb9c03535fd61839e91d4d4d3e51ac71affected · git
    • 3c68198e75111a905ac2412be12bf7b29099729b and later · before ad673e514b2793b8d5902f6ba6ab7e890dea23d5affected · git
    • 3c68198e75111a905ac2412be12bf7b29099729b and later · before f0bb3935470684306e4e04793a20ac4c4b08de0baffected · git
    • 3c68198e75111a905ac2412be12bf7b29099729b and later · before ea62dd1383913b5999f3d16ae99d411f41b528d4affected · git
    • before 3.8not affected · semver
    • 5.4.292 and later · up to and including 5.4.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.128-16.1.128-1
Debian:13linuxbefore 6.12.10-16.12.10-1

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2025-21635Jan 19, 2025 · rds: sysctl: rds_tcp_{rcv,snd}buf: avoid using current->nsproxy
    22Monitor
  • ← EarlierCVE-2025-21638Jan 19, 2025 · sctp: sysctl: auth_enable: avoid using current->nsproxy
    22Monitor
  • Later →CVE-2025-21645Jan 19, 2025 · platform/x86/amd/pmc: Only disable IRQ1 wakeup where i8042 actually enabled it
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux03ca51faba2b017bf6c90e139434c4117d0afcdcVendor (CNA)
Linux Linux3cd0659deb9c03535fd61839e91d4d4d3e51ac71Vendor (CNA)
Linux Linux5599b212d2f4466e1832a94e9932684aaa364587Vendor (CNA)
Linux Linux86ddf8118123cb58a0fb8724cad6979c4069065bVendor (CNA)
Linux Linuxad673e514b2793b8d5902f6ba6ab7e890dea23d5Vendor (CNA)
Linux Linuxea62dd1383913b5999f3d16ae99d411f41b528d4Vendor (CNA)
Linux Linuxf0bb3935470684306e4e04793a20ac4c4b08de0bVendor (CNA)
azl3 kernel 6.6.64.2-9 on Azure Linux 3.06.6.78.1-3 · CBL-Mariner ReleasesMicrosoft (MSRC)
azl3 kernel 6.6.78.1-3 on Azure Linux 3.06.6.78.1-3 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 kernel 5.15.179.1-1 on CBL Mariner 2.05.15.179.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 kernel 5.15.182.1-1 on CBL Mariner 2.0CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 kernel 5.15.182.1-1 on CBL-Mariner 2.05.15.179.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
debian:linux6.1.128-1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. SSVC exploitation— → none
  2. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records