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

CVE-2026-90036 — Linux: In the Linux kernel, the following vulnerability has been resolved: NFSD: Prevent client use-after-free

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

In the Linux kernel, the following vulnerability has been resolved: NFSD: Prevent client use-after-free during blocked-lock reaping A bare lock owner -- its only remaining reference a blocked lock on nn->blocked_locks_lru -- holds a raw pointer to its nfs4_client but no reference keeping the client alive. When the per-net laundromat reaps such a lock, freeing the nbl drops the owner reference held through flc_owner, and the final nfs4_put_stateowner() takes the client's cl_ CVSSv3.1 9.8 (CRITICAL)

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

CVE-2026-90018 — Linux: For each candidate attribute it only checks that the fixed 4-byte attribute header (2-byte

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

In the Linux kernel, the following vulnerability has been resolved: staging: rtl8723bs: fix OOB read / stack overflow in rtw_get_wps_attr() rtw_get_wps_attr() walks WPS attributes inside a WPS IE taken from a wireless management frame. For each candidate attribute it only checks that the fixed 4-byte attribute header (2-byte ID + 2-byte length) fits inside the IE: if (attr_ptr + 4 > wps_ie + wps_ielen) break; u16 attr_id = get_unaligned_be16(attr_ptr); u16 attr_data_l CVSSv3.1 8.8 (HIGH)

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

CVE-2026-90012 — Linux: In the Linux kernel, the following vulnerability has been resolved: spi: Fix DMA mapping

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

In the Linux kernel, the following vulnerability has been resolved: spi: Fix DMA mapping ownership on partial map failure If RX mapping fails after TX mapping succeeds, __spi_map_msg() unmaps TX but leaves tx_sg_mapped set. If TX mapping fails on a later transfer, mappings created for earlier transfers remain active. In both cases, cur_{tx,rx}_dma_dev have not yet been updated because they are assigned only after every transfer has been mapped. The subsequent spi_unmap_msg CVSSv3.1 9.8 (CRITICAL)

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

CVE-2026-90011 — Linux: In the Linux kernel, the following vulnerability has been resolved: scsi: target: iscsi: Reserve

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

In the Linux kernel, the following vulnerability has been resolved: scsi: target: iscsi: Reserve a terminator byte for the login payload iscsi_target_check_login_request() rejects a login PDU whose DataSegmentLength exceeds MAX_KEY_VALUE_PAIRS, but the test is '>' and login->req_buf is allocated with exactly MAX_KEY_VALUE_PAIRS bytes. Since iscsit_get_login_rx() receives payload_length + padding bytes, where padding = ((-payload_length) & 3); any payload_length from 8189 CVSSv3.1 9.1 (CRITICAL)

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

CVE-2026-90000 — Linux: This does not even need a lying device -- rmi_f01_probe() issues a fixed 21-byte

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

In the Linux kernel, the following vulnerability has been resolved: HID: rmi: fix OOB access with undersized RMI reports The hid-rmi driver sizes its writeReport/readReport buffer purely from the report descriptor supplied by the device, with no minimum bound: data->input_report_size = hid_report_len(input_report); data->output_report_size = hid_report_len(output_report); alloc_size = data->output_report_size + data->input_report_size; data->writeReport = devm_kzalloc CVSSv3.1 8.8 (HIGH)

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

CVE-2026-89999 — Linux: The driver then reads past the received report and forwards the bytes to userspace

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

In the Linux kernel, the following vulnerability has been resolved: HID: wacom: validate report length in wacom_intuos_pro2_bt_irq wacom_intuos_pro2_bt_irq() receives the wire report length in `len` but never consults it before parsing. After the report-id gate it unconditionally calls wacom_intuos_pro2_bt_pen() and then, selected by features.type, a fixed chain of sub-parsers, none of which receive `len`: wacom_intuos_pro2_bt_pen(wacom); if (type == INTUOSP2_BT || type CVSSv3.1 8.1 (HIGH)

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

CVE-2026-89995 — Linux: In the Linux kernel, the following vulnerability has been resolved: dma-direct: return struct page

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

In the Linux kernel, the following vulnerability has been resolved: dma-direct: return struct page from dma_direct_alloc_from_pool() Commit 5b138c534fda ("dma-direct: factor out a dma_direct_alloc_from_pool helper") changed dma_direct_alloc_from_pool() to return the CPU address from dma_alloc_from_pool(). That fits dma_direct_alloc(), but dma_direct_alloc_pages() also uses the helper and expects a struct page *. Fix this by making dma_direct_alloc_from_pool() return the st 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:17Z
HIGH

CVE-2026-89992 — Linux: In the Linux kernel, the following vulnerability has been resolved: cpuidle: dt_idle_genpd: kfree() the

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

In the Linux kernel, the following vulnerability has been resolved: cpuidle: dt_idle_genpd: kfree() the original name allocation dt_idle_pd_alloc() kasprintf()s the full node path, then points pd->name at kbasename() of that string. dt_idle_pd_free() kfree()s pd->name, which is no longer the start of the allocation. Copy the basename instead. CVSSv3.1 8.4 (HIGH)

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

CVE-2026-89990 — Linux: A concurrent session reopen can therefore free the array while it is being inspected

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

In the Linux kernel, the following vulnerability has been resolved: ceph: lock mutex in ceph_mds_check_access() MDS session OPEN handling replaces mdsc->s_cap_auths under mdsc->mutex, freeing the previous array and its strings. ceph_mds_check_access() traverses this array without holding the mutex. A concurrent session reopen can therefore free the array while it is being inspected, resulting in a use-after-free like this: Unable to handle kernel paging request at virt CVSSv3.1 9.8 (CRITICAL)

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

CVE-2026-89980 — Linux: In the Linux kernel, the following vulnerability has been resolved: ALSA: harmony: initialize locks

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

In the Linux kernel, the following vulnerability has been resolved: ALSA: harmony: initialize locks before requesting IRQ snd_harmony_create() registers the IRQ before initializing h->lock and h->mixer_lock. A pending interrupt can invoke the handler while these locks are uninitialized. Initialize both locks before requesting the IRQ so the handler always sees valid lock state. CVSSv3.1 8.4 (HIGH)

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

CVE-2026-89973 — Linux: No data is copied, so this is not memory corruption.

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

In the Linux kernel, the following vulnerability has been resolved: nvme-tcp: check the data direction of a C2HData PDU nvme_tcp_handle_c2h_data() finds the request by command id and checks that it has a payload, but it does not check that the command asked for data to be read. A controller that answers a write command with C2HData therefore reaches nvme_tcp_recv_data(), where _copy_to_iter() hits WARN_ON_ONCE(i->data_source) and returns 0. The receive path turns that int CVSSv3.1 8.2 (HIGH)

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

CVE-2026-89972 — Linux: In the Linux kernel, the following vulnerability has been resolved: nvme: add missing SRCU

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

In the Linux kernel, the following vulnerability has been resolved: nvme: add missing SRCU grace period in error path nvme_alloc_ns() error path at out_unlink_ns removes ns from the namespace head siblings list with list_del_rcu(&ns->siblings) but does not wait for SRCU readers before freeing the namespace struct. Multipath code iterates the head->list under srcu_read_lock() in nvme_find_path() and nvme_mpath_revalidate_paths(), so a concurrent reader can still hold a refer CVSSv3.1 9.8 (CRITICAL)

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

CVE-2026-89970 — Linux: In the Linux kernel, the following vulnerability has been resolved: nvmet-auth: Synchronize timeout work

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

In the Linux kernel, the following vulnerability has been resolved: nvmet-auth: Synchronize timeout work during SQ teardown nvmet_auth_sq_free() cancels auth_expired_work with cancel_delayed_work(). If the work has already started, cancellation does not wait for the callback. Transport teardown can consequently free or reuse the queue containing struct nvmet_sq while nvmet_auth_expired_work() still accesses that SQ. Add a teardown-specific helper that synchronously drains CVSSv3.1 9.8 (CRITICAL)

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

CVE-2026-89969 — Linux: In the Linux kernel, the following vulnerability has been resolved: nvmet-tcp: fix out-of-bounds write

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

In the Linux kernel, the following vulnerability has been resolved: nvmet-tcp: fix out-of-bounds write when receiving an over-long PDU nvmet_tcp_try_recv_pdu() reads a PDU header into the fixed 128-byte queue->pdu union, then computes the remaining payload length as queue->left = hdr->hlen - queue->offset + hdgst; and reads that many more bytes into &queue->pdu + queue->offset, without ever bounding the result against sizeof(queue->pdu). A struct nvme_tcp_icreq_pdu is i CVSSv3.1 9.8 (CRITICAL)

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

CVE-2026-89960 — Linux: If matrix_mdev is subsequently freed, any PQAP instruction executed by the guest will dereference

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

In the Linux kernel, the following vulnerability has been resolved: s390/vfio-ap: fix stale pqap_hook pointer on error in vfio_ap_mdev_set_kvm() In vfio_ap_mdev_set_kvm(), kvm->arch.crypto.pqap_hook is set to &matrix_mdev->pqap_hook before the update locks are acquired and the mdev list is checked for a conflicting assignment. If another mdev is already attached to the same KVM instance, the function returns -EPERM without restoring the hook pointer, leaving kvm->arch.crypt CVSSv3.1 8.8 (HIGH)

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

CVE-2026-89959 — Linux: In the Linux kernel, the following vulnerability has been resolved: s390/vfio-ap: Fix control domain

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

In the Linux kernel, the following vulnerability has been resolved: s390/vfio-ap: Fix control domain removal in vfio_ap_mdev_cfg_remove The vfio_ap_config_remove function uses the bitmap_andnot function to clear bits from the matrix_mdev->matrix.adm bitmap (specifies the control domains assigned to the mdev). This prevents the explicitly unplugged control domains from being removed the KVM guest. The bitmap_and function is used instead. CVSSv3.1 8.8 (HIGH)

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

CVE-2026-89957 — Linux: In the Linux kernel, the following vulnerability has been resolved: s390/vfio-ap: Fix hot-unplug skipped

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

In the Linux kernel, the following vulnerability has been resolved: s390/vfio-ap: Fix hot-unplug skipped when last AP adapter or domain removed The vfio_ap_mdev_hot_unplug_cfg() function uses the return value of bitmap_andnot() to determine whether the guest APCB needs to be updated. However, bitmap_andnot() returns false when the resulting destination bitmap is empty. This means that if the only adapter, domain or control domain assigned to an mdev is removed from the host CVSSv3.1 8.8 (HIGH)

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

CVE-2026-89954 — Linux: In the Linux kernel, the following vulnerability has been resolved: mtd: afs: validate v2

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

In the Linux kernel, the following vulnerability has been resolved: mtd: afs: validate v2 image info bounds The AFS v2 parser uses footer[8] to locate the image information block inside the current erase block, then uses the image information region_count to walk entries from a fixed local array. The footer offset and region count come from flash contents and are not checked against the erase block or the local image-info array before use. Reject v2 entries whose image inf CVSSv3.1 8.0 (HIGH)

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

CVE-2026-89951 — Linux: In the Linux kernel, the following vulnerability has been resolved: batman-adv: fix stale receive

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

In the Linux kernel, the following vulnerability has been resolved: batman-adv: fix stale receive device on merged fragments Fragment reassembly reuses the skb from the highest-numbered buffered fragment as the merged packet. When that fragment was received on a hard interface which is deleted before the chain completes, the merged skb can re-enter the receive path with a stale skb->dev and skb_iif. batadv_batman_skb_recv() passes such merged packets through the normal rec CVSSv3.1 8.8 (HIGH)

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

CVE-2026-89947 — Linux: In the Linux kernel, the following vulnerability has been resolved: clk: meson: align gxbb_32k_clk_sel

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

In the Linux kernel, the following vulnerability has been resolved: clk: meson: align gxbb_32k_clk_sel number of parents with actual count The following out-of-bounds read has been observed by Christian on a GXBB WeTek Hub: ================================================================== BUG: KASAN: global-out-of-bounds in __clk_register+0x1b70/0x2418 Read of size 8 at addr ffffd66320cf88e0 by task swapper/0/1 CPU: 0 UID: 0 PID: 1 Comm: swapper/0 Not tainted 7.0.0-rc5 #1 CVSSv3.1 8.0 (HIGH)

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

CVE-2026-89943 — Linux: In the Linux kernel, the following vulnerability has been resolved: ASoC: loongson: Fix error

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

In the Linux kernel, the following vulnerability has been resolved: ASoC: loongson: Fix error handling in ACPI property parsing In loongson_card_parse_acpi(), the return value of device_property_read_string() for the `codec-dai-name` property was ignored. If the property is missing or invalid, an uninitialized pointer would be used later, potentially leading to undefined behavior. Fix this by checking the return value and propagating the error appropriately. CVSSv3.1 8.4 (HIGH)

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

CVE-2026-89932 — Linux: nested_vmx_transition_tlb_flush() will always detect a VPID change on first VM-Enter after VMXON, because VPID=0

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

In the Linux kernel, the following vulnerability has been resolved: KVM: nVMX: Always flush vpid02 on first use Make sure vpid02 is always flushed on first use by setting last_vpid=0 when allocating vpid02. nested_vmx_transition_tlb_flush() will always detect a VPID change on first VM-Enter after VMXON, because VPID=0 in vmcs12 is not allowed if L1 enables VPID. This avoids using stale TLB entries from a previous lifetime of the VPID, that might have been associated with CVSSv3.1 8.8 (HIGH)

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

CVE-2026-89930 — Linux: In the Linux kernel, the following vulnerability has been resolved: KVM: nVMX: Service local

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

In the Linux kernel, the following vulnerability has been resolved: KVM: nVMX: Service local TLB flushes on failed nested VM-Enter KVM services local TLB flushes on "full" nested VM-Exits (through __nested_vmx_vmexit()), but not if a nested VM-Enter fails (e.g. due to failed VMCS checks in nested_vmx_enter_non_root_mode()). However, it is possible that KVM had queued TLB flushes that need to be performed, even if the nested VM-Enter was not successful. For example, if VPID 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-89929 — Linux: In the Linux kernel, the following vulnerability has been resolved: KVM: nVM: Ensure INVVPID

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

In the Linux kernel, the following vulnerability has been resolved: KVM: nVM: Ensure INVVPID is emulated on the correct physical CPU When emulating INVVPID, KVM executes INVVPID on the physical CPU using vpid02 (instead of the L1 assigned VPID), after doing some validations on the operands. However, it is possible that the physical CPU KVM executes INVVPID on is different from the CPU L2 is running on. For example, in the following scenario: - L2 runs on CPU #1 and exits t CVSSv3.1 8.8 (HIGH)

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

CVE-2026-89928 — Linux: In that case kvm_rmap_lock_readonly() also re-enables preemption and returns zero, so the caller holds

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

In the Linux kernel, the following vulnerability has been resolved: KVM: x86/mmu: Consume the locked rmap value in the lockless rmap walk __kvm_rmap_lock() deliberately elides the rmap lock when it observes an empty rmap. In that case kvm_rmap_lock_readonly() also re-enables preemption and returns zero, so the caller holds neither the rmap lock nor a preemption reference. The elision documents the invariant it relies on: * Elide the lock if the rmap is empty, as lockle CVSSv3.1 8.8 (HIGH)

TYPVulnerability
8.8
CVSS v3.1
94
Edit Score