Release bpftool-4.18.0-553.181.1.el8_10 ALSA-2026:93436

Cerrado
  • ¿Algo no está bien?
#4,078 211 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
5/100
Tipo de issue
Error
Claridad
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
linux
Área
operating-systems, security

Línea de trabajo

This is a release announcement for kernel security updates, not a task with a defined change. It lists CVE-referenced kernel fixes and affected package builds, but names no file, test or entry point to change. It is not a starting point for a first contribution; work on it belongs with the AlmaLinux maintainers and the upstream kernel CVE pages.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

kernel security update
Severity: Important
Description
The kernel packages contain the Linux kernel, the core of any Linux operating system.

Security Fix(es):

  • kernel: ipv6: exthdrs: refresh nh pointer after ipv6_hop_jumbo() (CVE-2026-63924)
  • kernel: ipv6: exthdrs: refresh nh after handling HAO option (CVE-2026-63922)
  • kernel: af_unix: Fix UAF read of tail->len in unix_stream_data_wait() (CVE-2026-64109)
  • kernel: scsi: target: core: Fix iSCSI ISID use-after-free in REGISTER AND MOVE (CVE-2026-72083)
  • kernel: tipc: require net admin for TIPCv2 netlink mutators (CVE-2026-74283)
  • kernel: smb: client: bound dirent name against end of SMB response in cifs_filldir (CVE-2026-93787)
  • kernel: ZDI-CAN-33367: Linux Kernel skbuff skb_zerocopy Improper Ownership Management Local Privilege Escalation Vulnerability ()

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 packages:
bpftool-4.18.0-553.181.1.el8_10.x86_64
kernel-4.18.0-553.181.1.el8_10.x86_64
kernel-abi-stablelists-4.18.0-553.181.1.el8_10.noarch
kernel-core-4.18.0-553.181.1.el8_10.x86_64
kernel-cross-headers-4.18.0-553.181.1.el8_10.x86_64
kernel-debug-4.18.0-553.181.1.el8_10.x86_64
kernel-debug-core-4.18.0-553.181.1.el8_10.x86_64
kernel-debug-devel-4.18.0-553.181.1.el8_10.x86_64
kernel-debug-modules-4.18.0-553.181.1.el8_10.x86_64
kernel-debug-modules-extra-4.18.0-553.181.1.el8_10.x86_64
kernel-devel-4.18.0-553.181.1.el8_10.x86_64
kernel-doc-4.18.0-553.181.1.el8_10.noarch
kernel-headers-4.18.0-553.181.1.el8_10.x86_64
kernel-modules-4.18.0-553.181.1.el8_10.x86_64
kernel-modules-extra-4.18.0-553.181.1.el8_10.x86_64
kernel-tools-4.18.0-553.181.1.el8_10.x86_64
kernel-tools-libs-4.18.0-553.181.1.el8_10.x86_64
perf-4.18.0-553.181.1.el8_10.x86_64
python3-perf-4.18.0-553.181.1.el8_10.x86_64
bpftool-4.18.0-553.181.1.el8_10.s390x
kernel-4.18.0-553.181.1.el8_10.s390x
kernel-abi-stablelists-4.18.0-553.181.1.el8_10.noarch
kernel-core-4.18.0-553.181.1.el8_10.s390x
kernel-cross-headers-4.18.0-553.181.1.el8_10.s390x
kernel-debug-4.18.0-553.181.1.el8_10.s390x
kernel-debug-core-4.18.0-553.181.1.el8_10.s390x
kernel-debug-devel-4.18.0-553.181.1.el8_10.s390x
kernel-debug-modules-4.18.0-553.181.1.el8_10.s390x
kernel-debug-modules-extra-4.18.0-553.181.1.el8_10.s390x
kernel-devel-4.18.0-553.181.1.el8_10.s390x
kernel-doc-4.18.0-553.181.1.el8_10.noarch
kernel-headers-4.18.0-553.181.1.el8_10.s390x
kernel-modules-4.18.0-553.181.1.el8_10.s390x
kernel-modules-extra-4.18.0-553.181.1.el8_10.s390x
kernel-tools-4.18.0-553.181.1.el8_10.s390x
kernel-zfcpdump-4.18.0-553.181.1.el8_10.s390x
kernel-zfcpdump-core-4.18.0-553.181.1.el8_10.s390x
kernel-zfcpdump-devel-4.18.0-553.181.1.el8_10.s390x
kernel-zfcpdump-modules-4.18.0-553.181.1.el8_10.s390x
kernel-zfcpdump-modules-extra-4.18.0-553.181.1.el8_10.s390x
perf-4.18.0-553.181.1.el8_10.s390x
python3-perf-4.18.0-553.181.1.el8_10.s390x
bpftool-4.18.0-553.181.1.el8_10.ppc64le
kernel-4.18.0-553.181.1.el8_10.ppc64le
kernel-abi-stablelists-4.18.0-553.181.1.el8_10.noarch
kernel-core-4.18.0-553.181.1.el8_10.ppc64le
kernel-cross-headers-4.18.0-553.181.1.el8_10.ppc64le
kernel-debug-4.18.0-553.181.1.el8_10.ppc64le
kernel-debug-core-4.18.0-553.181.1.el8_10.ppc64le
kernel-debug-devel-4.18.0-553.181.1.el8_10.ppc64le
kernel-debug-modules-4.18.0-553.181.1.el8_10.ppc64le
kernel-debug-modules-extra-4.18.0-553.181.1.el8_10.ppc64le
kernel-devel-4.18.0-553.181.1.el8_10.ppc64le
kernel-doc-4.18.0-553.181.1.el8_10.noarch
kernel-headers-4.18.0-553.181.1.el8_10.ppc64le
kernel-modules-4.18.0-553.181.1.el8_10.ppc64le
kernel-modules-extra-4.18.0-553.181.1.el8_10.ppc64le
kernel-tools-4.18.0-553.181.1.el8_10.ppc64le
kernel-tools-libs-4.18.0-553.181.1.el8_10.ppc64le
perf-4.18.0-553.181.1.el8_10.ppc64le
python3-perf-4.18.0-553.181.1.el8_10.ppc64le
bpftool-4.18.0-553.181.1.el8_10.aarch64
kernel-4.18.0-553.181.1.el8_10.aarch64
kernel-abi-stablelists-4.18.0-553.181.1.el8_10.noarch
kernel-core-4.18.0-553.181.1.el8_10.aarch64
kernel-cross-headers-4.18.0-553.181.1.el8_10.aarch64
kernel-debug-4.18.0-553.181.1.el8_10.aarch64
kernel-debug-core-4.18.0-553.181.1.el8_10.aarch64
kernel-debug-devel-4.18.0-553.181.1.el8_10.aarch64
kernel-debug-modules-4.18.0-553.181.1.el8_10.aarch64
kernel-debug-modules-extra-4.18.0-553.181.1.el8_10.aarch64
kernel-devel-4.18.0-553.181.1.el8_10.aarch64
kernel-doc-4.18.0-553.181.1.el8_10.noarch
kernel-headers-4.18.0-553.181.1.el8_10.aarch64
kernel-modules-4.18.0-553.181.1.el8_10.aarch64
kernel-modules-extra-4.18.0-553.181.1.el8_10.aarch64
kernel-tools-4.18.0-553.181.1.el8_10.aarch64
kernel-tools-libs-4.18.0-553.181.1.el8_10.aarch64
perf-4.18.0-553.181.1.el8_10.aarch64
python3-perf-4.18.0-553.181.1.el8_10.aarch64
kernel-tools-libs-devel-4.18.0-553.181.1.el8_10.x86_64
kernel-tools-libs-devel-4.18.0-553.181.1.el8_10.ppc64le
kernel-tools-libs-devel-4.18.0-553.181.1.el8_10.aarch64

Lenguaje dominante
Sin datos de lenguaje
Estrellas
2
Forks
0
Sin PR fusionados en 30 d

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de AlmaLinux/updates

Todos los issues de AlmaLinux/updates

Issues similares

Más issues de Operating Systems

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.