RLSA-2026:98597: Important: oci-seccomp-bpf-hook security update
OCI Hook to generate seccomp json files based on EBF syscalls used by container oci-seccomp-bpf-hook provides a library for applications looking to use the Container Pod concept popularized by Kubernetes.
Security Fix(es):
net/http: golang: Go net/http: Unencrypted HTTP/2 connections vulnerable to Denial of Service (CVE-2026-56853)
net/http: golang: golang: Denial of Service via crafted HTTP Range headers (CVE-2026-78667)
crypto/tls: golang: crypto/tls: Denial of Service via multiple ECH outer extension references (CVE-2026-97031)
net/textproto: mime/multipart: golang: golang: Denial of Service via memory limit bypass in multipart form parsing (CVE-2026-94440)
For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
rocky-linux/oci-seccomp-bpf-hook-debugsourceto a version that resolves this vulnerability.Fixed in 0:1.3.0-3.el10_3 - Upgrade
Upgrade
rocky-linux/oci-seccomp-bpf-hook-debuginfoto a version that resolves this vulnerability.Fixed in 0:1.3.0-3.el10_3 - Upgrade
Upgrade
rocky-linux/oci-seccomp-bpf-hookto a version that resolves this vulnerability.Fixed in 0:1.3.0-3.el10_3
Event History
Child vulnerabilities
Contains the following vulnerabilities.
Frequently Asked Questions
Which deployed components are affected by this update?
The advisory lists the Rocky Linux oci-seccomp-bpf-hook package and its debuginfo and debugsource packages. The described fixes are in Go standard-library components used by the software, including net/http, crypto/tls, and net/textproto multipart parsing.
What access does an attacker need to exploit the reported issues?
The provided CVSS vector indicates network reachability, low attack complexity, no privileges required, and no user interaction required. It also indicates the reported impact is denial of service, with no stated confidentiality or integrity impact.
Are systems using unencrypted HTTP/2, HTTP Range requests, TLS ECH, or multipart form parsing relevant?
Yes. The listed fixes specifically cover denial-of-service conditions involving unencrypted HTTP/2 connections, crafted HTTP Range headers, multiple ECH outer-extension references, and a multipart form-parsing memory-limit bypass. The advisory does not state which of these code paths are enabled or exposed in a particular deployment.