CVE-2026-63966 iio: imu: adis16550: fix stack leak in trigger handler

In the Linux kernel, the following vulnerability has been resolved: iio: imu: adis16550: fix stack leak in trigger handler adis16550triggerhandler declares the scan data array on the stack without initializing it. The memcpy at the bottom fills only the first 28 bytes TEMP + 6 channels of...

CVE-2026-63967

In the Linux kernel, the following vulnerability has been resolved: iio: imu: stlsm6dsx: fix stack leak in tagged FIFO buffer The tagged FIFO path declares iiobuff on the stack with aligned8 but no initializer, but there is a hole in the structure, which will then leak to userspace as...

CVE-2026-63965

In the Linux kernel, the following vulnerability has been resolved: iio: pressure: bmp280: fix stack leak in bmp580 trigger handler bmp580triggerhandler declares its scan buffer on the stack without an initializer and then memcpys 3 bytes of 24-bit sensor data into each 4-byte le32 field. The hig...

CVE-2026-63965 iio: pressure: bmp280: fix stack leak in bmp580 trigger handler

In the Linux kernel, the following vulnerability has been resolved: iio: pressure: bmp280: fix stack leak in bmp580 trigger handler bmp580triggerhandler declares its scan buffer on the stack without an initializer and then memcpys 3 bytes of 24-bit sensor data into each 4-byte le32 field. The hig...

CVE-2026-63965

The CVE-2026-63965 entry describes a Linux kernel IIO BMP280/BMP580 trigger handler stack leak: bmp580_trigger_handler() allocated a stack scan buffer and copied 24-bit sensor data into 32-bit fields without proper initialization, leaving high bytes uninitialized and causing two stack bytes per s...

EUVD-2026-45738

In the Linux kernel, the following vulnerability has been resolved: iio: pressure: bmp280: fix stack leak in bmp580 trigger handler bmp580triggerhandler declares its scan buffer on the stack without an initializer and then memcpys 3 bytes of 24-bit sensor data into each 4-byte le32 field. The hig...

CVE-2026-63838

The CVE-2026-63838 entry concerns the Linux kernel ASoC rsnd subsystem. It fixes a potential out-of-bounds access in rsnd_dai_of_node() caused by a boundary check (i >= RSND_MAX_COMPONENT) not guaranteeing component_dais[RSND_MAX_COMPONENT] remains zero, so a loop could read past the end of th...

CVE-2026-63838 ASoC: rsnd: Fix potential out-of-bounds access of component_dais[]

In the Linux kernel, the following vulnerability has been resolved: ASoC: rsnd: Fix potential out-of-bounds access of componentdais componentdaisRSNDMAXCOMPONENT is initially zero-initialized and later populated in rsnddaiofnode. However, the existing boundary check: if i = RSNDMAXCOMPONENT does...

EUVD-2026-45522

In the Linux kernel, the following vulnerability has been resolved: ASoC: rsnd: Fix potential out-of-bounds access of componentdais componentdaisRSNDMAXCOMPONENT is initially zero-initialized and later populated in rsnddaiofnode. However, the existing boundary check: if i = RSNDMAXCOMPONENT does...

CVE-2026-63838

In the Linux kernel, the following vulnerability has been resolved: ASoC: rsnd: Fix potential out-of-bounds access of componentdais componentdaisRSNDMAXCOMPONENT is initially zero-initialized and later populated in rsnddaiofnode. However, the existing boundary check: if i = RSNDMAXCOMPONENT does...

AZL-92543 CVE-2026-53374 affecting package kernel for versions less than 6.6.144.1-2

In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: zero-initialize GART table on allocation GART TLB is flushed after unmapping but not after mapping. Since amdgpubocreatekernel does not zero-initialize the buffer, when a single PTE is written the TLB may speculativel...

CVE-2026-53374

In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: zero-initialize GART table on allocation GART TLB is flushed after unmapping but not after mapping. Since amdgpubocreatekernel does not zero-initialize the buffer, when a single PTE is written the TLB may speculativel...

CVE-2026-53374

In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: zero-initialize GART table on allocation GART TLB is flushed after unmapping but not after mapping. Since amdgpubocreatekernel does not zero-initialize the buffer, when a single PTE is written the TLB may speculativel...

CVE-2026-53374

The CVE-2026-53374 issue affects the Linux kernel’s DRM/AMDGPU path: during amdgpu_bo_create_kernel() allocation, the GART table is not zero-initialized, so writing a single PTE can cause the TLB to speculatively load other uninitialized entries from the same cacheline. This can yield stale or ga...

CVE-2026-53374 drm/amdgpu: zero-initialize GART table on allocation

In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: zero-initialize GART table on allocation GART TLB is flushed after unmapping but not after mapping. Since amdgpubocreatekernel does not zero-initialize the buffer, when a single PTE is written the TLB may speculativel...

CVE-2026-53374 drm/amdgpu: zero-initialize GART table on allocation

In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: zero-initialize GART table on allocation GART TLB is flushed after unmapping but not after mapping. Since amdgpubocreatekernel does not zero-initialize the buffer, when a single PTE is written the TLB may speculativel...

PT-2026-61155

Name of the Vulnerable Software and Affected Versions Linux kernel affected versions not specified Description An out-of-bounds access issue exists in the ASoC rsnd component. The component dais array is zero-initialized and populated via the rsnd dai of node function. Because the boundary check ...

Linux Distros Unpatched Vulnerability : CVE-2026-53374

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available. - drm/amdgpu: zero-initialize GART table on allocation GART TLB is flushed after unmapping but not after mapping. Since amdgpubocreatekernel does not...

EUVD-2026-45070

Quicly is an IETF QUIC protocol implementation intended primarily for use within the H2O HTTP server. Prior to commit dccf5d4, Quicly was vulnerable to stateless reset injection through lack of packet entry validation. The QUIC protocol is designed to withstand packet injection attacks, once the...

PT-2026-60600

Name of the Vulnerable Software and Affected Versions Quicly versions prior to commit dccf5d4 Description Quicly, an IETF QUIC protocol implementation used primarily in the H2O HTTP server, is susceptible to stateless reset injection due to insufficient packet entry validation. While the QUIC...