CVE-2025-38730 is a vulnerability in the Linux kernel's io_uring networking implementation. It involves improper handling of partial buffers on retry when using ring provided buffers, which can lead to data corruption or invalid memory access. The flaw occurs because buffers may be reused or invalidated incorrectly across multiple execution contexts, especially when MSG_WAITALL is set or streaming sockets process insufficient data. This can cause multiple sockets to consume the same memory or references to invalid buffers if the buffer ring is unregistered prematurely.
A race condition vulnerability in the Linux kernel's kcm_unattach() function was identified and fixed. The flaw occurs when kcm_unattach(psock) and kcm_release(kcm) execute concurrently, potentially causing a use-after-free scenario by requeuing work on a kcm object that is about to be freed. The issue stems from a missing check of the kcm->tx_stopped flag before queueing work, which was replaced by a safer disable_work_sync() call.
CVE-2025-38720 is a Linux kernel vulnerability involving a deadlock in the hibmcge network driver during PCI device reset. The issue arises because the driver acquires the rtnl_lock twice sequentially for different devices, causing a deadlock. The fix removes the need to hold the rtnl_lock during the reset process by detaching the network device beforehand and adjusts internal state to prevent concurrent resets.
A vulnerability in the Linux kernel's ftgmac100 network driver could lead to a NULL pointer dereference in the ftgmac100_phy_disconnect function. This occurs because after calling phy_disconnect(), the netdev->phydev pointer is reset to NULL, but fixed_phy_unregister() is then called with this NULL pointer. The issue was fixed by caching the phy_device pointer before the call to avoid passing a NULL pointer.
CVE-2025-38682 is a high-severity vulnerability in the Linux kernel's i2c core subsystem. It involves a double-free of a firmware node (fwnode) in the i2c_unregister_device() function. The flaw occurs when a software fwnode is treated as the primary node, leading to two separate calls that decrement its reference count, causing a use-after-free and potential system instability or crash.
In the Linux kernel, the following vulnerability has been resolved: media: iris: Fix NULL pointer dereference A warning reported by smatch indicated a possible null pointer dereference where one of the arguments to API "iris_hfi_gen2_handle_system_error" could sometimes be null. To fix this, add a check to validate that the argument passed is not null before accessing its members.
In the Linux kernel, the following vulnerability has been resolved: iio: accel: sca3300: fix uninitialized iio scan data Fix potential leak of uninitialized stack data to userspace by ensuring that the `channels` array is zeroed before use.
In the Linux kernel, the following vulnerability has been resolved: scsi: ufs: ufs-qcom: Fix ESI null pointer dereference ESI/MSI is a performance optimization feature that provides dedicated interrupts per MCQ hardware queue. This is optional feature and UFS MCQ should work with and without ESI feature. Commit e46a28cea29a ("scsi: ufs: qcom: Remove the MSI descriptor abuse") brings a regression in ESI (Enhanced System Interrupt) configuration that causes a null pointer dereference when Platform MSI allocation fails. The issue occurs in when platform_device_msi_init_and_alloc_irqs() in ufs_qcom_config_esi() fails (returns -EINVAL) but the current code uses __free() macro for automatic cleanup free MSI resources that were never successfully allocated. Unable to handle kernel NULL pointer dereference at virtual address 0000000000000008 Call trace: mutex_lock+0xc/0x54 (P) platform_device_msi_free_irqs_all+0x1c/0x40 ufs_qcom_config_esi+0x1d0/0x220 [ufs_qcom] ufshcd_config_mcq+0x28/0x104 ufshcd_init+0xa3c/0xf40 ufshcd_pltfrm_init+0x504/0x7d4 ufs_qcom_probe+0x20/0x58 [ufs_qcom] Fix by restructuring the ESI configuration to try MSI allocation first, before any other resource allocation and instead use explicit cleanup instead of __free() macro to avoid cleanup of unallocated resources. Tested on SM8750 platform with MCQ enabled, both with and without Platform ESI support.
In the Linux kernel, the following vulnerability has been resolved: drm/xe/migrate: prevent infinite recursion If the buf + offset is not aligned to XE_CAHELINE_BYTES we fallback to using a bounce buffer. However the bounce buffer here is allocated on the stack, and the only alignment requirement here is that it's naturally aligned to u8, and not XE_CACHELINE_BYTES. If the bounce buffer is also misaligned we then recurse back into the function again, however the new bounce buffer might also not be aligned, and might never be until we eventually blow through the stack, as we keep recursing. Instead of using the stack use kmalloc, which should respect the power-of-two alignment request here. Fixes a kernel panic when triggering this path through eudebug. v2 (Stuart): - Add build bug check for power-of-two restriction - s/EINVAL/ENOMEM/ (cherry picked from commit 38b34e928a08ba594c4bbf7118aa3aadacd62fff)
Note that users must have administrator access to the Craft Control Panel, and [allowAdminChanges](https://craftcms.com/docs/5.x/reference/config/general.html#allowadminchanges) must be enabled for this to work, which is against Craft CMS' recommendations for any non-dev environment.
https://craftcms.com/knowledge-base/securing-craft#set-allowAdminChanges-to-false-in-production
Note: This is a follow-up to [GHSA-f3cw-hg6r-chfv](https://github.com/craftcms/cms/security/advisories/GHSA-f3cw-hg6r-chfv)
Users should update to the patched versions (4.16.6 and 5.8.7) to mitigate the issue.
Resources: https://github.com/craftcms/cms/pull/17612
A security vulnerability (CVE-2025-54389) in the Advanced Intrusion Detection Environment (AIDE) utility for Red Hat Enterprise Linux 9 allows bypassing security measures due to improper output neutralization. AIDE is used to ensure file integrity and detect system intrusions. Red Hat has released an important security update addressing this issue.
CVE-2025-38667 is a high-severity vulnerability in the Linux kernel's Industrial I/O (iio) subsystem involving a potential out-of-bound write. The issue arises because a buffer of 20 characters may be overwritten if the input exceeds this size. The fix involves truncating the input size to the buffer capacity and ensuring a zero terminator is added after copying to prevent out-of-bound access.
CVE-2025-38672 is a medium-severity vulnerability in the Linux kernel's DRM subsystem related to the handling of dma_buf in GEM object instances. The dma_buf field in struct drm_gem_object can become NULL when the user space releases the final GEM handle, leading to a NULL-pointer dereference. Partial workarounds were insufficient, prompting a revert to a previous implementation that uses .import_attach->dmabuf to avoid this issue.
CVE-2025-38674 is a vulnerability in the Linux kernel's Direct Rendering Manager (DRM) subsystem related to the handling of dma_buf pointers in GEM objects. The dma_buf field in the drm_gem_object structure can become NULL when user space releases the final GEM handle, leading to a NULL-pointer dereference. Partial workarounds were insufficient, so the problematic commit was reverted to restore previous behavior using .import_attach->dmabuf. This vulnerability has a medium severity rating with an impact on availability due to potential kernel crashes.
CVE-2025-38669 is a medium-severity vulnerability in the Linux kernel's DRM subsystem related to the handling of dma_buf pointers in GEM objects. The dma_buf field in struct drm_gem_object can become NULL when user space releases the final GEM handle, leading to a NULL-pointer dereference and potential denial of service. Previous partial workarounds did not fully address the issue, especially for buffer objects without associated DRM framebuffers. The vulnerability was resolved by reverting a commit that introduced the unstable dma_buf usage and returning to a more stable reference approach.
CVE-2025-38675 is a medium severity vulnerability in the Linux kernel's xfrm subsystem. It involves improper initialization of a pointer (state_ptrs) in the xfrm_state_find function, which can lead to use of uninitialized memory during CPU preemption scenarios. This flaw can cause a denial of service (kernel crash) due to an invalid memory access. The issue has been resolved by initializing state_ptrs earlier in the function to prevent misuse.
CVE-2025-38673 is a medium severity vulnerability in the Linux kernel's Direct Rendering Manager (DRM) subsystem. It involves a NULL-pointer dereference caused by the dma_buf field in the drm_gem_object structure becoming NULL when user space releases the final GEM handle. Previous partial workarounds did not fully resolve the issue, especially for buffer objects without an associated DRM framebuffer. The vulnerability was addressed by reverting a prior commit and returning to the use of the .import_attach->dmabuf field.
In the Linux kernel, the following vulnerability has been resolved:
landlock: Fix warning from KUnit tests
get_id_range() expects a positive value as first argument but
get_random_u8() can return 0. Fix this by clamping it.
Validated by running the test in a for loop for 1000 times.
Note that MAX() is wrong as it is only supposed to be used for
constants, but max() is good here.
[..] ok 9 test_range2_rand1
[..] ok 10 test_range2_rand2
[..] ok 11 test_range2_rand15
[..] ------------[ cut here ]------------
[..] WARNING: CPU: 6 PID: 104 at security/landlock/id.c:99 test_range2_rand16 (security/landlock/id.c:99 (discriminator 1) security/landlock/id.c:234 (discriminator 1))
[..] Modules linked in:
[..] CPU: 6 UID: 0 PID: 104 Comm: kunit_try_catch Tainted: G N 6.16.0-rc1-dev-00001-g314a2f98b65f #1 PREEMPT(undef)
[..] Tainted: [N]=TEST
[..] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014
[..] RIP: 0010:test_range2_rand16 (security/landlock/id.c:99 (discriminator 1) security/landlock/id.c:234 (discriminator 1))
[..] Code: 49 c7 c0 10 70 30 82 4c 89 ff 48 c7 c6 a0 63 1e 83 49 c7 45 a0 e0 63 1e 83 e8 3f 95 17 00 e9 1f ff ff ff 0f 0b e9 df fd ff ff <0f> 0b ba 01 00 00 00 e9 68 fe ff ff 49 89 45 a8 49 8d 4d a0 45 31
[..] RSP: 0000:ffff888104eb7c78 EFLAGS: 00010246
[..] RAX: 0000000000000000 RBX: 000000000870822c RCX: 0000000000000000
^^^^^^^^^^^^^^^^
[..]
[..] Call Trace:
[..]
[..] ---[ end trace 0000000000000000 ]---
[..] ok 12 test_range2_rand16
[..] # landlock_id: pass:12 fail:0 skip:0 total:12
[..] # Totals: pass:12 fail:0 skip:0 total:12
[..] ok 1 landlock_id
[mic: Minor cosmetic improvements]
In the Linux kernel, the following vulnerability has been resolved:
arm64: dts: qcom: qcs615: fix a crash issue caused by infinite loop for Coresight
An infinite loop has been created by the Coresight devices. When only a
source device is enabled, the coresight_find_activated_sysfs_sink function
is recursively invoked in an attempt to locate an active sink device,
ultimately leading to a stack overflow and system crash. Therefore, disable
the replicator1 to break the infinite loop and prevent a potential stack
overflow.
replicator1_out -> funnel_swao_in6 -> tmc_etf_swao_in -> tmc_etf_swao_out
| |
replicator1_in replicator_swao_in
| |
replicator0_out1 replicator_swao_out0
| |
replicator0_in funnel_in1_in3
| |
tmc_etf_out <- tmc_etf_in <- funnel_merg_out <- funnel_merg_in1 <- funnel_in1_out
[call trace]
dump_backtrace+0x9c/0x128
show_stack+0x20/0x38
dump_stack_lvl+0x48/0x60
dump_stack+0x18/0x28
panic+0x340/0x3b0
nmi_panic+0x94/0xa0
panic_bad_stack+0x114/0x138
handle_bad_stack+0x34/0xb8
__bad_stack+0x78/0x80
coresight_find_activated_sysfs_sink+0x28/0xa0 [coresight]
coresight_find_activated_sysfs_sink+0x5c/0xa0 [coresight]
coresight_find_activated_sysfs_sink+0x5c/0xa0 [coresight]
coresight_find_activated_sysfs_sink+0x5c/0xa0 [coresight]
coresight_find_activated_sysfs_sink+0x5c/0xa0 [coresight]
...
coresight_find_activated_sysfs_sink+0x5c/0xa0 [coresight]
coresight_enable_sysfs+0x80/0x2a0 [coresight]
side effect after the change:
Only trace data originating from AOSS can reach the ETF_SWAO and EUD sinks.