A vulnerability in the Linux kernel's MACsec driver was resolved by initializing the SecY component before registering the network device. The issue caused warnings and potential reporting of uninitialized SecY attributes during device registration, particularly when MAC offload was used over an LRO-capable lower device with IPv4 forwarding enabled. The fix involves reordering initialization steps to ensure SecY and related attributes are properly set before notifications are emitted.
A vulnerability in the Linux kernel's filesystem code caused hung tasks when unmounting filesystems after disk removal. The issue stemmed from repeated scans of inodes during eviction, which could block unmount operations and trigger hung-task reports. A patch was applied to change the inode eviction process to avoid repeated scanning and ensure proper inode disposal without blocking. Testing confirmed the fix resolves the issue without introducing regressions.
A vulnerability in the Linux kernel's ASoC qcom lpass-cpu driver was resolved. The issue involved incorrect indexing of the DAI driver table when configuring certain hardware ports, leading to out-of-bounds memory access. This was due to using the hardware port ID as an index instead of the correct loop index. The fix uses the loop index to update playback channel constraints, preventing incorrect memory writes.
A NULL pointer dereference vulnerability in the Linux kernel's SPI-NAND driver was fixed. The issue occurs when the device tree sets "nand-no-ecc-engine", causing the ECC engine pointer to remain NULL while the code dereferences it unconditionally, leading to a kernel oops during device probing. The fix introduces a helper function to safely check the ECC engine pointer before use.
A vulnerability in the Linux kernel's KVM s390 subsystem related to IRQ injection with SIGP Stop and Store Status has been resolved. The issue involved storing status information while holding a spinlock, which could cause faults due to writing into userspace. The fix changes the behavior to defer the status storage outside the spinlock context, preventing potential faults.
A vulnerability in the Linux kernel ext4 filesystem allows a crash due to a NULL pointer dereference when large folios are enabled on encrypted inodes. This occurs because enabling the encrypt feature on a mounted filesystem bypasses a check that disables large folios, leading to a kernel crash during encrypted data writes. The issue affects Linux kernel versions from 6.19 up to but not including 7.3, where the code was refactored to prevent this. The vulnerability has been resolved by disabling large folios on encrypted inodes, similar to the handling of inodes using data journaling.
A vulnerability in the Linux kernel's AMD display driver (drm/amd/display) related to improper handling of the optional stream->sink pointer in DPMS sequences has been resolved. The issue involved dereferencing a potentially null pointer without proper checks, which could lead to inconsistencies or errors. The fix replaces usage of stream->sink->link with stream->link, adds assertions where sink is required, and improves resource access consistency.
A vulnerability in the Linux kernel's RTC driver was resolved by zero-initializing the struct rtc_wkalrm to prevent information leakage. The issue involved uninitialized kernel stack data in padding holes of the struct being exposed to userspace via the RTC_WKALRM_RD ioctl call. This could lead to unintended disclosure of kernel memory contents. The vulnerability has been fixed by initializing the struct at declaration, eliminating the risk of leaking sensitive information.
A vulnerability in the Linux kernel arm64 io subsystem related to ioremap_prot() was resolved. The issue involved improper handling of non-user protection flags in memory mappings, causing spurious warnings when reading process cmdline via /proc. The fix ensures ioremap_prot() rejects protection values without PTE_USER, preventing invalid warnings and cleanly failing access for PROT_NONE and execute-only mappings.
A vulnerability in the Linux kernel's BPF sockmap implementation caused double-counting of the copied_seq TCP sequence number during self-redirects of packets back to the same socket. This led to warnings and potential TCP receive buffer inconsistencies. The issue was fixed by changing the handling of self-redirect verdicts to avoid double advancement of copied_seq.
A vulnerability in the Linux kernel's ath11k WiFi driver was resolved by ensuring the 'num_stations' counter is reset properly on hardware restart. Without this fix, multiple hardware restarts could cause the driver to refuse new station or mesh peer associations, leading to connectivity issues and kernel warnings.
A vulnerability in the Linux kernel's KVM module for arm64 architecture related to the handling of the Scalable Vector Extension (SVE) feature bit at EL2 has been resolved. The issue involved inconsistent derivation and use of the GUEST_HAS_SVE flag, which could lead to a virtual CPU (vCPU) having a NULL SVE state. This inconsistency arose because the flag was taken separately from the host, but the actual feature bit was tested differently, potentially causing improper SVE state loading in guests. The fix derives the GUEST_HAS_SVE flag directly from the SVE feature bit and removes redundant code related to protected VMs, which do not allow SVE.
A vulnerability in the Linux kernel's emac network driver caused a kernel crash due to a NULL pointer dereference during driver initialization. The issue was triggered because netdev_ops were not set before calling of_phy_connect(), leading to a crash on certain PowerPC platforms. The fix involved moving the setting of netdev_ops earlier in the initialization sequence to prevent the crash. This bug appeared starting with kernel version 7.3-rc1 and was resolved by adjusting the initialization order in the emac driver code.
A vulnerability in the Linux kernel related to the HID steam driver has been resolved. The issue involved improper locking behavior, specifically that RCU (Read-Copy-Update) accesses were not properly guarded behind locks. This fix cleans up several locking issues to improve kernel stability and security.
A vulnerability in the Linux kernel scheduler extension (sched_ext) was resolved by changing how cid tables are built and published. Previously, cid tables were visible while being modified, allowing race conditions that could expose uninitialized memory or torn updates to tracing or syscall programs. The fix involves building cid tables privately and publishing them only when fully constructed, ensuring readers always see consistent and valid data. Additionally, the fix includes proper synchronization and NULL checks to prevent stale or invalid reads.
A vulnerability in the Linux kernel related to the parisc architecture has been resolved by increasing the kernel stack size to 32 KB for 64-bit kernels. This change addresses kernel crashes caused by kernel stack overflows, which were observed during specific workloads such as building the Debian vtk9 package with gcc 17. The issue manifested as kernel panics triggered by low stack detection in interrupt handlers.
A vulnerability in the Linux kernel's DAMON subsystem was resolved involving the use of an unaligned address in damon_ptep_mkold(). This caused an out-of-bounds write during page table walks on arm64 architectures, potentially corrupting adjacent memory or causing kernel crashes. The issue was triggered by the kernel selftest suite and could lead to kernel faults or silent memory corruption depending on the memory page permissions. The fix ensures a page-aligned address is used in the affected function, preventing the out-of-bounds access.
A use-after-free (UAF) vulnerability in the Linux kernel's overlay filesystem (ovl) was fixed in the ovl_do_mkdir() function. The issue occurs because ovl_do_mkdir() prints the input dentry after calling vfs_mkdir(), which may free or replace the dentry, leading to a UAF when CONFIG_OVERLAY_FS_DEBUG is enabled. The fix involves printing the dentry before the call and only printing the result afterward.
A vulnerability in the Linux kernel's netfs subsystem related to missing allocation tagging of direct mempool allocations has been resolved. The issue caused warnings and missing allocation tags when CONFIG_MEM_ALLOC_PROFILING_DEBUG was enabled, affecting memory allocation tracking during CIFS mount operations. The fix involves wrapping direct allocation calls with proper allocation tagging hooks to ensure correct profiling and avoid warnings.
A vulnerability in the Linux kernel's drm/xe component related to the adjust_idledly() function has been resolved. The function had multiple issues including a divide-by-zero error when an unrecognized crystal clock caused a zero timestamp base, and integer overflow problems in tick-to-nanosecond conversions. These issues could cause kernel panics or repeated warnings during initialization. The fix involves early returns to avoid divide-by-zero, using 64-bit arithmetic to prevent overflow, and careful clamping of delay values to avoid invalid programming of hardware registers.