CVE-2024-57949

In the Linux kernel, the following vulnerability has been resolved:

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

The following call-chain leads to enabling interrupts in a nested interrupt disabled section:

irq_set_vcpu_affinity() irq_get_desc_lock() raw_spin_lock_irqsave() <--- Disable interrupts its_irq_set_vcpu_affinity() guard(raw_spinlock_irq) <--- Enables interrupts when leaving the guard() irq_put_desc_unlock() <--- Warns because interrupts are enabled

This was broken in commit b97e8a2f7130, which replaced the original raw_spin_[un]lock() pair with guard(raw_spinlock_irq).

Fix the issue by using guard(raw_spinlock).

[ tglx: Massaged change log ]

In the Linux kernel, the following vulnerability has been resolved: irqchip/gic-v3-its: Don't enable interrupts in its_irq_set_vcpu_affinity() The following call-chain leads to enabling interrupts in a nested interrupt disabled section: irq_set_vcpu_affinity() irq_get_desc_lock() raw_spin_lock_irqsave() <--- Disable interrupts its_irq_set_vcpu_affinity() guard(raw_spinlock_irq) <--- Enables interrupts when leaving the guard() irq_put_desc_unlock() <--- Warns because interrupts are enabled This was broken in commit b97e8a2f7130, which replaced the original raw_spin_[un]lock() pair with guard(raw_spinlock_irq). Fix the issue by using guard(raw_spinlock). [ tglx: Massaged change log ]

The Linux Kernel, the operating system core itself.

Security Fix(es):

In the Linux kernel, the following vulnerability has been resolved:

net: wwan: t7xx: Fix FSM command timeout issue

When driver processes the internal state change command, it use an asynchronous thread to process the command operation. If the main thread detects that the task has timed out, the asynchronous thread will panic when executing the completion notification because the main thread completion object has been released.

BUG: unable to handle page fault for address: fffffffffffffff8 PGD 1f283a067 P4D 1f283a067 PUD 1f283c067 PMD 0 Oops: 0000 [#1] PREEMPT SMP NOPTI RIP: 0010:complete_all+0x3e/0xa0 [...] Call Trace: <TASK> ? __die_body+0x68/0xb0 ? page_fault_oops+0x379/0x3e0 ? exc_page_fault+0x69/0xa0 ? asm_exc_page_fault+0x22/0x30 ? complete_all+0x3e/0xa0 fsm_main_thread+0xa3/0x9c0 [mtk_t7xx (HASH:1400 5)] ? __pfx_autoremove_wake_function+0x10/0x10 kthread+0xd8/0x110 ? __pfx_fsm_main_thread+0x10/0x10 [mtk_t7xx (HASH:1400 5)] ? __pfx_kthread+0x10/0x10 ret_from_fork+0x38/0x50 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1b/0x30 </TASK> [...] CR2: fffffffffffffff8 ---[ end trace 0000000000000000 ]---

Use the reference counter to ensure safe release as Sergey suggests: https://lore.kernel.org/all/da90f64c-260a-4329-87bf-1f9ff20a5951@gmail.com/(CVE-2024-39282)

In the Linux kernel, the following vulnerability has been resolved:

i3c: mipi-i3c-hci: Mask ring interrupts before ring stop request

Bus cleanup path in DMA mode may trigger a RING_OP_STAT interrupt when the ring is being stopped. Depending on timing between ring stop request completion, interrupt handler removal and code execution this may lead to a NULL pointer dereference in hci_dma_irq_handler() if it gets to run after the io_data pointer is set to NULL in hci_dma_cleanup().

Prevent this my masking the ring interrupts before ring stop request.(CVE-2024-45828)

In the Linux kernel, the following vulnerability has been resolved:

ethtool: fail closed if we can't get max channel used in indirection tables

Commit 0d1b7d6c9274 ("bnxt: fix crashes when reducing ring count with active RSS contexts") proves that allowing indirection table to contain channels with out of bounds IDs may lead to crashes. Currently the max channel check in the core gets skipped if driver can't fetch the indirection table or when we can't allocate memory.

Both of those conditions should be extremely rare but if they do happen we should try to be safe and fail the channel change.(CVE-2024-46834)

In the Linux kernel, the following vulnerability has been resolved:

wifi: mt76: mt7921: fix NULL pointer access in mt7921_ipv6_addr_change

When disabling wifi mt7921_ipv6_addr_change() is called as a notifier. At this point mvif->phy is already NULL so we cannot use it here.(CVE-2024-46860)

In the Linux kernel, the following vulnerability has been resolved:

usbnet: ipheth: do not stop RX on failing RX callback

RX callbacks can fail for multiple reasons:

• Payload too short
• Payload formatted incorrecly (e.g. bad NCM framing)
• Lack of memory

None of these should cause the driver to seize up.

Make such failures non-critical and continue processing further incoming URBs.(CVE-2024-46861)

In the Linux kernel, the following vulnerability has been resolved:

nvme-rdma: unquiesce admin_q before destroy it

Kernel will hang on destroy admin_q while we create ctrl failed, such as following calltrace:

PID: 23644 TASK: ff2d52b40f439fc0 CPU: 2 COMMAND: "nvme" #0 [ff61d23de260fb78] __schedule at ffffffff8323bc15 #1 [ff61d23de260fc08] schedule at ffffffff8323c014 #2 [ff61d23de260fc28] blk_mq_freeze_queue_wait at ffffffff82a3dba1 #3 [ff61d23de260fc78] blk_freeze_queue at ffffffff82a4113a #4 [ff61d23de260fc90] blk_cleanup_queue at ffffffff82a33006 #5 [ff61d23de260fcb0] nvme_rdma_destroy_admin_queue at ffffffffc12686ce #6 [ff61d23de260fcc8]…

The Linux Kernel, the operating system core itself.

Security Fix(es):

In the Linux kernel, the following vulnerability has been resolved:

net: wwan: t7xx: Fix FSM command timeout issue

When driver processes the internal state change command, it use an asynchronous thread to process the command operation. If the main thread detects that the task has timed out, the asynchronous thread will panic when executing the completion notification because the main thread completion object has been released.

BUG: unable to handle page fault for address: fffffffffffffff8 PGD 1f283a067 P4D 1f283a067 PUD 1f283c067 PMD 0 Oops: 0000 [#1] PREEMPT SMP NOPTI RIP: 0010:complete_all+0x3e/0xa0 [...] Call Trace: <TASK> ? __die_body+0x68/0xb0 ? page_fault_oops+0x379/0x3e0 ? exc_page_fault+0x69/0xa0 ? asm_exc_page_fault+0x22/0x30 ? complete_all+0x3e/0xa0 fsm_main_thread+0xa3/0x9c0 [mtk_t7xx (HASH:1400 5)] ? __pfx_autoremove_wake_function+0x10/0x10 kthread+0xd8/0x110 ? __pfx_fsm_main_thread+0x10/0x10 [mtk_t7xx (HASH:1400 5)] ? __pfx_kthread+0x10/0x10 ret_from_fork+0x38/0x50 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1b/0x30 </TASK> [...] CR2: fffffffffffffff8 ---[ end trace 0000000000000000 ]---

Use the reference counter to ensure safe release as Sergey suggests: https://lore.kernel.org/all/da90f64c-260a-4329-87bf-1f9ff20a5951@gmail.com/(CVE-2024-39282)

In the Linux kernel, the following vulnerability has been resolved:

i3c: mipi-i3c-hci: Mask ring interrupts before ring stop request

Bus cleanup path in DMA mode may trigger a RING_OP_STAT interrupt when the ring is being stopped. Depending on timing between ring stop request completion, interrupt handler removal and code execution this may lead to a NULL pointer dereference in hci_dma_irq_handler() if it gets to run after the io_data pointer is set to NULL in hci_dma_cleanup().

Prevent this my masking the ring interrupts before ring stop request.(CVE-2024-45828)

In the Linux kernel, the following vulnerability has been resolved:

ethtool: fail closed if we can't get max channel used in indirection tables

Commit 0d1b7d6c9274 ("bnxt: fix crashes when reducing ring count with active RSS contexts") proves that allowing indirection table to contain channels with out of bounds IDs may lead to crashes. Currently the max channel check in the core gets skipped if driver can't fetch the indirection table or when we can't allocate memory.

Both of those conditions should be extremely rare but if they do happen we should try to be safe and fail the channel change.(CVE-2024-46834)

In the Linux kernel, the following vulnerability has been resolved:

nvme-rdma: unquiesce admin_q before destroy it

Kernel will hang on destroy admin_q while we create ctrl failed, such as following calltrace:

PID: 23644 TASK: ff2d52b40f439fc0 CPU: 2 COMMAND: "nvme" #0 [ff61d23de260fb78] __schedule at ffffffff8323bc15 #1 [ff61d23de260fc08] schedule at ffffffff8323c014 #2 [ff61d23de260fc28] blk_mq_freeze_queue_wait at ffffffff82a3dba1 #3 [ff61d23de260fc78] blk_freeze_queue at ffffffff82a4113a #4 [ff61d23de260fc90] blk_cleanup_queue at ffffffff82a33006 #5 [ff61d23de260fcb0] nvme_rdma_destroy_admin_queue at ffffffffc12686ce #6 [ff61d23de260fcc8] nvme_rdma_setup_ctrl at ffffffffc1268ced #7 [ff61d23de260fd28] nvme_rdma_create_ctrl at ffffffffc126919b #8 [ff61d23de260fd68] nvmf_dev_write at ffffffffc024f362 #9 [ff61d23de260fe38] vfs_write at ffffffff827d5f25 RIP: 00007fda7891d574 RSP: 00007ffe2ef06958 RFLAGS: 00000202 RAX: ffffffffffffffda RBX: 000055e8122a4d90 RCX: 00007fda7891d574 RDX: 000000000000012b RSI: 000055e8122a4d90 RDI: 0000000000000004 RBP: 00007ffe2ef079c0 R8: 000000000000012b R9: 000055e8122a4d90 R10: 0000000000000000 R11: 0000000000000202 R12: 0000000000000004 R13: 000055e8122923c0 R14: 000000000000012b R15: 00007fda78a54500 ORIG_RAX: 0000000000000001 CS: 0033 SS: 002b

This due to we have…

In the Linux kernel, the following vulnerability has been resolved: irqchip/gic-v3-its: Don't enable interrupts in its_irq_set_vcpu_affinity() The following call-chain leads to enabling interrupts in a nested interrupt disabled section: irq_set_vcpu_affinity() irq_get_desc_lock() raw_spin_lock_irqsave() <--- Disable interrupts its_irq_set_vcpu_affinity() guard(raw_spinlock_irq) <--- Enables interrupts when leaving the guard() irq_put_desc_unlock() <--- Warns because interrupts are enabled This was broken in commit b97e8a2f7130, which replaced the original raw_spin_[un]lock() pair with guard(raw_spinlock_irq). Fix the issue by using guard(raw_spinlock). [ tglx: Massaged change log ]

Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system. This update corrects flaws in the following subsystems:

• GPIO subsystem;
• GPU drivers;
• IRQ chip drivers;
• Network drivers;
• Mellanox network drivers;
• x86 platform drivers;
• i.MX PM domains;
• SCSI subsystem;
• USB Serial drivers;
• AFS file system;
• GFS2 file system;
• File systems infrastructure;
• Proc file system;
• SMB network file system;
• Timer subsystem;
• Kernel CPU control infrastructure;
• Memory management;
• Networking core;
• Ethtool driver;
• IEEE 802.15.4 subsystem;
• Open vSwitch;
• Network traffic control;
• VMware vSockets driver; (CVE-2025-21685, CVE-2025-21684, CVE-2025-21756, CVE-2025-21670, CVE-2024-57949, CVE-2025-21677, CVE-2025-21680, CVE-2025-21703, CVE-2024-57952, CVE-2025-21674, CVE-2025-21701, CVE-2025-21691, CVE-2025-21689, CVE-2025-21668, CVE-2025-21665, CVE-2025-21683, CVE-2025-21675, CVE-2025-21672, CVE-2024-57948, CVE-2025-21669, CVE-2025-21673, CVE-2025-21692, CVE-2025-21699, CVE-2025-21702, CVE-2025-21682, CVE-2025-21690, CVE-2025-21681, CVE-2025-21695, CVE-2025-21696, CVE-2025-21700, CVE-2025-21678, CVE-2025-21676, CVE-2024-57950, CVE-2025-21666, CVE-2025-21694, CVE-2025-21693, CVE-2025-21993, CVE-2024-57951, CVE-2025-21697, CVE-2025-21667)

It was discovered that the CIFS network file system implementation in the Linux kernel did not properly verify the target namespace when handling upcalls. An attacker could use this to expose sensitive information. (CVE-2025-2312)

Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system. This update corrects flaws in the following subsystems:

• GPIO subsystem;
• GPU drivers;
• IRQ chip drivers;
• Network drivers;
• Mellanox network drivers;
• x86 platform drivers;
• i.MX PM domains;
• SCSI subsystem;
• USB Serial drivers;
• AFS file system;
• GFS2 file system;
• File systems infrastructure;
• Proc file system;
• SMB network file system;
• Timer subsystem;
• Kernel CPU control infrastructure;
• Memory management;
• Networking core;
• Ethtool driver;
• IEEE 802.15.4 subsystem;
• Open vSwitch;
• Network traffic control;
• VMware vSockets driver; (CVE-2025-21694, CVE-2025-21993, CVE-2025-21684, CVE-2025-21681, CVE-2025-21675, CVE-2025-21672, CVE-2025-21696, CVE-2025-21691, CVE-2025-21683, CVE-2025-21666, CVE-2025-21682, CVE-2025-21697, CVE-2025-21668, CVE-2025-21701, CVE-2025-21670, CVE-2025-21676, CVE-2025-21695, CVE-2025-21692, CVE-2025-21674, CVE-2025-21699, CVE-2024-57948, CVE-2025-21677, CVE-2024-57951, CVE-2025-21702, CVE-2025-21700, CVE-2024-57949, CVE-2025-21669, CVE-2025-21703, CVE-2025-21756, CVE-2025-21667, CVE-2024-57952, CVE-2024-57950, CVE-2025-21685, CVE-2025-21693, CVE-2025-21678, CVE-2025-21665, CVE-2025-21680, CVE-2025-21689, CVE-2025-21690, CVE-2025-21673)

It was discovered that the CIFS network file system implementation in the Linux kernel did not properly verify the target namespace when handling upcalls. An attacker could use this to expose sensitive information. (CVE-2025-2312)

Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system. This update corrects flaws in the following subsystems:

• GPIO subsystem;
• GPU drivers;
• InfiniBand drivers;
• IRQ chip drivers;
• Network drivers;
• Mellanox network drivers;
• i.MX PM domains;
• SCSI subsystem;
• USB Serial drivers;
• AFS file system;
• GFS2 file system;
• File systems infrastructure;
• File system notification infrastructure;
• Overlay file system;
• Proc file system;
• SMB network file system;
• Timer subsystem;
• Kernel CPU control infrastructure;
• Memory management;
• Networking core;
• DCCP (Datagram Congestion Control Protocol);
• IPv6 networking;
• IEEE 802.15.4 subsystem;
• Open vSwitch;
• Network traffic control;
• VMware vSockets driver; (CVE-2025-21943, CVE-2025-21672, CVE-2024-57952, CVE-2024-57949, CVE-2025-21683, CVE-2025-21690, CVE-2025-21699, CVE-2025-21676, CVE-2024-57924, CVE-2025-21694, CVE-2024-57948, CVE-2025-21675, CVE-2024-57951, CVE-2025-21692, CVE-2025-21684, CVE-2025-21668, CVE-2025-21665, CVE-2025-21667, CVE-2025-21670, CVE-2025-21674, CVE-2025-21697, CVE-2024-53124, CVE-2025-21666, CVE-2025-21682, CVE-2025-21680, CVE-2025-21681, CVE-2025-21691, CVE-2025-21669, CVE-2025-21673, CVE-2024-50157, CVE-2025-21689, CVE-2025-21678)

It was discovered that the CIFS network file system implementation in the Linux kernel did not properly verify the target namespace when handling upcalls. An attacker could use this to expose sensitive information. (CVE-2025-2312)

Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system. This update corrects flaws in the following subsystems:

• GPIO subsystem;
• GPU drivers;
• InfiniBand drivers;
• IRQ chip drivers;
• Network drivers;
• Mellanox network drivers;
• i.MX PM domains;
• SCSI subsystem;
• USB Serial drivers;
• AFS file system;
• GFS2 file system;
• File systems infrastructure;
• File system notification infrastructure;
• Overlay file system;
• Proc file system;
• SMB network file system;
• Timer subsystem;
• Kernel CPU control infrastructure;
• Memory management;
• Networking core;
• DCCP (Datagram Congestion Control Protocol);
• IPv6 networking;
• IEEE 802.15.4 subsystem;
• Open vSwitch;
• Network traffic control;
• VMware vSockets driver; (CVE-2025-21943, CVE-2025-21672, CVE-2024-57952, CVE-2024-57949, CVE-2025-21683, CVE-2025-21690, CVE-2025-21699, CVE-2025-21676, CVE-2024-57924, CVE-2025-21694, CVE-2024-57948, CVE-2025-21675, CVE-2024-57951, CVE-2025-21692, CVE-2025-21684, CVE-2025-21668, CVE-2025-21665, CVE-2025-21667, CVE-2025-21670, CVE-2025-21674, CVE-2025-21697, CVE-2024-53124, CVE-2025-21666, CVE-2025-21682, CVE-2025-21680, CVE-2025-21681, CVE-2025-21691, CVE-2025-21669, CVE-2025-21673, CVE-2024-50157, CVE-2025-21689, CVE-2025-21678)

It was discovered that the CIFS network file system implementation in the Linux kernel did not properly verify the target namespace when handling upcalls. An attacker could use this to expose sensitive information. (CVE-2025-2312)

Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system. This update corrects flaws in the following subsystems:

• GPIO subsystem;
• GPU drivers;
• InfiniBand drivers;
• IRQ chip drivers;
• Network drivers;
• Mellanox network drivers;
• i.MX PM domains;
• SCSI subsystem;
• USB Serial drivers;
• AFS file system;
• GFS2 file system;
• File systems infrastructure;
• File system notification infrastructure;
• Overlay file system;
• Proc file system;
• SMB network file system;
• Timer subsystem;
• Kernel CPU control infrastructure;
• Memory management;
• Networking core;
• DCCP (Datagram Congestion Control Protocol);
• IPv6 networking;
• IEEE 802.15.4 subsystem;
• Open vSwitch;
• Network traffic control;
• VMware vSockets driver; (CVE-2025-21943, CVE-2025-21672, CVE-2024-57952, CVE-2024-57949, CVE-2025-21683, CVE-2025-21690, CVE-2025-21699, CVE-2025-21676, CVE-2024-57924, CVE-2025-21694, CVE-2024-57948, CVE-2025-21675, CVE-2024-57951, CVE-2025-21692, CVE-2025-21684, CVE-2025-21668, CVE-2025-21665, CVE-2025-21667, CVE-2025-21670, CVE-2025-21674, CVE-2025-21697, CVE-2024-53124, CVE-2025-21666, CVE-2025-21682, CVE-2025-21680, CVE-2025-21681, CVE-2025-21691, CVE-2025-21669, CVE-2025-21673, CVE-2024-50157, CVE-2025-21689, CVE-2025-21678)

It was discovered that the CIFS network file system implementation in the Linux kernel did not properly verify the target namespace when handling upcalls. An attacker could use this to expose sensitive information. (CVE-2025-2312)

Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system. This update corrects flaws in the following subsystems:

• GPIO subsystem;
• GPU drivers;
• InfiniBand drivers;
• IRQ chip drivers;
• Network drivers;
• Mellanox network drivers;
• i.MX PM domains;
• SCSI subsystem;
• USB Serial drivers;
• AFS file system;
• GFS2 file system;
• File systems infrastructure;
• File system notification infrastructure;
• Overlay file system;
• Proc file system;
• SMB network file system;
• Timer subsystem;
• Kernel CPU control infrastructure;
• Memory management;
• Networking core;
• DCCP (Datagram Congestion Control Protocol);
• IPv6 networking;
• IEEE 802.15.4 subsystem;
• Open vSwitch;
• Network traffic control;
• VMware vSockets driver; (CVE-2025-21943, CVE-2025-21672, CVE-2024-57952, CVE-2024-57949, CVE-2025-21683, CVE-2025-21690, CVE-2025-21699, CVE-2025-21676, CVE-2024-57924, CVE-2025-21694, CVE-2024-57948, CVE-2025-21675, CVE-2024-57951, CVE-2025-21692, CVE-2025-21684, CVE-2025-21668, CVE-2025-21665, CVE-2025-21667, CVE-2025-21670, CVE-2025-21674, CVE-2025-21697, CVE-2024-53124, CVE-2025-21666, CVE-2025-21682, CVE-2025-21680, CVE-2025-21681, CVE-2025-21691, CVE-2025-21669, CVE-2025-21673, CVE-2024-50157, CVE-2025-21689, CVE-2025-21678)

It was discovered that the CIFS network file system implementation in the Linux kernel did not properly verify the target namespace when handling upcalls. An attacker could use this to expose sensitive information. (CVE-2025-2312)

Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system. This update corrects flaws in the following subsystems:

• GPIO subsystem;
• GPU drivers;
• InfiniBand drivers;
• IRQ chip drivers;
• Network drivers;
• Mellanox network drivers;
• i.MX PM domains;
• SCSI subsystem;
• USB Serial drivers;
• AFS file system;
• GFS2 file system;
• File systems infrastructure;
• File system notification infrastructure;
• Overlay file system;
• Proc file system;
• SMB network file system;
• Timer subsystem;
• Kernel CPU control infrastructure;
• Memory management;
• Networking core;
• DCCP (Datagram Congestion Control Protocol);
• IPv6 networking;
• IEEE 802.15.4 subsystem;
• Open vSwitch;
• Network traffic control;
• VMware vSockets driver; (CVE-2025-21943, CVE-2025-21672, CVE-2024-57952, CVE-2024-57949, CVE-2025-21683, CVE-2025-21690, CVE-2025-21699, CVE-2025-21676, CVE-2024-57924, CVE-2025-21694, CVE-2024-57948, CVE-2025-21675, CVE-2024-57951, CVE-2025-21692, CVE-2025-21684, CVE-2025-21668, CVE-2025-21665, CVE-2025-21667, CVE-2025-21670, CVE-2025-21674, CVE-2025-21697, CVE-2024-53124, CVE-2025-21666, CVE-2025-21682, CVE-2025-21680, CVE-2025-21681, CVE-2025-21691, CVE-2025-21669, CVE-2025-21673, CVE-2024-50157, CVE-2025-21689, CVE-2025-21678)

Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system. This update corrects flaws in the following subsystems:

• GPIO subsystem;
• GPU drivers;
• InfiniBand drivers;
• IRQ chip drivers;
• Network drivers;
• Mellanox network drivers;
• i.MX PM domains;
• SCSI subsystem;
• USB Serial drivers;
• AFS file system;
• GFS2 file system;
• File systems infrastructure;
• File system notification infrastructure;
• Overlay file system;
• Proc file system;
• SMB network file system;
• Timer subsystem;
• Kernel CPU control infrastructure;
• Memory management;
• Networking core;
• DCCP (Datagram Congestion Control Protocol);
• IPv6 networking;
• IEEE 802.15.4 subsystem;
• Open vSwitch;
• Network traffic control;
• VMware vSockets driver; (CVE-2025-21675, CVE-2025-21697, CVE-2025-21668, CVE-2024-57951, CVE-2025-21680, CVE-2024-50157, CVE-2025-21699, CVE-2025-21669, CVE-2025-21678, CVE-2025-21665, CVE-2024-57924, CVE-2024-57949, CVE-2024-53124, CVE-2025-21684, CVE-2025-21676, CVE-2025-21672, CVE-2025-21682, CVE-2025-21670, CVE-2025-21690, CVE-2025-21673, CVE-2025-21691, CVE-2024-57952, CVE-2025-21674, CVE-2025-21689, CVE-2025-21943, CVE-2025-21692, CVE-2025-21667, CVE-2025-21666, CVE-2024-57948, CVE-2025-21694, CVE-2025-21683, CVE-2025-21681)

Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system. This update corrects flaws in the following subsystems:

• GPIO subsystem;
• GPU drivers;
• InfiniBand drivers;
• IRQ chip drivers;
• Network drivers;
• Mellanox network drivers;
• i.MX PM domains;
• SCSI subsystem;
• USB Serial drivers;
• AFS file system;
• GFS2 file system;
• File systems infrastructure;
• File system notification infrastructure;
• Overlay file system;
• Proc file system;
• SMB network file system;
• Timer subsystem;
• Kernel CPU control infrastructure;
• Memory management;
• Networking core;
• DCCP (Datagram Congestion Control Protocol);
• IPv6 networking;
• IEEE 802.15.4 subsystem;
• Open vSwitch;
• Network traffic control;
• VMware vSockets driver; (CVE-2025-21675, CVE-2025-21697, CVE-2025-21668, CVE-2024-57951, CVE-2025-21680, CVE-2024-50157, CVE-2025-21699, CVE-2025-21669, CVE-2025-21678, CVE-2025-21665, CVE-2024-57924, CVE-2024-57949, CVE-2024-53124, CVE-2025-21684, CVE-2025-21676, CVE-2025-21672, CVE-2025-21682, CVE-2025-21670, CVE-2025-21690, CVE-2025-21673, CVE-2025-21691, CVE-2024-57952, CVE-2025-21674, CVE-2025-21689, CVE-2025-21943, CVE-2025-21692, CVE-2025-21667, CVE-2025-21666, CVE-2024-57948, CVE-2025-21694, CVE-2025-21683, CVE-2025-21681)

It was discovered that the CIFS network file system implementation in the Linux kernel did not properly verify the target namespace when handling upcalls. An attacker could use this to expose sensitive information. (CVE-2025-2312)

Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system. This update corrects flaws in the following subsystems:

• PowerPC architecture;
• S390 architecture;
• Block layer subsystem;
• Serial ATA and Parallel ATA drivers;
• Drivers core;
• Network block device driver;
• Character device driver;
• TPM device driver;
• Clock framework and drivers;
• FireWire subsystem;
• GPIO subsystem;
• GPU drivers;
• HID subsystem;
• I3C subsystem;
• InfiniBand drivers;
• IOMMU subsystem;
• IRQ chip drivers;
• Media drivers;
• NVIDIA Tegra memory controller driver;
• Fastrpc Driver;
• Network drivers;
• Mellanox network drivers;
• Operating Performance Points (OPP) driver;
• PCI subsystem;
• x86 platform drivers;
• i.MX PM domains;
• PPS (Pulse Per Second) driver;
• PTP clock framework;
• Remote Processor subsystem;
• Real Time Clock drivers;
• SCSI subsystem;
• QCOM SoC drivers;
• Media staging drivers;
• TTY drivers;
• UFS subsystem;
• USB Gadget drivers;
• USB Host Controller drivers;
• USB Serial drivers;
• AFS file system;
• File systems infrastructure;
• BTRFS file system;
• F2FS file system;
• GFS2 file system;
• NILFS2 file system;
• File system notification infrastructure;
• Overlay file system;
• Proc file system;
• SMB network file system;
• UBI file system;
• Timer subsystem;
• KVM subsystem;
• Networking core;
• ptr_ring data structure definitions;
• Networking subsytem;
• Amateur Radio drivers;
• XFRM subsystem;
• Tracing infrastructure;
• BPF subsystem;
• Kernel CPU control infrastructure;
• Padata parallel execution mechanism;
• printk logging mechanism;
• Memory management;
• Bluetooth subsystem;
• DCCP (Datagram Congestion Control Protocol);
• IPv4 networking;
• IPv6 networking;
• MAC80211 subsystem;
• IEEE 802.15.4 subsystem;
• Multipath TCP;
• Netfilter;
• NFC subsystem;
• Open vSwitch;
• Rose network layer;
• RxRPC session sockets;
• Network traffic control;
• VMware vSockets driver;
• Landlock security;
• Linux Security Modules (LSM) Framework;
• Tomoyo security module;
• SoC audio core drivers; (CVE-2025-21830, CVE-2025-21678, CVE-2025-21815, CVE-2024-57974, CVE-2025-21725, CVE-2025-21718, CVE-2025-21748, CVE-2025-21732, CVE-2024-57953, CVE-2025-21727, CVE-2025-21816, CVE-2025-21719, CVE-2024-53124, CVE-2024-58019, CVE-2025-38001, CVE-2025-21720, CVE-2025-21734, CVE-2025-21672, CVE-2025-21692, CVE-2024-58076, CVE-2025-21694, CVE-2024-58061, CVE-2025-21714, CVE-2025-21689, CVE-2024-49887, CVE-2024-57949, CVE-2025-38177, CVE-2025-21683, CVE-2025-21669, CVE-2025-21722, CVE-2024-57980, CVE-2025-38000, CVE-2025-37932, CVE-2024-58034, CVE-2024-58081, CVE-2025-21733, CVE-2025-21682, CVE-2024-57924, CVE-2025-21743, CVE-2024-57975, CVE-2025-37798, CVE-2024-58058, CVE-2025-21809, CVE-2025-21676, CVE-2024-57993, CVE-2025-21699, CVE-2024-58016, CVE-2025-21832, CVE-2025-21804, CVE-2024-58011, CVE-2024-58007, CVE-2025-21826, CVE-2024-58055, CVE-2025-21668, CVE-2025-21715, CVE-2024-58078, CVE-2025-21829, CVE-2025-21811, CVE-2025-21814, CVE-2024-58053, CVE-2025-21726, CVE-2025-21943, CVE-2025-37750, CVE-2025-21673, CVE-2024-57984, CVE-2025-37997, CVE-2025-21684, CVE-2025-21750, CVE-2024-58013, CVE-2025-21799, CVE-2024-58083, CVE-2025-21798, CVE-2025-21731, CVE-2025-21708, CVE-2024-57986, CVE-2025-21744, CVE-2024-58014, CVE-2025-21721, CVE-2024-58063, CVE-2024-57979, CVE-2024-58005, CVE-2025-21728, CVE-2025-21681, CVE-2025-21806, CVE-2024-57982, CVE-2024-58002, CVE-2024-58082, CVE-2025-21812, CVE-2025-21745, CVE-2024-58017, CVE-2025-21665, CVE-2025-21828, CVE-2025-37890,…