PT-2026-72976

In the Linux kernel, the following vulnerability has been resolved: riscv: mm: Fix out-of-bounds page-table walk during memory hot-remove remove pud mapping and remove p4d mapping obtain a child table base with pud offsetp4dp, 0 and p4d offsetpgd, 0, then add the index for addr. RISC-V folds...

PT-2026-72221

In the Linux kernel, the following vulnerability has been resolved: net/mlx5: HWS, fix matcher leak on resize target setup failure hws bwc matcher move allocates a replacement matcher before setting it as the resize target. If mlx5hws matcher resize set target fails, the replacement matcher is no...

PT-2026-72363

In the Linux kernel, the following vulnerability has been resolved: fs/proc/task mmu: fix make uffd wp huge pte prot-update race Patch series "userfaultfd/pagemap: pre-existing fixes". These are pre-existing bug fixes that were carried at the front of the userfaultfd RWP working-set-tracking seri...

PT-2026-72357

In the Linux kernel, the following vulnerability has been resolved: kho: make sure scratch size is always aligned by CMA MIN ALIGNMENT BYTES When using scratch scale, the scratch sizes are rounded up to CMA MIN ALIGNMENT BYTES since they will be released as MIGRATE CMA. This is not done when usin...

PT-2026-72475

In the Linux kernel, the following vulnerability has been resolved: KVM: nVMX: Move vTPR vs. TPR Threshold consistency check into "normal" checks Move the off-by-default consistency check for vmcs12.tpr threshold vs. the virtual APIC vTPR into the "normal" controls checks, as waiting until KVM ha...

PT-2026-72532

In the Linux kernel, the following vulnerability has been resolved: net/mlx5e: TC, skip peer flow cleanup when LAG seq is unavailable mlx5 lag get dev seq will return error when the peer isn't in the LAG or when no device is marked as master. Result bad memory access and kernel crash1. Hence, ski...

PT-2026-72439

In the Linux kernel, the following vulnerability has been resolved: netfilter: nf nat sip: reload possible stale data pointer quoting sashiko: ------------------------------------------------------------------------ .. noticed a potential memory bug and header corruption involving the SIP NAT...

PT-2026-72455

In the Linux kernel, the following vulnerability has been resolved: fbdev: carminefb: fix potential memory leak in alloc carmine fb The memory allocated for modelist in fb videomode to modelist is not freed in the subsequent error path. Fix that by calling fb destroy modelist...

PT-2026-72815

In the Linux kernel, the following vulnerability has been resolved: dax/kmem: account for partial discontiguous resource upon removal When dev dax kmem probe partially succeeds at least one range is mapped but a subsequent range fails request mem region or add memory driver managed, the probe...

PT-2026-72459

In the Linux kernel, the following vulnerability has been resolved: fbdev: i740fb: fix potential memory leak in i740fb probe In i740fb probe, the memory allocated in fb videomode to modelist for modelist is not freed in the error paths. Fix that by calling fb destroy modelist...

PT-2026-72988

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: ISO: fix leaking sk after socket release iso sock kill tests !sock flagsk, SOCK ZAPPED || sk-sk socket || sock flagsk, SOCK DEAD for early return, but this is always true since sock orphansk sets SOCK DEAD, so the sk...

PT-2026-72499

In the Linux kernel, the following vulnerability has been resolved: drm/xe: free madvise VMA array on L2 flush failure xe vm madvise ioctl allocates madvise range.vmas in get vmas. After get vmas succeeds with at least one VMA, error paths must go through free vmas so the array is released before...

PT-2026-72456

In the Linux kernel, the following vulnerability has been resolved: fbdev: tdfxfb: fix potential memory leak in tdfxfb probe In tdfxfb probe, the memory allocated for modelist using fb videomode to modelist when CONFIG FB 3DFX I2C is defined, is not freed in the subsequent error paths. Fix that b...

PT-2026-72804

In the Linux kernel, the following vulnerability has been resolved: wifi: ath12k: fix memory leak in ath12k wifi7 dp rx h verify tkip mic In ath12k wifi7 dp rx h verify tkip mic, the call to ath12k dp rx check nwifi hdr len valid may return false when the NWIFI header length is invalid, causing t...

PT-2026-72916

In the Linux kernel, the following vulnerability has been resolved: net: openvswitch: fix skb leak on flow key update failure during ct ovs ct execute always steals or frees the skb on failure while ovs flow key update does not. So, if it fails and we return right away, the skb ends up leaked. Fi...

PT-2026-72509

In the Linux kernel, the following vulnerability has been resolved: ipv4: igmp: Fix potential memory leaks in igmp mod timer and igmp stop timer When a timer is deleted and not re-armed in igmp mod timer, or stopped in igmp stop timer, the code currently decrements the reference counter of the...

PT-2026-72493

In the Linux kernel, the following vulnerability has been resolved: VDUSE: avoid leaking information to userspace The bounceing is not necessarily page aligned, so current VDUSE can leak kernel information through mapping bounce pages to userspace. Allocate bounce pages with GFP ZERO to avoid...

PT-2026-72544

In the Linux kernel, the following vulnerability has been resolved: cifs: Fix missing credit release on failure in cifs issue read Fix missing release of credits in the failure path in cifs issue read lest retrying the subreq just overwrites the credits value...

PT-2026-72971

In the Linux kernel, the following vulnerability has been resolved: pinctrl: devicetree: don't free uninitialized dev name on error path dt remember or free map duplicates dev name for each map entry. If kstrdup const fails, dt free map frees dev name in all num maps entries, including entries th...

PT-2026-72839

In the Linux kernel, the following vulnerability has been resolved: crypto: ccp - Check for page allocation failure correctly in TIO Sashiko notes: if snp alloc firmware pages returns NULL under memory pressure, is it safe to pass it directly to page address? On architectures without HASHED PAGE...