dbcve.org
Linux KernelOperating system · Linux

CVE-2026-53004

HIGH · 7.8 CVSS v3.1 Published 2026-06-24
Fix available
A fix is available. Upgrade to 5.10.258 / 5.15.209 or later.
See remediation →
80/100
Remediation priority · High
Zero-click 8 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
In the Linux kernel, the following vulnerability has been resolved: sctp: fix OOB write to userspace in sctp_getsockopt_peer_auth_chunks sctp_getsockopt_peer_auth_chunks() checks that the caller's optval buffer is large enough for the peer AUTH chunk list with if (len < num_chunks) return -EINVAL; but then writes num_chunks bytes to p->gauth_chunks, which lives at offset offsetof(struct sctp_authchunks, gauth_chunks) == 8 inside optval. The check is missing the sizeof(struct sctp_authchunks) = 8-byte header. When the caller supplies len == num_chunks (for any num_chunks > 0) the test passes but copy_to_user() writes sizeof(struct sctp_authchunks) = 8 bytes past the declared buffer. The sibling function sctp_getsockopt_local_auth_chunks() at the next line already has the correct check: if (len < sizeof(struct sctp_authchunks) + num_chunks) return -EINVAL; Align the peer variant with its sibling. Reproducer confirms on v7.0-13-generic: an unprivileged userspace caller that opens a loopback SCTP association with AUTH enabled, queries num_chunks with a short optval, then issues the real getsockopt with len == num_chunks and sentinel bytes painted past the buffer observes those sentinel bytes overwritten with the peer's AUTH chunk type. The bytes written are under the peer's control but land in the caller's own userspace; this is not a kernel memory corruption, but it is a kernel-side contract violation that can silently corrupt adjacent userspace data.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Out-of-bounds write vulnerability in Linux kernel SCTP's sctp_getsockopt_peer_auth_chunks() function. The code validates buffer length with 'len < num_chunks' but writes to p->gauth_chunks which starts 8 bytes into the structure, missing the struct sctp_authchunks header. When len equals num_chunks, copy_to_user() writes 8 bytes past the user's buffer, corrupting adjacent userspace memory.

MitigationApply the kernel patch that corrects the buffer length check to include sizeof(struct sctp_authchunks), aligning with the sibling function sctp_getsockopt_local_auth_chunks(). Update Linux kernel to version containing the fix.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Linux KernelOperating system
Affected:>= 2.6.24, < 5.10.258>= 5.11, < 5.15.209>= 5.16, < 6.1.175>= 6.2, < 6.6.141>= 6.7, < 6.12.91>= 6.13, < 6.18.33>= 6.19, < 7.0.10

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if SCTP protocol support is enabled
    Run 'lsmod | grep sctp' to see if the sctp module is loaded, or check /proc/config.gz for CONFIG_IP_SCTP=y if the kernel was built with modular SCTP support
    Affected if The sctp module is loaded or SCTP is compiled into the kernel (CONFIG_IP_SCTP is set)
  2. Identify running SCTP sockets
    Run 'ss -S' or 'netstat -S' to list active SCTP associations and sockets on the system
    Affected if Any SCTP sockets (SOCK_STREAM, SOCK_SEQPACKET) are established or listening on the host
  3. Check for applications using SCTP
    Run 'lsof +c 0 2>/dev/null | grep -i sctp' or 'ss -S state established' to see which processes have SCTP connections
    Affected if Any process is actively using SCTP sockets, as the vulnerable function is called via getsockopt() on SCTP sockets
  4. Verify kernel version against affected ranges
    Run 'uname -r' to get the kernel version, then compare against the affected ranges: < 5.10.258, >= 5.11 to < 5.15.209, >= 5.16 to < 6.1.175, >= 6.2 to < 6.6.141, >= 6.7 to < 6.12.91, >= 6.13 to < 6.18.33, >= 6.19 to < 7.0.10
    Affected if The running kernel version falls within any of the listed vulnerable version ranges

The system is affected if the kernel version is in a vulnerable range AND SCTP is enabled with active SCTP socket usage, since the out-of-bounds write occurs when getsockopt() is called with SCTP_PEER_AUTH_CHUNKS on an SCTP socket.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 5.10.258 / 5.15.209 / 6.1.175 or later
Fixed in 5.10.2585.15.2096.1.175
Interim mitigation

Apply the kernel patch that corrects the buffer length check to include sizeof(struct sctp_authchunks), aligning with the sibling function sctp_getsockopt_local_auth_chunks(). Update Linux kernel to version containing the fix.

Recommended fix High confidence

Upgrade to Linux kernel >= 5.10.258 (for 5.10.y), >= 5.15.209 (for 5.15.y), >= 6.1.175 (for 6.1.y), or >= 6.6.141 (for 6.2-6.6.y) - or any later stable release

  1. Identify the currently running kernel version using `uname -r`
  2. Check if your distribution has released a kernel update for your version by running `apt list --upgradable` (Debian/Ubuntu), `dnf check-update` (RHEL/Fedora), or checking your distribution's security advisories
  3. If an updated kernel is available, upgrade it using your package manager (e.g., `sudo apt update && sudo apt upgrade linux-image-*` for Debian/Ubuntu, or `sudo dnf update kernel` for RHEL/Fedora)
  4. Reboot the system to load the patched kernel using `sudo reboot`
  5. Verify the fix is applied by checking the kernel version with `uname -r` matches a version >= 5.10.258, 5.15.209, 6.1.175, or 6.6.141 depending on your branch
Caveat Kernel upgrades may require system reboot and could introduce compatibility issues with custom kernel modules or specific hardware drivers; test in staging before production deployment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Linux Kernel Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-53004 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-53004 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data