CVE-2025-68225 lib/test_kho: check if KHO is enabled

In the Linux kernel, the following vulnerability has been resolved: lib/testkho: check if KHO is enabled We must check whether KHO is enabled prior to issuing KHO commands, otherwise KHO internal data structures are not initialized...

CVE-2025-68224

...

CVE-2025-68224

CVE-2025-68224 is rejected/not used as stated in the Initial Description.

CVE-2025-68224 scsi: core: Fix a regression triggered by scsi_host_busy()

In the Linux kernel, the following vulnerability has been resolved: scsi: core: Fix a regression triggered by scsihostbusy Commit 995412e23bb2 "blk-mq: Replace tags-lock with SRCU for tag iterators" introduced the following regression: Call trace: srcureadlock+0x30/0x80 P...

CVE-2025-68222 pinctrl: s32cc: fix uninitialized memory in s32_pinctrl_desc

In the Linux kernel, the following vulnerability has been resolved: pinctrl: s32cc: fix uninitialized memory in s32pinctrldesc s32pinctrldesc is allocated with devmkmalloc, but not all of its fields are initialized. Notably, numcustomparams is used in pinconfgenericparsedtconfig, resulting in...

CVE-2025-68213

CVE-2025-68213: Linux kernel idpf driver vulnerability where remove() may dereference a NULL vport_config if vport initialization failed, causing a kernel crash during device removal. Mitigation implemented by adding a NULL pointer check for vport_config[i] before freeing user_config.q_coalesce. ...

CVE-2025-68213 idpf: fix possible vport_config NULL pointer deref in remove

In the Linux kernel, the following vulnerability has been resolved: idpf: fix possible vportconfig NULL pointer deref in remove Attempting to remove the driver will cause a crash in cases where the vport failed to initialize. Following trace is from an instance where the driver failed during an...

CVE-2025-68213 idpf: fix possible vport_config NULL pointer deref in remove

In the Linux kernel, the following vulnerability has been resolved: idpf: fix possible vportconfig NULL pointer deref in remove Attempting to remove the driver will cause a crash in cases where the vport failed to initialize. Following trace is from an instance where the driver failed during an...

CVE-2025-68212

The CVE-2025-68212 entry describes a Linux kernel issue in fs/namespace.c: statmount_string() uses an offp pointer for several flags, but STATMOUNT_MNT_UIDMAP and STATMOUNT_MNT_GIDMAP set struct fields directly, leaving offp uninitialized. This can cause an uninitialized dereference when *offp is...

CVE-2025-68204 pmdomain: arm: scmi: Fix genpd leak on provider registration failure

In the Linux kernel, the following vulnerability has been resolved: pmdomain: arm: scmi: Fix genpd leak on provider registration failure If ofgenpdaddprovideronecell fails during probe, the previously created generic power domains are not removed, leading to a memory leak and potential kernel cra...

CVE-2025-68187

The CVE-2025-68187 issue affects the Linux kernel: in the airoha_mdio_probe path, device_node_to_regmap() may return an ERR_PTR() if regmap initialization fails, but the driver previously stored that pointer without validation, risking a crash on dereference. The vulnerability is mitigated by add...

CVE-2025-68168

The CVE-2025-68168 issue is in the Linux kernel JFS transaction manager. The root cause was that txInit() did not initialize TxBlock[0].waitor, so when reading from a read-only filesystem txEnd(0) accessed an uninitialized waitqueue via tid_to_tblock(0). This could trigger a non-static key lockde...

CVE-2025-68168 jfs: fix uninitialized waitqueue in transaction manager

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 TxBlock0.waitor waitqueue, causing a crash when txEnd0 is called on read-only filesystems. Whe...

CVE-2025-68168 jfs: fix uninitialized waitqueue in transaction manager

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 TxBlock0.waitor waitqueue, causing a crash when txEnd0 is called on read-only filesystems. Whe...

CVE-2025-68167 gpiolib: fix invalid pointer access in debugfs

In the Linux kernel, the following vulnerability has been resolved: gpiolib: fix invalid pointer access in debugfs If the memory allocation in gpiolibseqstart fails, the s-private field remains uninitialized and is later dereferenced without checking in gpiolibseqstop. Initialize s-private to NUL...

CVE-2025-68167

Summary (CVE-2025-68167) : In the Linux kernel gpiolib, a path in debugfs allows a local attacker to trigger a pointer dereference. The root cause is that if memory allocation in gpiolib_seq_start() fails, s->private remains uninitialized and is later dereferenced in gpiolib_seq_stop(). The fi...

CVE-2025-14758 Initialization of a Resource with an Insecure Default in YAOOK

Incorrect configuration of replication security in the MariaDB component of the infra-operator in YAOOK Operator allows an on-path attacker to read database contents, potentially including credentials...

Linux kernel 安全漏洞

Linux kernel is the kernel used by Linux, the open source operating system of the Linux Foundation in the United States. A security vulnerability exists in the Linux kernel that stems from a call to putdevice in most:usb:hdmprobe before device initialization, which may result in a kernel warning...

Linux Distros Unpatched Vulnerability : CVE-2025-68224

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available. - scsi: core: Fix a regression triggered by scsihostbusy Commit 995412e23bb2 blk-mq: Replace tags-lock with SRCU for tag iterators introduced the following...

PT-2025-51638

Name of the Vulnerable Software and Affected Versions Linux kernel affected versions not specified Description The Linux kernel contains an issue in lib/test kho where a check for Kernel Hardware Observability KHO enablement is missing. Without verifying KHO is enabled before issuing KHO commands...