Vulnerability-Lookup

GHSA-H9P5-Q3G4-GM7M

Vulnerability from github – Published: 2026-10-28 12:31 – Updated: 2026-10-28 12:31

Details

In the Linux kernel, the following vulnerability has been resolved:

sctp: revalidate output stream after association connect wait

When message interleaving is enabled, the first send waits for association establishment before building its data chunks. The wait drops the socket lock, and handshake processing can reduce the output stream count to the peer-advertised inbound stream count. sctp_stream_init() then frees the extension of every removed stream.

The sender resumes with the stream that it checked before the wait. If the peer removed that stream, sctp_outq_tail() later dereferences its NULL extension. Fatal-oops policies then panic the host.

KASAN: null-ptr-deref in range [0x38-0x3f] RIP: sctp_outq_tail+0x49e/0xaa0 Call Trace: sctp_primitive_SEND sctp_sendmsg_to_asoc sctp_sendmsg

A range check alone is insufficient. Stream reconfiguration can grow the output count again while the lock is released without recreating extensions freed by the earlier shrink. The stream can then be in range while its extension remains NULL. The send-buffer wait has the same issue.

Factor the range and extension checks into a helper and repeat both after each send-path wait that drops the socket lock. Once the lock is reacquired, the validation remains stable through data creation and queueing.

If validation fails after the connect wait, the auto-created association is already established. Return ESRCH so the existing caller path keeps it under state-machine ownership instead of freeing it directly, which would leave protocol, counter and socket state inconsistent.

Show details on source website

JSON

To clipboard

{
  "affected": [],
  "aliases": [
    "CVE-2026-99165"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-10-28T11:17:36Z",
    "severity": null
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nsctp: revalidate output stream after association connect wait\n\nWhen message interleaving is enabled, the first send waits for association\nestablishment before building its data chunks.  The wait drops the socket\nlock, and handshake processing can reduce the output stream count to the\npeer-advertised inbound stream count.  sctp_stream_init() then frees the\nextension of every removed stream.\n\nThe sender resumes with the stream that it checked before the wait.  If the\npeer removed that stream, sctp_outq_tail() later dereferences its NULL\nextension.  Fatal-oops policies then panic the host.\n\nKASAN: null-ptr-deref in range [0x38-0x3f]\nRIP: sctp_outq_tail+0x49e/0xaa0\nCall Trace:\n sctp_primitive_SEND\n sctp_sendmsg_to_asoc\n sctp_sendmsg\n\nA range check alone is insufficient.  Stream reconfiguration can grow the\noutput count again while the lock is released without recreating extensions\nfreed by the earlier shrink.  The stream can then be in range while its\nextension remains NULL.  The send-buffer wait has the same issue.\n\nFactor the range and extension checks into a helper and repeat both after\neach send-path wait that drops the socket lock.  Once the lock is\nreacquired, the validation remains stable through data creation and\nqueueing.\n\nIf validation fails after the connect wait, the auto-created association is\nalready established.  Return ESRCH so the existing caller path keeps it\nunder state-machine ownership instead of freeing it directly, which would\nleave protocol, counter and socket state inconsistent.",
  "id": "GHSA-h9p5-q3g4-gm7m",
  "modified": "2026-10-28T12:31:06Z",
  "published": "2026-10-28T12:31:06Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-99165"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/77a63d1b813b08c4e5a948f5e04fbaca6176aa8f"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/b7ad72414c673ce1fa1f463e807cd4f34f8be9bf"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/fd56ac95ec31a05b66e8938debfa847f49c0e993"
    }
  ],
  "schema_version": "1.4.0",
  "severity": []
}

CVE-2026-99165 (GCVE-0-2026-99165)

Vulnerability from cvelistv5 – Published: 2026-10-28 10:35 – Updated: 2026-10-28 10:35

Title

sctp: revalidate output stream after association connect wait

Summary

In the Linux kernel, the following vulnerability has been resolved: sctp: revalidate output stream after association connect wait When message interleaving is enabled, the first send waits for association establishment before building its data chunks. The wait drops the socket lock, and handshake processing can reduce the output stream count to the peer-advertised inbound stream count. sctp_stream_init() then frees the extension of every removed stream. The sender resumes with the stream that it checked before the wait. If the peer removed that stream, sctp_outq_tail() later dereferences its NULL extension. Fatal-oops policies then panic the host. KASAN: null-ptr-deref in range [0x38-0x3f] RIP: sctp_outq_tail+0x49e/0xaa0 Call Trace: sctp_primitive_SEND sctp_sendmsg_to_asoc sctp_sendmsg A range check alone is insufficient. Stream reconfiguration can grow the output count again while the lock is released without recreating extensions freed by the earlier shrink. The stream can then be in range while its extension remains NULL. The send-buffer wait has the same issue. Factor the range and extension checks into a helper and repeat both after each send-path wait that drops the socket lock. Once the lock is reacquired, the validation remains stable through data creation and queueing. If validation fails after the connect wait, the auto-created association is already established. Return ESRCH so the existing caller path keeps it under state-machine ownership instead of freeing it directly, which would leave protocol, counter and socket state inconsistent.

Severity

No CVSS data available.

Assigner

Linux CNA under the mitre root

CNA scorecard D 53/100 over 7033 records in the last 180 days details

References

3 references

URL	Tags
https://git.kernel.org/stable/c/77a63d1b813b08c4e…
https://git.kernel.org/stable/c/fd56ac95ec31a05b6…
https://git.kernel.org/stable/c/b7ad72414c673ce1f…

Impacted products

2 products

Vendor	Product	Version
Linux	Linux	Affected: 668c9beb9020d5834ee9e43c208190a07d2b1928 , < 77a63d1b813b08c4e5a948f5e04fbaca6176aa8f (git) Affected: 668c9beb9020d5834ee9e43c208190a07d2b1928 , < fd56ac95ec31a05b66e8938debfa847f49c0e993 (git) Affected: 668c9beb9020d5834ee9e43c208190a07d2b1928 , < b7ad72414c673ce1fa1f463e807cd4f34f8be9bf (git)
Linux	Linux	Affected: 4.16 Unaffected: 0 , < 4.16 (semver) Unaffected: 6.18.59 , ≤ 6.18.* (semver) Unaffected: 7.2.13 , ≤ 7.2.* (semver) Unaffected: 7.3 , ≤ * (original_commit_for_fix)

Show details on NVD website

JSON

To clipboard

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "net/sctp/socket.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "77a63d1b813b08c4e5a948f5e04fbaca6176aa8f",
              "status": "affected",
              "version": "668c9beb9020d5834ee9e43c208190a07d2b1928",
              "versionType": "git"
            },
            {
              "lessThan": "fd56ac95ec31a05b66e8938debfa847f49c0e993",
              "status": "affected",
              "version": "668c9beb9020d5834ee9e43c208190a07d2b1928",
              "versionType": "git"
            },
            {
              "lessThan": "b7ad72414c673ce1fa1f463e807cd4f34f8be9bf",
              "status": "affected",
              "version": "668c9beb9020d5834ee9e43c208190a07d2b1928",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "net/sctp/socket.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "4.16"
            },
            {
              "lessThan": "4.16",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.18.*",
              "status": "unaffected",
              "version": "6.18.59",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "7.2.*",
              "status": "unaffected",
              "version": "7.2.13",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "7.3",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.18.59",
                  "versionStartIncluding": "4.16",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.2.13",
                  "versionStartIncluding": "4.16",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.3",
                  "versionStartIncluding": "4.16",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nsctp: revalidate output stream after association connect wait\n\nWhen message interleaving is enabled, the first send waits for association\nestablishment before building its data chunks.  The wait drops the socket\nlock, and handshake processing can reduce the output stream count to the\npeer-advertised inbound stream count.  sctp_stream_init() then frees the\nextension of every removed stream.\n\nThe sender resumes with the stream that it checked before the wait.  If the\npeer removed that stream, sctp_outq_tail() later dereferences its NULL\nextension.  Fatal-oops policies then panic the host.\n\nKASAN: null-ptr-deref in range [0x38-0x3f]\nRIP: sctp_outq_tail+0x49e/0xaa0\nCall Trace:\n sctp_primitive_SEND\n sctp_sendmsg_to_asoc\n sctp_sendmsg\n\nA range check alone is insufficient.  Stream reconfiguration can grow the\noutput count again while the lock is released without recreating extensions\nfreed by the earlier shrink.  The stream can then be in range while its\nextension remains NULL.  The send-buffer wait has the same issue.\n\nFactor the range and extension checks into a helper and repeat both after\neach send-path wait that drops the socket lock.  Once the lock is\nreacquired, the validation remains stable through data creation and\nqueueing.\n\nIf validation fails after the connect wait, the auto-created association is\nalready established.  Return ESRCH so the existing caller path keeps it\nunder state-machine ownership instead of freeing it directly, which would\nleave protocol, counter and socket state inconsistent."
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-10-28T10:35:17.366Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/77a63d1b813b08c4e5a948f5e04fbaca6176aa8f"
        },
        {
          "url": "https://git.kernel.org/stable/c/fd56ac95ec31a05b66e8938debfa847f49c0e993"
        },
        {
          "url": "https://git.kernel.org/stable/c/b7ad72414c673ce1fa1f463e807cd4f34f8be9bf"
        }
      ],
      "title": "sctp: revalidate output stream after association connect wait",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2026-99165",
    "datePublished": "2026-10-28T10:35:17.366Z",
    "dateReserved": "2026-09-25T10:25:14.398Z",
    "dateUpdated": "2026-10-28T10:35:17.366Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

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.

Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

Order JSON

Publication & reservation Sightings KEV catalogs Other timestamps

Loading timeline…

The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base model, served locally by ML-Gateway. They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.

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.

Action not permitted