CVSS: 7.1EPSS: 0%CPEs: 4EXPL: 0CVE-2025-68184 – drm/mediatek: Disable AFBC support on Mediatek DRM driver
https://notcve.org/view.php?id=CVE-2025-68184
16 Dec 2025 — In the Linux kernel, the following vulnerability has been resolved: drm/mediatek: Disable AFBC support on Mediatek DRM driver Commit c410fa9b07c3 ("drm/mediatek: Add AFBC support to Mediatek DRM driver") added AFBC support to Mediatek DRM and enabled the 32x8/split/sparse modifier. However, this is currently broken on Mediatek MT8188 (Genio 700 EVK platform); tested using upstream Kernel and Mesa (v25.2.1), AFBC is used by default since Mesa v25.0. Kernel trace reports vblank timeouts constantly, and the re... • https://git.kernel.org/stable/c/c410fa9b07c32cc69968ec83a148366d16c76dc4 •
CVSS: 7.1EPSS: 0%CPEs: 4EXPL: 0CVE-2025-68183 – ima: don't clear IMA_DIGSIG flag when setting or removing non-IMA xattr
https://notcve.org/view.php?id=CVE-2025-68183
16 Dec 2025 — In the Linux kernel, the following vulnerability has been resolved: ima: don't clear IMA_DIGSIG 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 writes/removes some other security xattr for the file. For example, on Fedora, after booting the kernel with "ima_appraise=fix evm=fix ima_policy=appraise_tcb" and installing rpm-plugin-ima, installing/reinstalling... • https://git.kernel.org/stable/c/e3ccfe1ad7d895487977ef64eda3441d16c9851a •
CVSS: 7.1EPSS: 0%CPEs: 4EXPL: 0CVE-2025-68179 – s390: Disable ARCH_WANT_OPTIMIZE_HUGETLB_VMEMMAP
https://notcve.org/view.php?id=CVE-2025-68179
16 Dec 2025 — In the Linux kernel, the following vulnerability has been resolved: s390: Disable ARCH_WANT_OPTIMIZE_HUGETLB_VMEMMAP As reported by Luiz Capitulino enabling HVO on s390 leads to reproducible crashes. The problem is that kernel page tables are modified without flushing corresponding TLB entries. Even if it looks like the empty flush_tlb_all() implementation on s390 is the problem, it is actually a different problem: on s390 it is not allowed to replace an active/valid page table entry with another valid page... • https://git.kernel.org/stable/c/00a34d5a99c0631bd780b14cbe3813d0b39c3886 •
CVSS: 5.5EPSS: 0%CPEs: 8EXPL: 0CVE-2025-68177 – cpufreq/longhaul: handle NULL policy in longhaul_exit
https://notcve.org/view.php?id=CVE-2025-68177
16 Dec 2025 — In the Linux kernel, the following vulnerability has been resolved: cpufreq/longhaul: handle NULL policy in longhaul_exit longhaul_exit() was calling cpufreq_cpu_get(0) without checking for a NULL policy pointer. On some systems, this could lead to a NULL dereference and a kernel warning or panic. This patch adds a check using unlikely() and returns early if the policy is NULL. Bugzilla: #219962 In the Linux kernel, the following vulnerability has been resolved: cpufreq/longhaul: handle NULL policy in longh... • https://git.kernel.org/stable/c/b43a7ffbf33be7e4d3b10b7714ee663ea2c52fe2 •
CVSS: 5.5EPSS: 0%CPEs: 7EXPL: 0CVE-2025-68176 – PCI: cadence: Check for the existence of cdns_pcie::ops before using it
https://notcve.org/view.php?id=CVE-2025-68176
16 Dec 2025 — In the Linux kernel, the following vulnerability has been resolved: PCI: cadence: Check for the existence of cdns_pcie::ops before using it cdns_pcie::ops might not be populated by all the Cadence glue drivers. This is going to be true for the upcoming Sophgo platform which doesn't set the ops. Hence, add a check to prevent NULL pointer dereference. [mani: reworded subject and description] In the Linux kernel, the following vulnerability has been resolved: PCI: cadence: Check for the existence of cdns_pcie:... • https://git.kernel.org/stable/c/40d957e6f9eb3a8a585007b8b730340c829afbdb •
CVSS: 6.6EPSS: 0%CPEs: 5EXPL: 0CVE-2025-68173 – ftrace: Fix softlockup in ftrace_module_enable
https://notcve.org/view.php?id=CVE-2025-68173
16 Dec 2025 — In the Linux kernel, the following vulnerability has been resolved: ftrace: Fix softlockup in ftrace_module_enable A soft lockup was observed when loading amdgpu module. If a module has a lot of tracable functions, multiple calls to kallsyms_lookup can spend too much time in RCU critical section and with disabled preemption, causing kernel panic. This is the same issue that was fixed in commit d0b24b4e91fc ("ftrace: Prevent RCU stall on PREEMPT_VOLUNTARY kernels") and commit 42ea22e754ba ("ftrace: Add cond_... • https://git.kernel.org/stable/c/b7ffffbb46f205e7727a18bcc7a46c3c2b534f7c •
CVSS: 5.5EPSS: 0%CPEs: 5EXPL: 0CVE-2025-68171 – x86/fpu: Ensure XFD state on signal delivery
https://notcve.org/view.php?id=CVE-2025-68171
16 Dec 2025 — In the Linux kernel, the following vulnerability has been resolved: x86/fpu: Ensure XFD state on signal delivery Sean reported [1] the following splat when running KVM tests: WARNING: CPU: 232 PID: 15391 at xfd_validate_state+0x65/0x70 Call Trace:
CVSS: 5.5EPSS: 0%CPEs: 11EXPL: 0CVE-2025-68168 – jfs: fix uninitialized waitqueue in transaction manager
https://notcve.org/view.php?id=CVE-2025-68168
16 Dec 2025 — In the Linux kernel, the following vulnerability has been resolved: jfs: fix uninitialized waitqueue in transaction manager The transaction manager initialization in txInit() was not properly initializing TxBlock[0].waitor waitqueue, causing a crash when txEnd(0) is called on read-only filesystems. When a filesystem is mounted read-only, txBegin() returns tid=0 to indicate no transaction. However, txEnd(0) still gets called and tries to access TxBlock[0].waitor via tid_to_tblock(0), but this waitqueue was n... • https://git.kernel.org/stable/c/2a8807f9f511c64de0c7cc9900a1683e3d72a3e5 •
CVSS: -EPSS: 0%CPEs: 8EXPL: 0CVE-2025-40363 – net: ipv6: fix field-spanning memcpy warning in AH output
https://notcve.org/view.php?id=CVE-2025-40363
16 Dec 2025 — In the Linux kernel, the following vulnerability has been resolved: net: ipv6: fix field-spanning memcpy warning in AH output Fix field-spanning memcpy warnings in ah6_output() and ah6_output_done() where extension headers are copied to/from IPv6 address fields, triggering fortify-string warnings about writes beyond the 16-byte address fields. memcpy: detected field-spanning write (size 40) of single field "&top_iph->saddr" at net/ipv6/ah6.c:439 (size 16) WARNING: CPU: 0 PID: 8838 at net/ipv6/ah6.c:439 ah6_... • https://git.kernel.org/stable/c/1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 •
CVSS: -EPSS: 0%CPEs: 7EXPL: 0CVE-2025-40361 – fs: ext4: change GFP_KERNEL to GFP_NOFS to avoid deadlock
https://notcve.org/view.php?id=CVE-2025-40361
16 Dec 2025 — In the Linux kernel, the following vulnerability has been resolved: fs: ext4: change GFP_KERNEL to GFP_NOFS to avoid deadlock The parent function ext4_xattr_inode_lookup_create already uses GFP_NOFS for memory alloction, so the function ext4_xattr_inode_cache_find should use same gfp_flag. • https://git.kernel.org/stable/c/71b565ceff377a52e7d58cd871745cd339447323 •