12760 matches found
CVE-2022-49997
The CVE-2022-49997 issue affects the Linux kernel, specifically the net: lantiq_xrx200 driver. Root cause: when memory allocation fails, an invalid buffer address can be stored; using the descriptor again may cause a panic in build_skb(), resulting in an availability impact. Supported documents i...
CVE-2022-49997 net: lantiq_xrx200: restore buffer if memory allocation failed
In the Linux kernel, the following vulnerability has been resolved: net: lantiqxrx200: restore buffer if memory allocation failed In a situation where memory allocation fails, an invalid buffer address is stored. When this descriptor is used again, the system panics in the buildskb function when...
CVE-2022-49997
In the Linux kernel, the following vulnerability has been resolved: net: lantiqxrx200: restore buffer if memory allocation failed In a situation where memory allocation fails, an invalid buffer address is stored. When this descriptor is used again, the system panics in the buildskb function when...
CVE-2025-38071
In the Linux kernel, the following vulnerability has been resolved: x86/mm: Check return value from memblockphysallocrange At least with CONFIGPHYSICALSTART=0x100000, if there is 4 MiB of contiguous free memory available at this point, the kernel will crash and burn because memblockphysallocrange...
DEBIAN-CVE-2025-38071
In the Linux kernel, the following vulnerability has been resolved: x86/mm: Check return value from memblockphysallocrange At least with CONFIGPHYSICALSTART=0x100000, if there is 4 MiB of contiguous free memory available at this point, the kernel will crash and burn because memblockphysallocrange...
AZL-63932 CVE-2025-38043 affecting package kernel for versions less than 6.6.96.1-1
In the Linux kernel, the following vulnerability has been resolved: firmware: armffa: Set dmamask for ffa devices Set dmamask for FFA devices, otherwise DMA allocation using the device pointer lead to following warning: WARNING: CPU: 1 PID: 1 at kernel/dma/mapping.c:597 dmaallocattrs+0xe0/0x124...
DEBIAN-CVE-2025-38023
In the Linux kernel, the following vulnerability has been resolved: nfs: handle failure of nfsgetlockcontext in unlock path When memory is insufficient, the allocation of nfslockcontext in nfsgetlockcontext fails and returns -ENOMEM. If we mistakenly treat an nfs4unlockdata structure whose lctx...
DEBIAN-CVE-2025-38007
In the Linux kernel, the following vulnerability has been resolved: HID: uclogic: Add NULL check in uclogicinputconfigured devmkasprintf returns NULL when memory allocation fails. Currently, uclogicinputconfigured does not check for this case, which results in a NULL pointer dereference. Add NULL...
CVE-2025-38007
In the Linux kernel, the following vulnerability has been resolved: HID: uclogic: Add NULL check in uclogicinputconfigured devmkasprintf returns NULL when memory allocation fails. Currently, uclogicinputconfigured does not check for this case, which results in a NULL pointer dereference. Add NULL...
UBUNTU-CVE-2025-38023
In the Linux kernel, the following vulnerability has been resolved: nfs: handle failure of nfsgetlockcontext in unlock path When memory is insufficient, the allocation of nfslockcontext in nfsgetlockcontext fails and returns -ENOMEM. If we mistakenly treat an nfs4unlockdata structure whose lctx...
CVE-2025-38071
In the Linux kernel, the following vulnerability has been resolved: x86/mm: Check return value from memblockphysallocrange At least with CONFIGPHYSICALSTART=0x100000, if there is 4 MiB of contiguous free memory available at this point, the kernel will crash and burn because memblockphysallocrange...
CVE-2025-38071
CVE-2025-38071 affects the Linux kernel (x86/mm). Root cause: memblock_phys_alloc_range() may return 0 on failure when CONFIG_PHYSICAL_START=0x100000, causing memblock_phys_free() to mis-handle the first 4 MiB of memory and crash. The vulnerability is resolved in the kernel by checking the return...
CVE-2025-38070 ASoC: sma1307: Add NULL check in sma1307_setting_loaded()
In the Linux kernel, the following vulnerability has been resolved: ASoC: sma1307: Add NULL check in sma1307settingloaded All varibale allocated by kzalloc and devmkzalloc could be NULL. Multiple pointer checks and their cleanup are added. This issue is found by our static analysis tool...
CVE-2025-38071 x86/mm: Check return value from memblock_phys_alloc_range()
In the Linux kernel, the following vulnerability has been resolved: x86/mm: Check return value from memblockphysallocrange At least with CONFIGPHYSICALSTART=0x100000, if there is 4 MiB of contiguous free memory available at this point, the kernel will crash and burn because memblockphysallocrange...
CVE-2025-38029
In the Linux kernel, the following vulnerability has been resolved: kasan: avoid sleepable page allocation from atomic context applytopterange enters the lazy MMU mode and then invokes kasanpopulatevmallocpte callback on each page table walk iteration. However, the callback can go into sleep when...
CVE-2025-38023 nfs: handle failure of nfs_get_lock_context in unlock path
In the Linux kernel, the following vulnerability has been resolved: nfs: handle failure of nfsgetlockcontext in unlock path When memory is insufficient, the allocation of nfslockcontext in nfsgetlockcontext fails and returns -ENOMEM. If we mistakenly treat an nfs4unlockdata structure whose lctx...
CVE-2025-38023 nfs: handle failure of nfs_get_lock_context in unlock path
In the Linux kernel, the following vulnerability has been resolved: nfs: handle failure of nfsgetlockcontext in unlock path When memory is insufficient, the allocation of nfslockcontext in nfsgetlockcontext fails and returns -ENOMEM. If we mistakenly treat an nfs4unlockdata structure whose lctx...
CVE-2025-38023
CVE-2025-38023 affects the Linux kernel: if nfs_get_lock_context() fails due to ENOMEM, a stored -ENOMEM in an nfs4_unlockdata could be treated as valid and lead to a NULL pointer dereference in nfs4_locku_prepare via rpc_run_task. The fix ensures nfs4_unlockdata is freed when allocation fails an...
CVE-2025-38007
CVE-2025-38007 affects HID uclogic in the Linux kernel. Root cause: uclogic_input_configured() dereferences a NULL after devm_kasprintf() returns NULL due to allocation failure. Mitigation: a NULL check is added after devm_kasprintf() to prevent the dereference. Described fixes are documented in ...
CVE-2025-38007 HID: uclogic: Add NULL check in uclogic_input_configured()
In the Linux kernel, the following vulnerability has been resolved: HID: uclogic: Add NULL check in uclogicinputconfigured devmkasprintf returns NULL when memory allocation fails. Currently, uclogicinputconfigured does not check for this case, which results in a NULL pointer dereference. Add NULL...