Threats Tagged 'cve-2026-68388'

A security advisory from Red Hat addresses multiple vulnerabilities and bugs in the Linux kernel packages for Red Hat Enterprise Linux 8. The update includes fixes for several security issues such as dangling pointers, race conditions, memory counter updates, CRC overreads, double-free errors, and improper handling of allocated ranges. The advisory also includes bug fixes and enhancements related to network interface controller stalls and resets. The update is rated as important by Red Hat and requires a system reboot to take effect.

This Red Hat security advisory addresses multiple vulnerabilities and bugs in the kernel-rt packages, which provide the Real Time Linux Kernel for systems requiring high determinism. The update fixes several security issues including dangling pointer, race conditions, memory counter updates, CRC overread, double-free errors, and improper handling of server-provided modes. The advisory also includes bug fixes and enhancements related to network interface controller stalls and resets. The update is rated as important by Red Hat and requires a system reboot to take effect.

This security update provides a functional equivalent of RHSA-2026:57252. The original Red Hat(R) advisory is available from the Red Hat web site at https://access.redhat.com/errata/RHSA-2026:57252.

In the Linux kernel, the following vulnerability has been resolved: smb/client: handle overlapping allocated ranges in fallocate smb3_simple_fallocate_range() can skip holes when an allocated range returned by the server starts before the current fallocate offset. The skipped hole is not zero-filled, but fallocate still returns success. A later write to that hole may therefore fail with ENOSPC. The function queries allocated ranges so that it can preserve existing contents and write zeroes only into holes. However, the server may return a range that starts before the current fallocate offset. For example, assume the fallocate request is [100, 400) and the only allocated range returned by the server is [0, 200): Request: [100, 400) Server range: [ 0, 200) allocated Correct: [100, 200) allocated data, skip [200, 400) hole, zero-fill Current: [100, 300) skipped [300, 400) zero-filled afterwards The current code adds the full server range length, 200, to the current offset 100 and moves to 300. As a result, the hole in [200, 300) is skipped without being zero-filled. Fix this by advancing only over the part of the allocated range that overlaps the current fallocate offset. Ignore ranges that end before the current offset and reject ranges whose end offset overflows. This also prevents a malformed range length from causing an out-of-bounds zero-buffer read.