# CVE-2026-80717: sctp: validate Adaptation Indication parameter length

> A remote attacker can disclose four bytes of kernel memory by sending a malformed SCTP INIT packet with a truncated Adaptation Indication parameter.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 Aug 2026
- **Updated:** 16 Oct 2026
- **Also known as:** AZL-98190, BELL-CVE-2026-80717, DEBIAN-CVE-2026-80717, GHSA-fq3m-cvqw-wrvh, UBUNTU-CVE-2026-80717

## What is CVE-2026-80717?

CVE-2026-80717 is a high-severity vulnerability in Linux, published on 28 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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

sctp: validate Adaptation Indication parameter length

The Adaptation Layer Indication parameter contains a fixed 32-bit
Adaptation Code Point after its parameter header. However,
sctp_verify_param() accepts a header-only parameter because the generic
parameter walker only requires the header to be present.

sctp_process_param() then reads adaptation_ind beyond the declared
parameter. When the malformed parameter is last in an INIT, the read
starts at the receive skb tail, and the value is copied into the state
cookie returned in the INIT ACK. This may disclose four receive-buffer
tail bytes.

Require the declared parameter length to match the fixed structure size
and abort the association through the existing invalid parameter length
path otherwise.

## Which versions are affected by CVE-2026-80717?


## How do I fix CVE-2026-80717?

Apply the vendor's patch.

## Is CVE-2026-80717 being exploited?

There is no known exploitation of CVE-2026-80717 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-80717 and fix it if it is affected.

What it is: CVE-2026-80717 is a high-severity vulnerability in Linux, published on 28 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-80717 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-80717/ (Markdown: https://insights.sbomify.com/CVE-2026-80717/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-80717
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-80717
- OSV: https://osv.dev/vulnerability/CVE-2026-80717

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-80717/
Summaries are generated and may contain mistakes; the official description above is the record.