GCVE Workshop - 22 September 2026 (14:00-18:00), Luxembourg Before The Vulnopticon Conference - Registration

GHSA-P5MF-MJH6-46FM

Vulnerability from github – Published: 2026-08-15 06:32 – Updated: 2026-08-15 06:32
VLAI
Details

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.

Show details on source website
To clipboard 

{
  "affected": [],
  "aliases": [
    "CVE-2026-72447"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-08-15T06:22:18Z",
    "severity": null
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nsctp: hold socket lock when dumping endpoints in sctp_diag\n\nSCTP_DIAG endpoint dumping was traversing endpoint address lists without\nholding lock_sock(), while those lists could change concurrently via\nsocket operations (e.g., bindx changes). This creates a race where\nnla_reserve() counts addresses under RCU protection, but the subsequent\ncopy may see fewer entries, potentially leaking uninitialized memory to\nuserspace.\n\nFix this by:\n\n- Taking a reference on each endpoint during hash traversal\n- Moving socket operations (lock_sock()) outside read_lock_bh()\n- Serializing address list access during dump\n- Reworking sctp_for_each_endpoint() to support restart-based traversal\n  with (net, pos) tracking\n\nAlso:\n\n- Add WARN_ON_ONCE() for inconsistent address counts\n- Fix idiag_states filtering for LISTEN vs association cases\n- Skip dumping endpoints being freed (ep-\u003ebase.dead)\n- Move dump position tracking into iterator, removing cb-\u003eargs[4] and\n  its comment for sctp_ep_dump().,\n- Update the comment for cb-\u003eargs[4] and remove the comment for unused\n  cb-\u003eargs[5] for sctp_sock_dump().\n\nNote: traversal is restart-based and may re-scan buckets multiple times,\nbut this is acceptable due to small bucket sizes and required to support\nsleeping-safe callbacks.\n\nThis issue was reported by Nico Yip (@_cyeaa_) working with TrendAI Zero\nDay Initiative.",
  "id": "GHSA-p5mf-mjh6-46fm",
  "modified": "2026-08-15T06:32:25Z",
  "published": "2026-08-15T06:32:24Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-72447"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/207bb4ce8fe7de961ae7bb33569ad2cd61f44954"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/722576aba0a6d9423714550b1c03239b0f0def77"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/7d8297e26b4e20b5d1c3c3fe51fe81a1c7fbc823"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/8b38e3dcfde3077dbc03eb8ef88e03cc19f70b8a"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/abe7f8828e6ac8be858870c2bf836258844f97d5"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/ec3c2d59a192e17e1014ba71afc368ba162ecac3"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/f09a245f33e567b604efa1960b7a2d25dd9c8713"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/f98c294a9369b6fe89e652c06357ee594be4dfa2"
    }
  ],
  "schema_version": "1.4.0",
  "severity": []
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.





Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.


Detection rules are retrieved from Rulezet.


Related by attack behaviour

Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.