28 matches found
EUVD-2026-71506
In the Linux kernel, the following vulnerability has been resolved: ring-buffer: Fix event length with forced 8-byte alignment When RBFORCE8BYTEALIGNMENT is true, rbcalculateeventlength reserves the space of event-array0 for placing the data length and rbupdateevent stores the data length in...
CVE-2026-80876 ring-buffer: Fix event length with forced 8-byte alignment
In the Linux kernel, the following vulnerability has been resolved: ring-buffer: Fix event length with forced 8-byte alignment When RBFORCE8BYTEALIGNMENT is true, rbcalculateeventlength reserves the space of event-array0 for placing the data length and rbupdateevent stores the data length in...
CVE-2026-80876
In the Linux kernel, the following vulnerability has been resolved: ring-buffer: Fix event length with forced 8-byte alignment When RBFORCE8BYTEALIGNMENT is true, rbcalculateeventlength reserves the space of event-array0 for placing the data length and rbupdateevent stores the data length in...
CVE-2026-80876
CVE-2026-80876 affects the Linux kernel ring-buffer subsystem on architectures where RB_FORCE_8BYTE_ALIGNMENT is true (observed on riscv64 with CONFIG_HAVE_64BIT_ALIGNED_ACCESS=y). The root cause is a mismatch in length calculation: rb_calculate_event_length() unconditionally reserves sizeof(even...
Astra Linux – Vulnerabilities in Linux 5.10, Linux 5.15
In the Linux kernel, the following vulnerability has been resolved: ubifswbufwritenolock: A read out-of-bounds issue exists in this function. This issue occurs when ubifswbufwritenolock attempts to access memory beyond the allocated bounds of the buffer buf. Here’s an example of how this issue...
Astra Linux – Vulnerability in Linux 5.10
In the Linux kernel, the following vulnerability has been resolved: “hungtask”: fixed warnings caused by unaligned lock pointers. The blocker tracking mechanism assumes that lock pointers are at least 4-byte aligned, so that their lower bits can be used for type encoding. However, as reported by...
OESA-2026-2234 kernel security update
The Linux Kernel, the operating system core itself. Security Fixes: In the Linux kernel, the following vulnerability has been resolved: bpf, arm64: Force 8-byte alignment for JIT buffer to prevent atomic tearing struct bpfplt contains a u64 target field. Currently, the BPF JIT allocator requests ...
SUSE CVE-2026-23383
In the Linux kernel, the following vulnerability has been resolved: bpf, arm64: Force 8-byte alignment for JIT buffer to prevent atomic tearing struct bpfplt contains a u64 target field. Currently, the BPF JIT allocator requests an alignment of 4 bytes sizeofu32 for the JIT buffer. Because the ba...
CVE-2026-23383
In the Linux kernel, the following vulnerability has been resolved: bpf, arm64: Force 8-byte alignment for JIT buffer to prevent atomic tearing struct bpfplt contains a u64 target field. Currently, the BPF JIT allocator requests an alignment of 4 bytes sizeofu32 for the JIT buffer. Because the ba...
UBUNTU-CVE-2026-23383
In the Linux kernel, the following vulnerability has been resolved: bpf, arm64: Force 8-byte alignment for JIT buffer to prevent atomic tearing struct bpfplt contains a u64 target field. Currently, the BPF JIT allocator requests an alignment of 4 bytes sizeofu32 for the JIT buffer. Because the ba...
CVE-2026-23383 bpf, arm64: Force 8-byte alignment for JIT buffer to prevent atomic tearing
In the Linux kernel, the following vulnerability has been resolved: bpf, arm64: Force 8-byte alignment for JIT buffer to prevent atomic tearing struct bpfplt contains a u64 target field. Currently, the BPF JIT allocator requests an alignment of 4 bytes sizeofu32 for the JIT buffer. Because the ba...
CVE-2026-23383
In the Linux kernel, the following vulnerability has been resolved: bpf, arm64: Force 8-byte alignment for JIT buffer to prevent atomic tearing struct bpfplt contains a u64 target field. Currently, the BPF JIT allocator requests an alignment of 4 bytes sizeofu32 for the JIT buffer. Because the ba...
PT-2026-27748
Name of the Vulnerable Software and Affected Versions Linux kernel affected versions not specified Description The Linux kernel contains a flaw related to the BPF JIT allocator. The allocator requests 4-byte alignment for the JIT buffer, but the bpf plt structure contains a 64-bit u64 target fiel...
EUVD-2025-203646
In the Linux kernel, the following vulnerability has been resolved: hungtask: fix warnings caused by unaligned lock pointers The blocker tracking mechanism assumes that lock pointers are at least 4-byte aligned to use their lower bits for type encoding. However, as reported by Eero Tamminen, some...
CVE-2025-68250
In the Linux kernel, the following vulnerability has been resolved: hungtask: fix warnings caused by unaligned lock pointers The blocker tracking mechanism assumes that lock pointers are at least 4-byte aligned to use their lower bits for type encoding. However, as reported by Eero Tamminen, some...
UBUNTU-CVE-2025-68250
In the Linux kernel, the following vulnerability has been resolved: hungtask: fix warnings caused by unaligned lock pointers The blocker tracking mechanism assumes that lock pointers are at least 4-byte aligned to use their lower bits for type encoding. However, as reported by Eero Tamminen, some...
CVE-2025-68250 hung_task: fix warnings caused by unaligned lock pointers
In the Linux kernel, the following vulnerability has been resolved: hungtask: fix warnings caused by unaligned lock pointers The blocker tracking mechanism assumes that lock pointers are at least 4-byte aligned to use their lower bits for type encoding. However, as reported by Eero Tamminen, some...
CVE-2025-68250 hung_task: fix warnings caused by unaligned lock pointers
In the Linux kernel, the following vulnerability has been resolved: hungtask: fix warnings caused by unaligned lock pointers The blocker tracking mechanism assumes that lock pointers are at least 4-byte aligned to use their lower bits for type encoding. However, as reported by Eero Tamminen, some...
CVE-2025-68250
CVE-2025-68250 affects the Linux kernel. The issue arises from an assumption that lock pointers are 4-byte aligned to use lower bits for type encoding, which fails on architectures with only 2-byte alignment (e.g., m68k). This causes two WARN_ON_ONCE checks to trigger in the hung_task blocker log...