Linux Kernel up to 7.0.12 sctp net/sctp/input.c __sctp_rcv_asconf_lookup header uninitialized pointer

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
6.0$0-$5k1.22

Summaryinfo

A vulnerability classified as critical has been found in Linux Kernel up to 7.0.12. This issue affects the function __sctp_rcv_asconf_lookup of the file net/sctp/input.c of the component sctp. This manipulation of the argument header causes uninitialized pointer. The identification of this vulnerability is CVE-2026-53225. There is no exploit available. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability has been found in Linux Kernel up to 7.0.12 and classified as critical. Affected by this vulnerability is the function __sctp_rcv_asconf_lookup of the file net/sctp/input.c of the component sctp. The manipulation of the argument header with an unknown input leads to a uninitialized pointer vulnerability. The CWE definition for the vulnerability is CWE-824. The product accesses or uses a pointer that has not been initialized. The impact remains unknown. The summary by CVE is:

In the Linux kernel, the following vulnerability has been resolved: sctp: fix uninit-value in __sctp_rcv_asconf_lookup() __sctp_rcv_asconf_lookup() in net/sctp/input.c only checks that the ASCONF chunk can hold the ADDIP header and a parameter header, then calls af->from_addr_param(), which reads the full address (16 bytes for IPv6) trusting the parameter's declared length. An unauthenticated peer can send a truncated trailing ASCONF chunk that declares an IPv6 address parameter but stops after the 4-byte parameter header; reached from the no-association lookup path, from_addr_param() then reads uninitialized bytes past the parameter. Impact: an unauthenticated SCTP peer makes the receive path read up to 16 bytes of uninitialized memory past a truncated ASCONF address parameter. The sibling __sctp_rcv_init_lookup() bounds parameters with sctp_walk_params(); this path open-codes the fetch and omits the bound. Verify the whole address parameter lies within the chunk before from_addr_param() reads it, the same class of fix as commit 51e5ad549c43 ("net: sctp: fix KMSAN uninit-value in sctp_inq_pop").

The advisory is shared at git.kernel.org. This vulnerability is known as CVE-2026-53225 since 06/09/2026. The exploitation doesn't need any form of authentication. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 06/25/2026).

Upgrading to version 5.10.259, 5.15.210, 6.1.176, 6.6.143, 6.12.94, 6.18.36 or 7.0.13 eliminates this vulnerability. Applying the patch 446e0ecd845abc394b24ae2030a883572bec9d16/928dd94db23e8ba340f83d68f7f24d831b7a4426/d796cfd06074b579d265b28401306cadd30db945/8ce96f1182644079249a24ac7e2ffc32e0301a46/d6bd0bb7697ea8c0387b0d9d973453f479017b23/f76a8b323e28e0951f979dbef20a7496383c47df/8e86817b8af4d552f3c6fe04ca52bb0c8c57411d/f8373d7090b745728de66308deeecc67e8d319ce is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 6.3
VulDB Meta Temp Score: 6.0

VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Uninitialized pointer
CWE: CWE-824 / CWE-908
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
Remote: Partially

Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 5.10.259/5.15.210/6.1.176/6.6.143/6.12.94/6.18.36/7.0.13
Patch: 446e0ecd845abc394b24ae2030a883572bec9d16/928dd94db23e8ba340f83d68f7f24d831b7a4426/d796cfd06074b579d265b28401306cadd30db945/8ce96f1182644079249a24ac7e2ffc32e0301a46/d6bd0bb7697ea8c0387b0d9d973453f479017b23/f76a8b323e28e0951f979dbef20a7496383c47df/8e86817b8af4d552f3c6fe04ca52bb0c8c57411d/f8373d7090b745728de66308deeecc67e8d319ce

Timelineinfo

06/09/2026 CVE reserved
06/25/2026 +16 days Advisory disclosed
06/25/2026 +0 days VulDB entry created
06/25/2026 +0 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-53225 (🔒)
GCVE (CVE): GCVE-0-2026-53225
GCVE (VulDB): GCVE-100-373729

Entryinfo

Created: 06/25/2026 12:10
Changes: 06/25/2026 12:10 (22), 06/25/2026 12:11 (39)
Complete: 🔍
Cache ID: 216::103

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Do you need the next level of professionalism?

Upgrade your account now!