CVE-2026-74747 json
ipvs: revalidate ihl to prevent out-of-bounds access
published 2026-08-26 2 mo ago modified 2026-10-30 9 d ago also EUVD-2026-66577
- cvss
- 7.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.1%
- EPSS 0.1% chance of exploitation in 30 days, percentile 3%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
ipvs: revalidate ihl to prevent out-of-bounds access
While the outer IP header is already pulled into the skb head, we must be careful and revalidate the embedded headers after reading them from the skb frags to prevent out-of-bounds access.
One such place reported by Sashiko is ip_vs_nat_icmp() where local process can change the ihl field and after skb_ensure_writable() we can see larger value which is a problem for the ip_send_check(cih) calls.
Add check to drop the packet if the ihl field is changed.
Patch / fix
- Linux Linux 6.1.191, 6.6.160, 6.12.114, 6.18.57, 7.1.10, 7.2
- linux Debian 13 6.12.115-2
- linux Debian 14 7.1.10-1
debian advisories DEBIAN-CVE-2026-74747
- linux Ubuntu 26.04 LTS 7.0.0-42.42
- linux-aws Ubuntu 26.04 LTS 7.0.0-1016.17
- linux-gcp Ubuntu 26.04 LTS 7.0.0-1016.18
- linux-ibm Ubuntu 26.04 LTS 7.0.0-1017.17
- linux-riscv Ubuntu 26.04 LTS 7.0.0-42.42.1
- linux-oracle Ubuntu 26.04 LTS 7.0.0-1015.16
- linux-hwe-7.0 Ubuntu 24.04 LTS 7.0.0-42.42~24.04.1
- linux-oem-7.0 Ubuntu 26.04 LTS 7.0.0-1017.17
ubuntu advisories UBUNTU-CVE-2026-74747
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
- git.kernel.org/stable/c/f55bb94946fb8ee6304590a731c39c1fbc3b28bc commit
- git.kernel.org/stable/c/2512289cbf58706fd558e8fccea4e28003a2af54 commit
- git.kernel.org/stable/c/041b2303c8019394735c1f76c5138657bf660a7d commit
- git.kernel.org/stable/c/eb81c8e758f49e04391f77d9470a6232bb5f1c7a commit
- git.kernel.org/stable/c/5365f012451fce2453f13a568dcb72ea534c1e4d commit
- git.kernel.org/stable/c/d93660df4dd1d116f608ada4a29a80a5d6f0a6ed commit
Vendor 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-74747 updated cvss 5.5
kernel: ipvs: revalidate ihl to prevent out-of-bounds access
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 moreaffected: workaround, no fix planned “Out of support scope”
-
Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more 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 Enterprise Linux 10 kernelaffected: workaround, no fix available “Fix deferred”
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
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 23 d ago
Exploit prediction
0.14% chance of exploitation in the next 30 days, higher than 3% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/f55bb94946fb8ee6304590a731c39c1fbc3b28bc
- git.kernel.org /stable/c/2512289cbf58706fd558e8fccea4e28003a2af54
- git.kernel.org /stable/c/041b2303c8019394735c1f76c5138657bf660a7d
- git.kernel.org /stable/c/eb81c8e758f49e04391f77d9470a6232bb5f1c7a
- git.kernel.org /stable/c/5365f012451fce2453f13a568dcb72ea534c1e4d
- git.kernel.org /stable/c/d93660df4dd1d116f608ada4a29a80a5d6f0a6ed
Sources
- CVE List CVE-2026-74747
- NVD CVE-2026-74747
Fencer Vulns 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.