CVE-2026-72447

CVE CVE-2026-72447EUVD EUVD-2026-59346Published 2026-08-15T05:56:57.000ZLast changed 2026-08-17T05:14:49.000Z

What the advisory describes

In the Linux kernel, the following vulnerability has been resolved: sctp: hold socket lock when dumping endpoints in sctp_diag SCTP_DIAG endpoint dumping was traversing endpoint address lists without holding lock_sock(), while those lists could change concurrently via socket operations (e.g., bindx changes). This creates a race where nla_reserve() counts addresses under RCU protection, but the subsequent copy may see fewer entries, potentially leaking uninitialized memory to userspace. Fix this by: - Taking a reference on each endpoint during hash traversal - Moving socket operations (lock_sock()) outside read_lock_bh() - Serializing address list access during dump - Reworking sctp_for_each_endpoint() to support restart-based traversal with (net, pos) tracking Also: - Add WARN_ON_ONCE() for inconsistent address counts - Fix idiag_states filtering for LISTEN vs association cases - Skip dumping endpoints being freed (ep->base.dead) - Move dump position tracking into iterator, removing cb->args[4] and its comment for sctp_ep_dump()., - Update the comment for cb->args[4] and remove the comment for unused cb->args[5] for sctp_sock_dump(). Note: traversal is restart-based and may re-scan buckets multiple times, but this is acceptable due to small bucket sizes and required to support sleeping-safe callbacks. This issue was reported by Nico Yip (@_cyeaa_) working with TrendAI Zero Day Initiative.

Source: EUVD (ENISA), in the words of the advisory.

Products the advisory names

These come from the advisory itself, not from any check we performed.

• Linux — Linux patch: 7.2; patch: 0; patch: 5.10.261; patch: 7.1.5; 8f840e47f190cbe61a96945c13e9551048d42cef <8b38e3dcfde3077dbc03eb8ef88e03cc19f70b8a; 8f840e47f190cbe61a96945c13e9551048d42cef <7d8297e26b4e20b5d1c3c3fe51fe81a1c7fbc823; 4.7; 8f840e47f190cbe61a96945c13e9551048d42cef <722576aba0a6d9423714550b1c03239b0f0def77; patch: 6.18.40; 8f840e47f190cbe61a96945c13e9551048d42cef <207bb4ce8fe7de961ae7bb33569ad2cd61f44954; 8f840e47f190cbe61a96945c13e9551048d42cef <abe7f8828e6ac8be858870c2bf836258844f97d5; 8f840e47f190cbe61a96945c13e9551048d42cef <f09a245f33e567b604efa1960b7a2d25dd9c8713; 8f840e47f190cbe61a96945c13e9551048d42cef <ec3c2d59a192e17e1014ba71afc368ba162ecac3; patch: 6.1.178; 8f840e47f190cbe61a96945c13e9551048d42cef <f98c294a9369b6fe89e652c06357ee594be4dfa2; patch: 5.15.212; patch: 6.6.145; patch: 6.12.97

The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.

Carried in the product catalogue

An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.

• Linux — Linux

Patchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.