A vulnerability in the Linux kernel's network stack related to the handling of Generic Segmentation Offload (GSO) packets in the __virtio_net_hdr_to_skb() function has been resolved. The issue involved improper flow dissection of GSO packets when skb->network_header was zero, leading to potential out-of-bounds reads in TCP header processing. This could occur with malformed network headers or packets carrying IP options or IPv6 extension headers. The fix involves proper initialization of skb fields and ensuring all GSO packets are fully dissected and validated.
A vulnerability in the Linux kernel's riscv ptrace implementation was resolved by zero-initializing regset buffers before copying user data. The flaw involved uninitialized stack buffer data when a PTRACE_SETREGSET request provided a short iov_len, potentially causing garbage data to be copied into the target's vstate or shadow stack pointer.
A vulnerability in the Linux kernel's flow_dissector component was resolved to prevent u16 truncation of the hlen parameter in the bpf_flow_dissect() function. The issue caused offsets to be incorrectly clamped when hlen exceeded 65535, potentially forcing offset values to zero even if valid. This bug is similar to a previously fixed truncation issue but affected the BPF path specifically. The fix involves capping hlen to the maximum value of a 16-bit unsigned integer before clamping. The vulnerability was discovered during code review and has been addressed.
A resource leak vulnerability in the Linux kernel's mlxsw spectrum_flower component was fixed. The flaw involved port range registers acquired during flow template parsing that were not properly released, leading to a resource leak. The fix ensures that these registers are released correctly to prevent the leak.
A memory leak vulnerability in the Linux kernel's vsock component was fixed in the function vmci_transport_recv_dgram_cb(). The leak occurs during the closure of a datagram socket when packets are moved between the socket's backlog and receive queue improperly, leading to unreleased memory. The fix involves adding a receive queue cleanup in the socket destructor.
A vulnerability in the Linux kernel's drm/vc4 driver was resolved by disabling the V3D interrupt across runtime suspend transitions. The issue involved the interrupt handler potentially running after the power domain was off, causing spurious interrupts and unexpected behavior due to the ARMCTRL interrupt controller lacking an active state. This could lead to scheduling of overflow memory work after the interrupt was disabled.
A vulnerability in the Linux kernel's HID steam driver has been fixed by rearranging the teardown sequence. The issue involved a narrow timing window during cleanup where callbacks could be scheduled referencing a freed steam struct, leading to potential use-after-free conditions. The fix also ensures that work canceling for rumble and mode switch occurs properly during steam device unregistration.
A vulnerability in the Linux kernel related to the HID steam driver has been resolved. The issue involved improper handling of registration and unregistration flows, which could leave a lingering power_supply object after the steam object was torn down. The fix refactors the registration logic, removing assumptions about serial numbers and correcting the omission of unregistering the battery when registration steps fail.
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'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 vulnerability in the Linux kernel's perf subsystem allowed users with kernel profiling privileges to bypass intended permission checks when requesting kernel callchain data. The flaw was due to an incomplete permission check that did not enforce kernel profiling privilege for kernel callchain collection when kernel sampling was excluded. This issue has been resolved by updating the permission checks to properly gate kernel callchain requests, preventing unprivileged access.
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 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 IPv6 segment routing code (seg6_make_flowlabel) was resolved by using skb_get_hash_net() to properly obtain a network pointer. The issue arose when seg6_make_flowlabel() was called with an skb lacking both skb->dev and skb->sk pointers, which could occur in specific network scenarios involving TIPC UDP bearers and IPv4 routes with seg6 encapsulation enabled. This was fixed by ensuring the function uses skb_get_hash_net() to retrieve the network namespace pointer correctly.
A use-after-free vulnerability in the Linux kernel's EDAC altera driver was fixed. The issue occurred in error paths of altr_edac_a10_device_add() and altr_portb_setup() where a dci structure was freed before unregistering IRQ handlers, potentially allowing IRQs to access freed memory.
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'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 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.