2026-09-16
2026-09-16 11:17Z
CRIT

CVE-2026-89918 — Linux: In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: Correctly handle

NVD (auto-promoted CVEs)·nvd.nist.govCVE-2026-89918

In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: Correctly handle end of VA space TLBI invalidation Our TLB invalidation by VA code is based on comparing two ranges, one defined by the TLB, and one defined by the TLBI instruction. Each range is defined by a start and a size. However, the way the comparison is done doesn't account for address rollover, as it compares an address with (base + size). This works nicely until this expression repres CVSSv3.1 9.3 (CRITICAL)

TYPVulnerability
9.3
CVSS v3.1
97
Edit Score
2026-09-16
2026-09-16 11:17Z
CRIT

CVE-2026-89916 — Linux: In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: Make VNCR

NVD (auto-promoted CVEs)·nvd.nist.govCVE-2026-89916

In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: Make VNCR invalidation participate in MMU invalidation retry A VNCR TLB invalidation can occur on one vcpu while another vcpu is faulting in this same page. Without correctly handling this, we can end up with the following scenario: - vcpu A walks the PTs to translate VNCR - before vcpu A is able to grab the MMU lock to insert the TLB, vcpu B updates the S1 PTs with an invalid entry, and issu CVSSv3.1 9.3 (CRITICAL)

TYPVulnerability
9.3
CVSS v3.1
97
Edit Score
2026-09-16
2026-09-16 11:17Z
CRIT

CVE-2026-89915 — Linux: Checking this counter to decide whether a TLB needs to be invalidated may result

NVD (auto-promoted CVEs)·nvd.nist.govCVE-2026-89915

In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: Remove VM-wide VNCR mapping counter The global VNCR mapping counter is used to decide whether an L1 provided VNCR page is mapped in L0 on any CPU at the point of dealing with a TLB invalidation. It is incremented when a mapping is made in the fixmap, and decremented when unmapped. As it turns out, this tracking has several flaws: - we are trying to invalidate TLBs, and the mapping is only an CVSSv3.1 9.3 (CRITICAL)

TYPVulnerability
9.3
CVSS v3.1
97
Edit Score
2026-09-16
2026-09-16 11:17Z
CRIT

CVE-2026-89914 — Linux: In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: Sign-extend VA

NVD (auto-promoted CVEs)·nvd.nist.govCVE-2026-89914

In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: Sign-extend VA for range-based TLBI invalidation When the decode_range_tlbi() helper was moved to be used for S1 TLBIs, the required sign extension was omitted. Add it. As a result, special care must be taken to not overflow PA bits when this is used for S2 invalidation. CVSSv3.1 9.3 (CRITICAL)

TYPVulnerability
9.3
CVSS v3.1
97
Edit Score
2026-09-16
2026-09-16 11:17Z
HIGH

CVE-2026-89913 — Linux: A concurrent path can trigger this race: the irqfd cached injection path (vgic_its_inject_cached_translation) obtains

NVD (auto-promoted CVEs)·nvd.nist.govCVE-2026-89913

In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: vgic-v3: take an LPI reference in vgic_v3_save_pending_tables vgic_v3_save_pending_tables() iterates dist->lpi_xa using xa_for_each() and dereferences the returned struct vgic_irq in the loop body without holding a reference on the LPI. The xarray iterator only provides temporary RCU coverage while looking up the current entry. That is not sufficient for this loop body, which reads fields from CVSSv3.1 8.8 (HIGH)

TYPVulnerability
8.8
CVSS v3.1
94
Edit Score
2026-09-16
2026-09-16 11:16Z
HIGH

CVE-2026-89908 — Linux: In the Linux kernel, the following vulnerability has been resolved: LoongArch: KVM: Preserve memslot

NVD (auto-promoted CVEs)·nvd.nist.govCVE-2026-89908

In the Linux kernel, the following vulnerability has been resolved: LoongArch: KVM: Preserve memslot arch flags on KVM_MR_FLAGS_ONLY kvm_arch_prepare_memory_region() computes new->arch.flags, i.e. whether a memslot is KVM_MEM_HUGEPAGE_CAPABLE or KVM_MEM_HUGEPAGE_INCAPABLE, only for KVM_MR_CREATE and KVM_MR_MOVE, and returns early for every other change. But the generic code allocates a zeroed memslot for every change and never copies old->arch, so after a KVM_MR_FLAGS_ONLY CVSSv3.1 8.8 (HIGH)

TYPVulnerability
8.8
CVSS v3.1
94
Edit Score
2026-09-16
2026-09-16 11:16Z
HIGH

CVE-2026-89907 — Linux: In the Linux kernel, the following vulnerability has been resolved: LoongArch: KVM: Validate MSI

NVD (auto-promoted CVEs)·nvd.nist.govCVE-2026-89907

In the Linux kernel, the following vulnerability has been resolved: LoongArch: KVM: Validate MSI data before routing it to EIOINTC pch_msi_set_irq() passes e->msi.data straight into eiointc_set_irq() as the irq number. The MSI data comes from userspace, that either via a KVM_IRQ_ROUTING_MSI entry set with KVM_SET_GSI_ROUTING (used by irqfd and KVM_IRQ_LINE) or directly via KVM_SIGNAL_MSI, and is never checked against EIOINTC_IRQS. eiointc_set_irq() uses the value with __se CVSSv3.1 8.8 (HIGH)

TYPVulnerability
8.8
CVSS v3.1
94
Edit Score
728 × 90 / responsive · programmatic ad slot
2026-09-16
2026-09-16 11:16Z
HIGH

CVE-2026-89904 — Linux: In the Linux kernel, the following vulnerability has been resolved: LoongArch: Fix acpi_package_ids[] array

NVD (auto-promoted CVEs)·nvd.nist.govCVE-2026-89904

In the Linux kernel, the following vulnerability has been resolved: LoongArch: Fix acpi_package_ids[] array overflow With LoongArch virt machine, a typical setting is one core per socket, there will max 256 sockets (packages) on one VM. With PPTT acpi table, array acpi_package_ids[] will be overflowed. Here change the array size of acpi_package_ids[] with the max value of MAX_PACKAGES and KVM_MAX_VCPUS. CVSSv3.1 8.4 (HIGH)

TYPVulnerability
8.4
CVSS v3.1
92
Edit Score
2026-09-16
2026-09-16 11:16Z
HIGH

CVE-2026-89898 — Linux: In the Linux kernel, the following vulnerability has been resolved: media: cec: extron-da-hd-4k-plus: add

NVD (auto-promoted CVEs)·nvd.nist.govCVE-2026-89898

In the Linux kernel, the following vulnerability has been resolved: media: cec: extron-da-hd-4k-plus: add sanity check Add check to prevent overflowing msg.msg[] in case the incoming data is malformed. CVSSv3.1 8.8 (HIGH)

TYPVulnerability
8.8
CVSS v3.1
94
Edit Score
2026-09-16
2026-09-16 11:16Z
HIGH

CVE-2026-89885 — Linux: In the Linux kernel, the following vulnerability has been resolved: media: platform: mtk-mdp3: Fix

NVD (auto-promoted CVEs)·nvd.nist.govCVE-2026-89885

In the Linux kernel, the following vulnerability has been resolved: media: platform: mtk-mdp3: Fix SCP device refcounting mdp_probe() first tries to get the SCP handle with scp_get(). When that fails, it falls back to looking up the SCP platform device with __get_pdev_by_id() and then reads its driver data. The fallback lookup returns the platform device with a reference, just like scp_get() does. However, the fallback path currently drops that reference immediately after CVSSv3.1 8.4 (HIGH)

TYPVulnerability
8.4
CVSS v3.1
92
Edit Score
2026-09-16
2026-09-16 11:16Z
HIGH

CVE-2026-89877 — Linux: In the Linux kernel, the following vulnerability has been resolved: media: saa7164: fix cleanup

NVD (auto-promoted CVEs)·nvd.nist.govCVE-2026-89877

In the Linux kernel, the following vulnerability has been resolved: media: saa7164: fix cleanup on resource allocation failure saa7164_dev_setup() adds the device to the global saa7164_devlist before requesting the PCI BAR memory regions. If get_resources() fails, saa7164_dev_setup() decrements the device count and returns an error, but leaves the device on saa7164_devlist. The probe error path then frees the device, leaving a dangling entry on the global list. Reuse the CVSSv3.1 8.4 (HIGH)

TYPVulnerability
8.4
CVSS v3.1
92
Edit Score
2026-09-16
2026-09-16 11:16Z
HIGH

CVE-2026-89861 — Linux: No reference is taken across that window, so a concurrent qla24xx_deallocate_vp_id() can tear the

NVD (auto-promoted CVEs)·nvd.nist.govCVE-2026-89861

In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Hold vport reference in qla24xx_report_id_acquisition() In the format 1 path, the virtual port is located on ha->vp_list while holding vport_slock, but the lock is dropped before vp is used: qla_update_host_map() is called and VP_IDX_ACQUIRED/REGISTER_FC4_NEEDED/ REGISTER_FDMI_NEEDED are set on vp. No reference is taken across that window, so a concurrent qla24xx_deallocate_vp_id() can tear t CVSSv3.1 8.1 (HIGH)

TYPVulnerability
8.1
CVSS v3.1
91
Edit Score
2026-09-16
2026-09-16 11:16Z
HIGH

CVE-2026-89860 — Linux: If an abort is issued more than once for the same command (for example

NVD (auto-promoted CVEs)·nvd.nist.govCVE-2026-89860

In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Initialize NVMe abort_work once at submission qla_nvme_fcp_abort() and qla_nvme_ls_abort() ran INIT_WORK() on priv->abort_work immediately before schedule_work(). INIT_WORK() reinitializes the work_struct, resetting its list head and clearing the pending bit. If an abort is issued more than once for the same command (for example, concurrent transport teardown and a timeout-driven abort), the CVSSv3.1 8.8 (HIGH)

TYPVulnerability
8.8
CVSS v3.1
94
Edit Score
2026-09-16
2026-09-16 11:16Z
CRIT

CVE-2026-89857 — Linux: In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Hold qpair

NVD (auto-promoted CVEs)·nvd.nist.govCVE-2026-89857

In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Hold qpair lock when sending NVMe LS reject qla_nvme_ls_reject_iocb() allocates from and advances the request ring through __qla2x00_alloc_iocbs() (which assumes the hardware_lock is held) and qla2x00_start_iocbs() (which advances the ring and rings the request-in doorbell), but takes no lock itself. Two of its callers invoke it without the producer lock held: - qla_nvme_xmt_ls_rsp(), the N CVSSv3.1 9.8 (CRITICAL)

TYPVulnerability
9.8
CVSS v3.1
99
Edit Score
2026-09-16
2026-09-16 11:16Z
HIGH

CVE-2026-89856 — Linux: In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Clamp MSI-X

NVD (auto-promoted CVEs)·nvd.nist.govCVE-2026-89856

In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Clamp MSI-X derived queue counts to avoid truncation ha->msix_count is u16, but ha->max_req_queues, ha->max_rsp_queues and ha->max_qpairs are u8. Deriving the queue count as "ha->max_req_queues = ha->msix_count - 1" therefore truncates: a board (or a misconfigured/malicious hot-plugged device) advertising 257 MSI-X vectors yields msix_count - 1 == 256, which truncates to 0. An MSI-X count of CVSSv3.1 8.4 (HIGH)

TYPVulnerability
8.4
CVSS v3.1
92
Edit Score
2026-09-16
2026-09-16 11:16Z
HIGH

CVE-2026-89849 — Linux: In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Reject non-SCSI

NVD (auto-promoted CVEs)·nvd.nist.govCVE-2026-89849

In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Reject non-SCSI SRB on status IOCB fast path qla2x00_status_entry() filters out non-TYPE_SRB entries and the SRB_NVME_CMD, SRB_BIDI_CMD and SRB_TM_CMD types, then falls through to a SCSI fast path that assumes the command is an SRB_SCSI_CMD. The first thing on that path, qla_chk_edif_rx_sa_delete_pending(), and the subsequent handling both evaluate GET_CMD_SP(sp), i.e. sp->u.scmd.cmd. The sr CVSSv3.1 8.8 (HIGH)

TYPVulnerability
8.8
CVSS v3.1
94
Edit Score
2026-09-16
2026-09-16 11:16Z
HIGH

CVE-2026-89848 — Linux: In that window the response interrupt can still fire, qla2xxx_msix_rsp_q() queues qpair->q_work, and qla_do_work()

NVD (auto-promoted CVEs)·nvd.nist.govCVE-2026-89848

In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Quiesce response IRQ before freeing request queue qla2xxx_delete_qpair() deletes the request queue before the response queue. qla25xx_delete_req_que() frees the request queue memory (kfree(req) in qla25xx_free_req_que()), but the response-queue MSI-X is only released later, in qla25xx_free_rsp_que(). In that window the response interrupt can still fire, qla2xxx_msix_rsp_q() queues qpair->q_wo CVSSv3.1 8.1 (HIGH)

TYPVulnerability
8.1
CVSS v3.1
91
Edit Score
2026-09-16
2026-09-16 11:16Z
CRIT

CVE-2026-89847 — Linux: The timeout then issues a second sp->done() -> qla_ctrlvp_sp_done(), which evaluates "if (sp->comp) complete(sp->comp)"

NVD (auto-promoted CVEs)·nvd.nist.govCVE-2026-89847

In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Avoid double completion in async IOCB timeout qla2x00_async_iocb_timeout() tries to abort a timed-out async IOCB. When qla24xx_async_abort_cmd() fails, both the SRB_LOGIN_CMD path and the SRB_CTRL_VP/default path scan outstanding_cmds[] for the SRB and then call sp->done(sp, QLA_FUNCTION_TIMEOUT) unconditionally, without checking whether the SRB was actually found and removed. If the respons CVSSv3.1 9.8 (CRITICAL)

TYPVulnerability
9.8
CVSS v3.1
99
Edit Score
2026-09-16
2026-09-16 11:16Z
CRIT

CVE-2026-89846 — Linux: A hostile or buggy target reporting an rsp_info_len larger than par_sense_len makes the unsigned

NVD (auto-promoted CVEs)·nvd.nist.govCVE-2026-89846

In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Bound rsp_info_len to avoid OOB sense-data read In qla2x00_status_entry(), the FWI2 status path advances sense_data and shrinks par_sense_len by rsp_info_len: if (IS_FWI2_CAPABLE(ha)) { sense_data += rsp_info_len; par_sense_len -= rsp_info_len; } rsp_info_len is a 32-bit value taken directly from the target's FCP response (sf.rsp_data_len), while par_sense_len is the IOCB data area si CVSSv3.1 9.1 (CRITICAL)

TYPVulnerability
9.1
CVSS v3.1
96
Edit Score
2026-09-16
2026-09-16 11:16Z
HIGH

CVE-2026-89844 — Linux: In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Hold vport_slock

NVD (auto-promoted CVEs)·nvd.nist.govCVE-2026-89844

In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Hold vport_slock for host map update in report ID acquisition qla24xx_report_id_acquisition() format-1 handling drops vport_slock after taking the vport reference and then calls qla_update_host_map() without the lock. That reaches qla_update_vp_map(), which mutates the ha->host_map btree via btree_insert32()/btree_update32()/btree_remove32() and is documented to require vport_slock to be held CVSSv3.1 8.8 (HIGH)

TYPVulnerability
8.8
CVSS v3.1
94
Edit Score
2026-09-16
2026-09-16 11:16Z
HIGH

CVE-2026-89811 — Linux: This causes a race condition where in-flight DMA descriptors can access memory that has

NVD (auto-promoted CVEs)·nvd.nist.govCVE-2026-89811

In the Linux kernel, the following vulnerability has been resolved: drm/amdkfd: Add TLB flush after MES queue eviction/suspension MES (Micro Engine Scheduler) does not perform heavy-weight TLB invalidation after unmapping queues, unlike HWS which does this automatically. This causes a race condition where in-flight DMA descriptors can access memory that has been unmapped, leading to page faults and GPU queue hangs during SVM page migration. The issue manifests as KFDSVMRan CVSSv3.1 8.8 (HIGH)

TYPVulnerability
8.8
CVSS v3.1
94
Edit Score
2026-09-16
2026-09-16 11:16Z
HIGH

CVE-2026-89806 — Linux: In the Linux kernel, the following vulnerability has been resolved: drm/sysfb: ofdrm: Fix integer

NVD (auto-promoted CVEs)·nvd.nist.govCVE-2026-89806

In the Linux kernel, the following vulnerability has been resolved: drm/sysfb: ofdrm: Fix integer overflow in fb_size calculation The framebuffer size calculation `fb_size = linebytes * height` can overflow when both values are large (e.g., 46341 * 46341 > INT_MAX). Since linebytes and height are both int types, the multiplication is performed as int * int, which results in undefined behavior on overflow. Use check_mul_overflow() to detect and prevent this overflow, consis CVSSv3.1 8.4 (HIGH)

TYPVulnerability
8.4
CVSS v3.1
92
Edit Score
2026-09-16
2026-09-16 11:16Z
HIGH

CVE-2026-89804 — Linux: In the Linux kernel, the following vulnerability has been resolved: drm/nouveau/dmem: fix mismatched DMA

NVD (auto-promoted CVEs)·nvd.nist.govCVE-2026-89804

In the Linux kernel, the following vulnerability has been resolved: drm/nouveau/dmem: fix mismatched DMA unmap size for large folios Device-private THP migration maps migration buffers with page_size() and records that length in dma_info->size. For a compound folio page_size() is PAGE_SIZE << order, but two teardown sites still pass a literal PAGE_SIZE to dma_unmap_page(): - nouveau_dmem_migrate_to_ram() on the success path, and - nouveau_dmem_migrate_copy_one() on th CVSSv3.1 8.8 (HIGH)

TYPVulnerability
8.8
CVSS v3.1
94
Edit Score
2026-09-16
2026-09-16 11:16Z
HIGH

CVE-2026-89795 — Linux: In the Linux kernel, the following vulnerability has been resolved: PCI: Allow per function

NVD (auto-promoted CVEs)·nvd.nist.govCVE-2026-89795

In the Linux kernel, the following vulnerability has been resolved: PCI: Allow per function PCI slots to fix slot reset on s390 On s390 systems, which use a machine level hypervisor, PCI devices are always accessed through a form of PCI pass-through which fundamentally operates on a per PCI function granularity. This is also reflected in the s390 PCI hotplug driver which creates hotplug slots for individual PCI functions. Its reset_slot() function, which is a wrapper for zp CVSSv3.1 8.4 (HIGH)

TYPVulnerability
8.4
CVSS v3.1
92
Edit Score
2026-09-16
2026-09-16 11:16Z
CRIT

CVE-2026-86106 — This could result in elevated command execution on Edge units where HA is enabled.

NVD (auto-promoted CVEs)·nvd.nist.govCVE-2026-86106

An unauthenticated actor with network access to the private HA interconnect may trigger sensitive HA peer functions without verification. This could result in elevated command execution on Edge units where HA is enabled. CVSSv3.1 9.6 (CRITICAL)

CWECWE 306TYPVulnerability
9.6
CVSS v3.1
98
Edit Score