CVE Vulnerability Catalog

In the Linux kernel, IP tunnel devices derive their advertised needed_headroom from lower output devices. A stack of user-created devices can make the derived value exceed the range representable by 16-bit skb header offsets, so once IP output reserves it, skb head expansion can wrap those offsets.

In the Linux kernel, skb_tx_error() completes the zerocopy uarg and clears SKBFL_ALL_ZEROCOPY, while skb_zcopy_downgrade_managed() clears SKBFL_MANAGED_FRAG_REFS — both in skb_shinfo(), which every clone shares. With an Open vSwitch clone (OVS_ACTION_ATTR_RECIRC) this strips the marker from a packet still being forwarded and a later local ESP delivery decrypts in place over frags it does not own privately.

A vulnerability exists in the Linux kernel's IPv6 segment routing (SRv6) handling. The decap_and_validate() function fails to reset the IPv6 control block (IP6CB) after decapsulation, allowing an unprivileged user to trigger a slab-out-of-bounds read in ip6_protocol_deliver_rcu().

In the Linux kernel, a vulnerability exists in the mfd: qnap-mcu driver. The qnap_mcu_exec() function publishes an on-stack buffer (rx) to the receive path, which can write to it after a command timeout or write failure when the stack frame is no longer valid. This leads to stack memory corruption and potential arbitrary code execution.

In the Linux kernel, memory allocated for the sm501_devdata structure in sm501_pci_probe() and sm501_plat_probe() is not freed by the corresponding remove functions sm501_pci_remove() and sm501_plat_remove(). This causes a memory leak on each device removal.

In the Linux kernel, the ALSA driver for USB 6fire devices (snd_usb_6fire) allowed usb6fire_comm_receiver_handler() to forward a MIDI event using a device-supplied length byte without any bound check. A malicious or faulty device could supply a length of 0xFF, causing a 255-byte read from a 64-byte buffer (out-of-bounds read). The issue occurs on device plug-in, and bytes beyond the buffer may be exposed to userspace via the rawmidi interface.

The ALSA aloop driver in the Linux kernel blindly trusts the devptr->id value at probe, assuming it is within the proper card index range. When a device is bound manually via sysfs, this value can be -1 ("none"), leading to out-of-bounds access to index[] and other parameters.

In the Linux kernel ALSA bcd2000 driver, the USB resource cleanup function freed URB structures without clearing the pointers. An open rawmidi substream could access freed memory (use-after-free) after device disconnect, leading to kernel memory corruption.

In the Linux kernel, the ALSA FCP driver's fcp_ioctl_init() allocated its response buffer with kmalloc() without zeroing it and copied the entire buffer back to userspace. A short or zero-length USB step-0 transfer was accepted as success, causing uninitialised kernel memory bytes to be disclosed to userspace. The fix zeroes the buffer and requires the step-0 transfer to deliver the full step0_resp_size bytes.

The ALSA mpu401 driver in the Linux kernel blindly trusts the devptr->id value at probe, assuming it is within the proper card index range. When a device is bound manually via sysfs, this value can be -1 ("none"), leading to out-of-bounds access to index[] and other parameters.

The ALSA mts64 driver in the Linux kernel checks the devptr->id value but does not validate negative values, which are often passed as "none" when a device is bound via sysfs. This may lead to out-of-bounds access to index[] and other parameters.

The pcxhr_probe() function in the Linux kernel requests pcxhr_threaded_irq() before initializing mgr->lock, even though the threaded handler takes that mutex. An early interrupt can therefore run against uninitialized mutex state during probe.

The ALSA portman2x4 driver in the Linux kernel checks the devptr->id value but does not validate negative values, which are often passed as "none" when a device is bound via sysfs. This may lead to out-of-bounds access to index[] and other parameters.

In the Linux kernel, the ALSA serial-u16550 driver blindly trusts that devptr->id is within the valid card index range at probe. When a device is bound manually via sysfs, this value can be -1 ("none"), leading to out-of-bounds access of index[] and other parameters. A sanity check was added to warn and correct out-of-range card index values.

In the Linux kernel, the ALSA virmidi driver blindly trusts that devptr->id is within the valid card index range at probe. When a device is bound manually via sysfs, this value can be -1 ("none"), leading to out-of-bounds access of index[] and other parameters. A sanity check was added to warn and correct out-of-range card index values.

In the Linux kernel, the dm-stats module has a bug where if per-CPU data allocation (dm_kvzalloc) fails, the code jumps to the "out" label and calls dm_stat_free, which dereferences s->stat_percpu[cpu] without a NULL check. This causes a NULL pointer dereference and kernel crash. The fix adds a NULL check before using the pointer.

In the Linux kernel, the dm-pcache module does not validate geometry fields (n_segs and segment id) from on-disk cache_info metadata. cache_segs_init() iterates n_segs times, indexing cache->segments[] sized to the device geometry. Since metadata is only CRC-protected with a public seed, whoever supplies the cache device (CAP_SYS_ADMIN) can provide an oversized n_segs or out-of-range id, causing out-of-bounds read and write. The fix rejects invalid values before use.

In the Linux kernel, the dm-pcache module does not bound the kset key_num field or intra-segment bounds. key_num drives cache_kset_crc() and the replay loop in cache_replay(), and since only magic and a fixed-seed CRC are checked, an invalid key_num can read past the PCACHE_KSET_KEYS_MAX buffer. Additionally, a key's offset and length in cache_key_decode() are taken verbatim, allowing reads past the segment and leaking data to user space. The fix adds validation of key_num and key bounds.

In the Linux kernel, the dm-pcache module does not validate the seg_num field from the crc32c-only superblock. seg_num sizes cache->segments[] and bounds all later segment ids, but is never checked against the device. Whoever supplies the cache device (CAP_SYS_ADMIN) can provide an oversized seg_num, causing an out-of-bounds write (12 KiB memset) into kernel memory at table load. The fix rejects seg_num that is zero, larger than the device can hold, or larger than PCACHE_CACHE_SEGS_MAX.

In the Linux kernel, the dm-pcache module does not bound the seg_off offset in cache_pos_decode(), which takes persisted key_tail and dirty_tail values from the cache device. A seg_off at or past the segment data_size, controllable by whoever supplies the device (CAP_SYS_ADMIN), reads past the segment data. The fix rejects a decoded seg_off that is not below the segment data_size.