Skip to content
Noroxi
CVE-2022-50243· NVD / CVE Program· CNA Linux

sctp: handle the error returned from sctp_auth_asoc_init_active_key

Noroxi assessment

Priority: Monitor (action score 31/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.16% (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 022152aaebe116a25c39818a07e175a8cd3c1e11, 0f90099d18e3abdc01babf686f41f63fe04939c1, 19d636b663e0e92951bba5fced929ca7fd25c552.

Low priority for now. Upgrade to Linux Linux 022152aaebe116a25c39818a07e175a8cd3c1e11, 0f90099d18e3abdc01babf686f41f63fe04939c1, 19d636b663e0e92951bba5fced929ca7fd25c552 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: handle the error returned from sctp_auth_asoc_init_active_key When it returns an error from sctp_auth_asoc_init_active_key(), the active_key is actually not updated. The old sh_key will be freeed while it's still used as active key in asoc. Then an use-after-free will be triggered when sending patckets, as found by syzbot: sctp_auth_shkey_hold+0x22/0xa0 net/sctp/auth.c:112 sctp_set_owner_w net/sctp/socket.c:132 [inline] sctp_sendmsg_to_asoc+0xbd5/0x1a20 net/sctp/socket.c:1863 sctp_sendmsg+0x1053/0x1d50 net/sctp/socket.c:2025 inet_sendmsg+0x99/0xe0 net/ipv4/af_inet.c:819 sock_sendmsg_nosec net/socket.c:714 [inline] sock_sendmsg+0xcf/0x120 net/socket.c:734 This patch is to fix it by not replacing the sh_key when it returns errors from sctp_auth_asoc_init_active_key() in sctp_auth_set_key(). For sctp_auth_set_active_key(), old active_key_id will be set back to asoc->active_key_id when the same thing happens.

HighCVSS 7.8 · v3.1—No exploit Fix available
Published
Sep 15, 2025
Updated
Aug 5, 2026
EPSS
0.1% · 5th percentile

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CNA vs NVD score

NVD
7.8
CNA · Linux
7.8
agree

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-2022-50243

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 kernel4.19.199 and later · before 4.19.262
  • linux linux kernel5.4.136 and later · before 5.4.220
  • linux linux kernel5.10.54 and later · before 5.10.150
  • linux linux kernel5.13.6 and later · before 5.14
  • linux linux kernel5.14.1 and later · before 5.15.75
  • linux linux kernel5.16 and later · before 5.19.17
  • linux linux kernel6.0 and later · before 6.0.3
  • linux linux kernel5.14

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

    • c1de376423a7759bf4fa25d6a038a4c1e035c9e1, 5.14affected
    • 50b57223da67653c61e405d0a7592355cfe4585e and later · before b8fa99a3a11bdd77fef6b4a97f1021eb30b5ba40affected · git
    • b60461696a0b0fdaf240bc365b7983698f88ded2 and later · before 382ff44716603a54f5fd238ddec6a2468e217612affected · git
    • 8eb225873246312660ccd68296959a7b213d0cdd and later · before f65955340e0044f5c41ac799a01698ac7dee8a4eaffected · git
    • 58acd10092268831e49de279446c314727101292 and later · before 19d636b663e0e92951bba5fced929ca7fd25c552affected · git
    • 58acd10092268831e49de279446c314727101292 and later · before 0f90099d18e3abdc01babf686f41f63fe04939c1affected · git
    • 58acd10092268831e49de279446c314727101292 and later · before 3b0fcf5e29c0940e1169ce9c44f73edd98bdf12daffected · git
    • 58acd10092268831e49de279446c314727101292 and later · before 022152aaebe116a25c39818a07e175a8cd3c1e11affected · git
    • 4.19.199 and later · before 4.19.262affected · semver
    • 5.4.136 and later · before 5.4.220affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.0.3-16.0.3-1
Red Hat:rhel_eus:8.6::baseosbpftoolbefore 0:4.18.0-372.80.1.el8_60:4.18.0-372.80.1.el8_6
Red Hat:rhel_eus:8.6::baseoskernelbefore 0:4.18.0-372.80.1.el8_60:4.18.0-372.80.1.el8_6
Red Hat:rhel_eus:8.6::baseoskernel-abi-stablelistsbefore 0:4.18.0-372.80.1.el8_60:4.18.0-372.80.1.el8_6
Red Hat:rhel_eus:8.6::baseoskernel-corebefore 0:4.18.0-372.80.1.el8_60:4.18.0-372.80.1.el8_6
Red Hat:rhel_eus:8.6::baseoskernel-debugbefore 0:4.18.0-372.80.1.el8_60:4.18.0-372.80.1.el8_6
Red Hat:rhel_eus:8.6::baseoskernel-debug-corebefore 0:4.18.0-372.80.1.el8_60:4.18.0-372.80.1.el8_6
Red Hat:rhel_eus:8.6::baseoskernel-debug-develbefore 0:4.18.0-372.80.1.el8_60:4.18.0-372.80.1.el8_6
Red Hat:rhel_eus:8.6::baseoskernel-debug-modulesbefore 0:4.18.0-372.80.1.el8_60:4.18.0-372.80.1.el8_6
Red Hat:rhel_eus:8.6::baseoskernel-debug-modules-extrabefore 0:4.18.0-372.80.1.el8_60:4.18.0-372.80.1.el8_6
Red Hat:rhel_eus:8.6::baseoskernel-debuginfo-common-aarch64before 0:4.18.0-372.80.1.el8_60:4.18.0-372.80.1.el8_6
Red Hat:rhel_eus:8.6::baseoskernel-debuginfo-common-ppc64lebefore 0:4.18.0-372.80.1.el8_60:4.18.0-372.80.1.el8_6
Red Hat:rhel_eus:8.6::baseoskernel-debuginfo-common-s390xbefore 0:4.18.0-372.80.1.el8_60:4.18.0-372.80.1.el8_6
Red Hat:rhel_eus:8.6::baseoskernel-docbefore 0:4.18.0-372.80.1.el8_60:4.18.0-372.80.1.el8_6
Red Hat:rhel_eus:8.6::baseoskernel-modulesbefore 0:4.18.0-372.80.1.el8_60:4.18.0-372.80.1.el8_6
Red Hat:rhel_eus:8.6::baseoskernel-modules-extrabefore 0:4.18.0-372.80.1.el8_60:4.18.0-372.80.1.el8_6
Red Hat:rhel_eus:8.6::baseoskernel-toolsbefore 0:4.18.0-372.80.1.el8_60:4.18.0-372.80.1.el8_6
Red Hat:rhel_eus:8.6::baseoskernel-tools-libsbefore 0:4.18.0-372.80.1.el8_60:4.18.0-372.80.1.el8_6
Red Hat:rhel_eus:8.6::baseoskernel-zfcpdumpbefore 0:4.18.0-372.80.1.el8_60:4.18.0-372.80.1.el8_6
Red Hat:rhel_eus:8.6::baseoskernel-zfcpdump-corebefore 0:4.18.0-372.80.1.el8_60:4.18.0-372.80.1.el8_6
Red Hat:rhel_eus:8.6::baseoskernel-zfcpdump-debuginfobefore 0:4.18.0-372.80.1.el8_60:4.18.0-372.80.1.el8_6
Red Hat:rhel_eus:8.6::baseoskernel-zfcpdump-develbefore 0:4.18.0-372.80.1.el8_60:4.18.0-372.80.1.el8_6
Red Hat:rhel_eus:8.6::baseoskernel-zfcpdump-modulesbefore 0:4.18.0-372.80.1.el8_60:4.18.0-372.80.1.el8_6
Red Hat:rhel_eus:8.6::baseoskernel-zfcpdump-modules-extrabefore 0:4.18.0-372.80.1.el8_60:4.18.0-372.80.1.el8_6

+11

Other highest-scoring records for the same primary product.

  • 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
  • CVE-2016-5195Race condition in mm/gup.c in the Linux kernel 2.x through 4.x before 4.8.3 allows local users to gain privileges by leveraging incorrect haKEV
    83Now
  • CVE-2019-13272In the Linux kernel before 5.1.17, ptrace_link in kernel/ptrace.c mishandles the recording of the credentials of a process that wants to creKEV
    77This week
  • CVE-2013-6282The (1) get_user and (2) put_user API functions in the Linux kernel before 3.5.5 on the v6k and v7 ARM platforms do not validate certain addKEV
    77This week
  • CVE-2013-2094The perf_swevent_init function in kernel/events/core.c in the Linux kernel before 3.8.9 uses an incorrect integer data type, which allows loKEV
    77This week

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 Linux022152aaebe116a25c39818a07e175a8cd3c1e11Vendor (CNA)
Linux Linux0f90099d18e3abdc01babf686f41f63fe04939c1Vendor (CNA)
Linux Linux19d636b663e0e92951bba5fced929ca7fd25c552Vendor (CNA)
Linux Linux382ff44716603a54f5fd238ddec6a2468e217612Vendor (CNA)
Linux Linux3b0fcf5e29c0940e1169ce9c44f73edd98bdf12dVendor (CNA)
Linux Linux4.19.262Vendor (CNA)
Linux Linux5.10.150Vendor (CNA)
Linux Linux5.14Vendor (CNA)
Linux Linux5.4.220Vendor (CNA)
Linux Linuxb8fa99a3a11bdd77fef6b4a97f1021eb30b5ba40Vendor (CNA)
Linux Linuxf65955340e0044f5c41ac799a01698ac7dee8a4eVendor (CNA)
debian:linux6.0.3-1 · Debian:12Package registry (OSV)
red hat:bpftool0:4.18.0-372.80.1.el8_6 · Red Hat:rhel_eus:8.6::baseosPackage registry (OSV)
red hat:bpftool-debuginfo0:4.18.0-372.80.1.el8_6 · Red Hat:rhev_hypervisor:4.4::el8Package registry (OSV)
red hat:kernel0:4.18.0-372.80.1.el8_6 · Red Hat:rhel_eus:8.6::baseosPackage registry (OSV)
red hat:kernel-abi-stablelists0:4.18.0-372.80.1.el8_6 · Red Hat:rhel_eus:8.6::baseosPackage registry (OSV)
red hat:kernel-debug-debuginfo0:4.18.0-372.80.1.el8_6 · Red Hat:rhev_hypervisor:4.4::el8Package registry (OSV)
red hat:kernel-debuginfo0:4.18.0-372.80.1.el8_6 · Red Hat:rhev_hypervisor:4.4::el8Package registry (OSV)
red hat:kernel-debuginfo-common-x86_640:4.18.0-372.80.1.el8_6 · Red Hat:rhev_hypervisor:4.4::el8Package registry (OSV)
red hat:kernel-devel0:4.18.0-372.80.1.el8_6 · Red Hat:rhev_hypervisor:4.4::el8Package registry (OSV)
red hat:kernel-tools-debuginfo0:4.18.0-372.80.1.el8_6 · Red Hat:rhev_hypervisor:4.4::el8Package registry (OSV)
red hat:perf0:4.18.0-372.80.1.el8_6 · Red Hat:rhev_hypervisor:4.4::el8Package registry (OSV)
red hat:perf-debuginfo0:4.18.0-372.80.1.el8_6 · Red Hat:rhev_hypervisor:4.4::el8Package registry (OSV)
red hat:python3-perf-debuginfo0:4.18.0-372.80.1.el8_6 · Red Hat:rhev_hypervisor:4.4::el8Package 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.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

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
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

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

nvd-primary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

c
free(dev->buf);/* ... another thread is still running ... */process(dev->buf);

Fixed

c
lock(&dev->lock);free(dev->buf);dev->buf = NULL;unlock(&dev->lock);

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. Fix✗ → ✓

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

References

All records