CVE-2025-21878 i2c: npcm: disable interrupt enable bit before devm_request_irq

In the Linux kernel, the following vulnerability has been resolved: i2c: npcm: disable interrupt enable bit before devmrequestirq The customer reports that there is a soft lockup issue related to the i2c driver. After checking, the i2c module was doing a tx transfer and the bmc machine reboots in...

CVE-2025-21878

CVE-2025-21878 relates to the Linux kernel i2c npcm driver. The vulnerability arises from not disabling the interrupt enable bit before calling devm_request_irq, leaving an i2c-related status bit that is read-only and triggers repeated interrupts. This behavior can cause a soft lockup and a reboo...

CVE-2025-21878 i2c: npcm: disable interrupt enable bit before devm_request_irq

In the Linux kernel, the following vulnerability has been resolved: i2c: npcm: disable interrupt enable bit before devmrequestirq The customer reports that there is a soft lockup issue related to the i2c driver. After checking, the i2c module was doing a tx transfer and the bmc machine reboots in...

CVE-2023-52993: NULL Pointer Dereference

In the Linux kernel, the following vulnerability has been resolved: x86/i8259: Mark legacy PIC interrupts with IRQLEVEL Baoquan reported that after triggering a crash the subsequent crash-kernel fails to boot about half of the time. It triggers a NULL pointer dereference in the periodic tick code...

Linux Kernel Security Vulnerabilities

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 the ptdma driver's use of mutex locks in interrupt contexts...

Linux Kernel Security Vulnerabilities

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 imc-pmu's incorrect use of a mutex lock in the IRQ disable zone...

Linux Kernel Security Vulnerabilities

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 the npcm i2c driver not disabling interrupts before requesting IRQs, which could lead to a soft lockup...

Linux Kernel Security Vulnerabilities

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 Linux kernel that stems from not marking a legacy PIC interrupt as IRQLEVEL...

PT-2025-18409

Name of the Vulnerable Software and Affected Versions Linux kernel affected versions not specified Description A memory corruption issue has been identified in the Linux kernel, specifically in the stmmac driver. The problem arises from accessing a freed irq affinity hint, which is caused by the...

Azure Linux 3.0 Security Update: kernel (CVE-2024-45828)

The version of kernel installed on the remote Azure Linux 3.0 host is prior to tested version. It is, therefore, affected by a vulnerability as referenced in the CVE-2024-45828 advisory. - In the Linux kernel, the following vulnerability has been resolved: i3c: mipi-i3c-hci: Mask ring interrupts...

Azure Linux 3.0 Security Update: kernel (CVE-2024-56785)

The version of kernel installed on the remote Azure Linux 3.0 host is prior to tested version. It is, therefore, affected by a vulnerability as referenced in the CVE-2024-56785 advisory. - In the Linux kernel, the following vulnerability has been resolved: MIPS: Loongson64: DTS: Really fix PCIe...

misc: microchip: pci1xxxx: Resolve kernel panic during GPIO IRQ handling

...

irqchip/gic-v3-its: Don't enable interrupts in its_irq_set_vcpu_affinity()

...

CVE-2025-21849

In the Linux kernel, the following vulnerability has been resolved: drm/i915/gt: Use spinlockirqsave in interruptible context spinlock/unlock functions used in interrupt contexts could result in a deadlock, as seen in GitLab issue 13399, which occurs when interrupt comes in while holding a lock...

CVE-2025-21855 ibmvnic: Don't reference skb after sending to VIOS

In the Linux kernel, the following vulnerability has been resolved: ibmvnic: Don't reference skb after sending to VIOS Previously, after successfully flushing the xmit buffer to VIOS, the txbytes stat was incremented by the length of the skb. It is invalid to access the skb memory after sending t...

CVE-2025-21849 drm/i915/gt: Use spin_lock_irqsave() in interruptible context

In the Linux kernel, the following vulnerability has been resolved: drm/i915/gt: Use spinlockirqsave in interruptible context spinlock/unlock functions used in interrupt contexts could result in a deadlock, as seen in GitLab issue 13399, which occurs when interrupt comes in while holding a lock...

CVE-2025-21849 drm/i915/gt: Use spin_lock_irqsave() in interruptible context

In the Linux kernel, the following vulnerability has been resolved: drm/i915/gt: Use spinlockirqsave in interruptible context spinlock/unlock functions used in interrupt contexts could result in a deadlock, as seen in GitLab issue 13399, which occurs when interrupt comes in while holding a lock...

CVE-2025-21849 drm/i915/gt: Use spin_lock_irqsave() in interruptible context

In the Linux kernel, the following vulnerability has been resolved: drm/i915/gt: Use spinlockirqsave in interruptible context spinlock/unlock functions used in interrupt contexts could result in a deadlock, as seen in GitLab issue 13399, which occurs when interrupt comes in while holding a lock...

PT-2025-25823

Name of the Vulnerable Software and Affected Versions Linux kernel affected versions not specified Description A data-race issue has been identified in the Linux kernel, specifically in the virtio ring component. The issue occurs when accessing the event triggered variable, which can lead to a ra...

CVE-2025-21849: Improper Locking

In the Linux kernel, the following vulnerability has been resolved: drm/i915/gt: Use spinlockirqsave in interruptible context spinlock/unlock functions used in interrupt contexts could result in a deadlock, as seen in GitLab issue 13399, which occurs when interrupt comes in while holding a lock...