A vulnerability in the Linux kernel ALSA mts64 driver allows out-of-bounds (OOB) access due to missing validation of negative card index values during probe. This flaw occurs because the driver does not properly check for negative device IDs, which can be passed as 'none' or similar values via sysfs, potentially leading to memory access errors.
A vulnerability in the ALSA portman2x4 driver in the Linux kernel allows out-of-bounds (OOB) access due to improper validation of the card index during probe. The driver fails to check for negative card index values, which can be assigned as 'none' or similar via sysfs, potentially leading to invalid memory access. A fix has been implemented to add a sanity check for the card index and to warn or correct out-of-range values.
A vulnerability in the Linux kernel ALSA serial-u16550 driver allows out-of-bounds (OOB) access due to improper validation of the card index during device probe. The driver trusts the devptr->id value without checking if it is within the valid range, which can lead to OOB access when devices are manually bound via sysfs with an invalid index such as -1. A fix was introduced to add sanity checks for the card index and correct or warn about invalid values.
A vulnerability in the Linux kernel ALSA virmidi driver allows out-of-bounds (OOB) access due to improper validation of the card index during device probing. The driver blindly trusts the devptr->id value, which can be -1 when a device is manually bound via sysfs, leading to OOB access of internal arrays. A fix was introduced to add sanity checks and warnings for invalid card index values.
In the Linux kernel, the following vulnerability has been resolved: ALSA: aloop: Check card index validity at probe aloop driver blindly trusts that the given devptr->id value is within the proper card index range at probe. It's OK for the devices the driver itself creates at the module probe time, but if the device is bound manually via sysfs interface, this could be -1 as "none", and this leads to OOB access for index[] and other parameters. Add a sanity check for the card index and warn/correct it if it's a value out of the range.
In the Linux kernel, the following vulnerability has been resolved: seg6: reset IP6CB after IPv6 decapsulation decap_and_validate() pulls the outer SRv6 headers and makes the inner packet the skb network header. The IPv6 control block still contains values collected while parsing the outer packet, including nhoff and extension-header flags. End.DX6 and End.DT6 route the inner IPv6 packet directly to the IPv6 input path. An unprivileged user can reach End.DT6 from a user and net namespace by installing a local SID and injecting an outer packet with Hop-by-Hop and Destination Options headers followed by an SRH and a minimal inner IPv6 packet. The outer extension headers leave a large nhoff in IP6CB. After decapsulation, ip6_protocol_deliver_rcu() uses that stale offset on the inner packet and reads beyond the skb head. KASAN reports: BUG: KASAN: slab-out-of-bounds in ip6_protocol_deliver_rcu ip6_protocol_deliver_rcu+0x1118/0x1450 ip6_input_finish+0x11b/0x240 seg6_local_input_core+0xed/0x2e0 lwtunnel_input+0x1e9/0x4e0 ipv6_rthdr_rcv+0x525f/0x6c50 ip6_protocol_deliver_rcu+0xcb7/0x1450 Before clearing IP6CB for an inner IPv6 packet, save its incoming interface index and L3 slave state. Restore both after the clear and set nhoff to the inner IPv6 base-header nexthdr field. Use IP6CB(skb)->iif rather than skb->skb_iif because VRF processing can replace skb_iif with the L3 master while IP6CB keeps the receiving interface. Preserve IP6SKB_L3SLAVE for the same reason.
In the Linux kernel, the following vulnerability has been resolved: ALSA: mpu401: Check card index validity at probe mpu401 driver blindly trusts that the given devptr->id value is within the proper card index range at probe. It's OK for the devices the driver itself creates at the module probe time, but if the device is bound manually via sysfs interface, this could be -1 as "none", and this leads to OOB access for index[] and other parameters. Add a sanity check for the card index and warn/correct it if it's a value out of the range.
In the Linux kernel, the following vulnerability has been resolved: net: ravb: avoid dereferencing an invalid PTP clock The PTP clock is unavailable before the first open, so querying its index can dereference a NULL pointer. Registration failures can also leave an error pointer in priv->ptp.clock. Cache the PHC index separately and report -1 while no clock is registered. Normalize registration errors to NULL and preserve the static timestamping capabilities.
In the Linux kernel, the following vulnerability has been resolved: platform/chrome: sensorhub: Bound the EC-reported sensor number Each EC FIFO event carries an 8-bit sensor number (in->sensor_num). cros_ec_sensorhub_ring_handler() validates the FIFO event count, the per-read count and the ring bound, but not the sensor number, which cros_ec_sensor_ring_process_event() then uses unchecked to index sensorhub->batch_state[] - allocated with only sensorhub->sensor_num entries. A sensor number of sensor_num or larger is an out-of-bounds read and write of batch_state[]. Validate the sensor number in the ring handler, where each event is read from the EC, and drop a malformed event before it is used.
In the Linux kernel, the following vulnerability has been resolved: platform/x86: ISST: Validate level in perf mask ioctls isst_if_get_perf_level_mask() and isst_if_get_base_freq_mask() use the user-provided level as an index into perf_levels[] via _read_pp_level_info() and _read_bf_level_info(), but neither helper validates it first. The adjacent level-info helpers reject levels above max_level before reading the same per-level register block. Add the same bounds checks to the mask helpers, and reject disabled SST-PP levels in isst_if_get_perf_level_mask() to match isst_if_get_perf_level_info(). This prevents out-of-bounds reads from the per-level offset table on invalid ioctl input.
In the Linux kernel, the following vulnerability has been resolved: platform/x86: ISST: Validate socket ID in clos_assoc ioctl isst_if_clos_assoc() validates the user-supplied socket_id with 'socket_id > topology_max_packages()', but isst_common.sst_inst[] is allocated with topology_max_packages() entries, so the valid index range is [0, topology_max_packages()). The '>' comparison lets socket_id == topology_max_packages() pass and index one entry past the array. In addition, isst_common.sst_inst[socket_id] is NULL for an in-range package that has no bound TPMI SST instance, and the pointer is used without a NULL check. Both the out-of-bounds entry and the NULL pointer are then dereferenced by map_partition_power_domain_id() and the following power_domain_info access. Reject socket_id >= topology_max_packages() and a NULL sst_inst, matching the checks already performed by get_instance().
A vulnerability in the Linux kernel's UDF filesystem implementation allows an out-of-bounds read due to improper bounds checking of VAT indexes. The issue arises because the code incorrectly permits an index equal to the number of entries, leading to a read past the allocated VAT table. This can cause a kernel panic or memory corruption. The flaw affects specific Linux kernel versions listed and was demonstrated with a reproducer causing a KASAN slab-out-of-bounds error.
A vulnerability in the Linux kernel's NTFS3 filesystem driver allows an out-of-bounds write due to improper bounds checking in the handling of page_lcns[] indices. The flaw arises because the copy_lcns loop and redo shorten loop index page_lcns[] using values from a crafted log record that are only checked against the record's length, not the target entry's length. This can lead to an overflow of the page_lcns[] array. The issue has been fixed by adding additional validation to reject records whose runs do not fit the entry, ensuring all accesses are properly bounded.
A high-severity vulnerability in the Linux kernel's rtlwifi driver (rtl8192du) allows out-of-bounds array indexing due to improper validation of QoS TID values. The flaw occurs because the driver uses a QoS TID value (0..15) as an index into an array with only 9 entries, potentially leading to memory corruption. This issue has been fixed by adding proper bounds checking before indexing.
CVE-2026-89492 is a critical vulnerability in the Linux kernel's ocfs2 filesystem. It involves improper validation of directory-index entry counts when reading metadata, allowing an out-of-bounds read of slab memory. This occurs because the code does not properly bound the number of entries it processes against the block capacity, enabling a crafted on-disk image to trigger the flaw during directory operations such as path lookup, stat(), or open(). The issue has been fixed by adding validation checks that reject corrupted metadata before out-of-range reads occur.