CVE-2025-68321

CVE-2025-68321 is documented in the Linux kernel page_pool patch: GFP_NOWARN is now added by default for ATOMIC page allocations to reduce user-visible OOM surprises. This fix targets kernel networking datapath paths where page allocations may fail under memory pressure. The connected Astra Linux...

CVE-2025-68321 page_pool: always add GFP_NOWARN for ATOMIC allocations

In the Linux kernel, the following vulnerability has been resolved: pagepool: always add GFPNOWARN for ATOMIC allocations Driver authors often forget to add GFPNOWARN for page allocation from the datapath. This is annoying to users as OOMs are a fact of life, and we pretty much expect network Rx ...

EUVD-2025-203648

In the Linux kernel, the following vulnerability has been resolved: vmwballoon: indicate success when effectively deflating during migration When migrating a balloon page, we first deflate the old page to then inflate the new page. However, if inflating the new page succeeded, we effectively...

EUVD-2025-203707

In the Linux kernel, the following vulnerability has been resolved: drm/msm: Fix GEM free for imported dma-bufs Imported dma-bufs also have obj-resv != &obj-resv. So we should check both this condition in addition to flags for handling the NOSHARE case. Fixes this splat that was reported with IRI...

UBUNTU-CVE-2025-68248

In the Linux kernel, the following vulnerability has been resolved: vmwballoon: indicate success when effectively deflating during migration When migrating a balloon page, we first deflate the old page to then inflate the new page. However, if inflating the new page succeeded, we effectively...

CVE-2025-68292

The CVE-2025-68292 issue concerns the Linux kernel memfd hugetlb folio allocation. A path used by memfd bypassed the normal page fault handler (hugetlb_no_page), omitting three initialisation steps that could leak kernel memory or cause races: (1) folios not zeroed, risking information disclosure...

CVE-2025-68282 usb: gadget: udc: fix use-after-free in usb_gadget_state_work

In the Linux kernel, the following vulnerability has been resolved: usb: gadget: udc: fix use-after-free in usbgadgetstatework A race condition during gadget teardown can lead to a use-after-free in usbgadgetstatework, as reported by KASAN: BUG: KASAN: invalid-access in sysfsnotify+0x2c/0xd0...

CVE-2025-68282 usb: gadget: udc: fix use-after-free in usb_gadget_state_work

In the Linux kernel, the following vulnerability has been resolved: usb: gadget: udc: fix use-after-free in usbgadgetstatework A race condition during gadget teardown can lead to a use-after-free in usbgadgetstatework, as reported by KASAN: BUG: KASAN: invalid-access in sysfsnotify+0x2c/0xd0...

CVE-2025-68282

In the Linux kernel, the following vulnerability has been resolved: usb: gadget: udc: fix use-after-free in usbgadgetstatework A race condition during gadget teardown can lead to a use-after-free in usbgadgetstatework, as reported by KASAN: BUG: KASAN: invalid-access in sysfsnotify+0x2c/0xd0...

CVE-2025-68282

The CVE-2025-68282 issue is in the Linux kernel USB gadget UDC teardown: a race can cause a use-after-free in usb_gadget_state_work due to a concurrent event scheduling work during cleanup. The fix introduces a teardown flag and a state_lock spinlock in the usb_gadget struct; the flag is set duri...

CVE-2025-68261

In the Linux kernel, the following vulnerability has been resolved: ext4: add idatasem protection in ext4destroyinlinedatanolock Fix a race between inline data destruction and block mapping. The function ext4destroyinlinedatanolock changes the inode data layout by clearing EXT4INODEINLINEDATA and...

CVE-2025-68261

CVE-2025-68261 affects the Linux kernel’s ext4 filesystem. The fix adds i_data_sem protection to ext4_destroy_inline_data_nolock() to close a race between destroying inline data and block mapping. Without protection, ext4_ind_map_blocks() may receive an inode with EXT4_INODE_EXTENTS set, triggeri...

CVE-2025-68248 vmw_balloon: indicate success when effectively deflating during migration

In the Linux kernel, the following vulnerability has been resolved: vmwballoon: indicate success when effectively deflating during migration When migrating a balloon page, we first deflate the old page to then inflate the new page. However, if inflating the new page succeeded, we effectively...

CVE-2025-40361

Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority...

UBUNTU-CVE-2025-68183

In the Linux kernel, the following vulnerability has been resolved: ima: don't clear IMADIGSIG flag when setting or removing non-IMA xattr Currently when both IMA and EVM are in fix mode, the IMA signature will be reset to IMA hash if a program first stores IMA signature in security.ima and then...

UBUNTU-CVE-2025-68189

In the Linux kernel, the following vulnerability has been resolved: drm/msm: Fix GEM free for imported dma-bufs Imported dma-bufs also have obj-resv != &obj-resv. So we should check both this condition in addition to flags for handling the NOSHARE case. Fixes this splat that was reported with IRI...

CVE-2025-68189

In the Linux kernel, the following vulnerability has been resolved: drm/msm: Fix GEM free for imported dma-bufs Imported dma-bufs also have obj-resv != &obj-resv. So we should check both this condition in addition to flags for handling the NOSHARE case. Fixes this splat that was reported with IRI...

CVE-2025-68183 ima: don't clear IMA_DIGSIG flag when setting or removing non-IMA xattr

In the Linux kernel, the following vulnerability has been resolved: ima: don't clear IMADIGSIG flag when setting or removing non-IMA xattr Currently when both IMA and EVM are in fix mode, the IMA signature will be reset to IMA hash if a program first stores IMA signature in security.ima and then...

CVE-2025-40361

CVE-2025-40361 entry is rejected/not used and not an active vulnerability.

CVE-2025-40361 fs: ext4: change GFP_KERNEL to GFP_NOFS to avoid deadlock

In the Linux kernel, the following vulnerability has been resolved: fs: ext4: change GFPKERNEL to GFPNOFS to avoid deadlock The parent function ext4xattrinodelookupcreate already uses GFPNOFS for memory alloction, so the function ext4xattrinodecachefind should use same gfpflag...