CVE-2026-74358

In the Linux kernel, the following vulnerability has been resolved: ext4: fix fast commit wait/wake bit mapping on 64-bit On 64-bit, ext4 dynamic inode states live in the upper half of iflags, and ext4testinodestate applies the corresponding +32 offset. The fast-commit wait and wake paths...

CVE-2026-74356 vhost: fix vhost_get_avail_idx for a non empty ring

In the Linux kernel, the following vulnerability has been resolved: vhost: fix vhostgetavailidx for a non empty ring vhostgetavailidx is supposed to report whether it has updated vq-availidx. Instead, it returns whether all entries have been consumed, which is usually the same. But not always - i...

CVE-2026-74356

In the Linux kernel, the following vulnerability has been resolved: vhost: fix vhostgetavailidx for a non empty ring vhostgetavailidx is supposed to report whether it has updated vq-availidx. Instead, it returns whether all entries have been consumed, which is usually the same. But not always - i...

CVE-2026-74356 vhost: fix vhost_get_avail_idx for a non empty ring

In the Linux kernel, the following vulnerability has been resolved: vhost: fix vhostgetavailidx for a non empty ring vhostgetavailidx is supposed to report whether it has updated vq-availidx. Instead, it returns whether all entries have been consumed, which is usually the same. But not always - i...

EUVD-2026-59503

In the Linux kernel, the following vulnerability has been resolved: vhost: fix vhostgetavailidx for a non empty ring vhostgetavailidx is supposed to report whether it has updated vq-availidx. Instead, it returns whether all entries have been consumed, which is usually the same. But not always - i...

CVE-2026-74356

CVE-2026-74356 concerns the Linux kernel vhost subsystem. The issue is that vhost_get_avail_idx incorrectly reported whether all entries were consumed instead of whether new entries were added to the virtqueue, particularly affecting drivers/vhost/net.c when mergeable buffers are enabled. This mi...

EUVD-2026-59502

In the Linux kernel, the following vulnerability has been resolved: iommu/vt-d: Fix RB-tree corruption in probe error path The info-node RB-tree member is zero-initialized via kzalloc. If a device does not support ATS, the devicerbtreeinsert call is skipped. If a subsequent probe step fails, the...

EUVD-2026-59501

In the Linux kernel, the following vulnerability has been resolved: bpf: Take mmaplock in zappages zapvmarange requires the owning mm's mmaplock to be held. Taking mmapreadlock under arena-lock would AB-BA against arenavmclose and arenamapmmap, both of which run with mmapwritelock held and then...

CVE-2026-74354 bpf: Take mmap_lock in zap_pages()

In the Linux kernel, the following vulnerability has been resolved: bpf: Take mmaplock in zappages zapvmarange requires the owning mm's mmaplock to be held. Taking mmapreadlock under arena-lock would AB-BA against arenavmclose and arenamapmmap, both of which run with mmapwritelock held and then...

CVE-2026-74355 iommu/vt-d: Fix RB-tree corruption in probe error path

In the Linux kernel, the following vulnerability has been resolved: iommu/vt-d: Fix RB-tree corruption in probe error path The info-node RB-tree member is zero-initialized via kzalloc. If a device does not support ATS, the devicerbtreeinsert call is skipped. If a subsequent probe step fails, the...

CVE-2026-74355

In the Linux kernel vulnerability CVE-2026-74355, the issue occurs in iommu/vt-d where the info->node RB-tree is zero-initialized via kzalloc. If ATS is not supported, device_rbtree_insert() is skipped, and on a later failed probe step, device_rbtree_remove() can misinterpret the zeroed node a...

CVE-2026-74354

In the Linux kernel, the following vulnerability has been resolved: bpf: Take mmaplock in zappages zapvmarange requires the owning mm's mmaplock to be held. Taking mmapreadlock under arena-lock would AB-BA against arenavmclose and arenamapmmap, both of which run with mmapwritelock held and then...

CVE-2026-74354

CVE-2026-74354 : In the Linux kernel, a vulnerability in the BPF zap_pages path is resolved by changing how mmap_lock is taken for zap_vma_range(). The root cause is that zap_vma_range() requires the owning mm’s mmap_lock to be held, and taking mmap_read_lock under arena->lock could AB-BA agai...

CVE-2026-74354 bpf: Take mmap_lock in zap_pages()

In the Linux kernel, the following vulnerability has been resolved: bpf: Take mmaplock in zappages zapvmarange requires the owning mm's mmaplock to be held. Taking mmapreadlock under arena-lock would AB-BA against arenavmclose and arenamapmmap, both of which run with mmapwritelock held and then...

CVE-2026-74355

In the Linux kernel, the following vulnerability has been resolved: iommu/vt-d: Fix RB-tree corruption in probe error path The info-node RB-tree member is zero-initialized via kzalloc. If a device does not support ATS, the devicerbtreeinsert call is skipped. If a subsequent probe step fails, the...

CVE-2026-74355 iommu/vt-d: Fix RB-tree corruption in probe error path

In the Linux kernel, the following vulnerability has been resolved: iommu/vt-d: Fix RB-tree corruption in probe error path The info-node RB-tree member is zero-initialized via kzalloc. If a device does not support ATS, the devicerbtreeinsert call is skipped. If a subsequent probe step fails, the...

CVE-2026-74353 drm/amdkfd: always resume_all after suspend_all

In the Linux kernel, the following vulnerability has been resolved: drm/amdkfd: always resumeall after suspendall Need to restore any good queues even if the suspendall failed for some. Always run removequeue as that will schedule a GPU reset is removing the queue fails. v2: move resumeall after...

CVE-2026-74353

The CVE-2026-74353 entry concerns the Linux kernel component drm/amdkfd. The issue arises from an incorrect flow around suspend_all/resume_all: the fix ensures that queues are restored even if suspend_all fails and that remove_queue is always run because it can trigger a GPU reset if removing the...

CVE-2026-74353

In the Linux kernel, the following vulnerability has been resolved: drm/amdkfd: always resumeall after suspendall Need to restore any good queues even if the suspendall failed for some. Always run removequeue as that will schedule a GPU reset is removing the queue fails. v2: move resumeall after...

CVE-2026-74353 drm/amdkfd: always resume_all after suspend_all

In the Linux kernel, the following vulnerability has been resolved: drm/amdkfd: always resumeall after suspendall Need to restore any good queues even if the suspendall failed for some. Always run removequeue as that will schedule a GPU reset is removing the queue fails. v2: move resumeall after...