CVE-2026-98323 in the critical feed json
RDMA/siw: Bound fragmented header copies by the remaining length
published last mo. modified 23d ago also EUVD-2026-93308
- cvss
- 9.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 44%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
RDMA/siw: Bound fragmented header copies by the remaining length
siw_get_hdr() can receive an extended DDP/RDMAP header across more than one TCP callback. The first callback may receive most of the header, while the next one still limits the copy to hdrlen - MIN_DDP_HDR instead of the number of missing bytes. This makes the destination move past the end of the header and overwrite the receive state, including fpdu_part_rcvd. A later callback can then use a negative fpdu_part_rcvd value as a copy offset, which creates an OOB write.
Use the number of header bytes already received when calculating the next copy length.
Patch / fix
- Linux Linux 5.5, 5.10.271, 5.15.222, 5.20, 6.1, 7.3
- linux Debian 12 6.1.190-1
- linux Debian 13 6.12.113-1
- linux Debian 14 7.2.8-1
- linux-6.12 Debian 12 6.12.113-1~deb12u1
debian advisories DEBIAN-CVE-2026-98323
- linux Ubuntu 22.04 LTS 5.15.0-202.212
- linux Ubuntu 24.04 LTS 6.8.0-149.149
- linux Ubuntu 26.04 LTS 7.0.0-42.42
- linux-aws Ubuntu 22.04 LTS 5.15.0-1119.126
- linux-aws Ubuntu 24.04 LTS 6.8.0-1069.74
- linux-aws Ubuntu 26.04 LTS 7.0.0-1016.17
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1120.130
- linux-gcp Ubuntu 24.04 LTS 6.8.0-1073.81
ubuntu advisories UBUNTU-CVE-2026-98323
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- kernel-rt Real Time Module 15 SP7 6.4.0-150700.7.81.1
- kernel-syms-rt Real Time Module 15 SP7 6.4.0-150700.7.81.1
- kernel-source-rt Real Time Module 15 SP7 6.4.0-150700.7.81.1
- kernel-rt SLE Micro 5.4 5.14.21-150400.15.192.2
- kernel-source-rt SLE Micro 5.4 5.14.21-150400.15.192.2
- kernel-rt SLE Micro 5.5 5.14.21-150500.13.167.2
- kernel-source-rt SLE Micro 5.5 5.14.21-150500.13.167.2
- kernel-64kb SLES 15 SP4-LTSS, SLE High Performance Computing 15 SP4-LTSS, SLE High Performance Computing 15 SP4-ESPOS 5.14.21-150400.24.246.1
suse advisories SUSE-SU-2026:4940-1SUSE-SU-2026:4939-1SUSE-SU-2026:4938-1SUSE-SU-2026:4937-1SUSE-SU-2026:4936-1SUSE-SU-2026:4935-1
- kernel-rt openSUSE Leap 16.0 6.12.0-160000.40.1
- dtb-aarch64 openSUSE Leap 16.0 6.12.0-160000.40.1
- kernel-64kb openSUSE Leap 16.0 6.12.0-160000.40.1
- kernel-syms openSUSE Leap 16.0 6.12.0-160000.40.1
- kernel-azure openSUSE Leap 16.0 6.12.0-160000.40.1
- kernel-obs-qa openSUSE Leap 16.0 6.12.0-160000.40.1
- kernel-source openSUSE Leap 16.0 6.12.0-160000.40.1
- kernel-default openSUSE Leap 16.0 6.12.0-160000.40.1
opensuse advisories openSUSE-SU-2026:22167-1openSUSE-SU-2026:12131-1
- kernel Azure Linux 3.0 6.6.158.1-1
azure linux advisories AZL-106458
Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT
- git.kernel.org/stable/c/2c6fbcf4bfac0b2b186acc8d91154c0fa24468a7 commit
- git.kernel.org/stable/c/af9f5b474a260ad23ffb9793d716a5e3bbce3b48 commit
- git.kernel.org/stable/c/262dcd809723723ed8a4e05437ec7e9c21a8f17e commit
- git.kernel.org/stable/c/eb4d7a946970469b3ab0c762432bf161d5b0836c commit
- git.kernel.org/stable/c/8628f8ebf41669302513fb3f0bf0eba38b226742 commit
- git.kernel.org/stable/c/b72dcfb9bf1f0f0147cda03dc59e4002a315067f commit
- git.kernel.org/stable/c/e6bdfdf3bcb02d0d626a45e8c98b7e63d2fddf9d commit
- git.kernel.org/stable/c/9ff797e516dbc1ecb73701ec4c24055712d44411 commit
Is CVE-2026-98323 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-98323 updated cvss 7.0
kernel: RDMA/siw: Bound fragmented header copies by the remaining length
-
Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat OpenShift Container Platform 4 openshift/ose-rhel-coreos-9 Red Hat OpenShift Container Platform 5 openshift/ose-rhel-coreos-9affected: workaround, no fix available
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 10 kernel Red Hat OpenShift Container Platform 4 openshift/ose-rhel-coreos-8not affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.51% chance of exploitation in the next 30 days, higher than 44% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/2c6fbcf4bfac0b2b186acc8d91154c0fa24468a7
- git.kernel.org /stable/c/af9f5b474a260ad23ffb9793d716a5e3bbce3b48
- git.kernel.org /stable/c/262dcd809723723ed8a4e05437ec7e9c21a8f17e
- git.kernel.org /stable/c/eb4d7a946970469b3ab0c762432bf161d5b0836c
- git.kernel.org /stable/c/8628f8ebf41669302513fb3f0bf0eba38b226742
- git.kernel.org /stable/c/b72dcfb9bf1f0f0147cda03dc59e4002a315067f
- git.kernel.org /stable/c/e6bdfdf3bcb02d0d626a45e8c98b7e63d2fddf9d
- git.kernel.org /stable/c/9ff797e516dbc1ecb73701ec4c24055712d44411
Sources
- CVE List CVE-2026-98323
- NVD CVE-2026-98323
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.