{
    "summary": {
        "snap": {
            "added": [],
            "removed": [],
            "diff": []
        },
        "deb": {
            "added": [
                "linux-headers-5.15.0-1113-kvm",
                "linux-image-5.15.0-1113-kvm",
                "linux-kvm-headers-5.15.0-1113",
                "linux-modules-5.15.0-1113-kvm"
            ],
            "removed": [
                "linux-headers-5.15.0-1112-kvm",
                "linux-image-5.15.0-1112-kvm",
                "linux-kvm-headers-5.15.0-1112",
                "linux-modules-5.15.0-1112-kvm"
            ],
            "diff": [
                "linux-headers-kvm",
                "linux-image-kvm",
                "linux-kvm"
            ]
        }
    },
    "diff": {
        "deb": [
            {
                "name": "linux-headers-kvm",
                "from_version": {
                    "source_package_name": "linux-meta-kvm",
                    "source_package_version": "5.15.0.1112.108",
                    "version": "5.15.0.1112.108"
                },
                "to_version": {
                    "source_package_name": "linux-meta-kvm",
                    "source_package_version": "5.15.0.1113.109",
                    "version": "5.15.0.1113.109"
                },
                "cves": [],
                "launchpad_bugs_fixed": [],
                "changes": [
                    {
                        "cves": [],
                        "log": [
                            "",
                            "  * Bump ABI 5.15.0-1113",
                            ""
                        ],
                        "package": "linux-meta-kvm",
                        "version": "5.15.0.1113.109",
                        "urgency": "medium",
                        "distributions": "jammy",
                        "launchpad_bugs_fixed": [],
                        "author": "Ubuntu Kernel Preparation Bot <ubuntu-kernel-bot@canonical.com>",
                        "date": "Mon, 09 Nov 2026 16:21:43 +0000"
                    }
                ],
                "notes": null,
                "is_version_downgrade": false
            },
            {
                "name": "linux-image-kvm",
                "from_version": {
                    "source_package_name": "linux-meta-kvm",
                    "source_package_version": "5.15.0.1112.108",
                    "version": "5.15.0.1112.108"
                },
                "to_version": {
                    "source_package_name": "linux-meta-kvm",
                    "source_package_version": "5.15.0.1113.109",
                    "version": "5.15.0.1113.109"
                },
                "cves": [],
                "launchpad_bugs_fixed": [],
                "changes": [
                    {
                        "cves": [],
                        "log": [
                            "",
                            "  * Bump ABI 5.15.0-1113",
                            ""
                        ],
                        "package": "linux-meta-kvm",
                        "version": "5.15.0.1113.109",
                        "urgency": "medium",
                        "distributions": "jammy",
                        "launchpad_bugs_fixed": [],
                        "author": "Ubuntu Kernel Preparation Bot <ubuntu-kernel-bot@canonical.com>",
                        "date": "Mon, 09 Nov 2026 16:21:43 +0000"
                    }
                ],
                "notes": null,
                "is_version_downgrade": false
            },
            {
                "name": "linux-kvm",
                "from_version": {
                    "source_package_name": "linux-meta-kvm",
                    "source_package_version": "5.15.0.1112.108",
                    "version": "5.15.0.1112.108"
                },
                "to_version": {
                    "source_package_name": "linux-meta-kvm",
                    "source_package_version": "5.15.0.1113.109",
                    "version": "5.15.0.1113.109"
                },
                "cves": [],
                "launchpad_bugs_fixed": [],
                "changes": [
                    {
                        "cves": [],
                        "log": [
                            "",
                            "  * Bump ABI 5.15.0-1113",
                            ""
                        ],
                        "package": "linux-meta-kvm",
                        "version": "5.15.0.1113.109",
                        "urgency": "medium",
                        "distributions": "jammy",
                        "launchpad_bugs_fixed": [],
                        "author": "Ubuntu Kernel Preparation Bot <ubuntu-kernel-bot@canonical.com>",
                        "date": "Mon, 09 Nov 2026 16:21:43 +0000"
                    }
                ],
                "notes": null,
                "is_version_downgrade": false
            }
        ],
        "snap": []
    },
    "added": {
        "deb": [
            {
                "name": "linux-headers-5.15.0-1113-kvm",
                "from_version": {
                    "source_package_name": "linux-kvm",
                    "source_package_version": "5.15.0-1112.117",
                    "version": null
                },
                "to_version": {
                    "source_package_name": "linux-kvm",
                    "source_package_version": "5.15.0-1113.118",
                    "version": "5.15.0-1113.118"
                },
                "cves": [
                    {
                        "cve": "CVE-2026-99115",
                        "url": "https://ubuntu.com/security/CVE-2026-99115",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ksmbd: fill in FileSysIdentifier in FS_POSIX_INFORMATION  smb2_get_info_filesystem() reports 56 bytes for FS_POSIX_INFORMATION, that is the whole of FILE_SYSTEM_POSIX_INFO, but never assigns FileSysIdentifier.  Those eight bytes go to the client as they are found in the response buffer.  The buffer is zeroed on allocation, so a standalone request leaks nothing.  A compound request can leak: the offset of the next response is advanced by the length pinned for the previous one, so a reply that was written into the buffer and then dropped in favour of the short error response of smb2_set_err_rsp() stays there, and the next reply is laid over it with only the header cleared.  Report the file system id statfs() returned, which is what the field is for.  FileSysIdentifier is __le64 and f_fsid is a pair of ints, so assemble the value first, val[0] as the low half, and convert it on the way out.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99113",
                        "url": "https://ubuntu.com/security/CVE-2026-99113",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ksmbd: zero the FS_OBJECT_ID_INFORMATION buffer before filling it in  smb2_get_info_filesystem() reports 64 bytes for FS_OBJECT_ID_INFORMATION, that is the whole of struct object_id_info, but writes only 46 of them:   - objid[] is 16 bytes, and when the volume UUID is not available only    sizeof(stfs.f_fsid) (8) bytes are copied into it;  - extended_info.version_string[] is STRING_LENGTH (28) bytes, and only    strlen(\"1.1.0\") (5) bytes are copied into it.  The response buffer is zeroed on allocation (kvzalloc() in smb2_allocate_rsp_buf()), so for a standalone request the remaining 31 bytes are zero.  In a compound request they need not be.  The offset of the next response is advanced by the length pinned for the previous one, so if a preceding command wrote its reply into the buffer and then failed, smb2_set_err_rsp() pins only the short error response and the next reply lands inside the area that has already been written.  Only the header is cleared there:  \tmemset((char *)rsp_hdr, 0, sizeof(struct smb2_hdr) + 2);  The client then receives up to 31 bytes of a response it was not meant to see, including one that failed with an access denied error.  Clear the structure before filling it in.  As a side effect version_string is now NUL terminated.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99114",
                        "url": "https://ubuntu.com/security/CVE-2026-99114",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ksmbd: initialize FileSystemControlFlags in FS_CONTROL_INFORMATION  smb2_get_info_filesystem() reports 48 bytes for FS_CONTROL_INFORMATION, that is the whole of struct smb2_fs_control_info, but never assigns FileSystemControlFlags.  Those four bytes go to the client as they are found in the response buffer.  The buffer is zeroed on allocation, so a standalone request leaks nothing.  A compound request can leak: the offset of the next response is advanced by the length pinned for the previous one, so a reply that was written into the buffer and then dropped in favour of the short error response of smb2_set_err_rsp() stays there, and the next reply is laid over it with only the header cleared.  ksmbd does not implement quota tracking, so report no control flags.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99132",
                        "url": "https://ubuntu.com/security/CVE-2026-99132",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  xfs: don't hold buffer locks across sync transaction commit in xfs_sync_sb_buf  xfs_sync_sb_buf() holds sb/rtsb buffer locks across a synchronous xfs_trans_commit(), which flushes the CIL push workqueue internally. If shutdown occurs during the CIL push, xfs_buf_item_unpin() needs to lock these buffers to fail them, causing a deadlock:    setlabel:          holds buf lock -> flush_workqueue(xfs-cil)   CIL push worker:   xfs_buf_item_unpin -> xfs_buf_lock(same buf)  Remove the xfs_trans_bhold() calls so that commit releases the buffer locks normally.  After the sync commit, re-acquire the buffers via mp->m_sb_bp / mp->m_rtsb_bp for the on-disk writeback.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99135",
                        "url": "https://ubuntu.com/security/CVE-2026-99135",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  dm-integrity: fix infinite loop on discard with large tag size  When integrity_metadata handles a discard, it fills a buffer with DISCARD_FILLER and writes it over the tags, max_blocks blocks at a time. If the kmalloc fails, the buffer is the on-stack array checksums_onstack and max_size is set to HASH_MAX_DIGESTSIZE. So if the tag size is larger than HASH_MAX_DIGESTSIZE, max_blocks is zero, bi_size is never decremented and the loop never terminates.  Fix this by using sizeof(checksums_onstack) as max_size. The array has MAX_TAG_SIZE bytes since commit b93b6643e9b5 (\"dm integrity: fix a crash with unusually large tag size\"), so max_blocks is at least 1.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99118",
                        "url": "https://ubuntu.com/security/CVE-2026-99118",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  drm/i915/dmc: Harden DMC firmware payload parsing  Validate the conversion of the DMC firmware size from dwords to bytes using check_mul_overflow() before calculating the firmware payload size.  Reject zero-length payloads and zero MMIO counts in the DMC firmware header so malformed firmware is caught early. Also set dmc_fw_size only after the payload allocation succeeds.  (cherry picked from commit efde6601a1f1daedfe3dcc2816c934ddb44e3eef)",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99169",
                        "url": "https://ubuntu.com/security/CVE-2026-99169",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  futex: Fix mm reuse handling for FUT_OFF_MMSHARED  A FUT_OFF_MMSHARED futex is a shared futex that refers to an MM. It is possible for a process to wait on a shared futex with a different MM because a FUT_OFF_INODE waiter can be requeued onto a FUT_OFF_MMSHARED futex by another process. This can cause FUT_OFF_MMSHARED waiters on a freed MM to consume wakeups intended for a newly allocated MM at the same address.  Fix it by keying FUT_OFF_MMSHARED using a unique 64-bit per-MM ID. Leave private futexes as before to avoid influencing the performance of the hotpath.  (Multi-threaded processes typically implicitly use FUT_OFF_MMSHARED by setting clear_child_tid such that it points into anonymous memory, which causes mm_release() in a multi-threaded mm to perform FUTEX_WAKE.)",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99161",
                        "url": "https://ubuntu.com/security/CVE-2026-99161",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  i2c: viai2c-wmt: Fix clock leak in wmt_i2c_probe()  In wmt_i2c_probe(), i2c->clk is acquired using of_clk_get(). If any subsequent operation fails or when the module is unloaded, the clock reference count is never decremented via clk_put(), leading to a resource leak.  Switch to devm_clk_get() so that the clock is automatically managed and released.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99077",
                        "url": "https://ubuntu.com/security/CVE-2026-99077",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ipv4: udp: Create exceptions before socket matching  Currently, when ICMP Fragmentation Needed and Redirect Message packets are locally delivered and quote a UDP packet, a FIB nexthop exception (FNHE) is only created if the kernel can match the UDP packet to an existing socket.  This behavior allows off-path attackers to conduct a side-channel attack on the FNHE cache in order to discover the ephemeral port used by a connected UDP socket.  Commit 6457378fe796 (\"ipv4: use siphash instead of Jenkins in fnhe_hashfun()\") and commit 67d6d681e15b (\"ipv4: make exception cache less predictible\") tried to mitigate such attacks by making it harder for attackers to discover hash collisions in the FNHE cache and by randomizing the number of exceptions a hash bucket can hold, respectively. Unfortunately, both of the mitigations can be bypassed.  Instead, mitigate such attacks by always creating a FNHE, even before trying to find a matching socket. Do that by calling ipv4_update_pmtu() and ipv4_redirect(), the helpers used when the quoted packet did not originate from a socket.  This means that guesses (right or wrong) from an off-path attacker will always result in a FNHE being created or updated in the cache that the attacker can observe.  Pass an oif of 0, in a similar fashion to icmp_err(). This is also the oif used by the socket path for sockets that are not bound to a device.  Note that this does not allow attackers to create FNHEs that they could not create before, as both helpers can already be reached with little to no validation. For example, by sending an ICMP error that quotes an ICMP Echo Reply or one that quotes a UDP source port that matches a wildcard socket.  Also note that in the good case (matched socket) the above scheme comes at the cost of an extra route lookup, as the no socket helpers perform their own lookup before the one performed by ipv4_sk_update_pmtu() / ipv4_sk_redirect(). When the two resolve to different nexthops, it also results in two exceptions being created for the same destination IP. One in the FNHE cache of the nexthop resolved by the no socket helpers and another in the FNHE cache of the nexthop used by the socket.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99123",
                        "url": "https://ubuntu.com/security/CVE-2026-99123",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  vsock/virtio: validate packet source for connected sockets  virtio_transport_recv_pkt() looks up sockets first by the full source and destination tuple, then by destination only in the bound table. The fallback is needed for listening and connecting sockets, but sockets remain in the bound table after connect(), so it can also return a non-listening socket.  The fallback does not validate the source address. In TCP_SYN_SENT, a RESPONSE from an unrelated source can transition the victim socket to TCP_ESTABLISHED while its stored remote address remains unchanged. Subsequent RW packets from that source are delivered through the same destination-only fallback.  This was reproduced with capability-empty processes under different UIDs. The attacker discovered the target tuple through unprivileged AF_VSOCK sock_diag and caused the victim socket to read 16 attacker-chosen bytes; the intended peer-side socket read 0 of those 16 bytes.  Add vsock_check_source() to validate the transport, source port and source CID against the peer stored in a non-listening socket. The local transport is the CID exception because its packets are generated internally with VMADDR_CID_LOCAL as their source, including connections using CID aliases.  Use the helper after lock_sock() in the virtio receive path.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-89987",
                        "url": "https://ubuntu.com/security/CVE-2026-89987",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  mm/huge_memory: transfer the pmd dirty bit to the folio on zap  zap_huge_pmd_folio() propagates the pmd young bit to the folio for the file case, but not the dirty bit.  The pte path does propagate it, in zap_present_folio_ptes() and so does the pmd split path, in __split_huge_pmd_locked().  For most file mappings the omission is harmless, because writing to a shared file mapping goes through page_mkwrite(), which dirties the folio. tmpfs is different: it has no page_mkwrite(), and vma_wants_writenotify() is false for it, so a *read* fault on a MAP_SHARED tmpfs mapping installs a writable pmd via do_read_fault().  do_read_fault() does not call fault_dirty_shared_page(), so subsequent stores through that mapping set only the hardware dirty bit in the pmd and never call folio_mark_dirty(). A shmem folio allocated by a fault is marked uptodate but not dirty (see the clear: block in shmem_get_folio_gfp()), so PG_dirty is never set at all.  Unmapping such a folio - munmap(), or exit_mmap() when the process dies - then loses the only record that it was written, because zap_huge_pmd() drops the pmd without transferring the dirty bit.  Reclaim afterwards sees a clean shmem folio: the whole swap-out block in shrink_folio_list() is inside \"if (folio_test_dirty(folio))\", so pageout() is skipped and the folio falls into __remove_mapping().  There, folio_is_file_lru() is false for a swapbacked folio, so no shadow entry is created and __filemap_remove_folio(folio, NULL) simply empties the i_pages slot.  The data is freed without ever being written to swap, and the next fault on that index returns a freshly zeroed folio.  This is silent data loss for any process that keeps state in a MAP_SHARED tmpfs segment across an unmap - for example a cache handed from one process generation to the next through /dev/shm.  It requires the folio to be PMD-mapped, so it only shows up once shmem THP is enabled (which is what we did in Meta fleet and started noticing crashes); with THP off the pte path transfers the dirty bit correctly.  It also only becomes visible when swap is enabled, because with no swap device shmem folios (which are on the anon LRU) are not scanned by reclaim at all, so the clean folio is never dropped.  Reproduced on x86_64 with a tmpfs mounted huge=within_size: read-fault a 2MB-backed region, write a known pattern through the resulting mapping, munmap, force reclaim of the cgroup, then re-map and read back.  Without this patch the region reads back as zeros and vmstat shows zswpout 0 - the data was discarded rather than swapped.  With this patch the region reads back correctly and the pages are swapped out as expected.  With huge=never, or when the first touch is a write, the test passes either way.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-09-16 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-80572",
                        "url": "https://ubuntu.com/security/CVE-2026-80572",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  Input: byd - synchronize timer deletion before freeing private data  byd_disconnect() uses timer_delete() before freeing the driver's private data.  This does not wait for a running byd_clear_touch() callback, which dereferences the private data and its psmouse pointer.  A callback racing with disconnect can therefore access the private data after it has been freed.  The timer can also still be re-armed by byd_process_byte() while the disconnect is in progress.  Use timer_shutdown_sync() before freeing the private data: it waits for a running callback and turns any later re-arm attempt into a no-op.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-08-26 15:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99180",
                        "url": "https://ubuntu.com/security/CVE-2026-99180",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  unicode: free the map after a grace period  generic_ci_d_hash() and generic_ci_d_compare() read sb->s_encoding and dereference the unicode map while a pathwalk in rcu mode holds nothing but rcu_read_lock(). The filesystems that use them, ext4, f2fs and tmpfs, drop the map with utf8_unload() from ->put_super(), which runs when the last reference to the mount goes away. A lookup that is still inside such a filesystem at that point reads a freed map.  With a pathwalk held up in utf8_casefold_hash() while the last reference to a casefolded tmpfs goes away:    BUG: KASAN: slab-use-after-free in utf8nlookup+0x74c/0x950   Read of size 8 at addr ff110001030fe658 by task walker/98   Call Trace:    <TASK>    utf8nlookup+0x74c/0x950    utf8byte+0x160/0x1560    utf8_casefold_hash+0x167/0x230    generic_ci_d_hash+0xdd/0x1c0    link_path_walk+0x11ad/0x1d30    path_lookupat+0x63/0xb00    filename_lookup+0x1f1/0x5b0    vfs_statx+0xd7/0x3b0   [...]   Allocated by task 94:    __kmalloc_cache_noprof+0x249/0x560    utf8_load+0x4e/0x570    shmem_parse_opt_casefold.isra.0+0x92/0x270   [...]   Freed by task 97:    kfree+0x1db/0x5b0    shmem_put_super+0x72/0x170    generic_shutdown_super+0x14c/0x530    kill_anon_super+0x3a/0x60    deactivate_locked_super+0x9c/0xf0    cleanup_mnt+0x9f/0x130  So far that has been hard to hit. umount(2) waits for a grace period in namespace_unlock() before it drops the mount, so only a mount whose last reference goes away elsewhere, like the close of a file or a chdir out of a lazily unmounted directory, can race a walker. So it is reachable.  Delay the free until a grace period has passed. The map and the data table it holds a reference to then outlive any pathwalk that found the superblock before the mount went away. The reference on the data table module is dropped from the rcu callback as well. utf8-core is built in whenever CONFIG_UNICODE is set, so there is no module exit that would have to wait for the callbacks.  Overlayfs points the s_encoding of an overlay at the map of its first layer without taking a reference of its own. That stays correct. The layer is held by the overlay, so its map is dropped only after the overlay is gone.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99179",
                        "url": "https://ubuntu.com/security/CVE-2026-99179",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  watch_queue: Fix note pool publication race in watch_queue_set_size()  There is a race between watch_queue_set_size() and post_one_notification(). watch_queue_set_size() publishes wqueue->notes, notes_bitmap, nr_pages and nr_notes with plain stores, and post_one_notification() reads them with plain loads under a different lock, so nothing orders the four stores against the poster's loads: depending on the build, notes can be stored last (gcc 14 on x86-64 does this).  Since keyctl_watch_key() lets a watch attach to a queue before it is sized, post_one_notification() can already be running on another CPU at that moment: it reads nr_notes > 0, passes its bounds check, and then reads notes while it is still NULL, dereferencing notes[0].  An unprivileged user triggers this reliably by watching one of its own keys through a notification pipe and racing ioctl(IOC_WATCH_QUEUE_SET_SIZE) on that pipe against keyctl(KEYCTL_SETPERM) on the key from another CPU, triggering:    BUG: kernel NULL pointer dereference, address: 0000000000000000   RIP: 0010:post_one_notification.isra.0+0xa2/0x1e0   Call Trace:    __post_watch_notification+0x148/0x180    keyctl_setperm_key+0x119/0x130    do_syscall_64+0x108/0x4c0    entry_SYSCALL_64_after_hwframe+0x77/0x7f   Kernel panic - not syncing: Fatal exception in interrupt  Fix this by publishing nr_notes last with smp_store_release(), and by reading it once with smp_load_acquire() in post_one_notification() before the bitmap and the page array are touched.  A poster that observes a non-zero nr_notes then also observes the pool behind it; one that observes zero drops the notification as before.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-89912",
                        "url": "https://ubuntu.com/security/CVE-2026-89912",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  KVM: arm64: vgic-its: Don't dereference a NULL collection on ITT save  MAPC with V=0 drops ite->collection but leaves the ITE on the device's ITT list, and vgic_its_save_ite() dereferences it unconditionally. A guest that issues MAPD, MAPTI and then MAPC(V=0) therefore oopses the host when the VMM issues KVM_DEV_ARM_ITS_SAVE_TABLES to migrate it. That sequence is UNPREDICTABLE per the architecture, but KVM already handles the resulting state in the translate, MOVI and DISCARD paths.  Save a zeroed entry, which vgic_its_restore_ite() reads back as invalid. Skipping the ITE instead would leave the ITT slot holding whatever is in guest memory, and restore rejects an entry naming a collection the restored collection table does not have.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-09-16 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99156",
                        "url": "https://ubuntu.com/security/CVE-2026-99156",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  scsi: st: Fix use-after-free race between st_remove() and st_open()  st_remove() drops the probe reference on the scsi_tape with kref_put() and only afterwards removes its index from st_index_idr. If that was the last reference, scsi_tape_release() frees the structure while it is still published in the idr.  scsi_tape_get(), called from st_open(), looks up the tape in st_index_idr and takes a reference under st_ref_mutex and st_index_lock. remove_cdevs() does not wait for opens that are already past chrdev_open(), so an open that is blocked on st_ref_mutex while st_remove() holds it can take the mutex as soon as st_remove() drops it, find the freed tpnt in the idr and call kref_get() on it:    BUG: KASAN: slab-use-after-free in st_open   Write of size 4 ...    st_open (drivers/scsi/st.c:254 drivers/scsi/st.c:1291)    chrdev_open   ...   Freed by task ...:    kfree    st_remove (drivers/scsi/st.c:4512)  Remove the index from the idr before dropping the reference, all under st_ref_mutex. A concurrent scsi_tape_get() now either runs first and holds a valid reference that keeps the tape alive, or runs afterwards and finds nothing, so st_open() fails with -ENXIO.  This restores the ordering st_remove() had before the conversion to st_index_idr, where the tape was unpublished from scsi_tapes[] before the final kref_put().",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99112",
                        "url": "https://ubuntu.com/security/CVE-2026-99112",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net/sched: cls_flower: validate mask pointer after nla_next()  fl_set_enc_opt() iterates the key's nested tunnel-option attributes with nla_for_each_attr() while advancing a single mask pointer via nla_next() at the bottom of each loop, so the mask cursor is driven by the number of key attributes rather than by the mask's own attributes.  The nla_ok() added by commit c96adff956191 (\"cls_flower: call nla_ok() before nla_next()\") only validates the mask pointer that was just consumed; the pointer produced by nla_next() is used by the next iteration (fl_set_geneve_opt() and siblings) without any validation.  The mask's nested attributes are validated with NL_VALIDATE_LIBERAL, which merely warns on trailing bytes that do not form a complete attribute.  A mask carrying one valid attribute plus 1-3 residue bytes (or a non-aligned attribute length making msk_depth negative) therefore reaches the next iteration with msk_depth != 0, so neither the !msk_depth check in fl_set_enc_opt() nor the !depth check in the per-type helpers fires.  nla_type() then reads past the mask payload and nla_parse_nested_deprecated() iterates with an nla_len taken from those bytes, reading well beyond the mask attribute (KASAN: slab-out-of-bounds read in __nla_validate_parse from fl_change()).  Validate the advanced mask pointer as well: when the mask is not legitimately exhausted (msk_depth != 0) and the new pointer fails nla_ok(), reject the filter with -EINVAL.  An exactly exhausted mask still skips the check, preserving exact-match behaviour for the remaining key attributes.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99117",
                        "url": "https://ubuntu.com/security/CVE-2026-99117",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net: bridge: mcast: don't truncate the port group walk on teardown  __br_multicast_disable_port_ctx() and br_multicast_del_port() walk port->mglist with hlist_for_each_entry_safe(). However, br_multicast_find_del_pg() can also delete other entries from the same list through br_multicast_fwd_src_remove() or __fwd_del_star_excl().  If such an entry is the iterator's saved next node, hlist_del_init() clears its ->next and terminates the walk early. The reproducer triggers this in both teardown walks, leaving port groups in the bridge mdb with a dangling ->key.port after del_nbp() frees the port:    BUG: KASAN: slab-use-after-free in __mdb_fill_info+0x1191/0x1320    __mdb_fill_info+0x1191/0x1320    br_mdb_dump+0x594/0xe40    rtnl_mdb_dump+0x1cf/0x5d0  Use hlist_del_init_rcu() to unlink the group while preserving ->next. br_multicast_del_pg() and the teardown walks run under br->multicast_lock. The GC worker must acquire the same lock before detaching the group for destruction, so the node remains alive while the walk uses the preserved pointer.  Preserving ->next means a walk can now reach a group that an earlier iteration already deleted as a side effect. That group is off mp->ports, so br_multicast_find_del_pg() would fall through its port scan and hit the trailing WARN_ON(1). Skip such groups at the top of that helper: a port group is put on port->mglist when it is created and only unlinked when it is deleted, so hlist_unhashed() identifies exactly this case.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-74405",
                        "url": "https://ubuntu.com/security/CVE-2026-74405",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  OPP: Fix race between OPP addition and lookup  A race exists between dev_pm_opp_add_dynamic() and dev_pm_opp_find_freq_exact():    CPU0 (add)                          CPU1 (lookup)   -------------------------------     ------------------------------   _opp_add()     mutex_lock()     list_add(&new_opp->node, head)     mutex_unlock()                    _opp_table_find_key()                                         mutex_lock()                                         dev_pm_opp_get(opp)                                           kref_get()                                         mutex_unlock()     kref_init(&new_opp->kref)                                       dev_pm_opp_put()                                         kref_put_mutex()  The newly added OPP is inserted into the list before its kref is initialized. A concurrent lookup can find this OPP and increment its reference count while it is still uninitialized, leading to refcount corruption and a potential premature free.  Fix this by initializing ->kref and ->opp_table before making the OPP visible via list_add(). This ensures any concurrent lookup observes a fully initialized object.  [ Viresh: Updated commit log ]",
                        "cve_priority": "low",
                        "cve_public_date": "2026-08-15 06:22:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-74739",
                        "url": "https://ubuntu.com/security/CVE-2026-74739",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net/sched: cls_u32: skip hash tables in u32_bind_class()  u32_walk() enumerates both struct tc_u_hnode and struct tc_u_knode through the walker callback. u32_bind_class() unconditionally casts the passed fh to tc_u_knode and accesses &n->res, so when fh is actually a tc_u_hnode, which has no tcf_result member, this results in a slab-out-of-bounds read of res->classid in tc_cls_bind_class().  The issue can be reproduced with the following commands:      tc qdisc add dev lo root handle 1: hfsc     tc class add dev lo parent 1: classid 1:1 hfsc sc rate 1000kbit     tc filter add dev lo parent 1:1 protocol ip prio 1 u32 match u32 0 0 flowid 1:1     tc class add dev lo parent 1: classid 1:2 hfsc sc rate 2000kbit  Fix this by skipping hash tables via the TC_U32_KEY(handle) check.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-08-26 15:16:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-64015",
                        "url": "https://ubuntu.com/security/CVE-2026-64015",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  security/keys: fix missed RCU read section on lookup  Nicholas Carlini reports that the keyring code calls assoc_array_find() in find_key_to_update() without holding the RCU read lock, while the assoc_array_gc() code really is designed around removing the node from the tree and then freeing it after an RCU grace-period.  The regular key handling doesn't see this because holding the keyring semaphore hides any lifetime issues, but the persistent key handling uses a different model.  Instead of extending the keyring locking, just do the simple RCU locking that the assoc_array was designed for.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-07-19 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-74672",
                        "url": "https://ubuntu.com/security/CVE-2026-74672",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  mm/vmalloc: acquire init_mm lock on huge vmap to avoid ptdump UAF  Patch series \"mm: fix UAF caused by race between ptdump and vmap pgtable freeing\", v6.  Kernel page table walkers fall into two broad categories - those ranges where no exclusion is required via walk_kernel_page_table_range_lockless() and those where exclusion is required via walk_kernel_page_table_range() or walk_page_range_debug().  The former category is used only by arm64 arch code operating on ranges it both wholly owns and does not concurrently write.  The latter category consists of kernel page table walkers operating on ranges that are wholly owned (but which need exclusion against concurrent writers).  The lock used for exclusion is the mmap lock, and for kernel ranges this is the mmap lock on init_mm.  ptdump is a special case being both the only user of walk_page_range_debug(), and the only case in which it walks ranges it does not own.  This presents a problem, as page tables may be freed under ptdump.  And indeed there is a use-after-free bug in the kernel as a result, which this series addresses.  vmap promotes page tables to huge leaf entries where possible, freeing the lower page table when it does.  It does this with no meaningful locks held against concurrent ptdump walks.  As a result, use-after-free can currently occur.  This series addresses the issue by having the vmap huge promotion logic acquire the mmap read lock while both setting the huge page table entry and freeing the prior leaf page table.  The ptdump code already acquires the mmap write lock, so by doing so we ensure that the ptdump walker only ever observes either the huge page table entry or the existing page table entry, and nothing is freed underneath it.  A mitigation for this issue was already applied for arm64 in commit fa93b45fd397 (\"arm64: Enable vmalloc-huge with ptdump\"), which this series has to deal with carefully.  This mitigation resolves the issue by acquiring the mmap read lock on init_mm on vmap page table free if a ptdump is in progress.  However the fix in this series would cause a deadlock if we were to simply apply it for arm64 without also reverting the change.  This is because vmap may acquire the read lock before ptdump attempts to acquire the write lock, which then gets queued, and rwsem starvation rules mean that the (unacknowledged) nested mmap read lock in the arm64 code would also block, meaning the original read lock is never released and thus deadlock.  This series works around this by #ifndef CONFIG_ARM64'ing the mmap read lock in vmap logic, then partially reverting commit fa93b45fd397 (\"arm64: Enable vmalloc-huge with ptdump\"), keeping the enablement of huge vmap support, and removing the ifdeffery with the partial revert patch.  There are related issues that are also addressed in this series:  * x86 page attribute logic, specifically Change Page Attributes (CPA),   implements a feature whereby huge ranges can be collapsed into huge leaf   entries. This can similarly cause a UAF when done in parallel with a   ptdump walk, so similarly acquire the init_mm mmap lock to avoid this.  * The CPA logic allows concurrent page table manipulation and CPA   collapse, meaning the former risks accessing a page table the latter   frees. Fix this by acquiring mmap write lock on init_mm across the   whole CPA collapse operation and read lock on the page table   manipulation.  * x86 and arm64 permit walks of non-kernel mm's (both allowing efi mm   walks, and in x86's case arbitrary mm's), so we ensure kernel mappings   remain stable by locking the init_mm as well as the mm being walked.  The ordering of patches is established for both strict dependencies (the arm64 partial revert in particular has to be done after the vmap changes) and logical ones (the non-kernel mm fix only makes sense once the vmap/CPA fixes are in place).   This patch (of 3):  Currently there is a nasty ra ---truncated---",
                        "cve_priority": "low",
                        "cve_public_date": "2026-08-22 16:16:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99121",
                        "url": "https://ubuntu.com/security/CVE-2026-99121",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ipv4: avoid divide by zero in fib_rebalance  fib_rebalance() computes the total eligible nexthop weight in one pass and programs upper bounds in a second pass. A concurrent change to ignore_routes_with_linkdown can make the first pass return zero while the second pass sees an eligible nexthop, resulting in division by zero.  If the first pass reports a zero total, set each nexthop upper bound to -1 and skip the division. This matches the IPv6 fix in commit d2c26c2911dd (\"ipv6: avoid divide by zero in rt6_multipath_rebalance\") and preserves the lock-free rebalance path.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99124",
                        "url": "https://ubuntu.com/security/CVE-2026-99124",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  s390/pci: Fix leak of uninitialized kernel data in SCLP report  While report_error_write() checks that the provided buffer is at least as large as the header struct, but not that it is large enough to contain the report with the length claimed by report->length. If user-space provides a short buffer, meaning a larger report->length than the actually written payload, up to around 4K of kernel data from past the kmalloc(len + 1) sized buffer allocated in kernfs_fop_write_iter() will leak into the SCLP report.  However, as the entity processing the SCLP is privileged and able to access at least the page including the report, this does not leak data that entity could not access but it is still an out of bounds read and a malformed error report that should be rejected.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99126",
                        "url": "https://ubuntu.com/security/CVE-2026-99126",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  s390/ctcm: Prevent XID null dereference  The mpc_validate_xid() function sets grp->saved_xid2->xid2_flag2 to 0x40 to signal XID validation error. If peer XID is NULL or r/w channel pairing mismatch happens, grp->saved_xid2 is never initialized. An attempt to set the flag in such case leads to NULL dereference.  Fix this by using the always available priv->xid->xid2_flag2 instead of grp->saved_xid2->xid2_flag2 for validation errors.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99127",
                        "url": "https://ubuntu.com/security/CVE-2026-99127",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  page_pool: keep frag_offset aligned for odd-sized requests  page_pool_alloc_frag_netmem() rounds the requested fragment size with  \tsize = ALIGN(size, dma_get_cache_alignment());  dma_get_cache_alignment() returns 1 unless the architecture defines ARCH_DMA_MINALIGN, which DMA-coherent architectures such as x86 do not. There the ALIGN() is a no-op and pool->frag_offset advances by the raw, unrounded size.  A single caller asking for an odd size then leaves frag_offset misaligned for every fragment carved out of that page afterwards.  The pool is shared, so the damage is not confined to the caller that caused it.  The per-cpu system_page_pool used by generic XDP hits this. skb_pp_cow_data() allocates its fragments with the raw packet length:  \tsize = min_t(u32, len, PAGE_SIZE); \ttruesize = size; \tpage = page_pool_dev_alloc(pool, &page_off, &truesize);  leaving frag_offset odd for whatever is carved out of that page next.  Its own head allocation is already aligned -- SKB_HEAD_ALIGN(size) plus the XDP_PACKET_HEADROOM its callers pass -- so it is a later user of the shared pool that pays: page_pool_dev_alloc_va() returns a misaligned buffer, napi_build_skb() installs it as skb->head, and skb_shinfo(skb) == skb->head + skb->end is misaligned with it.  skb_shinfo()->dataref is a 4-byte atomic_t at offset 0x20, so the atomic_inc() in __skb_clone() straddles a cache line.  On x86 with split lock detection -- fatal for kernel split locks by default -- this panics the machine:    Oops: Split lock detected   RIP: 0010:skb_clone+0x154/0x1e0   Call Trace:    <IRQ>    raw_local_deliver+0x1ed/0x2c0    ip_protocol_deliver_rcu+0x54/0x1c0    ip_local_deliver_finish+0x85/0x100    ip_local_deliver+0x67/0x100    __netif_receive_skb_one_core+0x85/0xa0    process_backlog+0x87/0x130  Reproduced by attaching any generic-mode XDP program to loopback and opening a RAW IPPROTO_UDP socket, which makes raw_local_deliver() clone every locally delivered UDP packet; ordinary DNS traffic then triggers it, roughly once per 2500 clones.  Observed on 6.12.101 and 7.1.8.  Tracing page_pool_alloc_frag_netmem() over one such run shows the amplification -- two odd-sized requests, nine misaligned offsets:    requested size & 7:   0: 17035    5: 1    7: 1   frag_offset & 7:      0: 17028    3: 1    4: 1    5: 1    6: 1    7: 5  and skb_pp_cow_data() returning heads that were aligned on entry:    head 0xffff8f4c86aeac00 -> 0xffff8f4c53a9a9c4 (&7=4)   head 0xffff8f4d6a8a42c0 -> 0xffff8f4c4f7b7a45 (&7=5)  Round the fragment size up to at least the alignment struct skb_shared_info requires, so fragments are always suitably aligned for the objects callers build on them.  Architectures needing a larger DMA alignment keep it.  This also makes the remainder computed in page_pool_alloc_netmem(),  \t*size = max_size - *offset;  aligned, since max_size is a power of two -- which fixes the matching misalignment of skb->end.  Verified with a controlled A/B under QEMU/KVM: same tree, same config, same compiler, same rootfs and identical traffic, differing only by this patch.  A SEC(\"xdp.frags\") XDP_PASS program on lo plus UDP datagrams larger than max_head_size drives skb_pp_cow_data()'s fragment loop, which passes raw packet lengths to the pool.  Measured at the return of skb_pp_cow_data():                            unpatched   patched   skb_pp_cow_data calls       40800     40800   misaligned skb->head         1120         0   dataref at line offset >60     80         0  The last row counts the accesses that actually fault: skb_shinfo()->dataref sits at head+end+0x20 and is a 4-byte atomic, so `lock incl` splits a 64-byte cache line only when that address lands at offset 61..63.  All 80 occurrences were at offset 61; the panic reported above was at offset 62.  Eliminating the misalignment removes every one of them.  Same class of bug as commit 3bed3cc4156e (\"net: Do not allocate page fragments t ---truncated---",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99128",
                        "url": "https://ubuntu.com/security/CVE-2026-99128",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  sctp: validate chunk length in the inqueue parser  SCTP chunks always include a four-byte generic header, but sctp_inq_pop() currently accepts shorter declared lengths. A zero-length chunk leaves chunk_end at the current header.  When ASCONF is covered by the association's SCTP-AUTH policy, sctp_assoc_bh_rcv() can continue before the state machine performs its normal chunk-length check. sctp_inq_pop() then returns the same malformed chunk repeatedly and the receive softirq can lock up.  A remote SCTP peer can trigger this after establishing an association on a kernel built with CONFIG_IP_SCTP and configured with net.sctp.addip_enable=1 and net.sctp.auth_enable=1. The reproducer did not require application credentials, a shared SCTP AUTH key, or net.sctp.addip_noauth_enable=1.  On commit f967455fb2a5 (\"seg6: reset IP6CB after IPv6 decapsulation\"), one zero-length ASCONF caused repeated watchdog soft-lockup reports in a two-vCPU KVM guest. All 3 pre-trigger health probes succeeded, while 36 of 37 post-trigger probes failed. With this change, all 37 post-trigger probes succeeded and no equivalent soft-lockup signature appeared.  Reject chunks shorter than the generic SCTP header at the shared inqueue parser boundary. Mark the packet for discard before either caller can continue processing it, while preserving the four-byte generic minimum. Declared-length 1 through 4 controls and kernel-generated ASCONF traffic remained healthy. The patched sctp_hello selftest passed for IPv4 and IPv6.  The complete private reproducer and validation evidence are available directly to maintainers on request.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99133",
                        "url": "https://ubuntu.com/security/CVE-2026-99133",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net/iucv: fix the recvmsg window update  iucv_sock_recvmsg() sends the HiperSockets-only AF_IUCV_FLAG_WIN without testing the transport, so on a classic z/VM socket iucv_send_ctrl() sizes the skb through a NULL iucv->hs_dev. SO_MSGLIMIT accepts 1, so msglimit / 2 is zero and one recvmsg() on its own socket is enough for an unprivileged process to take a spurious disconnect.  It also calls iucv_send_ctrl() under spin_lock_bh(&message_q.lock), which allocates GFP_KERNEL inside a section the code treats as atomic. Sending outside that lock lets two recvmsg() reach afiucv_hs_send() at once, where msg_recv is sampled for the advertised window and subtracted after dev_queue_xmit() -- and sendmsg reaches that counter under lock_sock() while recvmsg holds no socket lock, so both can subtract the same value, the counter goes negative and the credit reaches the peer twice.  Test the transport, claim the credit with atomic_xchg() after the last error exit and hand it back if the transmit fails, and send once the lock is dropped.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99136",
                        "url": "https://ubuntu.com/security/CVE-2026-99136",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  dm-crypt: fix a tiny race condition in crypt_dec_pending  crypt_dec_pending reads io->error before calling atomic_dec_and_test. Another context, for example crypt_endio called from an interrupt, may set io->error and drop its reference between the read and the decrement. crypt_dec_pending then drops the last reference and completes the bio with the stale status - so a read that failed and was never decrypted, or a write that failed, is reported as successful.  The read was placed before the decrement by commit b35f8caa0890 (\"dm crypt: wait for endio to complete before destruction\"), because that commit freed dm_crypt_io before calling bio_endio. This is no longer the case, dm_crypt_io lives in the per-bio data now.  Read io->error after atomic_dec_and_test instead. atomic_dec_and_test is fully ordered, so no additional barrier is needed.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99138",
                        "url": "https://ubuntu.com/security/CVE-2026-99138",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  tcp: fix use-after-free in do_tcp_getsockopt(TCP_CC_INFO)  do_tcp_getsockopt() reads icsk->icsk_ca_ops and dereferences the get_info function pointer without rcu_read_lock(). With BPF struct_ops congestion control, ca_ops can point to dynamically allocated memory that is freed concurrently, resulting in a use-after-free when the kernel dereferences or calls through the stale pointer.    BUG: KASAN: slab-use-after-free in do_tcp_getsockopt+0x2037/0x23e0   Read of size 8 at addr ffff888013701258 by task exploit/149    do_tcp_getsockopt+0x2037/0x23e0 (net/ipv4/tcp.c:4564)    tcp_getsockopt+0x91/0xf0    __sys_getsockopt+0xf7/0x170  Fix this by wrapping the ca_ops load and get_info call within rcu_read_lock()/rcu_read_unlock(), and using READ_ONCE() to load the icsk_ca_ops pointer.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99100",
                        "url": "https://ubuntu.com/security/CVE-2026-99100",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: p54: validate firmware record lengths  The p54 firmware parser accesses component ID and component version records without checking that their lengths cover the fields being read. A malformed record can therefore make the parser read past the record.  Validate the component ID and component version record lengths before accessing their data. The descriptor record is also checked against the shortest descriptor length found in the supported firmware images.  Reject descriptor values that underflow the RX offset or produce an empty RX range before updating the driver state.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-28 04:18:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99140",
                        "url": "https://ubuntu.com/security/CVE-2026-99140",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  tracing: Fix hist trigger timestamps for buffered events  Syzkaller triggered a WARN_ON_ONCE(!nest) warning:    WARNING: kernel/trace/ring_buffer.c:821 at ring_buffer_event_time_stamp   Call trace:     ring_buffer_event_time_stamp     hist_field_timestamp     hist_fn_call     event_hist_trigger     event_triggers_call     __event_trigger_test_discard     trace_event_buffer_commit     do_trace_event_raw_event_sched_switch     trace_event_raw_event_sched_switch  The warning is probabilistically reproducible and is related to syzkaller executing the following commands:    echo 'prev_pid == 999999' > events/sched/sched_switch/filter   echo 'hist:keys=common_timestamp' > events/sched/sched_switch/trigger  The specific triggering process is as follows:  CPU 0                                           CPU 1 (context switching)                             (echo 'hist:keys=common_timestamp' > \\                                                        events/sched/sched_switch/trigger) do_trace_event_raw_event_##call   trace_event_buffer_lock_reserve     if (!tr->no_filter_buffering_ref &&         trace_file->flags & EVENT_FILE_FL_FILTERED)         return entry;  // return directly                                                 event_hist_trigger_parse                                                   hist_register_trigger                                                    tracing_set_filter_buffering(file->tr, true);                                                      tr->no_filter_buffering_ref++;     __trace_buffer_lock_reserve       rb_start_commit         local_inc(&cpu_buffer->committing);  // skipped and not executed   trace_event_buffer_commit     __event_trigger_test_discard       event_triggers_call         event_hist_trigger           hist_fn_call             hist_field_timestamp               ring_buffer_event_time_stamp                 nest = local_read(&cpu_buffer->committing);                 WARN_ON_ONCE(!nest)  // trigger warning  The root cause is that when an event file has a filter attached and the hist trigger has not yet been attached, trace_event_buffer_lock_reserve() writes the event into the per-CPU trace_buffered_event temp buffer instead of reserving it in the ring buffer, so cpu_buffer->committing is not incremented. When the event is later processed at commit time by a hist trigger, hist_field_timestamp() -> ring_buffer_event_time_stamp() sees a zero committing count, triggering WARN_ON_ONCE(!nest).  tracing_event_time_stamp() was added by commit d8279bfc5e959 (\"tracing: Add tracing_event_time_stamp() API\") for exactly this case: if the event is the per-CPU trace_buffered_event, it returns the current ring buffer timestamp. But it never gained a caller. Use it in hist_field_timestamp(), so that a hist trigger that races onto a buffered event records the current time, which is only marginally later than when the event was recorded, instead of warning and recording a bogus timestamp.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99150",
                        "url": "https://ubuntu.com/security/CVE-2026-99150",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  drm/amdgpu: don't drop the runtime PM reference twice in amdgpu_gpr  amdgpu_debugfs_gpr_read() drops its runtime PM reference right after reading the wave registers. When copying them to userspace fails, it jumps to the err label, which drops the reference a second time. A read into a bad buffer on Navi31 either steals a reference somebody else holds (power/runtime_usage goes from 1 to 0) or underflows the count:    amdgpu 0000:03:00.0: Runtime PM usage count underflow!  The registers are already in the kernel buffer at that point, so finish the hardware access first and copy the buffer with a single copy_to_user() instead of the put_user() loop with its own error path.  (cherry picked from commit 31035bbd74f7c3e10c163db875b8e67f8b50ee6a)",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99152",
                        "url": "https://ubuntu.com/security/CVE-2026-99152",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  scsi: libiscsi: Validate the task named by a management response  __iscsi_complete_pdu() fetches the task for five response types from one place and checks only that the index resolved:        case ISCSI_OP_LOGOUT_RSP:       case ISCSI_OP_LOGIN_RSP:       case ISCSI_OP_TEXT_RSP:       case ISCSI_OP_SCSI_TMFUNC_RSP:       case ISCSI_OP_NOOP_IN:               task = iscsi_itt_to_task(conn, hdr->itt);               if (!task)                       return ISCSI_ERR_BAD_ITT;  iscsi_itt_to_task() bounds the index against cmds_max and looks at nothing else, so a target can name any slot in the pool, including one that has never been used. task->conn is then NULL, and both iscsi_nop_out_rsp() and iscsi_complete_task() dereference it. One unsolicited NOP-In is enough; a Text Response carrying the same ITT crashes in iscsi_complete_task() instead.  Require the task to be in flight and not a SCSI command, the way iscsi_itt_to_ctask() does for the command opcodes.  [    6.298634] Oops: general protection fault, probably for non-canonical address 0xdffffc000000000c: 0000 [#1] SMP KASAN NOPTI [    6.298642] KASAN: null-ptr-deref in range [0x0000000000000060-0x0000000000000067] [    6.298652] CPU: 1 UID: 0 PID: 111 Comm: iscsistart Not tainted 7.2.0-rc5-ISCSI1-gf5098b6bae76 #1 PREEMPT(lazy) [    6.298654] Hardware name: QEMU Ubuntu 24.04 PC v2 (i440FX + PIIX, arch_caps fix, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 [    6.298656] RIP: 0010:iscsi_nop_out_rsp.constprop.0+0x46/0x160 [    6.298691] Code: c1 ea 03 48 83 ec 08 80 3c 02 00 0f 85 f5 00 00 00 48 b8 00 00 00 00 00 fc ff df 48 8b 6b 58 48 8d 7d 60 48 89 fa 48 c1 ea 03 <80> 3c 02 00 0f 85 c0 00 00 00 48 8b 45 60 48 39 c3 74 50 48 b8 00 [    6.298698] RSP: 0018:ffff88806c907be8 EFLAGS: 00010206 [    6.298701] RAX: dffffc0000000000 RBX: ffff888006116800 RCX: 0000000000000020 [    6.298702] RDX: 000000000000000c RSI: ffff88800525d578 RDI: 0000000000000060 [    6.298703] RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000 [    6.298706] R10: 0000000000000020 R11: 0000000000000000 R12: 0000000000000000 [    6.298706] R13: 000000000000002e R14: ffff8880056eb440 R15: ffff888006116800 [    6.298707] FS:  00007fc02d1c2740(0000) GS:ffff8880b29bc000(0000) knlGS:0000000000000000 [    6.298710] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [    6.298711] CR2: 000055fe3b56ddf8 CR3: 00000000053b9004 CR4: 0000000000770ef0 [    6.298712] PKRU: 55555554 [    6.298713] Call Trace: [    6.298714]  <IRQ> [    6.298714]  __iscsi_complete_pdu+0x13a8/0x22a0 [    6.298758]  iscsi_complete_pdu+0x54/0xa0 [    6.298759]  iscsi_tcp_hdr_recv_done+0x870/0x2c80 [    6.298778]  iscsi_tcp_recv_skb+0x31e/0xec0 [    6.298800]  iscsi_sw_tcp_recv+0x12f/0x390 [    6.298804]  __tcp_read_sock+0x1ab/0x810 [    6.298812]  iscsi_sw_tcp_data_ready+0x18b/0x510 [    6.298814]  tcp_rcv_established+0x1f56/0x3a00 [    6.298842]  tcp_v4_do_rcv+0x449/0x960 [    6.298847]  tcp_v4_rcv+0x2245/0x3bc0",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99153",
                        "url": "https://ubuntu.com/security/CVE-2026-99153",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  scsi: libiscsi: Validate the ITT reflected in a Reject PDU  A Reject PDU carries a copy of the header it rejects, and iscsi_handle_reject() takes the ITT out of that copy to find the task to clean up:        memcpy(&rejected_pdu, data, sizeof(struct iscsi_hdr));       ...       task = iscsi_itt_to_task(conn, rejected_pdu.itt);  That value is whatever the target put there. iscsi_itt_to_task() bounds the index against cmds_max and checks nothing else, so any task in the pool can be named, and iscsi_nop_out_rsp() then completes it.  An index that has never been used gives a NULL task->conn: the pool is zeroed at session setup and conn is assigned only when a task is allocated. If the task was used and returned, iscsi_complete_task() hits its WARN_ON_ONCE(task->state == ISCSI_TASK_FREE) and the refcount underflows. An in-flight SCSI command is completed as successful - a 1 MiB read returned 1048576 with none of its buffer written and no warning.  Validate the reflected ITT the way iscsi_itt_to_ctask() validates a command ITT, and require the task to be in flight and not a SCSI command.  [    6.248477] Oops: general protection fault, probably for non-canonical address 0xdffffc000000000c: 0000 [#1] SMP KASAN NOPTI [    6.249357] KASAN: null-ptr-deref in range [0x0000000000000060-0x0000000000000067] [    6.249951] CPU: 1 UID: 0 PID: 0 Comm: swapper/1 Not tainted 7.2.0-rc5-ISCSI1-gf5098b6bae76 #1 PREEMPT(lazy) [    6.250718] Hardware name: QEMU Ubuntu 24.04 PC v2 (i440FX + PIIX, arch_caps fix, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 [    6.251616] RIP: 0010:iscsi_nop_out_rsp.constprop.0+0x46/0x160 [    6.252043] Code: c1 ea 03 48 83 ec 08 80 3c 02 00 0f 85 f5 00 00 00 48 b8 00 00 00 00 00 fc ff df 48 8b 6b 58 48 8d 7d 60 48 89 fa 48 c1 ea 03 <80> 3c 02 00 0f 85 c0 00 00 00 48 8b 45 60 48 39 c3 74 50 48 b8 00 [    6.252813] RSP: 0018:ffff88806c907b80 EFLAGS: 00010206 [    6.253042] RAX: dffffc0000000000 RBX: ffff88800607e000 RCX: ffffffff8d571a25 [    6.253345] RDX: 000000000000000c RSI: ffff88806c907c38 RDI: 0000000000000060 [    6.253642] RBP: 0000000000000000 R08: 0000000000000000 R09: fffffbfff235a504 [    6.253947] R10: 0000000000000003 R11: 7463656e6e6f6320 R12: 0000000000000000 [    6.254251] R13: 0000000000000000 R14: ffff88806c907c38 R15: 0000000000000000 [    6.254549] FS:  0000000000000000(0000) GS:ffff8880d95bc000(0000) knlGS:0000000000000000 [    6.254887] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [    6.255140] CR2: 00007fc393e8ffc0 CR3: 0000000005252006 CR4: 0000000000770ef0 [    6.255439] PKRU: 55555554 [    6.255564] Call Trace: [    6.255674]  <IRQ> [    6.255768]  __iscsi_complete_pdu+0x18bf/0x22a0 [    6.256733]  iscsi_complete_pdu+0x54/0xa0 [    6.256905]  iscsi_tcp_data_recv_done+0xf4/0x250 [    6.257103]  iscsi_tcp_recv_skb+0x31e/0xec0 [    6.257680]  iscsi_sw_tcp_recv+0x12f/0x390 [    6.258061]  __tcp_read_sock+0x1ab/0x810 [    6.258853]  iscsi_sw_tcp_data_ready+0x18b/0x510 [    6.259808]  tcp_data_queue+0x1f13/0x4cd0 [    6.260567]  tcp_rcv_established+0x8a5/0x3a00 [    6.261931]  tcp_v4_do_rcv+0x449/0x960 [    6.262269]  tcp_v4_rcv+0x2245/0x3bc0",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99154",
                        "url": "https://ubuntu.com/security/CVE-2026-99154",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  scsi: libiscsi: Reject a negative task index from parse_pdu_itt  A transport that implements parse_pdu_itt hands libiscsi an index taken from the PDU, and both lookups bound it from above only:        if (i >= session->cmds_max)  i and cmds_max are both int, so a negative index passes and session->cmds[i] is read from before the array.  be2iscsi produces one. beiscsi_parse_pdu() assigns the raw tag,        *index = (int)itt;  and beiscsi_complete_pdu() forwards an unsolicited NOP-In from the hardware async ring without replacing its ITT, so the value is the target's. It also reports the session's own age rather than the one in the tag, which leaves the age comparison in iscsi_verify_itt() with nothing to reject.  Bound the index from below in both lookups.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99165",
                        "url": "https://ubuntu.com/security/CVE-2026-99165",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  sctp: revalidate output stream after association connect wait  When message interleaving is enabled, the first send waits for association establishment before building its data chunks.  The wait drops the socket lock, and handshake processing can reduce the output stream count to the peer-advertised inbound stream count.  sctp_stream_init() then frees the extension of every removed stream.  The sender resumes with the stream that it checked before the wait.  If the peer removed that stream, sctp_outq_tail() later dereferences its NULL extension.  Fatal-oops policies then panic the host.  KASAN: null-ptr-deref in range [0x38-0x3f] RIP: sctp_outq_tail+0x49e/0xaa0 Call Trace:  sctp_primitive_SEND  sctp_sendmsg_to_asoc  sctp_sendmsg  A range check alone is insufficient.  Stream reconfiguration can grow the output count again while the lock is released without recreating extensions freed by the earlier shrink.  The stream can then be in range while its extension remains NULL.  The send-buffer wait has the same issue.  Factor the range and extension checks into a helper and repeat both after each send-path wait that drops the socket lock.  Once the lock is reacquired, the validation remains stable through data creation and queueing.  If validation fails after the connect wait, the auto-created association is already established.  Return ESRCH so the existing caller path keeps it under state-machine ownership instead of freeing it directly, which would leave protocol, counter and socket state inconsistent.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99166",
                        "url": "https://ubuntu.com/security/CVE-2026-99166",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net: rds: fix uninitialized trans dereference in CM event handler  rds_rdma_cm_event_handler_cmn() assigns trans only when the RDMA device is an InfiniBand CA (RDMA_NODE_IB_CA).  On any other device type, e.g. an iWARP RNIC such as siw, trans stays uninitialized, but the event switch dereferences it: unconditionally in the RDMA_CM_EVENT_CONNECT_REQUEST case via trans->cm_handle_connect(), and (with a connection context) in the ROUTE_RESOLVED and ESTABLISHED cases.  An RDS listener on an iWARP device therefore crashes the kernel as soon as a connect request arrives: with CONFIG_INIT_STACK_ALL_ZERO the wild load becomes a NULL dereference at offset 0xa0 (&trans->cm_handle_connect) in the iw_cm_wq workqueue.  GCC masks the bug in default builds by folding the uninitialized load into &rds_ib_transport; Clang-built kernels take the real uninitialized path and oops.  The active side can land on a non-IB device too: the id that rds_ib_conn_path_connect() creates is not restricted to a node type, so rdma_resolve_addr() binds it to whichever device serves the local address, and an iWARP RNIC on the same netdev qualifies.  The crash there is different: resolving a route on an iWARP id never fills in cm_id->route.path_rec, and the ROUTE_RESOLVED case writes path_rec[0].sl before it calls into the transport.  The iWARP transport was dropped long ago and IB is the only transport left, so make that explicit: initialize trans to &rds_ib_transport at declaration, drop the conditional assignment, reject a connect request that arrives on a non-IB device, and drop a connection whose address resolved to one instead of resolving a route on it.  The rejection is limited to RDMA_CM_EVENT_CONNECT_REQUEST on purpose: a non-zero return from the handler makes rdma_cm destroy the id the event was delivered on, which is right for the request's freshly created id but would free a connection id that RDS still owns for any other event.  On the active side the id stays ic->i_cm_id and the connection's shutdown destroys it, so that case returns 0.  [achender: reject only on RDMA_CM_EVENT_CONNECT_REQUEST instead of  bailing out for every event on a non-IB device, so that rdma_cm does  not destroy connection ids RDS still tracks; drop a connection whose  address resolved to a non-IB device before a route is resolved on it;  changelog adjusted]",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99167",
                        "url": "https://ubuntu.com/security/CVE-2026-99167",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net/sched: fix use-after-free in __tcf_action_put()  __tcf_action_put() decrements the reference count before decrementing the binding count. Another thread can free the action between these operations, causing the binding-count update to access freed memory. KASAN reports it as:    BUG: KASAN: slab-use-after-free in __tcf_action_put+0x327/0x340   Write of size 4 at addr ff11000000d46420 by task tc-put-pause/64  Hold the action IDR mutex across both counter updates and IDR removal, keeping cleanup outside the lock.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99175",
                        "url": "https://ubuntu.com/security/CVE-2026-99175",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  fsnotify: prevent mark additions during connector teardown  fsnotify_destroy_marks() keeps a reference to its current mark while it drops conn->lock to destroy the mark. This stabilizes the forward-walk cursor, but does not prevent a new mark from being inserted before it. For example, an inotify watch re-added after IN_IGNORED sorts before the old, detached mark for the same group. The walk can miss the replacement and then detach the entire connector from the object.  The replacement is still on its group's marks_list and, for inotify, in the watch IDR. The group mutex no longer protects the connector's object from disappearing. An unprivileged fdinfo read racing the final detach can consequently call igrab(NULL):    BUG: KASAN: null-ptr-deref in igrab+0x24/0x100   Write of size 4 at addr 0000000000000148   Call Trace:    igrab+0x24/0x100    inotify_show_fdinfo+0x1dc/0x5e0    seq_show+0x397/0x690  Set a DESTROYING flag under conn->lock before starting the walk, and reject new marks on that connector with -ENOENT. The existing add-mark error paths undo the temporary group-list entry and the backend's watch allocation. Do not wait for teardown while holding the group mutex, which the destroyer needs. Once the old connector is detached, an add can install a fresh connector as before.  This closes the insertion race for all object types using the common connector teardown, without changing the mark reference or SRCU lifetime rules.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99176",
                        "url": "https://ubuntu.com/security/CVE-2026-99176",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  KVM: nVMX: Reset MMU back to the root MMU if loading L2 state fails for !VM-Entry  Reset the vCPU's MMU pointer back to the root MMU if loading L2 state fails in the \"not from VM-Entry\" case, i.e. when emulating RSM or handling KVM_SET_NESTED_STATE.  Failure to unwind the MMU pointer results in KVM trying to run L1 with a nested MMU, and is especially problematic if the vCPU manages to free its nested state before the VM crashes.  Constructing the root for a nested EPT MMU goes through vmcs12, which is dynamically allocated/freed when nVMX is enabled/disabled.  And so if the nested state is freed with the MMU still pointing at the nested MMU, KVM will hit a NULL pointer deref when attempting to get L1=>L2 EPTP.    BUG: kernel NULL pointer dereference, address: 0000000000000078   #PF: supervisor read access in kernel mode   #PF: error_code(0x0000) - not-present page   PGD 114a2d067 P4D 111743067 PUD 11141f067 PMD 0   Oops: Oops: 0000 [#1] SMP   CPU: 20 UID: 1000 PID: 1272 Comm: nested_tdp_faul Not tainted 7.3.0-rc4-8c89f11d1a99b-sink-vm #1914 PREEMPTLAZY   Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015   RIP: 0010:nested_ept_get_eptp+0xb/0x10 [kvm_intel]   Call Trace:    <TASK>    kvm_mmu_load+0xcd/0x870 [kvm]    kvm_arch_vcpu_ioctl_run+0x18f5/0x1f80 [kvm]    kvm_vcpu_ioctl+0x2c7/0x970 [kvm]    __x64_sys_ioctl+0x90/0xd0    do_syscall_64+0x9c/0x4d0    entry_SYSCALL_64_after_hwframe+0x4b/0x53   RIP: 0033:0x47491b    </TASK>   Modules linked in: kvm_intel kvm irqbypass   CR2: 0000000000000078   ---[ end trace 0000000000000000 ]---   RIP: 0010:nested_ept_get_eptp+0xb/0x10 [kvm_intel]  [sean: write changelog]",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99181",
                        "url": "https://ubuntu.com/security/CVE-2026-99181",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  autofs: ignore notification errors from a replaced pipe  autofs_notify_daemon() takes a reference to the current notification pipe under wq_mutex, then drops the mutex before writing the request. The write can block while the daemon enters catatonic mode and installs a replacement pipe.  If the old pipe's reader is then closed, the delayed write returns -EPIPE and the generic error path enters catatonic mode again. That transition acts on the current superblock state, closes the replacement pipe, and releases the new daemon generation's wait queues.  Only enter catatonic mode when the pipe which failed is still the current pipe. Factor the already-locked transition so the identity check and state change are atomic with respect to another replacement.  This was reproduced on v7.3-rc5-337-gff47652a4b66c in a local QEMU guest. An unprivileged UID 65534 lookup filled the old packet pipe before a normal CATATONIC/SETPIPEFD restart. On the unmodified kernel, the new pipe received HUP and both a pending victim lookup and a later lookup failed with ENOENT in two out of two fresh-mount runs.  With this change, the new pipe remained active, received an intact 304-byte request, and both victim lookups completed in two out of two runs. Normal lookup and restart-without-a-blocked-writer controls passed. No KASAN, oops, refcount, or lock diagnostic was observed. A source reproducer and complete local logs are available privately on request.  The demonstrated impact is limited to denial of a shared autofs service during a legitimate daemon restart. No memory corruption, information leak, privilege escalation, or code execution primitive was observed.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99201",
                        "url": "https://ubuntu.com/security/CVE-2026-99201",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  netlink: avoid hashing the network namespace pointer  The netlink rhashtable key includes a raw struct net pointer and a user-controlled port ID. Both /proc/net/netlink and socket diagnostics expose the table's bucket order. By binding and rebinding chosen NETLINK_USERSOCK port IDs, an unprivileged reader can distinguish equal buckets and recover the low bits of the Jenkins hash. Its 32-bit seed and the limited set of kernel-image slides can then be searched offline to recover the address of init_net.  Use the namespace's unique, non-address net_cookie in the comparison key instead. It is assigned before the per-net initializers run and remains unchanged for the namespace's lifetime. The lookup key and object hash are still built by netlink_compare_arg_init(), keeping lookup, insertion, removal and rehashing consistent while preserving namespace separation. Neither public table walker needs to change.  Reading the socket's namespace cookie in netlink_compare() is safe under RCU, including during namespace teardown. netlink_release() removes the socket from the hash table and defers its final put with call_rcu(). cleanup_net() runs the per-net exit methods and waits for outstanding RCU callbacks with rcu_barrier() before freeing namespace storage.  Unlike ns.ns_id, net_cookie is also available and initialized during setup_net() in older stable kernels, making the change straightforward to backport to v5.15 and later.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99203",
                        "url": "https://ubuntu.com/security/CVE-2026-99203",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  pipe: preserve existing fasync readers on writer setup failure  F_SETFL and FIOASYNC decide whether to invoke ->fasync() before pipe_fasync() takes pipe->mutex. Two enables of one O_RDWR FIFO can therefore both enter the callback.  fasync_helper() allocates before checking for an existing entry. If the first enable installs both entries, a second enable can update the reader entry and then fail the allocation for the writer entry. The error path removes the pre-existing reader entry, clearing FASYNC while the writer entry remains registered. __fput() then skips ->fasync(), so a later pipe notification can dereference the freed file or its f_owner. An unprivileged memory-pressure reproducer triggers a KASAN slab-use-after-free in send_sigio() through this path.  Keep the reader helper's result and undo the registration only if this call added it. The pipe mutex serializes changes to both lists, so a failed new registration still removes its reader, while a failed duplicate preserves the existing registrations and FASYNC. Successful duplicate enables continue to update fa_fd as before.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99204",
                        "url": "https://ubuntu.com/security/CVE-2026-99204",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ocfs2/dlm: Protect the recovery list during debugfs reads  Recovery participant records must remain alive while debug_state_print() walks reco.node_data and formats their fields. The formatter holds dlm->spinlock, but the recovery participant list is protected by dlm_reco_state_lock. In particular, dlm_destroy_recovery_area() detaches the list under dlm_reco_state_lock and frees the detached records after releasing it. A concurrent debugfs open can therefore read freed memory.  Protect the participant traversal and field reads in debug_state_print() with dlm_reco_state_lock, matching the existing list writers. This also serializes the traversal against list_add_tail() during recovery-area initialization. Make the existing lock available to the debug code through dlmcommon.h; the lock remains internal to the OCFS2 DLM module.  Release dlm->spinlock after formatting the other domain state and before acquiring dlm_reco_state_lock, so the debug reader does not nest the two locks. Leave recovery list insertion, detachment and freeing unchanged.  KASAN report as below:      BUG: KASAN: slab-use-after-free in debug_state_open+0x1169/0x12d0     Read of size 4 at addr ffff88810662ef80 by task dlm-state-stres/896      CPU: 1 UID: 0 PID: 896 Comm: dlm-state-stres Not tainted 7.3.0-rc4-next-20260921-pmb-ocfs2-functional-v1+ #1 PREEMPT(lazy)     Hardware name: QEMU Ubuntu 24.04 PC v2 (i440FX + PIIX, arch_caps fix, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014     Call Trace:      <TASK>      dump_stack_lvl+0x93/0xd0      print_report+0xce/0x630      ? debug_state_open+0x1169/0x12d0      ? srso_alias_return_thunk+0x5/0xfbef5      ? __virt_addr_valid+0x20e/0x420      ? debug_state_open+0x1169/0x12d0      kasan_report+0xe0/0x110      ? debug_state_open+0x1169/0x12d0      debug_state_open+0x1169/0x12d0      ? __pfx_debug_state_open+0x10/0x10      full_proxy_open_regular+0x193/0x310      do_dentry_open+0x595/0x12d0      ? __pfx_full_proxy_open_regular+0x10/0x10      vfs_open_consume+0xd1/0x400      ? srso_alias_return_thunk+0x5/0xfbef5      path_openat+0x18d0/0x2020      ? __pfx_path_openat+0x10/0x10      do_file_open+0x21e/0x470      ? __pfx_do_file_open+0x10/0x10      ? _raw_spin_unlock+0x23/0x40      ? srso_alias_return_thunk+0x5/0xfbef5      ? alloc_fd+0x3a6/0x6b0      do_sys_openat2+0xf4/0x1b0      ? __pfx_do_sys_openat2+0x10/0x10      ? srso_alias_return_thunk+0x5/0xfbef5      ? __fput+0x5b5/0xa60      __x64_sys_openat+0x136/0x1e0      ? __pfx___x64_sys_openat+0x10/0x10      do_syscall_64+0x114/0x620      entry_SYSCALL_64_after_hwframe+0x77/0x7f     [Register dump omitted.]      </TASK>      Allocated by task 880:      kasan_save_stack+0x33/0x60      kasan_save_track+0x14/0x30      __kasan_kmalloc+0xaa/0xb0      __kmalloc_cache_noprof+0x28d/0x610      dlm_remaster_locks+0x147/0x1d90      dlm_do_recovery+0xde1/0x1580      dlm_recovery_thread+0x109/0x300      kthread+0x351/0x460      ret_from_fork+0x659/0x940      ret_from_fork_asm+0x1a/0x30      Freed by task 880:      kasan_save_stack+0x33/0x60      kasan_save_track+0x14/0x30      kasan_save_free_info+0x3b/0x60      __kasan_slab_free+0x5f/0x80      kfree+0x308/0x580      dlm_destroy_recovery_area+0x285/0x460      dlm_remaster_locks+0x17c4/0x1d90      dlm_do_recovery+0xde1/0x1580      dlm_recovery_thread+0x109/0x300      kthread+0x351/0x460      ret_from_fork+0x659/0x940      ret_from_fork_asm+0x1a/0x30      The buggy address belongs to the object at ffff88810662ef80      which belongs to the cache kmalloc-32 of size 32     The buggy address is located 0 bytes inside of      freed 32-byte region [ffff88810662ef80, ffff88810662efa0)      [Page and memory-state dumps omitted.]",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99206",
                        "url": "https://ubuntu.com/security/CVE-2026-99206",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  scsi: target: iscsi: Fix race in discovery auth updates  Separate configfs opens can concurrently update the discovery AuthMethod parameter. Both callers may free the same value in iscsi_update_param_value(), causing a double-free.  Protect the lookup and replacement with the discovery TPG access lock, as used by the other TPG configfs parameter updates.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99211",
                        "url": "https://ubuntu.com/security/CVE-2026-99211",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  netlink: reset skb headers before unicast and multicast filtering  Socket filters can use SKF_NET_OFF and SKF_LL_OFF to read relative to an skb's network and MAC headers. Netlink producers may reserve headroom without resetting those headers, allowing a receiving socket's filter to read data before the initialized message.  For example, IWPM HELLO replies are allocated with dev_alloc_skb(), which reserves NET_SKB_PAD bytes. An unprivileged NETLINK_RDMA user can attach a classic socket filter and disclose this headroom through the length of the delivered reply. The resets in netlink_dump() do not help because IWPM sends a separately allocated skb through netlink_unicast().  Reset both headers before running the receiver's filter in unicast and broadcast delivery, as is already done for dump skbs. This also covers other netlink producers that reserve headroom without changing their allocation or message-building code.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99212",
                        "url": "https://ubuntu.com/security/CVE-2026-99212",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net/rds: don't let the rdma_cm destroy an id RDS still owns on route failure  rds_rdma_cm_event_handler_cmn() hands the return value of rdma_resolve_route() straight back to the rdma_cm on RDMA_CM_EVENT_ADDR_RESOLVED.  A synchronous failure there - -ENOMEM from the route work allocation, an SA query that cannot be set up, a RoCE route with no usable device - makes addr_handler() destroy the id the event was delivered on.  That id is ic->i_cm_id, and nothing clears the pointer: the connection sits in RDS_CONN_CONNECTING with a freed id until its shutdown calls rdma_disconnect() and rdma_destroy_id() on it.  The ROUTE_RESOLVED case already avoids this: rds_ib_cm_initiate_connect() forces a zero return while ic->i_cm_id == cm_id, as the comment there explains.  Do the same here - drop the connection and return 0 - so the id stays RDS's to destroy from the shutdown, and the reconnect gets a fresh one.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99213",
                        "url": "https://ubuntu.com/security/CVE-2026-99213",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  vsock: treat TCP_CLOSING as once-established  Handle the TCP_ESTABLISHED -> TCP_CLOSING transition on OP_RST, which can race with the connect loop. Immediately break and return 0 on ESTABLISHED/CLOSING. The return value of connect() should reflect what happened up to the point the connection was established or failed. Events that occur afterwards must not affect it. E.g. even if OP_RW has already set sk_err, connect() should still return 0, not ENOBUFS because of it. Adapt the inaccurate comment above signal_pending().  Resetting a socket that is still present in connected_table can lead to memory corruption. The reporter noted lost transports for in-flight skbs, and I have reproduced crashes caused by re-insertion into connected_table.    list_add double add: new=, prev=, next=.   kernel BUG at lib/list_debug.c:35!   Oops: invalid opcode: 0000 [#1] SMP KASAN NOPTI   Workqueue: vsock-loopback vsock_loopback_work   RIP: 0010:__list_add_valid_or_report+0x11f/0x130   Call Trace:    vsock_insert_connected.cold+0xe/0x13    virtio_transport_recv_pkt+0x10e9/0x1460    vsock_loopback_work+0x305/0x480    process_one_work+0xe4c/0x1560    worker_thread+0x4f1/0xd60    kthread+0x36e/0x470    ret_from_fork+0x47b/0x6b0    ret_from_fork_asm+0x1a/0x30  This fix is supplementary to commit 002541ef650b (\"vsock: Ignore signal/timeout on connect() if already established\"). Details under Link.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99216",
                        "url": "https://ubuntu.com/security/CVE-2026-99216",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  Drivers: hv: Don't reset VMBus connection state on error/exit paths  In two places, current code forces vmbus_connection.conn_state to DISCONNECTED prior to calling vmbus_disconnect(). But vmbus_disconnect() calls vmbus_initiate_unload(), which unloads the VMBus connection only if the conn_state is CONNECTED. Consequently, the connection remains and the Hyper-V host might continue to send messages or post VMBus interrupts.  The problem was introduced in commit 74347a99e73ae (\"x86/Hyper-V: Unload vmbus channel in hv panic callback\"), in that vmbus_initiate_unload() started checking the current connection state before doing the unload. This commit removed some occurrences where conn_state was forced to DISCONNECTED, but these two remained, apparently due to an oversight at the time.  Fix this by not forcing conn_state to DISCONNECTED during VMBus exit, or if a failure occurs when establishing the connection in the first place. Whatever value conn_state has at the time is then read by vmbus_initiate_unload() to determine if there is a connection to be unloaded.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2022-50167",
                        "url": "https://ubuntu.com/security/CVE-2022-50167",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  bpf: fix potential 32-bit overflow when accessing ARRAY map element  If BPF array map is bigger than 4GB, element pointer calculation can overflow because both index and elem_size are u32. Fix this everywhere by forcing 64-bit multiplication. Extract this formula into separate small helper and use it consistently in various places.  Speculative-preventing formula utilizing index_mask trick is left as is, but explicit u64 casts are added in both places.",
                        "cve_priority": "high",
                        "cve_public_date": "2025-06-18 11:15:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99082",
                        "url": "https://ubuntu.com/security/CVE-2026-99082",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  KVM: x86: Use active memslots for the per-vCPU MMIO cache  KVM tags the per-vCPU MMIO cache with a memslot generation so that a memslot update invalidates cached MMIO information.  Both the fill and validation paths use kvm_memslots(), which unconditionally selects address space 0, even when the vCPU is running in SMM and using address space 1.  Commit 56f17dd3fbc4 (\"kvm: x86: fix stale mmio cache bug\") added the memslot generation to the cache key so that a memslot update could not leave a stale entry valid.  When commit 699023e23965 (\"KVM: x86: add SMM to the MMU role, support SMRAM address space\") added the SMM address space, these helpers were not converted to use the active memslots.  Consequently, an update to the SMM memslots can leave an entry from the old SMM address space apparently valid after the vCPU returns to the normal address space.  A guest can then cause an access to valid RAM at the same GFN to be returned to userspace as KVM_EXIT_MMIO.  Completing that exit through the VMM's RAM address space writes the backing page without going through KVM's write-tracking path.  If the page backs a nested EPT table, KVM can continue using shadow translations derived from the old contents.  The WARN_ON_ONCE() in kvm_mmu_write_protect_fault() catches this invalid cache and memslot combination.  Use the vCPU's active memslots when caching and validating the entry. Memslot generations are unique across address spaces, so the generation also distinguishes the normal and SMM views.  This matches the MMIO SPTE cache, which already uses kvm_vcpu_memslots().  On an unpatched current-mainline kernel, a regression test that fills the cache in SMM and updates only the SMM memslots fails the intended RAM write and triggers the kvm_mmu_write_protect_fault() warning.  With this change, the same test completes the RAM write without a warning.  The x86/smm_test, set_memory_region_test, and memslot_modification_stress_test selftests also pass.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99083",
                        "url": "https://ubuntu.com/security/CVE-2026-99083",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ksmbd: fix heap out-of-bounds write in krb5_authenticate()  In krb5_authenticate(), out_len is calculated to determine available headroom in response_buf for the incoming Kerberos AP-REP token. However, when SMB2_SESSION_SETUP is processed as a non-first element of a compounded SMB2 request, the calculation omits work->next_smb2_rsp_hdr_off.  This causes out_len to overstate remaining buffer headroom by the cumulative size of prior responses in the compound chain. Consequently, the length check in ksmbd_krb5_authenticate() (*out_len <= resp->spnego_blob_len) passes erroneously, allowing memcpy() to write the AP-REP blob past the end of response_buf into adjacent kernel heap memory.  Fix this by subtracting work->next_smb2_rsp_hdr_off when computing out_len, ensuring it accurately reflects physical remaining buffer space.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98977",
                        "url": "https://ubuntu.com/security/CVE-2026-98977",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  namespace: handle mount locking for automounts correctly  If mounts are propagated across user namespaces, attach_recursive_mnt() locks every copy of the source mount to protect overmounts from vanishing and revealing the underlying files or directories.  The user namespace is taken from the caller's mount namespaces since this is where the mounts end up. Except, that's not always true. Automounts may legitimately get popped in by tasks located in a different mount and user namespace during path lookup.  Then check doesn't make sense at that point. The copy in the namespace of the parent - which may be the host's - is now locked and the host cannot change the flags of its own mounts anymore.  Here's the reproducer:  - host has debugfs mounted nosuid,nodev,noexec and shared - tracefs automount below it is not yet active - hand a child process a directory descriptor on that mount - child process enters auser and mount namespace - child process' namespace now holds a locked copy of the host's debugfs   mount that receives propagation from it - child process stats \"tracing/.\" through the descriptor - lookup runs on the host's mount so the automount lands below the host's mount - propagation puts a copy below the child's copy - both try to clear the flags on the mount they got, with a bind remount:      host, on its own automount:            MS_REMOUNT|MS_BIND = EPERM     child, on the copy in its namespace:   MS_REMOUNT|MS_BIND = 0  So the lock landed on the host's mount instead of the child's copy. Congrats. So we need to compare with the owner of the namespace the mount actually gets mounted on. For all regular cases that is the caller's mount namespace and so nothing changes.  Detached trees in anonymous mount namespaces by be handed over via SCM_RIGHTS or inherited in other ways on purpose so the attaching task's mount namespace is authoritative, not the creator of the detached tree.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98992",
                        "url": "https://ubuntu.com/security/CVE-2026-98992",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  namespace: don't copy an unmounted mount tree  may_copy_tree() accepts a mount whose root is an nsfs or pidfs file before it checks whether that mount is mounted. This exception exists for nsfs and pidfs mounts. They are part of no mount namespace so neither check_mnt() nor is_mounted() would let them through and bind-mounting a nsfsfd or a pidfd wouldn't work.  Problem is that exception also admits a bind mount of such a file when it was lazily unmounted and is only kept alive by a file descriptor:    mount --bind /proc/self/ns/net /tmp/x   exec 3< /tmp/x   umount -l /tmp/x   mount --rbind /proc/self/fd/3 /tmp/y  With MS_REC or AT_RECURSIVE copy_tree() doesn't stop at the unmounted mount. It copies every mount that stayed attached to it as well. So if you have a bunch of overmounts over the nsfsfd or the pidfd the whole unmounted stack is copied. That's a bug.  So refuse to walk an unmounted tree. Copying its root alone stays possible. So a bind mount of a namespace that is gone can still be recreated from a file descriptor on the old one. The file descriptor pins that mount and its root and __has_locked_children() only reads the direct children which don't leave the parent's list without namespace_sem. The internal mounts carry MNT_NS_INTERNAL instead of NULL and are still walked. Copying an unmounted tree recursively fails with EINVAL.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98981",
                        "url": "https://ubuntu.com/security/CVE-2026-98981",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  namespace: unhash a dentry before detaching the mounts on it  unlink(), rmdir() and rename() remove the entry from the filesystem, call detach_mounts() on the entry with the inode locked and then call d_delete() once the inode is unlocked.  The thing is that between detach_mounts() and d_delete() the dentry is still hashed and positive. But after detach_mounts() nothing covers the dentry anymore. A lookup that finds this dentry in the dcache can uncover what the mounts hid.  That's a problem when unlinking files or directories that are mountpoints in other mount namespaces. Everybody who had the underlying entry covered can race the detach_mount() call until d_delete() has run.  The race window isn't all that small. It encompasses namespace_unlock() with a full synchronize_rcu_expedited() grace period and the inode_unlock() of the entry.  In my experiments three walkers that kept trying read an overmounted file in 11938 of the 16140 unlinks that removed its mountpoint from a bind mount of the filesystem within a minute.  Fun fact, d_invalidate() has the same ordering problem but gets it right. It unhashes the dentry first and detaches the mounts afterwards. Let's do the same in __detach_mounts():  - A lookup that hasn't found the dentry yet misses it in the dcache and   waits for the directory lock that the caller holds until the name is   gone for good.  - A lockless lookup that found it already fails the mount_lock check   while the dentry still counts as a mountpoint and the d_seq check once   it doesn't, and retries.  This fixes the lockless path. We still need to fix the reference count lookup in a follow-up patch.  So d_drop() the dentry. The dentry stays positive and held but can't be found anymore. Then proceed with the detach and unlink.  Reproducer:  The reads were counted with the program below, three walkers for 60 s in a VM with 4 CPUs. The race window is stretched with the debug patch pasted here. fs.detach_race_walk_us sleeps in lookup_fast() once it found a mountpoint dentry and before its mounts are crossed. fs.detach_race_unlink_us sleeps in vfs_unlink() between detach_mounts() and d_delete().    // SPDX-License-Identifier: GPL-2.0   /*    * unlink_covered: unlink a file that is a mountpoint in a detached copy of    * its mount, against lookups that open it through that copy.    *    * A is a tmpfs with the file f1 (content SECRET_F) and the plain file    * MARK_A. A' is an open_tree(OPEN_TREE_CLONE) copy of A with MARK_A bound    * on A'/f1, held through an O_PATH fd on its root once the tree fd is    * closed. Walkers open f1 through that fd while the driver unlinks A/f1,    * where nothing is mounted on it. A walker may read MARK_A or get ENOENT.    * A read of SECRET_F is a hit: the name was found after its mount was    * gone. The lockless walks use openat2(RESOLVE_CACHED).    *    * usage: unlink_covered [-t seconds] [-w walkers]    */   #ifndef _GNU_SOURCE   #define _GNU_SOURCE   #endif   #include <errno.h>   #include <fcntl.h>   #include <pthread.h>   #include <stdatomic.h>   #include <stdio.h>   #include <stdlib.h>   #include <string.h>   #include <unistd.h>   #include <sys/mount.h>   #include <sys/stat.h>   #include <sys/syscall.h>   #include <linux/openat2.h>    #ifndef __NR_open_tree   #define __NR_open_tree 428   #endif   #ifndef __NR_move_mount   #define __NR_move_mount 429   #endif   #ifndef __NR_openat2   #define __NR_openat2 437   #endif   #ifndef OPEN_TREE_CLONE   #define OPEN_TREE_CLONE 1   #endif   #ifndef OPEN_TREE_CLOEXEC   #define OPEN_TREE_CLOEXEC O_CLOEXEC   #endif   #ifndef MOVE_MOUNT_F_EMPTY_PATH   #define MOVE_MOUNT_F_EMPTY_PATH 0x00000004   #endif    #define WORK \"/tmp/uc\"   #define ADIR WORK \"/A\"    static int duration = 60, nwalkers = 3;   static atomic_int stop, writer_waiting;   static pthread_rwlock_t cur_lock = PTHREAD_RWLOCK_INITIALIZER;   static int cur_fd = -1;\t\t/* the root of A', -1 wh ---truncated---",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99005",
                        "url": "https://ubuntu.com/security/CVE-2026-99005",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  drm/i915/gt: Unmask interrupts only when ACTIVE is true  There is a small race window between intel_rps_boost() reading a stale ACTIVE state and queuing rps->work, where ACTIVE may be changed via asynchronous calls triggered by wakeref drop. This means that rps_work() could be triggered after the GT has been parked, so unmasking RPS PM interrupts would happen without holding PM wakelock. This sequence of events may be observed during live_rc6_ctx_wa() selftest:  1) live_rc6_ctx_wa()    -> intel_engine_pm_put()       -> wakeref_put()  ASYNC1) wakeref_put() callback           -> __engine_park()              -> intel_gt_pm_put_async()                 -> intel_gt_pm_put_async_untracked()                    -> intel_wakeref_put_async()  ASYNC2) wakeref_put_async() callback           -> __gt_park()              -> intel_rps_park()                 -> intel_rps_clear_active() [clear ACTIVE]                 WITH INTERRUPTS:                 -> rps_disable_interrupts()                    -> cancel_work_sync(rps->work)                    -> rps_reset_interrupts() [rps->pm_iir = 0]                 WITHOUT INTERRUPTS (TIMER mode):                 -> rps_stop_timer()                    -> cancel_work_sync(rps->work)  2) live_rc6_ctx_wa()    -> intel_gt_wait_for_idle()       -> intel_gt_retire_requests_timeout()          -> dma_fence_wait_timeout()             -> ops->wait() [i915_fence_wait()]                -> i915_request_wait_timeout()                   -> intel_rps_boost()                      -> intel_rps_is_active() [check ACTIVE]                         [OPEN RACE WINDOW]                      -> queue_work(rps->work)          -> retire_requests()             -> i915_request_retire()                -> intel_rps_dec_waiters() [from 1 to 0]  If ASYNC1 and ASYNC2 would execute during [OPEN RACE WINDOW], then:  3) rps_work() executes from the workqueue and may satisfy    \"(!pm_iir && !client_boost)\" test (in TIMER mode rps->pm_iir    is zeroed by an earlier rps_work() call or never gets a new    value after previous intel_rps_unpark() event), so it jumps    to \"out\" label, bypassing intel_rps_is_active() guard and    executes gen6_gt_pm_unmask_irq();  4) GT is parked and runtime PM wakelock is dropped, so only    a raw reference in __gt_park() ->    intel_display_power_put_async() remains for 100ms, then the    MMIO write in gen6_gt_pm_unmask_irq() detects missing    wakelock via assert_rpm_wakelock_held() and emits    \"RPM wakelock ref not held during HW access\" tainting kernel.  Commit 3e7abf814193 (\"drm/i915: Extract GT render power state management\") dropped the \"if (rps->interrupts_enabled)\" guard that gen6_pm_rps_work() had around this unmask in i915_irq.c. INTEL_RPS_ACTIVE brackets the same window, since it is set in intel_rps_unpark() before rps_enable_interrupts() and rps_start_timer() and cleared in intel_rps_park() before rps_stop_timer() and rps_disable_interrupts().  Skip unmasking when RPS is no longer active (reaching unmask operation is independent of INTERRUPT mode). This does not prevent RPS operation from resuming on the next unpark. In interrupt mode, intel_rps_unpark() calls rps_enable_interrupts(), which enables and unmasks the PM interrupts. In timer mode, it calls rps_start_timer(), restarting periodic engine-busyness evaluation. The timer generates software RPS events and queues rps_work() directly, independently of PM interrupt delivery. Neither mode requires the late worker to unmask interrupts while the GT is parked  (cherry picked from commit ca4a6deadad15b91ee083afe445fa6bdbfb68206)",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99007",
                        "url": "https://ubuntu.com/security/CVE-2026-99007",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  drm/fb-helper: defer setup when fbdev_probe() fails, not just on -EAGAIN  __drm_fb_helper_initial_config_and_unlock() calls drm_client_modeset_probe() first, which already fills in each mode_set->mode/num_connectors for every connected output, and only afterwards calls drm_fb_helper_single_fb_probe() to create fb_helper->fb and wire it into those mode_sets via drm_setup_crtcs_fb().  If drm_fb_helper_single_fb_probe() fails with anything other than -EAGAIN (e.g. dev->driver->fbdev_probe() itself fails), the function bails out before drm_setup_crtcs_fb() runs and before setting fb_helper->deferred_setup. The client is left with mode_sets that have a mode and connectors but mode_set->fb == NULL, and nothing marks this fb_helper as needing a retry.  __drm_fb_helper_restore_fbdev_mode_unlocked() only skips committing when fb_helper->deferred_setup is set, so a later .restore() call (drm_lastclose() on process exit, in this report) commits the stale mode_set through drm_client_modeset_commit() -> drm_client_modeset_commit_atomic() -> __drm_atomic_helper_set_config(), which hits WARN_ON(!set->fb).  Mark fb_helper->deferred_setup on any drm_fb_helper_single_fb_probe() failure, not just -EAGAIN, so restore keeps skipping the commit until a later hotplug event successfully re-probes and re-populates mode_set->fb. The real error code is still returned to the caller unchanged.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99019",
                        "url": "https://ubuntu.com/security/CVE-2026-99019",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  scsi: ch: Do not keep references to data transfer element devices  ch_readconfig() looks up the scsi_device of every data transfer element whose SCSI id the changer reports in READ ELEMENT STATUS, and stores it in ch->dt[]. scsi_device_lookup() takes a reference, and nothing ever drops it: ch_destroy() frees the array with kfree(). ch->dt[] is read nowhere else - it only supplies the vendor, model and revision printed in the same loop.  Once such a drive is removed, its scsi_device can never be released. It stays on the host's device list at its address, so a new device there is refused by anything that walks the list - target_core_pscsi reports \"scsi_device_get() failed for H:C:T:L\" - and the low-level driver's module can no longer be unloaded. Only a reboot recovers.  It shows with any changer that reports its drives' ids; with the mhvtl virtual library (IBM 3573-TL personality), each create and remove of a library with four drives leaves four references behind, counted by the module's use count in lsmod. With ch not bound the count is unchanged, and with this patch applied it is unchanged too.  Drop the reference as soon as the name has been printed, and remove the now unused dt[] array. That also removes the array leaked when ch_probe() fails after ch_readconfig().  The same leak was reported with an RFC patch in 2022, which was not merged.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99024",
                        "url": "https://ubuntu.com/security/CVE-2026-99024",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  optee: register TEE devices only once fully initialized  optee_probe() called tee_device_register() on both the client and the supplicant device before the rest of struct optee had been initialized.  tee_device_register() calls cdev_device_add(), which does two things at once: it creates /dev/tee0 and /dev/teepriv0, and it links the device into the tee class so that class_find_device() can find it. From that moment on the device is reachable both from user space via tee_open() and from kernel space via tee_client_open_context(). The only gate in teedev_open() is tee_device_get(), which merely checks that teedev->desc is non-NULL, which was already set by tee_device_alloc(). Therefore, there is effectively no gate at all.  A context opened in that window can run against a struct optee where    - optee->call_queue.mutex is not initialized by optee_cq_init()   - optee->supp mutex and completions is not initialized by     optee_supp_init()   - optee->rpmb_dev_mutex is not initialized yet,   - the message argument cache is not initialized by     optee_shm_arg_cache_init()   - optee->ctx is still NULL  Any open session or invoke during this window takes uninitialized mutexes and dereferences a NULL pointer.  Fix it by moving both tee_device_register() calls down to the point where all of struct optee is set up.  [JW: adding fixes and cc]",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99036",
                        "url": "https://ubuntu.com/security/CVE-2026-99036",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  dm: fix reading free memory in do_resume  When do_resume calls dm_table_get_mode(new_map), the call is done without holding any locks (it only holds a reference to the md). It may be possible that another concurrent ioctl on the same device will swap table after dm_swap_table and before dm_table_get_mode. In this case, dm_table_get_mode(new_map) reads freed memory.  This race condition was triggered by syzbot.  This commit fixes the race by reading mode of the new table before dm_swap_table. Note that new_map is also passed to dm_ima_need_measure, but this function doesn't attempt to dereference it, so this call should be safe.  Note that this is not a security bug because only root can trigger it and the commonly used tools such as lvm or cryptsetup do not call the ioctls concurrently, so that they can't trigger it acceidentally.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98985",
                        "url": "https://ubuntu.com/security/CVE-2026-98985",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  namespace: check the mounts before reading their parents in pivot_root()  path_pivot_root() reads the parents of new_root and of the caller's root and checks whether they are shared before it checks that either mount is in the caller's mount namespace. Only namespace_sem is held. That's fine for a mount that is in the caller's mount namespace.  But new_root can be a file descriptor to a mount that has been unmounted and that only the file descriptor keeps alive. If that mount stayed attached to its parent when it was unmounted nothing pins the parent for it. The final mntput() of the parent unhooks the children under mount_lock alone and frees the parent afterwards:    pivot_root()                     close(fd), last ref on the parent   ------------                     ---------------------------------   ex_parent = new_mnt->mnt_parent                                    mntput_no_expire_slowpath()                                      __umount_mnt(new_mnt)                                    cleanup_mnt()                                      call_rcu()   IS_MNT_SHARED(ex_parent)    BUG: KASAN: slab-use-after-free in path_pivot_root+0xf1a/0x1840   Read of size 4 at addr ffff8881047382f8 by task pivot_widen/157    path_pivot_root+0xf1a/0x1840    __x64_sys_pivot_root+0x165/0x190  The same goes for the caller's root via chroot(). Both outcomes of the check end in EINVAL so nothing but the read itself goes wrong. It's the same thing commit bb4609405752 (\"statmount: read the parent of an unmounted mount under mount_lock\") fixed for statmount().  Check that both mounts are in the caller's namespace before their parents are read. Every path returns EINVAL either way.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98993",
                        "url": "https://ubuntu.com/security/CVE-2026-98993",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  namespace: don't inherit MNT_UMOUNT in clone_mnt()  MNT_UMOUNT gets raised on a mount that umount_tree() or umount_one() has taken out of its namespace. It's never cleared. __detach_mounts() unhooks a mount that carries it instead of unmounting it.  disconnect_mount() lets an unmounted child stay attached only if its parent carries it. propagate_umount() takes it as the sign that a mount is going to be unmounted when it decides what else can be unmounted, where a chain of locked mounts ends and where a for reparenting an overmount.  clone_mnt() copies the flags of the source and only masks MNT_INTERNAL_FLAGS which doesn't include MNT_UMOUNT. A mount that was lazily unmounted but is kept alive by a file descriptor can still be copied when its root is an nsfs or pidfs file because may_copy_tree() accepts those before checking whether the source is mounted at all:    mount --bind /proc/self/ns/net /tmp/x   exec 3< /tmp/x   umount -l /tmp/x   mount --bind /proc/self/fd/3 /tmp/y  The mount on /tmp/y is attached to the caller's namespace with MNT_UMOUNT already set and every copy of it inherits the flag again.  That causes a number of bugs:  - Unlink its mountpoint from a mount namespace where it isn't one.   __detach_mounts() takes it for a mount that was unmounted earlier,   unhooks it from its parent and drops the reference the namespace   holds on it. It stays in the namespace with one reference too few   and as its own parent, so it can't be unmounted through the file   descriptor anymore and the namespace never finds it again. When the   namespace goes away it's leaked and points to a freed struct   mnt_namespace that may_change_propagation() and anon_ns_root() read   on the next propagation change or mount_setattr() through the file   descriptor.  - Make it shared and unmount a peer. trace_transfers() follows the   flag from the peer into it and strips it from its peer group.  - Let a propagated umount reach it. gather_candidates() marks it with   T_UMOUNT_CANDIDATE but never puts it on the candidate list, so the   mark is never cleared and every later propagated umount skips it. If   it's the parent of a locked mount handle_locked() takes it as the   cutoff and commits the locked child that should have stayed and   disconnect_mount() leaves that child attached to it, unmounted under   a mounted parent, which is what disconnect_mount() exists to   prevent. When the namespace goes away umount_tree() visits the child   a second time. And once __detach_mounts() has made it its own parent   reparent() never finds the end of the chain of unmounted parents.  A clone is a new mount that has never been unmounted. Add MNT_UMOUNT to MNT_INTERNAL_FLAGS so clone_mnt() never copies it. And warn when umount_tree() reaches a mount that already has it set.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99002",
                        "url": "https://ubuntu.com/security/CVE-2026-99002",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  drm/vmwgfx: validate pitch coming from userspace  Validate the pitch, alongside the box dimensions before trying to copy data from the underlying surface. Fixes possible out of bounds reads with cursor snooping.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99027",
                        "url": "https://ubuntu.com/security/CVE-2026-99027",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net: team: stop reusing skb after queue override  A nonzero dev_queue_xmit() result does not return ownership of the skb. When an override port's qdisc drops it, the queue override helper used to try another port or the mode transmit op with the freed skb.  Return the handoff decision separately from transmit success. Select only the first override port under RCU and stop after handing it the skb, regardless of the lower transmit result. Keep the existing success and drop accounting.    BUG: KASAN: slab-use-after-free in sk_skb_reason_drop   Write of size 4 by task poc/5040   sk_skb_reason_drop (net/core/skbuff.c:1240)   dev_kfree_skb_any_reason (net/core/dev.c:3470)   ab_transmit (drivers/net/team/team_mode_activebackup.c:49)   team_xmit (drivers/net/team/team_core.c:1849)   __dev_direct_xmit (net/core/dev.c:4934)   Freed by task 5040:   __tcf_kfree_skb_list (net/sched/sch_generic.c:43)   __dev_queue_xmit (net/core/dev.c:4831)   team_xmit (drivers/net/team/team_core.c:1846)   Kernel panic - not syncing: KASAN: panic_on_warn set ...",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-64190",
                        "url": "https://ubuntu.com/security/CVE-2026-64190",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net: team: fix NULL pointer dereference in team_xmit during mode change  __team_change_mode() clears team->ops with memset() before restoring safe dummy handlers via team_adjust_ops(). A concurrent team_xmit() running under RCU on another CPU can read team->ops.transmit during this window and call a NULL function pointer, crashing the kernel.  The race requires a mode change (CAP_NET_ADMIN) concurrent with transmit on the team device.   BUG: kernel NULL pointer dereference, address: 0000000000000000  Oops: 0010 [#1] SMP KASAN NOPTI  RIP: 0010:0x0  Call Trace:   team_xmit (drivers/net/team/team_core.c:1853)   dev_hard_start_xmit (net/core/dev.c:3904)   __dev_queue_xmit (net/core/dev.c:4871)   packet_sendmsg (net/packet/af_packet.c:3109)   __sys_sendto (net/socket.c:2265)  The original code assumed that no ports means no traffic, so mode changes could freely memset()/memcpy() the ops.  AF_PACKET with forced carrier breaks that assumption.  Prevent the race instead of making it safe: replace memset()/memcpy() with per-field updates that never touch transmit or receive.  Those two handlers are managed solely by team_adjust_ops(), which already installs dummies when tx_en_port_count == 0 (always true during mode change since no ports are present).  WRITE_ONCE/READ_ONCE prevent store/load tearing on the handler pointers.  synchronize_net() before exit_op() drains in-flight readers that may still reference old mode state from before port removal switched the handlers to dummies.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-07-20 17:18:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99041",
                        "url": "https://ubuntu.com/security/CVE-2026-99041",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ip6_gre: remove obsolete ERSPAN PMTU update  A tc tunnel_key action can attach a METADATA_IP_TUNNEL dst to an skb, and mirred can redirect it to a native ip6erspan device. The legacy PMTU update in ip6erspan_tunnel_xmit() treats that metadata dst as a route. Since it has no output device, dst_dev(dst)->mtu dereferences NULL.  On v7.2 with KASAN, an initial UID/GID 65534 process with CapEff 0 used self-created user and network namespaces to trigger:    KASAN: null-ptr-deref   RIP: ip6erspan_tunnel_xmit+0x10fc/0x2cc0   Kernel panic - not syncing: Fatal exception in interrupt  The update is obsolete. Commit fe1a4ca0a2b7 (\"ip6_gre: process toobig in a better way\") changed IPv6 GRE Too Big handling to update the underlay route and removed the equivalent block from __gre6_xmit(). ip6_tnl_xmit() then propagates the underlay PMTU to the overlay route.  Remove the stale ERSPAN copy and its now-unused dst variable. This eliminates the metadata-dst dereference and keeps ERSPAN aligned with IPv6 GRE PMTU handling.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-97935",
                        "url": "https://ubuntu.com/security/CVE-2026-97935",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  tracing: Set the trace clock before registering the histogram trigger  hist_register_trigger() puts the trigger on the global named_triggers list in cmd_ops->init(), and only then sets the trace clock:  \tif (data->cmd_ops->init) { \t\tret = data->cmd_ops->init(data); \t\tif (ret < 0) \t\t\tgoto out; \t}  \tif (hist_data->enable_timestamps) { \t\tret = tracing_set_clock(file->tr, hist_data->attrs->clock); \t\tif (ret) { \t\t\thist_err(tr, HIST_ERR_SET_CLOCK_FAIL, errpos(clock)); \t\t\tgoto out; \t\t}  The clock string is not checked anywhere before that call, so a named trigger using common_timestamp with an unknown clock fails after it has already become findable. event_hist_trigger_parse() then frees it without taking it off the list, and the next lookup by name reads the freed object:   ~# cd /sys/kernel/tracing/events/sched/sched_switch  ~# echo 'hist:name=foo:keys=common_pid:ts=common_timestamp:clock=bogus' > trigger  bash: echo: write error: Invalid argument  ~# echo 'hist:name=foo:keys=common_pid' > trigger    BUG: KASAN: slab-use-after-free in find_named_trigger+0xac/0xc0   Read of size 8 at addr ffff88800915d760 by task init/1    find_named_trigger+0xac/0xc0    hist_register_trigger+0xc1/0x900    event_hist_trigger_parse+0x3146/0x6af0    event_trigger_write+0xce/0x160   Freed by task 63:    kfree+0x154/0x420    trigger_kthread_fn+0xfd/0x160  Set the clock before the trigger is registered, so that nothing which can fail runs after it is published, the way commit 6f86bdeab633 (\"tracing: Fix bad hist from corrupting named_triggers list\") moved the registration below the rest of the setup.  tracing_set_filter_buffering() is reference counted, so the init failure path has to drop the reference that the clock block now takes first.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-09-25 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98944",
                        "url": "https://ubuntu.com/security/CVE-2026-98944",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  HID: steam: Refactor registration  This refactors and simplifies the registration/unregistration flow. Since we now only perform registration when the client isn't opened anymore, the logic for handling that can be removed, and the rest of the function streamlined.  We also remove the previous assumption that we have a serial number to show we're registered, replacing it with a single purpose boolean.  In a previous refactor the code for unregistering a battery if later registration steps failed was accidentally left out. As a result, a lingering power_supply object could get left over after the steam object was torn down. This is also fixed here.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98945",
                        "url": "https://ubuntu.com/security/CVE-2026-98945",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  HID: steam: Rearrange teardown sequence  This fixes a narrow window during the teardown sequence where callbacks could still be scheduled during cleanup that would then have a dangling pointer to the now-freed steam struct.  This also puts work canceling for rumble and mode switch in steam_unregister, as that shouldn't persist while the client hdev is open.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2025-40135",
                        "url": "https://ubuntu.com/security/CVE-2025-40135",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ipv6: use RCU in ip6_xmit()  Use RCU in ip6_xmit() in order to use dst_dev_rcu() to prevent possible UAF.",
                        "cve_priority": "high",
                        "cve_public_date": "2025-11-12 11:15:00 UTC"
                    },
                    {
                        "cve": "CVE-2025-38728",
                        "url": "https://ubuntu.com/security/CVE-2025-38728",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  smb3: fix for slab out of bounds on mount to ksmbd  With KASAN enabled, it is possible to get a slab out of bounds during mount to ksmbd due to missing check in parse_server_interfaces() (see below):   BUG: KASAN: slab-out-of-bounds in  parse_server_interfaces+0x14ee/0x1880 [cifs]  Read of size 4 at addr ffff8881433dba98 by task mount/9827   CPU: 5 UID: 0 PID: 9827 Comm: mount Tainted: G  OE       6.16.0-rc2-kasan #2 PREEMPT(voluntary)  Tainted: [O]=OOT_MODULE, [E]=UNSIGNED_MODULE  Hardware name: Dell Inc. Precision Tower 3620/0MWYPT,  BIOS 2.13.1 06/14/2019  Call Trace:   <TASK>  dump_stack_lvl+0x9f/0xf0  print_report+0xd1/0x670  __virt_addr_valid+0x22c/0x430  ? parse_server_interfaces+0x14ee/0x1880 [cifs]  ? kasan_complete_mode_report_info+0x2a/0x1f0  ? parse_server_interfaces+0x14ee/0x1880 [cifs]    kasan_report+0xd6/0x110    parse_server_interfaces+0x14ee/0x1880 [cifs]    __asan_report_load_n_noabort+0x13/0x20    parse_server_interfaces+0x14ee/0x1880 [cifs]  ? __pfx_parse_server_interfaces+0x10/0x10 [cifs]  ? trace_hardirqs_on+0x51/0x60  SMB3_request_interfaces+0x1ad/0x3f0 [cifs]  ? __pfx_SMB3_request_interfaces+0x10/0x10 [cifs]  ? SMB2_tcon+0x23c/0x15d0 [cifs]  smb3_qfs_tcon+0x173/0x2b0 [cifs]  ? __pfx_smb3_qfs_tcon+0x10/0x10 [cifs]  ? cifs_get_tcon+0x105d/0x2120 [cifs]  ? do_raw_spin_unlock+0x5d/0x200  ? cifs_get_tcon+0x105d/0x2120 [cifs]  ? __pfx_smb3_qfs_tcon+0x10/0x10 [cifs]  cifs_mount_get_tcon+0x369/0xb90 [cifs]  ? dfs_cache_find+0xe7/0x150 [cifs]  dfs_mount_share+0x985/0x2970 [cifs]  ? check_path.constprop.0+0x28/0x50  ? save_trace+0x54/0x370  ? __pfx_dfs_mount_share+0x10/0x10 [cifs]  ? __lock_acquire+0xb82/0x2ba0  ? __kasan_check_write+0x18/0x20  cifs_mount+0xbc/0x9e0 [cifs]  ? __pfx_cifs_mount+0x10/0x10 [cifs]  ? do_raw_spin_unlock+0x5d/0x200  ? cifs_setup_cifs_sb+0x29d/0x810 [cifs]  cifs_smb3_do_mount+0x263/0x1990 [cifs]",
                        "cve_priority": "high",
                        "cve_public_date": "2025-09-04 16:15:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-31678",
                        "url": "https://ubuntu.com/security/CVE-2026-31678",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  openvswitch: defer tunnel netdev_put to RCU release  ovs_netdev_tunnel_destroy() may run after NETDEV_UNREGISTER already detached the device. Dropping the netdev reference in destroy can race with concurrent readers that still observe vport->dev.  Do not release vport->dev in ovs_netdev_tunnel_destroy(). Instead, let vport_netdev_free() drop the reference from the RCU callback, matching the non-tunnel destroy path and avoiding additional synchronization under RTNL.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-04-25 09:16:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99088",
                        "url": "https://ubuntu.com/security/CVE-2026-99088",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net: openvswitch: validate transport header presence in set_ipv6_addr  When executing IPv6 address rewrite actions on IPv6 fragments, set_ipv6_addr() calls update_ipv6_checksum(). If parse_ipv6hdr() processes a non-first IPv6 fragment, it sets key->ip.proto to NEXTHDR_FRAGMENT and returns early without calling skb_set_transport_header().  update_ipv6_checksum() unconditionally evaluates skb_transport_offset() on entry before checking l4_proto.  Because skb->transport_header is uninitialized, this triggers a warning under CONFIG_DEBUG_NET=y although it is completely harmless.  Fix this by returning early in update_ipv6_checksum() if l4_proto is NEXTHDR_FRAGMENT. This avoids reading the uninitialized transport offset for fragments while preserving the debug warning for any other protocol where the transport header is unexpectedly missing.  See the syzbot trace:  !skb_transport_header_was_set(skb) WARNING: ./include/linux/skbuff.h:3075 at skb_transport_header include/linux/skbuff.h:3075 [inline], CPU#1: syz-executor463/5635 WARNING: ./include/linux/skbuff.h:3075 at skb_transport_offset include/linux/skbuff.h:3250 [inline], CPU#1: syz-executor463/5635 WARNING: ./include/linux/skbuff.h:3075 at update_ipv6_checksum net/openvswitch/actions.c:361 [inline], CPU#1: syz-executor463/5635 WARNING: ./include/linux/skbuff.h:3075 at set_ipv6_addr+0x462/0x660 net/openvswitch/actions.c:399, CPU#1: syz-executor463/5635 [...] RIP: 0010:skb_transport_header include/linux/skbuff.h:3075 [inline] RIP: 0010:skb_transport_offset include/linux/skbuff.h:3250 [inline] RIP: 0010:update_ipv6_checksum net/openvswitch/actions.c:361 [inline] RIP: 0010:set_ipv6_addr+0x462/0x660 net/openvswitch/actions.c:399 [...] Call Trace:  <TASK>  set_ipv6 net/openvswitch/actions.c:531 [inline]  do_execute_actions+0x557e/0x8600 net/openvswitch/actions.c:1366  ovs_execute_actions+0xde/0x520 net/openvswitch/actions.c:1592  ovs_packet_cmd_execute+0xb4f/0xf10 net/openvswitch/datapath.c:705  genl_family_rcv_msg_doit+0x233/0x340 net/netlink/genetlink.c:1114  genl_rcv_msg+0x614/0x7a0 net/netlink/genetlink.c:1209  netlink_rcv_skb+0x226/0x4a0 net/netlink/af_netlink.c:2572  genl_rcv+0x28/0x40 net/netlink/genetlink.c:1218  netlink_unicast+0x7bd/0x940 net/netlink/af_netlink.c:1361  netlink_sendmsg+0x813/0xb40 net/netlink/af_netlink.c:1916  sock_sendmsg_nosec+0x14e/0x190 net/socket.c:800",
                        "cve_priority": "negligible",
                        "cve_public_date": "2026-10-26 15:16:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98950",
                        "url": "https://ubuntu.com/security/CVE-2026-98950",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  flow_dissector: avoid u16 truncation of hlen in bpf_flow_dissect()  bpf_flow_dissect() sanitizes the offsets returned by the BPF program with clamp_t(u16, ..., hlen).  If hlen is bigger than 65535, the upper bound is truncated before the comparison. For instance, with hlen == 65536, both nhoff and thoff are forced to zero, even if the program returned sane values.  This is the same class of bug as the one fixed in commit 99bda1ecbd56 (\"flow_dissector: avoid u16 truncation of skb->len when computing thoff\"). That fix does not cover the BPF path, because __skb_flow_dissect() returns early when a BPF flow dissector handles the packet.  struct bpf_flow_keys stores nhoff and thoff as u16, so cap hlen to U16_MAX before clamping.  Found by sashiko while reviewing the commit above.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98955",
                        "url": "https://ubuntu.com/security/CVE-2026-98955",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  flow_dissector: avoid u16 truncation of skb->len when computing thoff  __skb_flow_dissect() computes key_control->thoff using:    key_control->thoff = min_t(u16, nhoff, skb ? skb->len : hlen);  min_t(u16, ...) casts both arguments to u16 before comparing them. Whenever skb->len (or hlen) modulo 65536 is smaller than nhoff, the truncated length wins and thoff is set to a bogus small value, even when the dissection succeeded. For example, an IPv4/TCP frame with skb->len == 65540 and nhoff == 34 gets thoff == 4, so callers such as skb_probe_transport_header() point the transport header inside the Ethernet header.  Such skbs are not exotic: - At the time of commit d0c081b49137 (\"flow_dissector: properly cap   thoff field\"), AF_PACKET with PACKET_VNET_HDR could already build GSO   skbs larger than 64KB (MTU checks are skipped for GSO, and   alloc_skb_with_frags() accepted up to MAX_SKB_FRAGS (17) order-0   pages on top of the linear part). - BIG TCP now makes skbs larger than 64KB common. - The following patch makes tun_get_user() dissect IFF_TAP frames   before eth_type_trans() pulls the Ethernet header, so a GSO frame   carrying a 65522..65535 byte L3 packet will be dissected with   skb->len in [65536, 65549].  Compare as u32 instead. If the resulting offset cannot be represented in the u16 key_control->thoff, cap it to U16_MAX and report the dissection as failed rather than silently returning a wrong transport offset. thoff is still set on failure, as some callers (such as eth_get_headlen()) use it regardless of the return value.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99089",
                        "url": "https://ubuntu.com/security/CVE-2026-99089",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ASoC: samsung: i2s: enable op_clk in probe to balance runtime PM  The probe function puts the device into the runtime PM active state with only the \"iis\" bus clock enabled, but it also sets priv->op_clk to the parent of the RCLK_SRC mux without enabling it. The runtime PM suspend callback disables both clocks, so the first runtime suspend after probe disables op_clk once more than it was enabled.  On Exynos5250 Arndale both clocks resolve to the same EXYNOS_I2S_BUS gate, so this triggers the following warning during boot:   WARNING: drivers/clk/clk.c:1270 at clk_core_disable+0xe4/0x23c, CPU#0: kworker/u8:3/45  i2s_bus already disabled  ...  Workqueue: pm pm_runtime_work  Call trace:   ...   clk_core_disable from clk_disable+0x28/0x34   clk_disable from i2s_runtime_suspend+0x58/0x68 [snd_soc_i2s]   i2s_runtime_suspend [snd_soc_i2s] from genpd_runtime_suspend+0xc4/0x298   genpd_runtime_suspend from __rpm_callback+0x48/0x18c   __rpm_callback from rpm_callback+0x4c/0x50   rpm_callback from rpm_suspend+0xf4/0x718   rpm_suspend from pm_runtime_work+0x9c/0xa0   ...  Fix this by enabling op_clk in probe right after getting it, so the clock state matches the runtime PM active state, and by disabling it in remove.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-26 15:16:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98956",
                        "url": "https://ubuntu.com/security/CVE-2026-98956",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ASoC: adau1372: allow sleepy powerdown GPIOs  gpiod_set_value() emits a WARN when the GPIO provider indicates that it can sleep, as is typical for I2C controlled GPIO expanders. Since the powerdown GPIO is only manipulated in process context, use the _cansleep variant instead. This lets the driver use sleepy GPIOs to power off the chip.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98964",
                        "url": "https://ubuntu.com/security/CVE-2026-98964",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  nvmet: use the local P2P device on metadata allocation failure  nvmet_req_alloc_p2pmem_sgls() assigns req->p2p_dev only after the data and metadata SGL allocations succeed. If the data allocation succeeds but the metadata allocation fails, out_free_sg passes req->p2p_dev to pci_p2pmem_free_sgl() before that assignment has taken place.  Pass the local p2p_dev argument instead, so cleanup uses the same PCI device as the successful data allocation.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98967",
                        "url": "https://ubuntu.com/security/CVE-2026-98967",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  cxgb4/ch_ktls: disable softirqs around tid_list erases  chcr_ktls_cpl_act_open_rpl() inserts into tid_list from the receive path using xa_insert_bh().  The array is shared by the adapter's connections and initialized with XA_FLAGS_LOCK_BH.  However, chcr_ktls_dev_del() and the chcr_ktls_dev_add() error path use xa_erase(), which takes the XArray lock without disabling softirqs.  When cleanup runs with softirqs enabled, a receive softirq for another connection on the same CPU can interrupt the erase and spin on the lock held by the interrupted task.  Use xa_erase_bh() at both sites to match the insertion path.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98969",
                        "url": "https://ubuntu.com/security/CVE-2026-98969",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net/sched: em_text: reject unterminated algo before autoload  This is a follow-up to commit 9c572a83037a (\"net/sched: fix potential stack infoleak in em_text_dump()\"), which zero-initialised the dump-side struct. Sashiko pointed at a pre-existing bug that exposed the change-side input-validation gap open.  em_text_change() casts the raw netlink attribute payload to struct tcf_em_text and passes conf->algo, a 16-byte array with no enforced NUL terminator, to textsearch_prepare().  On the TS_AUTOLOAD retry textsearch_prepare() calls request_module(\"ts_%s\", algo); vsnprintf() walks %s until it finds a NUL, so an algo[] with no NUL reads past the array into the adjacent struct fields and payload and feeds those bytes to the usermode helper command line.  This is an out-of-bounds read and a kernel memory disclosure.  Reject the attribute when no NUL exists within TC_EM_TEXT_ALGOSIZ bytes, matching the check xt_string has had since 3ab720881b6e.  Conditions to recreate the bug: - CAP_NET_ADMIN on the target netns (namespace-local via unshare -Urn   is enough) - install clsact on an interface, then add a basic filter with one text   ematch whose algo[] is 16 bytes with no NUL (e.g. \"A\"*16) and   pattern_len at least 1 - the add fails with -ENOENT and the kernel invokes modprobe with a   module name made of \"ts_\" plus the 16 bytes and the adjacent payload",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98970",
                        "url": "https://ubuntu.com/security/CVE-2026-98970",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  drm/vc4: Free the BO cache size list on teardown  vc4_bo_cache_destroy() purges the cached BOs but never frees the size list, leaking it on every unbind.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98971",
                        "url": "https://ubuntu.com/security/CVE-2026-98971",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  gpio: exar: initialize the ID before registering its cleanup  devm_add_action_or_reset() invokes the cleanup action immediately when registering the action fails.  gpio_exar_probe() currently stores the allocated ID in exar_gpio only after registering the action, so that failure makes exar_devm_ida_free() release ID 0.  If the allocated ID is nonzero, this leaks that ID and can free ID 0 belonging to another device.  Store the ID before registering the cleanup action so both the immediate failure path and normal device teardown release the correct allocation.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98979",
                        "url": "https://ubuntu.com/security/CVE-2026-98979",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  namespace: refuse an automount below a mount that is in no namespace  It's possible to add autmounts even when the parent mount isn't in the mount namespace of the caller. The only requirement we have is that the parent mount namespace must not be NULL, i.e., unmounted.  Problem is that clone_private_mount() has MNT_NS_INTERNAL which makes that trivially true. So that passes the test and attach_recursive_mnt() accepts that as a mount point and funny enough, count_mounts() dereferences MNT_NS_INTERNAL. The problem is it is an error pointer...  So we can reach this in userspace via fanotify. A filesystem mark on the lower filesystem of an overlay reports paths on the layer clone and reading the event hands out a descriptor on it. For example with debugfs as the lower layer it goes kaboom:    openat(evfd, \"tracing\", O_DIRECTORY)    Oops: general protection fault   KASAN: null-ptr-deref in range [0x1d0-0x1d7]   RIP: 0010:count_mounts+0x35/0x200    attach_recursive_mnt    finish_automount  And since that sleeping beauty happens under namespace_sem held for writing every mount operation on the system blocks from then on. Congrats.  Use is_mounted() instead which rejects unmounted and internal mounts alike. The open fails with EINVAL just as it did before clone_private_mount() used MNT_NS_INTERNAL.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98984",
                        "url": "https://ubuntu.com/security/CVE-2026-98984",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  dcache: don't put a mountpoint on a dentry that's being removed  rmdir(), unlink() and rename() call dont_mount() on the victim and then detach_mounts() with the victim's inode locked. do_lock_mount() takes the inode lock of the mountpoint and checks cant_mount() so a mount can't show up after detach_mounts().  But attach_recursive_mnt() makes a second mountpoint for the root of the source mount so that the mounts already located at the destination can be put on top of it. No inode is locked for that one and d_set_mounted() only refuses a dentry that is unlinked. Between detach_mounts() and d_delete() the victim is still hashed:    rmrace: b passed dont_mount() and detach_mounts(), sleeping   T2: move_mount(S, /tmp/plcant/x, BENEATH) = 0 errno 0 ()   T1: rmdir(/tmp/plcant/d/b) = 0 errno 0       109 107 0:61 /d/b//deleted /tmp/plcant/x rw,relatime - tmpfs tmpfs rw       108 109 0:63 / /tmp/plcant/x rw,relatime - tmpfs T rw  A bind mount of the directory that's being removed is moved beneath an existing mount while the rmdir() is located between the two calls. The mount ends up on the removed directory and nothing will ever detach it.  Check cant_mount() in d_set_mounted() as well. dont_mount() raises the flag under d_lock before detach_mounts() runs so either the mountpoint is set first and detach_mounts() finds the mount or the flag is seen and the mount is refused.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98990",
                        "url": "https://ubuntu.com/security/CVE-2026-98990",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  namespace: check a submount for references right before unmounting it  shrink_submounts() and mark_mounts_for_expiry() first collect all the mounts they are allowed to unmount and then unmount them.  Whether a mount is busy is decided by propagate_mount_busy() on the tree. But unmounting the first mount changes the tree that the second one propagates into. propagate_umount() moves a surviving overmount off a copy it unmounts and mounts it where the copy was mounted. If that's where the propagated copy of the second victim is looked up the overmount becomes a candidate of the second umount_tree(). It's childless and so trim_one() commits it without looking at its reference count.  So a synchronous umount pulls out a busy mount that is in use somewhere else and marks it MNT_SYNC_UMOUNT while it has users:    umount2(/tmp/plshrink/p1, 0) = 0 errno 0   cwd is (unreachable)  The same two umounts requested one after the other fail with EBUSY. This needs a mount with MNT_SHRINKABLE, i.e., automounted submounts of NFS, AFS and CIFS or the tracefs mount below debugfs. Bind mounts inherit the flag.  Check each mount right before it is unmounted under the same hold of namespace_sem and mount_lock as the umount itself. Make sure that the algorithm stays linear.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99095",
                        "url": "https://ubuntu.com/security/CVE-2026-99095",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  drm/vc4: drain the hangcheck timer and works on V3D unbind  Nothing stops the hangcheck timer that submitted jobs arm, or the job_done_work that the render-done interrupt queues, at teardown: vc4_irq_disable() cancels only overflow_mem_work, and vc4_gem_destroy() runs from the drm-managed release, after vc4_v3d_unbind() has already uninstalled the V3D interrupt and cleared vc4->v3d. A timer still armed by then reads V3D registers through the NULL vc4->v3d pointer, and the late callbacks run on the vc4_dev embedding them after it has been freed.  Drain them in vc4_v3d_unbind(): shut the timer down and cancel reset_work before the interrupt is taken down, because its vc4_irq_reset() re-enables it, then flush job_done_work so that completions queued at teardown still release their jobs.  This issue was found by an in-house static analysis tool.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-26 15:16:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99006",
                        "url": "https://ubuntu.com/security/CVE-2026-99006",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  drm/i915/gem: Prevent overstepping exec array boundary  It is possible for eb_relocate_parse_slow() to call kvfree() on entries outside the original exec array during following scenario inside eb_relocate_parse_slow():  1) eb_copy_relocations() allocates as many as eb->buffer_count    copies for exec entries; 2) eb_parse() appends up to two VMAs, right after incrementing    eb->buffer_count; 3) cleanup under \"out\" label uses this incremented buffer_count    to release relocation pointers from exec array via kvfree(),    not from VMA array.  To amend this problem, ensure that relocation cleanup uses the original exec object count, excluding the VMAs appended by the command parser.  (cherry picked from commit 2a0158925fb943c7ba8f3216e2734952128defc9)",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99008",
                        "url": "https://ubuntu.com/security/CVE-2026-99008",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  Bluetooth: RFCOMM: Fix NULL tty_dev dereference in rfcomm_dev_shutdown  syzbot hit a NULL pointer dereference in rfcomm_dev_shutdown() when an RFCOMM tty is closed.  rfcomm_dev_add() puts the new device on rfcomm_dev_list first and only then registers the tty device and saves it in dev->tty_dev. If that registration fails, dev->tty_dev is never set at all. The device can be looked up in the meantime, so an open() of /dev/rfcommN gets through rfcomm_tty_install() and attaches to it. When that tty is closed again, rfcomm_dev_shutdown() uses dev->tty_dev without checking it:    Oops: general protection fault, probably for non-canonical address   KASAN: null-ptr-deref in range [0x0000000000000040-0x0000000000000047]   RIP: 0010:rfcomm_dev_shutdown+0x48/0xb0 net/bluetooth/rfcomm/tty.c:131   Call Trace:    tty_port_shutdown+0x1bf/0x220 drivers/tty/tty_port.c:372    tty_port_close+0x4e/0x150 drivers/tty/tty_port.c:705    tty_release+0x359/0x1670 drivers/tty/tty_io.c:1718    __fput+0x418/0xa50 fs/file_table.c:512  rfcomm_dev_destruct() already copes with a NULL dev->tty_dev. Add the same check to rfcomm_dev_shutdown(), so the tty device is only moved when it was actually registered.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99010",
                        "url": "https://ubuntu.com/security/CVE-2026-99010",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  Bluetooth: RFCOMM: free the skb when the DLC has no owner  rfcomm_recv_data() hands the skb to d->data_ready() and returns 0 without freeing it, so the callback owns the skb from that point on. The tty implementation frees it when the DLC has been detached from its device:    static void rfcomm_dev_data_ready(struct rfcomm_dlc *dlc,                                     struct sk_buff *skb)   {           struct rfcomm_dev *dev = dlc->owner;            if (!dev) {                   kfree_skb(skb);                   return;           }  The socket implementation returns without freeing it, and the skb is leaked.  A connected DLC can have no owner: rfcomm_sock_destruct() clears d->owner, while the DLC itself stays on the session until it is closed. Data frames that arrive in that window still find d->state == BT_CONNECTED in rfcomm_recv_data() and are handed to the callback, one leaked skb each.  The leak does not stop on its own either.  The remote runs out of credits only once RFCOMM_RX_THROTTLED is set, and for a socket the only place that sets it is rfcomm_sk_data_ready() itself, below the return. rfcomm_process_dlcs() keeps granting credits, so the remote keeps sending and the leak keeps growing.  Free the skb, as the tty side does.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99015",
                        "url": "https://ubuntu.com/security/CVE-2026-99015",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  Bluetooth: hci_sock: Serialize dead-device detachment  Rebinding an HCI socket after its controller is unregistered can race monitor control replay and crash the kernel. hci_sock_bind() clears hci_pi(sk)->hdev and drops the device reference under only the socket lock, whereas send_monitor_control_replay() holds hci_sk_list.lock for reading.  Replay can observe a non-NULL hdev, then bind can clear it and drop the last reference before create_monitor_ctrl_open() reads hdev->id. This can cause a NULL pointer dereference if the pointer is reloaded, or a use-after-free if the old pointer is retained.  The kernel reported:    KASAN: null-ptr-deref in range [0x0000000000000068-0x000000000000006f]   RIP: 0010:create_monitor_ctrl_open+0x579/0x800   Call Trace:    hci_sock_bind+0xd96/0x1190    __sys_bind+0x166/0x200    __x64_sys_bind+0x6d/0xb0    do_syscall_64+0xdd/0x4a0    entry_SYSCALL_64_after_hwframe+0x77/0x7f  The same missing serialization lets hci_send_to_sock() select a socket for the old device and queue its frame after bind has detached the socket or installed a new binding.  Take hci_sk_list.lock for writing when clearing the device pointer and resetting the socket state. This waits for existing replay and delivery readers to finish before detachment and prevents later readers from using the old binding. Keep hci_dev_put() outside the critical section because the final device release can sleep.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99022",
                        "url": "https://ubuntu.com/security/CVE-2026-99022",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  regulator: ltc3676: don't read the write-only HRST and CLIRQ registers  HRST (0x1e) and CLIRQ (0x1f) are write-only command strobes. Writing HRST triggers a hard reset of the chip and writing CLIRQ clears the interrupt; reading them returns nothing useful, and the read itself fires the command.  The result is that a plain register dump resets the board:    cat /sys/kernel/debug/regmap/2-003c/registers  walks every readable register, hits HRST, and the board reboots.  Split the callback back in two so HRST and CLIRQ stay writable but are no longer readable. The readable range is left unchanged (LTC3676_BUCK1 ... LTC3676_IRQSTAT).",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99025",
                        "url": "https://ubuntu.com/security/CVE-2026-99025",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  openvswitch: fix soft lockup in the netlink flow dump  A production compute node carrying a few thousand datapath flows hit a soft lockup inside a single netlink flow dump and panicked.  ovs_flow_cmd_dump() calls ovs_flow_stats_get() for every flow it emits, and that releases stats->lock with spin_unlock_bh() once per CPU that has touched the flow. Every release is a local_bh_enable(), and each one runs the pending softirq backlog in the dumping thread's own context.  The skb bounds the flows one callback emits, but not the softirq work it absorbs. On a CPU that carries the box's packet load the backlog refills as fast as it drains, so the dumping thread becomes that CPU's softirq engine. It never sleeps and it has no reschedule point, so under voluntary preemption nothing can take the CPU away from it: neither the ksoftirqd the kernel woke to take the work over, nor the stopper thread the softlockup detector dispatches to refresh its timestamp.  Hold BH off across the whole callback instead, the way ctnetlink_dump_table() does, so the nested spin_unlock_bh() stop draining softirqs. The loop already runs under rcu_read_lock() and cannot sleep. What it gives up is preemption under CONFIG_PREEMPT, since a BH-off region is not preemptible outside PREEMPT_RT. The region stays short: the skb caps the flows one callback emits, and empty buckets cost no skb space but are each visited once per dump, as the cursor only moves forward. The table grows on insert and shrinks only on flush, so the walk is bounded by the largest flow count the datapath has held. The softirq backlog the callback used to absorb has no bound at all.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99031",
                        "url": "https://ubuntu.com/security/CVE-2026-99031",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net: bridge: avoid recursive multicast port cleanup  br_multicast_sg_del_exclude_ports() removes automatically added STAR_EXCL port groups by calling br_multicast_del_pg(). For S,G entries, that deletion calls back into br_multicast_sg_del_exclude_ports(), so a large number of STAR_EXCL ports consumes one kernel stack frame per port and can hit the stack guard page.  Keep the complete port-group deletion path for cleanup, but suppress the S,G exclude-port cleanup while that helper is already walking the same entry. Normal deletion callers retain the existing behavior.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99032",
                        "url": "https://ubuntu.com/security/CVE-2026-99032",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net/smc: protect clcsock lifetime in smc_getname  smc_getname() dereferences smc->clcsock without holding clcsock_release_lock. Link-group termination can release the CLC socket through smc_close_active_abort() while the SMC socket is still open, for example after shutdown(SHUT_WR).  A getsockname() caller can load smc->clcsock, then the termination worker can clear the pointer and call sock_release() before the caller accesses clcsock->ops or invokes getname(). This causes a use-after-free; if the worker clears the pointer before the load, it causes a NULL dereference. The syscall's file reference keeps the SMC socket alive but does not prevent asynchronous release of its CLC socket.  KASAN reported the following with test-only timing instrumentation:    BUG: KASAN: slab-use-after-free in smc_getname+0x19e/0x1b0   Read of size 8 at addr ffff888109abb4e0 by task poc/103   Call Trace:    smc_getname+0x19e/0x1b0    do_getsockname+0xe5/0x170    __sys_getsockname+0x8c/0x100    Allocated by task 95:    sock_alloc_inode+0x1e/0x280    sock_alloc+0x3d/0x240    __sock_create+0x7e/0x430    smc_create+0x121/0x240    Freed by task 0:    kmem_cache_free+0xcc/0x340    rcu_core+0x50a/0x1850    Last potentially related work creation:    evict+0x446/0x6c0    smc_clcsock_release+0xa8/0xd0    smc_close_active_abort+0x26a/0x3a0    __smc_lgr_terminate.part.0+0x137/0x2e0  Hold clcsock_release_lock across the pointer check and the getname() callback to serialize with smc_clcsock_release(). Return -EBADF if the CLC socket has already been released, preserving the existing peer state check and the callback's return value otherwise.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99033",
                        "url": "https://ubuntu.com/security/CVE-2026-99033",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net/packet: guard the ll header push in packet_rcv_spkt()  packet_rcv_spkt() restores the link layer header with  \tskb_push(skb, skb->data - skb_mac_header(skb));  That subtraction is only meaningful when the device actually has a link layer header.  packet_rcv() and tpacket_rcv() both wrap it in dev_has_header(), which is also the predicate the block comment at the top of the file states the restore in terms of; packet_rcv_spkt() does not.  commit d549699048b4 (\"net/packet: fix packet receive on L3 devices without visible hard header\") introduced the helper and changed the two call sites, and this one stayed behind.  A device without a visible ll header can leave skb->mac_header at the 0xFFFF sentinel that __alloc_skb() initialises it to.  A CAN skb does: init_can_skb() sets pkt_type and ip_summed but does not reset the headers, and commit 9f10374bb024 (\"can: remove private CAN skb headroom infrastructure\") dropped the skb_reset_*_header() calls that used to be there.  skb_mac_header() is then 0xFFFF, the length becomes a large negative number and skb_push() reports it through skb_under_panic() -- from softirq context, so it is a full system panic even with panic_on_oops=0:    skbuff: skb_under_panic: text:ffffffff8bd21bc1 len:-65455 put:-65471 head:... data:... tail:0x50 end:0x180 dev:can0   kernel BUG at net/core/skbuff.c:214!   RIP: 0010:skb_panic+0x50/0x60   Call Trace:    <IRQ>    skb_push+0x38/0x40    packet_rcv_spkt+0xe1/0x170    __netif_receive_skb_core.constprop.0+0x7e8/0xd30    ...   Kernel panic - not syncing: Fatal exception in interrupt  The socket type is reachable: packet_create() accepts SOCK_PACKET alongside SOCK_RAW and SOCK_DGRAM behind the same CAP_NET_RAW check, and neither the socket length nor a capability check keeps it away from a CAN interface.  The missing skb_reset_*_header() calls in init_can_skb() are a regression in their own right and are being fixed separately, but a packet socket should not turn a link layer that did not initialise its mac header into a kernel panic.  Guard the push the way the other two receive paths do.  Tested on v7.3-rc5 under QEMU with a slcan device on a pty, which is the driver RX path: vcan does not reproduce it, because can_send() resets the headers on the way out.  One SOCK_PACKET socket bound to can0 and one frame written into the line discipline panics an unpatched kernel with the trace above; the same image with this patch prints no panic and powers off normally.  Both kernels are this tree, defconfig plus CONFIG_CAN_SLCAN=y, differing only in this hunk.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99034",
                        "url": "https://ubuntu.com/security/CVE-2026-99034",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  mmc: sdhci-sprd: disable runtime PM on remove  sdhci_sprd_probe() enables runtime PM, while sdhci_sprd_remove() does not perform the corresponding runtime PM cleanup.  The probe failure path disables runtime PM before disabling the clocks, but the normal remove path directly disables clocks that are also managed by the runtime PM callbacks. If the device is runtime suspended, those clocks may already be disabled.  Resume the device before removal, disable runtime PM and drop the temporary runtime PM reference before disabling the clocks.  This issue was found by manual code inspection.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99035",
                        "url": "https://ubuntu.com/security/CVE-2026-99035",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  mmc: mtk-sd: Cancel request timeout work on remove  The driver queues req_timeout while a request is active. msdc_request_done() uses cancel_delayed_work(), which does not wait for a timeout callback that has already started.  The timeout callback calls mmc_request_done(), which wakes the request waiter, and then continues to use host->dev_comp and check the SDIO IRQ. During unbind, msdc_drv_remove() can return and the managed mmc_host can be freed before the callback finishes.  KASAN reported use-after-free accesses in msdc_request_done() and msdc_recheck_sdio_irq() in each of three unbind tests.  The same tests completed without a kernel diagnostic after this change.  Call cancel_delayed_work_sync() after mmc_remove_host() has stopped new requests and before the driver releases the host resources.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99037",
                        "url": "https://ubuntu.com/security/CVE-2026-99037",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  dm-crypt: reject the lmk IV mode with AEAD ciphers  A \"capi:\" table line that pairs an AEAD cipher with the lmk IV mode, for example \"capi:gcm(aes)-lmk\" with the integrity:28:aead option, causes an oops when it is loaded. lmk sets tfms_count to 64, but crypt_alloc_tfms_aead only allocates one transform, so crypt_setkey reads past the end of the tfms_aead array and calls crypto_aead_setkey on the values it finds there.  lmk exists for compatibility with Loop-AES, which uses CBC, so refuse it with an AEAD cipher rather than allocate 64 AEAD transforms. The check cannot go in crypt_iv_lmk_ctr with the other lmk checks, because the IV constructor runs after crypt_set_key.  Note that this is not a security bug because the memory corruption can only be triggered by root.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99038",
                        "url": "https://ubuntu.com/security/CVE-2026-99038",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  memstick: rtsx_usb_ms: complete requests after eject instead of dropping them  memstick_check() can pass its host->removing check just before rtsx_usb_ms_drv_remove() sets eject/removing. Its next request is then silently dropped: rtsx_usb_ms_request() skips schedule_work() once eject is set, and drv_remove's cancel_work_sync() can also cancel a queued handle_req before it picks the request up. Nobody completes card->mrq_complete.  Once memstick core waits for requests without a timeout (\"memstick: core: wait for request completion before freeing card\"), this hangs removal: memstick_check() never returns and memstick_remove_host() blocks in flush_workqueue():    INFO: task kworker/u10:3:65 blocked for more than 20 seconds.   Workqueue: kmemstick memstick_check    __wait_for_common    memstick_check    INFO: task kworker/1:1:33 blocked for more than 20 seconds.   Workqueue: usb_hub_wq hub_event    __flush_workqueue    memstick_remove_host    rtsx_usb_ms_drv_remove  Never drop a request. rtsx_usb_ms_request() always schedules handle_req, and handle_req fails requests with -ENOMEDIUM once eject is set, without touching the device. drv_remove flushes handle_req instead of cancelling it, and cancels it only after memstick_remove_host(), when no new request can arrive, so it cannot run on a freed host.  The host_mutex drain in drv_remove is removed: handle_req always leaves host->req NULL when it finishes, so the drain never had anything to do, and it would now race with handle_req.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99039",
                        "url": "https://ubuntu.com/security/CVE-2026-99039",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  memstick: core: wait for request completion before freeing card  In memstick_alloc_card() and memstick_set_rw_addr(), wait_for_completion_timeout() is used to wait for device identification and address configuration requests to complete.  The memstick subsystem does not provide an abort or cancellation callback in struct memstick_host for in-flight requests. If wait_for_completion_timeout() expires (for instance, when a USB transfer or command retry is delayed), memstick_alloc_card() returns an error and frees the memstick_dev structure via kfree(card).  However, the host controller driver (such as rtsx_usb_ms) is still running the request asynchronously in worker context. When the transfer eventually finishes, the driver writes into host->req->data, which points to memory inside the already freed card structure. This leads to a KASAN slab-use-after-free write:    BUG: KASAN: slab-use-after-free in ms_read_bytes+0x8fe/0x990   Write of size 1 at addr ffff88813c188079 by task kworker/1:5/5239   Workqueue: events rtsx_usb_ms_handle_req   Call Trace:    ms_read_bytes+0x8fe/0x990 drivers/memstick/host/rtsx_usb_ms.c:450    rtsx_usb_ms_issue_cmd drivers/memstick/host/rtsx_usb_ms.c:477 [inline]    rtsx_usb_ms_handle_req+0x557/0x1a00 drivers/memstick/host/rtsx_usb_ms.c:531    process_one_work+0xac7/0x1b10 kernel/workqueue.c:3396    worker_thread+0x5ef/0xe50 kernel/workqueue.c:3560    kthread+0x373/0x450 kernel/kthread.c:436    Allocated by task 1662:    memstick_alloc_card drivers/memstick/core/memstick.c:383 [inline]    memstick_check+0x2c1/0x10d0 drivers/memstick/core/memstick.c:452    process_one_work+0xac7/0x1b10 kernel/workqueue.c:3396    Freed by task 1662:    kfree+0x20c/0x650 mm/slub.c:6792    memstick_alloc_card drivers/memstick/core/memstick.c:420 [inline]    memstick_check+0x72b/0x10d0 drivers/memstick/core/memstick.c:452    process_one_work+0xac7/0x1b10 kernel/workqueue.c:3396  Host controller drivers (rtsx_usb_ms, jmb38x_ms, tifm_ms, r592) already implement their own hardware and bus timeouts, and callers in mspro_block and ms_block already rely on wait_for_completion() unconditionally.  Replace wait_for_completion_timeout() with wait_for_completion() in memstick_set_rw_addr() and memstick_alloc_card() so that the card structure is never freed while an asynchronous request is in flight.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99040",
                        "url": "https://ubuntu.com/security/CVE-2026-99040",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  KEYS: Fix add_key() race with keyring restriction  __key_create_or_update() snapshots keyring->restrict_link before taking the destination keyring's semaphore.  keyring_restrict() installs a restriction while holding that semaphore.  This allows a writer to observe no restriction, wait for the keyring owner to install a reject-all restriction and return successfully, and then link a key using the stale NULL snapshot.  The writer only needs write permission on the destination keyring.  Move the restrict_link read after __key_link_lock() and __key_link_begin().  The read and the subsequent restriction check are then serialized with restriction installation by keyring->sem.  The race was reproduced on v7.2.8 in 19 executions where restriction installation returned before the link completed.  All 19 linked the key despite the reject-all restriction.  With this change, 312 executions reached the same ordering and every add_key() call failed with -EPERM.  The issue was found by manual concurrency analysis assisted by AI-based analysis and independently verified with a QEMU reproducer and kernel instrumentation.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99045",
                        "url": "https://ubuntu.com/security/CVE-2026-99045",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ibmveth: h_free logical LAN on open-fail after register  ibmveth_open() registers the logical LAN, then allocates the RX buffer pools. A pool failure jumps to out_free_buffer_pools without h_free_logical_lan(), so PHYP still owns the buffer-list page when it is unmapped. request_irq() failure already issued the hypercall before taking the same label.  Move that h_free to the shared post-register unwind so both paths deregister before the buffer list is unmapped.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99049",
                        "url": "https://ubuntu.com/security/CVE-2026-99049",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  gpio: xilinx: fix runtime PM leak on request error path  pm_runtime_get_sync() leaves the usage counter incremented even when it fails, and xgpio_request() returns the error without dropping it.  gpiolib does not call ->free() when ->request() fails, so xgpio_free(), which holds the only matching pm_runtime_put(), never runs. The reference is leaked and the controller can no longer runtime-suspend, so its clock stays enabled.  Switch to pm_runtime_resume_and_get(), which only increments the usage counter on success.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99052",
                        "url": "https://ubuntu.com/security/CVE-2026-99052",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  selinux: preserve NATIVE_LABELS on already-initialized sb in set_mnt_opts  When an NFSv4 filesystem exported with security_label is mounted a second time, sget_fc() returns the existing superblock and nfs_get_root() calls security_sb_set_mnt_opts() again on it. Since the superblock is already SB_INITIALIZED, selinux_set_mnt_opts() takes an early exit without setting SECURITY_LSM_NATIVE_LABELS in *set_kern_flags. nfs_get_root() then sees kflags without SECURITY_LSM_NATIVE_LABELS set and clears NFS_CAP_SECURITY_LABEL on the shared nfs_server, silently disabling per-file labeling for both the new and the original mount.  Commit 3815a245b501 (\"security/selinux: fix SECURITY_LSM_NATIVE_LABELS on reused superblock\") fixed the same problem in selinux_sb_clone_mnt_opts().  The reused-superblock path for a plain second mount now goes through sb_set_mnt_opts rather than sb_clone_mnt_opts, so it needs the same treatment: on both SE_SBINITIALIZED early exits, set SECURITY_LSM_NATIVE_LABELS in *set_kern_flags when the superblock was already using SECURITY_FS_USE_NATVE.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99053",
                        "url": "https://ubuntu.com/security/CVE-2026-99053",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  tipc: hold a reference to nodes found by link name  tipc_node_find_by_name() returns a node after dropping its RCU read lock without taking a reference.  The LINK_SET, LINK_GET and LINK_RESET_STATS handlers then lock and access the node, racing with timer-driven cleanup of a down peer.  Generic netlink serialization does not exclude the node timer.  The following interleaving can leave a handler using a freed node:    CPU 0: find the node under RCU and release the node read lock   CPU 1: tipc_node_timeout() clears the links and unlinks the down node   CPU 1: drop the list and timer references, queuing tipc_node_free()   CPU 0: leave the RCU read-side critical section   CPU 1: complete the grace period and free the node   CPU 0: acquire the node lock through the stale pointer  LINK_SET also uses the node's media address after releasing the node lock, when passing queued packets to tipc_bearer_xmit().  KASAN on v7.3-rc5 reported:    BUG: KASAN: slab-use-after-free in _raw_read_lock_bh   Write of size 4 at addr ffff88807e06f008 by task poc/92   Call Trace:    _raw_read_lock_bh                 kernel/locking/spinlock.c:287    tipc_nl_node_set_link             net/tipc/node.c:2475    genl_family_rcv_msg_doit          net/netlink/genetlink.c:1114    genl_rcv_msg                      net/netlink/genetlink.c:1209    netlink_rcv_skb                   net/netlink/af_netlink.c:2575    Allocated by task 0:    tipc_node_create                  net/tipc/node.c:539    tipc_node_check_dest              net/tipc/node.c:1196    tipc_disc_rcv                     net/tipc/discover.c:252    Freed by task 92:    kfree                             mm/slub.c:6801    rcu_core                          kernel/rcu/tree.c:2919    Last potentially related work creation:    __call_rcu_common.constprop.0     kernel/rcu/tree.c:3181    tipc_node_timeout                 net/tipc/node.c:814  Acquire a reference to the selected node with kref_get_unless_zero() before leaving RCU, returning NULL if the node has already been released.  Release that reference on every caller exit after the last node access, including transmission in LINK_SET.  Keep the existing link lookup order and locking so concurrent link removal still takes the existing error paths.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99054",
                        "url": "https://ubuntu.com/security/CVE-2026-99054",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  tipc: destroy topsrv workqueues before closing connections  tipc_topsrv_stop() closed subscriber connections while the topology server's send and receive workqueues were still running. Socket callbacks and subscription events could then queue more work, and in-flight send/recv work could drop the last connection reference during the conn_idr walk.  That race produced several teardown failures: refcount_t addition on 0 from conn_get() on a connection whose release was blocked on idr_lock, a subsequent use-after-free in tipc_conn_close(), queue_work() on an already destroyed workqueue from the listener data-ready callback, and an RCU stall in tipc_topsrv_exit_net() while the walk spun under idr_lock.  Clear srv->listener under idr_lock so it acts as a shutdown flag, skip queue_work() once it is NULL, destroy the workqueues to flush in-flight work, and only then close the remaining connections. Refuse tipc_conn_lookup() after that flag is cleared, and drop idr_lock when the teardown walk finds no connection, so an in-flight subscription event cannot pin idr_in_use while the walk holds the lock.  v3 supersedes the narrower in-thread diff Tung Quang Nguyen posted on 2026-09-23. It keeps his teardown order and adds the lookup refusal and the empty-idr unlock.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99056",
                        "url": "https://ubuntu.com/security/CVE-2026-99056",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  strparser: make sure __strp_recv isn't running before tearing down the parser  The comment above strp_done() claims that if strp is stopped, strp_recv will no longer be called. That's only true if the caller has a mechanism (eg locking) to guarantee that strp_recv() calls that started before strp_stop() have completed by the time we call strp_done().  This adds a dummy lock_sock/release_sock pair to guarantee that any in-flight strp_recv() (which runs under either bh_lock_sock or lock_sock, depending if it's called from ->sk_data_ready or strp_work) has completed.  Only espintcp can be affected by this race condition, but this patch makes sure no future user of strp can have the bug.  This could crash on strp->sk (\"general mode\" of strp), but this mode has been here for 9 years and has never been used. It'll be gone soon, no point worrying about it.  Switch the stopped/paused/etc bits to u8's to avoid races between strp_stop() and strp_pause/unpause().  A reproducer has been published and turns the possible UAF into an exploit [1].",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99057",
                        "url": "https://ubuntu.com/security/CVE-2026-99057",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  xen/netfront: don't leak the skb when xennet_fill_frags() fails  When a response chain has more slots than fit in the skb's frags, xennet_fill_frags() returns an error and xennet_poll() jumps to its error path.  That path moves what's left on tmpq to errq to be freed, but the skb being filled was already dequeued from tmpq, so it's never freed.  Each chain that overflows leaks the skb and the pages attached to it as frags, and the backend decides how many slots it sends.  Put the skb back on tmpq before taking the error path, like the xennet_set_skb_gso() failure just above it does.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99058",
                        "url": "https://ubuntu.com/security/CVE-2026-99058",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  workqueue: Fix NULL current_pwq deref in chained work check  current_wq_worker() only tells us that %current is a kworker. It does not guarantee that the worker is currently executing a work item, as worker->current_pwq is populated only while process_one_work() is running the work function.  is_chained_work() can be reached while queueing on a draining or destroying workqueue. If a kworker outside work-item execution reaches that path, current_wq_worker() returns a worker but worker->current_pwq is NULL, and the chained-work test can fault before it emits the intended warning.  Guard the chained-work test with worker->current_pwq. A kworker without current_pwq is not executing work on the target workqueue, so the helper should return false and let the draining/destroying warning fire.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99059",
                        "url": "https://ubuntu.com/security/CVE-2026-99059",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wireguard: noise: reject response consumption after intermediate initiation  Two threads begin processing the identical response message, received twice. The first thread, A, runs. While it's running, the second one, B, gets partway through, and during that slow calculation, or even while blocking on down_write(), A completes and then also a handshake initiation that's already been queued up runs in thread C, which itself takes that same down_write(). The handshake initiation creation succeeds, and sets the state back to waiting-for-response, and calls up_write(), at which point thread B resumes, because either its finished its calculations or was finally allowed to acquire down_write(). Thread B then copies the state back to the peer, and begins a new session, using that state, which is the same session as the one made in thread A.  Thread A\t\t\tThread B\t\t\tThread C  down_read()  sA = handshake->state  memcpy(cA, handshake->crypto) up_read() if (sA != 1)  goto fail slow_crypto(cA) \t\t\t\tdown_read() \t\t\t\t sB = handshake->state \t\t\t\t memcpy(cB, handshake->crypto) \t\t\t\tup_read() \t\t\t\tif (sB != 1) \t\t\t\t goto fail \t\t\t\tslow_crypto(cB) down_write()  if (sA != handshake->state)   goto fail  memcpy(handshake->crypto, cA)  handshake->state = 2 up_write() down_write()  if (handshake->state != 2)   goto fail  derive_session(handshake->crypto) up_write() \t\t\t\t\t\t\t\tdown_write() \t\t\t\t\t\t\t\t slow_crypto(handshake->crypto) \t\t\t\t\t\t\t\t handshake->state = 1 \t\t\t\t\t\t\t\tup_write() \t\t\t\tdown_write() \t\t\t\t if (sB != handshake->state) \t\t\t\t   goto fail \t\t\t\t memcpy(handshake->crypto, cB) \t\t\t\t handshake->state = 2 \t\t\t\tup_write() \t\t\t\tdown_write() \t\t\t\t if (handshake->state != 2) \t\t\t\t  goto fail \t\t\t\t derive_session(handshake->crypto) \t\t\t\tup_write()  This seems basically impossible to hit in a meaningful way in practice, but ensure that it absolutely cannot happen by comparing the ephemeral private key that's on the stack with the latest one that the peer's handshake state has.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99061",
                        "url": "https://ubuntu.com/security/CVE-2026-99061",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: brcmfmac: fix P2P device removal race in brcmf_detach()  When the driver is removed while the user space process that created the P2P device (e.g. wpa_supplicant) is still exiting, the P2P device interface is removed twice and the kernel crashes.  The two paths are:   - wpa_supplicant, on exit, sends NL80211_CMD_DEL_INTERFACE for the P2P    device. nl80211_del_interface() holds RTNL and the wiphy mutex and    calls brcmf_p2p_del_vif(), which disables discovery and waits up to    1.5 s for BRCMF_E_IF_DEL. Then it calls brcmf_remove_interface(),    which unregisters the wdev and frees the vif and the ifp.   - brcmf_detach() sets the bus down, so BRCMF_E_IF_DEL never arrives,    and calls brcmf_remove_interface(ifp, false) for the same ifp.    brcmf_p2p_ifp_removed() reads ifp->vif and then blocks on    rtnl_lock(). When brcmf_p2p_del_vif() releases RTNL, it calls    cfg80211_unregister_wdev() on the wdev that was already unregistered    and freed.  The second list_del_rcu() of wdev->list faults on LIST_POISON2:    brcmfmac: brcmf_p2p_del_vif delete P2P vif   brcmfmac: brcmf_p2p_deinit_discovery enter   brcmfmac: brcmf_p2p_del_vif P2P: GO_NEG_PHASE status cleared   brcmfmac: brcmf_detach Enter   brcmfmac: brcmf_bus_change_state 1 -> 0   brcmfmac: brcmf_remove_interface Enter, bsscfgidx=1, ifidx=0   brcmfmac: brcmf_del_if Enter, bsscfgidx=1, ifidx=0   brcmfmac: brcmf_p2p_ifp_removed P2P: device interface removed   [1.5 s later, brcmf_p2p_del_vif() timed out]   brcmfmac: brcmf_remove_interface Enter, bsscfgidx=1, ifidx=0   brcmfmac: brcmf_del_if Enter, bsscfgidx=1, ifidx=0   brcmfmac: brcmf_p2p_ifp_removed P2P: device interface removed   Unable to handle kernel paging request at virtual address dead000000000122   Internal error: Oops: 96000044 [#1] PREEMPT_RT SMP   pc : _cfg80211_unregister_wdev+0x6c/0x264 [cfg80211]   Call trace:    _cfg80211_unregister_wdev+0x6c/0x264 [cfg80211]    cfg80211_unregister_wdev+0x10/0x1c [cfg80211]    brcmf_p2p_ifp_removed+0x84/0xb0 [brcmfmac]    brcmf_remove_interface+0x1f4/0x254 [brcmfmac]    brcmf_detach+0x88/0x180 [brcmfmac]    brcmf_sdio_remove+0x90/0x7b0 [brcmfmac]    brcmf_sdiod_remove+0x20/0xa0 [brcmfmac]    brcmf_ops_sdio_remove+0xbc/0x12c [brcmfmac]    sdio_bus_remove+0x38/0x144    device_release_driver_internal+0x1e8/0x2c0    device_release_driver+0x14/0x20    brcmf_sdio_bus_remove+0x2c/0x40 [brcmfmac]    brcmf_fwvid_unregister_vendor+0xd8/0x170 [brcmfmac]    __exit_compat+0x18/0x418 [brcmfmac_cyw]    __arm64_sys_delete_module+0x1ac/0x244  The log was taken with debug=0x406 on an i.MX 8M Plus board with a CYW55513 (Sona IF513) on SDIO. The driver is the Ezurio backport of brcmfmac from v6.18.22 on a 5.4-rt kernel. The code involved is the same in mainline.  To reproduce:    1. Start wpa_supplicant on wlan0 and let it associate. It creates the      P2P device (iw dev shows \"type P2P-device\").   2. Stop wpa_supplicant and remove the driver without waiting for      wpa_supplicant to exit:         kill $(pidof wpa_supplicant)        rmmod brcmfmac_cyw brcmfmac  The crash is reproducible on that board.  For the interface without a netdev (the P2P device), take RTNL and the wiphy mutex in brcmf_detach() before reading iflist, and remove it with locked=true. If brcmf_p2p_del_vif() runs first, brcmf_detach() finds the slot empty. If brcmf_detach() runs first, nl80211 does not find the wdev any more. The interfaces with a netdev are removed as before, because brcmf_del_if() takes RTNL on its own for the primary interface.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99063",
                        "url": "https://ubuntu.com/security/CVE-2026-99063",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  dm ioctl: don't let data_start run past the buffer  struct dm_ioctl has seven bytes of trailing padding, so the smallest buffer userspace is allowed to ask for, offsetof(struct dm_ioctl, data), is seven bytes shorter than sizeof(struct dm_ioctl).  get_result_buffer() sets data_start to sizeof(struct dm_ioctl) without looking at how big the buffer actually is. Ask for the minimum and data_start ends up seven bytes past the end. Callers add it to data_size, and ctl_ioctl() copies that much back to userspace:    BUG: KASAN: slab-out-of-bounds in _copy_to_user+0xad/0xd0   Read of size 312 at addr ffff8880169e4c00 by task repro-dm/140    ctl_ioctl+0x5e3/0xcb0    dm_ctl_ioctl+0x25/0x40   allocated 305-byte region [ffff8880169e4c00, ffff8880169e4d31)  A DM_LIST_DEVICES with data_size set to 305 is enough to hit it, and the seven bytes that leak are whatever sat next to the allocation.  Clamp data_start to the buffer size.  Note that this is not a security bug because the out-of-bounds read can only be triggered by root.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99067",
                        "url": "https://ubuntu.com/security/CVE-2026-99067",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  btrfs: scrub: fix local_root reference leak in scrub_print_warning_inode()  When paths_from_inode() fails, scrub_print_warning_inode() jumps to err without dropping the reference taken by btrfs_get_fs_root(), leaking a reference to the root every time path resolution fails while printing scrub warnings.  Every other error and success path of the function drops the reference.  Drop the reference on the paths_from_inode() failure path too.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99070",
                        "url": "https://ubuntu.com/security/CVE-2026-99070",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ipv6: do not warn on route notification size race  fib6_info_hw_flags_set() sizes the skb with rt6_nlmsg_size() and later fills it with rt6_fill_node().  With nexthop compatibility mode enabled, a concurrent replacement can grow the group between these independent snapshots.  rt6_fill_node() can then legitimately return -EMSGSIZE, so the warning does not prove a sizing bug.  Remove the warning.  The existing error path still frees the skb and reports the error to listeners.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99071",
                        "url": "https://ubuntu.com/security/CVE-2026-99071",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ipv4: do not warn on route notification size race  Commit 680aea08e78c (\"net: ipv4: Emit notification when fib hardware flags are changed\") added asynchronous route notifications for hardware flag changes.  fib_alias_hw_flags_set() sizes the skb with fib_nlmsg_size() and later fills it with fib_dump_info() while holding only RCU.  With nexthop compatibility mode enabled, a concurrent replacement can grow the group between these independent snapshots.  fib_dump_info() can then legitimately return -EMSGSIZE, so the warning does not prove a sizing bug.  Remove the warning.  The existing error path still frees the skb and reports the error to listeners.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99072",
                        "url": "https://ubuntu.com/security/CVE-2026-99072",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ipv4: stop route notification sizing when nexthop group shrinks  Commit 680aea08e78c (\"net: ipv4: Emit notification when fib hardware flags are changed\") added an RCU-only fib_nlmsg_size() call for asynchronous hardware flag notifications.  fib_nlmsg_size() checks fib_info_num_path() before each iteration, then fib_info_nhc() independently reloads nh->nh_grp. If RTM_NEWNEXTHOP replaces a group with fewer paths between those loads, fib_info_nhc() returns NULL and fib_nexthop_nlmsg_size() dereferences it.  Stop sizing when the indexed path is absent. Nexthop groups are dense, so the current snapshot has no later path.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98686",
                        "url": "https://ubuntu.com/security/CVE-2026-98686",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  smb: client: discard post-EOF pagecache when extending a file via zero range  smb3_zero_range() removed the pagecache only for the range being zeroed, so when it extends the file the folio straddling the old EOF - which may hold data dirtied past EOF through an mmap - was never dropped and became visible as file content once the file was extended.  Lower the discard boundary to the smaller of the zero-range offset and the old EOF.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98700",
                        "url": "https://ubuntu.com/security/CVE-2026-98700",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: mac80211: set info->band for 802.3 encap offload frames  Unlike the 802.11 TX paths, ieee80211_8023_xmit() does not set info->band from the channel context on non-MLD interfaces. It stays at 0, so ieee80211_get_tx_rates() uses the wrong band for these frames.  Set it the same way as ieee80211_build_hdr(): drop the frame if there is no channel context, and leave the band at 0 on MLD interfaces.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98716",
                        "url": "https://ubuntu.com/security/CVE-2026-98716",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  KVM: SVM: Use the active VMCB's MSR bitmap when checking if MSR is intercepted  Use the MSR permission bitmap of the active VMCB instead of assuming that KVM is always using vmcb02's bitmap when L2 is active, as KVM uses msrpm02 if and only if L1 wants to intercept MSR accesses, i.e. if and only if KVM needs to merge msprm01 with msrpm12.  Don't bother tracking the virtual address of the bitmap that's being used, as __va() is cheap on x86, and caching the virtual address would introduce yet another source of potentially stale information.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99080",
                        "url": "https://ubuntu.com/security/CVE-2026-99080",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  fs: Free any excess xarray nodes in clear_inode()  For many years we've had a hard to hit leak of xarray nodes.  Hugh documented it well in commit 786b31121a2c.  Recently people and syzbot have found ways to force it to happen with madvise.  Rather than fix the leaks where they happen, just call xa_destroy() which has the side-effect of cycling the i_pages lock.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98709",
                        "url": "https://ubuntu.com/security/CVE-2026-98709",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: mac80211: count only matching reservations in reserved switch  ieee80211_vif_use_reserved_switch() validates a replacement by counting assigned links on ctx->replace_ctx and treating reservations too broadly. A link can still be assigned to the old channel context while holding a reservation that belongs to a different replacement operation.  That can make the current replacement appear complete too early. If another link finalizes first, the function can free the WILL_BE_REPLACED chanctx while the unmatched link and driver still use it, leading to a use-after-free in later beacon generation.  Require an in-place reservation to point at the current replacement context, and require the reserved and assigned contexts to be the matching replacement pair, before counting or moving the link.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98708",
                        "url": "https://ubuntu.com/security/CVE-2026-98708",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: mac80211: keep paired old chanctx alive  An in-place replacement keeps reciprocal replace_ctx pointers between the old WILL_BE_REPLACED chanctx and the new REPLACES_OTHER chanctx. However, the early free paths only consider assigned and reserved link users when deciding whether to free the old chanctx.  That lets the old chanctx be freed too early while the replacement partner still points back to it, either when the last assigned link is released or when that link successfully reassigns to another existing context. Later unreserve and switch-finalization paths can then follow a stale replace_ctx pointer.  Keep a paired old chanctx alive until the replacement pair has been torn down. Apply the same check to both __ieee80211_link_release_channel() and ieee80211_link_use_reserved_reassign(). If the replacement is later abandoned, ieee80211_link_unreserve_chanctx() already tears down the pairing before freeing the old chanctx once no users remain.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98752",
                        "url": "https://ubuntu.com/security/CVE-2026-98752",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  tty: port: fix tty_port_tty_vhangup() race  Drivers rely on tty_port_tty_vhangup() to synchronously hang up their ports before tearing down resources as part of deregistration (e.g. on physical disconnect).  If tty_port_tty_vhangup() races with another hangup it may however return before the port has been shut down. This is in turn can lead to use-after-free and NULL-pointer dereferences in racing ioctls (including a synchronous hangup) and in processing of racing asynchronous hangups (carrier loss).  Add the missing serialisation to tty_port_tty_vhangup() and tty_port_hangup() so that the former does not return until the port has been shut down also when there is a racing hangup.  Note that serial core does not use tty_port_hangup(), but it already holds the port mutex when clearing port->tty and shutting down the port in uart_hangup().",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99081",
                        "url": "https://ubuntu.com/security/CVE-2026-99081",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  bnxt_en: fix DMA mapping length for padded small packets  Stefan Fleischmann reported Intel IOMMU DMA Read faults on BCM57412 NetXtreme-E NICs when transmitting packets on VLAN/macvlan interfaces:    DMAR: [DMA Read NO_PASID] Request device [18:00.0] fault addr 0xfc499000         [fault reason 0x06] PTE Read access is not set   bnxt_en 0000:18:00.0 eno1np0: Abandoning msg {0xb4 0x41a} len: 0 due to firmware status: 0x2000001   ...   NETDEV WATCHDOG: eno1np0 (bnxt_en): transmit queue 0 timed out  The fault address (0xfc499000) is on an exact 4KB page boundary, pointing to a DMA read buffer overrun.  In bnxt_start_xmit(), packets smaller than BNXT_MIN_PKT_SIZE (52 bytes), such as 42-byte untagged ARP frames, are padded:      if (length < BNXT_MIN_PKT_SIZE) {         pad = BNXT_MIN_PKT_SIZE - length;         if (skb_pad(skb, pad))             goto tx_kick_pending;         length = BNXT_MIN_PKT_SIZE;     }      mapping = dma_map_single(&pdev->dev, skb->data, len, DMA_TO_DEVICE);     ...     dma_unmap_len_set(tx_buf, len, len);  However, 'len' was initialized earlier to skb_headlen(skb) (e.g. 42 bytes) and is left unadjusted after padding. Consequently, dma_map_single() and dma_unmap_len_set() map and track only 42 bytes.  Later, the hardware TX buffer descriptor is programmed with the padded length:      txbd->tx_bd_len_flags_type =         cpu_to_le32(((len + pad) << TX_BD_LEN_SHIFT) | flags |                     TX_BD_FLAGS_PACKET_END);  The NIC DMA engine is thus instructed to read 52 bytes from a region where only 42 bytes were DMA-mapped. If skb->data ends near the boundary of a 4KB page (within 'pad' bytes of the next page), the hardware DMA read overruns into the unmapped adjacent page, triggering an IOMMU fault.  This issue was exposed after commit 447cbe95ebb9 (\"vlan: fix skb_under_panic and races when toggling HW VLAN offload\") because reserving extra VLAN headroom rounded LL_RESERVED_SPACE from 48 up to 64 bytes, shifting skb->data offsets and potentially causing small frames to land right against page boundaries.  Fix this by using skb_put_padto(skb, BNXT_MIN_PKT_SIZE) in bnxt_start_xmit(), before skb_shinfo(skb)->nr_frags is sampled, because padding might linearize the skb. This ensures skb->len and skb_headlen(skb) reflect the padded size so that dma_map_single() maps the full buffer and the descriptor length is consistent. This also removes the temporary 'pad' variable and masking logic.  The padding is done after the SW USO branch, otherwise bnxt_sw_udp_gso_xmit() would account the padding as UDP payload and send it in extra segments.  Note that SW USO segments are still not padded: with IPv4, a segment carrying less than 10 bytes of UDP payload (small gso_size, or a short last segment) is sent as a frame shorter than BNXT_MIN_PKT_SIZE. This is a separate issue, left for a followup patch.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98696",
                        "url": "https://ubuntu.com/security/CVE-2026-98696",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  USB: serial: fix driver deregistration order  USB serial driver modules register one driver for the USB bus and one or more drivers for the ports on the USB serial bus.  When unloading a driver module, the USB driver must be deregistered before the USB serial bus drivers so that I/O is stopped before unbinding the ports to avoid use-after-free in completion handlers accessing port data.  Note that the \"new_id\" attributes must first be removed to prevent new ids from being added and triggering a probe of the USB driver after it has been deregistered.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98705",
                        "url": "https://ubuntu.com/security/CVE-2026-98705",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: mac80211: account proxy paths against the mesh path limit  Proxy-path churn can drive the interface path counter negative and let later mesh path additions exceed MESH_MAX_MPATHS.  mesh_path_free_rcu() decrements the interface mpaths counter for entries from both the mesh and proxy path tables, but mpp_path_add() never reserves a slot in that counter. Removing or expiring a proxy path therefore returns a slot that was never charged.  mesh_path_add() uses the same counter to enforce MESH_MAX_MPATHS, so once it falls below the number of installed paths the limit no longer holds.  Reserve the shared quota before allocating a proxy path and release it on every unsuccessful addition. Mesh and proxy paths now share one 1024-entry budget, so mpp_path_add() can return -ENOSPC at that limit.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98722",
                        "url": "https://ubuntu.com/security/CVE-2026-98722",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  mtd: block2mtd: Fix divide error when erase_size is zero  The erase size is parsed from the \"block2mtd\" module parameter and can be set to zero. add_device() then evaluates          if (size % erase_size)  with a zero divisor, which triggers a divide error:  divide error: 0000 [#1] PREEMPT SMP PTI RIP: 0010:add_device drivers/mtd/devices/block2mtd.c:296 [inline] RIP: 0010:block2mtd_setup2+0x592/0xda0 drivers/mtd/devices/block2mtd.c:459 Call Trace: block2mtd_setup+0x27/0xe0 drivers/mtd/devices/block2mtd.c:476 param_attr_store+0x214/0x310 kernel/params.c:589 module_attr_store+0x65/0x90 kernel/params.c:904 kernfs_fop_write_iter+0x3a4/0x540 fs/kernfs/file.c:345 ...  Reject a zero erase size before performing the modulo operation so the existing \"erasesize must be a divisor of device size\" error path reports the invalid argument and frees the device.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98695",
                        "url": "https://ubuntu.com/security/CVE-2026-98695",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  USB: serial: fix ioctl hangup race  The tty ioctls can race with hangup and end up calling into a tty driver for a device that is already gone or powered down.  Serialise the callbacks using the tty port mutex and add the missing checks to make sure the port has not been hung up before accessing port driver data or hardware.  This specifically avoids dereferencing a NULL-pointer if a device is disconnected during lengthy break signalling.  Note that TIOCGICOUNT and TIOCMIWAIT do not access port driver data or hardware and are therefore not affected by the race.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98694",
                        "url": "https://ubuntu.com/security/CVE-2026-98694",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  thunderbolt: Fix KASAN reported use-after-free when request is canceled  Alan reported that when doing stress testing sometimes KASAN notices use-after-free during control channel operation (stripped down keeping the relevant parts):   BUG: KASAN: slab-use-after-free in tb_cfg_request_sync+0x240/0x250 [thunderbolt]  Read of size 24 at addr ffff88811067f290 by task kworker/u40:2/1760   <TASK>   tb_cfg_request_sync+0x240/0x250 [thunderbolt]   tb_cfg_read_raw+0x367/0x510 [thunderbolt]   tb_cfg_read+0xec/0x240 [thunderbolt]   tb_port_get_link_generation+0x258/0x420 [thunderbolt]   tb_usb3_consumed_bandwidth+0x1c1/0x2c0 [thunderbolt]   tb_tunnel_consumed_bandwidth+0xfd/0x910 [thunderbolt]   tb_available_bandwidth+0x5f2/0xeb0 [thunderbolt]   tb_recalc_estimated_bandwidth+0x2a0/0x1bc0 [thunderbolt]   tb_handle_dp_bandwidth_request+0x1897/0x5e20 [thunderbolt]   process_one_work+0x675/0x1230   worker_thread+0x5e6/0xf70   kthread+0x365/0x470   ret_from_fork+0x54d/0x710   ret_from_fork_asm+0x1a/0x30   </TASK>   Allocated by task 1760:   __kmalloc_cache_noprof+0x1ee/0x550   tb_cfg_read_raw+0x1d3/0x510 [thunderbolt]   tb_cfg_read+0xec/0x240 [thunderbolt]   tb_port_get_link_generation+0x258/0x420 [thunderbolt]   tb_usb3_consumed_bandwidth+0x1c1/0x2c0 [thunderbolt]   tb_tunnel_consumed_bandwidth+0xfd/0x910 [thunderbolt]   tb_available_bandwidth+0x5f2/0xeb0 [thunderbolt]   tb_recalc_estimated_bandwidth+0x2a0/0x1bc0 [thunderbolt]   tb_handle_dp_bandwidth_request+0x1897/0x5e20 [thunderbolt]   process_one_work+0x675/0x1230   worker_thread+0x5e6/0xf70   kthread+0x365/0x470   ret_from_fork+0x54d/0x710   ret_from_fork_asm+0x1a/0x30   Freed by task 926:   kfree+0x18f/0x4a0   tb_cfg_request_put+0xb7/0xe0 [thunderbolt]   tb_cfg_request_work+0x82/0x120 [thunderbolt]   process_one_work+0x675/0x1230   worker_thread+0x5e6/0xf70   kthread+0x365/0x470   ret_from_fork+0x54d/0x710   ret_from_fork_asm+0x1a/0x30   Second to last potentially related work creation:   __queue_work+0x575/0xd00   queue_work_on+0x77/0x80   tb_cfg_request_cancel+0xc7/0x260 [thunderbolt]   tb_cfg_request_sync+0x1f6/0x250 [thunderbolt]   tb_cfg_read_raw+0x367/0x510 [thunderbolt]   tb_cfg_read+0xec/0x240 [thunderbolt]   tb_port_get_link_generation+0x258/0x420 [thunderbolt]   tb_usb3_consumed_bandwidth+0x1c1/0x2c0 [thunderbolt]   tb_tunnel_consumed_bandwidth+0xfd/0x910 [thunderbolt]   tb_available_bandwidth+0x5f2/0xeb0 [thunderbolt]   tb_recalc_estimated_bandwidth+0x2a0/0x1bc0 [thunderbolt]   tb_handle_dp_bandwidth_request+0x1897/0x5e20 [thunderbolt]   process_one_work+0x675/0x1230   worker_thread+0x5e6/0xf70   kthread+0x365/0x470   ret_from_fork+0x54d/0x710   ret_from_fork_asm+0x1a/0x30  The last stack trace is helpful because it shows that we are cancelling a request and looking at tb_cfg_request_cancel() what might happen is that tb_cfg_request_work() completes right before tb_cfg_request_cancel() starts and because of this it will call schedule_work() queueing the same work to run again. However, it is already removed from the request_queue and reference count is dropped so when tb_cfg_request_work() triggers again it will access memory that is already released.  Fix this so that we first make sure a cancelled request is not handed away from tb_cfg_request_find() or scheduled to run. Then instead of relying on the worker to clean up the request we will do it in tb_cfg_request_cancel() after the work is canceled from running. Make tb_cfg_request_dequeue() release the request only if it was actually removed from the queue.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98704",
                        "url": "https://ubuntu.com/security/CVE-2026-98704",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: mac80211: keep fallback association elements alive  Associating to a non-transmitted MBSSID profile reads freed memory while determining the operating channel and applying HT capabilities.  When an association response omits WMM, HT, or VHT information, ieee80211_assoc_config_link() parses the cached BSS IEs and copies the missing element pointers out of that fallback parse. For a non-transmitted MBSSID profile those pointers refer to merged-profile storage owned by the parse object, and the fallback block frees that object at its end. The copied pointers are used afterwards to determine the operating channel, configure bandwidth, and apply HT capabilities.  Keep the fallback parse result alive until association setup finishes.  [reorder variable declaration]",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98707",
                        "url": "https://ubuntu.com/security/CVE-2026-98707",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: mac80211: shut down RX BA session timer on teardown  Tearing down an RX BA session can leave the session timer queued on a freed tid_rx. Later timer-wheel processing and the timer callback itself then run against freed memory.  An RX BAR handler can dereference tid_rx under RCU before teardown unpublishes it and stay in its read-side critical section while teardown deletes the session timer. The stale handler can then rearm the timer after timer_delete_sync() returns and before the RCU callback frees tid_rx.  Use timer_shutdown_sync() so rearm attempts become ineffective once teardown starts. Keep reorder_timer unchanged: teardown marks the session removed under reorder_lock and its release path checks that state before rearming. session_timer has no equivalent guard because ieee80211_rx_h_ctrl() rearms it before taking reorder_lock.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98749",
                        "url": "https://ubuntu.com/security/CVE-2026-98749",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  tty: serial: max3100: shut down timer before freeing port  max3100_shutdown() stops the polling timer but returns early during system suspend. If the SPI device is unbound before resume, the serial core does not call max3100_shutdown() again, so max3100_remove() frees the port while the timer remains armed. max3100_timeout() may then access the freed port and re-arm the timer.  Add final timer teardown to max3100_remove() and use timer_shutdown_sync() to prevent a racing callback from re-arming it. Also free the IRQ and destroy the workqueue there before freeing the port. Keep timer_delete_sync() in max3100_shutdown() so that a subsequent open() can re-arm the timer.  The workqueue is created before request_irq() and destroyed on both request_irq() failure and normal shutdown. Its presence at remove thus identifies the IRQ left registered when suspend bypasses shutdown.  Free the IRQ before destroying the workqueue, in both max3100_shutdown() and max3100_remove(), and cancel the pending work in between. free_irq() waits for a running interrupt handler to finish and no new handler can start afterwards, so a racing handler cannot queue work on a workqueue that is being destroyed; the force_end_work check in max3100_dowork() only narrows that window, as a handler delayed between the check and queue_work() could still run after the teardown has cleared the workqueue pointer. Cancelling the work also keeps destroy_workqueue() from waiting on a queued work item in case remove() ever runs while the freezable workqueue is still frozen, e.g. device removal during the resume window, before workqueues are thawed.  This issue was found by an in-house static analysis tool.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98751",
                        "url": "https://ubuntu.com/security/CVE-2026-98751",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  tty: abort break signalling on hangup  The break ioctls can race with hangup and end up calling into a tty driver for a device that is already gone or powered down.  Drivers must handle this race, but TCSBRK and TCSBRKP should still be aborted to avoid calling back into the driver after a user-controlled timeout (possibly even after the tty has been reopened).  Note that drivers should disable any break state on shutdown so just return on hangup (calling break_ctl() again is racy and will most likely fail for drivers handling the race).",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98753",
                        "url": "https://ubuntu.com/security/CVE-2026-98753",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  tty: tty_port: restore TTY_IO_ERROR on activation failure  Make sure to restore the TTY_IO_ERROR flag if activation fails to prevent I/O attempts on a port that is gone or powered down.  This specifically avoids issues like kernel panic due to unclocked accesses or NULL-pointer dereferences when accessing powered down or deregistered ports when a TTY ioctl races with hangup and open.  Note that the flag is set again in tty_port_close() but not restoring it on activation failure leaves a window where drivers fail to handle the ioctl-hangup race.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98762",
                        "url": "https://ubuntu.com/security/CVE-2026-98762",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  USB: dwc2: shut down wakeup timer before freeing HCD state  dwc2_wakeup_detected() accesses the DWC2 host state and can rearm the wakeup timer.  dwc2_hcd_free() currently deletes the timer only after freeing host-owned state, and timer_delete() does not synchronize a callback or prevent it from being queued again.  Stop and shut down the timer in dwc2_hcd_release(), before the HCD resources are freed.  This covers both the HCD initialization error path and normal HCD removal.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98784",
                        "url": "https://ubuntu.com/security/CVE-2026-98784",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  drm/amdgpu/gfx6: fix firmware leak on teardown  The firmware requested in gfx_v6_0_init_microcode() is not released when the GFX block is torn down, leaking the firmware resources.  Add gfx_v6_0_free_microcode() and call it from gfx_v6_0_sw_fini() to release the PFP, ME, CE and RLC firmware.  (cherry picked from commit 386e81346f95ab0be5a82c5535de932e7a456924)",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98779",
                        "url": "https://ubuntu.com/security/CVE-2026-98779",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  drm/amdgpu: fix ACP MFD device leak on init failure  acp_hw_init() registers ACP child devices with mfd_add_devices() before attaching them to the ACP power domain and initializing the hardware.  If attaching a child to the power domain fails, or if the ACP reset or clock enable operation times out, the failure path frees only the source cell, resource, and platform-data allocations. The child platform devices already registered by mfd_add_devices() remain registered and are never released.  Remove the children from the power domain and unregister the MFD devices on failures that occur after mfd_add_devices() succeeds. Keep mfd_add_devices() failures on the existing cleanup path since the MFD core already rolls back partially registered children itself.  The issue was identified by a static analysis tool I developed and confirmed by manual review.  (cherry picked from commit 63da68d6a2279ec945581c990c5a59a5ae8b5560)",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98742",
                        "url": "https://ubuntu.com/security/CVE-2026-98742",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ALSA: seq: Serialize compat port-info ioctls  The native sequencer ioctl path serializes handler calls with client->ioctl_mutex, but the translated port-info compat path invokes the same handlers through snd_seq_kernel_client_ctl() without taking that mutex.  This lets concurrent compat CREATE_PORT requests pass the port-count check before any request reaches the serialized insertion. The computed integer port index can then exceed the address field range and wrap to an existing index. Subsequent subscriber teardown can resolve the duplicate address to the wrong port and access a freed subscriber.  Take ioctl_mutex while dispatching converted port-info requests, matching the native ioctl path. All translated port-info commands share this helper, so their accesses to the client port state are serialized as well.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98655",
                        "url": "https://ubuntu.com/security/CVE-2026-98655",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  perf: Require kernel access for text poke events  Perf events with exclude_kernel=1 can be opened without kernel perf access. However, exclude_kernel does not suppress text-poke sideband records. Every PERF_RECORD_TEXT_POKE is marked PERF_RECORD_MISC_KERNEL and contains a raw kernel instruction address.  An unprivileged task can therefore open and mmap a task-local software event with text_poke=1. Both opening a count-only tracepoint event and configuring UDP GRO for ESP-in-UDP cause updates to inline static calls; the observer receives the relocated addresses of the modified instructions. For a known kernel image, any such address reveals the runtime kernel text base despite KASLR.  Call perf_allow_kernel() whenever attr.text_poke is set, regardless of exclude_kernel. Events that neither monitor kernel execution nor request text-poke records retain their existing permissions.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98750",
                        "url": "https://ubuntu.com/security/CVE-2026-98750",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  tty: fix saved termios reset race  Resetting saved termios state on device registration is needed where a minor number can be reused for an entirely different device and where the old settings may prevent the port from even being opened (e.g. when CLOCAL is not set).  Not all TTY drivers guarantee that the minor number is no longer in use when registering devices however, something which can lead to a use-after-free when closing a TTY (and saving its termios) races with re-registration.  Add a new TTY_DRIVER_RESET_SAVED_TERMIOS flag to request that any saved termios state is reset on registration and only set it for drivers that make sure that the minor number is no longer in use.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-89638",
                        "url": "https://ubuntu.com/security/CVE-2026-89638",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  smb: client: clear setuid/setgid bit on write with cifsacl/modefromsid/posix extensions  When a file has the setuid or setgid bit set and is written to, the VFS strips those bits and issues a setattr with ATTR_KILL_SUID/ATTR_KILL_SGID together with an ATTR_MODE carrying the already-cleared mode.  Both cifs_setattr_unix() and cifs_setattr_nounix() unconditionally dropped ATTR_MODE in that case:  \t/* skip mode change if it's just for clearing setuid/setgid */ \tif (attrs->ia_valid & (ATTR_KILL_SUID|ATTR_KILL_SGID)) \t\tattrs->ia_valid &= ~ATTR_MODE;  This is fine for the default mount, where the mode is only emulated via the DOS read-only attribute and cannot represent the setuid/setgid bits anyway.  However, with the \"cifsacl\" or \"modefromsid\" mount options the mode is stored on the server through an ACL (id_mode_to_cifs_acl()), with the SMB3.1.1 POSIX extensions the mode is sent to the server directly, and with the SMB1 Unix extensions (cifs_setattr_unix) the mode is sent via CIFSSMBUnixSetPathInfo().  In all those cases dropping ATTR_MODE means the cleared mode is never pushed to the server, so the setuid/setgid bit survives the write.  This is a security issue: on local filesystems the setuid bit is stripped when a file is written, but over these cifs.ko mounts the bit persists on the server, potentially allowing an unexpected privilege escalation on subsequent execution.  Fix this in two places:    1. cifs_setattr_nounix(): only take the \"skip mode change\" shortcut      when the mode is emulated via the DOS read-only attribute (i.e.      neither cifsacl/modefromsid nor the SMB3.1.1 POSIX extensions are      in effect), so that the cleared mode is propagated to the server      in the ACL / POSIX cases.    2. cifs_setattr_unix(): this function is only called when Unix      extensions are in effect, so the mode is always stored on the      server.  Remove the shortcut entirely so that the cleared mode is      always pushed.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-09-11 20:19:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98375",
                        "url": "https://ubuntu.com/security/CVE-2026-98375",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  xen/netfront: drop RX packets with a short Ethernet header  handle_incoming_queue() pulls pull_to bytes into the head before calling eth_type_trans().  pull_to is the length of the first RX slot, capped at RX_COPY_THRESHOLD, and that length comes from the backend. Nothing checks it against ETH_HLEN.  If the first slot is shorter than ETH_HLEN and more slots follow, the head ends up shorter than an Ethernet header while skb->len is longer, and eth_type_trans() BUG()s in __skb_pull().  If the whole packet is shorter than ETH_HLEN, eth_type_trans() reads the header past the end of the data instead.  Pull at least ETH_HLEN, and drop the packet if that fails, which also drops packets too short to hold an Ethernet header.  This also checks the return value of the pull, which was ignored.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-09 08:16:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-89738",
                        "url": "https://ubuntu.com/security/CVE-2026-89738",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  usb: gadget: at91_udc: drain polled-VBUS timer/work before udc is freed  In polled-VBUS mode (board.vbus_pin && board.vbus_polled), probe arms a self-restarting cycle: at91_vbus_timer() schedules vbus_timer_work, and at91_vbus_timer_work() calls at91_vbus_update() and re-arms the timer via mod_timer(). Both recover the same udc through container_of and dereference it on every iteration.  Neither teardown path cancels this cycle. udc is devm-allocated, so it is freed after at91udc_remove() returns, and is likewise freed when probe fails and devres runs. A timer callback or work item that is pending or running at either point dereferences the freed udc.  Add at91_udc_shutdown_vbus_timer() and call it from at91udc_remove() and from the usb_add_gadget_udc() failure path in probe; the remaining probe error paths fail before the timer is armed. timer_shutdown_sync() waits for a running callback and clears timer->function, which makes the work handler's mod_timer() a permanent no-op; cancel_work_sync() then drains any pending or running work whose re-arm attempt now does nothing. The timer must be shut down first, since cancelling the work alone would let the timer re-queue it. The guard mirrors probe: in IRQ mode the timer and work_struct are never initialized.  This does not require a fault; a normal driver unbind can interleave with an already queued work item.  This issue was found by an in-house static analysis tool.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-09-11 20:20:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-89740",
                        "url": "https://ubuntu.com/security/CVE-2026-89740",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  serial: imx: serialize imx_uart_ports[] lifetime  imx_uart_probe() publishes its devm-allocated port in imx_uart_ports[] before uart_add_one_port() because console setup uses the table. The entry is not cleared when adding the port fails or after removal, leaving a dangling pointer.  A sibling probe can register the shared console through that stale entry. This was reproduced under KASAN on QEMU mcimx6ul-evk by unbinding a sibling UART, unbinding the console UART and rebinding the sibling.  Keep the entry valid through uart_remove_one_port(), then clear it. Protect port addition and removal together with their table updates so sibling operations cannot interleave. Reject an occupied slot rather than clobbering an active port during a duplicate-line probe.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-09-11 20:20:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-74341",
                        "url": "https://ubuntu.com/security/CVE-2026-74341",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: wcn36xx: fix heap overflow from oversized firmware HAL response  The firmware response dispatcher copies all synchronous HAL responses into the 4096-byte hal_buf without validating the response length. A response exceeding WCN36XX_HAL_BUF_SIZE causes a heap buffer overflow with firmware-controlled content.  Add a bounds check on the response length.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-08-15 06:22:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-74406",
                        "url": "https://ubuntu.com/security/CVE-2026-74406",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  vxlan: Fix potential null-ptr-deref in vxlan_gro_prepare_receive().  udp_tunnel_sock_release() could set sk->sk_user_data to NULL while vxlan_gro_prepare_receive() is running.  Let's check if rcu_dereference_sk_user_data() is NULL after skb_gro_remcsum_init().",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-08-15 06:22:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-46265",
                        "url": "https://ubuntu.com/security/CVE-2026-46265",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  RDMA/hns: Fix WQ_MEM_RECLAIM warning  When sunrpc is used, if a reset triggered, our wq may lead the following trace:  workqueue: WQ_MEM_RECLAIM xprtiod:xprt_rdma_connect_worker [rpcrdma] is flushing !WQ_MEM_RECLAIM hns_roce_irq_workq:flush_work_handle [hns_roce_hw_v2] WARNING: CPU: 0 PID: 8250 at kernel/workqueue.c:2644 check_flush_dependency+0xe0/0x144 Call trace:   check_flush_dependency+0xe0/0x144   start_flush_work.constprop.0+0x1d0/0x2f0   __flush_work.isra.0+0x40/0xb0   flush_work+0x14/0x30   hns_roce_v2_destroy_qp+0xac/0x1e0 [hns_roce_hw_v2]   ib_destroy_qp_user+0x9c/0x2b4   rdma_destroy_qp+0x34/0xb0   rpcrdma_ep_destroy+0x28/0xcc [rpcrdma]   rpcrdma_ep_put+0x74/0xb4 [rpcrdma]   rpcrdma_xprt_disconnect+0x1d8/0x260 [rpcrdma]   xprt_rdma_connect_worker+0xc0/0x120 [rpcrdma]   process_one_work+0x1cc/0x4d0   worker_thread+0x154/0x414   kthread+0x104/0x144   ret_from_fork+0x10/0x18  Since QP destruction frees memory, this wq should have the WQ_MEM_RECLAIM.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-06-03 18:16:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98681",
                        "url": "https://ubuntu.com/security/CVE-2026-98681",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  smb: client: split cifsFileInfo bitfields to avoid shared-byte RMW races  The invalidHandle, swapfile, oplock_break_cancelled, offload, and status_file_deleted fields are stored in the same bitfield byte in struct cifsFileInfo, but are updated in different code paths that may run simultaneously, and are protected by different locks.  Since bitfield assignments generate byte-level read-modify-write operations, a modification to one flag can overwrite a concurrent modification to another flag.  To avoid these races, convert these flags from a bitfield to separate bool fields.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-89539",
                        "url": "https://ubuntu.com/security/CVE-2026-89539",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  SUNRPC: reject duplicate CREDS_VALUE options  gssx_dec_option_array() walks the wire-supplied option array and, for every entry whose name matches CREDS_VALUE, calls gssx_dec_linux_creds() on the same struct svc_cred. That helper unconditionally installs a fresh groups_alloc() result into creds->cr_group_info without releasing whatever pointer was already there:      for (i = 0; i < count; i++) {         ... decode name ...         if (length == sizeof(CREDS_VALUE) &&             memcmp(p, CREDS_VALUE, sizeof(CREDS_VALUE)) == 0) {             err = gssx_dec_linux_creds(xdr, creds);             ...         }     }  A reply that carries two CREDS_VALUE entries therefore overwrites cr_group_info on the second iteration and orphans the group_info allocated by the first call. The earlier free_creds path only releases the last cr_group_info via free_svc_cred(), so the first allocation's refcount stays at one and its kvmalloc-backed storage is leaked. No in-tree caller of gssp_accept_sec_context_upcall() expects more than one CREDS_VALUE per reply.  Fix by tracking whether a CREDS_VALUE option has already been decoded and returning -EINVAL on any subsequent match, so the free_creds path releases the single group_info that was installed.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-09-11 20:19:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-93179",
                        "url": "https://ubuntu.com/security/CVE-2026-93179",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  drm/amd/powerplay: fix VoltageObjectInfo zero-stride loop and OOB read  Reject voltage objects whose usSize is smaller than the header or would advance the cursor past the table end, preventing an infinite loop or heap OOB read when the VBIOS supplies a malformed VoltageObjectInfo table.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-09-17 17:18:00 UTC"
                    },
                    {
                        "cve": "CVE-2023-52561",
                        "url": "https://ubuntu.com/security/CVE-2023-52561",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  arm64: dts: qcom: sdm845-db845c: Mark cont splash memory region as reserved  Adding a reserved memory region for the framebuffer memory (the splash memory region set up by the bootloader).  It fixes a kernel panic (arm-smmu: Unhandled context fault at this particular memory region) reported on DB845c running v5.10.y.",
                        "cve_priority": "low",
                        "cve_public_date": "2024-03-02 22:15:00 UTC"
                    },
                    {
                        "cve": "CVE-2023-53651",
                        "url": "https://ubuntu.com/security/CVE-2023-53651",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  Input: exc3000 - properly stop timer on shutdown  We need to stop the timer on driver unbind or probe failures, otherwise we get UAF/Oops.",
                        "cve_priority": "low",
                        "cve_public_date": "2025-10-07 16:15:00 UTC"
                    },
                    {
                        "cve": "CVE-2023-53733",
                        "url": "https://ubuntu.com/security/CVE-2023-53733",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net: sched: cls_u32: Undo tcf_bind_filter if u32_replace_hw_knode  When u32_replace_hw_knode fails, we need to undo the tcf_bind_filter operation done at u32_set_parms.",
                        "cve_priority": "medium",
                        "cve_public_date": "2025-10-24 12:15:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98657",
                        "url": "https://ubuntu.com/security/CVE-2026-98657",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  iio: proximity: pulsedlight: fix iio_device left registered on PM setup failure  pm_runtime_set_active() failing in probe() jumps to error_unreg_buffer, which only calls iio_triggered_buffer_cleanup() -- it does not undo the iio_device_register() that already succeeded a few lines above. probe() then returns the error, the devm-managed indio_dev is freed, but the iio core still has it registered: the sysfs/chardev nodes stay live and point at freed memory.  Add an error_unreg_dev label that unregisters the iio device before falling through to the existing buffer cleanup, mirroring the teardown order already used in lidar_remove().",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98662",
                        "url": "https://ubuntu.com/security/CVE-2026-98662",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  iio: light: gp2ap020a00f: drain irq_work after free_irq  The threaded IRQ handler queues data->work through irq_work_queue() so the trigger is polled from a per-CPU context.  free_irq() does not flush an irq_work the handler already queued, so after gp2ap020a00f_remove() returns that work may still run and call iio_trigger_poll() on data->trig, which the devm cleanup has already freed, causing a use-after-free.  Add irq_work_sync(&data->work) after free_irq() in remove() and in the probe error path, mirroring commit 78601726d4a5 (\"iio: trigger: sysfs: fix use-after-free on remove\").  Found by an in-house static analysis tool, confirmed by manual review.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98663",
                        "url": "https://ubuntu.com/security/CVE-2026-98663",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  iio: imu: adis16480: fix unprotected debugfs reads  The firmware_revision and firmware_date file operations are open coded and never call debugfs_file_get(), which debugfs_create_file_unsafe() requires. debugfs_remove_recursive() therefore does not wait for a read in progress, and unbind frees the iio_dev underneath it.  Use debugfs_create_file() instead.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98664",
                        "url": "https://ubuntu.com/security/CVE-2026-98664",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  iio: imu: adis16400: fix unprotected debugfs reads  adis16400_serial_number_fops is open coded and never calls debugfs_file_get(), so debugfs_remove_recursive() does not wait for a read in progress and unbind frees the iio_dev underneath it.  Commit ae1d37a9bb4b (\"iio: imu: adis16400: use DEFINE_DEBUGFS_ATTRIBUTE instead of DEFINE_SIMPLE_ATTRIBUTE\") converted product_id and flash_count to DEFINE_DEBUGFS_ATTRIBUTE, which protects itself, but moved all three files to debugfs_create_file_unsafe().  serial_number prints three registers as \"%.4x-%.4x-%.4x\" and DEFINE_DEBUGFS_ATTRIBUTE() formats a single u64, so it cannot be converted without changing what the file returns. adis16475 and adis16550 already use debugfs_create_file() for their open coded files. Use it here too.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98666",
                        "url": "https://ubuntu.com/security/CVE-2026-98666",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  iio: gyro: adis16136: fix unprotected debugfs reads  The serial_number file operations are open coded and never call debugfs_file_get(), which debugfs_create_file_unsafe() requires. debugfs_remove_recursive() therefore does not wait for a read in progress, and unbind frees the iio_dev underneath it.  Use debugfs_create_file() instead.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98671",
                        "url": "https://ubuntu.com/security/CVE-2026-98671",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  iio: adc: sun4i-gpadc-iio: clean up on thermal zone registration failure  If devm_thermal_of_zone_register() fails, probe returns without unregistering the IIO map array or disabling runtime PM.  Jump to err_map to release them.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98679",
                        "url": "https://ubuntu.com/security/CVE-2026-98679",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  iio: accel: kxcjk-1013: reject duplicate event disable  The IIO core does not filter duplicate writes to the event enable attribute. kxcjk1013_write_event_config() already ignores repeated enable requests, but a repeated disable request still calls kxcjk1013_set_power_state(data, false), dropping a runtime PM reference that was not acquired for this request. This can underflow the runtime PM usage count and trigger a \"Runtime PM usage count underflow\" warning.  Return early when the requested state already matches ev_enable_state.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98687",
                        "url": "https://ubuntu.com/security/CVE-2026-98687",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  thunderbolt: Reject oversized XDomain properties responses  tb_xdp_properties_request() allocates room for 45 data dwords in its 252-byte response buffer.  The XDomain length field is six bits wide, however, and a malicious peer can set it to 63.  After the fixed response fields are subtracted, the driver treats this as 48 data dwords.  Commit 322e93448d90 (\"thunderbolt: Clamp XDomain response data copy to allocation size\") only bounds the copy against data_len.  If data_len is at least 48, memcpy() reads 192 bytes from the 180-byte res->data array, causing a 12-byte heap out-of-bounds read.  Commit 4db2bd2ed478 (\"thunderbolt: Limit XDomain response copy to actual frame size\") limits the earlier copy but does not constrain this header-derived length.  Reject response data lengths that exceed the allocated source buffer before copying them into the assembled property block.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98697",
                        "url": "https://ubuntu.com/security/CVE-2026-98697",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  USB: serial: fix dynamic id driver deregistration race  Only free the dynamic ids after having deregistered the driver and removed the \"new_id\" attribute to avoid leaking any id added by a racing write to the attribute.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98698",
                        "url": "https://ubuntu.com/security/CVE-2026-98698",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: mac80211: handle empty FILS association request payload  fils_encrypt_assoc_req() accepts a (Re)Association Request frame whose last element is the FILS Session element.  crypt_len is then zero and aes_siv_encrypt() is called with an empty plaintext.  kmemdup() returns ZERO_SIZE_PTR for a zero-length allocation, so the unconditional sg_init_one() puts an invalid page into the scatterlist. With CONFIG_DEBUG_SG this triggers a kernel BUG in sg_set_buf(); without the debug check the bogus page is handed to the crypto backend.  AES-SIV is defined for empty plaintext and the S2V result is then the complete output, so handle this case before the CTR step, which has nothing to encrypt.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98701",
                        "url": "https://ubuntu.com/security/CVE-2026-98701",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: mac80211: release mesh path quota on failed additions  Repeated failed or duplicate mesh path additions can exhaust MESH_MAX_MPATHS while the path table holds fewer paths, which stops new paths to reachable destinations from being created.  mesh_path_add() reserves a slot before allocating and inserting a path. If allocation fails, the function returns without releasing the slot. If the rhashtable insertion reports an error or an existing destination, the function discards its candidate but retains the reservation. No new path is installed in any of these cases.  Release the reservation whenever the candidate is not installed.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98703",
                        "url": "https://ubuntu.com/security/CVE-2026-98703",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: mac80211: minstrel_ht: validate fixed rate index  The fixed_rate_idx debugfs file is a plain u32 attribute, so any value can be written to it.  minstrel_ht_update_stats() then copies the value into mi->max_tp_rate[] and mi->max_prob_rate, and minstrel_ht_set_rate() uses MI_RATE_GROUP()/MI_RATE_IDX() to index minstrel_mcs_groups[] (42 entries) and mi->groups[].rates[] (10 entries) with it.  Writing e.g. 65535 selects group 4095 and rate index 15, far outside both arrays.  The out-of-bounds entries are dereferenced and updated as struct minstrel_rate_stats (retry counts, etc.), so the invalid index corrupts adjacent kernel memory.  With CONFIG_UBSAN_BOUNDS the access is reported as an array-index-out-of-bounds in minstrel_ht_set_rate().  Only a valid group/rate pair, or U32_MAX to disable fixed rate processing, can be used safely, so reject any other value when the debugfs file is written.  The file is only reachable through a root-only debugfs mount, so this is not a privilege boundary.  The out-of-bounds access is still a bug that must not be reachable through a writable debugfs attribute.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98706",
                        "url": "https://ubuntu.com/security/CVE-2026-98706",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: mac80211: drain PS delivery work during station teardown  Removing an AP or mesh station can notify the driver and wake TXQs after the station has already been removed from the driver, and can update num_sta_ps and the power-save queues after station cleanup has purged them.  sta_deliver_ps_frames() tests sta->dead only before it starts delivery. A worker that passes that test can be delayed while teardown sets sta->dead and removes the station from the driver; when it resumes it still runs the full delivery.  The existing cancel_work_sync() sits near the end of __cleanup_single_sta(), after the final driver state transition and after PS accounting and queue purging, so it drains the worker only once the state it has to protect has already changed. Before commit d34ba2168a3c (\"mac80211: don't delay station destruction\") cleanup was deferred through the same ordered workqueue as the delivery work, which kept the two ordered.  Cancel the work after setting sta->dead and before moving the driver state, and move the existing cancellation to the start of __cleanup_single_sta(). The first drain closes the driver-lifetime window; driver callbacks during the remaining state transitions can still queue drv_deliver_wk through ieee80211_sta_block_awake(), so retain the second drain at the start of __cleanup_single_sta(). That drain also covers insertion failures, which reach cleanup without setting sta->dead.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98710",
                        "url": "https://ubuntu.com/security/CVE-2026-98710",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: iwlegacy: 3945: free EEPROM data on remove  il3945_pci_probe() calls il_eeprom_init(), which allocates memory for the EEPROM data. The probe failure paths release this allocation with il_eeprom_free(), but the remove path does not free it after a successful probe.  As a result, the EEPROM data is leaked when the PCI device is removed.  Free the EEPROM data in il3945_pci_remove() before releasing the mac80211 hardware structure.  This issue was found by manual code inspection.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98711",
                        "url": "https://ubuntu.com/security/CVE-2026-98711",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: cw1200: fix TX padding OOB read leaking heap data to device  The TX path rounds the transfer size up to the bus alignment (align_size(), up to 511 bytes for SDIO, 1 byte for SPI) but sends the padded length straight from the frame buffer, which has no room reserved for the padding.  cw1200_data_write() therefore reads past the end of the frame and the bus transfer carries those bytes to the device.  A bogus device can collect up to 511 bytes of kernel heap data per TX frame.  The RX path does not have this problem: it allocates the skb with the aligned length (alloc_len) before reading.  Compute the exact padding with the bus align_size() callback, make sure queued TX frames have tailroom for it, and zero the padding bytes before the transfer so nothing past the frame is exposed.  This is not expected to change driver behavior on most cases: frame contents and transfer sizes are unchanged, only the content of the padding bytes (previously undefined stale memory, now zero), which the device never reads since the WSM header carries the real frame length.  The skb expansion can only fail under memory exhaustion, in which case the frame is dropped like on the existing error paths of cw1200_tx().  Discovered by Atuin - Automated Vulnerability Discovery Engine.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98721",
                        "url": "https://ubuntu.com/security/CVE-2026-98721",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  mtd: rawnand: cadence: Initialize IRQ state before requesting IRQ  The Cadence NAND interrupt handler uses both the IRQ lock and completion object. Registering the IRQ before initializing them leaves a window in which a pending interrupt can access uninitialized synchronization state.  Initialize them before registering the handler.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98726",
                        "url": "https://ubuntu.com/security/CVE-2026-98726",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  nvme-multipath: fix underflow in ANA log bounds checks  The number of ANA groups advertised through Identify Controller sizes the ANA log buffer. The ANA log header and group descriptors independently supply the number of groups and namespace IDs to parse.  Both bounds checks subtract an untrusted object size from ana_log_size before comparing the current offset. If the object is larger than the buffer, the size_t subtraction underflows and lets the parser read beyond ana_log_buf.  Check the current offset before the first subtraction and compare each object size with the remaining buffer instead. This rejects inconsistent ANA data before dereferencing a truncated group descriptor or walking an oversized namespace ID array.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98856",
                        "url": "https://ubuntu.com/security/CVE-2026-98856",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  kprobes: Skip disarmed probes when checking optkprobe overlap  On x86, an optkprobe at A replaces five bytes with a jump. If a disabled probe B is at A+2, get_optimized_kprobe() stops at B when arming a new probe C at A+4. It leaves A optimized:                A    A+1  A+2  A+3  A+4   A's jump  | e9 | d0 | d1 | d2 | d3 |   after C   | e9 | d0 | d1 | d2 | cc |  The INT3 for C overwrites the last byte of A's jump displacement, so execution can jump to the wrong address. B can have prepared optinsns while disarmed, but has no jump to unoptimize.  Continue past disarmed and unprepared probes to find the active optimized probe before arming a probe in its jump.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98857",
                        "url": "https://ubuntu.com/security/CVE-2026-98857",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ipvs: bound LBLCR and LBLC cache growth  ip_vs_lblcr_new() and ip_vs_lblc_new() create cache entries for every previously unseen destination address. The table max_size only tells the periodic collector to reclaim entries after the cache has already exceeded the limit. It does not reclaim entries that the attacker continues to use.  Reject new cache entries once either table reaches max_size * 3 / 2. The extra headroom lets the periodic collector catch up while the existing scheduler fallback continues to use the selected destination when cache creation fails. New traffic therefore stays serviceable without growing the tables further.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98732",
                        "url": "https://ubuntu.com/security/CVE-2026-98732",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  Bluetooth: btintel: fix buffer over-read in btintel_hw_error()  The \"Exception info %s\" print uses skb->data + 1, but the 12-byte payload is not guaranteed to be NUL-terminated and can be read past its end.  Bound the print with \"%.*s\" and skb->len - 1.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98735",
                        "url": "https://ubuntu.com/security/CVE-2026-98735",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  Bluetooth: hci_core: Serialize ACL scheduling with channel deletion  hci_chan_sent() selects a channel under RCU but drops the read lock before accessing chan->conn and returning the channel. The ACL and LE schedulers then use its packet queue and update its transmit counters without any protection against channel deletion.  After TX selects a channel and releases RCU, a disconnect command timeout on the separate request workqueue can run hci_conn_failed() and l2cap_conn_del(). hci_chan_del() can then unlink the channel, complete synchronize_rcu(), purge its queue and free it before TX resumes. This causes use-after-free both in hci_chan_sent() and in its callers.  KASAN reported:    BUG: KASAN: slab-use-after-free in hci_chan_sent+0x892/0x9b0   Workqueue: hci0 hci_tx_work   Call Trace:    hci_chan_sent+0x892/0x9b0    hci_tx_work+0x5e6/0xb70   Allocated by task 91:    hci_chan_create+0xe3/0x350    l2cap_conn_add.part.0+0x12/0xa30    l2cap_chan_connect+0x110d/0x1b60    l2cap_sock_connect+0x310/0x530   Freed by task 99:    hci_chan_del+0x11f/0x170    l2cap_conn_del+0x4f1/0x800    l2cap_connect_cfm+0x88c/0xd30    hci_conn_failed+0x150/0x250    hci_abort_conn_sync+0x3e3/0x800    hci_cmd_sync_run+0x7e/0xc0    hci_abort_conn+0x105/0x1f0    disconnect_sync+0x157/0x290    hci_cmd_sync_work+0x13c/0x290  Hold the existing device mutex across channel selection and transmission in both schedulers to serialize them with channel teardown. Keep timeout handling outside the critical sections because hci_link_tx_to() acquires the same mutex. This also permits the transmit path to sleep, unlike extending the RCU read-side critical section across packet submission.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98739",
                        "url": "https://ubuntu.com/security/CVE-2026-98739",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  Bluetooth: RFCOMM: Fix initial port reference race  For RFCOMM_RELEASE_ONHUP devices, rfcomm_tty_install() and __rfcomm_release_dev() both use RFCOMM_TTY_OWNED to decide who drops the initial tty_port reference. The release path tests the bit separately from the install path setting it, so both can drop that reference.  The synchronous hangup does not prevent this race: port->tty is not assigned until tty_port_open(), after installation. The following interleaving is possible:    1. Install and release each obtain a reference with rfcomm_dev_get().   2. Release observes RFCOMM_TTY_OWNED clear.   3. Install sets RFCOMM_TTY_OWNED and drops the initial reference.   4. Release drops the same initial reference again.   5. TTY cleanup drops its reference and frees the device.   6. Release performs its final tty_port_put() on the freed port.  KASAN reported:    BUG: KASAN: slab-use-after-free in tty_port_put+0x22/0x190   Write of size 4 at addr ffff8881001d3d5c by task poc/92    Call Trace:    tty_port_put+0x22/0x190    rfcomm_dev_ioctl+0x1d4/0x1930    sock_do_ioctl+0x110/0x260    sock_ioctl+0x380/0x590    __x64_sys_ioctl+0x134/0x1c0    Allocated by task 88:    rfcomm_dev_ioctl+0x8f6/0x1930    sock_do_ioctl+0x110/0x260    sock_ioctl+0x380/0x590    __x64_sys_ioctl+0x134/0x1c0    Freed by task 65:    kfree+0x131/0x3c0    rfcomm_dev_destruct+0x23b/0x2f0    release_one_tty+0xc1/0x370    process_one_work+0x661/0x1090  Use test_and_set_bit() in both paths so that only the caller that changes RFCOMM_TTY_OWNED from clear to set drops the initial reference. Each path keeps its own lookup reference until release or TTY cleanup, preserving the existing callback ordering and error handling.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98741",
                        "url": "https://ubuntu.com/security/CVE-2026-98741",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ALSA: ua101: reject mismatched capture/playback packet sizes  detect_usb_format() cross-checks bSubframeSize, bBitResolution and tSamFreq between the capture and playback interfaces, but never relates the two endpoints' wMaxPacketSize and bNrChannels.  Each playback URB gets a buffer of ua->playback.max_packet_bytes, while the number of bytes written into it is derived from the capture stream: capture_urb_complete() computes frames from the received capture packet and capture.frame_bytes, and start_usb_playback() and playback_work() multiply that by playback.frame_bytes.  A device declaring a large capture wMaxPacketSize with few capture channels and a small playback wMaxPacketSize with many playback channels therefore memset()s and memcpy()s past the end of the playback buffer, in open() of the PCM node the driver registers during probe. usb_submit_urb() rejects the over-long iso_frame_desc[0].length with -EMSGSIZE, but only after the write.  Reject such descriptors at probe time.  Genuine UA-101/UA-1000 hardware declares proportional packet sizes and is unaffected.    BUG: KASAN: slab-out-of-bounds in start_usb_playback (sound/usb/misc/ua101.c:586)   Write of size 2048 at addr ffff8881098f3c00 by task exploit/5021   Call Trace:    __asan_memset (mm/kasan/shadow.c:84)    start_usb_playback (sound/usb/misc/ua101.c:586)    playback_pcm_open (sound/usb/misc/ua101.c:679)    snd_pcm_open_substream (sound/core/pcm_native.c:2829)    snd_pcm_open (sound/core/pcm_native.c:2865 sound/core/pcm_native.c:2932)    snd_pcm_playback_open (sound/core/pcm_native.c:2891)    snd_open (sound/core/sound.c:166)    chrdev_open (fs/char_dev.c:411)    do_dentry_open (fs/open.c:996)    vfs_open (fs/open.c:1101)    path_openat (fs/namei.c:4837 fs/namei.c:5000)    do_file_open (fs/namei.c:5029)    do_sys_openat2 (fs/open.c:1417)    __x64_sys_openat (fs/open.c:1423 fs/open.c:1439 fs/open.c:1434)    do_syscall_64 (arch/x86/entry/syscall_64.c:61 arch/x86/entry/syscall_64.c:84)    entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:121)    The buggy address belongs to the object at ffff8881098f3c00    which belongs to the cache kmalloc-192 of size 192   The buggy address is located 0 bytes inside of    allocated 168-byte region [ffff8881098f3c00, ffff8881098f3ca8)",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98940",
                        "url": "https://ubuntu.com/security/CVE-2026-98940",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ASoC: qcom: lpass-cpu: use DAI table index for playback constraints  The DAI ID is a hardware port ID and is not necessarily the index of the corresponding entry in variant->dai_driver.  When configuring a DAI with LPAIF_I2SCTL_MODE_QUAD01, the probe code currently uses dai_id to index variant->dai_driver. This is incorrect for platforms where DAI IDs are sparse. For example, the IPQ806x MI2S DAI has ID 4 while it is the only entry in the DAI driver table. If that DAI is configured for QUAD01 and probe reaches this branch, the code writes beyond that single entry via dai_driver[4] instead of updating the DAI being processed.  Use the loop index i when updating the current DAI's playback channel constraints, while retaining dai_id for indexing the hardware-port specific playback SD-line mode array.  This fixes the incorrect DAI table access for platforms where the DAI ID does not match its position in the driver table.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98748",
                        "url": "https://ubuntu.com/security/CVE-2026-98748",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  serial: 8250_bcm7271: fix use-after-free in brcmuart_remove()  brcmuart_handle_irq() starts priv->hrt to work around a receive-timeout quirk of the 8250 core when hardware flow control is enabled; the timer callback brcmuart_hrtimer_func() dereferences priv.  brcmuart_remove() cancels the hrtimer before it unregisters the port, so a receive-timeout interrupt that arrives in between re-arms the timer. After devm frees priv, the callback runs on freed memory.  Unregister the port before cancelling the hrtimer. serial8250_unregister_port() shuts the port down and frees its IRQ, so brcmuart_handle_irq() can no longer restart the timer, and the final hrtimer_cancel() drains any timer that was armed before or during the unregister.  This issue was found by an in-house static analysis tool.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98754",
                        "url": "https://ubuntu.com/security/CVE-2026-98754",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  tty: vcc: hold port lock when clearing tty pointer in vcc_cleanup  vcc_cleanup() sets port->tty to NULL without holding port->lock, racing with vcc_event() LDC callbacks that read port->tty under port->lock and then use tty->port. This can cause a use-after-free when the callback dereferences tty->port after cleanup has already destroyed and freed it.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98755",
                        "url": "https://ubuntu.com/security/CVE-2026-98755",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  tty: vcc: zero-initialize control packet in vcc_send_ctl()  The stack-allocated struct vio_vcc pkt was partially initialized, leaving the tag.stype_env field uninitialized before being sent via ldc_write(), potentially leaking kernel stack data to the LDC peer.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98756",
                        "url": "https://ubuntu.com/security/CVE-2026-98756",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  usb: cdns3: Fix NULL pointer dereference in cdns3_pci_probe  The Cadence USBSS controller is a two-function PCI device. The first probed function allocates the driver data and stores it with pci_set_drvdata(), while the second function reuses it via pci_get_drvdata() when pci_is_enabled() reports that the first function has already been probed.  When the second function is probed while the first one has been enabled but has not yet set its driver data, pci_get_drvdata() returns NULL, and the subsequent wrap->devfn assignment dereferences a NULL pointer and crashes the kernel. logs: Call trace:   cdns3_pci_probe+0xa4/0x300   local_pci_probe+0x44/0xa8   pci_call_probe+0x54/0x158   pci_device_probe+0x84/0x100   really_probe+0x184/0x3d0   __driver_probe_device+0x80/0x178   driver_probe_device+0x44/0xe8   __driver_attach+0xec/0x1f8   bus_for_each_dev+0x7c/0xe0   driver_attach+0x28/0x38   bus_add_driver+0x110/0x238   driver_register+0x64/0x128   __pci_register_driver+0x50/0x60   cdns3_pci_driver_init+0x28/0x38   do_one_initcall+0x5c/0x280   do_initcalls+0x104/0x1d8   kernel_init_freeable+0x140/0x218   kernel_init+0x28/0x1f8   ret_from_fork+0x10/0x20  Return -EPROBE_DEFER in this case so that probing is retried after the first function has completed its probe.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98757",
                        "url": "https://ubuntu.com/security/CVE-2026-98757",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  usb: cdns3: fix use-after-free in cdns3_gadget_exit()  cdns3_gadget_start() arms two works on system_freezable_wq: pending_status_wq for the deferred ep0 status stage and aligned_buf_wq for realigned request buffers. Both handlers use the cdns3_device the works are embedded in, and cdns3_pending_setup_status_handler() also calls the ep0 request completion.  cdns3_gadget_exit() does not wait for these works. It frees all endpoints and aligned buffers and drops the last reference to the gadget device, which frees priv_dev, so a work queued before the exit can run after the free.  Fix this by waiting for both works after the gadget driver is unbound and the IRQ is freed, when no new work can be queued, and before the endpoints and buffers are released.  This issue was found by an in-house static analysis tool.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98760",
                        "url": "https://ubuntu.com/security/CVE-2026-98760",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  usb: typec: tipd: fix uninitialized typec_partner_desc in tps6598x_connect()  tps6598x_connect() passes a stack-allocated typec_partner_desc to typec_register_partner() after initializing only usb_pd, accessory and identity.  typec_register_partner() copies attach and deattach from the descriptor into the partner. With those fields left unset, garbage function pointers may be stored and later invoked from typec_partner_link_device() when a USB device is linked to the port. Uninitialized pd_revision and usb_capability similarly leak stack data through partner sysfs.  Zero-initialize the descriptor so optional callbacks remain NULL and the remaining fields are zero.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98761",
                        "url": "https://ubuntu.com/security/CVE-2026-98761",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  usb: typec: tcpm: recover after failure to start the frs ams  Reset the port if the tcpm fails to start the FAST_ROLE_SWAP AMS by initiating error recovery on it.  This helps in cases where some cables (incorrectly) signal an FRS to an FRS capable port during disconnection. The TCPC autonomously starts sourcing VBUS on detecting the FRS signal. However, the VBUS sourcing is left on when the FAST_ROLE_SWAP AMS fails to start (as tcpm_sink_tx_ok is 0 as CC is open due to the cable disconnect). This is because the code sets the state to INVALID_STATE without resetting the port state.  Log snippet before changes: [  101.401960] AMS FAST_ROLE_SWAP start [  101.401971] Sink TX No Go [  101.401982] sourcing vbus [  101.401987] VBUS on [  101.402159] VBUS on [  109.257809] CC1: 0 -> 0, CC2: 5 -> 0 [state SNK_READY, polarity 1, disconnected] [  111.267442] VBUS on  After changes: [   70.541211] AMS FAST_ROLE_SWAP start [   70.541220] Sink TX No Go [   70.541228] state change SNK_READY -> ERROR_RECOVERY [rev3 NONE_AMS] [   70.541362] VBUS on [   70.541365] sourcing vbus [   70.541367] VBUS on [   70.541374] state change ERROR_RECOVERY -> PORT_RESET [rev3 NONE_AMS] [   70.541410] disable vbus discharge ret:0 [   70.543028] Setting usb_comm capable false [   70.544009] Setting voltage/current limit 0 mV 0 mA [   70.544034] polarity 0 [   70.544239] Requesting mux state 0, usb-role 0, orientation 0 [   70.555550] cc:=0 [   70.555595] pending state change PORT_RESET -> PORT_RESET_WAIT_OFF @ 100 ms [rev3 NONE_AMS] [   70.555697] VBUS off [   70.555702] VBUS VSAFE0V [   70.555762] CC1: 5 -> 0, CC2: 0 -> 0 [state PORT_RESET, polarity 0, disconnected] [   70.587794] VBUS off [   70.587799] VBUS VSAFE0V [   70.655672] state change PORT_RESET -> PORT_RESET_WAIT_OFF [delayed 100 ms] [   70.655682] state change PORT_RESET_WAIT_OFF -> SNK_UNATTACHED [rev3 NONE_AMS] [   70.655686] Start toggling [   70.656274] CC1: 0 -> 0, CC2: 0 -> 0 [state TOGGLING, polarity 0, disconnected]",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98763",
                        "url": "https://ubuntu.com/security/CVE-2026-98763",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  usb: core: clear both ep_in and ep_out for non-ep0 control endpoints  In usb_enable_endpoint(), non-zero control endpoints (where usb_endpoint_xfer_control(&ep->desc) is true) populate both dev->ep_in[epnum] and dev->ep_out[epnum] with the same struct usb_host_endpoint pointer.  However, usb_disable_endpoint() only clears either dev->ep_out[epnum] or dev->ep_in[epnum] depending on the direction bit of epaddr when reset_hardware is set, leaving the opposite direction's array slot pointing to the disabled/freed endpoint.  Clear both dev->ep_out[epnum] and dev->ep_in[epnum] when disabling a non-ep0 control endpoint with reset_hardware set, and update the function kerneldoc accordingly.  Tested in QEMU against Linux 7.3.0-rc3 using dummy_hcd and raw-gadget to enumerate a USB device with a non-zero control endpoint (bEndpointAddress 0x01, bmAttributes USB_ENDPOINT_XFER_CONTROL), verifying that both dev->ep_in[1] and dev->ep_out[1] are cleared when the interface is disabled.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98764",
                        "url": "https://ubuntu.com/security/CVE-2026-98764",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  usb: gadget: f_fs: Fix NULL pointer dereference in FUNCTIONFS_ENDPOINT_DESC  When user space sets up FunctionFS with only full-speed descriptors (e.g., flags = FUNCTIONFS_HAS_FS_DESC) and the gadget operates at a higher speed (such as USB_SPEED_HIGH or USB_SPEED_SUPER), config_ep_by_speed() detects that the function lacks descriptors for the current speed, logs a warning, and falls back to full-speed descriptors. The endpoint is then successfully enabled via usb_ep_enable(), and epfile->ep becomes valid.  However, when user space subsequently issues the FUNCTIONFS_ENDPOINT_DESC ioctl to query the endpoint descriptor, ffs_epfile_ioctl() selects the descriptor index solely based on gadget->speed:  \tswitch (epfile->ffs->gadget->speed) { \tcase USB_SPEED_SUPER: \tcase USB_SPEED_SUPER_PLUS: \t\tdesc_idx = 2; \t\tbreak; \tcase USB_SPEED_HIGH: \t\tdesc_idx = 1; \t\tbreak; \tdefault: \t\tdesc_idx = 0; \t} \tdesc = epfile->ep->descs[desc_idx]; \tmemcpy(&desc1, desc, desc->bLength);  Because user space only supplied full-speed descriptors, epfile->ep->descs[1] is NULL. Dereferencing desc->bLength triggers an immediate kernel NULL pointer dereference panic.  Fix this by falling back through lower speed descriptors if the current speed descriptor was not supplied, matching the fallback logic in config_ep_by_speed() and historical f_fs behavior. If still missing, fall back to epfile->ep->ep->desc (the active descriptor), and return -EINVAL safely if no valid descriptor is found. In addition, mark desc as const to match struct usb_ep::desc and avoid discarding qualifiers.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98765",
                        "url": "https://ubuntu.com/security/CVE-2026-98765",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  USB: gadget: dummy-hcd: Fix wait for outstanding request completions  The dummy-hcd driver emulates synchronize_irq() by waiting until its private callback_usage counter drops to 0 (with the private lock not held).  This counter is incremented whenever a gadget driver callback occurs (which requires the private lock to be dropped), but not when a request completion handler is called.  This is an oversight.  Request completion is triggered by timer interrupts (emulating device IRQs in a real UDC), and the interrupt handlers are supposed to have completed when the synchronize_irq() emulation routine returns -- they aren't supposed to be in the middle of a completion callback.  If this happens it can lead to a gadget driver's unbind routine running before all outstanding request completions have finished, maybe even allowing the gadget driver's module to be unloaded while a completion handler is still running.  Fix the oversight by incrementing the callback_usage value across request completion callbacks.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98766",
                        "url": "https://ubuntu.com/security/CVE-2026-98766",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  usb: gadget: aspeed-vhub: cancel wake work on device removal  wake_work is armed from the gadget .wakeup callback to resume suspended downstream ports, and it is never cancelled in ast_vhub_remove(), so a work item queued before or during removal can run after devm has freed vhub and its ports, a use-after-free.  Cancelling the work alone is not sufficient: usb_gadget_wakeup() takes no lock and the unbind path never clears wakeup_en, so a remote-wakeup request in flight on another CPU can re-arm the work after the cancel and before vhub is freed.  ast_vhub_del_dev() already clears d->registered under vhub->lock before unregistering the gadget. Refuse the wakeup in ast_vhub_udc_wakeup() once d->registered is clear: the check and the schedule_work() are then atomic against the unbind, so a wakeup that passed before the flag was cleared is drained by the cancel_work_sync() after the del_dev loop, and one that arrives later returns without arming. Also move INIT_WORK() to the top of ast_vhub_probe(), since the probe error path reuses ast_vhub_remove() and would otherwise cancel a never-initialized work item.  This issue was found by an in-house static analysis tool.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98769",
                        "url": "https://ubuntu.com/security/CVE-2026-98769",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  usb: gadget: f_uac1_legacy: validate bRequest index in generic_{set,get}_cmd  generic_set_cmd() and generic_get_cmd() use the low nibble of ctrl->bRequest as an index into con->data[]:      u8 cmd = (ctrl->bRequest & 0x0F);  /* 0 .. 15 */     ...     con->data[cmd] = value;            /* OOB when cmd >= 5 */  struct usb_audio_control (include/linux/usb/audio.h) declares data as a 5-element array, so indices 5 through 15 write (or read) up to 44 bytes past the end of the array on the heap.  A malicious USB host can craft a class-specific SET_CUR / GET_CUR request with an arbitrary bRequest value, triggering the out-of-bounds access from an IRQ completion handler with no further preconditions.  Add an ARRAY_SIZE() guard to both functions.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98771",
                        "url": "https://ubuntu.com/security/CVE-2026-98771",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  usb: storage: sierra_ms: reject short SWoC info transfers  sierra_get_swoc_info() requests sizeof(struct swoc_info) (60) bytes from the device via usb_control_msg(), but its callers only treat a negative return value as failure. A device that answers the vendor-specific GetSwocInfo request with a short IN transfer is therefore accepted, leaving the tail of the freshly allocated (kmalloc(), non-zeroing) swoc_info buffer uninitialized.  truinst_show() subsequently prints swocInfo->rev, swocInfo->LinuxSKU and swocInfo->LinuxVer from that buffer into the world-readable (0444) \"truinst\" sysfs attribute. An emulated/malicious USB device (VID 0x1199, PID 0x0fff) can exploit this to disclose up to 5 bytes of stale kernel heap memory (kmalloc-64) to unprivileged userspace, once per sysfs read, indefinitely. On kernels built without init_on_alloc this leaks recently freed heap contents.  Only accept the transfer when the full structure was received. sierra_ms_init() already retries failed queries, so well-behaved devices are unaffected.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98772",
                        "url": "https://ubuntu.com/security/CVE-2026-98772",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  USB: serial: fix port tear down use-after-free  Some drivers for multiport devices access port driver data from completion handlers of shared URBs submitted at attach() or first open() and stopped at disconnect() or last close(), respectively.  A simple NULL check before accessing the driver data makes sure that a port state container has at least been allocated, but a completion handler can still race with port tear down.  Reorder the disconnect handling so that ports are not deregistered (and their driver data freed) until after all ports have been hung up and the driver disconnect() callback has run so that all I/O has been stopped.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98775",
                        "url": "https://ubuntu.com/security/CVE-2026-98775",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  nitro_enclaves: fix use-after-free on SLOT_ALLOC failure  When ne_create_vm_ioctl() fails the SLOT_ALLOC request after anon_inode_getfile() has succeeded, the error path calls fput(enclave_file) and then frees ne_enclave.  In normal userspace context, fput() defers the final __fput() via task_work. ne_enclave_release() therefore runs after ne_enclave has already been freed and dereferences ne_enclave->slot_uid, causing a use-after-free: KASAN: slab-use-after-free in ne_enclave_release.  The enclave has no slot allocated and is not yet linked into the enclaves list on this error path, so ne_enclave_release() is expected to return early when slot_uid is zero. However, reading slot_uid already accesses the freed object.  Clear enclave_file->private_data before fput() on the error path. ne_enclave_release() then returns immediately when private_data is NULL, leaving the ioctl error path as the sole owner of ne_enclave. This is safe because the file has not been fd_install()'d yet.  Tested on an AWS EC2 m5.2xlarge with CONFIG_KASAN=y. Without the patch, the reproducer triggers a KASAN slab-use-after-free on every SLOT_ALLOC failure. With the patch, no KASAN report is produced and the SLOT_ALLOC error is still returned. Normal enclave creation and teardown are unaffected.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98790",
                        "url": "https://ubuntu.com/security/CVE-2026-98790",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  perf: Fix race between perf_event_exit_task() and perf_pending_task()  A race condition exists between perf_event_exit_task() and perf_pending_task() during begin_new_exec().  During begin_new_exec(), perf_event_exit_task() may be called, and the PF_EXITING flag is not set on task. So perf_sigtrap() continues to execute and triggers WARN_ON_ONCE(event->ctx->task != current).  Since both task exit and exec paths can call perf_event_exit_task() which sets ctx->task to TASK_TOMBSTONE, fix this by explicitly checking if event->ctx->task equals TASK_TOMBSTONE and dropping the redundant PF_EXITING check.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98934",
                        "url": "https://ubuntu.com/security/CVE-2026-98934",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ipv6: sr: use skb_get_hash_net() in seg6_make_flowlabel()  Since commit d58e468b1112 (\"flow_dissector: implements flow dissector BPF hook\") __skb_flow_dissect() needs a net pointer, either from skb->dev, skb->sk, or since commit 3cbf4ffba5ee (\"net: plumb network namespace into __skb_flow_dissect\") a caller provided pointer.  syzbot was able to reach seg6_make_flowlabel() with an skb having neither skb->dev nor skb->sk set: a TIPC UDP bearer sends a discovery message through an IPv4 route using seg6 encap, while net.ipv6.seg6_flowlabel is set to 1.  seg6_make_flowlabel() already has a net pointer, use skb_get_hash_net().  WARNING: net/core/flow_dissector.c:1131 at __skb_flow_dissect+0x910/0x5368 net/core/flow_dissector.c:1126, CPU#0: syz.0.17/4930 Call trace:   __skb_flow_dissect+0x910/0x5368 net/core/flow_dissector.c:1126 (P)   __skb_get_hash_net+0xe0/0x29c net/core/flow_dissector.c:1903   skb_get_hash include/linux/skbuff.h:1663 [inline]   seg6_make_flowlabel+0xcc/0x1ec net/ipv6/seg6_iptunnel.c:132   __seg6_do_srh_encap+0x320/0xbf4 net/ipv6/seg6_iptunnel.c:161   seg6_do_srh+0x4b4/0xa44 net/ipv6/seg6_iptunnel.c:431   seg6_output_core+0x164/0x688 net/ipv6/seg6_iptunnel.c:681   seg6_output+0x44/0x1ac net/ipv6/seg6_iptunnel.c:744   lwtunnel_output+0x3d0/0x664 net/core/lwtunnel.c:356   dst_output include/net/dst.h:470 [inline]   ip_local_out+0x110/0x148 net/ipv4/ip_output.c:131   iptunnel_xmit+0x50c/0xd38 net/ipv4/ip_tunnel_core.c:97   udp_tunnel_xmit_skb+0x220/0x348 net/ipv4/udp_tunnel_core.c:187   tipc_udp_xmit+0x75c/0x9c0 net/tipc/udp_media.c:202   tipc_udp_send_msg+0x214/0x374 net/tipc/udp_media.c:274   tipc_bearer_xmit_skb+0x260/0x3b0 net/tipc/bearer.c:576   tipc_enable_bearer net/tipc/bearer.c:366 [inline]   __tipc_nl_bearer_enable+0xc90/0xfb0 net/tipc/bearer.c:1048   tipc_nl_bearer_enable+0x2c/0x48 net/tipc/bearer.c:1057   genl_family_rcv_msg_doit+0x1e4/0x2d4 net/netlink/genetlink.c:1114",
                        "cve_priority": "negligible",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2022-49622",
                        "url": "https://ubuntu.com/security/CVE-2022-49622",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  netfilter: nf_tables: avoid skb access on nf_stolen  When verdict is NF_STOLEN, the skb might have been freed.  When tracing is enabled, this can result in a use-after-free: 1. access to skb->nf_trace 2. access to skb->mark 3. computation of trace id 4. dump of packet payload  To avoid 1, keep a cached copy of skb->nf_trace in the trace state struct. Refresh this copy whenever verdict is != STOLEN.  Avoid 2 by skipping skb->mark access if verdict is STOLEN.  3 is avoided by precomputing the trace id.  Only dump the packet when verdict is not \"STOLEN\".",
                        "cve_priority": "medium",
                        "cve_public_date": "2025-02-26 07:01:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98794",
                        "url": "https://ubuntu.com/security/CVE-2026-98794",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ipvs: filter some flags received in the backup server  While the IPVS SYNC protocol is not secure by design we can still protect the backup server from messages that can wreak havoc.  This commit addresses problems from received connection flags or their combinations. We now drop messages as follows:  1. the NO_CPORT+TEMPLATE combination allows lookups for normal connections to hit template which can break in many ways. While the master does not sync connections with NO_CPORT flag, i.e. before they are established, we still accept NO_CPORT without TEMPLATE.  2. ONE_PACKET: it is not sent by master, so we do not expect it in backup. Before now it was ignored by IP_VS_CONN_F_BACKUP_MASK for protocol v1 while protocol v0 created connections that are not hashed and dropped immediately. Better to apply the IP_VS_CONN_F_BACKUP_MASK also to the flags from v0 messages for consistency with v1.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98805",
                        "url": "https://ubuntu.com/security/CVE-2026-98805",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  tipc: prevent GCM nonce reuse on peer key changes  TIPC can encrypt traffic between nodes using a different transmit key for each node. In this mode, the AES-GCM nonce for a packet sent to a known peer consists of a 32-bit prefix (a per-key salt XOR the peer's address) followed by a 64-bit counter. That counter is stored in the peer's RX crypto object. When the peer reports a change in which key it uses to receive packets, TIPC resets this counter. The sender can still be using the same TX key and salt, so subsequent packets reuse earlier nonces. This nonce reuse breaks confidentiality and exposes GCM's authentication key. This makes forgeries trivial: an attacker can exploit CTR malleability to alter captured ciphertexts and use the recovered authentication key to compute a valid tag for the modified ciphertext, under the same key and nonce.  Use the TX key's existing aead->seqno counter instead. All encryptions using that key object share the same atomic counter, so concurrent encryptions get distinct nonce counter values. The counter survives key activation and peer reconnection, and peer key-status reports cannot reset it. This prevents those transitions from causing nonce reuse while the same TX key remains installed.  The nonce format is unchanged, and receivers do not require consecutive counter values, so sharing the counter across peers remains compatible with existing receivers. A pre-existing check still invokes key revocation in the unlikely event that the counter wraps to zero.",
                        "cve_priority": "critical",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98811",
                        "url": "https://ubuntu.com/security/CVE-2026-98811",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net/sched: cls_api: reclaim an empty proto on the error path  Two racing tc filter add requests on the same chain/prio of an unlocked classifier both run change() on the shared proto and both can fail: the winner's tcf_chain_tp_delete_empty() attempt gives up because the loser's handle is still in the idr, and the loser's error path drops only its own reference without a second reclamation attempt. The empty proto stays linked in the chain, holding the chain reference, a block reference and the classifier module reference until the chain or block is torn down.  Reclaim the proto on the error path of any failed request that holds a proto reference. The reclamation is emptiness-gated: tcf_chain_tp_delete_empty() unlinks the proto only when delete_empty() admits it is empty, so a live shared proto is never unlinked. A proto the request created is reclaimed unconditionally - it is the only owner, so marking it for deletion is safe even without a delete_empty callback. Classifiers without one (the check marks the proto unconditionally) are rtnl-serialized, so the raced window this guard closes cannot arise for them.  This is a follow-up to commit d4e359b3608a (\"net/sched: cls_api: fix teardown of an adopted proto on insert-race loss\"), which stopped the loser of the insert race from unlinking the winner's live proto but left the empty-proto residual in place.  Conditions to recreate: - CONFIG_NET_CLS_FLOWER=y; veth pair - tc qdisc add dev veth0 ingress - two concurrent `tc filter add dev veth0 ingress protocol ip pref 1   flower skip_sw ... action drop` (both fail in fl_hw_replace_filter   after publishing their handle in the idr); repeat in a loop - an empty flower tp stays linked after both requests fail; visible   as a bare `filter protocol ip pref 1 flower chain 0` header in   `tc filter show` with no filter entries - CAP_NET_ADMIN (namespace-local via unshare -Urn suffices)",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98812",
                        "url": "https://ubuntu.com/security/CVE-2026-98812",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net/mctp: publish the mctp_dev only after it is initialised  mctp_add_dev() links the new mctp_dev into dev->mctp_ptr before mdev->dev is assigned, so a reader that picks the device up in that window dereferences a net_device pointer that is still NULL:  KASAN: null-ptr-deref in range [0x00000000000000b0-0x00000000000000b7] Call Trace:  <TASK>  ? __pfx_mctp_sendmsg (./include/linux/sockptr.h:49)  ? __pfx_mctp_dst_output (net/mctp/route.c:41)  ? selinux_socket_sendmsg (security/selinux/hooks.c:5278)  ____sys_sendmsg (net/socket.c:775 (discriminator 1) net/socket.c:790  (discriminator 1) net/socket.c:2684 (discriminator 1))  ? __pfx_____sys_sendmsg (net/socket.c:1131)  ? __pfx_copy_msghdr_from_user (net/socket.c:2590)  ? update_cfs_rq_load_avg (kernel/sched/fair.c:5478)  ___sys_sendmsg (net/socket.c:2738)  ? __pfx____sys_sendmsg (net/socket.c:2625)  ? perf_event_task_tick (./include/linux/rcupdate.h:838)  ? sched_tick (kernel/sched/core.c:5818)  ? clockevents_program_event (kernel/time/clockevents.c:372)  ? fdget (./include/linux/rcupdate.h:873 fs/file.c:1100)  __sys_sendmsg (net/socket.c:2770)  ? __pfx___sys_sendmsg (net/socket.c:2751)  do_syscall_64 (arch/x86/entry/syscall_64.c:63)  entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:121)  </TASK>  Fix by publishing only once the object is fully initialised: __mctp_dev_get() runs under rcu_read_lock() only and hands this object to readers as soon as mctp_ptr is assigned, so they must never observe mdev->dev == NULL.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98819",
                        "url": "https://ubuntu.com/security/CVE-2026-98819",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  Bluetooth: btintel: validate DDC record lengths  Parse DDC record lengths in unsigned storage so 0xFF does not wrap. Reject records smaller than the mandatory three-byte header, records exceeding U8_MAX, and records exceeding remaining firmware bytes before issuing Intel_Write_DDC.  This issue was reported by Claude Mythos.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98823",
                        "url": "https://ubuntu.com/security/CVE-2026-98823",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: cfg80211: preserve hidden-group beacon IE ownership  A hidden-group probe-response entry borrows its beacon IEs from the group's beacon entry. cfg80211_update_assoc_bss_entry() can pass such an entry to cfg80211_update_known_bss() when merging scan entries after a channel switch.  Copying the borrowed beacon_ies into the associated entry gives the same allocation two owners. Releasing the group's beacon entry can then leave the associated entry pointing to freed IEs, which are freed again when that entry is released.  Skip beacon IE replacement when the source entry belongs to a hidden group. Preserve probe-response processing, the subsequent metadata updates, and the existing rejection path for conflicting hidden beacon updates.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98936",
                        "url": "https://ubuntu.com/security/CVE-2026-98936",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: ath11k: reset ar->num_stations on hardware start  When (multiple) hw restart occurs, we end up in a situation where we cannot accept new stations / mesh peers. This seems to be the 'num_stations' in 'struct ath11k' that did not get reset properly in this case. In ath11k_mac_op_start(), it was indeed the only accounting var that did not get reset so let's clear it too.  This avoids problems like those:  \t[1248828.088023] WARNING: CPU: 0 PID: 12281 at net/mac80211/util.c:1682 ieee80211_reconfig_stations+0x98/0xc0 \t[1248828.088115] Call trace: \t[1248828.088116]  ieee80211_reconfig_stations+0x98/0xc0 (P) \t[1248828.088119]  ieee80211_reconfig+0x774/0x1438 \t[1248828.088123]  ieee80211_restart_work+0x10c/0x178 \t[1248828.088127]  process_one_work+0x178/0x3c0 \t[1248828.088130]  worker_thread+0x280/0x440 \t[1248828.088133]  kthread+0xe0/0xf8 \t[1248828.088137]  ret_from_fork+0x10/0x20 \t[1248828.088141] ---[ end trace 0000000000000000 ]--- \t[1248836.686604] ath11k_pci 0000:04:00.0: refusing to associate station: too many connected already (128) \t[1248836.686609] ath11k_pci 0000:04:00.0: Failed to add station: xx:xx:xx:xx:xx:xx for VDEV: 1  Tested-on: QCN9074 hw1.0 PCI WLAN.HK.2.9.0.1-01977-QCAHKSWPL_SILICONZ-1",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98831",
                        "url": "https://ubuntu.com/security/CVE-2026-98831",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  of/overlay: don't leak fragment references when changeset init fails  init_overlay_changeset() stores the number of initialized fragments in ovcs->count only on full success. When find_target() or the __symbols__ lookup fails partway through, the target and overlay references taken for the fragments initialized so far are never dropped: free_overlay_changeset() bounds its cleanup loop by ovcs->count, which is still 0.  Store the running count on the error path so free_overlay_changeset() puts whatever was set up. The store is guarded by ovcs->fragments because on the allocation-failure path cnt still holds the counting pass total while there is no fragments array; everywhere else cnt only counts fully-initialized fragments.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98833",
                        "url": "https://ubuntu.com/security/CVE-2026-98833",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  mtd: core: call _get_device() with the master MTD  __get_mtd_device() calls the master's _get_device() callback with mtd, which may be a partition. __put_mtd_device() passes the master.  This breaks gluebi partitions because gluebi_get_device() uses container_of() and therefore requires the master MTD. Pass the master to _get_device(), matching _put_device().",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-89860",
                        "url": "https://ubuntu.com/security/CVE-2026-89860",
                        "cve_description": "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 second INIT_WORK() reinitializes a work item that is already queued, which can corrupt the workqueue list and lead to crashes or a looping worker.  Initialize priv->abort_work once at command submission, next to the existing per-command spin_lock_init(&priv->cmd_lock), and leave only schedule_work() in the abort paths. schedule_work() already does nothing when the work item is still pending, so a repeated abort no longer disturbs an in-flight work item. The command is not returned to the transport until the final kref_put()/release callback runs after abort_work has completed, so the work item is idle before priv is reused and the single submission-time INIT_WORK() is safe.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-09-16 11:16:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-53353",
                        "url": "https://ubuntu.com/security/CVE-2026-53353",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  hsr: Remove WARN_ONCE() in hsr_addr_is_self().  syzbot reported the warning [0] in hsr_addr_is_self(), whose assumption is simply wrong.  hsr->self_node is cleared in hsr_del_self_node(), which is called from hsr_dellink().  Since dev->rtnl_link_ops->dellink() is called before unregister_netdevice_many(), there is a window when user can find the device but without hsr->self_node.  Let's remove WARN_ONCE() in hsr_addr_is_self().  [0]: HSR: No self node WARNING: net/hsr/hsr_framereg.c:39 at hsr_addr_is_self+0x211/0x3f0 net/hsr/hsr_framereg.c:39, CPU#0: syz.4.16848/17220 Modules linked in: CPU: 0 UID: 0 PID: 17220 Comm: syz.4.16848 Tainted: G             L     syzkaller #0 PREEMPT_{RT,(full)} Tainted: [L]=SOFTLOCKUP Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/18/2026 RIP: 0010:hsr_addr_is_self+0x211/0x3f0 net/hsr/hsr_framereg.c:39 Code: 33 2f 41 0f b7 dd 89 ee 09 de 31 ff e8 c8 b4 c6 f6 09 dd 74 54 e8 0f b0 c6 f6 31 ed eb 53 e8 06 b0 c6 f6 48 8d 3d 2f 50 9c 04 <67> 48 0f b9 3a 31 ed eb 42 e8 c1 13 1f 00 89 c5 31 ff 89 c6 e8 96 RSP: 0018:ffffc900041c70e0 EFLAGS: 00010283 RAX: ffffffff8afdc6ca RBX: ffffffff8afdc4e6 RCX: 0000000000080000 RDX: ffffc90010493000 RSI: 0000000000000948 RDI: ffffffff8f9a1700 RBP: 0000000000000001 R08: 0000000000000000 R09: 0000000000000000 R10: ffffc900041c71e8 R11: fffff52000838e3f R12: dffffc0000000000 R13: ffff888041f9e3c0 R14: ffff888086ee3802 R15: 0000000000000000 FS:  00007f6fe985d6c0(0000) GS:ffff888126176000(0000) knlGS:0000000000000000 CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f80bd437dac CR3: 0000000025096000 CR4: 00000000003526f0 DR0: ffffffffffffffff DR1: 00000000000001f8 DR2: 0000000000000002 DR3: ffffffffefffff15 DR6: 00000000ffff0ff0 DR7: 0000000000000400 Call Trace:  <TASK>  check_local_dest net/hsr/hsr_forward.c:592 [inline]  fill_frame_info net/hsr/hsr_forward.c:728 [inline]  hsr_forward_skb+0xa11/0x2a80 net/hsr/hsr_forward.c:739  hsr_dev_xmit+0x253/0x370 net/hsr/hsr_device.c:236  __netdev_start_xmit include/linux/netdevice.h:5368 [inline]  netdev_start_xmit include/linux/netdevice.h:5377 [inline]  xmit_one net/core/dev.c:3888 [inline]  dev_hard_start_xmit+0x2df/0x860 net/core/dev.c:3904  __dev_queue_xmit+0x1428/0x3900 net/core/dev.c:4870  neigh_output include/net/neighbour.h:556 [inline]  ip_finish_output2+0xcec/0x10b0 net/ipv4/ip_output.c:237  ip_send_skb net/ipv4/ip_output.c:1510 [inline]  ip_push_pending_frames+0x8b/0x110 net/ipv4/ip_output.c:1530  raw_sendmsg+0x1547/0x1a50 net/ipv4/raw.c:659  sock_sendmsg_nosec net/socket.c:787 [inline]  __sock_sendmsg net/socket.c:802 [inline]  ____sys_sendmsg+0x7da/0x9c0 net/socket.c:2698  ___sys_sendmsg+0x2a5/0x360 net/socket.c:2752  __sys_sendmsg net/socket.c:2784 [inline]  __do_sys_sendmsg net/socket.c:2789 [inline]  __se_sys_sendmsg net/socket.c:2787 [inline]  __x64_sys_sendmsg+0x1c3/0x2a0 net/socket.c:2787  do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]  do_syscall_64+0x15f/0xf80 arch/x86/entry/syscall_64.c:94  entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f6feb62ce59 Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 e8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f6fe985d028 EFLAGS: 00000246 ORIG_RAX: 000000000000002e RAX: ffffffffffffffda RBX: 00007f6feb8a6090 RCX: 00007f6feb62ce59 RDX: 0000000000000000 RSI: 0000200000000000 RDI: 0000000000000004 RBP: 00007f6feb6c2d6f R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007f6feb8a6128 R14: 00007f6feb8a6090 R15: 00007ffcf01cc488  </TASK>",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-07-01 14:16:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98836",
                        "url": "https://ubuntu.com/security/CVE-2026-98836",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ALSA: line6: reject oversized playback packets  Each playback URB is handed a slice of out.buffer that is exactly LINE6_ISO_PACKETS * max_packet_size_out bytes, sized from the OUT endpoint, but the number of bytes written into that slice is never compared against it.  submit_audio_out_urb() takes the frame count from prev_fsize, which audio_in_callback() derived from the *IN* endpoint's received packet length, and rescales it with the playback frame size; when prev_fsize is still zero it synthesizes a length from the sample rate instead.  On a device declaring a large IN wMaxPacketSize and a small OUT wMaxPacketSize, the resulting memcpy(), or the memset() when the playback stream is idle, runs past its slice and, as the reproducer below shows, beyond the allocation.  usb_submit_urb() is not a backstop.  max_packet_size_out comes from usb_maxpacket(), which returns only the low 11 bits of wMaxPacketSize, while USB core validates a high-speed isochronous length against that base scaled by usb_endpoint_maxp_mult().  A length of up to three times the allocated slice is therefore accepted, and even a rejected URB is only rejected after the write.  Reject a packet that does not fit the slice the driver allocated for it. Clamping it instead would silently shorten the capture-derived rate feedback and desynchronize the two streams.    BUG: KASAN: slab-out-of-bounds in submit_audio_out_urb (sound/usb/line6/playback.c:229)   Write of size 1024 at addr ffff888100bbd400 by task kworker/1:2/5002   Workqueue: events line6_startup_work   Call Trace:    __asan_memcpy (mm/kasan/shadow.c:106)    submit_audio_out_urb (sound/usb/line6/playback.c:229)    line6_submit_audio_out_all_urbs (sound/usb/line6/playback.c:291)    line6_stream_start (sound/usb/line6/pcm.c:194)    line6_pcm_acquire (sound/usb/line6/pcm.c:337)    line6_startup_work (sound/usb/line6/driver.c:728)    process_one_work (kernel/workqueue.c:3396)    worker_thread (kernel/workqueue.c:3479 kernel/workqueue.c:3560)    kthread (kernel/kthread.c:436)    ret_from_fork (arch/x86/kernel/process.c:158)    ret_from_fork_asm (arch/x86/entry/entry_64.S:245)    The buggy address belongs to the object at ffff888100bbd400    which belongs to the cache kmalloc-256 of size 256   The buggy address is located 0 bytes inside of    allocated 256-byte region [ffff888100bbd400, ffff888100bbd500)",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98838",
                        "url": "https://ubuntu.com/security/CVE-2026-98838",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  vt: skip screen update for DEC alignment test on backgroup consoles  [BUG] Recently, we encountered a KASAN warning as follows:  BUG: KASAN: slab-out-of-bounds in fb_pad_aligned_buffer+0x11f/0x140 Read of size 1 at addr ff1100015fd9f6a4 by task tty_fbcon_oob/1239 CPU: 7 UID: 0 PID: 1239 Comm: tty_fbcon_oob Not tainted 7.3.0-rc1 #100 PREEMPT(full) Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.17.0-4.fc41 04/01/2014 Call Trace:  <TASK>  ...  kasan_report+0xf0/0x120  fb_pad_aligned_buffer+0x11f/0x140  ccw_putcs+0x86c/0xa80  fbcon_putcs+0x338/0x410  do_update_region+0x21d/0x450  do_con_write+0x1e0e/0x4880  con_write+0x13/0x80  n_tty_write+0x374/0x1010  file_tty_write.isra.0+0x404/0x7a0  ...  reproduce: 1) open /dev/tty0, set a KDFONTOP ioctl with op.op = KD_FONT_OP_SET, op.width = 8 and op.height = 16 (visible VC1) 2) open /dev/tty1, set a KDFONTOP ioctl with op.op = KD_FONT_OP_SET, op.width = 28 and op.height = 24 (invisible VC2) 3) echo 3 > /sys/devices/virtual/graphics/fbcon/rotate_all 4) write EShash8(esc hash8) to tty1  [CAUSE] All VCs render to the framebuffer. setfont only modifies the target VC's font without resizing the framebuffer backing buffer (par->rotated.buf); the buffer is only resized for the visible VC (fbcon_do_set_font -> ... -> vc_do_resize -> update_screen). This relies on the con_should_update() check performed before every update_region().  However, the ESC # 8 path (do_con_trol -> do_update_region) omits the con_should_update() check. After changing the font size of an invisible VC, do_update_region() fills using the new font size against a buffer that was never resized, causing an out-of-bounds access.  [FIX] Only push the update when the console is visible and not blanked, add the con_should_update() check in the do_con_trol() like every other call site of do_update_region() (update_region(), invert_screen(), ...).",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98568",
                        "url": "https://ubuntu.com/security/CVE-2026-98568",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  vxlan: use one headroom snapshot for neighbour replies  vxlan_na_create() samples LL_RESERVED_SPACE() to size the reply skb and then samples it again to reserve headroom. A concurrent vxlan_changelink() can update needed_headroom between the two reads, creating a TOCTOU race. The second value can exceed the allocation and make the Ethernet header write out of bounds.  The race is reproducible on the unpatched kernel. It occurred when vxlan_na_create() generated a neighbour reply while vxlan_changelink() changed the link headroom. KASAN caught a four-byte write two bytes beyond a 704-byte skbuff_small_head allocation.  Snapshot the headroom once and use that value for both allocation and reservation.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2024-49901",
                        "url": "https://ubuntu.com/security/CVE-2024-49901",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  drm/msm/adreno: Assign msm_gpu->pdev earlier to avoid nullptrs  There are some cases, such as the one uncovered by Commit 46d4efcccc68 (\"drm/msm/a6xx: Avoid a nullptr dereference when speedbin setting fails\") where  msm_gpu_cleanup() : platform_set_drvdata(gpu->pdev, NULL);  is called on gpu->pdev == NULL, as the GPU device has not been fully initialized yet.  Turns out that there's more than just the aforementioned path that causes this to happen (e.g. the case when there's speedbin data in the catalog, but opp-supported-hw is missing in DT).  Assigning msm_gpu->pdev earlier seems like the least painful solution to this, therefore do so.  Patchwork: https://patchwork.freedesktop.org/patch/602742/",
                        "cve_priority": "low",
                        "cve_public_date": "2024-10-21 18:15:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98846",
                        "url": "https://ubuntu.com/security/CVE-2026-98846",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  sctp: check RCV_SHUTDOWN after the sendmsg connect wait  sctp_wait_for_connect() drops the socket lock while it sleeps. An out-of-the-blue ABORT can then be processed from the socket backlog and unlink the association. If a concurrent shutdown(fd, SHUT_RD) sets RCV_SHUTDOWN, the waiter breaks with err == 0 before checking asoc->base.dead. Its final sctp_association_put() can then free the association, leaving sctp_sendmsg_to_asoc() to continue with a dangling pointer.  Check RCV_SHUTDOWN along with the wait error in sctp_sendmsg_to_asoc() before using the association again. The check only accesses the socket, so it needs no additional association reference. Return the existing -ESRCH so that sctp_sendmsg() skips freeing a new association that may already have been destroyed.  Keep sctp_wait_for_connect() unchanged to preserve its behavior for the connect() caller.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98847",
                        "url": "https://ubuntu.com/security/CVE-2026-98847",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  rtc: spear: initialize IRQ state before requesting alarm IRQ  devm_request_irq() enables the interrupt before it returns, so the handler may run while probe is still initializing the device. Initialize the MMIO address and spinlock before requesting the alarm IRQ.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98850",
                        "url": "https://ubuntu.com/security/CVE-2026-98850",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net/packet: prevent TX_RING byte count overflow  tpacket_snd() drains every SEND_REQUEST frame in a TX ring and adds each valid packet length to the signed int len_sum. Userspace can recycle completed frames concurrently, so a single blocking send call is not bounded by the ring size.  After enough successful transmissions len_sum wraps into the negative range. In particular, 65536 65535-byte frames followed by a 65007-byte frame produce 0xfffffdef, or -EIOCBQUEUED. sock_sendmsg_nosec() treats that as an impossible return and triggers a BUG. On systems configured to panic on oops, a CAP_NET_RAW holder can panic the host kernel.  Stop before the next frame would make the byte count exceed INT_MAX. The positive short count leaves that frame pending for a later send call.  A two-thread TPACKET_V2 reproducer triggered the BUG on an arm64 build of Linux 7.3-rc4. With this change, the same reproducer returned the expected positive short count without an oops.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98851",
                        "url": "https://ubuntu.com/security/CVE-2026-98851",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  netfilter: nft_flow_offload: drop flowtable reference on init error path  nft_flow_offload_init() bumps the flowtable use count with nft_use_inc() before calling nf_ct_netns_get().  When the latter fails, the error is returned as-is and the reference is leaked.  The upper layers do not balance it either: nf_tables_newexpr() clears expr->ops when the expression init callback fails, so the nft_expr_more() iteration in nft_rule_expr_deactivate() and nf_tables_rule_destroy() stops right before the failed expression and its ->destroy callback, which would drop the reference, never runs.  Each failed rule addition therefore leaks one flowtable reference and the flowtable can no longer be removed: NFT_MSG_DELFLOWTABLE keeps reporting -EBUSY even though no rule references it.  Save the nf_ct_netns_get() return value and undo the nft_use_inc() when it fails, restoring the inc/dec pairing within nft_flow_offload_init() itself.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98854",
                        "url": "https://ubuntu.com/security/CVE-2026-98854",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  of/overlay: only treat a positive changeset id as registered  of_overlay_fdt_apply() stores the idr_alloc() return value in ovcs->id before checking it. On failure the stored id is negative, free_overlay_changeset()'s \"if (ovcs->id)\" check passes, idr_remove() is called with a negative id and list_del() runs on ovcs->ovcs_list, which is not initialized until after the id allocation. An allocation failure at that point dereferences NULL.  Make free_overlay_changeset() treat only a strict-positive id as registered. The rest of the function already copes with a partially-initialized ovcs, so the error path stays a plain goto err_free_ovcs.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98855",
                        "url": "https://ubuntu.com/security/CVE-2026-98855",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  of/overlay: put property on deadprops only after changeset add succeeds  add_changeset_property() links a new property of a not-yet-live target node into the node's deadprops list before handing it to of_changeset_add_property(). If that fails, the error path frees the property but leaves the freed pointer linked in deadprops, and of_node_release() frees it a second time when the aborted overlay's node is released.  Record the changeset entry first and link the property into deadprops only on success. of_changeset_add_property() never looks at the node's property lists, so the order of the two steps is otherwise immaterial, and the error path frees a property that nothing references.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98862",
                        "url": "https://ubuntu.com/security/CVE-2026-98862",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  audit: fix exe mark UAF in kill_rules()  kill_rules() removes mixed AUDIT_DIR and AUDIT_EXE rules when an audit tree is pruned. It drops entry->rule.exe before removing the rule from the RCU-visible filter lists.  After a rule has been installed with AUDIT_ADD_RULE, which requires CAP_AUDIT_CONTROL, removing the watched directory can race with another task that is still evaluating the rule. In that case, fsnotify can free the executable mark before the reader reaches audit_mark_compare(), causing a use-after-free.  KASAN reports:      BUG: KASAN: slab-use-after-free in audit_mark_compare+0x8d/0xa0  Unlink the published rules from the RCU-visible lists and retain them on tree->rules for cleanup. If any rule has an executable mark, wait for a single RCU grace period before removing the marks and scheduling the entries for freeing. Otherwise, call_rcu() already provides the required deferred freeing without a synchronous wait.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98450",
                        "url": "https://ubuntu.com/security/CVE-2026-98450",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  smb: client: close completed creates on compound wait errors  compound_send_recv() waits for responses in order. If a later wait is interrupted, or if a later MID fails during response synchronization, an earlier CREATE may already have opened a remote handle. The earlier mid is then released without invoking handle_cancelled_mid(), leaving the remote handle open because no FID was copied to the caller.  Mark completed earlier mids as cancelled when a compound wait or MID synchronization aborts. Keep their response buffers attached while the MIDs are synchronized, and transfer them only after synchronization of the processed responses, so the release path can inspect successful CREATE responses and queue SMB2_close() after a later failure. Account for a remote open only after the close work is allocated and before it is queued, since the caller has not yet updated num_remote_opens. Mark the create+close compound used by smb2_unlink() so it is not closed again. Non-CREATE responses and compounds that already include a close keep their existing behavior.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:16:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98502",
                        "url": "https://ubuntu.com/security/CVE-2026-98502",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  HID: alps: unregister DualPoint Stick input device on remove  alps_input_configured() allocates a second input device (\"DualPoint Stick\") with input_allocate_device() and registers it, but the alps_driver struct has no .remove handler and input2 is not tracked in hdev->inputs.  The default remove path (hid_hw_stop -> hidinput_disconnect) only iterates hdev->inputs, so input2 is never unregistered and leaks on every device removal.  Add a .remove handler that stops the device first (preventing URB callbacks from touching input2 during teardown) and then unregisters input2.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98456",
                        "url": "https://ubuntu.com/security/CVE-2026-98456",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  Bluetooth: mgmt: fix race in read_unconf_index_list()  read_unconf_index_list() counts unconfigured controllers before allocating its response, then checks the device flags again while filling it.  hci_dev_list_lock stabilizes list membership, but it does not serialize the per-device flags. During asynchronous controller setup, the worker can set HCI_UNCONFIGURED and clear HCI_SETUP between the two passes. A controller omitted from the allocation count can then become eligible for the fill pass, causing an out-of-bounds write to rp->index[].  Allocate space for every device on hci_dev_list. Since list membership cannot change while hci_dev_list_lock is held, the response remains large enough regardless of flag transitions. The reported count and response length still include only eligible unconfigured controllers.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-18 16:16:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98451",
                        "url": "https://ubuntu.com/security/CVE-2026-98451",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  smb: client: use finish_no_open() for non-regular inodes  An O_CREAT open can find an existing symlink or another non-regular inode. cifs_atomic_open() calls finish_open() on it and attaches a cifsFileInfo. Symlink inodes have no CIFS release operation, so the dentry reference held by cifsFileInfo is leaked. FMODE_OPENED also prevents the VFS from following the symlink.  Track whether cifs_do_create() returned an open server handle. For non-regular inodes, close the handle if present, remove the pending open, and call finish_no_open() so the VFS can continue the lookup. Do not set FMODE_CREATED unless a regular file was opened. For O_NOFOLLOW with __O_REGULAR, return -ELOOP before the VFS's -EFTYPE check.  Defer closing a legacy POSIX handle on a non-regular inode until after inode lookup. This avoids closing it again if lookup fails.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-18 16:16:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98484",
                        "url": "https://ubuntu.com/security/CVE-2026-98484",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  netfilter: nf_tables: skip expired catchall elements on insert and delete  nft_setelem_catchall_insert() looks up duplicates with nft_set_elem_active() only, while nft_set_catchall_lookup() and the dump path additionally skip expired elements.  Once a catchall element with a timeout expires, this predicate drift makes it invisible to userspace dumps, yet it still blocks re-insertion: with NLM_F_EXCL the request fails with -EEXIST, and without it the request reports success but silently inserts nothing. The stale entry only goes away when the (user-tunable) gc interval elapses, so the catchall rule may silently stop matching for an arbitrarily long time after its first expiration.  The delete path shows the same drift: nft_setelem_catchall_deactivate() picks the first active-next entry in the catchall list, so with an expired entry still pending GC it retires the stale entry instead of the fresh one, and it deactivates an element that userspace no longer sees instead of failing with -ENOENT.  Align both walks with the lookup and dump predicates: only an element that is active and not expired counts as a duplicate or delete candidate, using the per-netns timestamp taken at transaction start, in line with the set backend .insert/.deactivate and catchall GC sync paths.",
                        "cve_priority": "negligible",
                        "cve_public_date": "2026-10-18 16:16:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98486",
                        "url": "https://ubuntu.com/security/CVE-2026-98486",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net: ena: fix MMIO read buffer leak on probe failure  ena_device_init() initializes the MMIO read mechanism with ena_com_mmio_reg_read_request_init(), which allocates a coherent DMA buffer for MMIO read responses.  The normal removal path releases this buffer through ena_com_mmio_reg_read_request_destroy(). However, if ena_probe() fails after ena_device_init() succeeds, the error path destroys the admin resources and eventually frees ena_dev without destroying the MMIO read request, leaving the coherent DMA buffer allocated.  Call ena_com_mmio_reg_read_request_destroy() in the probe error path before releasing the remaining device resources.  This issue was found by manual code inspection.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:16:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98493",
                        "url": "https://ubuntu.com/security/CVE-2026-98493",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net: ipconfig: bound DHCP option construction  ic_dhcp_init_options() appends the hostname (option 12), vendor-class (option 60) and client-ID (option 61) options into the fixed 312-byte bootp_pkt.exten[] buffer.  Only the client-ID branch checked the remaining space; the hostname and vendor-class writes were unbounded.  A 64-byte hostname together with the maximum 252-byte dhcpclass= identifier needs 18 + (2 + 64) + (2 + 252) = 338 of the 312 available bytes even before the terminating END marker, so the vendor-class memcpy runs past the end of exten[].  With CONFIG_FORTIFY_SOURCE this is reported as a field-spanning write and, when the kernel is booted with panic_on_warn=1, aborts boot with a panic.  Route the optional options through a common helper that makes sure the option, its 2-byte header and the END marker all fit and drops an option that would not.  Configurations with short options keep sending exactly the same bytes as before.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98454",
                        "url": "https://ubuntu.com/security/CVE-2026-98454",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  smb: client: fix create context out-of-bounds reads  smb2_parse_contexts() validates the complete create-context area but does not limit each record to its Next field before dispatching it.  A malformed chain can therefore expose bytes beyond the current context to a handler.  The QFid handler also used a full response-structure cast although it only reads DiskFileId.  The SMB2/SMB3 lease parsers made the same layout assumption: they read LeaseState and LeaseFlags at canonical offsets rather than at DataOffset.  A valid non-canonical DataOffset could therefore yield unrelated in-bounds data, while a short DataLength was still accepted.  Limit each context to its Next value, reject offsets before the context header, and reject malformed chains.  Bound the name range by the current context and do not dispatch a known handler when DataLength is zero.  Read the QFid DiskFileId only when the context data covers that field.  Parse the lease context from DataOffset and require DataLength to match the v1 or v2 lease_context size used by ksmbd.  A size mismatch skips lease parsing without failing the open.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-18 16:16:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98490",
                        "url": "https://ubuntu.com/security/CVE-2026-98490",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net: openvswitch: conntrack: fix helper UAF due to extensions realloc  While calling the helpers, a raw pointer to the extensions area is wired into expectations list:    -> nf_ct_helper()    -> helper->help()     -> nf_ct_expect_related_report()      -> nf_ct_expect_insert()       -> hlist_add_head_rcu(&exp->lnode, &master_help->expectations)  In case the connection is not confirmed yet, more extensions can be added afterwards with *_ext_add() calls reallocating the extension space and leaving the now invalid pointer in the expectations list that is later accessed while removing the expectation.  Make sure that helpers are called at the end after all the other extensions are already added.  Note that the helper rejection now leaves the mark and labels set, but that's not different from how the NAT was handled before or how the mark and the labels were handled on confirmation failure.  And there are no atomicity guarantees provided by the API anyway.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-18 16:16:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98507",
                        "url": "https://ubuntu.com/security/CVE-2026-98507",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  mm/rmap: fix missing barrier between anon_vma init and vma->anon_vma publish  On arm64 server, we find that a task trying to grab the anon_vma lock triggers hungtask.  INFO: task main:2354726 blocked for more than 120 seconds.       Tainted: G            E     5.10.0-0021.aarch64 #1 \"echo 0 > /proc/sys/kernel/hung_task_timeout_secs\" disables this message. task:main            state:D stack:    0 pid:2354726 ppid:2350673 flags:0x00000a01 Call trace:  __switch_to+0x7c/0xbc  __schedule+0x3b4/0x8a0  schedule+0x50/0xe0  rwsem_down_write_slowpath+0x3cc/0x6cc  down_write+0x60/0x260  __anon_vma_prepare+0x6c/0x210  do_anonymous_page+0x258/0x660  handle_pte_fault+0x188/0x214  __handle_mm_fault+0x1b0/0x380  handle_mm_fault+0xf4/0x284  do_page_fault+0x19c/0x494  do_translation_fault+0xcc/0xf8  do_mem_abort+0x48/0xac  el0_da+0x44/0x80  el0_sync_handler+0x88/0xb4  el0_sync+0x160/0x180  After analyzing the vmcore, we found the anon_vma->root->rwsem.count is -1.  There is another anon_vma whose anon_vma->root->rwsem.count is 1, the anon_vma->root->rwsem.owner shows the lock is held, but the stack of the task shows the task doesn't hold the anon_vma lock.  After adding more debugging info, we found __anon_vma_prepare() reuses anon_vma and triggers the UAF of anon_vma->root due to missing memory barrier, leading to locking and unlocking two different anon_vma->root, thus leading to an anon_vma will never be unlocked, and another anon_vma couldn't be locked anymore.  This race requires two adjacent VMAs that are not merged but are anon_vma-compatible (e.g., they differ in VMA_ACCESS_FLAGS that can be changed by mprotect()).  Two threads fault on each VMA concurrently, both calling __anon_vma_prepare() with only mmap_lock held for reading.      THREAD A                             THREAD B __anon_vma_prepare                __anon_vma_prepare  find_mergeable_anon_vma() -> NULL  anon_vma = anon_vma_alloc();    anon_vma->root = anon_vma;  // the two stores may be reordered  vma->anon_vma = anon_vma;                                    // finds A's anon_vma                                    anon_vma = find_mergeable_anon_vma(vma);                                    anon_vma_lock_write(anon_vma);                                      // may still see the old root                                      down_write(&anon_vma->root->rwsem);                                    anon_vma_unlock_write(anon_vma);                                      // see the new root, never unlock old                                      up_write(&anon_vma->root->rwsem);  thread A triggers page fault and calls __anon_vma_prepare() to prepare anon_vma for the faulting vma.  __anon_vma_prepare() allocates and initializes a new anon_vma, and then publishes it to the vma with a plain store.  anon_vma_prepare() only requires the mmap_lock to be held for reading, so two threads can fault on adjacent VMAs at the same time. While thread A publishes a new anon_vma, thread B could find the anon_vma via find_mergeable_anon_vma() and then locks anon_vma->root->rwsem.  The store to anon_vma->root in anon_vma_alloc() and the store to vma->anon_vma can be reordered.  The anon_vma_lock_write() and spin_lock() only provide acquire semantics, which do not prevent prior stores from being reordered after them.  The release semantics of the corresponding spin_unlock() and anon_vma_unlock_write() come too late, the store to vma->anon_vma is already published before they take effect.  As a result, thread B can observe the following order:      vma->anon_vma = anon_vma;     anon_vma->root = anon_vma;  The anon_vma slab is SLAB_TYPESAFE_BY_RCU, so a newly allocated anon_vma may reuse memory from a previously freed one.  The constructor (anon_vma_ctor) does not reset anon_vma->root, and __put_anon_vma() doesn't clear it either, so the old root value persists until anon_vma_alloc() overwrites it.  If that store isn't v ---truncated---",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98519",
                        "url": "https://ubuntu.com/security/CVE-2026-98519",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  drm/amdgpu: Fix runtime PM leak in amdgpu_debugfs_test_ib_show()  amdgpu_debugfs_test_ib_show() resumes the device with pm_runtime_get_sync() before taking the reset domain semaphore with down_write_killable().  If the write lock acquisition is interrupted, the function returns without calling pm_runtime_put_autosuspend(), leaking the runtime PM reference acquired for the device and keeping the GPU awake.  Drop the runtime PM reference on the interrupted down_write_killable() error path before returning.  (cherry picked from commit ec30a576c2d4c0364549e6c04218f50704ef56c8)",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98549",
                        "url": "https://ubuntu.com/security/CVE-2026-98549",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  tcp: prevent collapsing skbs across boundary in rtx queue  tcp_write_collapse_fence() sets TCP_SKB_CB(skb)->eor = 1 on tcp_write_queue_tail(sk) to prevent skbs queued after a switch to device encryption from being collapsed into earlier skbs.  The fence is a no-op if all earlier data has already been transmitted when the switch happens: sk->sk_write_queue is empty. The not yet acknowledged earlier skbs wait in sk->tcp_rtx_queue with eor 0.  On a subsequent retransmit or SACK shift, tcp_retrans_try_collapse() or tcp_shift_skb_data() can then merge an skb queued after the switch into one queued before it.  Both users of the fence are affected:  - psp: devices only encrypt skbs with skb->decrypted set. The merged skb   keeps decrypted = 0 from the earlier skb, so merged data sent after   psp_sock_assoc_set_tx() is retransmitted in cleartext.  - tls device offload: the merged skb straddles the start marker set in   tls_set_device_offload(). The software fallback (fill_sg_in() returns   -EINVAL) and the mlx5, nfp and funeth drivers cannot handle such an   skb and drop it. Every retransmit rebuilds the same skb, so the   connection stalls.  Fix this in two places, for defense in depth:  1. Fall back to tcp_rtx_queue_tail(sk) in tcp_write_collapse_fence()    when tcp_write_queue_tail(sk) is NULL.  2. Check !skb_cmp_decrypted(to, from) in tcp_skb_can_collapse(), as    tcp_skb_can_collapse_rx() does on receive. skb_shift(), which both    collapse paths call, already has a DEBUG_NET_WARN_ON_ONCE() for this    condition.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98544",
                        "url": "https://ubuntu.com/security/CVE-2026-98544",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  bna: prevent IOC timer rearm during teardown  bna: prevent IOC timer rearm during teardown  bnad_pci_remove() and the probe disable_ioceth path call timer_delete_sync() for ioc_timer, sem_timer and hb_timer, but not for iocpf_timer.  bnad_iocpf_timeout() then takes bnad->bna_lock after free_netdev() has freed the struct bnad.  Deleting iocpf_timer last does not fix this.  sem_timer and iocpf_timer rearm each other: bnad_iocpf_sem_timeout() can arm iocpf_timer, and bnad_iocpf_timeout() arms sem_timer from bfa_ioc_hw_sem_get() when the semaphore is busy. timer_delete_sync() only waits out its own callback. bnad_ioceth_disable() can time out and leave that callback live.  Shut all four IOC timers down with timer_shutdown_sync() on both paths, so a later mod_timer() is ignored.  This issue was identified during our ongoing static-analysis research while reviewing kernel code.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98172",
                        "url": "https://ubuntu.com/security/CVE-2026-98172",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  smb: client: fix smbd_connection leak on cifs_get_tcp_session() error  When an RDMA connection is successfully established via smbd_get_connection() but cifs_get_tcp_session() later fails (e.g. kthread_create() returns an error), the error path frees tcp_ses without first destroying the smbd_connection.  Fix this by calling smbd_destroy() in the out_err cleanup path before kfree(tcp_ses).  smbd_destroy() safely handles the case where smbd_conn is NULL, so it can be called unconditionally.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-06 09:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98192",
                        "url": "https://ubuntu.com/security/CVE-2026-98192",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: wcn36xx: Fix potential use-after-free in TX ack timer teardown  wcn36xx_dxe_deinit() tears down the TX ack timer with timer_delete(), which only dequeues the timer and does not wait for a callback that is already executing; the preceding free_irq() calls synchronize the interrupt handlers only. The callback, wcn36xx_dxe_tx_timer(), can therefore be running past the teardown and use the wcn freed along with the ieee80211_hw in wcn36xx_remove(): it takes wcn->dxe_lock, reads wcn->tx_ack_skb and passes wcn->hw to ieee80211_tx_status_irqsafe().  Fix this by using timer_shutdown_sync(), which waits for a running callback and also prevents the timer from being rearmed again. The timer is set up again by wcn36xx_dxe_init() on the next start, so the start/stop cycle is unaffected.  This issue was found by an in-house static analysis tool.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-06 09:18:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98198",
                        "url": "https://ubuntu.com/security/CVE-2026-98198",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  hwmon: (pwm-fan) Stop RPM timer before freeing tach data  sample_timer() rearms the RPM timer and accesses the devm-managed ctx->tachs and ctx->pulses_per_revolution arrays. The cleanup action which stops the timer is registered before those arrays are allocated.  Since devres releases entries in reverse order, driver detach can free the arrays before pwm_fan_cleanup() shuts down the timer. A timer expiry in that window accesses the freed tach data.  With a KASAN kernel, a test-only kprobe delayed entry to pwm_fan_cleanup() while normal sysfs unbind ran. Each of three runs reported three four-byte reads and two four-byte writes in sample_timer() after its backing devm allocations had been freed. The helper did not invoke the timer callback, cleanup actions or free functions.  With the fix, three matching unbind runs completed without KASAN, BUG, WARNING, Oops or panic. Instrumentation confirmed that timer retirement completed before the first timer backing allocation was released.  Split timer retirement from the power cleanup and register its devres action after the timer backing data and IRQ actions are installed. This preserves the early power rollback action while ensuring the timer is retired before its backing data is released. Use timer_shutdown_sync() because the callback can rearm itself.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-06 09:18:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98409",
                        "url": "https://ubuntu.com/security/CVE-2026-98409",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  watchdog: rtd119x: Avoid division by zero  clk_get_rate() could return 0.  Avoid a division by zero panic.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-14 14:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98245",
                        "url": "https://ubuntu.com/security/CVE-2026-98245",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  btrfs: take commit root semaphore when iterating in mark_block_group_to_copy()  mark_block_group_to_copy() iterates over the commit root with skip_locking=true. A concurrent transaction commit can swap and free the commit root during iteration, causing use-after-free when accessing extent buffers.  Fix it by using path->need_commit_sem to protect the commit root search.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-06 09:18:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98264",
                        "url": "https://ubuntu.com/security/CVE-2026-98264",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ALSA: virtio: reset device before deleting virtqueues  virtsnd_remove() and virtsnd_freeze() delete the virtqueues before resetting the device. del_vqs() frees the vring backing, but does not provide a generic device quiesce operation. In particular, modern virtio-pci keeps enabled queues active until the device is reset.  Reset the device before deleting the virtqueues so it can no longer access the vring memory when that memory is released. This also covers probe failures after DRIVER_OK, which unwind through virtsnd_remove().",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-06 09:18:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-97558",
                        "url": "https://ubuntu.com/security/CVE-2026-97558",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  smb: client: fix cifsFileInfo reference leak in deferred close  When cifs_close() defers a close, it hands the cifsFileInfo reference of the closing struct file to the queued work. Each execution of smb2_deferred_work_close() drops one such reference.  deferred_close_scheduled can be false while the work is pending: the workqueue clears PENDING when the callback starts to run, before the callback clears the flag under deferred_lock. A close in that interval requeues the running work, and the callback then clears the flag, leaving the requeued work pending with the flag down. A later cifs_open() can reuse the handle and its cifs_close() reaches the same branch: queue_delayed_work() fails because the work is still pending, but cifs_close() returns without dropping the closing file's reference. The cifsFileInfo count stays pinned and its tlink, dentry and server handle are leaked.  Check the return value and hand off the reference only when work was actually queued. Otherwise, use the shared _cifsFileInfo_put(), like the mod_delayed_work() branch above: the pending execution already owns its reference.  This issue was found by an in-house static analysis tool.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-09-25 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-97616",
                        "url": "https://ubuntu.com/security/CVE-2026-97616",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net/sched: act_api: release all action references on NEWACTION failure  When a batched RTM_NEWACTION request replaces an existing action, tcf_idr_check_alloc() takes a temporary reference on it. If a later action fails to initialize, tcf_action_destroy() uses strict release semantics to clean up the actions initialized so far. For an action bound to a filter, the strict check returns -EPERM without dropping the temporary reference.  This error also makes tcf_action_destroy() return before releasing subsequent entries. Any new action initialized between the bound action and the failing entry is leaked together with its reserved IDR slot, preventing reuse of its index.  Use tcf_idr_release() to drop each reference held by the batch without rejecting bound actions. This allows cleanup to continue through all initialized entries and preserves the module reference release when an action is destroyed. Explicit action deletion and flushing retain their separate bind-count checks.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-09-25 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-97939",
                        "url": "https://ubuntu.com/security/CVE-2026-97939",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ipmr: account multicast table and route memory  A netadmin in a user+net namespace can create many IPv4 and IPv6 multicast routing tables with MRT_TABLE and MRT6_TABLE. Each unseen id allocates an mr_table via the shared mr_table_alloc(), links it into the per-net list, and leaves it until netns teardown. Those objects were not charged to memcg, so the host unreclaimable slab grows with the table count.  Account mr_table allocations with GFP_KERNEL_ACCOUNT and mark the IPv4/IPv6 MFC caches SLAB_ACCOUNT. This matches the established handling of IP addresses, routes and alternate interface names.  Unresolved MFC entries are still allocated from softIRQ with GFP_ATOMIC and are not charged. They expire after 10 seconds and are bounded by the socket receive queue; see commit 0079ad8e8dc3 (\"ipmr: remove hard code cache_resolve_queue_len limit\").",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-09-25 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-89837",
                        "url": "https://ubuntu.com/security/CVE-2026-89837",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  f2fs: fix dentry folio leak in find_in_level  find_in_level() gets a dentry folio with f2fs_find_data_folio() before calling find_in_block().  If find_in_block() returns an error, the function stores the error in res_folio and breaks out of the loop without dropping the dentry folio.  This leaks the folio reference on the find_in_block() error path.  Drop the dentry folio before returning the error to the caller.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-09-16 11:16:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-89838",
                        "url": "https://ubuntu.com/security/CVE-2026-89838",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  f2fs: limit recovery filename logging to stored length  F2FS stores recovery filenames as a length plus a fixed-size i_name buffer.  The buffer is not NUL-terminated, but recover_inode() and recover_dentry() print it with %s.  For a 255-byte filename, recovery logging can read past i_name into the following raw inode fields.  Print the name with a precision bounded by i_namelen and F2FS_NAME_LEN.",
                        "cve_priority": "negligible",
                        "cve_public_date": "2026-09-16 11:16:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-97530",
                        "url": "https://ubuntu.com/security/CVE-2026-97530",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  scsi: qla2xxx: Fix soft lockup polling continuation IOCB signature  qla27xx_copy_multiple_pkt() and qla27xx_copy_fpin_pkt() poll rsp_q->ring_ptr->signature for RESPONSE_PROCESSED (0xDEADDEAD) to decide whether the next continuation IOCB has arrived, spinning on cpu_relax() without advancing the ring or decrementing the entry count while it has not. response_t::signature lives at byte offset 60, but a continuation IOCB (sts_cont_entry_t / struct sts_cont_entry_ext) carries raw FC frame payload at that offset (data[56..59]). A received frame whose payload bytes happen to equal 0xDEADDEAD is therefore misread as \"not yet arrived\", and the loop spins forever in interrupt/DPC context, causing a CPU soft lockup.  The poll is also unnecessary: callers of qla27xx_copy_multiple_pkt() (PT_LS4_UNSOL and the NVMe purls path) already gate on qla_chk_cont_iocb_avail(), which guarantees all entry_count IOCBs are present before copying begins. The sibling helper __qla_copy_purex_to_buffer() already drops the signature poll and relies on the entry_type == STATUS_CONT_TYPE guard instead.  Remove the signature busy-wait from both helpers, keeping the entry_type guard, and gate the FPIN path with qla_chk_cont_iocb_avail() so it defers and re-processes on the next interrupt once all continuation IOCBs have arrived, mirroring the ELS_AUTH_ELS and PT_LS4_UNSOL arms. With this the signature field is never read on a continuation IOCB, eliminating the payload-aliasing lockup.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-09-25 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98386",
                        "url": "https://ubuntu.com/security/CVE-2026-98386",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  scsi: qla2xxx: Use memset_io() to clear QLAFX00 request ring slot  For QLAFX00 the request ring is ioremapped device I/O memory (ha->iobase + req_que_off), not DMA-coherent RAM, which is why the rest of the FX00 path accesses it through memcpy_toio() and the wrt_reg_* helpers. __qla2x00_alloc_iocbs() however zeroed the producer slot with a plain memset(). On architectures such as ARM64 a regular memset() may emit unaligned or block-zeroing instructions (e.g. DC ZVA) that are invalid on Device memory, leading to a synchronous external abort.  Use memset_io() to clear the slot for QLAFX00, matching the I/O accessors used elsewhere on this ring. Other adapters keep the plain memset() on their DMA-coherent rings. The zero-fill is retained for FX00 because its IOCB builders (e.g. qlafx00_fxdisc_iocb()) copy only part of the entry and rely on the unused tail being pre-zeroed.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-14 14:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-89848",
                        "url": "https://ubuntu.com/security/CVE-2026-89848",
                        "cve_description": "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_work, and qla_do_work() -> qla24xx_process_response_queue() dereferences the now-freed rsp->req (LOGINOUT/CT/ELS entries and the status path), a use-after-free.  The cancel_work_sync() added for the qpair teardown lives in the response free path, which runs after the request queue is already freed, so it does not protect rsp->req.  Release the response-queue interrupt and flush qpair->q_work before deleting the request queue, so no late completion can reach the freed request queue. Clearing have_irq makes the subsequent qla25xx_free_rsp_que() skip its free_irq(), and the firmware queue-delete order (request then response) is preserved; the request-delete mailbox completes on the default vector and is unaffected by dropping the qpair response interrupt early.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-09-16 11:16:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-97532",
                        "url": "https://ubuntu.com/security/CVE-2026-97532",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  scsi: qla2xxx: Null out freed pointers in qla2x00_mem_alloc() error path  When qla2x00_mem_alloc() fails, qla2x00_probe_one() jumps to probe_hw_failed and calls qla2x00_mem_free(). Several error labels in qla2x00_mem_alloc() freed adapter members (elsrej.c, purex_dma_pool, flt, sfp_data, loop_id_map, async_pd, sf_init_cb, ex_init_cb, npiv_info) but left the pointers dangling. qla2x00_mem_free() then freed them a second time. Worse, for the dma_pool members it issued dma_pool_free(ha->s_dma_pool, ...) after s_dma_pool had already been destroyed and set to NULL at fail_s_dma_pool, dereferencing a NULL pool.  Clear each freed pointer (and its DMA handle) in the error labels so the subsequent qla2x00_mem_free() skips them.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-09-25 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-89877",
                        "url": "https://ubuntu.com/security/CVE-2026-89877",
                        "cve_description": "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 existing MMIO mapping error path to remove the device from saa7164_devlist and decrement the device count before returning.  Also release BAR0 if it was successfully requested but the BAR2 request fails.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-09-16 11:16:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-93239",
                        "url": "https://ubuntu.com/security/CVE-2026-93239",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  arm64: mm: Fix the lockless page-table walk in show_pte()  show_pte() walks page tables locklessly and can run with interrupts enabled. A concurrent teardown can free a table page while it is being walked. It can also clear a parent entry after show_pte() checked it; the regular pXd_offset() helpers then reread the cleared entry and can derive a bogus lower-level pointer and fault again.  Use the lockless offset helpers with the saved parent entries, as gup_fast() does, and pass the saved PMD to pte_offset_map().  For task page tables, arm64 selects MMU_GATHER_RCU_TABLE_FREE. Disable local interrupts around the walk to hold off RCU-deferred table frees and block the tlb_remove_table_sync_one() IPI until the walk is finished.  Place the IRQ guard after the header print. This does not make the output a consistent snapshot, but prevents the task page-table walk from dereferencing a released table page or deriving a pointer from a different parent value.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-09-24 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-90023",
                        "url": "https://ubuntu.com/security/CVE-2026-90023",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  usb: gadget: f_mass_storage: fix null pointer dereference in fsg_common_set_num_buffers()  Previously fsg_num_buffers_validate() was removed as it was not necessary due to Kconfig setting the limits for n from 2 to 256 with default as 2. However, setting the page content in such a way that kstrtou8() reflects n value as either 0 or 1 bypasses these restrictions leading to a null pointer dereference if n is 0. Fix this by adding a check for n < 2 and returning -EINVAL if n is either 0 or 1 consistent with Kconfig logic.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-09-16 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-93200",
                        "url": "https://ubuntu.com/security/CVE-2026-93200",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  i3c: master: Fix use-after-free of master->this  sysfs attribute callbacks for the master controller device dereference master->this.  However, master->this is freed in i3c_master_detach_free_devs() before the master device itself is released.  As a result, sysfs accesses can dereference a freed master->this pointer, leading to a use-after-free.  Keep master->this alive until i3c_masterdev_release(), which is called after the master device and its sysfs state are being torn down. Do not free master->this as part of the normal device detach path.  On the error path in i3c_master_set_info(), reset master->this and bus.cur_master to NULL before freeing the allocated device.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-09-17 17:18:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-93199",
                        "url": "https://ubuntu.com/security/CVE-2026-93199",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  i3c: master: Do not treat master device as a duplicate target  i3c_master_search_i3c_dev_duplicate() searches the bus for another I3C device with the same PID as the reference device.  The search can match master->this, causing the controller itself to be returned as a duplicate.  Since the controller is not a target device, it cannot be a duplicate of one.  Exclude master->this from matching so that the function only returns real duplicate target devices.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-09-17 17:18:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-89441",
                        "url": "https://ubuntu.com/security/CVE-2026-89441",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  mmc: via-sdmmc: cancel card-detect work on remove  Disabling the device interrupt and freeing the IRQ prevents new card-detect work from being queued, but carddet_work already queued by the handler can still run after via_sd_remove() returns. via_sdc_card_detect() recovers the host through container_of() and dereferences its MMIO base; once remove() returns the host can be freed, so that work would touch freed memory.  Cancel carddet_work after freeing the IRQ and before cancelling finish_bh_work, which the card-detect handler can also queue. carddet_work can re-enable the interrupt through via_reset_pcictrl(); mask it again afterwards.  This issue was found by an in-house static analysis tool and confirmed by manual code review.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-09-11 20:19:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-89465",
                        "url": "https://ubuntu.com/security/CVE-2026-89465",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  power: supply: rt9455: quiesce delayed work before teardown  The threaded IRQ handler can queue pwr_rdy_work, max_charging_time_work and batt_presence_work.  pwr_rdy_work and batt_presence_work can also queue max_charging_time_work, while batt_presence_work can requeue itself.  rt9455_remove() cancels max_charging_time_work before batt_presence_work.  The latter can therefore queue max_charging_time_work after it has already been cancelled:    rt9455_remove()                   workqueue     cancel pwr_rdy_work     cancel max_charging_time_work                                       batt_presence_work queues                                         max_charging_time_work     cancel batt_presence_work     return     devres frees rt9455_info                                       max_charging_time_work dereferences                                         rt9455_info  The IRQ also remains registered until devres cleanup and can queue more work after any of the cancellation calls.  If rt9455_hw_init() fails after the IRQ has been requested, probe returns without cancelling work that may already have been queued.  A pending callback can then access rt9455_info after it has been freed.  Register rt9455_cancel_all_delayed_works() through devm_add_action_or_reset() right after devm_power_supply_register(). devres invokes the action in reverse registration order, after the managed IRQ has been freed and before rt9455_info is released, so the delayed works are drained in both rt9455_remove() and the probe error path.  Cancel pwr_rdy_work and batt_presence_work before max_charging_time_work because both can queue the latter.  This issue was found by an in-house static analysis tool.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-09-11 20:19:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-93231",
                        "url": "https://ubuntu.com/security/CVE-2026-93231",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  lockd: fix swapped arguments in nlmsvc_match_ip()  When releasing locks by server IP address via /proc/fs/nfsd/unlock_ip, nlmsvc_unlock_all_by_ip() calls nlm_traverse_files() with the server sockaddr as the opaque @data argument:  \tnlm_traverse_files(server_addr, nlmsvc_match_ip, NULL);  The match callback is later invoked from nlm_traverse_locks() as:  \tmatch(lockhost, host);  where the first argument is the nlm_host that owns the lock, and the second argument is the @data that was originally passed down (here the server sockaddr).  This is the convention every other match callback relies on (nlmsvc_mark_host(), nlmsvc_same_host(), nlmsvc_is_client()): arg1 is the real nlm_host, arg2 is the caller-supplied reference value.  nlmsvc_match_ip() has had these two arguments reversed ever since the unlock-by-IP feature was introduced in commit 4373ea84c84d (\"lockd: unlock lockd locks associated with a given server ip\"):  \treturn rpc_cmp_addr(nlm_srcaddr(host), datap);  Here @host is actually the server sockaddr, so nlm_srcaddr(host) dereferences a struct sockaddr as a struct nlm_host and reads garbage at the offset of h_srcaddr; meanwhile @datap is actually the lock owner's nlm_host but is compared as a sockaddr.  As a result the comparison practically never matches and locks are not released for the requested IP.  Swap the arguments so the lock owner's source address is compared against the requested server address:  \treturn rpc_cmp_addr(nlm_srcaddr(datap), (struct sockaddr *)host);  [ cel: fix the misleading typedef parameter names too ]",
                        "cve_priority": "low",
                        "cve_public_date": "2026-09-24 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-89552",
                        "url": "https://ubuntu.com/security/CVE-2026-89552",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  params: fix charp corruption on allocation failure  param_set_charp() stores charp parameters in allocated memory after slab is available, and releases the previous value when the parameter is updated.  The previous value is released before the replacement allocation succeeds. If kmalloc_parameter() fails, the setter returns -ENOMEM with the parameter left as NULL.  Failing zswap's compressor update before zswap is initialized can later trigger:    BUG: kernel NULL pointer dereference, address: 0000000000000000   RIP: 0010:strcmp+0x10/0x30   Call Trace:     zswap_setup+0x3b1/0x490     zswap_enabled_param_set+0x5b/0xa0     param_attr_store+0x93/0xe0     module_attr_store+0x1c/0x30     kernfs_fop_write_iter+0x116/0x1f0  Allocate and copy the replacement first, then replace the parameter value only after allocation succeeds.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-09-11 20:19:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-89640",
                        "url": "https://ubuntu.com/security/CVE-2026-89640",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  cifs: fix loff_t underflow in cifs_remap_file_range() when len == 0  With len == 0 (clone to EOF), the effective length is computed as:      len = src_inode->i_size - off;  If off > i_size, this is a negative loff_t, corrupting the ByteCount in the FSCTL_DUPLICATE_EXTENTS_TO_FILE request and inverting the range in filemap_write_and_wait_range().  The existing off >= i_size check fires only after the ioctl has already been sent.  Snapshot i_size_read() once for both the bounds check and the length calculation, eliminating the TOCTOU and 32-bit torn-read risk.  Reject off > src_size with -EINVAL.  Treat off == src_size as a no-op, consistent with __generic_remap_file_range_prep().",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-09-11 20:19:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-89672",
                        "url": "https://ubuntu.com/security/CVE-2026-89672",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  nfsd: gate nfs2 setacl by argp->mask  The NFSACL v2 SETACL path shares the decoder convention used by its v3 sibling: nfsaclsvc_decode_setaclargs() fills in argp->acl_access only when NFS_ACL is set in the request mask and argp->acl_default only when NFS_DFACL is set, leaving the other pointer NULL because the argument buffer is zeroed up to pc_argzero before decode.  nfsacld_proc_setacl() then hands both pointers to set_posix_acl() unconditionally. set_posix_acl(idmap, dentry, type, NULL) is the VFS \"remove this ACL type\" operation, so an omitted arm is indistinguishable from an explicit request to delete that ACL. A SETACL carrying only NFS_ACL silently strips the directory's default ACL; mask=0 strips both.  This is the same defect just fixed in nfsd3_proc_setacl(); apply the same remedy. Gate each set_posix_acl() call on its mask bit and initialize error to 0 so that a request with neither bit set leaves the on-disk ACLs untouched and returns success. The out_drop_lock path and the unconditional posix_acl_release() in nfsaclsvc_release_setacl() already tolerate the skipped arms.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-09-11 20:19:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-89685",
                        "url": "https://ubuntu.com/security/CVE-2026-89685",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  nfsd: fix clock domain mismatch in clients_still_reclaiming()  clients_still_reclaiming() computes a deadline from nn->boot_time (CLOCK_REALTIME, ~1.7 billion) but compares it against ktime_get_boottime_seconds() (CLOCK_BOOTTIME, seconds since boot). The comparison is always false — it would take ~54 years of uptime for BOOTTIME to exceed the REALTIME-derived deadline.  This means any client can hold the server in grace indefinitely by sending CLAIM_PREVIOUS OPEN requests, blocking all non-reclaim operations for all other clients.  Add boot_time_bt (CLOCK_BOOTTIME) alongside the existing boot_time and use it for the deadline computation. boot_time (CLOCK_REALTIME) is preserved for its cl_boot clientid-nonce role.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-09-11 20:19:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-89707",
                        "url": "https://ubuntu.com/security/CVE-2026-89707",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  nfsd: release path refs on follow_down() error  nfsd_cross_mnt() initializes a local struct path with mntget() and dget() before calling follow_down(). On a negative return the error arm jumps to out without releasing those references:      err = follow_down(&path, follow_flags);     if (err < 0)             goto out;  follow_down() never drops the caller's entry-time refs on any error sub-case; for example a pre-cross d_manage() failure leaves path untouched, so the mntget()/dget() taken on entry survive the call.  Every other early-exit arm in nfsd_cross_mnt() (other-namespace return, IS_ERR(exp2), and the success tail after the swap) already calls path_put(&path); the err < 0 arm is the lone omission. The leak inflates mnt_count and d_count on each failed cross-mount, blocking umount and pinning dentries against the shrinker, and is reachable by any authenticated NFS client through nfsd_lookup_dentry or the NFSv4 READDIR encode path.  Fix by calling path_put(&path) before the goto out in the err < 0 arm so the entry-time refs are released on all follow_down() error returns.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-09-11 20:19:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-89719",
                        "url": "https://ubuntu.com/security/CVE-2026-89719",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  zram: fix out-of-bounds access in read_block_state()  read_block_state() calculates nr_pages before taking dev_lock.  If the device is reset and reinitialized with a smaller disksize before lock acquisition, nr_pages still describes the old table.  The subsequent loop can then call slot_lock() past the end of the newly allocated table.  Read disksize after acquiring dev_lock and checking that the device is initialized.  The read lock then keeps the table and its bound stable for the duration of the scan.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-09-11 20:20:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-89763",
                        "url": "https://ubuntu.com/security/CVE-2026-89763",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  KEYS: trusted: Fix TPM teardown ordering  trusted_tpm_exit() drops the TPM chip reference and frees the digest array before unregistering the trusted key type. key_type_lookup() holds key_types_sem for reading until the key operation finishes, while unregister_key_type() takes it for writing. It therefore provides the synchronization point that must precede backend teardown.  The current order permits this interleaving:    CPU 0                              CPU 1   trusted_tpm_exit()                 key_type_lookup(\"trusted\")     put_device(&chip->dev)             trusted_tpm_seal()     kfree(digests)                       pcrlock()     unregister_key_type()                  tpm_pcr_extend(..., digests)  CPU 1 can consequently dereference the freed digest array. The chip can also be released before callbacks stop using it.  KASAN reported:    BUG: KASAN: slab-use-after-free in tpm_pcr_extend+0x1f0/0x200   Read of size 2 at addr ffff88810872d000 by task poc/89   Call Trace:     tpm_pcr_extend+0x1f0/0x200     pcrlock+0x42/0x70 [trusted]     trusted_tpm_seal+0x1b6/0x570 [trusted]     trusted_instantiate+0x293/0x340 [trusted]     __key_instantiate_and_link+0xb2/0x2b0     __key_create_or_update+0x61e/0xb50     __do_sys_add_key+0x1b8/0x310   Allocated by task 88:     __kmalloc_noprof+0x1a7/0x490     do_one_initcall+0xa1/0x390     do_init_module+0x2df/0x840   Freed by task 90:     kfree+0x131/0x3c0     trusted_tpm_exit+0x59/0xa0 [trusted]     __do_sys_delete_module+0x346/0x510  Move unregister_key_type() before releasing either resource. This stops new lookups and waits for in-flight key operations to finish before the backend state is destroyed.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-09-11 20:20:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-80851",
                        "url": "https://ubuntu.com/security/CVE-2026-80851",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  gtp: serialize PDP context updates  PDP contexts can be deleted through GTP_CMD_DELPDP or while the GTP network device is being unregistered. The latter is serialized by RTNL, but the generic-netlink delete path only holds RCU.  Running both paths concurrently can therefore make both paths delete the same PDP context. The issue was found through static analysis and reproduced on a KASAN-enabled kernel by a simple two-thread program racing GTP_CMD_DELPDP against RTM_DELLINK:    Oops: general protection fault, probably for non-canonical address   KASAN: maybe wild-memory-access in range          [0xdead000000000120-0xdead000000000127]   RIP: gtp_genl_del_pdp+0x1c1/0x420 [gtp]   RBP: dead000000000122  The second deletion dereferenced the poisoned hlist pprev pointer.  Serialize gtp_pdp_add(), gtp_genl_del_pdp(), and gtp_dellink() with a shared mutex. Keep the mutex held until the final use of a PDP context in the NEWPDP path, and keep the RCU read-side section around the complete PDP context use in the DELPDP path.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-09-04 16:18:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-80861",
                        "url": "https://ubuntu.com/security/CVE-2026-80861",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  usb: xhci: bail out of setup if the controller is inaccessible  xhci_gen_setup() locates the operational registers using the capability length read from the very first register:  \txhci->op_regs = hcd->regs + \t\tHC_LENGTH(readl(&xhci->cap_regs->hc_capbase));  If the controller is dead or has dropped off the bus, that read returns ~0, HC_LENGTH() truncates it to 0xff, and op_regs ends up 0xff bytes past the page-aligned MMIO base, i.e. unaligned. The first access through it, xhci_halt() -> xhci_handshake() reading op_regs->status, is then an unaligned readl() on device memory. arm64 faults on unaligned device accesses, so instead of xhci_handshake() catching the all-ones value and returning -ENODEV, setup oopses:    xhci-pci-renesas 0005:08:00.0: Unable to change power state from D3cold to D0, device inaccessible   xhci-pci-renesas 0005:08:00.0: xHCI Host Controller   xhci-pci-renesas 0005:08:00.0: new USB bus registered, assigned bus number 1   Unable to handle kernel paging request at virtual address ffff80030a770103     ESR = 0x0000000096000021     FSC = 0x21: alignment fault   Internal error: Oops: 0000000096000021 [#1]  SMP   pc : xhci_halt [xhci_hcd]   Call trace:    xhci_halt    xhci_gen_setup    xhci_pci_setup    usb_add_hcd    usb_hcd_pci_probe    xhci_pci_common_probe    xhci_pci_renesas_probe  This was hit with a Renesas uPD720201 that failed to power up (\"Unable to change power state from D3cold to D0, device inaccessible\") yet still reached the HCD probe path.  Read the capability register once, and if it reads back the all-ones value (as xhci_handshake() and xhci_reset() already test for), abort setup with -ENODEV before op_regs is derived from it. Reading it once also avoids re-reading a register that may change under a concurrent hot-removal.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-09-04 16:18:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98377",
                        "url": "https://ubuntu.com/security/CVE-2026-98377",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  vlan: require the MAC header to be present in __vlan_insert_inner_tag()  __vlan_insert_inner_tag() only guarantees head room via skb_cow_head(), never that mac_len bytes of MAC header are present.  Its ETH_HLEN wrappers - __vlan_insert_tag() under skb_vlan_push(), and vlan_insert_tag() under validate_xmit_vlan() on the generic transmit path - therefore rewrite the first 16 bytes at skb->data: a 12-byte memmove plus two 2-byte stores at +12 and +14.  No caller supplies the bound, while the pop helpers use skb_ensure_writable()/pskb_may_pull().  An IFF_TUN device has hard_header_len == 0, so packet_snd() accepts a one-byte AF_PACKET/SOCK_RAW frame.  The first vlan push only sets a hwaccel tag; the next - clsact \"action vlan push\" or bpf_skb_vlan_push() - enters the helper with skb->len still 1.  The head comes from skbuff_small_head without __GFP_ZERO, so each push drags bytes from beyond skb->tail into the frame.  After three the one-byte send leaves as 13 bytes carrying 11 bytes of uninitialised slab:    0000: 5a b3 62 12 80 88 ff ff 00 b3 62 12 81            `------------------------------'   only 0x5a was sent; the rest is slab, here the top 56 bits of a   linear-map address  Require the MAC header the helper rewrites to be present, so such a frame is dropped rather than transmitted.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-09 08:16:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98170",
                        "url": "https://ubuntu.com/security/CVE-2026-98170",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  smb: client: fix OOB struct field reads in move_smb2_ea_to_cifs()  In move_smb2_ea_to_cifs(), the while (src_size > 0) loop condition is insufficient. It allows iteration to continue even if the remaining src_size is too small to contain a complete smb2_ea_info structure. Consequently, reads of ea_name_length and ea_value_length can occur out-of-bounds.  Fix this by ensuring src_size >= sizeof(*src) before attempting to read any structure fields. Additionally, reject any next_entry_offset that is smaller than sizeof(*src) or that would advance the pointer beyond the available buffer.  Note that for calls where the server returns a malformed EA list, the error returned to userspace changes from -ENODATA (getxattr) or -ERANGE (listxattr) to -EIO. This correctly signals a server protocol error rather than misleadingly indicating \"attribute not present\" or \"output buffer too small\".",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-06 09:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98171",
                        "url": "https://ubuntu.com/security/CVE-2026-98171",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  smb: client: fix next_buffer UAF and NextCommand bounds in compound PDUs  Fix several related bounds checking and pointer lifecycle issues in receive_encrypted_standard()'s handling of compound encrypted frames:  - Clear next_buffer after assigning it to server->bigbuf. A stale   next_buffer pointer can lead to a use-after-free on subsequent   error paths. - Update pdu_length to the decrypted plaintext size (buf_size). Using   the pre-decryption length allows NextCommand to point into stale   ciphertext residue. - Reject next_cmd values smaller than MID_HEADER_SIZE(server). - Fix an integer overflow in the upper bound check by verifying   pdu_length - next_cmd < MID_HEADER_SIZE(server), ensuring the   trailing slice is large enough for a header.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-06 09:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98169",
                        "url": "https://ubuntu.com/security/CVE-2026-98169",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  smb: client: fix potential OOB read in smb3_enum_snapshots()  If snapshot_array_size is smaller than GMT_TOKEN_SIZE, smb3_enum_snapshots() sets ret_data_len to sizeof(struct smb_snapshot_array) without verifying the actual length of the server's reply.  Because SMB2_ioctl() places no lower bound on the server-supplied OutputCount and allocates retbuf to exactly that length, a short reply results in ret_data_len exceeding the size of retbuf. The subsequent copy_to_user() then reads past the end of retbuf, leaking adjacent slab memory to userspace.  The subsequent clamp check is ineffective as it only reduces ret_data_len.  Fix this by rejecting replies shorter than sizeof(struct smb_snapshot_array) with -EIO. Note that the bound is set to the 12-byte struct size rather than the 16-byte MIN_SNAPSHOT_ARRAY_SIZE defined in MS-SMB2 3.3.5.15.1, because 12 bytes is exactly what copy_to_user() attempts to read.",
                        "cve_priority": "negligible",
                        "cve_public_date": "2026-10-06 09:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98193",
                        "url": "https://ubuntu.com/security/CVE-2026-98193",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: libipw: reject TKIP frames without a full MIC  libipw_michael_mic_verify() assumes that an skb contains an eight-byte Michael MIC. A short TKIP frame makes the unsigned payload length wrap, causing michael_mic() to read past the skb.  Check that the MIC is present before verifying it, and use the existing MICHAEL_MIC_LEN constant for all MIC lengths in the verifier.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-06 09:18:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-97555",
                        "url": "https://ubuntu.com/security/CVE-2026-97555",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  smb: client: fix heap overflow in DACL owner/group rewrite  When id_mode_to_cifs_acl rewrites an existing DACL, it allocates a buffer sized according to the on-disk DACL length reported by dacl_ptr->size. However, replace_sids_and_copy_aces may rewrite each ACE with a new owner/group SID obtained from the cifs.idmap upcall. Those SIDs can have up to SID_MAX_SUB_AUTHORITIES (15) sub-authorities, making each ACE up to 76 bytes (sizeof(struct smb_ace)).  If the original DACL contains short SIDs (e.g., 1 sub-authority) while the replacement SIDs are long, the rewritten ACEs overflow the allocation.  Fix this by always budgeting for worst-case SID expansion: allocate sizeof(struct smb_acl) plus num_aces * sizeof(struct smb_ace), which covers the smb_acl header and room for every ACE at maximum SID size. This replaces the previous split logic that used dacl_ptr->size for cifsacl mounts but num_aces * sizeof(struct smb_ace) for mode_from_sid mounts: both paths can trigger the same rewrite and need the same headroom.  KASAN reports this as:   BUG: KASAN: slab-out-of-bounds in build_sec_desc+0x1e8a/0x2680 [cifs]   Write of size 4 at addr ffff8881a5e25374 by task chown/5298   ...   The buggy address is located 0 bytes to the right of    allocated 884-byte region [ffff8881a5e25000, ffff8881a5e25374)",
                        "cve_priority": "high",
                        "cve_public_date": "2026-09-25 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-97557",
                        "url": "https://ubuntu.com/security/CVE-2026-97557",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  smb: client: avoid leaking refcount in cifs_queue_oplock_break()  cifs_queue_oplock_break() unconditionally takes a reference on the target file before queueing cifs_oplock_break(). Only that work item decreases the reference counter again.  If another oplock break arrives while that work is still queued, queue_work() will return false and not queue this second work item. As a result, we will never reach the point to drop the file reference again and are leaking this reference. This can be triggered when interacting with a slow-responding server.  As a result, later unmount operations for this file system will fail with    BUG: Dentry ... still in use (1) [unmount of cifs cifs]   VFS: Busy inodes after unmount of cifs (cifs)   kernel BUG at fs/super.c:777!  Fix this by only incrementing the reference count if the work has been queued successfully. Taking it after queue_work() is safe because all three callers hold tcon->open_file_lock across the call and _cifsFileInfo_put() decrements under that same lock, so a worker that starts the handler in the window cannot drop the reference before it has been taken.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-09-25 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-97564",
                        "url": "https://ubuntu.com/security/CVE-2026-97564",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  smb: client: reject userspace cifs.idmap descriptions  cifs.idmap key descriptions carry authority-bearing fields (owner and group SIDs and uid/gid values in \"os:\"/\"gs:\"/\"oi:\"/\"gi:\" form) that the cifs.idmap upcall helper treats as kernel-originating inputs.  Unlike its sibling cifs.spnego, the cifs.idmap key type has no vet_description hook, so userspace can create keys of this type through request_key(2)/add_key(2) and supply those fields without CIFS origin. A request_key(2) call with a non-NULL callout then drives a root usermodehelper upcall (/sbin/request-key -> cifs.idmap) that consumes the unvetted description in root context.  Only accept cifs.idmap descriptions while CIFS is using its private root_cred to request the key.  id_to_sid()/sid_to_id() already run under override_creds(root_cred), so the kernel-originated path is unaffected.  This mirrors commit 3da1fdf4efbc (\"smb: client: reject userspace cifs.spnego descriptions\"), which applied the same restriction to cifs.spnego.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-09-25 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-97615",
                        "url": "https://ubuntu.com/security/CVE-2026-97615",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net: bridge: use option bits for CFM/MRP frame handlers  CFM and MRP register a global br_frame_type whose hlist_node is linked into the per-bridge frame_type_list when the first MEP/MRP instance is created. Enabling the protocol on multiple bridges therefore inserts the same node into multiple lists. Unregistering it on one bridge then corrupts list state belonging to another.  These handlers can only be installed once per bridge, and they are uncommon. Track their per-bridge enable state with net_bridge option bits, which already live on the Rx hot cache line, and dispatch the matching handler directly from the receive path. Check both bits together first as an unlikely case.  Remove the generic frame_type_list and br_frame_type helpers, which have had no other users since CFM and MRP were added. That shrinks struct net_bridge by 8 bytes and drops the list walk from the fast path. When neither protocol is compiled in, BR_CFM_MRP_OPTS is 0 and the compiler prunes the branch.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-09-25 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-97901",
                        "url": "https://ubuntu.com/security/CVE-2026-97901",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  genetlink: pin family module during policy dump  The generic netlink controller's policy dump keeps pointers to the target family's operation and policy tables in its callback state.  A dump may be split across multiple skbs and remain pending after the initial request.  Netlink pins the module which owns the dump callback, but in this case that is the controller's owner rather than the target family's owner.  The target family can consequently be unregistered and its module unloaded while a policy dump is pending.  Advancing the dump then dereferences policy memory from the unloaded module.  Take a reference to the target family's module when the dump starts. Drop it from the error and done paths.  This matches the lifetime for which the dump context retains the family and policy pointers.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-09-25 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-97908",
                        "url": "https://ubuntu.com/security/CVE-2026-97908",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  Bluetooth: btqcomsmd: destroy RPMsg endpoints before freeing hci_dev  The command and ACL RPMsg endpoints store struct btqcomsmd as their callback private data. The receive callbacks dereference btq->hdev without taking an hci_dev reference.  The current teardown order frees the hci_dev before destroying the RPMsg endpoints in both the hci_register_dev() error path and the driver remove path. If WCNSS delivers data in that window, the endpoint callback can run with an already freed hci_dev and pass it to the Bluetooth core.  For qcom_smd endpoints, rpmsg_destroy_ept() closes the channel and clears the callback under the channel recv_lock. The receive path holds the same lock while invoking the callback, so destroying the endpoints first both prevents new callbacks and serializes with any callback already running.  Destroy the command and ACL endpoints before hci_free_dev(). Keep hci_unregister_dev() first during remove so the HCI core stops issuing operations before the transport endpoints are shut down. In the full registration-error cleanup path, return directly after freeing the hci_dev to avoid falling through to the partial-construction labels and destroying the endpoints twice.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-09-25 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-97925",
                        "url": "https://ubuntu.com/security/CVE-2026-97925",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  tick/broadcast: Plug clockevents replacement race  朱恺乾 reported and decoded the following race condition when a broadcast device is replaced:  CPUA\t\t\t\t\tCPUB  __tick_broadcast_oneshot_control()    bc = tick_broadcast_device.evtdev; \t\t\t\t\ttick_install_broadcast_device(dev)         \t\t\t\tclockevents_exchange_device(cur, dev) \t\t\t\t\t   shutdown(cur); \t\t\t\t\t   detach(cur); \t\t\t\t\t   cur->handler = noop; \t\t\t\t\t   tick_broadcast_device.evtdev = dev;    tick_broadcast_set_event(bc, next_event); <- FAIL: arms a detached device.  If the original broadcast device has a restricted interrupt affinity mask and the last CPU in that mask goes offline then the BUG() in tick_cleanup_dead_cpu() triggers because the clockevent device is not in detached state.  The reason for this is that tick_install_broadcast_device() is not serialized vs. tick broadcast operations.  The obvious cure is to serialize tick_install_broadcast_device() with tick_broadcast_lock against a concurrent tick broadcast operation.  That requires to split clockevents_exchange_device() into two parts, one which does the exchange, shutdown and detach operation and the other which drops the module reference count. This is required because the module reference cannot be dropped while holding tick_broadcast_lock.  Let clockevents_exchange_device() do both operations as before, but let the broadcast device code take the two step approach and do the device exchange under tick_broadcast_lock and drop the module reference count after releasing it.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-09-25 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-93285",
                        "url": "https://ubuntu.com/security/CVE-2026-93285",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  f2fs: embed f2fs_gc_kthread in f2fs_sb_info  Instead of allocating f2fs_gc_kthread dynamically, embed it in f2fs_sb_info. This simplifies lifetime management and prepares for fixing race conditions during teardown.  - __sbi_store\t\t\t- remount|shutdown \t\t\t\t - f2fs_stop_gc_thread  - access sbi->gc_thread \t\t\t\t  - sbi->gc_thread = NULL  - access sbi->gc_thread->f2fs_gc_task",
                        "cve_priority": "low",
                        "cve_public_date": "2026-09-24 17:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-97529",
                        "url": "https://ubuntu.com/security/CVE-2026-97529",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  scsi: qla2xxx: Validate BSG request_len before reading vendor_cmd[]  The FC BSG transport allocates job->request via memdup_user() using the exact user-supplied request_len. For FC_BSG_HST_VENDOR, fc_bsg_host_dispatch() only guarantees request_len covers msgcode and vendor_id; it does not account for the vendor_cmd[] flexible array.  qla2xxx then reads the command selector vendor_cmd[0] and, in several sub-handlers, vendor_cmd[1]/[2] or structures overlaid on the vendor command area without verifying request_len. A caller holding CAP_SYS_RAWIO can submit a short request whose vendor_id matches the host, triggering out-of-bounds heap reads (KASAN-detectable, and able to mis-select a command or panic).  Add a central guard in qla2x00_process_vendor_specific() so the selector is always in bounds, restrict the early vendor_cmd[0] read in qla24xx_bsg_request() to sufficiently long vendor messages, and add request_len checks to the sub-handlers that read further: qla24xx_proc_fcp_prio_cfg_cmd(), qla2x00_process_loopback(), qla84xx_reset(), qla84xx_updatefw(), qla2x00_read_optrom(), qla2x00_update_optrom(), qlafx00_mgmt_cmd() and qla28xx_validate_flash_image().",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-09-25 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-97536",
                        "url": "https://ubuntu.com/security/CVE-2026-97536",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  scsi: qla2xxx: Fix use-after-free of qpair work on queue teardown  The response queue MSI-X handler qla2xxx_msix_rsp_q() schedules qla_do_work() via queue_work(ha->wq, &qpair->q_work). qla_do_work() dereferences the qpair (vha, rsp) and takes qpair->qp_lock.  During teardown, qla2xxx_delete_qpair() deletes the response queue, which calls free_irq() in qla25xx_free_rsp_que(), and then frees the queue and the qpair. free_irq() waits for running hardirq handlers but does not cancel work already placed on ha->wq. A still-pending q_work then runs qla_do_work() against the freed qpair and response queue, causing a use-after-free. This is especially likely during full adapter teardown, where destroy_workqueue(ha->wq) forces pending work to run after the queue pairs have been freed.  Flush the work item with cancel_work_sync() in qla25xx_free_rsp_que() after free_irq() has released the interrupt (so no new work can be queued) and before the response queue and qpair memory are freed (so the flushed handler still sees valid memory). Guard on rsp->qpair and ha->wq to match the INIT_WORK() condition and avoid operating on an uninitialized work_struct.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-09-25 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-97537",
                        "url": "https://ubuntu.com/security/CVE-2026-97537",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  scsi: qla2xxx: Fix queue teardown NULL dma_free and bitmap locking  qla25xx_free_req_que() and qla25xx_free_rsp_que() have two pre-existing bugs exposed on the error path of qla25xx_create_{req,rsp}_que():   1. When dma_alloc_coherent() fails during queue creation, the error     path calls the free function with req->ring / rsp->ring still NULL     (from kzalloc).  The unconditional dma_free_coherent() with a NULL     cpu_addr is undefined behavior and can panic.   2. The free functions clear req_qid_map / rsp_qid_map under vport_lock,     but the create functions protect the same bitmaps with mq_lock.     This provides no mutual exclusion.  Additionally, the create error     path clears the bit and releases mq_lock before calling the free     function, creating a window where another thread can allocate the     same que_id and have its ha->req_q_map entry clobbered by the     subsequent lockless NULL assignment in the free function.  Fix by:   - Guarding dma_free_coherent() with a NULL check on the ring pointer.   - Using mq_lock (the lock held by all creators) in the free functions    to atomically NULL the map entry and clear the bitmap bit.   - Removing the now-redundant clear_bit blocks from the create error    paths since the free functions handle it atomically.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-09-25 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-89859",
                        "url": "https://ubuntu.com/security/CVE-2026-89859",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  scsi: qla2xxx: Zero dport diagnostics buffer to avoid info leak  qla2x00_do_dport_diagnostics() allocates the qla_dport_diag response buffer with kmalloc_obj() (non-zeroing) and, on success, copies the full sizeof(*dd) back to user space via sg_copy_from_buffer(). The inbound sg_copy_to_buffer() only fills as many bytes as the user request payload provides, and qla26xx_dport_diagnostics() zeroes only dd->buf. The options and unused[] fields are therefore copied out uninitialized, leaking kernel heap contents to user space.  Allocate with kzalloc_obj(), matching qla2x00_do_dport_diagnostics_v2().",
                        "cve_priority": "low",
                        "cve_public_date": "2026-09-16 11:16:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-89921",
                        "url": "https://ubuntu.com/security/CVE-2026-89921",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  KVM: s390: Zero initialize data structures for inject_pfault_token  __kvm_inject_pfault_token() only sets .type and .u.ext.ext_params2 of the on-stack struct kvm_s390_irq but the full ext substructure is copied into the cpu local variable on inject. ext_params and pad contain stale stack values.  Interrupt delivery only uses ext_params2, so nothing leaks to the guest, but a host user can use the migration ioctls to get to the data.  Fix by zero-initializing the irq struct. Do the same for the inti data structure.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-09-16 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-89972",
                        "url": "https://ubuntu.com/security/CVE-2026-89972",
                        "cve_description": "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 reference to ns when kfree(ns) runs.  The normal removal path in nvme_ns_remove() correctly calls synchronize_srcu(&ns->head->srcu) after list_del_rcu() to wait for in-progress readers. Add the same grace period in the error path.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-09-16 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-89988",
                        "url": "https://ubuntu.com/security/CVE-2026-89988",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  kprobes: Protect kprobe_blacklist with RCU  __within_kprobe_blacklist() traverses kprobe_blacklist without holding kprobe_mutex. When a module is unloaded, kprobe_remove_area_blacklist() removes blacklist entries and immediately frees them with kfree(). A concurrent call to within_kprobe_blacklist() can therefore dereference freed memory.  Furthermore, within_kprobe_blacklist() can be called in atomic or non-preemptible contexts where the sleeping kprobe_mutex cannot be taken.  Protect kprobe_blacklist with RCU. Use guard(rcu)() and list_for_each_entry_rcu() for traversal, list_add_tail_rcu() for insertions, list_del_rcu() for deletions, and kfree_rcu() to reclaim entries safely after a grace period.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-09-16 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-90002",
                        "url": "https://ubuntu.com/security/CVE-2026-90002",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ftrace: Take trace_array reference before accessing its ftrace_ops  The trace instance files set_ftrace_filter and set_ftrace_notrace was updated to work with specific trace instances (trace_arrays). The issue is that when these files are opened, there is a small race window where it will use the ftrace_ops from the inode->private pointer to get a reference to the trace_array and then take its reference. The problem is that the ftrace_ops itself could be freed. If the rmdir on the instance happens at the same time the set_ftrace_filter file is opened, the rmdir could have also freed the ftrace_ops and referencing it will cause a use-after-free bug and crash the kernel.  Instead, pass in the trace_array as the file private data (NULL for the top level instance), and then pass both the trace_array and the ftrace_ops to the ftrace_regex_open() function. If the trace_array is NULL, then it just uses the ftrace_ops without the need to take its reference (like normal). If the ftrace_ops is NULL, that is only the case for the top level instance and the global_ops can be used.  This allows the trace_array to have its reference incremented before touching the ftrace_ops that could also be freed when the instance is.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-09-16 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-90016",
                        "url": "https://ubuntu.com/security/CVE-2026-90016",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  staging: rtl8723bs: fix OOB read in rtw_restruct_wmm_ie()  rtw_restruct_wmm_ie() scans in_ie for a WMM IE with:  \twhile (i < in_len) { \t\t... \t\tif (i + 5 < in_len && in_ie[i] == 0xDD && ...) { \t\t\t... \t\t\tbreak; \t\t} \t\ti += (in_ie[i + 1] + 2); /* to the next IE element */ \t}  When the \"i + 5 < in_len\" match check fails simply because i is within 5 bytes of the end of the buffer (i.e. no WMM IE was found near the tail of in_ie), execution falls through to \"i += (in_ie[i + 1] + 2)\", which reads in_ie[i + 1]. If i == in_len - 1 at that point, this is a 1-byte out-of-bounds read of an attacker-influenced IE buffer built from association/scan data.  Commit a75281626fc8f (\"staging: rtl8723bs: fix potential out-of-bounds read in rtw_restruct_wmm_ie\") added the \"i + 5 < in_len\" guard to the match condition itself, but did not add an equivalent guard before the fallthrough advance, so the same class of OOB read remained reachable through the non-matching path.  Add an explicit bounds check before advancing to the next IE.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-09-16 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-90029",
                        "url": "https://ubuntu.com/security/CVE-2026-90029",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  usb: storage: realtek_cr: fix use-after-free on disconnect  realtek_cr_destructor() calls timer_delete() before the chip containing the timer is freed. The timer callback may still be running and can rearm itself, resulting in a use-after-free.  Use timer_shutdown_sync() to wait for the callback and prevent further rearming. Do this unconditionally because ss_en may be changed after the timer is armed.  Move timer_setup() into init_realtek_cr() so the timer is initialized before any failure path can invoke the destructor.  Found by static analysis.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-09-16 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-80947",
                        "url": "https://ubuntu.com/security/CVE-2026-80947",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: rtl8xxxu: fix use-after-free from rx_urb_wq on stop  rtl8xxxu arms rx_urb_wq from the RX completion path: rtl8xxxu_rx_complete() hands the URB to rtl8xxxu_queue_rx_urb(), which queues it on rx_urb_pending_list and, once the list grows past RTL8XXXU_RX_URB_PENDING_WATER, schedules rx_urb_wq.  The worker rtl8xxxu_rx_urb_work() drains rx_urb_pending_list, recovers priv through container_of, and resubmits each URB through rtl8xxxu_submit_rx_urb(), which anchors it on rx_anchor and dereferences priv->udev.  rtl8xxxu_stop() cancels the sibling work items (c2hcmd_work, ra_watchdog, update_beacon_work) but never cancels rx_urb_wq, so a worker armed during the last burst of RX traffic can run rtl8xxxu_rx_urb_work() after rtl8xxxu_disconnect() has called ieee80211_free_hw(), which frees priv, producing a use-after-free.  The window opens under active RX traffic (pending count above the watermark) followed by a disconnect.  There are two teardown races to close:    * rtl8xxxu_queue_rx_urb() decided whether to enqueue under rx_urb_lock     but called schedule_work() after dropping the lock.  A completion     that observed shutdown == false and released the lock could then call     schedule_work() after rtl8xxxu_stop() had set shutdown and     cancel_work_sync() had already returned, arming the worker to run     after the teardown.  Move schedule_work() under the same !shutdown     branch so the arming decision is atomic with the shutdown check.    * rtl8xxxu_rx_urb_work() anchors every URB it drained back onto     rx_anchor through rtl8xxxu_submit_rx_urb().  A worker still running     when usb_kill_anchored_urbs(&priv->rx_anchor) returned would submit a     URB that escaped the kill.  In rtl8xxxu_stop(), call     cancel_work_sync(&priv->rx_urb_wq) before the kill so the worker is     drained first.  After priv->shutdown is set under rx_urb_lock, completions can no longer queue rx_urb_wq. cancel_work_sync() then drains the last queued or running worker, and the following usb_kill_anchored_urbs() kills the URBs it may have submitted.  rtl8xxxu_disconnect() is covered because ieee80211_unregister_hw() guarantees .stop() runs for a live interface before ieee80211_free_hw() frees priv.  The probe error path needs no cancel: rx_urb_wq is INIT_WORK()'d there but cannot have been scheduled, since no URB is submitted before ieee80211_register_hw() succeeds.  This bug was found by static analysis.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-09-11 20:19:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-89481",
                        "url": "https://ubuntu.com/security/CVE-2026-89481",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  nvme-tcp: fix host memory disclosure on R2T for a read command  nvme_tcp_handle_r2t() does not check the direction of the request the R2T refers to. A malicious controller can send an R2T for a READ and the host will answer it: nvme_tcp_setup_h2c_data_pdu() builds the H2CData header and nvme_tcp_try_send_data() sends the request's data buffer. That buffer is the READ destination, so its contents go to the controller.  The command then completes normally and nothing is logged.  Against a test controller that answers every READ with an R2T, a 4096 byte buffered read returned all 4096 bytes, split over two R2Ts. The pages contained stale kernel data, including an array of struct page pointers.  Reject an R2T for a request that is not a write.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-09-11 20:19:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-89492",
                        "url": "https://ubuntu.com/security/CVE-2026-89492",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ocfs2: validate directory-index entry counts when reading metadata  ocfs2_validate_dx_leaf() and ocfs2_validate_dx_root() check the ECC and signature of an indexed-directory block before it reaches higher-level callers, but neither validator bounds the ocfs2_dx_entry_list counts against the capacity of the block that holds them.  ocfs2_dx_dir_search() then walks  \tfor (i = 0; i < le16_to_cpu(entry_list->de_num_used); i++) \t\tdx_entry = &entry_list->de_entries[i];  over de_num_used entries with no bounds check.  entry_list is either dx_leaf->dl_list (from ocfs2_read_dx_leaf) or, for an inline root, dx_root->dr_entries.  A crafted on-disk image can set de_num_used (and de_count, which is the __counted_by_le() bound of de_entries) to 0xffff and make the walk read far past the end of the 4KB metadata block, giving a slab out-of-bounds read reachable from any path lookup, stat() or open() on an indexed directory once the image is mounted.  Commit 775c17386a6f (\"ocfs2: validate dx_root extent list fields during block read\") already bounds dr_list for the non-inline dx_root, but left the inline dr_entries path and the dx_leaf dl_list unchecked.  Add the same read-time validation for both entry lists: de_count must equal the capacity of the block (ocfs2_dx_entries_per_leaf()/per_root()) and de_num_used must not exceed de_count, rejecting corrupted metadata with -EFSCORRUPTED before ocfs2_dx_dir_search() can walk an out-of-range entry array.  de_count is always written as exactly the block capacity when a leaf or inline root is formatted, so the equality check does not reject any valid image.  Found by 0sec automated security-research tooling (https://0sec.ai).",
                        "cve_priority": "high",
                        "cve_public_date": "2026-09-11 20:19:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-89553",
                        "url": "https://ubuntu.com/security/CVE-2026-89553",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  nouveau/gem: reserve the bo in the info ioctl around the vma lookup  In the non-uvmm path, there could be a race between the info lookup finding the vma, and the gem close path closing the vma leading to a use-after-free.  Spotted with the help of Opus 4.6.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-09-11 20:19:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-89625",
                        "url": "https://ubuntu.com/security/CVE-2026-89625",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  HID: sony: fix UAF of ghl_poke_timer / ghl_urb at driver unbind  For GHL (Guitar Hero Live) dongles, sony_probe() arms a periodic timer: ghl_magic_poke() (the timer callback) submits sc->ghl_urb, and the URB completion ghl_magic_poke_cb() re-arms the timer with mod_timer().  sony_remove() drained the timer with timer_delete_sync() and then freed the URB with usb_free_urb():  \ttimer_delete_sync(&sc->ghl_poke_timer); \tusb_free_urb(sc->ghl_urb);  timer_delete_sync() does not block re-arming, and while the URB is in flight the timer is not pending, so the sync delete is a no-op. A URB completion that runs after the delete re-arms the timer, and usb_free_urb() only drops a reference -- it does not kill an in-flight URB. sc is allocated with devm_kzalloc() and freed once sony_remove() returns, so the re-armed ghl_poke_timer (embedded in sc) then fires on freed memory, a use-after-free from timer softirq. This is a disconnect/rmmod race.  Poison the URB first, then shut the timer down, before freeing the URB. usb_poison_urb() kills any in-flight URB and permanently rejects further submissions, so a poke timer that is still pending cannot re-submit the URB from ghl_magic_poke() in the window before timer_shutdown_sync() runs. usb_kill_urb() would not suffice: it only cancels the in-flight URB and leaves it submittable once it returns, so the pending timer could re-submit it and put a fresh URB in flight over the freed sc. timer_shutdown_sync() then drains any last callback and blocks re-arming. The probe error path is unaffected: it is only reached before the timer is armed.  Reproduced under KASAN on next-20260710 via dummy_hcd + raw-gadget emulation of the GHL PS4 dongle (VID 0x1430 / PID 0x07bb): hid-sony binds and arms the poke timer, the poke URB is held in flight, the driver is unbound (freeing sc), then the URB is released. The completion re-arms the timer on the freed sc, and the re-armed timer fires ~8 s later:    BUG: KASAN: slab-use-after-free in ghl_magic_poke+0x98/0xb0   Read of size 8 at addr ffff88810b02fd50 by task swapper/0/0    ghl_magic_poke+0x98/0xb0    call_timer_fn+0x35/0x2b0    __run_timers+0x69c/0x9a0    run_timer_softirq+0x173/0x2a0   Allocated by task 169:  sony_probe   Freed by task 338:      devres_release_group <- hid_device_remove (sony_remove)  Found by 0sec (https://0sec.ai) using automated source analysis.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-09-11 20:19:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-89633",
                        "url": "https://ubuntu.com/security/CVE-2026-89633",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  smb: client: fix OOB read/write from unvalidated DataOffset in coalesce_t2()  coalesce_t2() computes data pointers directly from server-supplied DataOffset fields with no validation against buffer bounds:    data_area_of_tgt = (char *)&pSMBt->hdr.Protocol +                      get_unaligned_le16(&pSMBt->t2_rsp.DataOffset);   data_area_of_src = (char *)&pSMBs->hdr.Protocol +                      get_unaligned_le16(&pSMBs->t2_rsp.DataOffset);   data_area_of_tgt += total_in_tgt;   ...   memcpy(data_area_of_tgt, data_area_of_src, total_in_src);  A small DataOffset can push a pointer below the actual byte area, overwriting header fields; a large one can push it past the buffer end, causing out-of-bounds heap reads (source) or writes (target). The BCC overflow guard does not prevent this: BCC reflects how much data is present, while DataOffset controls where in the buffer it starts.  The \"validate target area\" comment present since the function was first written in 2005 was a placeholder that was never implemented.  Add lower- and upper-bound checks for both data pointers before the memcpy, and before any target header fields are modified.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-09-11 20:19:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-89652",
                        "url": "https://ubuntu.com/security/CVE-2026-89652",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ceph: bound copied dentry name length in NFS export get_name  ceph_get_name() copies the MDS-supplied name into the caller's NAME_MAX-sized buffer with memcpy(name, rinfo->dname, rinfo->dname_len) and then writes name[rinfo->dname_len] = 0, without checking dname_len against NAME_MAX. A malicious or buggy MDS that returns a LOOKUPNAME reply with dname_len > NAME_MAX overflows the buffer. __get_snap_name() copies rde->name / rde->name_len the same unchecked way.  Impact: a malicious or compromised Ceph MDS overflows the NAME_MAX name buffer in a client's NFS-export get_name path, a slab out-of-bounds write reported by KASAN. Reachable when a CephFS mount is re-exported over NFS.  Add ceph_export_copy_name(), which rejects lengths above NAME_MAX with -ENAMETOOLONG before the copy, and use it in both ceph_get_name() and __get_snap_name().",
                        "cve_priority": "critical",
                        "cve_public_date": "2026-09-11 20:19:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-89680",
                        "url": "https://ubuntu.com/security/CVE-2026-89680",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  nfsd: fix nfsd_file leak on inter-server COPY setup failure  When nfsd4_setup_inter_ssc() fails, nfsd4_copy() returns nfserr_offload_denied directly, bypassing the out: label where release_copy_files() would drop the nf_dst reference taken by nfs4_preprocess_stateid_op(). Each failed inter-server COPY leaks one nfsd_file, pinning file/inode/dentry/vfsmount.  Fix by setting status and jumping to out: instead of returning directly.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-09-11 20:19:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-89761",
                        "url": "https://ubuntu.com/security/CVE-2026-89761",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  apparmor: fix out-of-bounds write when null terminating a label vec  aa_vec_unique() null terminates at vec[n - dups] when VEC_FLAG_TERMINATE is passed. If the components are all distinct no duplicates are dropped, dups is 0 and the terminator goes to vec[n], so the caller has to provide room for n + 1 entries.  aa_label_strn_parse() sets up its vector with vec_setup(profile, vec, len, gfp) and then calls aa_vec_unique(vec, len, VEC_FLAG_TERMINATE), but vec_setup() does not reserve the terminator entry. Up to LOCAL_VEC_ENTRIES it uses the local array of LOCAL_VEC_ENTRIES pointers, above that it allocates exactly len pointers. The terminator therefore lands one entry past the end of the local array when len is LOCAL_VEC_ENTRIES, and one entry past the end of the allocation when len is larger.  len comes from the number of \"//&\" separated components in the label name and label_count_strn_entries() does not bound it. An unprivileged task reaches the parse by writing to /proc/self/attr/apparmor/current or through lsm_set_self_attr(2), both of which go through do_setattr(), and the name is parsed before the change_profile permission is checked. The query_label() path behind the securityfs .access file, which is mode 0666, performs no permission check at all. Every component has to resolve to a loaded profile, so a system with policy loaded is required.  The other two VEC_FLAG_TERMINATE users work on a label vec that aa_label_alloc() has already sized with \"+ 1 for null terminator entry on vec\". Reserve the same entry in vec_setup() and DEFINE_VEC(). Passing len + 1 from the caller instead would move len == LOCAL_VEC_ENTRIES out of the local array and into kzalloc().",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-09-11 20:20:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-80852",
                        "url": "https://ubuntu.com/security/CVE-2026-80852",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  tls: device: fix out-of-bounds write in tls_append_frag()  Found with syzkaller and a local syzbot instance running on top of a netdevsim TLS offload emulation; tls_device.c is otherwise only reachable on a machine with a NIC that implements the offload.  tls_push_data() only checks whether the open record still has room for another frag at the bottom of its loop, and the MSG_MORE early break skips that check.  The record survives to the next syscall with the frag count it already had, and tls_append_frag() does not check either, so with TLS_TX_ZEROCOPY_RO every splice(SPLICE_F_MORE) of a byte or two adds a non-coalescing pipe page and num_frags walks off the end of tls_record_info.frags[MAX_SKB_FRAGS].  Once the record is pushed, tls_push_record() runs the same index over sg_tx_data[MAX_SKB_FRAGS] and the sg_set_page() writes land on the destruct_work that follows it, which the workqueue then calls.  The byte limit is fine because copy drops to 0 and the loop falls through to the same check; the frag count has no such feedback.  Push the record rather than keep a full one open, which is what a plain TCP socket does - tcp_sendmsg_locked() uses tcp_mark_push() and new_segment in both the copy and the MSG_SPLICE_PAGES paths, and tls_sw already sets full_record when the sk_msg ring fills up, MSG_MORE or not.    BUG: KASAN: slab-out-of-bounds in tls_append_frag ( net/tls/tls_device.c:269)   Write of size 8 at addr ffff8881104d1530 by task tls_oob/450    CPU: 2 UID: 0 PID: 450 Comm: tls_oob Not tainted 7.2.0-rc7+ #329 PREEMPT   Call Trace:    <TASK>    dump_stack_lvl (lib/dump_stack.c:94 lib/dump_stack.c:120)    print_report (mm/kasan/report.c:378 mm/kasan/report.c:482)    kasan_report (mm/kasan/report.c:595)    tls_append_frag (net/tls/tls_device.c:269)    tls_push_data (net/tls/tls_device.c:518)    tls_device_sendmsg (net/tls/tls_device.c:583)    inet_sendmsg (net/ipv4/af_inet.c:865)    sock_sendmsg (net/socket.c:775 net/socket.c:790 net/socket.c:813)    splice_to_socket (fs/splice.c:884)    do_splice (fs/splice.c:936 fs/splice.c:1349)    __do_splice (fs/splice.c:1431)    __x64_sys_splice (fs/splice.c:1634 fs/splice.c:1616)    do_syscall_64 (arch/x86/entry/syscall_64.c:63 arch/x86/entry/syscall_64.c:94)    entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:121)    </TASK>  and, once the record is pushed:    UBSAN: array-index-out-of-bounds in net/tls/tls_device.c:300:24   index 18 is out of range for type 'skb_frag_t [17]'   UBSAN: array-index-out-of-bounds in net/tls/tls_device.c:301:41   index 18 is out of range for type 'scatterlist [17]'   UBSAN: array-index-out-of-bounds in net/tls/tls_device.c:302:39   index 18 is out of range for type 'scatterlist [17]'   UBSAN: array-index-out-of-bounds in net/tls/tls_device.c:307:38   index 26 is out of range for type 'scatterlist [17]'    kernel tried to execute NX-protected page - exploit attempt? (uid: 0)   BUG: unable to handle page fault for address: ffffea000411a680   #PF: supervisor instruction fetch in kernel mode   #PF: error_code(0x0011) - permissions violation   Oops: Oops: 0011 [#1] SMP KASAN PTI   Workqueue: ktls_device_destruct 0xffffea000411a680   RIP: 0010:0xffffea000411a680   Call Trace:    <TASK>    worker_thread (kernel/workqueue.c:3405 kernel/workqueue.c:3486)    kthread (kernel/kthread.c:436)    ret_from_fork (arch/x86/kernel/process.c:158)    ret_from_fork_asm (arch/x86/entry/entry_64.S:245)    </TASK>",
                        "cve_priority": "high",
                        "cve_public_date": "2026-09-04 16:18:00 UTC"
                    }
                ],
                "launchpad_bugs_fixed": [
                    2173211,
                    2173225,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857
                ],
                "changes": [
                    {
                        "cves": [
                            {
                                "cve": "CVE-2026-99115",
                                "url": "https://ubuntu.com/security/CVE-2026-99115",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ksmbd: fill in FileSysIdentifier in FS_POSIX_INFORMATION  smb2_get_info_filesystem() reports 56 bytes for FS_POSIX_INFORMATION, that is the whole of FILE_SYSTEM_POSIX_INFO, but never assigns FileSysIdentifier.  Those eight bytes go to the client as they are found in the response buffer.  The buffer is zeroed on allocation, so a standalone request leaks nothing.  A compound request can leak: the offset of the next response is advanced by the length pinned for the previous one, so a reply that was written into the buffer and then dropped in favour of the short error response of smb2_set_err_rsp() stays there, and the next reply is laid over it with only the header cleared.  Report the file system id statfs() returned, which is what the field is for.  FileSysIdentifier is __le64 and f_fsid is a pair of ints, so assemble the value first, val[0] as the low half, and convert it on the way out.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99113",
                                "url": "https://ubuntu.com/security/CVE-2026-99113",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ksmbd: zero the FS_OBJECT_ID_INFORMATION buffer before filling it in  smb2_get_info_filesystem() reports 64 bytes for FS_OBJECT_ID_INFORMATION, that is the whole of struct object_id_info, but writes only 46 of them:   - objid[] is 16 bytes, and when the volume UUID is not available only    sizeof(stfs.f_fsid) (8) bytes are copied into it;  - extended_info.version_string[] is STRING_LENGTH (28) bytes, and only    strlen(\"1.1.0\") (5) bytes are copied into it.  The response buffer is zeroed on allocation (kvzalloc() in smb2_allocate_rsp_buf()), so for a standalone request the remaining 31 bytes are zero.  In a compound request they need not be.  The offset of the next response is advanced by the length pinned for the previous one, so if a preceding command wrote its reply into the buffer and then failed, smb2_set_err_rsp() pins only the short error response and the next reply lands inside the area that has already been written.  Only the header is cleared there:  \tmemset((char *)rsp_hdr, 0, sizeof(struct smb2_hdr) + 2);  The client then receives up to 31 bytes of a response it was not meant to see, including one that failed with an access denied error.  Clear the structure before filling it in.  As a side effect version_string is now NUL terminated.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99114",
                                "url": "https://ubuntu.com/security/CVE-2026-99114",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ksmbd: initialize FileSystemControlFlags in FS_CONTROL_INFORMATION  smb2_get_info_filesystem() reports 48 bytes for FS_CONTROL_INFORMATION, that is the whole of struct smb2_fs_control_info, but never assigns FileSystemControlFlags.  Those four bytes go to the client as they are found in the response buffer.  The buffer is zeroed on allocation, so a standalone request leaks nothing.  A compound request can leak: the offset of the next response is advanced by the length pinned for the previous one, so a reply that was written into the buffer and then dropped in favour of the short error response of smb2_set_err_rsp() stays there, and the next reply is laid over it with only the header cleared.  ksmbd does not implement quota tracking, so report no control flags.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99132",
                                "url": "https://ubuntu.com/security/CVE-2026-99132",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  xfs: don't hold buffer locks across sync transaction commit in xfs_sync_sb_buf  xfs_sync_sb_buf() holds sb/rtsb buffer locks across a synchronous xfs_trans_commit(), which flushes the CIL push workqueue internally. If shutdown occurs during the CIL push, xfs_buf_item_unpin() needs to lock these buffers to fail them, causing a deadlock:    setlabel:          holds buf lock -> flush_workqueue(xfs-cil)   CIL push worker:   xfs_buf_item_unpin -> xfs_buf_lock(same buf)  Remove the xfs_trans_bhold() calls so that commit releases the buffer locks normally.  After the sync commit, re-acquire the buffers via mp->m_sb_bp / mp->m_rtsb_bp for the on-disk writeback.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99135",
                                "url": "https://ubuntu.com/security/CVE-2026-99135",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  dm-integrity: fix infinite loop on discard with large tag size  When integrity_metadata handles a discard, it fills a buffer with DISCARD_FILLER and writes it over the tags, max_blocks blocks at a time. If the kmalloc fails, the buffer is the on-stack array checksums_onstack and max_size is set to HASH_MAX_DIGESTSIZE. So if the tag size is larger than HASH_MAX_DIGESTSIZE, max_blocks is zero, bi_size is never decremented and the loop never terminates.  Fix this by using sizeof(checksums_onstack) as max_size. The array has MAX_TAG_SIZE bytes since commit b93b6643e9b5 (\"dm integrity: fix a crash with unusually large tag size\"), so max_blocks is at least 1.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99118",
                                "url": "https://ubuntu.com/security/CVE-2026-99118",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  drm/i915/dmc: Harden DMC firmware payload parsing  Validate the conversion of the DMC firmware size from dwords to bytes using check_mul_overflow() before calculating the firmware payload size.  Reject zero-length payloads and zero MMIO counts in the DMC firmware header so malformed firmware is caught early. Also set dmc_fw_size only after the payload allocation succeeds.  (cherry picked from commit efde6601a1f1daedfe3dcc2816c934ddb44e3eef)",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99169",
                                "url": "https://ubuntu.com/security/CVE-2026-99169",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  futex: Fix mm reuse handling for FUT_OFF_MMSHARED  A FUT_OFF_MMSHARED futex is a shared futex that refers to an MM. It is possible for a process to wait on a shared futex with a different MM because a FUT_OFF_INODE waiter can be requeued onto a FUT_OFF_MMSHARED futex by another process. This can cause FUT_OFF_MMSHARED waiters on a freed MM to consume wakeups intended for a newly allocated MM at the same address.  Fix it by keying FUT_OFF_MMSHARED using a unique 64-bit per-MM ID. Leave private futexes as before to avoid influencing the performance of the hotpath.  (Multi-threaded processes typically implicitly use FUT_OFF_MMSHARED by setting clear_child_tid such that it points into anonymous memory, which causes mm_release() in a multi-threaded mm to perform FUTEX_WAKE.)",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99161",
                                "url": "https://ubuntu.com/security/CVE-2026-99161",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  i2c: viai2c-wmt: Fix clock leak in wmt_i2c_probe()  In wmt_i2c_probe(), i2c->clk is acquired using of_clk_get(). If any subsequent operation fails or when the module is unloaded, the clock reference count is never decremented via clk_put(), leading to a resource leak.  Switch to devm_clk_get() so that the clock is automatically managed and released.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99077",
                                "url": "https://ubuntu.com/security/CVE-2026-99077",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ipv4: udp: Create exceptions before socket matching  Currently, when ICMP Fragmentation Needed and Redirect Message packets are locally delivered and quote a UDP packet, a FIB nexthop exception (FNHE) is only created if the kernel can match the UDP packet to an existing socket.  This behavior allows off-path attackers to conduct a side-channel attack on the FNHE cache in order to discover the ephemeral port used by a connected UDP socket.  Commit 6457378fe796 (\"ipv4: use siphash instead of Jenkins in fnhe_hashfun()\") and commit 67d6d681e15b (\"ipv4: make exception cache less predictible\") tried to mitigate such attacks by making it harder for attackers to discover hash collisions in the FNHE cache and by randomizing the number of exceptions a hash bucket can hold, respectively. Unfortunately, both of the mitigations can be bypassed.  Instead, mitigate such attacks by always creating a FNHE, even before trying to find a matching socket. Do that by calling ipv4_update_pmtu() and ipv4_redirect(), the helpers used when the quoted packet did not originate from a socket.  This means that guesses (right or wrong) from an off-path attacker will always result in a FNHE being created or updated in the cache that the attacker can observe.  Pass an oif of 0, in a similar fashion to icmp_err(). This is also the oif used by the socket path for sockets that are not bound to a device.  Note that this does not allow attackers to create FNHEs that they could not create before, as both helpers can already be reached with little to no validation. For example, by sending an ICMP error that quotes an ICMP Echo Reply or one that quotes a UDP source port that matches a wildcard socket.  Also note that in the good case (matched socket) the above scheme comes at the cost of an extra route lookup, as the no socket helpers perform their own lookup before the one performed by ipv4_sk_update_pmtu() / ipv4_sk_redirect(). When the two resolve to different nexthops, it also results in two exceptions being created for the same destination IP. One in the FNHE cache of the nexthop resolved by the no socket helpers and another in the FNHE cache of the nexthop used by the socket.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99123",
                                "url": "https://ubuntu.com/security/CVE-2026-99123",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  vsock/virtio: validate packet source for connected sockets  virtio_transport_recv_pkt() looks up sockets first by the full source and destination tuple, then by destination only in the bound table. The fallback is needed for listening and connecting sockets, but sockets remain in the bound table after connect(), so it can also return a non-listening socket.  The fallback does not validate the source address. In TCP_SYN_SENT, a RESPONSE from an unrelated source can transition the victim socket to TCP_ESTABLISHED while its stored remote address remains unchanged. Subsequent RW packets from that source are delivered through the same destination-only fallback.  This was reproduced with capability-empty processes under different UIDs. The attacker discovered the target tuple through unprivileged AF_VSOCK sock_diag and caused the victim socket to read 16 attacker-chosen bytes; the intended peer-side socket read 0 of those 16 bytes.  Add vsock_check_source() to validate the transport, source port and source CID against the peer stored in a non-listening socket. The local transport is the CID exception because its packets are generated internally with VMADDR_CID_LOCAL as their source, including connections using CID aliases.  Use the helper after lock_sock() in the virtio receive path.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-89987",
                                "url": "https://ubuntu.com/security/CVE-2026-89987",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  mm/huge_memory: transfer the pmd dirty bit to the folio on zap  zap_huge_pmd_folio() propagates the pmd young bit to the folio for the file case, but not the dirty bit.  The pte path does propagate it, in zap_present_folio_ptes() and so does the pmd split path, in __split_huge_pmd_locked().  For most file mappings the omission is harmless, because writing to a shared file mapping goes through page_mkwrite(), which dirties the folio. tmpfs is different: it has no page_mkwrite(), and vma_wants_writenotify() is false for it, so a *read* fault on a MAP_SHARED tmpfs mapping installs a writable pmd via do_read_fault().  do_read_fault() does not call fault_dirty_shared_page(), so subsequent stores through that mapping set only the hardware dirty bit in the pmd and never call folio_mark_dirty(). A shmem folio allocated by a fault is marked uptodate but not dirty (see the clear: block in shmem_get_folio_gfp()), so PG_dirty is never set at all.  Unmapping such a folio - munmap(), or exit_mmap() when the process dies - then loses the only record that it was written, because zap_huge_pmd() drops the pmd without transferring the dirty bit.  Reclaim afterwards sees a clean shmem folio: the whole swap-out block in shrink_folio_list() is inside \"if (folio_test_dirty(folio))\", so pageout() is skipped and the folio falls into __remove_mapping().  There, folio_is_file_lru() is false for a swapbacked folio, so no shadow entry is created and __filemap_remove_folio(folio, NULL) simply empties the i_pages slot.  The data is freed without ever being written to swap, and the next fault on that index returns a freshly zeroed folio.  This is silent data loss for any process that keeps state in a MAP_SHARED tmpfs segment across an unmap - for example a cache handed from one process generation to the next through /dev/shm.  It requires the folio to be PMD-mapped, so it only shows up once shmem THP is enabled (which is what we did in Meta fleet and started noticing crashes); with THP off the pte path transfers the dirty bit correctly.  It also only becomes visible when swap is enabled, because with no swap device shmem folios (which are on the anon LRU) are not scanned by reclaim at all, so the clean folio is never dropped.  Reproduced on x86_64 with a tmpfs mounted huge=within_size: read-fault a 2MB-backed region, write a known pattern through the resulting mapping, munmap, force reclaim of the cgroup, then re-map and read back.  Without this patch the region reads back as zeros and vmstat shows zswpout 0 - the data was discarded rather than swapped.  With this patch the region reads back correctly and the pages are swapped out as expected.  With huge=never, or when the first touch is a write, the test passes either way.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-09-16 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-80572",
                                "url": "https://ubuntu.com/security/CVE-2026-80572",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  Input: byd - synchronize timer deletion before freeing private data  byd_disconnect() uses timer_delete() before freeing the driver's private data.  This does not wait for a running byd_clear_touch() callback, which dereferences the private data and its psmouse pointer.  A callback racing with disconnect can therefore access the private data after it has been freed.  The timer can also still be re-armed by byd_process_byte() while the disconnect is in progress.  Use timer_shutdown_sync() before freeing the private data: it waits for a running callback and turns any later re-arm attempt into a no-op.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-08-26 15:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99180",
                                "url": "https://ubuntu.com/security/CVE-2026-99180",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  unicode: free the map after a grace period  generic_ci_d_hash() and generic_ci_d_compare() read sb->s_encoding and dereference the unicode map while a pathwalk in rcu mode holds nothing but rcu_read_lock(). The filesystems that use them, ext4, f2fs and tmpfs, drop the map with utf8_unload() from ->put_super(), which runs when the last reference to the mount goes away. A lookup that is still inside such a filesystem at that point reads a freed map.  With a pathwalk held up in utf8_casefold_hash() while the last reference to a casefolded tmpfs goes away:    BUG: KASAN: slab-use-after-free in utf8nlookup+0x74c/0x950   Read of size 8 at addr ff110001030fe658 by task walker/98   Call Trace:    <TASK>    utf8nlookup+0x74c/0x950    utf8byte+0x160/0x1560    utf8_casefold_hash+0x167/0x230    generic_ci_d_hash+0xdd/0x1c0    link_path_walk+0x11ad/0x1d30    path_lookupat+0x63/0xb00    filename_lookup+0x1f1/0x5b0    vfs_statx+0xd7/0x3b0   [...]   Allocated by task 94:    __kmalloc_cache_noprof+0x249/0x560    utf8_load+0x4e/0x570    shmem_parse_opt_casefold.isra.0+0x92/0x270   [...]   Freed by task 97:    kfree+0x1db/0x5b0    shmem_put_super+0x72/0x170    generic_shutdown_super+0x14c/0x530    kill_anon_super+0x3a/0x60    deactivate_locked_super+0x9c/0xf0    cleanup_mnt+0x9f/0x130  So far that has been hard to hit. umount(2) waits for a grace period in namespace_unlock() before it drops the mount, so only a mount whose last reference goes away elsewhere, like the close of a file or a chdir out of a lazily unmounted directory, can race a walker. So it is reachable.  Delay the free until a grace period has passed. The map and the data table it holds a reference to then outlive any pathwalk that found the superblock before the mount went away. The reference on the data table module is dropped from the rcu callback as well. utf8-core is built in whenever CONFIG_UNICODE is set, so there is no module exit that would have to wait for the callbacks.  Overlayfs points the s_encoding of an overlay at the map of its first layer without taking a reference of its own. That stays correct. The layer is held by the overlay, so its map is dropped only after the overlay is gone.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99179",
                                "url": "https://ubuntu.com/security/CVE-2026-99179",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  watch_queue: Fix note pool publication race in watch_queue_set_size()  There is a race between watch_queue_set_size() and post_one_notification(). watch_queue_set_size() publishes wqueue->notes, notes_bitmap, nr_pages and nr_notes with plain stores, and post_one_notification() reads them with plain loads under a different lock, so nothing orders the four stores against the poster's loads: depending on the build, notes can be stored last (gcc 14 on x86-64 does this).  Since keyctl_watch_key() lets a watch attach to a queue before it is sized, post_one_notification() can already be running on another CPU at that moment: it reads nr_notes > 0, passes its bounds check, and then reads notes while it is still NULL, dereferencing notes[0].  An unprivileged user triggers this reliably by watching one of its own keys through a notification pipe and racing ioctl(IOC_WATCH_QUEUE_SET_SIZE) on that pipe against keyctl(KEYCTL_SETPERM) on the key from another CPU, triggering:    BUG: kernel NULL pointer dereference, address: 0000000000000000   RIP: 0010:post_one_notification.isra.0+0xa2/0x1e0   Call Trace:    __post_watch_notification+0x148/0x180    keyctl_setperm_key+0x119/0x130    do_syscall_64+0x108/0x4c0    entry_SYSCALL_64_after_hwframe+0x77/0x7f   Kernel panic - not syncing: Fatal exception in interrupt  Fix this by publishing nr_notes last with smp_store_release(), and by reading it once with smp_load_acquire() in post_one_notification() before the bitmap and the page array are touched.  A poster that observes a non-zero nr_notes then also observes the pool behind it; one that observes zero drops the notification as before.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-89912",
                                "url": "https://ubuntu.com/security/CVE-2026-89912",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  KVM: arm64: vgic-its: Don't dereference a NULL collection on ITT save  MAPC with V=0 drops ite->collection but leaves the ITE on the device's ITT list, and vgic_its_save_ite() dereferences it unconditionally. A guest that issues MAPD, MAPTI and then MAPC(V=0) therefore oopses the host when the VMM issues KVM_DEV_ARM_ITS_SAVE_TABLES to migrate it. That sequence is UNPREDICTABLE per the architecture, but KVM already handles the resulting state in the translate, MOVI and DISCARD paths.  Save a zeroed entry, which vgic_its_restore_ite() reads back as invalid. Skipping the ITE instead would leave the ITT slot holding whatever is in guest memory, and restore rejects an entry naming a collection the restored collection table does not have.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-09-16 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99156",
                                "url": "https://ubuntu.com/security/CVE-2026-99156",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  scsi: st: Fix use-after-free race between st_remove() and st_open()  st_remove() drops the probe reference on the scsi_tape with kref_put() and only afterwards removes its index from st_index_idr. If that was the last reference, scsi_tape_release() frees the structure while it is still published in the idr.  scsi_tape_get(), called from st_open(), looks up the tape in st_index_idr and takes a reference under st_ref_mutex and st_index_lock. remove_cdevs() does not wait for opens that are already past chrdev_open(), so an open that is blocked on st_ref_mutex while st_remove() holds it can take the mutex as soon as st_remove() drops it, find the freed tpnt in the idr and call kref_get() on it:    BUG: KASAN: slab-use-after-free in st_open   Write of size 4 ...    st_open (drivers/scsi/st.c:254 drivers/scsi/st.c:1291)    chrdev_open   ...   Freed by task ...:    kfree    st_remove (drivers/scsi/st.c:4512)  Remove the index from the idr before dropping the reference, all under st_ref_mutex. A concurrent scsi_tape_get() now either runs first and holds a valid reference that keeps the tape alive, or runs afterwards and finds nothing, so st_open() fails with -ENXIO.  This restores the ordering st_remove() had before the conversion to st_index_idr, where the tape was unpublished from scsi_tapes[] before the final kref_put().",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99112",
                                "url": "https://ubuntu.com/security/CVE-2026-99112",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net/sched: cls_flower: validate mask pointer after nla_next()  fl_set_enc_opt() iterates the key's nested tunnel-option attributes with nla_for_each_attr() while advancing a single mask pointer via nla_next() at the bottom of each loop, so the mask cursor is driven by the number of key attributes rather than by the mask's own attributes.  The nla_ok() added by commit c96adff956191 (\"cls_flower: call nla_ok() before nla_next()\") only validates the mask pointer that was just consumed; the pointer produced by nla_next() is used by the next iteration (fl_set_geneve_opt() and siblings) without any validation.  The mask's nested attributes are validated with NL_VALIDATE_LIBERAL, which merely warns on trailing bytes that do not form a complete attribute.  A mask carrying one valid attribute plus 1-3 residue bytes (or a non-aligned attribute length making msk_depth negative) therefore reaches the next iteration with msk_depth != 0, so neither the !msk_depth check in fl_set_enc_opt() nor the !depth check in the per-type helpers fires.  nla_type() then reads past the mask payload and nla_parse_nested_deprecated() iterates with an nla_len taken from those bytes, reading well beyond the mask attribute (KASAN: slab-out-of-bounds read in __nla_validate_parse from fl_change()).  Validate the advanced mask pointer as well: when the mask is not legitimately exhausted (msk_depth != 0) and the new pointer fails nla_ok(), reject the filter with -EINVAL.  An exactly exhausted mask still skips the check, preserving exact-match behaviour for the remaining key attributes.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99117",
                                "url": "https://ubuntu.com/security/CVE-2026-99117",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net: bridge: mcast: don't truncate the port group walk on teardown  __br_multicast_disable_port_ctx() and br_multicast_del_port() walk port->mglist with hlist_for_each_entry_safe(). However, br_multicast_find_del_pg() can also delete other entries from the same list through br_multicast_fwd_src_remove() or __fwd_del_star_excl().  If such an entry is the iterator's saved next node, hlist_del_init() clears its ->next and terminates the walk early. The reproducer triggers this in both teardown walks, leaving port groups in the bridge mdb with a dangling ->key.port after del_nbp() frees the port:    BUG: KASAN: slab-use-after-free in __mdb_fill_info+0x1191/0x1320    __mdb_fill_info+0x1191/0x1320    br_mdb_dump+0x594/0xe40    rtnl_mdb_dump+0x1cf/0x5d0  Use hlist_del_init_rcu() to unlink the group while preserving ->next. br_multicast_del_pg() and the teardown walks run under br->multicast_lock. The GC worker must acquire the same lock before detaching the group for destruction, so the node remains alive while the walk uses the preserved pointer.  Preserving ->next means a walk can now reach a group that an earlier iteration already deleted as a side effect. That group is off mp->ports, so br_multicast_find_del_pg() would fall through its port scan and hit the trailing WARN_ON(1). Skip such groups at the top of that helper: a port group is put on port->mglist when it is created and only unlinked when it is deleted, so hlist_unhashed() identifies exactly this case.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-74405",
                                "url": "https://ubuntu.com/security/CVE-2026-74405",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  OPP: Fix race between OPP addition and lookup  A race exists between dev_pm_opp_add_dynamic() and dev_pm_opp_find_freq_exact():    CPU0 (add)                          CPU1 (lookup)   -------------------------------     ------------------------------   _opp_add()     mutex_lock()     list_add(&new_opp->node, head)     mutex_unlock()                    _opp_table_find_key()                                         mutex_lock()                                         dev_pm_opp_get(opp)                                           kref_get()                                         mutex_unlock()     kref_init(&new_opp->kref)                                       dev_pm_opp_put()                                         kref_put_mutex()  The newly added OPP is inserted into the list before its kref is initialized. A concurrent lookup can find this OPP and increment its reference count while it is still uninitialized, leading to refcount corruption and a potential premature free.  Fix this by initializing ->kref and ->opp_table before making the OPP visible via list_add(). This ensures any concurrent lookup observes a fully initialized object.  [ Viresh: Updated commit log ]",
                                "cve_priority": "low",
                                "cve_public_date": "2026-08-15 06:22:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-74739",
                                "url": "https://ubuntu.com/security/CVE-2026-74739",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net/sched: cls_u32: skip hash tables in u32_bind_class()  u32_walk() enumerates both struct tc_u_hnode and struct tc_u_knode through the walker callback. u32_bind_class() unconditionally casts the passed fh to tc_u_knode and accesses &n->res, so when fh is actually a tc_u_hnode, which has no tcf_result member, this results in a slab-out-of-bounds read of res->classid in tc_cls_bind_class().  The issue can be reproduced with the following commands:      tc qdisc add dev lo root handle 1: hfsc     tc class add dev lo parent 1: classid 1:1 hfsc sc rate 1000kbit     tc filter add dev lo parent 1:1 protocol ip prio 1 u32 match u32 0 0 flowid 1:1     tc class add dev lo parent 1: classid 1:2 hfsc sc rate 2000kbit  Fix this by skipping hash tables via the TC_U32_KEY(handle) check.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-08-26 15:16:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-64015",
                                "url": "https://ubuntu.com/security/CVE-2026-64015",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  security/keys: fix missed RCU read section on lookup  Nicholas Carlini reports that the keyring code calls assoc_array_find() in find_key_to_update() without holding the RCU read lock, while the assoc_array_gc() code really is designed around removing the node from the tree and then freeing it after an RCU grace-period.  The regular key handling doesn't see this because holding the keyring semaphore hides any lifetime issues, but the persistent key handling uses a different model.  Instead of extending the keyring locking, just do the simple RCU locking that the assoc_array was designed for.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-07-19 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-74672",
                                "url": "https://ubuntu.com/security/CVE-2026-74672",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  mm/vmalloc: acquire init_mm lock on huge vmap to avoid ptdump UAF  Patch series \"mm: fix UAF caused by race between ptdump and vmap pgtable freeing\", v6.  Kernel page table walkers fall into two broad categories - those ranges where no exclusion is required via walk_kernel_page_table_range_lockless() and those where exclusion is required via walk_kernel_page_table_range() or walk_page_range_debug().  The former category is used only by arm64 arch code operating on ranges it both wholly owns and does not concurrently write.  The latter category consists of kernel page table walkers operating on ranges that are wholly owned (but which need exclusion against concurrent writers).  The lock used for exclusion is the mmap lock, and for kernel ranges this is the mmap lock on init_mm.  ptdump is a special case being both the only user of walk_page_range_debug(), and the only case in which it walks ranges it does not own.  This presents a problem, as page tables may be freed under ptdump.  And indeed there is a use-after-free bug in the kernel as a result, which this series addresses.  vmap promotes page tables to huge leaf entries where possible, freeing the lower page table when it does.  It does this with no meaningful locks held against concurrent ptdump walks.  As a result, use-after-free can currently occur.  This series addresses the issue by having the vmap huge promotion logic acquire the mmap read lock while both setting the huge page table entry and freeing the prior leaf page table.  The ptdump code already acquires the mmap write lock, so by doing so we ensure that the ptdump walker only ever observes either the huge page table entry or the existing page table entry, and nothing is freed underneath it.  A mitigation for this issue was already applied for arm64 in commit fa93b45fd397 (\"arm64: Enable vmalloc-huge with ptdump\"), which this series has to deal with carefully.  This mitigation resolves the issue by acquiring the mmap read lock on init_mm on vmap page table free if a ptdump is in progress.  However the fix in this series would cause a deadlock if we were to simply apply it for arm64 without also reverting the change.  This is because vmap may acquire the read lock before ptdump attempts to acquire the write lock, which then gets queued, and rwsem starvation rules mean that the (unacknowledged) nested mmap read lock in the arm64 code would also block, meaning the original read lock is never released and thus deadlock.  This series works around this by #ifndef CONFIG_ARM64'ing the mmap read lock in vmap logic, then partially reverting commit fa93b45fd397 (\"arm64: Enable vmalloc-huge with ptdump\"), keeping the enablement of huge vmap support, and removing the ifdeffery with the partial revert patch.  There are related issues that are also addressed in this series:  * x86 page attribute logic, specifically Change Page Attributes (CPA),   implements a feature whereby huge ranges can be collapsed into huge leaf   entries. This can similarly cause a UAF when done in parallel with a   ptdump walk, so similarly acquire the init_mm mmap lock to avoid this.  * The CPA logic allows concurrent page table manipulation and CPA   collapse, meaning the former risks accessing a page table the latter   frees. Fix this by acquiring mmap write lock on init_mm across the   whole CPA collapse operation and read lock on the page table   manipulation.  * x86 and arm64 permit walks of non-kernel mm's (both allowing efi mm   walks, and in x86's case arbitrary mm's), so we ensure kernel mappings   remain stable by locking the init_mm as well as the mm being walked.  The ordering of patches is established for both strict dependencies (the arm64 partial revert in particular has to be done after the vmap changes) and logical ones (the non-kernel mm fix only makes sense once the vmap/CPA fixes are in place).   This patch (of 3):  Currently there is a nasty ra ---truncated---",
                                "cve_priority": "low",
                                "cve_public_date": "2026-08-22 16:16:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99121",
                                "url": "https://ubuntu.com/security/CVE-2026-99121",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ipv4: avoid divide by zero in fib_rebalance  fib_rebalance() computes the total eligible nexthop weight in one pass and programs upper bounds in a second pass. A concurrent change to ignore_routes_with_linkdown can make the first pass return zero while the second pass sees an eligible nexthop, resulting in division by zero.  If the first pass reports a zero total, set each nexthop upper bound to -1 and skip the division. This matches the IPv6 fix in commit d2c26c2911dd (\"ipv6: avoid divide by zero in rt6_multipath_rebalance\") and preserves the lock-free rebalance path.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99124",
                                "url": "https://ubuntu.com/security/CVE-2026-99124",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  s390/pci: Fix leak of uninitialized kernel data in SCLP report  While report_error_write() checks that the provided buffer is at least as large as the header struct, but not that it is large enough to contain the report with the length claimed by report->length. If user-space provides a short buffer, meaning a larger report->length than the actually written payload, up to around 4K of kernel data from past the kmalloc(len + 1) sized buffer allocated in kernfs_fop_write_iter() will leak into the SCLP report.  However, as the entity processing the SCLP is privileged and able to access at least the page including the report, this does not leak data that entity could not access but it is still an out of bounds read and a malformed error report that should be rejected.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99126",
                                "url": "https://ubuntu.com/security/CVE-2026-99126",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  s390/ctcm: Prevent XID null dereference  The mpc_validate_xid() function sets grp->saved_xid2->xid2_flag2 to 0x40 to signal XID validation error. If peer XID is NULL or r/w channel pairing mismatch happens, grp->saved_xid2 is never initialized. An attempt to set the flag in such case leads to NULL dereference.  Fix this by using the always available priv->xid->xid2_flag2 instead of grp->saved_xid2->xid2_flag2 for validation errors.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99127",
                                "url": "https://ubuntu.com/security/CVE-2026-99127",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  page_pool: keep frag_offset aligned for odd-sized requests  page_pool_alloc_frag_netmem() rounds the requested fragment size with  \tsize = ALIGN(size, dma_get_cache_alignment());  dma_get_cache_alignment() returns 1 unless the architecture defines ARCH_DMA_MINALIGN, which DMA-coherent architectures such as x86 do not. There the ALIGN() is a no-op and pool->frag_offset advances by the raw, unrounded size.  A single caller asking for an odd size then leaves frag_offset misaligned for every fragment carved out of that page afterwards.  The pool is shared, so the damage is not confined to the caller that caused it.  The per-cpu system_page_pool used by generic XDP hits this. skb_pp_cow_data() allocates its fragments with the raw packet length:  \tsize = min_t(u32, len, PAGE_SIZE); \ttruesize = size; \tpage = page_pool_dev_alloc(pool, &page_off, &truesize);  leaving frag_offset odd for whatever is carved out of that page next.  Its own head allocation is already aligned -- SKB_HEAD_ALIGN(size) plus the XDP_PACKET_HEADROOM its callers pass -- so it is a later user of the shared pool that pays: page_pool_dev_alloc_va() returns a misaligned buffer, napi_build_skb() installs it as skb->head, and skb_shinfo(skb) == skb->head + skb->end is misaligned with it.  skb_shinfo()->dataref is a 4-byte atomic_t at offset 0x20, so the atomic_inc() in __skb_clone() straddles a cache line.  On x86 with split lock detection -- fatal for kernel split locks by default -- this panics the machine:    Oops: Split lock detected   RIP: 0010:skb_clone+0x154/0x1e0   Call Trace:    <IRQ>    raw_local_deliver+0x1ed/0x2c0    ip_protocol_deliver_rcu+0x54/0x1c0    ip_local_deliver_finish+0x85/0x100    ip_local_deliver+0x67/0x100    __netif_receive_skb_one_core+0x85/0xa0    process_backlog+0x87/0x130  Reproduced by attaching any generic-mode XDP program to loopback and opening a RAW IPPROTO_UDP socket, which makes raw_local_deliver() clone every locally delivered UDP packet; ordinary DNS traffic then triggers it, roughly once per 2500 clones.  Observed on 6.12.101 and 7.1.8.  Tracing page_pool_alloc_frag_netmem() over one such run shows the amplification -- two odd-sized requests, nine misaligned offsets:    requested size & 7:   0: 17035    5: 1    7: 1   frag_offset & 7:      0: 17028    3: 1    4: 1    5: 1    6: 1    7: 5  and skb_pp_cow_data() returning heads that were aligned on entry:    head 0xffff8f4c86aeac00 -> 0xffff8f4c53a9a9c4 (&7=4)   head 0xffff8f4d6a8a42c0 -> 0xffff8f4c4f7b7a45 (&7=5)  Round the fragment size up to at least the alignment struct skb_shared_info requires, so fragments are always suitably aligned for the objects callers build on them.  Architectures needing a larger DMA alignment keep it.  This also makes the remainder computed in page_pool_alloc_netmem(),  \t*size = max_size - *offset;  aligned, since max_size is a power of two -- which fixes the matching misalignment of skb->end.  Verified with a controlled A/B under QEMU/KVM: same tree, same config, same compiler, same rootfs and identical traffic, differing only by this patch.  A SEC(\"xdp.frags\") XDP_PASS program on lo plus UDP datagrams larger than max_head_size drives skb_pp_cow_data()'s fragment loop, which passes raw packet lengths to the pool.  Measured at the return of skb_pp_cow_data():                            unpatched   patched   skb_pp_cow_data calls       40800     40800   misaligned skb->head         1120         0   dataref at line offset >60     80         0  The last row counts the accesses that actually fault: skb_shinfo()->dataref sits at head+end+0x20 and is a 4-byte atomic, so `lock incl` splits a 64-byte cache line only when that address lands at offset 61..63.  All 80 occurrences were at offset 61; the panic reported above was at offset 62.  Eliminating the misalignment removes every one of them.  Same class of bug as commit 3bed3cc4156e (\"net: Do not allocate page fragments t ---truncated---",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99128",
                                "url": "https://ubuntu.com/security/CVE-2026-99128",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  sctp: validate chunk length in the inqueue parser  SCTP chunks always include a four-byte generic header, but sctp_inq_pop() currently accepts shorter declared lengths. A zero-length chunk leaves chunk_end at the current header.  When ASCONF is covered by the association's SCTP-AUTH policy, sctp_assoc_bh_rcv() can continue before the state machine performs its normal chunk-length check. sctp_inq_pop() then returns the same malformed chunk repeatedly and the receive softirq can lock up.  A remote SCTP peer can trigger this after establishing an association on a kernel built with CONFIG_IP_SCTP and configured with net.sctp.addip_enable=1 and net.sctp.auth_enable=1. The reproducer did not require application credentials, a shared SCTP AUTH key, or net.sctp.addip_noauth_enable=1.  On commit f967455fb2a5 (\"seg6: reset IP6CB after IPv6 decapsulation\"), one zero-length ASCONF caused repeated watchdog soft-lockup reports in a two-vCPU KVM guest. All 3 pre-trigger health probes succeeded, while 36 of 37 post-trigger probes failed. With this change, all 37 post-trigger probes succeeded and no equivalent soft-lockup signature appeared.  Reject chunks shorter than the generic SCTP header at the shared inqueue parser boundary. Mark the packet for discard before either caller can continue processing it, while preserving the four-byte generic minimum. Declared-length 1 through 4 controls and kernel-generated ASCONF traffic remained healthy. The patched sctp_hello selftest passed for IPv4 and IPv6.  The complete private reproducer and validation evidence are available directly to maintainers on request.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99133",
                                "url": "https://ubuntu.com/security/CVE-2026-99133",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net/iucv: fix the recvmsg window update  iucv_sock_recvmsg() sends the HiperSockets-only AF_IUCV_FLAG_WIN without testing the transport, so on a classic z/VM socket iucv_send_ctrl() sizes the skb through a NULL iucv->hs_dev. SO_MSGLIMIT accepts 1, so msglimit / 2 is zero and one recvmsg() on its own socket is enough for an unprivileged process to take a spurious disconnect.  It also calls iucv_send_ctrl() under spin_lock_bh(&message_q.lock), which allocates GFP_KERNEL inside a section the code treats as atomic. Sending outside that lock lets two recvmsg() reach afiucv_hs_send() at once, where msg_recv is sampled for the advertised window and subtracted after dev_queue_xmit() -- and sendmsg reaches that counter under lock_sock() while recvmsg holds no socket lock, so both can subtract the same value, the counter goes negative and the credit reaches the peer twice.  Test the transport, claim the credit with atomic_xchg() after the last error exit and hand it back if the transmit fails, and send once the lock is dropped.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99136",
                                "url": "https://ubuntu.com/security/CVE-2026-99136",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  dm-crypt: fix a tiny race condition in crypt_dec_pending  crypt_dec_pending reads io->error before calling atomic_dec_and_test. Another context, for example crypt_endio called from an interrupt, may set io->error and drop its reference between the read and the decrement. crypt_dec_pending then drops the last reference and completes the bio with the stale status - so a read that failed and was never decrypted, or a write that failed, is reported as successful.  The read was placed before the decrement by commit b35f8caa0890 (\"dm crypt: wait for endio to complete before destruction\"), because that commit freed dm_crypt_io before calling bio_endio. This is no longer the case, dm_crypt_io lives in the per-bio data now.  Read io->error after atomic_dec_and_test instead. atomic_dec_and_test is fully ordered, so no additional barrier is needed.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99138",
                                "url": "https://ubuntu.com/security/CVE-2026-99138",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  tcp: fix use-after-free in do_tcp_getsockopt(TCP_CC_INFO)  do_tcp_getsockopt() reads icsk->icsk_ca_ops and dereferences the get_info function pointer without rcu_read_lock(). With BPF struct_ops congestion control, ca_ops can point to dynamically allocated memory that is freed concurrently, resulting in a use-after-free when the kernel dereferences or calls through the stale pointer.    BUG: KASAN: slab-use-after-free in do_tcp_getsockopt+0x2037/0x23e0   Read of size 8 at addr ffff888013701258 by task exploit/149    do_tcp_getsockopt+0x2037/0x23e0 (net/ipv4/tcp.c:4564)    tcp_getsockopt+0x91/0xf0    __sys_getsockopt+0xf7/0x170  Fix this by wrapping the ca_ops load and get_info call within rcu_read_lock()/rcu_read_unlock(), and using READ_ONCE() to load the icsk_ca_ops pointer.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99100",
                                "url": "https://ubuntu.com/security/CVE-2026-99100",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: p54: validate firmware record lengths  The p54 firmware parser accesses component ID and component version records without checking that their lengths cover the fields being read. A malformed record can therefore make the parser read past the record.  Validate the component ID and component version record lengths before accessing their data. The descriptor record is also checked against the shortest descriptor length found in the supported firmware images.  Reject descriptor values that underflow the RX offset or produce an empty RX range before updating the driver state.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-28 04:18:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99140",
                                "url": "https://ubuntu.com/security/CVE-2026-99140",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  tracing: Fix hist trigger timestamps for buffered events  Syzkaller triggered a WARN_ON_ONCE(!nest) warning:    WARNING: kernel/trace/ring_buffer.c:821 at ring_buffer_event_time_stamp   Call trace:     ring_buffer_event_time_stamp     hist_field_timestamp     hist_fn_call     event_hist_trigger     event_triggers_call     __event_trigger_test_discard     trace_event_buffer_commit     do_trace_event_raw_event_sched_switch     trace_event_raw_event_sched_switch  The warning is probabilistically reproducible and is related to syzkaller executing the following commands:    echo 'prev_pid == 999999' > events/sched/sched_switch/filter   echo 'hist:keys=common_timestamp' > events/sched/sched_switch/trigger  The specific triggering process is as follows:  CPU 0                                           CPU 1 (context switching)                             (echo 'hist:keys=common_timestamp' > \\                                                        events/sched/sched_switch/trigger) do_trace_event_raw_event_##call   trace_event_buffer_lock_reserve     if (!tr->no_filter_buffering_ref &&         trace_file->flags & EVENT_FILE_FL_FILTERED)         return entry;  // return directly                                                 event_hist_trigger_parse                                                   hist_register_trigger                                                    tracing_set_filter_buffering(file->tr, true);                                                      tr->no_filter_buffering_ref++;     __trace_buffer_lock_reserve       rb_start_commit         local_inc(&cpu_buffer->committing);  // skipped and not executed   trace_event_buffer_commit     __event_trigger_test_discard       event_triggers_call         event_hist_trigger           hist_fn_call             hist_field_timestamp               ring_buffer_event_time_stamp                 nest = local_read(&cpu_buffer->committing);                 WARN_ON_ONCE(!nest)  // trigger warning  The root cause is that when an event file has a filter attached and the hist trigger has not yet been attached, trace_event_buffer_lock_reserve() writes the event into the per-CPU trace_buffered_event temp buffer instead of reserving it in the ring buffer, so cpu_buffer->committing is not incremented. When the event is later processed at commit time by a hist trigger, hist_field_timestamp() -> ring_buffer_event_time_stamp() sees a zero committing count, triggering WARN_ON_ONCE(!nest).  tracing_event_time_stamp() was added by commit d8279bfc5e959 (\"tracing: Add tracing_event_time_stamp() API\") for exactly this case: if the event is the per-CPU trace_buffered_event, it returns the current ring buffer timestamp. But it never gained a caller. Use it in hist_field_timestamp(), so that a hist trigger that races onto a buffered event records the current time, which is only marginally later than when the event was recorded, instead of warning and recording a bogus timestamp.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99150",
                                "url": "https://ubuntu.com/security/CVE-2026-99150",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  drm/amdgpu: don't drop the runtime PM reference twice in amdgpu_gpr  amdgpu_debugfs_gpr_read() drops its runtime PM reference right after reading the wave registers. When copying them to userspace fails, it jumps to the err label, which drops the reference a second time. A read into a bad buffer on Navi31 either steals a reference somebody else holds (power/runtime_usage goes from 1 to 0) or underflows the count:    amdgpu 0000:03:00.0: Runtime PM usage count underflow!  The registers are already in the kernel buffer at that point, so finish the hardware access first and copy the buffer with a single copy_to_user() instead of the put_user() loop with its own error path.  (cherry picked from commit 31035bbd74f7c3e10c163db875b8e67f8b50ee6a)",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99152",
                                "url": "https://ubuntu.com/security/CVE-2026-99152",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  scsi: libiscsi: Validate the task named by a management response  __iscsi_complete_pdu() fetches the task for five response types from one place and checks only that the index resolved:        case ISCSI_OP_LOGOUT_RSP:       case ISCSI_OP_LOGIN_RSP:       case ISCSI_OP_TEXT_RSP:       case ISCSI_OP_SCSI_TMFUNC_RSP:       case ISCSI_OP_NOOP_IN:               task = iscsi_itt_to_task(conn, hdr->itt);               if (!task)                       return ISCSI_ERR_BAD_ITT;  iscsi_itt_to_task() bounds the index against cmds_max and looks at nothing else, so a target can name any slot in the pool, including one that has never been used. task->conn is then NULL, and both iscsi_nop_out_rsp() and iscsi_complete_task() dereference it. One unsolicited NOP-In is enough; a Text Response carrying the same ITT crashes in iscsi_complete_task() instead.  Require the task to be in flight and not a SCSI command, the way iscsi_itt_to_ctask() does for the command opcodes.  [    6.298634] Oops: general protection fault, probably for non-canonical address 0xdffffc000000000c: 0000 [#1] SMP KASAN NOPTI [    6.298642] KASAN: null-ptr-deref in range [0x0000000000000060-0x0000000000000067] [    6.298652] CPU: 1 UID: 0 PID: 111 Comm: iscsistart Not tainted 7.2.0-rc5-ISCSI1-gf5098b6bae76 #1 PREEMPT(lazy) [    6.298654] Hardware name: QEMU Ubuntu 24.04 PC v2 (i440FX + PIIX, arch_caps fix, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 [    6.298656] RIP: 0010:iscsi_nop_out_rsp.constprop.0+0x46/0x160 [    6.298691] Code: c1 ea 03 48 83 ec 08 80 3c 02 00 0f 85 f5 00 00 00 48 b8 00 00 00 00 00 fc ff df 48 8b 6b 58 48 8d 7d 60 48 89 fa 48 c1 ea 03 <80> 3c 02 00 0f 85 c0 00 00 00 48 8b 45 60 48 39 c3 74 50 48 b8 00 [    6.298698] RSP: 0018:ffff88806c907be8 EFLAGS: 00010206 [    6.298701] RAX: dffffc0000000000 RBX: ffff888006116800 RCX: 0000000000000020 [    6.298702] RDX: 000000000000000c RSI: ffff88800525d578 RDI: 0000000000000060 [    6.298703] RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000 [    6.298706] R10: 0000000000000020 R11: 0000000000000000 R12: 0000000000000000 [    6.298706] R13: 000000000000002e R14: ffff8880056eb440 R15: ffff888006116800 [    6.298707] FS:  00007fc02d1c2740(0000) GS:ffff8880b29bc000(0000) knlGS:0000000000000000 [    6.298710] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [    6.298711] CR2: 000055fe3b56ddf8 CR3: 00000000053b9004 CR4: 0000000000770ef0 [    6.298712] PKRU: 55555554 [    6.298713] Call Trace: [    6.298714]  <IRQ> [    6.298714]  __iscsi_complete_pdu+0x13a8/0x22a0 [    6.298758]  iscsi_complete_pdu+0x54/0xa0 [    6.298759]  iscsi_tcp_hdr_recv_done+0x870/0x2c80 [    6.298778]  iscsi_tcp_recv_skb+0x31e/0xec0 [    6.298800]  iscsi_sw_tcp_recv+0x12f/0x390 [    6.298804]  __tcp_read_sock+0x1ab/0x810 [    6.298812]  iscsi_sw_tcp_data_ready+0x18b/0x510 [    6.298814]  tcp_rcv_established+0x1f56/0x3a00 [    6.298842]  tcp_v4_do_rcv+0x449/0x960 [    6.298847]  tcp_v4_rcv+0x2245/0x3bc0",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99153",
                                "url": "https://ubuntu.com/security/CVE-2026-99153",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  scsi: libiscsi: Validate the ITT reflected in a Reject PDU  A Reject PDU carries a copy of the header it rejects, and iscsi_handle_reject() takes the ITT out of that copy to find the task to clean up:        memcpy(&rejected_pdu, data, sizeof(struct iscsi_hdr));       ...       task = iscsi_itt_to_task(conn, rejected_pdu.itt);  That value is whatever the target put there. iscsi_itt_to_task() bounds the index against cmds_max and checks nothing else, so any task in the pool can be named, and iscsi_nop_out_rsp() then completes it.  An index that has never been used gives a NULL task->conn: the pool is zeroed at session setup and conn is assigned only when a task is allocated. If the task was used and returned, iscsi_complete_task() hits its WARN_ON_ONCE(task->state == ISCSI_TASK_FREE) and the refcount underflows. An in-flight SCSI command is completed as successful - a 1 MiB read returned 1048576 with none of its buffer written and no warning.  Validate the reflected ITT the way iscsi_itt_to_ctask() validates a command ITT, and require the task to be in flight and not a SCSI command.  [    6.248477] Oops: general protection fault, probably for non-canonical address 0xdffffc000000000c: 0000 [#1] SMP KASAN NOPTI [    6.249357] KASAN: null-ptr-deref in range [0x0000000000000060-0x0000000000000067] [    6.249951] CPU: 1 UID: 0 PID: 0 Comm: swapper/1 Not tainted 7.2.0-rc5-ISCSI1-gf5098b6bae76 #1 PREEMPT(lazy) [    6.250718] Hardware name: QEMU Ubuntu 24.04 PC v2 (i440FX + PIIX, arch_caps fix, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 [    6.251616] RIP: 0010:iscsi_nop_out_rsp.constprop.0+0x46/0x160 [    6.252043] Code: c1 ea 03 48 83 ec 08 80 3c 02 00 0f 85 f5 00 00 00 48 b8 00 00 00 00 00 fc ff df 48 8b 6b 58 48 8d 7d 60 48 89 fa 48 c1 ea 03 <80> 3c 02 00 0f 85 c0 00 00 00 48 8b 45 60 48 39 c3 74 50 48 b8 00 [    6.252813] RSP: 0018:ffff88806c907b80 EFLAGS: 00010206 [    6.253042] RAX: dffffc0000000000 RBX: ffff88800607e000 RCX: ffffffff8d571a25 [    6.253345] RDX: 000000000000000c RSI: ffff88806c907c38 RDI: 0000000000000060 [    6.253642] RBP: 0000000000000000 R08: 0000000000000000 R09: fffffbfff235a504 [    6.253947] R10: 0000000000000003 R11: 7463656e6e6f6320 R12: 0000000000000000 [    6.254251] R13: 0000000000000000 R14: ffff88806c907c38 R15: 0000000000000000 [    6.254549] FS:  0000000000000000(0000) GS:ffff8880d95bc000(0000) knlGS:0000000000000000 [    6.254887] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [    6.255140] CR2: 00007fc393e8ffc0 CR3: 0000000005252006 CR4: 0000000000770ef0 [    6.255439] PKRU: 55555554 [    6.255564] Call Trace: [    6.255674]  <IRQ> [    6.255768]  __iscsi_complete_pdu+0x18bf/0x22a0 [    6.256733]  iscsi_complete_pdu+0x54/0xa0 [    6.256905]  iscsi_tcp_data_recv_done+0xf4/0x250 [    6.257103]  iscsi_tcp_recv_skb+0x31e/0xec0 [    6.257680]  iscsi_sw_tcp_recv+0x12f/0x390 [    6.258061]  __tcp_read_sock+0x1ab/0x810 [    6.258853]  iscsi_sw_tcp_data_ready+0x18b/0x510 [    6.259808]  tcp_data_queue+0x1f13/0x4cd0 [    6.260567]  tcp_rcv_established+0x8a5/0x3a00 [    6.261931]  tcp_v4_do_rcv+0x449/0x960 [    6.262269]  tcp_v4_rcv+0x2245/0x3bc0",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99154",
                                "url": "https://ubuntu.com/security/CVE-2026-99154",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  scsi: libiscsi: Reject a negative task index from parse_pdu_itt  A transport that implements parse_pdu_itt hands libiscsi an index taken from the PDU, and both lookups bound it from above only:        if (i >= session->cmds_max)  i and cmds_max are both int, so a negative index passes and session->cmds[i] is read from before the array.  be2iscsi produces one. beiscsi_parse_pdu() assigns the raw tag,        *index = (int)itt;  and beiscsi_complete_pdu() forwards an unsolicited NOP-In from the hardware async ring without replacing its ITT, so the value is the target's. It also reports the session's own age rather than the one in the tag, which leaves the age comparison in iscsi_verify_itt() with nothing to reject.  Bound the index from below in both lookups.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99165",
                                "url": "https://ubuntu.com/security/CVE-2026-99165",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  sctp: revalidate output stream after association connect wait  When message interleaving is enabled, the first send waits for association establishment before building its data chunks.  The wait drops the socket lock, and handshake processing can reduce the output stream count to the peer-advertised inbound stream count.  sctp_stream_init() then frees the extension of every removed stream.  The sender resumes with the stream that it checked before the wait.  If the peer removed that stream, sctp_outq_tail() later dereferences its NULL extension.  Fatal-oops policies then panic the host.  KASAN: null-ptr-deref in range [0x38-0x3f] RIP: sctp_outq_tail+0x49e/0xaa0 Call Trace:  sctp_primitive_SEND  sctp_sendmsg_to_asoc  sctp_sendmsg  A range check alone is insufficient.  Stream reconfiguration can grow the output count again while the lock is released without recreating extensions freed by the earlier shrink.  The stream can then be in range while its extension remains NULL.  The send-buffer wait has the same issue.  Factor the range and extension checks into a helper and repeat both after each send-path wait that drops the socket lock.  Once the lock is reacquired, the validation remains stable through data creation and queueing.  If validation fails after the connect wait, the auto-created association is already established.  Return ESRCH so the existing caller path keeps it under state-machine ownership instead of freeing it directly, which would leave protocol, counter and socket state inconsistent.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99166",
                                "url": "https://ubuntu.com/security/CVE-2026-99166",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net: rds: fix uninitialized trans dereference in CM event handler  rds_rdma_cm_event_handler_cmn() assigns trans only when the RDMA device is an InfiniBand CA (RDMA_NODE_IB_CA).  On any other device type, e.g. an iWARP RNIC such as siw, trans stays uninitialized, but the event switch dereferences it: unconditionally in the RDMA_CM_EVENT_CONNECT_REQUEST case via trans->cm_handle_connect(), and (with a connection context) in the ROUTE_RESOLVED and ESTABLISHED cases.  An RDS listener on an iWARP device therefore crashes the kernel as soon as a connect request arrives: with CONFIG_INIT_STACK_ALL_ZERO the wild load becomes a NULL dereference at offset 0xa0 (&trans->cm_handle_connect) in the iw_cm_wq workqueue.  GCC masks the bug in default builds by folding the uninitialized load into &rds_ib_transport; Clang-built kernels take the real uninitialized path and oops.  The active side can land on a non-IB device too: the id that rds_ib_conn_path_connect() creates is not restricted to a node type, so rdma_resolve_addr() binds it to whichever device serves the local address, and an iWARP RNIC on the same netdev qualifies.  The crash there is different: resolving a route on an iWARP id never fills in cm_id->route.path_rec, and the ROUTE_RESOLVED case writes path_rec[0].sl before it calls into the transport.  The iWARP transport was dropped long ago and IB is the only transport left, so make that explicit: initialize trans to &rds_ib_transport at declaration, drop the conditional assignment, reject a connect request that arrives on a non-IB device, and drop a connection whose address resolved to one instead of resolving a route on it.  The rejection is limited to RDMA_CM_EVENT_CONNECT_REQUEST on purpose: a non-zero return from the handler makes rdma_cm destroy the id the event was delivered on, which is right for the request's freshly created id but would free a connection id that RDS still owns for any other event.  On the active side the id stays ic->i_cm_id and the connection's shutdown destroys it, so that case returns 0.  [achender: reject only on RDMA_CM_EVENT_CONNECT_REQUEST instead of  bailing out for every event on a non-IB device, so that rdma_cm does  not destroy connection ids RDS still tracks; drop a connection whose  address resolved to a non-IB device before a route is resolved on it;  changelog adjusted]",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99167",
                                "url": "https://ubuntu.com/security/CVE-2026-99167",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net/sched: fix use-after-free in __tcf_action_put()  __tcf_action_put() decrements the reference count before decrementing the binding count. Another thread can free the action between these operations, causing the binding-count update to access freed memory. KASAN reports it as:    BUG: KASAN: slab-use-after-free in __tcf_action_put+0x327/0x340   Write of size 4 at addr ff11000000d46420 by task tc-put-pause/64  Hold the action IDR mutex across both counter updates and IDR removal, keeping cleanup outside the lock.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99175",
                                "url": "https://ubuntu.com/security/CVE-2026-99175",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  fsnotify: prevent mark additions during connector teardown  fsnotify_destroy_marks() keeps a reference to its current mark while it drops conn->lock to destroy the mark. This stabilizes the forward-walk cursor, but does not prevent a new mark from being inserted before it. For example, an inotify watch re-added after IN_IGNORED sorts before the old, detached mark for the same group. The walk can miss the replacement and then detach the entire connector from the object.  The replacement is still on its group's marks_list and, for inotify, in the watch IDR. The group mutex no longer protects the connector's object from disappearing. An unprivileged fdinfo read racing the final detach can consequently call igrab(NULL):    BUG: KASAN: null-ptr-deref in igrab+0x24/0x100   Write of size 4 at addr 0000000000000148   Call Trace:    igrab+0x24/0x100    inotify_show_fdinfo+0x1dc/0x5e0    seq_show+0x397/0x690  Set a DESTROYING flag under conn->lock before starting the walk, and reject new marks on that connector with -ENOENT. The existing add-mark error paths undo the temporary group-list entry and the backend's watch allocation. Do not wait for teardown while holding the group mutex, which the destroyer needs. Once the old connector is detached, an add can install a fresh connector as before.  This closes the insertion race for all object types using the common connector teardown, without changing the mark reference or SRCU lifetime rules.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99176",
                                "url": "https://ubuntu.com/security/CVE-2026-99176",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  KVM: nVMX: Reset MMU back to the root MMU if loading L2 state fails for !VM-Entry  Reset the vCPU's MMU pointer back to the root MMU if loading L2 state fails in the \"not from VM-Entry\" case, i.e. when emulating RSM or handling KVM_SET_NESTED_STATE.  Failure to unwind the MMU pointer results in KVM trying to run L1 with a nested MMU, and is especially problematic if the vCPU manages to free its nested state before the VM crashes.  Constructing the root for a nested EPT MMU goes through vmcs12, which is dynamically allocated/freed when nVMX is enabled/disabled.  And so if the nested state is freed with the MMU still pointing at the nested MMU, KVM will hit a NULL pointer deref when attempting to get L1=>L2 EPTP.    BUG: kernel NULL pointer dereference, address: 0000000000000078   #PF: supervisor read access in kernel mode   #PF: error_code(0x0000) - not-present page   PGD 114a2d067 P4D 111743067 PUD 11141f067 PMD 0   Oops: Oops: 0000 [#1] SMP   CPU: 20 UID: 1000 PID: 1272 Comm: nested_tdp_faul Not tainted 7.3.0-rc4-8c89f11d1a99b-sink-vm #1914 PREEMPTLAZY   Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015   RIP: 0010:nested_ept_get_eptp+0xb/0x10 [kvm_intel]   Call Trace:    <TASK>    kvm_mmu_load+0xcd/0x870 [kvm]    kvm_arch_vcpu_ioctl_run+0x18f5/0x1f80 [kvm]    kvm_vcpu_ioctl+0x2c7/0x970 [kvm]    __x64_sys_ioctl+0x90/0xd0    do_syscall_64+0x9c/0x4d0    entry_SYSCALL_64_after_hwframe+0x4b/0x53   RIP: 0033:0x47491b    </TASK>   Modules linked in: kvm_intel kvm irqbypass   CR2: 0000000000000078   ---[ end trace 0000000000000000 ]---   RIP: 0010:nested_ept_get_eptp+0xb/0x10 [kvm_intel]  [sean: write changelog]",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99181",
                                "url": "https://ubuntu.com/security/CVE-2026-99181",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  autofs: ignore notification errors from a replaced pipe  autofs_notify_daemon() takes a reference to the current notification pipe under wq_mutex, then drops the mutex before writing the request. The write can block while the daemon enters catatonic mode and installs a replacement pipe.  If the old pipe's reader is then closed, the delayed write returns -EPIPE and the generic error path enters catatonic mode again. That transition acts on the current superblock state, closes the replacement pipe, and releases the new daemon generation's wait queues.  Only enter catatonic mode when the pipe which failed is still the current pipe. Factor the already-locked transition so the identity check and state change are atomic with respect to another replacement.  This was reproduced on v7.3-rc5-337-gff47652a4b66c in a local QEMU guest. An unprivileged UID 65534 lookup filled the old packet pipe before a normal CATATONIC/SETPIPEFD restart. On the unmodified kernel, the new pipe received HUP and both a pending victim lookup and a later lookup failed with ENOENT in two out of two fresh-mount runs.  With this change, the new pipe remained active, received an intact 304-byte request, and both victim lookups completed in two out of two runs. Normal lookup and restart-without-a-blocked-writer controls passed. No KASAN, oops, refcount, or lock diagnostic was observed. A source reproducer and complete local logs are available privately on request.  The demonstrated impact is limited to denial of a shared autofs service during a legitimate daemon restart. No memory corruption, information leak, privilege escalation, or code execution primitive was observed.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99201",
                                "url": "https://ubuntu.com/security/CVE-2026-99201",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  netlink: avoid hashing the network namespace pointer  The netlink rhashtable key includes a raw struct net pointer and a user-controlled port ID. Both /proc/net/netlink and socket diagnostics expose the table's bucket order. By binding and rebinding chosen NETLINK_USERSOCK port IDs, an unprivileged reader can distinguish equal buckets and recover the low bits of the Jenkins hash. Its 32-bit seed and the limited set of kernel-image slides can then be searched offline to recover the address of init_net.  Use the namespace's unique, non-address net_cookie in the comparison key instead. It is assigned before the per-net initializers run and remains unchanged for the namespace's lifetime. The lookup key and object hash are still built by netlink_compare_arg_init(), keeping lookup, insertion, removal and rehashing consistent while preserving namespace separation. Neither public table walker needs to change.  Reading the socket's namespace cookie in netlink_compare() is safe under RCU, including during namespace teardown. netlink_release() removes the socket from the hash table and defers its final put with call_rcu(). cleanup_net() runs the per-net exit methods and waits for outstanding RCU callbacks with rcu_barrier() before freeing namespace storage.  Unlike ns.ns_id, net_cookie is also available and initialized during setup_net() in older stable kernels, making the change straightforward to backport to v5.15 and later.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99203",
                                "url": "https://ubuntu.com/security/CVE-2026-99203",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  pipe: preserve existing fasync readers on writer setup failure  F_SETFL and FIOASYNC decide whether to invoke ->fasync() before pipe_fasync() takes pipe->mutex. Two enables of one O_RDWR FIFO can therefore both enter the callback.  fasync_helper() allocates before checking for an existing entry. If the first enable installs both entries, a second enable can update the reader entry and then fail the allocation for the writer entry. The error path removes the pre-existing reader entry, clearing FASYNC while the writer entry remains registered. __fput() then skips ->fasync(), so a later pipe notification can dereference the freed file or its f_owner. An unprivileged memory-pressure reproducer triggers a KASAN slab-use-after-free in send_sigio() through this path.  Keep the reader helper's result and undo the registration only if this call added it. The pipe mutex serializes changes to both lists, so a failed new registration still removes its reader, while a failed duplicate preserves the existing registrations and FASYNC. Successful duplicate enables continue to update fa_fd as before.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99204",
                                "url": "https://ubuntu.com/security/CVE-2026-99204",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ocfs2/dlm: Protect the recovery list during debugfs reads  Recovery participant records must remain alive while debug_state_print() walks reco.node_data and formats their fields. The formatter holds dlm->spinlock, but the recovery participant list is protected by dlm_reco_state_lock. In particular, dlm_destroy_recovery_area() detaches the list under dlm_reco_state_lock and frees the detached records after releasing it. A concurrent debugfs open can therefore read freed memory.  Protect the participant traversal and field reads in debug_state_print() with dlm_reco_state_lock, matching the existing list writers. This also serializes the traversal against list_add_tail() during recovery-area initialization. Make the existing lock available to the debug code through dlmcommon.h; the lock remains internal to the OCFS2 DLM module.  Release dlm->spinlock after formatting the other domain state and before acquiring dlm_reco_state_lock, so the debug reader does not nest the two locks. Leave recovery list insertion, detachment and freeing unchanged.  KASAN report as below:      BUG: KASAN: slab-use-after-free in debug_state_open+0x1169/0x12d0     Read of size 4 at addr ffff88810662ef80 by task dlm-state-stres/896      CPU: 1 UID: 0 PID: 896 Comm: dlm-state-stres Not tainted 7.3.0-rc4-next-20260921-pmb-ocfs2-functional-v1+ #1 PREEMPT(lazy)     Hardware name: QEMU Ubuntu 24.04 PC v2 (i440FX + PIIX, arch_caps fix, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014     Call Trace:      <TASK>      dump_stack_lvl+0x93/0xd0      print_report+0xce/0x630      ? debug_state_open+0x1169/0x12d0      ? srso_alias_return_thunk+0x5/0xfbef5      ? __virt_addr_valid+0x20e/0x420      ? debug_state_open+0x1169/0x12d0      kasan_report+0xe0/0x110      ? debug_state_open+0x1169/0x12d0      debug_state_open+0x1169/0x12d0      ? __pfx_debug_state_open+0x10/0x10      full_proxy_open_regular+0x193/0x310      do_dentry_open+0x595/0x12d0      ? __pfx_full_proxy_open_regular+0x10/0x10      vfs_open_consume+0xd1/0x400      ? srso_alias_return_thunk+0x5/0xfbef5      path_openat+0x18d0/0x2020      ? __pfx_path_openat+0x10/0x10      do_file_open+0x21e/0x470      ? __pfx_do_file_open+0x10/0x10      ? _raw_spin_unlock+0x23/0x40      ? srso_alias_return_thunk+0x5/0xfbef5      ? alloc_fd+0x3a6/0x6b0      do_sys_openat2+0xf4/0x1b0      ? __pfx_do_sys_openat2+0x10/0x10      ? srso_alias_return_thunk+0x5/0xfbef5      ? __fput+0x5b5/0xa60      __x64_sys_openat+0x136/0x1e0      ? __pfx___x64_sys_openat+0x10/0x10      do_syscall_64+0x114/0x620      entry_SYSCALL_64_after_hwframe+0x77/0x7f     [Register dump omitted.]      </TASK>      Allocated by task 880:      kasan_save_stack+0x33/0x60      kasan_save_track+0x14/0x30      __kasan_kmalloc+0xaa/0xb0      __kmalloc_cache_noprof+0x28d/0x610      dlm_remaster_locks+0x147/0x1d90      dlm_do_recovery+0xde1/0x1580      dlm_recovery_thread+0x109/0x300      kthread+0x351/0x460      ret_from_fork+0x659/0x940      ret_from_fork_asm+0x1a/0x30      Freed by task 880:      kasan_save_stack+0x33/0x60      kasan_save_track+0x14/0x30      kasan_save_free_info+0x3b/0x60      __kasan_slab_free+0x5f/0x80      kfree+0x308/0x580      dlm_destroy_recovery_area+0x285/0x460      dlm_remaster_locks+0x17c4/0x1d90      dlm_do_recovery+0xde1/0x1580      dlm_recovery_thread+0x109/0x300      kthread+0x351/0x460      ret_from_fork+0x659/0x940      ret_from_fork_asm+0x1a/0x30      The buggy address belongs to the object at ffff88810662ef80      which belongs to the cache kmalloc-32 of size 32     The buggy address is located 0 bytes inside of      freed 32-byte region [ffff88810662ef80, ffff88810662efa0)      [Page and memory-state dumps omitted.]",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99206",
                                "url": "https://ubuntu.com/security/CVE-2026-99206",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  scsi: target: iscsi: Fix race in discovery auth updates  Separate configfs opens can concurrently update the discovery AuthMethod parameter. Both callers may free the same value in iscsi_update_param_value(), causing a double-free.  Protect the lookup and replacement with the discovery TPG access lock, as used by the other TPG configfs parameter updates.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99211",
                                "url": "https://ubuntu.com/security/CVE-2026-99211",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  netlink: reset skb headers before unicast and multicast filtering  Socket filters can use SKF_NET_OFF and SKF_LL_OFF to read relative to an skb's network and MAC headers. Netlink producers may reserve headroom without resetting those headers, allowing a receiving socket's filter to read data before the initialized message.  For example, IWPM HELLO replies are allocated with dev_alloc_skb(), which reserves NET_SKB_PAD bytes. An unprivileged NETLINK_RDMA user can attach a classic socket filter and disclose this headroom through the length of the delivered reply. The resets in netlink_dump() do not help because IWPM sends a separately allocated skb through netlink_unicast().  Reset both headers before running the receiver's filter in unicast and broadcast delivery, as is already done for dump skbs. This also covers other netlink producers that reserve headroom without changing their allocation or message-building code.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99212",
                                "url": "https://ubuntu.com/security/CVE-2026-99212",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net/rds: don't let the rdma_cm destroy an id RDS still owns on route failure  rds_rdma_cm_event_handler_cmn() hands the return value of rdma_resolve_route() straight back to the rdma_cm on RDMA_CM_EVENT_ADDR_RESOLVED.  A synchronous failure there - -ENOMEM from the route work allocation, an SA query that cannot be set up, a RoCE route with no usable device - makes addr_handler() destroy the id the event was delivered on.  That id is ic->i_cm_id, and nothing clears the pointer: the connection sits in RDS_CONN_CONNECTING with a freed id until its shutdown calls rdma_disconnect() and rdma_destroy_id() on it.  The ROUTE_RESOLVED case already avoids this: rds_ib_cm_initiate_connect() forces a zero return while ic->i_cm_id == cm_id, as the comment there explains.  Do the same here - drop the connection and return 0 - so the id stays RDS's to destroy from the shutdown, and the reconnect gets a fresh one.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99213",
                                "url": "https://ubuntu.com/security/CVE-2026-99213",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  vsock: treat TCP_CLOSING as once-established  Handle the TCP_ESTABLISHED -> TCP_CLOSING transition on OP_RST, which can race with the connect loop. Immediately break and return 0 on ESTABLISHED/CLOSING. The return value of connect() should reflect what happened up to the point the connection was established or failed. Events that occur afterwards must not affect it. E.g. even if OP_RW has already set sk_err, connect() should still return 0, not ENOBUFS because of it. Adapt the inaccurate comment above signal_pending().  Resetting a socket that is still present in connected_table can lead to memory corruption. The reporter noted lost transports for in-flight skbs, and I have reproduced crashes caused by re-insertion into connected_table.    list_add double add: new=, prev=, next=.   kernel BUG at lib/list_debug.c:35!   Oops: invalid opcode: 0000 [#1] SMP KASAN NOPTI   Workqueue: vsock-loopback vsock_loopback_work   RIP: 0010:__list_add_valid_or_report+0x11f/0x130   Call Trace:    vsock_insert_connected.cold+0xe/0x13    virtio_transport_recv_pkt+0x10e9/0x1460    vsock_loopback_work+0x305/0x480    process_one_work+0xe4c/0x1560    worker_thread+0x4f1/0xd60    kthread+0x36e/0x470    ret_from_fork+0x47b/0x6b0    ret_from_fork_asm+0x1a/0x30  This fix is supplementary to commit 002541ef650b (\"vsock: Ignore signal/timeout on connect() if already established\"). Details under Link.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99216",
                                "url": "https://ubuntu.com/security/CVE-2026-99216",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  Drivers: hv: Don't reset VMBus connection state on error/exit paths  In two places, current code forces vmbus_connection.conn_state to DISCONNECTED prior to calling vmbus_disconnect(). But vmbus_disconnect() calls vmbus_initiate_unload(), which unloads the VMBus connection only if the conn_state is CONNECTED. Consequently, the connection remains and the Hyper-V host might continue to send messages or post VMBus interrupts.  The problem was introduced in commit 74347a99e73ae (\"x86/Hyper-V: Unload vmbus channel in hv panic callback\"), in that vmbus_initiate_unload() started checking the current connection state before doing the unload. This commit removed some occurrences where conn_state was forced to DISCONNECTED, but these two remained, apparently due to an oversight at the time.  Fix this by not forcing conn_state to DISCONNECTED during VMBus exit, or if a failure occurs when establishing the connection in the first place. Whatever value conn_state has at the time is then read by vmbus_initiate_unload() to determine if there is a connection to be unloaded.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2022-50167",
                                "url": "https://ubuntu.com/security/CVE-2022-50167",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  bpf: fix potential 32-bit overflow when accessing ARRAY map element  If BPF array map is bigger than 4GB, element pointer calculation can overflow because both index and elem_size are u32. Fix this everywhere by forcing 64-bit multiplication. Extract this formula into separate small helper and use it consistently in various places.  Speculative-preventing formula utilizing index_mask trick is left as is, but explicit u64 casts are added in both places.",
                                "cve_priority": "high",
                                "cve_public_date": "2025-06-18 11:15:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99082",
                                "url": "https://ubuntu.com/security/CVE-2026-99082",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  KVM: x86: Use active memslots for the per-vCPU MMIO cache  KVM tags the per-vCPU MMIO cache with a memslot generation so that a memslot update invalidates cached MMIO information.  Both the fill and validation paths use kvm_memslots(), which unconditionally selects address space 0, even when the vCPU is running in SMM and using address space 1.  Commit 56f17dd3fbc4 (\"kvm: x86: fix stale mmio cache bug\") added the memslot generation to the cache key so that a memslot update could not leave a stale entry valid.  When commit 699023e23965 (\"KVM: x86: add SMM to the MMU role, support SMRAM address space\") added the SMM address space, these helpers were not converted to use the active memslots.  Consequently, an update to the SMM memslots can leave an entry from the old SMM address space apparently valid after the vCPU returns to the normal address space.  A guest can then cause an access to valid RAM at the same GFN to be returned to userspace as KVM_EXIT_MMIO.  Completing that exit through the VMM's RAM address space writes the backing page without going through KVM's write-tracking path.  If the page backs a nested EPT table, KVM can continue using shadow translations derived from the old contents.  The WARN_ON_ONCE() in kvm_mmu_write_protect_fault() catches this invalid cache and memslot combination.  Use the vCPU's active memslots when caching and validating the entry. Memslot generations are unique across address spaces, so the generation also distinguishes the normal and SMM views.  This matches the MMIO SPTE cache, which already uses kvm_vcpu_memslots().  On an unpatched current-mainline kernel, a regression test that fills the cache in SMM and updates only the SMM memslots fails the intended RAM write and triggers the kvm_mmu_write_protect_fault() warning.  With this change, the same test completes the RAM write without a warning.  The x86/smm_test, set_memory_region_test, and memslot_modification_stress_test selftests also pass.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99083",
                                "url": "https://ubuntu.com/security/CVE-2026-99083",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ksmbd: fix heap out-of-bounds write in krb5_authenticate()  In krb5_authenticate(), out_len is calculated to determine available headroom in response_buf for the incoming Kerberos AP-REP token. However, when SMB2_SESSION_SETUP is processed as a non-first element of a compounded SMB2 request, the calculation omits work->next_smb2_rsp_hdr_off.  This causes out_len to overstate remaining buffer headroom by the cumulative size of prior responses in the compound chain. Consequently, the length check in ksmbd_krb5_authenticate() (*out_len <= resp->spnego_blob_len) passes erroneously, allowing memcpy() to write the AP-REP blob past the end of response_buf into adjacent kernel heap memory.  Fix this by subtracting work->next_smb2_rsp_hdr_off when computing out_len, ensuring it accurately reflects physical remaining buffer space.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98977",
                                "url": "https://ubuntu.com/security/CVE-2026-98977",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  namespace: handle mount locking for automounts correctly  If mounts are propagated across user namespaces, attach_recursive_mnt() locks every copy of the source mount to protect overmounts from vanishing and revealing the underlying files or directories.  The user namespace is taken from the caller's mount namespaces since this is where the mounts end up. Except, that's not always true. Automounts may legitimately get popped in by tasks located in a different mount and user namespace during path lookup.  Then check doesn't make sense at that point. The copy in the namespace of the parent - which may be the host's - is now locked and the host cannot change the flags of its own mounts anymore.  Here's the reproducer:  - host has debugfs mounted nosuid,nodev,noexec and shared - tracefs automount below it is not yet active - hand a child process a directory descriptor on that mount - child process enters auser and mount namespace - child process' namespace now holds a locked copy of the host's debugfs   mount that receives propagation from it - child process stats \"tracing/.\" through the descriptor - lookup runs on the host's mount so the automount lands below the host's mount - propagation puts a copy below the child's copy - both try to clear the flags on the mount they got, with a bind remount:      host, on its own automount:            MS_REMOUNT|MS_BIND = EPERM     child, on the copy in its namespace:   MS_REMOUNT|MS_BIND = 0  So the lock landed on the host's mount instead of the child's copy. Congrats. So we need to compare with the owner of the namespace the mount actually gets mounted on. For all regular cases that is the caller's mount namespace and so nothing changes.  Detached trees in anonymous mount namespaces by be handed over via SCM_RIGHTS or inherited in other ways on purpose so the attaching task's mount namespace is authoritative, not the creator of the detached tree.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98992",
                                "url": "https://ubuntu.com/security/CVE-2026-98992",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  namespace: don't copy an unmounted mount tree  may_copy_tree() accepts a mount whose root is an nsfs or pidfs file before it checks whether that mount is mounted. This exception exists for nsfs and pidfs mounts. They are part of no mount namespace so neither check_mnt() nor is_mounted() would let them through and bind-mounting a nsfsfd or a pidfd wouldn't work.  Problem is that exception also admits a bind mount of such a file when it was lazily unmounted and is only kept alive by a file descriptor:    mount --bind /proc/self/ns/net /tmp/x   exec 3< /tmp/x   umount -l /tmp/x   mount --rbind /proc/self/fd/3 /tmp/y  With MS_REC or AT_RECURSIVE copy_tree() doesn't stop at the unmounted mount. It copies every mount that stayed attached to it as well. So if you have a bunch of overmounts over the nsfsfd or the pidfd the whole unmounted stack is copied. That's a bug.  So refuse to walk an unmounted tree. Copying its root alone stays possible. So a bind mount of a namespace that is gone can still be recreated from a file descriptor on the old one. The file descriptor pins that mount and its root and __has_locked_children() only reads the direct children which don't leave the parent's list without namespace_sem. The internal mounts carry MNT_NS_INTERNAL instead of NULL and are still walked. Copying an unmounted tree recursively fails with EINVAL.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98981",
                                "url": "https://ubuntu.com/security/CVE-2026-98981",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  namespace: unhash a dentry before detaching the mounts on it  unlink(), rmdir() and rename() remove the entry from the filesystem, call detach_mounts() on the entry with the inode locked and then call d_delete() once the inode is unlocked.  The thing is that between detach_mounts() and d_delete() the dentry is still hashed and positive. But after detach_mounts() nothing covers the dentry anymore. A lookup that finds this dentry in the dcache can uncover what the mounts hid.  That's a problem when unlinking files or directories that are mountpoints in other mount namespaces. Everybody who had the underlying entry covered can race the detach_mount() call until d_delete() has run.  The race window isn't all that small. It encompasses namespace_unlock() with a full synchronize_rcu_expedited() grace period and the inode_unlock() of the entry.  In my experiments three walkers that kept trying read an overmounted file in 11938 of the 16140 unlinks that removed its mountpoint from a bind mount of the filesystem within a minute.  Fun fact, d_invalidate() has the same ordering problem but gets it right. It unhashes the dentry first and detaches the mounts afterwards. Let's do the same in __detach_mounts():  - A lookup that hasn't found the dentry yet misses it in the dcache and   waits for the directory lock that the caller holds until the name is   gone for good.  - A lockless lookup that found it already fails the mount_lock check   while the dentry still counts as a mountpoint and the d_seq check once   it doesn't, and retries.  This fixes the lockless path. We still need to fix the reference count lookup in a follow-up patch.  So d_drop() the dentry. The dentry stays positive and held but can't be found anymore. Then proceed with the detach and unlink.  Reproducer:  The reads were counted with the program below, three walkers for 60 s in a VM with 4 CPUs. The race window is stretched with the debug patch pasted here. fs.detach_race_walk_us sleeps in lookup_fast() once it found a mountpoint dentry and before its mounts are crossed. fs.detach_race_unlink_us sleeps in vfs_unlink() between detach_mounts() and d_delete().    // SPDX-License-Identifier: GPL-2.0   /*    * unlink_covered: unlink a file that is a mountpoint in a detached copy of    * its mount, against lookups that open it through that copy.    *    * A is a tmpfs with the file f1 (content SECRET_F) and the plain file    * MARK_A. A' is an open_tree(OPEN_TREE_CLONE) copy of A with MARK_A bound    * on A'/f1, held through an O_PATH fd on its root once the tree fd is    * closed. Walkers open f1 through that fd while the driver unlinks A/f1,    * where nothing is mounted on it. A walker may read MARK_A or get ENOENT.    * A read of SECRET_F is a hit: the name was found after its mount was    * gone. The lockless walks use openat2(RESOLVE_CACHED).    *    * usage: unlink_covered [-t seconds] [-w walkers]    */   #ifndef _GNU_SOURCE   #define _GNU_SOURCE   #endif   #include <errno.h>   #include <fcntl.h>   #include <pthread.h>   #include <stdatomic.h>   #include <stdio.h>   #include <stdlib.h>   #include <string.h>   #include <unistd.h>   #include <sys/mount.h>   #include <sys/stat.h>   #include <sys/syscall.h>   #include <linux/openat2.h>    #ifndef __NR_open_tree   #define __NR_open_tree 428   #endif   #ifndef __NR_move_mount   #define __NR_move_mount 429   #endif   #ifndef __NR_openat2   #define __NR_openat2 437   #endif   #ifndef OPEN_TREE_CLONE   #define OPEN_TREE_CLONE 1   #endif   #ifndef OPEN_TREE_CLOEXEC   #define OPEN_TREE_CLOEXEC O_CLOEXEC   #endif   #ifndef MOVE_MOUNT_F_EMPTY_PATH   #define MOVE_MOUNT_F_EMPTY_PATH 0x00000004   #endif    #define WORK \"/tmp/uc\"   #define ADIR WORK \"/A\"    static int duration = 60, nwalkers = 3;   static atomic_int stop, writer_waiting;   static pthread_rwlock_t cur_lock = PTHREAD_RWLOCK_INITIALIZER;   static int cur_fd = -1;\t\t/* the root of A', -1 wh ---truncated---",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99005",
                                "url": "https://ubuntu.com/security/CVE-2026-99005",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  drm/i915/gt: Unmask interrupts only when ACTIVE is true  There is a small race window between intel_rps_boost() reading a stale ACTIVE state and queuing rps->work, where ACTIVE may be changed via asynchronous calls triggered by wakeref drop. This means that rps_work() could be triggered after the GT has been parked, so unmasking RPS PM interrupts would happen without holding PM wakelock. This sequence of events may be observed during live_rc6_ctx_wa() selftest:  1) live_rc6_ctx_wa()    -> intel_engine_pm_put()       -> wakeref_put()  ASYNC1) wakeref_put() callback           -> __engine_park()              -> intel_gt_pm_put_async()                 -> intel_gt_pm_put_async_untracked()                    -> intel_wakeref_put_async()  ASYNC2) wakeref_put_async() callback           -> __gt_park()              -> intel_rps_park()                 -> intel_rps_clear_active() [clear ACTIVE]                 WITH INTERRUPTS:                 -> rps_disable_interrupts()                    -> cancel_work_sync(rps->work)                    -> rps_reset_interrupts() [rps->pm_iir = 0]                 WITHOUT INTERRUPTS (TIMER mode):                 -> rps_stop_timer()                    -> cancel_work_sync(rps->work)  2) live_rc6_ctx_wa()    -> intel_gt_wait_for_idle()       -> intel_gt_retire_requests_timeout()          -> dma_fence_wait_timeout()             -> ops->wait() [i915_fence_wait()]                -> i915_request_wait_timeout()                   -> intel_rps_boost()                      -> intel_rps_is_active() [check ACTIVE]                         [OPEN RACE WINDOW]                      -> queue_work(rps->work)          -> retire_requests()             -> i915_request_retire()                -> intel_rps_dec_waiters() [from 1 to 0]  If ASYNC1 and ASYNC2 would execute during [OPEN RACE WINDOW], then:  3) rps_work() executes from the workqueue and may satisfy    \"(!pm_iir && !client_boost)\" test (in TIMER mode rps->pm_iir    is zeroed by an earlier rps_work() call or never gets a new    value after previous intel_rps_unpark() event), so it jumps    to \"out\" label, bypassing intel_rps_is_active() guard and    executes gen6_gt_pm_unmask_irq();  4) GT is parked and runtime PM wakelock is dropped, so only    a raw reference in __gt_park() ->    intel_display_power_put_async() remains for 100ms, then the    MMIO write in gen6_gt_pm_unmask_irq() detects missing    wakelock via assert_rpm_wakelock_held() and emits    \"RPM wakelock ref not held during HW access\" tainting kernel.  Commit 3e7abf814193 (\"drm/i915: Extract GT render power state management\") dropped the \"if (rps->interrupts_enabled)\" guard that gen6_pm_rps_work() had around this unmask in i915_irq.c. INTEL_RPS_ACTIVE brackets the same window, since it is set in intel_rps_unpark() before rps_enable_interrupts() and rps_start_timer() and cleared in intel_rps_park() before rps_stop_timer() and rps_disable_interrupts().  Skip unmasking when RPS is no longer active (reaching unmask operation is independent of INTERRUPT mode). This does not prevent RPS operation from resuming on the next unpark. In interrupt mode, intel_rps_unpark() calls rps_enable_interrupts(), which enables and unmasks the PM interrupts. In timer mode, it calls rps_start_timer(), restarting periodic engine-busyness evaluation. The timer generates software RPS events and queues rps_work() directly, independently of PM interrupt delivery. Neither mode requires the late worker to unmask interrupts while the GT is parked  (cherry picked from commit ca4a6deadad15b91ee083afe445fa6bdbfb68206)",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99007",
                                "url": "https://ubuntu.com/security/CVE-2026-99007",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  drm/fb-helper: defer setup when fbdev_probe() fails, not just on -EAGAIN  __drm_fb_helper_initial_config_and_unlock() calls drm_client_modeset_probe() first, which already fills in each mode_set->mode/num_connectors for every connected output, and only afterwards calls drm_fb_helper_single_fb_probe() to create fb_helper->fb and wire it into those mode_sets via drm_setup_crtcs_fb().  If drm_fb_helper_single_fb_probe() fails with anything other than -EAGAIN (e.g. dev->driver->fbdev_probe() itself fails), the function bails out before drm_setup_crtcs_fb() runs and before setting fb_helper->deferred_setup. The client is left with mode_sets that have a mode and connectors but mode_set->fb == NULL, and nothing marks this fb_helper as needing a retry.  __drm_fb_helper_restore_fbdev_mode_unlocked() only skips committing when fb_helper->deferred_setup is set, so a later .restore() call (drm_lastclose() on process exit, in this report) commits the stale mode_set through drm_client_modeset_commit() -> drm_client_modeset_commit_atomic() -> __drm_atomic_helper_set_config(), which hits WARN_ON(!set->fb).  Mark fb_helper->deferred_setup on any drm_fb_helper_single_fb_probe() failure, not just -EAGAIN, so restore keeps skipping the commit until a later hotplug event successfully re-probes and re-populates mode_set->fb. The real error code is still returned to the caller unchanged.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99019",
                                "url": "https://ubuntu.com/security/CVE-2026-99019",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  scsi: ch: Do not keep references to data transfer element devices  ch_readconfig() looks up the scsi_device of every data transfer element whose SCSI id the changer reports in READ ELEMENT STATUS, and stores it in ch->dt[]. scsi_device_lookup() takes a reference, and nothing ever drops it: ch_destroy() frees the array with kfree(). ch->dt[] is read nowhere else - it only supplies the vendor, model and revision printed in the same loop.  Once such a drive is removed, its scsi_device can never be released. It stays on the host's device list at its address, so a new device there is refused by anything that walks the list - target_core_pscsi reports \"scsi_device_get() failed for H:C:T:L\" - and the low-level driver's module can no longer be unloaded. Only a reboot recovers.  It shows with any changer that reports its drives' ids; with the mhvtl virtual library (IBM 3573-TL personality), each create and remove of a library with four drives leaves four references behind, counted by the module's use count in lsmod. With ch not bound the count is unchanged, and with this patch applied it is unchanged too.  Drop the reference as soon as the name has been printed, and remove the now unused dt[] array. That also removes the array leaked when ch_probe() fails after ch_readconfig().  The same leak was reported with an RFC patch in 2022, which was not merged.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99024",
                                "url": "https://ubuntu.com/security/CVE-2026-99024",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  optee: register TEE devices only once fully initialized  optee_probe() called tee_device_register() on both the client and the supplicant device before the rest of struct optee had been initialized.  tee_device_register() calls cdev_device_add(), which does two things at once: it creates /dev/tee0 and /dev/teepriv0, and it links the device into the tee class so that class_find_device() can find it. From that moment on the device is reachable both from user space via tee_open() and from kernel space via tee_client_open_context(). The only gate in teedev_open() is tee_device_get(), which merely checks that teedev->desc is non-NULL, which was already set by tee_device_alloc(). Therefore, there is effectively no gate at all.  A context opened in that window can run against a struct optee where    - optee->call_queue.mutex is not initialized by optee_cq_init()   - optee->supp mutex and completions is not initialized by     optee_supp_init()   - optee->rpmb_dev_mutex is not initialized yet,   - the message argument cache is not initialized by     optee_shm_arg_cache_init()   - optee->ctx is still NULL  Any open session or invoke during this window takes uninitialized mutexes and dereferences a NULL pointer.  Fix it by moving both tee_device_register() calls down to the point where all of struct optee is set up.  [JW: adding fixes and cc]",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99036",
                                "url": "https://ubuntu.com/security/CVE-2026-99036",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  dm: fix reading free memory in do_resume  When do_resume calls dm_table_get_mode(new_map), the call is done without holding any locks (it only holds a reference to the md). It may be possible that another concurrent ioctl on the same device will swap table after dm_swap_table and before dm_table_get_mode. In this case, dm_table_get_mode(new_map) reads freed memory.  This race condition was triggered by syzbot.  This commit fixes the race by reading mode of the new table before dm_swap_table. Note that new_map is also passed to dm_ima_need_measure, but this function doesn't attempt to dereference it, so this call should be safe.  Note that this is not a security bug because only root can trigger it and the commonly used tools such as lvm or cryptsetup do not call the ioctls concurrently, so that they can't trigger it acceidentally.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98985",
                                "url": "https://ubuntu.com/security/CVE-2026-98985",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  namespace: check the mounts before reading their parents in pivot_root()  path_pivot_root() reads the parents of new_root and of the caller's root and checks whether they are shared before it checks that either mount is in the caller's mount namespace. Only namespace_sem is held. That's fine for a mount that is in the caller's mount namespace.  But new_root can be a file descriptor to a mount that has been unmounted and that only the file descriptor keeps alive. If that mount stayed attached to its parent when it was unmounted nothing pins the parent for it. The final mntput() of the parent unhooks the children under mount_lock alone and frees the parent afterwards:    pivot_root()                     close(fd), last ref on the parent   ------------                     ---------------------------------   ex_parent = new_mnt->mnt_parent                                    mntput_no_expire_slowpath()                                      __umount_mnt(new_mnt)                                    cleanup_mnt()                                      call_rcu()   IS_MNT_SHARED(ex_parent)    BUG: KASAN: slab-use-after-free in path_pivot_root+0xf1a/0x1840   Read of size 4 at addr ffff8881047382f8 by task pivot_widen/157    path_pivot_root+0xf1a/0x1840    __x64_sys_pivot_root+0x165/0x190  The same goes for the caller's root via chroot(). Both outcomes of the check end in EINVAL so nothing but the read itself goes wrong. It's the same thing commit bb4609405752 (\"statmount: read the parent of an unmounted mount under mount_lock\") fixed for statmount().  Check that both mounts are in the caller's namespace before their parents are read. Every path returns EINVAL either way.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98993",
                                "url": "https://ubuntu.com/security/CVE-2026-98993",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  namespace: don't inherit MNT_UMOUNT in clone_mnt()  MNT_UMOUNT gets raised on a mount that umount_tree() or umount_one() has taken out of its namespace. It's never cleared. __detach_mounts() unhooks a mount that carries it instead of unmounting it.  disconnect_mount() lets an unmounted child stay attached only if its parent carries it. propagate_umount() takes it as the sign that a mount is going to be unmounted when it decides what else can be unmounted, where a chain of locked mounts ends and where a for reparenting an overmount.  clone_mnt() copies the flags of the source and only masks MNT_INTERNAL_FLAGS which doesn't include MNT_UMOUNT. A mount that was lazily unmounted but is kept alive by a file descriptor can still be copied when its root is an nsfs or pidfs file because may_copy_tree() accepts those before checking whether the source is mounted at all:    mount --bind /proc/self/ns/net /tmp/x   exec 3< /tmp/x   umount -l /tmp/x   mount --bind /proc/self/fd/3 /tmp/y  The mount on /tmp/y is attached to the caller's namespace with MNT_UMOUNT already set and every copy of it inherits the flag again.  That causes a number of bugs:  - Unlink its mountpoint from a mount namespace where it isn't one.   __detach_mounts() takes it for a mount that was unmounted earlier,   unhooks it from its parent and drops the reference the namespace   holds on it. It stays in the namespace with one reference too few   and as its own parent, so it can't be unmounted through the file   descriptor anymore and the namespace never finds it again. When the   namespace goes away it's leaked and points to a freed struct   mnt_namespace that may_change_propagation() and anon_ns_root() read   on the next propagation change or mount_setattr() through the file   descriptor.  - Make it shared and unmount a peer. trace_transfers() follows the   flag from the peer into it and strips it from its peer group.  - Let a propagated umount reach it. gather_candidates() marks it with   T_UMOUNT_CANDIDATE but never puts it on the candidate list, so the   mark is never cleared and every later propagated umount skips it. If   it's the parent of a locked mount handle_locked() takes it as the   cutoff and commits the locked child that should have stayed and   disconnect_mount() leaves that child attached to it, unmounted under   a mounted parent, which is what disconnect_mount() exists to   prevent. When the namespace goes away umount_tree() visits the child   a second time. And once __detach_mounts() has made it its own parent   reparent() never finds the end of the chain of unmounted parents.  A clone is a new mount that has never been unmounted. Add MNT_UMOUNT to MNT_INTERNAL_FLAGS so clone_mnt() never copies it. And warn when umount_tree() reaches a mount that already has it set.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99002",
                                "url": "https://ubuntu.com/security/CVE-2026-99002",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  drm/vmwgfx: validate pitch coming from userspace  Validate the pitch, alongside the box dimensions before trying to copy data from the underlying surface. Fixes possible out of bounds reads with cursor snooping.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99027",
                                "url": "https://ubuntu.com/security/CVE-2026-99027",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net: team: stop reusing skb after queue override  A nonzero dev_queue_xmit() result does not return ownership of the skb. When an override port's qdisc drops it, the queue override helper used to try another port or the mode transmit op with the freed skb.  Return the handoff decision separately from transmit success. Select only the first override port under RCU and stop after handing it the skb, regardless of the lower transmit result. Keep the existing success and drop accounting.    BUG: KASAN: slab-use-after-free in sk_skb_reason_drop   Write of size 4 by task poc/5040   sk_skb_reason_drop (net/core/skbuff.c:1240)   dev_kfree_skb_any_reason (net/core/dev.c:3470)   ab_transmit (drivers/net/team/team_mode_activebackup.c:49)   team_xmit (drivers/net/team/team_core.c:1849)   __dev_direct_xmit (net/core/dev.c:4934)   Freed by task 5040:   __tcf_kfree_skb_list (net/sched/sch_generic.c:43)   __dev_queue_xmit (net/core/dev.c:4831)   team_xmit (drivers/net/team/team_core.c:1846)   Kernel panic - not syncing: KASAN: panic_on_warn set ...",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-64190",
                                "url": "https://ubuntu.com/security/CVE-2026-64190",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net: team: fix NULL pointer dereference in team_xmit during mode change  __team_change_mode() clears team->ops with memset() before restoring safe dummy handlers via team_adjust_ops(). A concurrent team_xmit() running under RCU on another CPU can read team->ops.transmit during this window and call a NULL function pointer, crashing the kernel.  The race requires a mode change (CAP_NET_ADMIN) concurrent with transmit on the team device.   BUG: kernel NULL pointer dereference, address: 0000000000000000  Oops: 0010 [#1] SMP KASAN NOPTI  RIP: 0010:0x0  Call Trace:   team_xmit (drivers/net/team/team_core.c:1853)   dev_hard_start_xmit (net/core/dev.c:3904)   __dev_queue_xmit (net/core/dev.c:4871)   packet_sendmsg (net/packet/af_packet.c:3109)   __sys_sendto (net/socket.c:2265)  The original code assumed that no ports means no traffic, so mode changes could freely memset()/memcpy() the ops.  AF_PACKET with forced carrier breaks that assumption.  Prevent the race instead of making it safe: replace memset()/memcpy() with per-field updates that never touch transmit or receive.  Those two handlers are managed solely by team_adjust_ops(), which already installs dummies when tx_en_port_count == 0 (always true during mode change since no ports are present).  WRITE_ONCE/READ_ONCE prevent store/load tearing on the handler pointers.  synchronize_net() before exit_op() drains in-flight readers that may still reference old mode state from before port removal switched the handlers to dummies.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-07-20 17:18:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99041",
                                "url": "https://ubuntu.com/security/CVE-2026-99041",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ip6_gre: remove obsolete ERSPAN PMTU update  A tc tunnel_key action can attach a METADATA_IP_TUNNEL dst to an skb, and mirred can redirect it to a native ip6erspan device. The legacy PMTU update in ip6erspan_tunnel_xmit() treats that metadata dst as a route. Since it has no output device, dst_dev(dst)->mtu dereferences NULL.  On v7.2 with KASAN, an initial UID/GID 65534 process with CapEff 0 used self-created user and network namespaces to trigger:    KASAN: null-ptr-deref   RIP: ip6erspan_tunnel_xmit+0x10fc/0x2cc0   Kernel panic - not syncing: Fatal exception in interrupt  The update is obsolete. Commit fe1a4ca0a2b7 (\"ip6_gre: process toobig in a better way\") changed IPv6 GRE Too Big handling to update the underlay route and removed the equivalent block from __gre6_xmit(). ip6_tnl_xmit() then propagates the underlay PMTU to the overlay route.  Remove the stale ERSPAN copy and its now-unused dst variable. This eliminates the metadata-dst dereference and keeps ERSPAN aligned with IPv6 GRE PMTU handling.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-97935",
                                "url": "https://ubuntu.com/security/CVE-2026-97935",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  tracing: Set the trace clock before registering the histogram trigger  hist_register_trigger() puts the trigger on the global named_triggers list in cmd_ops->init(), and only then sets the trace clock:  \tif (data->cmd_ops->init) { \t\tret = data->cmd_ops->init(data); \t\tif (ret < 0) \t\t\tgoto out; \t}  \tif (hist_data->enable_timestamps) { \t\tret = tracing_set_clock(file->tr, hist_data->attrs->clock); \t\tif (ret) { \t\t\thist_err(tr, HIST_ERR_SET_CLOCK_FAIL, errpos(clock)); \t\t\tgoto out; \t\t}  The clock string is not checked anywhere before that call, so a named trigger using common_timestamp with an unknown clock fails after it has already become findable. event_hist_trigger_parse() then frees it without taking it off the list, and the next lookup by name reads the freed object:   ~# cd /sys/kernel/tracing/events/sched/sched_switch  ~# echo 'hist:name=foo:keys=common_pid:ts=common_timestamp:clock=bogus' > trigger  bash: echo: write error: Invalid argument  ~# echo 'hist:name=foo:keys=common_pid' > trigger    BUG: KASAN: slab-use-after-free in find_named_trigger+0xac/0xc0   Read of size 8 at addr ffff88800915d760 by task init/1    find_named_trigger+0xac/0xc0    hist_register_trigger+0xc1/0x900    event_hist_trigger_parse+0x3146/0x6af0    event_trigger_write+0xce/0x160   Freed by task 63:    kfree+0x154/0x420    trigger_kthread_fn+0xfd/0x160  Set the clock before the trigger is registered, so that nothing which can fail runs after it is published, the way commit 6f86bdeab633 (\"tracing: Fix bad hist from corrupting named_triggers list\") moved the registration below the rest of the setup.  tracing_set_filter_buffering() is reference counted, so the init failure path has to drop the reference that the clock block now takes first.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-09-25 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98944",
                                "url": "https://ubuntu.com/security/CVE-2026-98944",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  HID: steam: Refactor registration  This refactors and simplifies the registration/unregistration flow. Since we now only perform registration when the client isn't opened anymore, the logic for handling that can be removed, and the rest of the function streamlined.  We also remove the previous assumption that we have a serial number to show we're registered, replacing it with a single purpose boolean.  In a previous refactor the code for unregistering a battery if later registration steps failed was accidentally left out. As a result, a lingering power_supply object could get left over after the steam object was torn down. This is also fixed here.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98945",
                                "url": "https://ubuntu.com/security/CVE-2026-98945",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  HID: steam: Rearrange teardown sequence  This fixes a narrow window during the teardown sequence where callbacks could still be scheduled during cleanup that would then have a dangling pointer to the now-freed steam struct.  This also puts work canceling for rumble and mode switch in steam_unregister, as that shouldn't persist while the client hdev is open.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2025-40135",
                                "url": "https://ubuntu.com/security/CVE-2025-40135",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ipv6: use RCU in ip6_xmit()  Use RCU in ip6_xmit() in order to use dst_dev_rcu() to prevent possible UAF.",
                                "cve_priority": "high",
                                "cve_public_date": "2025-11-12 11:15:00 UTC"
                            },
                            {
                                "cve": "CVE-2025-38728",
                                "url": "https://ubuntu.com/security/CVE-2025-38728",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  smb3: fix for slab out of bounds on mount to ksmbd  With KASAN enabled, it is possible to get a slab out of bounds during mount to ksmbd due to missing check in parse_server_interfaces() (see below):   BUG: KASAN: slab-out-of-bounds in  parse_server_interfaces+0x14ee/0x1880 [cifs]  Read of size 4 at addr ffff8881433dba98 by task mount/9827   CPU: 5 UID: 0 PID: 9827 Comm: mount Tainted: G  OE       6.16.0-rc2-kasan #2 PREEMPT(voluntary)  Tainted: [O]=OOT_MODULE, [E]=UNSIGNED_MODULE  Hardware name: Dell Inc. Precision Tower 3620/0MWYPT,  BIOS 2.13.1 06/14/2019  Call Trace:   <TASK>  dump_stack_lvl+0x9f/0xf0  print_report+0xd1/0x670  __virt_addr_valid+0x22c/0x430  ? parse_server_interfaces+0x14ee/0x1880 [cifs]  ? kasan_complete_mode_report_info+0x2a/0x1f0  ? parse_server_interfaces+0x14ee/0x1880 [cifs]    kasan_report+0xd6/0x110    parse_server_interfaces+0x14ee/0x1880 [cifs]    __asan_report_load_n_noabort+0x13/0x20    parse_server_interfaces+0x14ee/0x1880 [cifs]  ? __pfx_parse_server_interfaces+0x10/0x10 [cifs]  ? trace_hardirqs_on+0x51/0x60  SMB3_request_interfaces+0x1ad/0x3f0 [cifs]  ? __pfx_SMB3_request_interfaces+0x10/0x10 [cifs]  ? SMB2_tcon+0x23c/0x15d0 [cifs]  smb3_qfs_tcon+0x173/0x2b0 [cifs]  ? __pfx_smb3_qfs_tcon+0x10/0x10 [cifs]  ? cifs_get_tcon+0x105d/0x2120 [cifs]  ? do_raw_spin_unlock+0x5d/0x200  ? cifs_get_tcon+0x105d/0x2120 [cifs]  ? __pfx_smb3_qfs_tcon+0x10/0x10 [cifs]  cifs_mount_get_tcon+0x369/0xb90 [cifs]  ? dfs_cache_find+0xe7/0x150 [cifs]  dfs_mount_share+0x985/0x2970 [cifs]  ? check_path.constprop.0+0x28/0x50  ? save_trace+0x54/0x370  ? __pfx_dfs_mount_share+0x10/0x10 [cifs]  ? __lock_acquire+0xb82/0x2ba0  ? __kasan_check_write+0x18/0x20  cifs_mount+0xbc/0x9e0 [cifs]  ? __pfx_cifs_mount+0x10/0x10 [cifs]  ? do_raw_spin_unlock+0x5d/0x200  ? cifs_setup_cifs_sb+0x29d/0x810 [cifs]  cifs_smb3_do_mount+0x263/0x1990 [cifs]",
                                "cve_priority": "high",
                                "cve_public_date": "2025-09-04 16:15:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-31678",
                                "url": "https://ubuntu.com/security/CVE-2026-31678",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  openvswitch: defer tunnel netdev_put to RCU release  ovs_netdev_tunnel_destroy() may run after NETDEV_UNREGISTER already detached the device. Dropping the netdev reference in destroy can race with concurrent readers that still observe vport->dev.  Do not release vport->dev in ovs_netdev_tunnel_destroy(). Instead, let vport_netdev_free() drop the reference from the RCU callback, matching the non-tunnel destroy path and avoiding additional synchronization under RTNL.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-04-25 09:16:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99088",
                                "url": "https://ubuntu.com/security/CVE-2026-99088",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net: openvswitch: validate transport header presence in set_ipv6_addr  When executing IPv6 address rewrite actions on IPv6 fragments, set_ipv6_addr() calls update_ipv6_checksum(). If parse_ipv6hdr() processes a non-first IPv6 fragment, it sets key->ip.proto to NEXTHDR_FRAGMENT and returns early without calling skb_set_transport_header().  update_ipv6_checksum() unconditionally evaluates skb_transport_offset() on entry before checking l4_proto.  Because skb->transport_header is uninitialized, this triggers a warning under CONFIG_DEBUG_NET=y although it is completely harmless.  Fix this by returning early in update_ipv6_checksum() if l4_proto is NEXTHDR_FRAGMENT. This avoids reading the uninitialized transport offset for fragments while preserving the debug warning for any other protocol where the transport header is unexpectedly missing.  See the syzbot trace:  !skb_transport_header_was_set(skb) WARNING: ./include/linux/skbuff.h:3075 at skb_transport_header include/linux/skbuff.h:3075 [inline], CPU#1: syz-executor463/5635 WARNING: ./include/linux/skbuff.h:3075 at skb_transport_offset include/linux/skbuff.h:3250 [inline], CPU#1: syz-executor463/5635 WARNING: ./include/linux/skbuff.h:3075 at update_ipv6_checksum net/openvswitch/actions.c:361 [inline], CPU#1: syz-executor463/5635 WARNING: ./include/linux/skbuff.h:3075 at set_ipv6_addr+0x462/0x660 net/openvswitch/actions.c:399, CPU#1: syz-executor463/5635 [...] RIP: 0010:skb_transport_header include/linux/skbuff.h:3075 [inline] RIP: 0010:skb_transport_offset include/linux/skbuff.h:3250 [inline] RIP: 0010:update_ipv6_checksum net/openvswitch/actions.c:361 [inline] RIP: 0010:set_ipv6_addr+0x462/0x660 net/openvswitch/actions.c:399 [...] Call Trace:  <TASK>  set_ipv6 net/openvswitch/actions.c:531 [inline]  do_execute_actions+0x557e/0x8600 net/openvswitch/actions.c:1366  ovs_execute_actions+0xde/0x520 net/openvswitch/actions.c:1592  ovs_packet_cmd_execute+0xb4f/0xf10 net/openvswitch/datapath.c:705  genl_family_rcv_msg_doit+0x233/0x340 net/netlink/genetlink.c:1114  genl_rcv_msg+0x614/0x7a0 net/netlink/genetlink.c:1209  netlink_rcv_skb+0x226/0x4a0 net/netlink/af_netlink.c:2572  genl_rcv+0x28/0x40 net/netlink/genetlink.c:1218  netlink_unicast+0x7bd/0x940 net/netlink/af_netlink.c:1361  netlink_sendmsg+0x813/0xb40 net/netlink/af_netlink.c:1916  sock_sendmsg_nosec+0x14e/0x190 net/socket.c:800",
                                "cve_priority": "negligible",
                                "cve_public_date": "2026-10-26 15:16:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98950",
                                "url": "https://ubuntu.com/security/CVE-2026-98950",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  flow_dissector: avoid u16 truncation of hlen in bpf_flow_dissect()  bpf_flow_dissect() sanitizes the offsets returned by the BPF program with clamp_t(u16, ..., hlen).  If hlen is bigger than 65535, the upper bound is truncated before the comparison. For instance, with hlen == 65536, both nhoff and thoff are forced to zero, even if the program returned sane values.  This is the same class of bug as the one fixed in commit 99bda1ecbd56 (\"flow_dissector: avoid u16 truncation of skb->len when computing thoff\"). That fix does not cover the BPF path, because __skb_flow_dissect() returns early when a BPF flow dissector handles the packet.  struct bpf_flow_keys stores nhoff and thoff as u16, so cap hlen to U16_MAX before clamping.  Found by sashiko while reviewing the commit above.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98955",
                                "url": "https://ubuntu.com/security/CVE-2026-98955",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  flow_dissector: avoid u16 truncation of skb->len when computing thoff  __skb_flow_dissect() computes key_control->thoff using:    key_control->thoff = min_t(u16, nhoff, skb ? skb->len : hlen);  min_t(u16, ...) casts both arguments to u16 before comparing them. Whenever skb->len (or hlen) modulo 65536 is smaller than nhoff, the truncated length wins and thoff is set to a bogus small value, even when the dissection succeeded. For example, an IPv4/TCP frame with skb->len == 65540 and nhoff == 34 gets thoff == 4, so callers such as skb_probe_transport_header() point the transport header inside the Ethernet header.  Such skbs are not exotic: - At the time of commit d0c081b49137 (\"flow_dissector: properly cap   thoff field\"), AF_PACKET with PACKET_VNET_HDR could already build GSO   skbs larger than 64KB (MTU checks are skipped for GSO, and   alloc_skb_with_frags() accepted up to MAX_SKB_FRAGS (17) order-0   pages on top of the linear part). - BIG TCP now makes skbs larger than 64KB common. - The following patch makes tun_get_user() dissect IFF_TAP frames   before eth_type_trans() pulls the Ethernet header, so a GSO frame   carrying a 65522..65535 byte L3 packet will be dissected with   skb->len in [65536, 65549].  Compare as u32 instead. If the resulting offset cannot be represented in the u16 key_control->thoff, cap it to U16_MAX and report the dissection as failed rather than silently returning a wrong transport offset. thoff is still set on failure, as some callers (such as eth_get_headlen()) use it regardless of the return value.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99089",
                                "url": "https://ubuntu.com/security/CVE-2026-99089",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ASoC: samsung: i2s: enable op_clk in probe to balance runtime PM  The probe function puts the device into the runtime PM active state with only the \"iis\" bus clock enabled, but it also sets priv->op_clk to the parent of the RCLK_SRC mux without enabling it. The runtime PM suspend callback disables both clocks, so the first runtime suspend after probe disables op_clk once more than it was enabled.  On Exynos5250 Arndale both clocks resolve to the same EXYNOS_I2S_BUS gate, so this triggers the following warning during boot:   WARNING: drivers/clk/clk.c:1270 at clk_core_disable+0xe4/0x23c, CPU#0: kworker/u8:3/45  i2s_bus already disabled  ...  Workqueue: pm pm_runtime_work  Call trace:   ...   clk_core_disable from clk_disable+0x28/0x34   clk_disable from i2s_runtime_suspend+0x58/0x68 [snd_soc_i2s]   i2s_runtime_suspend [snd_soc_i2s] from genpd_runtime_suspend+0xc4/0x298   genpd_runtime_suspend from __rpm_callback+0x48/0x18c   __rpm_callback from rpm_callback+0x4c/0x50   rpm_callback from rpm_suspend+0xf4/0x718   rpm_suspend from pm_runtime_work+0x9c/0xa0   ...  Fix this by enabling op_clk in probe right after getting it, so the clock state matches the runtime PM active state, and by disabling it in remove.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-26 15:16:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98956",
                                "url": "https://ubuntu.com/security/CVE-2026-98956",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ASoC: adau1372: allow sleepy powerdown GPIOs  gpiod_set_value() emits a WARN when the GPIO provider indicates that it can sleep, as is typical for I2C controlled GPIO expanders. Since the powerdown GPIO is only manipulated in process context, use the _cansleep variant instead. This lets the driver use sleepy GPIOs to power off the chip.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98964",
                                "url": "https://ubuntu.com/security/CVE-2026-98964",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  nvmet: use the local P2P device on metadata allocation failure  nvmet_req_alloc_p2pmem_sgls() assigns req->p2p_dev only after the data and metadata SGL allocations succeed. If the data allocation succeeds but the metadata allocation fails, out_free_sg passes req->p2p_dev to pci_p2pmem_free_sgl() before that assignment has taken place.  Pass the local p2p_dev argument instead, so cleanup uses the same PCI device as the successful data allocation.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98967",
                                "url": "https://ubuntu.com/security/CVE-2026-98967",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  cxgb4/ch_ktls: disable softirqs around tid_list erases  chcr_ktls_cpl_act_open_rpl() inserts into tid_list from the receive path using xa_insert_bh().  The array is shared by the adapter's connections and initialized with XA_FLAGS_LOCK_BH.  However, chcr_ktls_dev_del() and the chcr_ktls_dev_add() error path use xa_erase(), which takes the XArray lock without disabling softirqs.  When cleanup runs with softirqs enabled, a receive softirq for another connection on the same CPU can interrupt the erase and spin on the lock held by the interrupted task.  Use xa_erase_bh() at both sites to match the insertion path.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98969",
                                "url": "https://ubuntu.com/security/CVE-2026-98969",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net/sched: em_text: reject unterminated algo before autoload  This is a follow-up to commit 9c572a83037a (\"net/sched: fix potential stack infoleak in em_text_dump()\"), which zero-initialised the dump-side struct. Sashiko pointed at a pre-existing bug that exposed the change-side input-validation gap open.  em_text_change() casts the raw netlink attribute payload to struct tcf_em_text and passes conf->algo, a 16-byte array with no enforced NUL terminator, to textsearch_prepare().  On the TS_AUTOLOAD retry textsearch_prepare() calls request_module(\"ts_%s\", algo); vsnprintf() walks %s until it finds a NUL, so an algo[] with no NUL reads past the array into the adjacent struct fields and payload and feeds those bytes to the usermode helper command line.  This is an out-of-bounds read and a kernel memory disclosure.  Reject the attribute when no NUL exists within TC_EM_TEXT_ALGOSIZ bytes, matching the check xt_string has had since 3ab720881b6e.  Conditions to recreate the bug: - CAP_NET_ADMIN on the target netns (namespace-local via unshare -Urn   is enough) - install clsact on an interface, then add a basic filter with one text   ematch whose algo[] is 16 bytes with no NUL (e.g. \"A\"*16) and   pattern_len at least 1 - the add fails with -ENOENT and the kernel invokes modprobe with a   module name made of \"ts_\" plus the 16 bytes and the adjacent payload",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98970",
                                "url": "https://ubuntu.com/security/CVE-2026-98970",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  drm/vc4: Free the BO cache size list on teardown  vc4_bo_cache_destroy() purges the cached BOs but never frees the size list, leaking it on every unbind.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98971",
                                "url": "https://ubuntu.com/security/CVE-2026-98971",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  gpio: exar: initialize the ID before registering its cleanup  devm_add_action_or_reset() invokes the cleanup action immediately when registering the action fails.  gpio_exar_probe() currently stores the allocated ID in exar_gpio only after registering the action, so that failure makes exar_devm_ida_free() release ID 0.  If the allocated ID is nonzero, this leaks that ID and can free ID 0 belonging to another device.  Store the ID before registering the cleanup action so both the immediate failure path and normal device teardown release the correct allocation.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98979",
                                "url": "https://ubuntu.com/security/CVE-2026-98979",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  namespace: refuse an automount below a mount that is in no namespace  It's possible to add autmounts even when the parent mount isn't in the mount namespace of the caller. The only requirement we have is that the parent mount namespace must not be NULL, i.e., unmounted.  Problem is that clone_private_mount() has MNT_NS_INTERNAL which makes that trivially true. So that passes the test and attach_recursive_mnt() accepts that as a mount point and funny enough, count_mounts() dereferences MNT_NS_INTERNAL. The problem is it is an error pointer...  So we can reach this in userspace via fanotify. A filesystem mark on the lower filesystem of an overlay reports paths on the layer clone and reading the event hands out a descriptor on it. For example with debugfs as the lower layer it goes kaboom:    openat(evfd, \"tracing\", O_DIRECTORY)    Oops: general protection fault   KASAN: null-ptr-deref in range [0x1d0-0x1d7]   RIP: 0010:count_mounts+0x35/0x200    attach_recursive_mnt    finish_automount  And since that sleeping beauty happens under namespace_sem held for writing every mount operation on the system blocks from then on. Congrats.  Use is_mounted() instead which rejects unmounted and internal mounts alike. The open fails with EINVAL just as it did before clone_private_mount() used MNT_NS_INTERNAL.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98984",
                                "url": "https://ubuntu.com/security/CVE-2026-98984",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  dcache: don't put a mountpoint on a dentry that's being removed  rmdir(), unlink() and rename() call dont_mount() on the victim and then detach_mounts() with the victim's inode locked. do_lock_mount() takes the inode lock of the mountpoint and checks cant_mount() so a mount can't show up after detach_mounts().  But attach_recursive_mnt() makes a second mountpoint for the root of the source mount so that the mounts already located at the destination can be put on top of it. No inode is locked for that one and d_set_mounted() only refuses a dentry that is unlinked. Between detach_mounts() and d_delete() the victim is still hashed:    rmrace: b passed dont_mount() and detach_mounts(), sleeping   T2: move_mount(S, /tmp/plcant/x, BENEATH) = 0 errno 0 ()   T1: rmdir(/tmp/plcant/d/b) = 0 errno 0       109 107 0:61 /d/b//deleted /tmp/plcant/x rw,relatime - tmpfs tmpfs rw       108 109 0:63 / /tmp/plcant/x rw,relatime - tmpfs T rw  A bind mount of the directory that's being removed is moved beneath an existing mount while the rmdir() is located between the two calls. The mount ends up on the removed directory and nothing will ever detach it.  Check cant_mount() in d_set_mounted() as well. dont_mount() raises the flag under d_lock before detach_mounts() runs so either the mountpoint is set first and detach_mounts() finds the mount or the flag is seen and the mount is refused.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98990",
                                "url": "https://ubuntu.com/security/CVE-2026-98990",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  namespace: check a submount for references right before unmounting it  shrink_submounts() and mark_mounts_for_expiry() first collect all the mounts they are allowed to unmount and then unmount them.  Whether a mount is busy is decided by propagate_mount_busy() on the tree. But unmounting the first mount changes the tree that the second one propagates into. propagate_umount() moves a surviving overmount off a copy it unmounts and mounts it where the copy was mounted. If that's where the propagated copy of the second victim is looked up the overmount becomes a candidate of the second umount_tree(). It's childless and so trim_one() commits it without looking at its reference count.  So a synchronous umount pulls out a busy mount that is in use somewhere else and marks it MNT_SYNC_UMOUNT while it has users:    umount2(/tmp/plshrink/p1, 0) = 0 errno 0   cwd is (unreachable)  The same two umounts requested one after the other fail with EBUSY. This needs a mount with MNT_SHRINKABLE, i.e., automounted submounts of NFS, AFS and CIFS or the tracefs mount below debugfs. Bind mounts inherit the flag.  Check each mount right before it is unmounted under the same hold of namespace_sem and mount_lock as the umount itself. Make sure that the algorithm stays linear.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99095",
                                "url": "https://ubuntu.com/security/CVE-2026-99095",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  drm/vc4: drain the hangcheck timer and works on V3D unbind  Nothing stops the hangcheck timer that submitted jobs arm, or the job_done_work that the render-done interrupt queues, at teardown: vc4_irq_disable() cancels only overflow_mem_work, and vc4_gem_destroy() runs from the drm-managed release, after vc4_v3d_unbind() has already uninstalled the V3D interrupt and cleared vc4->v3d. A timer still armed by then reads V3D registers through the NULL vc4->v3d pointer, and the late callbacks run on the vc4_dev embedding them after it has been freed.  Drain them in vc4_v3d_unbind(): shut the timer down and cancel reset_work before the interrupt is taken down, because its vc4_irq_reset() re-enables it, then flush job_done_work so that completions queued at teardown still release their jobs.  This issue was found by an in-house static analysis tool.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-26 15:16:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99006",
                                "url": "https://ubuntu.com/security/CVE-2026-99006",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  drm/i915/gem: Prevent overstepping exec array boundary  It is possible for eb_relocate_parse_slow() to call kvfree() on entries outside the original exec array during following scenario inside eb_relocate_parse_slow():  1) eb_copy_relocations() allocates as many as eb->buffer_count    copies for exec entries; 2) eb_parse() appends up to two VMAs, right after incrementing    eb->buffer_count; 3) cleanup under \"out\" label uses this incremented buffer_count    to release relocation pointers from exec array via kvfree(),    not from VMA array.  To amend this problem, ensure that relocation cleanup uses the original exec object count, excluding the VMAs appended by the command parser.  (cherry picked from commit 2a0158925fb943c7ba8f3216e2734952128defc9)",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99008",
                                "url": "https://ubuntu.com/security/CVE-2026-99008",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  Bluetooth: RFCOMM: Fix NULL tty_dev dereference in rfcomm_dev_shutdown  syzbot hit a NULL pointer dereference in rfcomm_dev_shutdown() when an RFCOMM tty is closed.  rfcomm_dev_add() puts the new device on rfcomm_dev_list first and only then registers the tty device and saves it in dev->tty_dev. If that registration fails, dev->tty_dev is never set at all. The device can be looked up in the meantime, so an open() of /dev/rfcommN gets through rfcomm_tty_install() and attaches to it. When that tty is closed again, rfcomm_dev_shutdown() uses dev->tty_dev without checking it:    Oops: general protection fault, probably for non-canonical address   KASAN: null-ptr-deref in range [0x0000000000000040-0x0000000000000047]   RIP: 0010:rfcomm_dev_shutdown+0x48/0xb0 net/bluetooth/rfcomm/tty.c:131   Call Trace:    tty_port_shutdown+0x1bf/0x220 drivers/tty/tty_port.c:372    tty_port_close+0x4e/0x150 drivers/tty/tty_port.c:705    tty_release+0x359/0x1670 drivers/tty/tty_io.c:1718    __fput+0x418/0xa50 fs/file_table.c:512  rfcomm_dev_destruct() already copes with a NULL dev->tty_dev. Add the same check to rfcomm_dev_shutdown(), so the tty device is only moved when it was actually registered.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99010",
                                "url": "https://ubuntu.com/security/CVE-2026-99010",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  Bluetooth: RFCOMM: free the skb when the DLC has no owner  rfcomm_recv_data() hands the skb to d->data_ready() and returns 0 without freeing it, so the callback owns the skb from that point on. The tty implementation frees it when the DLC has been detached from its device:    static void rfcomm_dev_data_ready(struct rfcomm_dlc *dlc,                                     struct sk_buff *skb)   {           struct rfcomm_dev *dev = dlc->owner;            if (!dev) {                   kfree_skb(skb);                   return;           }  The socket implementation returns without freeing it, and the skb is leaked.  A connected DLC can have no owner: rfcomm_sock_destruct() clears d->owner, while the DLC itself stays on the session until it is closed. Data frames that arrive in that window still find d->state == BT_CONNECTED in rfcomm_recv_data() and are handed to the callback, one leaked skb each.  The leak does not stop on its own either.  The remote runs out of credits only once RFCOMM_RX_THROTTLED is set, and for a socket the only place that sets it is rfcomm_sk_data_ready() itself, below the return. rfcomm_process_dlcs() keeps granting credits, so the remote keeps sending and the leak keeps growing.  Free the skb, as the tty side does.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99015",
                                "url": "https://ubuntu.com/security/CVE-2026-99015",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  Bluetooth: hci_sock: Serialize dead-device detachment  Rebinding an HCI socket after its controller is unregistered can race monitor control replay and crash the kernel. hci_sock_bind() clears hci_pi(sk)->hdev and drops the device reference under only the socket lock, whereas send_monitor_control_replay() holds hci_sk_list.lock for reading.  Replay can observe a non-NULL hdev, then bind can clear it and drop the last reference before create_monitor_ctrl_open() reads hdev->id. This can cause a NULL pointer dereference if the pointer is reloaded, or a use-after-free if the old pointer is retained.  The kernel reported:    KASAN: null-ptr-deref in range [0x0000000000000068-0x000000000000006f]   RIP: 0010:create_monitor_ctrl_open+0x579/0x800   Call Trace:    hci_sock_bind+0xd96/0x1190    __sys_bind+0x166/0x200    __x64_sys_bind+0x6d/0xb0    do_syscall_64+0xdd/0x4a0    entry_SYSCALL_64_after_hwframe+0x77/0x7f  The same missing serialization lets hci_send_to_sock() select a socket for the old device and queue its frame after bind has detached the socket or installed a new binding.  Take hci_sk_list.lock for writing when clearing the device pointer and resetting the socket state. This waits for existing replay and delivery readers to finish before detachment and prevents later readers from using the old binding. Keep hci_dev_put() outside the critical section because the final device release can sleep.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99022",
                                "url": "https://ubuntu.com/security/CVE-2026-99022",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  regulator: ltc3676: don't read the write-only HRST and CLIRQ registers  HRST (0x1e) and CLIRQ (0x1f) are write-only command strobes. Writing HRST triggers a hard reset of the chip and writing CLIRQ clears the interrupt; reading them returns nothing useful, and the read itself fires the command.  The result is that a plain register dump resets the board:    cat /sys/kernel/debug/regmap/2-003c/registers  walks every readable register, hits HRST, and the board reboots.  Split the callback back in two so HRST and CLIRQ stay writable but are no longer readable. The readable range is left unchanged (LTC3676_BUCK1 ... LTC3676_IRQSTAT).",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99025",
                                "url": "https://ubuntu.com/security/CVE-2026-99025",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  openvswitch: fix soft lockup in the netlink flow dump  A production compute node carrying a few thousand datapath flows hit a soft lockup inside a single netlink flow dump and panicked.  ovs_flow_cmd_dump() calls ovs_flow_stats_get() for every flow it emits, and that releases stats->lock with spin_unlock_bh() once per CPU that has touched the flow. Every release is a local_bh_enable(), and each one runs the pending softirq backlog in the dumping thread's own context.  The skb bounds the flows one callback emits, but not the softirq work it absorbs. On a CPU that carries the box's packet load the backlog refills as fast as it drains, so the dumping thread becomes that CPU's softirq engine. It never sleeps and it has no reschedule point, so under voluntary preemption nothing can take the CPU away from it: neither the ksoftirqd the kernel woke to take the work over, nor the stopper thread the softlockup detector dispatches to refresh its timestamp.  Hold BH off across the whole callback instead, the way ctnetlink_dump_table() does, so the nested spin_unlock_bh() stop draining softirqs. The loop already runs under rcu_read_lock() and cannot sleep. What it gives up is preemption under CONFIG_PREEMPT, since a BH-off region is not preemptible outside PREEMPT_RT. The region stays short: the skb caps the flows one callback emits, and empty buckets cost no skb space but are each visited once per dump, as the cursor only moves forward. The table grows on insert and shrinks only on flush, so the walk is bounded by the largest flow count the datapath has held. The softirq backlog the callback used to absorb has no bound at all.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99031",
                                "url": "https://ubuntu.com/security/CVE-2026-99031",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net: bridge: avoid recursive multicast port cleanup  br_multicast_sg_del_exclude_ports() removes automatically added STAR_EXCL port groups by calling br_multicast_del_pg(). For S,G entries, that deletion calls back into br_multicast_sg_del_exclude_ports(), so a large number of STAR_EXCL ports consumes one kernel stack frame per port and can hit the stack guard page.  Keep the complete port-group deletion path for cleanup, but suppress the S,G exclude-port cleanup while that helper is already walking the same entry. Normal deletion callers retain the existing behavior.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99032",
                                "url": "https://ubuntu.com/security/CVE-2026-99032",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net/smc: protect clcsock lifetime in smc_getname  smc_getname() dereferences smc->clcsock without holding clcsock_release_lock. Link-group termination can release the CLC socket through smc_close_active_abort() while the SMC socket is still open, for example after shutdown(SHUT_WR).  A getsockname() caller can load smc->clcsock, then the termination worker can clear the pointer and call sock_release() before the caller accesses clcsock->ops or invokes getname(). This causes a use-after-free; if the worker clears the pointer before the load, it causes a NULL dereference. The syscall's file reference keeps the SMC socket alive but does not prevent asynchronous release of its CLC socket.  KASAN reported the following with test-only timing instrumentation:    BUG: KASAN: slab-use-after-free in smc_getname+0x19e/0x1b0   Read of size 8 at addr ffff888109abb4e0 by task poc/103   Call Trace:    smc_getname+0x19e/0x1b0    do_getsockname+0xe5/0x170    __sys_getsockname+0x8c/0x100    Allocated by task 95:    sock_alloc_inode+0x1e/0x280    sock_alloc+0x3d/0x240    __sock_create+0x7e/0x430    smc_create+0x121/0x240    Freed by task 0:    kmem_cache_free+0xcc/0x340    rcu_core+0x50a/0x1850    Last potentially related work creation:    evict+0x446/0x6c0    smc_clcsock_release+0xa8/0xd0    smc_close_active_abort+0x26a/0x3a0    __smc_lgr_terminate.part.0+0x137/0x2e0  Hold clcsock_release_lock across the pointer check and the getname() callback to serialize with smc_clcsock_release(). Return -EBADF if the CLC socket has already been released, preserving the existing peer state check and the callback's return value otherwise.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99033",
                                "url": "https://ubuntu.com/security/CVE-2026-99033",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net/packet: guard the ll header push in packet_rcv_spkt()  packet_rcv_spkt() restores the link layer header with  \tskb_push(skb, skb->data - skb_mac_header(skb));  That subtraction is only meaningful when the device actually has a link layer header.  packet_rcv() and tpacket_rcv() both wrap it in dev_has_header(), which is also the predicate the block comment at the top of the file states the restore in terms of; packet_rcv_spkt() does not.  commit d549699048b4 (\"net/packet: fix packet receive on L3 devices without visible hard header\") introduced the helper and changed the two call sites, and this one stayed behind.  A device without a visible ll header can leave skb->mac_header at the 0xFFFF sentinel that __alloc_skb() initialises it to.  A CAN skb does: init_can_skb() sets pkt_type and ip_summed but does not reset the headers, and commit 9f10374bb024 (\"can: remove private CAN skb headroom infrastructure\") dropped the skb_reset_*_header() calls that used to be there.  skb_mac_header() is then 0xFFFF, the length becomes a large negative number and skb_push() reports it through skb_under_panic() -- from softirq context, so it is a full system panic even with panic_on_oops=0:    skbuff: skb_under_panic: text:ffffffff8bd21bc1 len:-65455 put:-65471 head:... data:... tail:0x50 end:0x180 dev:can0   kernel BUG at net/core/skbuff.c:214!   RIP: 0010:skb_panic+0x50/0x60   Call Trace:    <IRQ>    skb_push+0x38/0x40    packet_rcv_spkt+0xe1/0x170    __netif_receive_skb_core.constprop.0+0x7e8/0xd30    ...   Kernel panic - not syncing: Fatal exception in interrupt  The socket type is reachable: packet_create() accepts SOCK_PACKET alongside SOCK_RAW and SOCK_DGRAM behind the same CAP_NET_RAW check, and neither the socket length nor a capability check keeps it away from a CAN interface.  The missing skb_reset_*_header() calls in init_can_skb() are a regression in their own right and are being fixed separately, but a packet socket should not turn a link layer that did not initialise its mac header into a kernel panic.  Guard the push the way the other two receive paths do.  Tested on v7.3-rc5 under QEMU with a slcan device on a pty, which is the driver RX path: vcan does not reproduce it, because can_send() resets the headers on the way out.  One SOCK_PACKET socket bound to can0 and one frame written into the line discipline panics an unpatched kernel with the trace above; the same image with this patch prints no panic and powers off normally.  Both kernels are this tree, defconfig plus CONFIG_CAN_SLCAN=y, differing only in this hunk.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99034",
                                "url": "https://ubuntu.com/security/CVE-2026-99034",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  mmc: sdhci-sprd: disable runtime PM on remove  sdhci_sprd_probe() enables runtime PM, while sdhci_sprd_remove() does not perform the corresponding runtime PM cleanup.  The probe failure path disables runtime PM before disabling the clocks, but the normal remove path directly disables clocks that are also managed by the runtime PM callbacks. If the device is runtime suspended, those clocks may already be disabled.  Resume the device before removal, disable runtime PM and drop the temporary runtime PM reference before disabling the clocks.  This issue was found by manual code inspection.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99035",
                                "url": "https://ubuntu.com/security/CVE-2026-99035",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  mmc: mtk-sd: Cancel request timeout work on remove  The driver queues req_timeout while a request is active. msdc_request_done() uses cancel_delayed_work(), which does not wait for a timeout callback that has already started.  The timeout callback calls mmc_request_done(), which wakes the request waiter, and then continues to use host->dev_comp and check the SDIO IRQ. During unbind, msdc_drv_remove() can return and the managed mmc_host can be freed before the callback finishes.  KASAN reported use-after-free accesses in msdc_request_done() and msdc_recheck_sdio_irq() in each of three unbind tests.  The same tests completed without a kernel diagnostic after this change.  Call cancel_delayed_work_sync() after mmc_remove_host() has stopped new requests and before the driver releases the host resources.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99037",
                                "url": "https://ubuntu.com/security/CVE-2026-99037",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  dm-crypt: reject the lmk IV mode with AEAD ciphers  A \"capi:\" table line that pairs an AEAD cipher with the lmk IV mode, for example \"capi:gcm(aes)-lmk\" with the integrity:28:aead option, causes an oops when it is loaded. lmk sets tfms_count to 64, but crypt_alloc_tfms_aead only allocates one transform, so crypt_setkey reads past the end of the tfms_aead array and calls crypto_aead_setkey on the values it finds there.  lmk exists for compatibility with Loop-AES, which uses CBC, so refuse it with an AEAD cipher rather than allocate 64 AEAD transforms. The check cannot go in crypt_iv_lmk_ctr with the other lmk checks, because the IV constructor runs after crypt_set_key.  Note that this is not a security bug because the memory corruption can only be triggered by root.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99038",
                                "url": "https://ubuntu.com/security/CVE-2026-99038",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  memstick: rtsx_usb_ms: complete requests after eject instead of dropping them  memstick_check() can pass its host->removing check just before rtsx_usb_ms_drv_remove() sets eject/removing. Its next request is then silently dropped: rtsx_usb_ms_request() skips schedule_work() once eject is set, and drv_remove's cancel_work_sync() can also cancel a queued handle_req before it picks the request up. Nobody completes card->mrq_complete.  Once memstick core waits for requests without a timeout (\"memstick: core: wait for request completion before freeing card\"), this hangs removal: memstick_check() never returns and memstick_remove_host() blocks in flush_workqueue():    INFO: task kworker/u10:3:65 blocked for more than 20 seconds.   Workqueue: kmemstick memstick_check    __wait_for_common    memstick_check    INFO: task kworker/1:1:33 blocked for more than 20 seconds.   Workqueue: usb_hub_wq hub_event    __flush_workqueue    memstick_remove_host    rtsx_usb_ms_drv_remove  Never drop a request. rtsx_usb_ms_request() always schedules handle_req, and handle_req fails requests with -ENOMEDIUM once eject is set, without touching the device. drv_remove flushes handle_req instead of cancelling it, and cancels it only after memstick_remove_host(), when no new request can arrive, so it cannot run on a freed host.  The host_mutex drain in drv_remove is removed: handle_req always leaves host->req NULL when it finishes, so the drain never had anything to do, and it would now race with handle_req.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99039",
                                "url": "https://ubuntu.com/security/CVE-2026-99039",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  memstick: core: wait for request completion before freeing card  In memstick_alloc_card() and memstick_set_rw_addr(), wait_for_completion_timeout() is used to wait for device identification and address configuration requests to complete.  The memstick subsystem does not provide an abort or cancellation callback in struct memstick_host for in-flight requests. If wait_for_completion_timeout() expires (for instance, when a USB transfer or command retry is delayed), memstick_alloc_card() returns an error and frees the memstick_dev structure via kfree(card).  However, the host controller driver (such as rtsx_usb_ms) is still running the request asynchronously in worker context. When the transfer eventually finishes, the driver writes into host->req->data, which points to memory inside the already freed card structure. This leads to a KASAN slab-use-after-free write:    BUG: KASAN: slab-use-after-free in ms_read_bytes+0x8fe/0x990   Write of size 1 at addr ffff88813c188079 by task kworker/1:5/5239   Workqueue: events rtsx_usb_ms_handle_req   Call Trace:    ms_read_bytes+0x8fe/0x990 drivers/memstick/host/rtsx_usb_ms.c:450    rtsx_usb_ms_issue_cmd drivers/memstick/host/rtsx_usb_ms.c:477 [inline]    rtsx_usb_ms_handle_req+0x557/0x1a00 drivers/memstick/host/rtsx_usb_ms.c:531    process_one_work+0xac7/0x1b10 kernel/workqueue.c:3396    worker_thread+0x5ef/0xe50 kernel/workqueue.c:3560    kthread+0x373/0x450 kernel/kthread.c:436    Allocated by task 1662:    memstick_alloc_card drivers/memstick/core/memstick.c:383 [inline]    memstick_check+0x2c1/0x10d0 drivers/memstick/core/memstick.c:452    process_one_work+0xac7/0x1b10 kernel/workqueue.c:3396    Freed by task 1662:    kfree+0x20c/0x650 mm/slub.c:6792    memstick_alloc_card drivers/memstick/core/memstick.c:420 [inline]    memstick_check+0x72b/0x10d0 drivers/memstick/core/memstick.c:452    process_one_work+0xac7/0x1b10 kernel/workqueue.c:3396  Host controller drivers (rtsx_usb_ms, jmb38x_ms, tifm_ms, r592) already implement their own hardware and bus timeouts, and callers in mspro_block and ms_block already rely on wait_for_completion() unconditionally.  Replace wait_for_completion_timeout() with wait_for_completion() in memstick_set_rw_addr() and memstick_alloc_card() so that the card structure is never freed while an asynchronous request is in flight.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99040",
                                "url": "https://ubuntu.com/security/CVE-2026-99040",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  KEYS: Fix add_key() race with keyring restriction  __key_create_or_update() snapshots keyring->restrict_link before taking the destination keyring's semaphore.  keyring_restrict() installs a restriction while holding that semaphore.  This allows a writer to observe no restriction, wait for the keyring owner to install a reject-all restriction and return successfully, and then link a key using the stale NULL snapshot.  The writer only needs write permission on the destination keyring.  Move the restrict_link read after __key_link_lock() and __key_link_begin().  The read and the subsequent restriction check are then serialized with restriction installation by keyring->sem.  The race was reproduced on v7.2.8 in 19 executions where restriction installation returned before the link completed.  All 19 linked the key despite the reject-all restriction.  With this change, 312 executions reached the same ordering and every add_key() call failed with -EPERM.  The issue was found by manual concurrency analysis assisted by AI-based analysis and independently verified with a QEMU reproducer and kernel instrumentation.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99045",
                                "url": "https://ubuntu.com/security/CVE-2026-99045",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ibmveth: h_free logical LAN on open-fail after register  ibmveth_open() registers the logical LAN, then allocates the RX buffer pools. A pool failure jumps to out_free_buffer_pools without h_free_logical_lan(), so PHYP still owns the buffer-list page when it is unmapped. request_irq() failure already issued the hypercall before taking the same label.  Move that h_free to the shared post-register unwind so both paths deregister before the buffer list is unmapped.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99049",
                                "url": "https://ubuntu.com/security/CVE-2026-99049",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  gpio: xilinx: fix runtime PM leak on request error path  pm_runtime_get_sync() leaves the usage counter incremented even when it fails, and xgpio_request() returns the error without dropping it.  gpiolib does not call ->free() when ->request() fails, so xgpio_free(), which holds the only matching pm_runtime_put(), never runs. The reference is leaked and the controller can no longer runtime-suspend, so its clock stays enabled.  Switch to pm_runtime_resume_and_get(), which only increments the usage counter on success.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99052",
                                "url": "https://ubuntu.com/security/CVE-2026-99052",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  selinux: preserve NATIVE_LABELS on already-initialized sb in set_mnt_opts  When an NFSv4 filesystem exported with security_label is mounted a second time, sget_fc() returns the existing superblock and nfs_get_root() calls security_sb_set_mnt_opts() again on it. Since the superblock is already SB_INITIALIZED, selinux_set_mnt_opts() takes an early exit without setting SECURITY_LSM_NATIVE_LABELS in *set_kern_flags. nfs_get_root() then sees kflags without SECURITY_LSM_NATIVE_LABELS set and clears NFS_CAP_SECURITY_LABEL on the shared nfs_server, silently disabling per-file labeling for both the new and the original mount.  Commit 3815a245b501 (\"security/selinux: fix SECURITY_LSM_NATIVE_LABELS on reused superblock\") fixed the same problem in selinux_sb_clone_mnt_opts().  The reused-superblock path for a plain second mount now goes through sb_set_mnt_opts rather than sb_clone_mnt_opts, so it needs the same treatment: on both SE_SBINITIALIZED early exits, set SECURITY_LSM_NATIVE_LABELS in *set_kern_flags when the superblock was already using SECURITY_FS_USE_NATVE.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99053",
                                "url": "https://ubuntu.com/security/CVE-2026-99053",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  tipc: hold a reference to nodes found by link name  tipc_node_find_by_name() returns a node after dropping its RCU read lock without taking a reference.  The LINK_SET, LINK_GET and LINK_RESET_STATS handlers then lock and access the node, racing with timer-driven cleanup of a down peer.  Generic netlink serialization does not exclude the node timer.  The following interleaving can leave a handler using a freed node:    CPU 0: find the node under RCU and release the node read lock   CPU 1: tipc_node_timeout() clears the links and unlinks the down node   CPU 1: drop the list and timer references, queuing tipc_node_free()   CPU 0: leave the RCU read-side critical section   CPU 1: complete the grace period and free the node   CPU 0: acquire the node lock through the stale pointer  LINK_SET also uses the node's media address after releasing the node lock, when passing queued packets to tipc_bearer_xmit().  KASAN on v7.3-rc5 reported:    BUG: KASAN: slab-use-after-free in _raw_read_lock_bh   Write of size 4 at addr ffff88807e06f008 by task poc/92   Call Trace:    _raw_read_lock_bh                 kernel/locking/spinlock.c:287    tipc_nl_node_set_link             net/tipc/node.c:2475    genl_family_rcv_msg_doit          net/netlink/genetlink.c:1114    genl_rcv_msg                      net/netlink/genetlink.c:1209    netlink_rcv_skb                   net/netlink/af_netlink.c:2575    Allocated by task 0:    tipc_node_create                  net/tipc/node.c:539    tipc_node_check_dest              net/tipc/node.c:1196    tipc_disc_rcv                     net/tipc/discover.c:252    Freed by task 92:    kfree                             mm/slub.c:6801    rcu_core                          kernel/rcu/tree.c:2919    Last potentially related work creation:    __call_rcu_common.constprop.0     kernel/rcu/tree.c:3181    tipc_node_timeout                 net/tipc/node.c:814  Acquire a reference to the selected node with kref_get_unless_zero() before leaving RCU, returning NULL if the node has already been released.  Release that reference on every caller exit after the last node access, including transmission in LINK_SET.  Keep the existing link lookup order and locking so concurrent link removal still takes the existing error paths.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99054",
                                "url": "https://ubuntu.com/security/CVE-2026-99054",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  tipc: destroy topsrv workqueues before closing connections  tipc_topsrv_stop() closed subscriber connections while the topology server's send and receive workqueues were still running. Socket callbacks and subscription events could then queue more work, and in-flight send/recv work could drop the last connection reference during the conn_idr walk.  That race produced several teardown failures: refcount_t addition on 0 from conn_get() on a connection whose release was blocked on idr_lock, a subsequent use-after-free in tipc_conn_close(), queue_work() on an already destroyed workqueue from the listener data-ready callback, and an RCU stall in tipc_topsrv_exit_net() while the walk spun under idr_lock.  Clear srv->listener under idr_lock so it acts as a shutdown flag, skip queue_work() once it is NULL, destroy the workqueues to flush in-flight work, and only then close the remaining connections. Refuse tipc_conn_lookup() after that flag is cleared, and drop idr_lock when the teardown walk finds no connection, so an in-flight subscription event cannot pin idr_in_use while the walk holds the lock.  v3 supersedes the narrower in-thread diff Tung Quang Nguyen posted on 2026-09-23. It keeps his teardown order and adds the lookup refusal and the empty-idr unlock.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99056",
                                "url": "https://ubuntu.com/security/CVE-2026-99056",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  strparser: make sure __strp_recv isn't running before tearing down the parser  The comment above strp_done() claims that if strp is stopped, strp_recv will no longer be called. That's only true if the caller has a mechanism (eg locking) to guarantee that strp_recv() calls that started before strp_stop() have completed by the time we call strp_done().  This adds a dummy lock_sock/release_sock pair to guarantee that any in-flight strp_recv() (which runs under either bh_lock_sock or lock_sock, depending if it's called from ->sk_data_ready or strp_work) has completed.  Only espintcp can be affected by this race condition, but this patch makes sure no future user of strp can have the bug.  This could crash on strp->sk (\"general mode\" of strp), but this mode has been here for 9 years and has never been used. It'll be gone soon, no point worrying about it.  Switch the stopped/paused/etc bits to u8's to avoid races between strp_stop() and strp_pause/unpause().  A reproducer has been published and turns the possible UAF into an exploit [1].",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99057",
                                "url": "https://ubuntu.com/security/CVE-2026-99057",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  xen/netfront: don't leak the skb when xennet_fill_frags() fails  When a response chain has more slots than fit in the skb's frags, xennet_fill_frags() returns an error and xennet_poll() jumps to its error path.  That path moves what's left on tmpq to errq to be freed, but the skb being filled was already dequeued from tmpq, so it's never freed.  Each chain that overflows leaks the skb and the pages attached to it as frags, and the backend decides how many slots it sends.  Put the skb back on tmpq before taking the error path, like the xennet_set_skb_gso() failure just above it does.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99058",
                                "url": "https://ubuntu.com/security/CVE-2026-99058",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  workqueue: Fix NULL current_pwq deref in chained work check  current_wq_worker() only tells us that %current is a kworker. It does not guarantee that the worker is currently executing a work item, as worker->current_pwq is populated only while process_one_work() is running the work function.  is_chained_work() can be reached while queueing on a draining or destroying workqueue. If a kworker outside work-item execution reaches that path, current_wq_worker() returns a worker but worker->current_pwq is NULL, and the chained-work test can fault before it emits the intended warning.  Guard the chained-work test with worker->current_pwq. A kworker without current_pwq is not executing work on the target workqueue, so the helper should return false and let the draining/destroying warning fire.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99059",
                                "url": "https://ubuntu.com/security/CVE-2026-99059",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wireguard: noise: reject response consumption after intermediate initiation  Two threads begin processing the identical response message, received twice. The first thread, A, runs. While it's running, the second one, B, gets partway through, and during that slow calculation, or even while blocking on down_write(), A completes and then also a handshake initiation that's already been queued up runs in thread C, which itself takes that same down_write(). The handshake initiation creation succeeds, and sets the state back to waiting-for-response, and calls up_write(), at which point thread B resumes, because either its finished its calculations or was finally allowed to acquire down_write(). Thread B then copies the state back to the peer, and begins a new session, using that state, which is the same session as the one made in thread A.  Thread A\t\t\tThread B\t\t\tThread C  down_read()  sA = handshake->state  memcpy(cA, handshake->crypto) up_read() if (sA != 1)  goto fail slow_crypto(cA) \t\t\t\tdown_read() \t\t\t\t sB = handshake->state \t\t\t\t memcpy(cB, handshake->crypto) \t\t\t\tup_read() \t\t\t\tif (sB != 1) \t\t\t\t goto fail \t\t\t\tslow_crypto(cB) down_write()  if (sA != handshake->state)   goto fail  memcpy(handshake->crypto, cA)  handshake->state = 2 up_write() down_write()  if (handshake->state != 2)   goto fail  derive_session(handshake->crypto) up_write() \t\t\t\t\t\t\t\tdown_write() \t\t\t\t\t\t\t\t slow_crypto(handshake->crypto) \t\t\t\t\t\t\t\t handshake->state = 1 \t\t\t\t\t\t\t\tup_write() \t\t\t\tdown_write() \t\t\t\t if (sB != handshake->state) \t\t\t\t   goto fail \t\t\t\t memcpy(handshake->crypto, cB) \t\t\t\t handshake->state = 2 \t\t\t\tup_write() \t\t\t\tdown_write() \t\t\t\t if (handshake->state != 2) \t\t\t\t  goto fail \t\t\t\t derive_session(handshake->crypto) \t\t\t\tup_write()  This seems basically impossible to hit in a meaningful way in practice, but ensure that it absolutely cannot happen by comparing the ephemeral private key that's on the stack with the latest one that the peer's handshake state has.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99061",
                                "url": "https://ubuntu.com/security/CVE-2026-99061",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: brcmfmac: fix P2P device removal race in brcmf_detach()  When the driver is removed while the user space process that created the P2P device (e.g. wpa_supplicant) is still exiting, the P2P device interface is removed twice and the kernel crashes.  The two paths are:   - wpa_supplicant, on exit, sends NL80211_CMD_DEL_INTERFACE for the P2P    device. nl80211_del_interface() holds RTNL and the wiphy mutex and    calls brcmf_p2p_del_vif(), which disables discovery and waits up to    1.5 s for BRCMF_E_IF_DEL. Then it calls brcmf_remove_interface(),    which unregisters the wdev and frees the vif and the ifp.   - brcmf_detach() sets the bus down, so BRCMF_E_IF_DEL never arrives,    and calls brcmf_remove_interface(ifp, false) for the same ifp.    brcmf_p2p_ifp_removed() reads ifp->vif and then blocks on    rtnl_lock(). When brcmf_p2p_del_vif() releases RTNL, it calls    cfg80211_unregister_wdev() on the wdev that was already unregistered    and freed.  The second list_del_rcu() of wdev->list faults on LIST_POISON2:    brcmfmac: brcmf_p2p_del_vif delete P2P vif   brcmfmac: brcmf_p2p_deinit_discovery enter   brcmfmac: brcmf_p2p_del_vif P2P: GO_NEG_PHASE status cleared   brcmfmac: brcmf_detach Enter   brcmfmac: brcmf_bus_change_state 1 -> 0   brcmfmac: brcmf_remove_interface Enter, bsscfgidx=1, ifidx=0   brcmfmac: brcmf_del_if Enter, bsscfgidx=1, ifidx=0   brcmfmac: brcmf_p2p_ifp_removed P2P: device interface removed   [1.5 s later, brcmf_p2p_del_vif() timed out]   brcmfmac: brcmf_remove_interface Enter, bsscfgidx=1, ifidx=0   brcmfmac: brcmf_del_if Enter, bsscfgidx=1, ifidx=0   brcmfmac: brcmf_p2p_ifp_removed P2P: device interface removed   Unable to handle kernel paging request at virtual address dead000000000122   Internal error: Oops: 96000044 [#1] PREEMPT_RT SMP   pc : _cfg80211_unregister_wdev+0x6c/0x264 [cfg80211]   Call trace:    _cfg80211_unregister_wdev+0x6c/0x264 [cfg80211]    cfg80211_unregister_wdev+0x10/0x1c [cfg80211]    brcmf_p2p_ifp_removed+0x84/0xb0 [brcmfmac]    brcmf_remove_interface+0x1f4/0x254 [brcmfmac]    brcmf_detach+0x88/0x180 [brcmfmac]    brcmf_sdio_remove+0x90/0x7b0 [brcmfmac]    brcmf_sdiod_remove+0x20/0xa0 [brcmfmac]    brcmf_ops_sdio_remove+0xbc/0x12c [brcmfmac]    sdio_bus_remove+0x38/0x144    device_release_driver_internal+0x1e8/0x2c0    device_release_driver+0x14/0x20    brcmf_sdio_bus_remove+0x2c/0x40 [brcmfmac]    brcmf_fwvid_unregister_vendor+0xd8/0x170 [brcmfmac]    __exit_compat+0x18/0x418 [brcmfmac_cyw]    __arm64_sys_delete_module+0x1ac/0x244  The log was taken with debug=0x406 on an i.MX 8M Plus board with a CYW55513 (Sona IF513) on SDIO. The driver is the Ezurio backport of brcmfmac from v6.18.22 on a 5.4-rt kernel. The code involved is the same in mainline.  To reproduce:    1. Start wpa_supplicant on wlan0 and let it associate. It creates the      P2P device (iw dev shows \"type P2P-device\").   2. Stop wpa_supplicant and remove the driver without waiting for      wpa_supplicant to exit:         kill $(pidof wpa_supplicant)        rmmod brcmfmac_cyw brcmfmac  The crash is reproducible on that board.  For the interface without a netdev (the P2P device), take RTNL and the wiphy mutex in brcmf_detach() before reading iflist, and remove it with locked=true. If brcmf_p2p_del_vif() runs first, brcmf_detach() finds the slot empty. If brcmf_detach() runs first, nl80211 does not find the wdev any more. The interfaces with a netdev are removed as before, because brcmf_del_if() takes RTNL on its own for the primary interface.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99063",
                                "url": "https://ubuntu.com/security/CVE-2026-99063",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  dm ioctl: don't let data_start run past the buffer  struct dm_ioctl has seven bytes of trailing padding, so the smallest buffer userspace is allowed to ask for, offsetof(struct dm_ioctl, data), is seven bytes shorter than sizeof(struct dm_ioctl).  get_result_buffer() sets data_start to sizeof(struct dm_ioctl) without looking at how big the buffer actually is. Ask for the minimum and data_start ends up seven bytes past the end. Callers add it to data_size, and ctl_ioctl() copies that much back to userspace:    BUG: KASAN: slab-out-of-bounds in _copy_to_user+0xad/0xd0   Read of size 312 at addr ffff8880169e4c00 by task repro-dm/140    ctl_ioctl+0x5e3/0xcb0    dm_ctl_ioctl+0x25/0x40   allocated 305-byte region [ffff8880169e4c00, ffff8880169e4d31)  A DM_LIST_DEVICES with data_size set to 305 is enough to hit it, and the seven bytes that leak are whatever sat next to the allocation.  Clamp data_start to the buffer size.  Note that this is not a security bug because the out-of-bounds read can only be triggered by root.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99067",
                                "url": "https://ubuntu.com/security/CVE-2026-99067",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  btrfs: scrub: fix local_root reference leak in scrub_print_warning_inode()  When paths_from_inode() fails, scrub_print_warning_inode() jumps to err without dropping the reference taken by btrfs_get_fs_root(), leaking a reference to the root every time path resolution fails while printing scrub warnings.  Every other error and success path of the function drops the reference.  Drop the reference on the paths_from_inode() failure path too.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99070",
                                "url": "https://ubuntu.com/security/CVE-2026-99070",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ipv6: do not warn on route notification size race  fib6_info_hw_flags_set() sizes the skb with rt6_nlmsg_size() and later fills it with rt6_fill_node().  With nexthop compatibility mode enabled, a concurrent replacement can grow the group between these independent snapshots.  rt6_fill_node() can then legitimately return -EMSGSIZE, so the warning does not prove a sizing bug.  Remove the warning.  The existing error path still frees the skb and reports the error to listeners.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99071",
                                "url": "https://ubuntu.com/security/CVE-2026-99071",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ipv4: do not warn on route notification size race  Commit 680aea08e78c (\"net: ipv4: Emit notification when fib hardware flags are changed\") added asynchronous route notifications for hardware flag changes.  fib_alias_hw_flags_set() sizes the skb with fib_nlmsg_size() and later fills it with fib_dump_info() while holding only RCU.  With nexthop compatibility mode enabled, a concurrent replacement can grow the group between these independent snapshots.  fib_dump_info() can then legitimately return -EMSGSIZE, so the warning does not prove a sizing bug.  Remove the warning.  The existing error path still frees the skb and reports the error to listeners.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99072",
                                "url": "https://ubuntu.com/security/CVE-2026-99072",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ipv4: stop route notification sizing when nexthop group shrinks  Commit 680aea08e78c (\"net: ipv4: Emit notification when fib hardware flags are changed\") added an RCU-only fib_nlmsg_size() call for asynchronous hardware flag notifications.  fib_nlmsg_size() checks fib_info_num_path() before each iteration, then fib_info_nhc() independently reloads nh->nh_grp. If RTM_NEWNEXTHOP replaces a group with fewer paths between those loads, fib_info_nhc() returns NULL and fib_nexthop_nlmsg_size() dereferences it.  Stop sizing when the indexed path is absent. Nexthop groups are dense, so the current snapshot has no later path.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98686",
                                "url": "https://ubuntu.com/security/CVE-2026-98686",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  smb: client: discard post-EOF pagecache when extending a file via zero range  smb3_zero_range() removed the pagecache only for the range being zeroed, so when it extends the file the folio straddling the old EOF - which may hold data dirtied past EOF through an mmap - was never dropped and became visible as file content once the file was extended.  Lower the discard boundary to the smaller of the zero-range offset and the old EOF.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98700",
                                "url": "https://ubuntu.com/security/CVE-2026-98700",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: mac80211: set info->band for 802.3 encap offload frames  Unlike the 802.11 TX paths, ieee80211_8023_xmit() does not set info->band from the channel context on non-MLD interfaces. It stays at 0, so ieee80211_get_tx_rates() uses the wrong band for these frames.  Set it the same way as ieee80211_build_hdr(): drop the frame if there is no channel context, and leave the band at 0 on MLD interfaces.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98716",
                                "url": "https://ubuntu.com/security/CVE-2026-98716",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  KVM: SVM: Use the active VMCB's MSR bitmap when checking if MSR is intercepted  Use the MSR permission bitmap of the active VMCB instead of assuming that KVM is always using vmcb02's bitmap when L2 is active, as KVM uses msrpm02 if and only if L1 wants to intercept MSR accesses, i.e. if and only if KVM needs to merge msprm01 with msrpm12.  Don't bother tracking the virtual address of the bitmap that's being used, as __va() is cheap on x86, and caching the virtual address would introduce yet another source of potentially stale information.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99080",
                                "url": "https://ubuntu.com/security/CVE-2026-99080",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  fs: Free any excess xarray nodes in clear_inode()  For many years we've had a hard to hit leak of xarray nodes.  Hugh documented it well in commit 786b31121a2c.  Recently people and syzbot have found ways to force it to happen with madvise.  Rather than fix the leaks where they happen, just call xa_destroy() which has the side-effect of cycling the i_pages lock.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98709",
                                "url": "https://ubuntu.com/security/CVE-2026-98709",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: mac80211: count only matching reservations in reserved switch  ieee80211_vif_use_reserved_switch() validates a replacement by counting assigned links on ctx->replace_ctx and treating reservations too broadly. A link can still be assigned to the old channel context while holding a reservation that belongs to a different replacement operation.  That can make the current replacement appear complete too early. If another link finalizes first, the function can free the WILL_BE_REPLACED chanctx while the unmatched link and driver still use it, leading to a use-after-free in later beacon generation.  Require an in-place reservation to point at the current replacement context, and require the reserved and assigned contexts to be the matching replacement pair, before counting or moving the link.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98708",
                                "url": "https://ubuntu.com/security/CVE-2026-98708",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: mac80211: keep paired old chanctx alive  An in-place replacement keeps reciprocal replace_ctx pointers between the old WILL_BE_REPLACED chanctx and the new REPLACES_OTHER chanctx. However, the early free paths only consider assigned and reserved link users when deciding whether to free the old chanctx.  That lets the old chanctx be freed too early while the replacement partner still points back to it, either when the last assigned link is released or when that link successfully reassigns to another existing context. Later unreserve and switch-finalization paths can then follow a stale replace_ctx pointer.  Keep a paired old chanctx alive until the replacement pair has been torn down. Apply the same check to both __ieee80211_link_release_channel() and ieee80211_link_use_reserved_reassign(). If the replacement is later abandoned, ieee80211_link_unreserve_chanctx() already tears down the pairing before freeing the old chanctx once no users remain.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98752",
                                "url": "https://ubuntu.com/security/CVE-2026-98752",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  tty: port: fix tty_port_tty_vhangup() race  Drivers rely on tty_port_tty_vhangup() to synchronously hang up their ports before tearing down resources as part of deregistration (e.g. on physical disconnect).  If tty_port_tty_vhangup() races with another hangup it may however return before the port has been shut down. This is in turn can lead to use-after-free and NULL-pointer dereferences in racing ioctls (including a synchronous hangup) and in processing of racing asynchronous hangups (carrier loss).  Add the missing serialisation to tty_port_tty_vhangup() and tty_port_hangup() so that the former does not return until the port has been shut down also when there is a racing hangup.  Note that serial core does not use tty_port_hangup(), but it already holds the port mutex when clearing port->tty and shutting down the port in uart_hangup().",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99081",
                                "url": "https://ubuntu.com/security/CVE-2026-99081",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  bnxt_en: fix DMA mapping length for padded small packets  Stefan Fleischmann reported Intel IOMMU DMA Read faults on BCM57412 NetXtreme-E NICs when transmitting packets on VLAN/macvlan interfaces:    DMAR: [DMA Read NO_PASID] Request device [18:00.0] fault addr 0xfc499000         [fault reason 0x06] PTE Read access is not set   bnxt_en 0000:18:00.0 eno1np0: Abandoning msg {0xb4 0x41a} len: 0 due to firmware status: 0x2000001   ...   NETDEV WATCHDOG: eno1np0 (bnxt_en): transmit queue 0 timed out  The fault address (0xfc499000) is on an exact 4KB page boundary, pointing to a DMA read buffer overrun.  In bnxt_start_xmit(), packets smaller than BNXT_MIN_PKT_SIZE (52 bytes), such as 42-byte untagged ARP frames, are padded:      if (length < BNXT_MIN_PKT_SIZE) {         pad = BNXT_MIN_PKT_SIZE - length;         if (skb_pad(skb, pad))             goto tx_kick_pending;         length = BNXT_MIN_PKT_SIZE;     }      mapping = dma_map_single(&pdev->dev, skb->data, len, DMA_TO_DEVICE);     ...     dma_unmap_len_set(tx_buf, len, len);  However, 'len' was initialized earlier to skb_headlen(skb) (e.g. 42 bytes) and is left unadjusted after padding. Consequently, dma_map_single() and dma_unmap_len_set() map and track only 42 bytes.  Later, the hardware TX buffer descriptor is programmed with the padded length:      txbd->tx_bd_len_flags_type =         cpu_to_le32(((len + pad) << TX_BD_LEN_SHIFT) | flags |                     TX_BD_FLAGS_PACKET_END);  The NIC DMA engine is thus instructed to read 52 bytes from a region where only 42 bytes were DMA-mapped. If skb->data ends near the boundary of a 4KB page (within 'pad' bytes of the next page), the hardware DMA read overruns into the unmapped adjacent page, triggering an IOMMU fault.  This issue was exposed after commit 447cbe95ebb9 (\"vlan: fix skb_under_panic and races when toggling HW VLAN offload\") because reserving extra VLAN headroom rounded LL_RESERVED_SPACE from 48 up to 64 bytes, shifting skb->data offsets and potentially causing small frames to land right against page boundaries.  Fix this by using skb_put_padto(skb, BNXT_MIN_PKT_SIZE) in bnxt_start_xmit(), before skb_shinfo(skb)->nr_frags is sampled, because padding might linearize the skb. This ensures skb->len and skb_headlen(skb) reflect the padded size so that dma_map_single() maps the full buffer and the descriptor length is consistent. This also removes the temporary 'pad' variable and masking logic.  The padding is done after the SW USO branch, otherwise bnxt_sw_udp_gso_xmit() would account the padding as UDP payload and send it in extra segments.  Note that SW USO segments are still not padded: with IPv4, a segment carrying less than 10 bytes of UDP payload (small gso_size, or a short last segment) is sent as a frame shorter than BNXT_MIN_PKT_SIZE. This is a separate issue, left for a followup patch.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98696",
                                "url": "https://ubuntu.com/security/CVE-2026-98696",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  USB: serial: fix driver deregistration order  USB serial driver modules register one driver for the USB bus and one or more drivers for the ports on the USB serial bus.  When unloading a driver module, the USB driver must be deregistered before the USB serial bus drivers so that I/O is stopped before unbinding the ports to avoid use-after-free in completion handlers accessing port data.  Note that the \"new_id\" attributes must first be removed to prevent new ids from being added and triggering a probe of the USB driver after it has been deregistered.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98705",
                                "url": "https://ubuntu.com/security/CVE-2026-98705",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: mac80211: account proxy paths against the mesh path limit  Proxy-path churn can drive the interface path counter negative and let later mesh path additions exceed MESH_MAX_MPATHS.  mesh_path_free_rcu() decrements the interface mpaths counter for entries from both the mesh and proxy path tables, but mpp_path_add() never reserves a slot in that counter. Removing or expiring a proxy path therefore returns a slot that was never charged.  mesh_path_add() uses the same counter to enforce MESH_MAX_MPATHS, so once it falls below the number of installed paths the limit no longer holds.  Reserve the shared quota before allocating a proxy path and release it on every unsuccessful addition. Mesh and proxy paths now share one 1024-entry budget, so mpp_path_add() can return -ENOSPC at that limit.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98722",
                                "url": "https://ubuntu.com/security/CVE-2026-98722",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  mtd: block2mtd: Fix divide error when erase_size is zero  The erase size is parsed from the \"block2mtd\" module parameter and can be set to zero. add_device() then evaluates          if (size % erase_size)  with a zero divisor, which triggers a divide error:  divide error: 0000 [#1] PREEMPT SMP PTI RIP: 0010:add_device drivers/mtd/devices/block2mtd.c:296 [inline] RIP: 0010:block2mtd_setup2+0x592/0xda0 drivers/mtd/devices/block2mtd.c:459 Call Trace: block2mtd_setup+0x27/0xe0 drivers/mtd/devices/block2mtd.c:476 param_attr_store+0x214/0x310 kernel/params.c:589 module_attr_store+0x65/0x90 kernel/params.c:904 kernfs_fop_write_iter+0x3a4/0x540 fs/kernfs/file.c:345 ...  Reject a zero erase size before performing the modulo operation so the existing \"erasesize must be a divisor of device size\" error path reports the invalid argument and frees the device.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98695",
                                "url": "https://ubuntu.com/security/CVE-2026-98695",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  USB: serial: fix ioctl hangup race  The tty ioctls can race with hangup and end up calling into a tty driver for a device that is already gone or powered down.  Serialise the callbacks using the tty port mutex and add the missing checks to make sure the port has not been hung up before accessing port driver data or hardware.  This specifically avoids dereferencing a NULL-pointer if a device is disconnected during lengthy break signalling.  Note that TIOCGICOUNT and TIOCMIWAIT do not access port driver data or hardware and are therefore not affected by the race.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98694",
                                "url": "https://ubuntu.com/security/CVE-2026-98694",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  thunderbolt: Fix KASAN reported use-after-free when request is canceled  Alan reported that when doing stress testing sometimes KASAN notices use-after-free during control channel operation (stripped down keeping the relevant parts):   BUG: KASAN: slab-use-after-free in tb_cfg_request_sync+0x240/0x250 [thunderbolt]  Read of size 24 at addr ffff88811067f290 by task kworker/u40:2/1760   <TASK>   tb_cfg_request_sync+0x240/0x250 [thunderbolt]   tb_cfg_read_raw+0x367/0x510 [thunderbolt]   tb_cfg_read+0xec/0x240 [thunderbolt]   tb_port_get_link_generation+0x258/0x420 [thunderbolt]   tb_usb3_consumed_bandwidth+0x1c1/0x2c0 [thunderbolt]   tb_tunnel_consumed_bandwidth+0xfd/0x910 [thunderbolt]   tb_available_bandwidth+0x5f2/0xeb0 [thunderbolt]   tb_recalc_estimated_bandwidth+0x2a0/0x1bc0 [thunderbolt]   tb_handle_dp_bandwidth_request+0x1897/0x5e20 [thunderbolt]   process_one_work+0x675/0x1230   worker_thread+0x5e6/0xf70   kthread+0x365/0x470   ret_from_fork+0x54d/0x710   ret_from_fork_asm+0x1a/0x30   </TASK>   Allocated by task 1760:   __kmalloc_cache_noprof+0x1ee/0x550   tb_cfg_read_raw+0x1d3/0x510 [thunderbolt]   tb_cfg_read+0xec/0x240 [thunderbolt]   tb_port_get_link_generation+0x258/0x420 [thunderbolt]   tb_usb3_consumed_bandwidth+0x1c1/0x2c0 [thunderbolt]   tb_tunnel_consumed_bandwidth+0xfd/0x910 [thunderbolt]   tb_available_bandwidth+0x5f2/0xeb0 [thunderbolt]   tb_recalc_estimated_bandwidth+0x2a0/0x1bc0 [thunderbolt]   tb_handle_dp_bandwidth_request+0x1897/0x5e20 [thunderbolt]   process_one_work+0x675/0x1230   worker_thread+0x5e6/0xf70   kthread+0x365/0x470   ret_from_fork+0x54d/0x710   ret_from_fork_asm+0x1a/0x30   Freed by task 926:   kfree+0x18f/0x4a0   tb_cfg_request_put+0xb7/0xe0 [thunderbolt]   tb_cfg_request_work+0x82/0x120 [thunderbolt]   process_one_work+0x675/0x1230   worker_thread+0x5e6/0xf70   kthread+0x365/0x470   ret_from_fork+0x54d/0x710   ret_from_fork_asm+0x1a/0x30   Second to last potentially related work creation:   __queue_work+0x575/0xd00   queue_work_on+0x77/0x80   tb_cfg_request_cancel+0xc7/0x260 [thunderbolt]   tb_cfg_request_sync+0x1f6/0x250 [thunderbolt]   tb_cfg_read_raw+0x367/0x510 [thunderbolt]   tb_cfg_read+0xec/0x240 [thunderbolt]   tb_port_get_link_generation+0x258/0x420 [thunderbolt]   tb_usb3_consumed_bandwidth+0x1c1/0x2c0 [thunderbolt]   tb_tunnel_consumed_bandwidth+0xfd/0x910 [thunderbolt]   tb_available_bandwidth+0x5f2/0xeb0 [thunderbolt]   tb_recalc_estimated_bandwidth+0x2a0/0x1bc0 [thunderbolt]   tb_handle_dp_bandwidth_request+0x1897/0x5e20 [thunderbolt]   process_one_work+0x675/0x1230   worker_thread+0x5e6/0xf70   kthread+0x365/0x470   ret_from_fork+0x54d/0x710   ret_from_fork_asm+0x1a/0x30  The last stack trace is helpful because it shows that we are cancelling a request and looking at tb_cfg_request_cancel() what might happen is that tb_cfg_request_work() completes right before tb_cfg_request_cancel() starts and because of this it will call schedule_work() queueing the same work to run again. However, it is already removed from the request_queue and reference count is dropped so when tb_cfg_request_work() triggers again it will access memory that is already released.  Fix this so that we first make sure a cancelled request is not handed away from tb_cfg_request_find() or scheduled to run. Then instead of relying on the worker to clean up the request we will do it in tb_cfg_request_cancel() after the work is canceled from running. Make tb_cfg_request_dequeue() release the request only if it was actually removed from the queue.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98704",
                                "url": "https://ubuntu.com/security/CVE-2026-98704",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: mac80211: keep fallback association elements alive  Associating to a non-transmitted MBSSID profile reads freed memory while determining the operating channel and applying HT capabilities.  When an association response omits WMM, HT, or VHT information, ieee80211_assoc_config_link() parses the cached BSS IEs and copies the missing element pointers out of that fallback parse. For a non-transmitted MBSSID profile those pointers refer to merged-profile storage owned by the parse object, and the fallback block frees that object at its end. The copied pointers are used afterwards to determine the operating channel, configure bandwidth, and apply HT capabilities.  Keep the fallback parse result alive until association setup finishes.  [reorder variable declaration]",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98707",
                                "url": "https://ubuntu.com/security/CVE-2026-98707",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: mac80211: shut down RX BA session timer on teardown  Tearing down an RX BA session can leave the session timer queued on a freed tid_rx. Later timer-wheel processing and the timer callback itself then run against freed memory.  An RX BAR handler can dereference tid_rx under RCU before teardown unpublishes it and stay in its read-side critical section while teardown deletes the session timer. The stale handler can then rearm the timer after timer_delete_sync() returns and before the RCU callback frees tid_rx.  Use timer_shutdown_sync() so rearm attempts become ineffective once teardown starts. Keep reorder_timer unchanged: teardown marks the session removed under reorder_lock and its release path checks that state before rearming. session_timer has no equivalent guard because ieee80211_rx_h_ctrl() rearms it before taking reorder_lock.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98749",
                                "url": "https://ubuntu.com/security/CVE-2026-98749",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  tty: serial: max3100: shut down timer before freeing port  max3100_shutdown() stops the polling timer but returns early during system suspend. If the SPI device is unbound before resume, the serial core does not call max3100_shutdown() again, so max3100_remove() frees the port while the timer remains armed. max3100_timeout() may then access the freed port and re-arm the timer.  Add final timer teardown to max3100_remove() and use timer_shutdown_sync() to prevent a racing callback from re-arming it. Also free the IRQ and destroy the workqueue there before freeing the port. Keep timer_delete_sync() in max3100_shutdown() so that a subsequent open() can re-arm the timer.  The workqueue is created before request_irq() and destroyed on both request_irq() failure and normal shutdown. Its presence at remove thus identifies the IRQ left registered when suspend bypasses shutdown.  Free the IRQ before destroying the workqueue, in both max3100_shutdown() and max3100_remove(), and cancel the pending work in between. free_irq() waits for a running interrupt handler to finish and no new handler can start afterwards, so a racing handler cannot queue work on a workqueue that is being destroyed; the force_end_work check in max3100_dowork() only narrows that window, as a handler delayed between the check and queue_work() could still run after the teardown has cleared the workqueue pointer. Cancelling the work also keeps destroy_workqueue() from waiting on a queued work item in case remove() ever runs while the freezable workqueue is still frozen, e.g. device removal during the resume window, before workqueues are thawed.  This issue was found by an in-house static analysis tool.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98751",
                                "url": "https://ubuntu.com/security/CVE-2026-98751",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  tty: abort break signalling on hangup  The break ioctls can race with hangup and end up calling into a tty driver for a device that is already gone or powered down.  Drivers must handle this race, but TCSBRK and TCSBRKP should still be aborted to avoid calling back into the driver after a user-controlled timeout (possibly even after the tty has been reopened).  Note that drivers should disable any break state on shutdown so just return on hangup (calling break_ctl() again is racy and will most likely fail for drivers handling the race).",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98753",
                                "url": "https://ubuntu.com/security/CVE-2026-98753",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  tty: tty_port: restore TTY_IO_ERROR on activation failure  Make sure to restore the TTY_IO_ERROR flag if activation fails to prevent I/O attempts on a port that is gone or powered down.  This specifically avoids issues like kernel panic due to unclocked accesses or NULL-pointer dereferences when accessing powered down or deregistered ports when a TTY ioctl races with hangup and open.  Note that the flag is set again in tty_port_close() but not restoring it on activation failure leaves a window where drivers fail to handle the ioctl-hangup race.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98762",
                                "url": "https://ubuntu.com/security/CVE-2026-98762",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  USB: dwc2: shut down wakeup timer before freeing HCD state  dwc2_wakeup_detected() accesses the DWC2 host state and can rearm the wakeup timer.  dwc2_hcd_free() currently deletes the timer only after freeing host-owned state, and timer_delete() does not synchronize a callback or prevent it from being queued again.  Stop and shut down the timer in dwc2_hcd_release(), before the HCD resources are freed.  This covers both the HCD initialization error path and normal HCD removal.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98784",
                                "url": "https://ubuntu.com/security/CVE-2026-98784",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  drm/amdgpu/gfx6: fix firmware leak on teardown  The firmware requested in gfx_v6_0_init_microcode() is not released when the GFX block is torn down, leaking the firmware resources.  Add gfx_v6_0_free_microcode() and call it from gfx_v6_0_sw_fini() to release the PFP, ME, CE and RLC firmware.  (cherry picked from commit 386e81346f95ab0be5a82c5535de932e7a456924)",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98779",
                                "url": "https://ubuntu.com/security/CVE-2026-98779",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  drm/amdgpu: fix ACP MFD device leak on init failure  acp_hw_init() registers ACP child devices with mfd_add_devices() before attaching them to the ACP power domain and initializing the hardware.  If attaching a child to the power domain fails, or if the ACP reset or clock enable operation times out, the failure path frees only the source cell, resource, and platform-data allocations. The child platform devices already registered by mfd_add_devices() remain registered and are never released.  Remove the children from the power domain and unregister the MFD devices on failures that occur after mfd_add_devices() succeeds. Keep mfd_add_devices() failures on the existing cleanup path since the MFD core already rolls back partially registered children itself.  The issue was identified by a static analysis tool I developed and confirmed by manual review.  (cherry picked from commit 63da68d6a2279ec945581c990c5a59a5ae8b5560)",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98742",
                                "url": "https://ubuntu.com/security/CVE-2026-98742",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ALSA: seq: Serialize compat port-info ioctls  The native sequencer ioctl path serializes handler calls with client->ioctl_mutex, but the translated port-info compat path invokes the same handlers through snd_seq_kernel_client_ctl() without taking that mutex.  This lets concurrent compat CREATE_PORT requests pass the port-count check before any request reaches the serialized insertion. The computed integer port index can then exceed the address field range and wrap to an existing index. Subsequent subscriber teardown can resolve the duplicate address to the wrong port and access a freed subscriber.  Take ioctl_mutex while dispatching converted port-info requests, matching the native ioctl path. All translated port-info commands share this helper, so their accesses to the client port state are serialized as well.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98655",
                                "url": "https://ubuntu.com/security/CVE-2026-98655",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  perf: Require kernel access for text poke events  Perf events with exclude_kernel=1 can be opened without kernel perf access. However, exclude_kernel does not suppress text-poke sideband records. Every PERF_RECORD_TEXT_POKE is marked PERF_RECORD_MISC_KERNEL and contains a raw kernel instruction address.  An unprivileged task can therefore open and mmap a task-local software event with text_poke=1. Both opening a count-only tracepoint event and configuring UDP GRO for ESP-in-UDP cause updates to inline static calls; the observer receives the relocated addresses of the modified instructions. For a known kernel image, any such address reveals the runtime kernel text base despite KASLR.  Call perf_allow_kernel() whenever attr.text_poke is set, regardless of exclude_kernel. Events that neither monitor kernel execution nor request text-poke records retain their existing permissions.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98750",
                                "url": "https://ubuntu.com/security/CVE-2026-98750",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  tty: fix saved termios reset race  Resetting saved termios state on device registration is needed where a minor number can be reused for an entirely different device and where the old settings may prevent the port from even being opened (e.g. when CLOCAL is not set).  Not all TTY drivers guarantee that the minor number is no longer in use when registering devices however, something which can lead to a use-after-free when closing a TTY (and saving its termios) races with re-registration.  Add a new TTY_DRIVER_RESET_SAVED_TERMIOS flag to request that any saved termios state is reset on registration and only set it for drivers that make sure that the minor number is no longer in use.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-89638",
                                "url": "https://ubuntu.com/security/CVE-2026-89638",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  smb: client: clear setuid/setgid bit on write with cifsacl/modefromsid/posix extensions  When a file has the setuid or setgid bit set and is written to, the VFS strips those bits and issues a setattr with ATTR_KILL_SUID/ATTR_KILL_SGID together with an ATTR_MODE carrying the already-cleared mode.  Both cifs_setattr_unix() and cifs_setattr_nounix() unconditionally dropped ATTR_MODE in that case:  \t/* skip mode change if it's just for clearing setuid/setgid */ \tif (attrs->ia_valid & (ATTR_KILL_SUID|ATTR_KILL_SGID)) \t\tattrs->ia_valid &= ~ATTR_MODE;  This is fine for the default mount, where the mode is only emulated via the DOS read-only attribute and cannot represent the setuid/setgid bits anyway.  However, with the \"cifsacl\" or \"modefromsid\" mount options the mode is stored on the server through an ACL (id_mode_to_cifs_acl()), with the SMB3.1.1 POSIX extensions the mode is sent to the server directly, and with the SMB1 Unix extensions (cifs_setattr_unix) the mode is sent via CIFSSMBUnixSetPathInfo().  In all those cases dropping ATTR_MODE means the cleared mode is never pushed to the server, so the setuid/setgid bit survives the write.  This is a security issue: on local filesystems the setuid bit is stripped when a file is written, but over these cifs.ko mounts the bit persists on the server, potentially allowing an unexpected privilege escalation on subsequent execution.  Fix this in two places:    1. cifs_setattr_nounix(): only take the \"skip mode change\" shortcut      when the mode is emulated via the DOS read-only attribute (i.e.      neither cifsacl/modefromsid nor the SMB3.1.1 POSIX extensions are      in effect), so that the cleared mode is propagated to the server      in the ACL / POSIX cases.    2. cifs_setattr_unix(): this function is only called when Unix      extensions are in effect, so the mode is always stored on the      server.  Remove the shortcut entirely so that the cleared mode is      always pushed.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-09-11 20:19:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98375",
                                "url": "https://ubuntu.com/security/CVE-2026-98375",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  xen/netfront: drop RX packets with a short Ethernet header  handle_incoming_queue() pulls pull_to bytes into the head before calling eth_type_trans().  pull_to is the length of the first RX slot, capped at RX_COPY_THRESHOLD, and that length comes from the backend. Nothing checks it against ETH_HLEN.  If the first slot is shorter than ETH_HLEN and more slots follow, the head ends up shorter than an Ethernet header while skb->len is longer, and eth_type_trans() BUG()s in __skb_pull().  If the whole packet is shorter than ETH_HLEN, eth_type_trans() reads the header past the end of the data instead.  Pull at least ETH_HLEN, and drop the packet if that fails, which also drops packets too short to hold an Ethernet header.  This also checks the return value of the pull, which was ignored.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-09 08:16:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-89738",
                                "url": "https://ubuntu.com/security/CVE-2026-89738",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  usb: gadget: at91_udc: drain polled-VBUS timer/work before udc is freed  In polled-VBUS mode (board.vbus_pin && board.vbus_polled), probe arms a self-restarting cycle: at91_vbus_timer() schedules vbus_timer_work, and at91_vbus_timer_work() calls at91_vbus_update() and re-arms the timer via mod_timer(). Both recover the same udc through container_of and dereference it on every iteration.  Neither teardown path cancels this cycle. udc is devm-allocated, so it is freed after at91udc_remove() returns, and is likewise freed when probe fails and devres runs. A timer callback or work item that is pending or running at either point dereferences the freed udc.  Add at91_udc_shutdown_vbus_timer() and call it from at91udc_remove() and from the usb_add_gadget_udc() failure path in probe; the remaining probe error paths fail before the timer is armed. timer_shutdown_sync() waits for a running callback and clears timer->function, which makes the work handler's mod_timer() a permanent no-op; cancel_work_sync() then drains any pending or running work whose re-arm attempt now does nothing. The timer must be shut down first, since cancelling the work alone would let the timer re-queue it. The guard mirrors probe: in IRQ mode the timer and work_struct are never initialized.  This does not require a fault; a normal driver unbind can interleave with an already queued work item.  This issue was found by an in-house static analysis tool.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-09-11 20:20:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-89740",
                                "url": "https://ubuntu.com/security/CVE-2026-89740",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  serial: imx: serialize imx_uart_ports[] lifetime  imx_uart_probe() publishes its devm-allocated port in imx_uart_ports[] before uart_add_one_port() because console setup uses the table. The entry is not cleared when adding the port fails or after removal, leaving a dangling pointer.  A sibling probe can register the shared console through that stale entry. This was reproduced under KASAN on QEMU mcimx6ul-evk by unbinding a sibling UART, unbinding the console UART and rebinding the sibling.  Keep the entry valid through uart_remove_one_port(), then clear it. Protect port addition and removal together with their table updates so sibling operations cannot interleave. Reject an occupied slot rather than clobbering an active port during a duplicate-line probe.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-09-11 20:20:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-74341",
                                "url": "https://ubuntu.com/security/CVE-2026-74341",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: wcn36xx: fix heap overflow from oversized firmware HAL response  The firmware response dispatcher copies all synchronous HAL responses into the 4096-byte hal_buf without validating the response length. A response exceeding WCN36XX_HAL_BUF_SIZE causes a heap buffer overflow with firmware-controlled content.  Add a bounds check on the response length.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-08-15 06:22:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-74406",
                                "url": "https://ubuntu.com/security/CVE-2026-74406",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  vxlan: Fix potential null-ptr-deref in vxlan_gro_prepare_receive().  udp_tunnel_sock_release() could set sk->sk_user_data to NULL while vxlan_gro_prepare_receive() is running.  Let's check if rcu_dereference_sk_user_data() is NULL after skb_gro_remcsum_init().",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-08-15 06:22:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-46265",
                                "url": "https://ubuntu.com/security/CVE-2026-46265",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  RDMA/hns: Fix WQ_MEM_RECLAIM warning  When sunrpc is used, if a reset triggered, our wq may lead the following trace:  workqueue: WQ_MEM_RECLAIM xprtiod:xprt_rdma_connect_worker [rpcrdma] is flushing !WQ_MEM_RECLAIM hns_roce_irq_workq:flush_work_handle [hns_roce_hw_v2] WARNING: CPU: 0 PID: 8250 at kernel/workqueue.c:2644 check_flush_dependency+0xe0/0x144 Call trace:   check_flush_dependency+0xe0/0x144   start_flush_work.constprop.0+0x1d0/0x2f0   __flush_work.isra.0+0x40/0xb0   flush_work+0x14/0x30   hns_roce_v2_destroy_qp+0xac/0x1e0 [hns_roce_hw_v2]   ib_destroy_qp_user+0x9c/0x2b4   rdma_destroy_qp+0x34/0xb0   rpcrdma_ep_destroy+0x28/0xcc [rpcrdma]   rpcrdma_ep_put+0x74/0xb4 [rpcrdma]   rpcrdma_xprt_disconnect+0x1d8/0x260 [rpcrdma]   xprt_rdma_connect_worker+0xc0/0x120 [rpcrdma]   process_one_work+0x1cc/0x4d0   worker_thread+0x154/0x414   kthread+0x104/0x144   ret_from_fork+0x10/0x18  Since QP destruction frees memory, this wq should have the WQ_MEM_RECLAIM.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-06-03 18:16:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98681",
                                "url": "https://ubuntu.com/security/CVE-2026-98681",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  smb: client: split cifsFileInfo bitfields to avoid shared-byte RMW races  The invalidHandle, swapfile, oplock_break_cancelled, offload, and status_file_deleted fields are stored in the same bitfield byte in struct cifsFileInfo, but are updated in different code paths that may run simultaneously, and are protected by different locks.  Since bitfield assignments generate byte-level read-modify-write operations, a modification to one flag can overwrite a concurrent modification to another flag.  To avoid these races, convert these flags from a bitfield to separate bool fields.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-89539",
                                "url": "https://ubuntu.com/security/CVE-2026-89539",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  SUNRPC: reject duplicate CREDS_VALUE options  gssx_dec_option_array() walks the wire-supplied option array and, for every entry whose name matches CREDS_VALUE, calls gssx_dec_linux_creds() on the same struct svc_cred. That helper unconditionally installs a fresh groups_alloc() result into creds->cr_group_info without releasing whatever pointer was already there:      for (i = 0; i < count; i++) {         ... decode name ...         if (length == sizeof(CREDS_VALUE) &&             memcmp(p, CREDS_VALUE, sizeof(CREDS_VALUE)) == 0) {             err = gssx_dec_linux_creds(xdr, creds);             ...         }     }  A reply that carries two CREDS_VALUE entries therefore overwrites cr_group_info on the second iteration and orphans the group_info allocated by the first call. The earlier free_creds path only releases the last cr_group_info via free_svc_cred(), so the first allocation's refcount stays at one and its kvmalloc-backed storage is leaked. No in-tree caller of gssp_accept_sec_context_upcall() expects more than one CREDS_VALUE per reply.  Fix by tracking whether a CREDS_VALUE option has already been decoded and returning -EINVAL on any subsequent match, so the free_creds path releases the single group_info that was installed.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-09-11 20:19:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-93179",
                                "url": "https://ubuntu.com/security/CVE-2026-93179",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  drm/amd/powerplay: fix VoltageObjectInfo zero-stride loop and OOB read  Reject voltage objects whose usSize is smaller than the header or would advance the cursor past the table end, preventing an infinite loop or heap OOB read when the VBIOS supplies a malformed VoltageObjectInfo table.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-09-17 17:18:00 UTC"
                            },
                            {
                                "cve": "CVE-2023-52561",
                                "url": "https://ubuntu.com/security/CVE-2023-52561",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  arm64: dts: qcom: sdm845-db845c: Mark cont splash memory region as reserved  Adding a reserved memory region for the framebuffer memory (the splash memory region set up by the bootloader).  It fixes a kernel panic (arm-smmu: Unhandled context fault at this particular memory region) reported on DB845c running v5.10.y.",
                                "cve_priority": "low",
                                "cve_public_date": "2024-03-02 22:15:00 UTC"
                            },
                            {
                                "cve": "CVE-2023-53651",
                                "url": "https://ubuntu.com/security/CVE-2023-53651",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  Input: exc3000 - properly stop timer on shutdown  We need to stop the timer on driver unbind or probe failures, otherwise we get UAF/Oops.",
                                "cve_priority": "low",
                                "cve_public_date": "2025-10-07 16:15:00 UTC"
                            },
                            {
                                "cve": "CVE-2023-53733",
                                "url": "https://ubuntu.com/security/CVE-2023-53733",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net: sched: cls_u32: Undo tcf_bind_filter if u32_replace_hw_knode  When u32_replace_hw_knode fails, we need to undo the tcf_bind_filter operation done at u32_set_parms.",
                                "cve_priority": "medium",
                                "cve_public_date": "2025-10-24 12:15:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98657",
                                "url": "https://ubuntu.com/security/CVE-2026-98657",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  iio: proximity: pulsedlight: fix iio_device left registered on PM setup failure  pm_runtime_set_active() failing in probe() jumps to error_unreg_buffer, which only calls iio_triggered_buffer_cleanup() -- it does not undo the iio_device_register() that already succeeded a few lines above. probe() then returns the error, the devm-managed indio_dev is freed, but the iio core still has it registered: the sysfs/chardev nodes stay live and point at freed memory.  Add an error_unreg_dev label that unregisters the iio device before falling through to the existing buffer cleanup, mirroring the teardown order already used in lidar_remove().",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98662",
                                "url": "https://ubuntu.com/security/CVE-2026-98662",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  iio: light: gp2ap020a00f: drain irq_work after free_irq  The threaded IRQ handler queues data->work through irq_work_queue() so the trigger is polled from a per-CPU context.  free_irq() does not flush an irq_work the handler already queued, so after gp2ap020a00f_remove() returns that work may still run and call iio_trigger_poll() on data->trig, which the devm cleanup has already freed, causing a use-after-free.  Add irq_work_sync(&data->work) after free_irq() in remove() and in the probe error path, mirroring commit 78601726d4a5 (\"iio: trigger: sysfs: fix use-after-free on remove\").  Found by an in-house static analysis tool, confirmed by manual review.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98663",
                                "url": "https://ubuntu.com/security/CVE-2026-98663",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  iio: imu: adis16480: fix unprotected debugfs reads  The firmware_revision and firmware_date file operations are open coded and never call debugfs_file_get(), which debugfs_create_file_unsafe() requires. debugfs_remove_recursive() therefore does not wait for a read in progress, and unbind frees the iio_dev underneath it.  Use debugfs_create_file() instead.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98664",
                                "url": "https://ubuntu.com/security/CVE-2026-98664",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  iio: imu: adis16400: fix unprotected debugfs reads  adis16400_serial_number_fops is open coded and never calls debugfs_file_get(), so debugfs_remove_recursive() does not wait for a read in progress and unbind frees the iio_dev underneath it.  Commit ae1d37a9bb4b (\"iio: imu: adis16400: use DEFINE_DEBUGFS_ATTRIBUTE instead of DEFINE_SIMPLE_ATTRIBUTE\") converted product_id and flash_count to DEFINE_DEBUGFS_ATTRIBUTE, which protects itself, but moved all three files to debugfs_create_file_unsafe().  serial_number prints three registers as \"%.4x-%.4x-%.4x\" and DEFINE_DEBUGFS_ATTRIBUTE() formats a single u64, so it cannot be converted without changing what the file returns. adis16475 and adis16550 already use debugfs_create_file() for their open coded files. Use it here too.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98666",
                                "url": "https://ubuntu.com/security/CVE-2026-98666",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  iio: gyro: adis16136: fix unprotected debugfs reads  The serial_number file operations are open coded and never call debugfs_file_get(), which debugfs_create_file_unsafe() requires. debugfs_remove_recursive() therefore does not wait for a read in progress, and unbind frees the iio_dev underneath it.  Use debugfs_create_file() instead.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98671",
                                "url": "https://ubuntu.com/security/CVE-2026-98671",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  iio: adc: sun4i-gpadc-iio: clean up on thermal zone registration failure  If devm_thermal_of_zone_register() fails, probe returns without unregistering the IIO map array or disabling runtime PM.  Jump to err_map to release them.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98679",
                                "url": "https://ubuntu.com/security/CVE-2026-98679",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  iio: accel: kxcjk-1013: reject duplicate event disable  The IIO core does not filter duplicate writes to the event enable attribute. kxcjk1013_write_event_config() already ignores repeated enable requests, but a repeated disable request still calls kxcjk1013_set_power_state(data, false), dropping a runtime PM reference that was not acquired for this request. This can underflow the runtime PM usage count and trigger a \"Runtime PM usage count underflow\" warning.  Return early when the requested state already matches ev_enable_state.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98687",
                                "url": "https://ubuntu.com/security/CVE-2026-98687",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  thunderbolt: Reject oversized XDomain properties responses  tb_xdp_properties_request() allocates room for 45 data dwords in its 252-byte response buffer.  The XDomain length field is six bits wide, however, and a malicious peer can set it to 63.  After the fixed response fields are subtracted, the driver treats this as 48 data dwords.  Commit 322e93448d90 (\"thunderbolt: Clamp XDomain response data copy to allocation size\") only bounds the copy against data_len.  If data_len is at least 48, memcpy() reads 192 bytes from the 180-byte res->data array, causing a 12-byte heap out-of-bounds read.  Commit 4db2bd2ed478 (\"thunderbolt: Limit XDomain response copy to actual frame size\") limits the earlier copy but does not constrain this header-derived length.  Reject response data lengths that exceed the allocated source buffer before copying them into the assembled property block.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98697",
                                "url": "https://ubuntu.com/security/CVE-2026-98697",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  USB: serial: fix dynamic id driver deregistration race  Only free the dynamic ids after having deregistered the driver and removed the \"new_id\" attribute to avoid leaking any id added by a racing write to the attribute.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98698",
                                "url": "https://ubuntu.com/security/CVE-2026-98698",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: mac80211: handle empty FILS association request payload  fils_encrypt_assoc_req() accepts a (Re)Association Request frame whose last element is the FILS Session element.  crypt_len is then zero and aes_siv_encrypt() is called with an empty plaintext.  kmemdup() returns ZERO_SIZE_PTR for a zero-length allocation, so the unconditional sg_init_one() puts an invalid page into the scatterlist. With CONFIG_DEBUG_SG this triggers a kernel BUG in sg_set_buf(); without the debug check the bogus page is handed to the crypto backend.  AES-SIV is defined for empty plaintext and the S2V result is then the complete output, so handle this case before the CTR step, which has nothing to encrypt.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98701",
                                "url": "https://ubuntu.com/security/CVE-2026-98701",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: mac80211: release mesh path quota on failed additions  Repeated failed or duplicate mesh path additions can exhaust MESH_MAX_MPATHS while the path table holds fewer paths, which stops new paths to reachable destinations from being created.  mesh_path_add() reserves a slot before allocating and inserting a path. If allocation fails, the function returns without releasing the slot. If the rhashtable insertion reports an error or an existing destination, the function discards its candidate but retains the reservation. No new path is installed in any of these cases.  Release the reservation whenever the candidate is not installed.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98703",
                                "url": "https://ubuntu.com/security/CVE-2026-98703",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: mac80211: minstrel_ht: validate fixed rate index  The fixed_rate_idx debugfs file is a plain u32 attribute, so any value can be written to it.  minstrel_ht_update_stats() then copies the value into mi->max_tp_rate[] and mi->max_prob_rate, and minstrel_ht_set_rate() uses MI_RATE_GROUP()/MI_RATE_IDX() to index minstrel_mcs_groups[] (42 entries) and mi->groups[].rates[] (10 entries) with it.  Writing e.g. 65535 selects group 4095 and rate index 15, far outside both arrays.  The out-of-bounds entries are dereferenced and updated as struct minstrel_rate_stats (retry counts, etc.), so the invalid index corrupts adjacent kernel memory.  With CONFIG_UBSAN_BOUNDS the access is reported as an array-index-out-of-bounds in minstrel_ht_set_rate().  Only a valid group/rate pair, or U32_MAX to disable fixed rate processing, can be used safely, so reject any other value when the debugfs file is written.  The file is only reachable through a root-only debugfs mount, so this is not a privilege boundary.  The out-of-bounds access is still a bug that must not be reachable through a writable debugfs attribute.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98706",
                                "url": "https://ubuntu.com/security/CVE-2026-98706",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: mac80211: drain PS delivery work during station teardown  Removing an AP or mesh station can notify the driver and wake TXQs after the station has already been removed from the driver, and can update num_sta_ps and the power-save queues after station cleanup has purged them.  sta_deliver_ps_frames() tests sta->dead only before it starts delivery. A worker that passes that test can be delayed while teardown sets sta->dead and removes the station from the driver; when it resumes it still runs the full delivery.  The existing cancel_work_sync() sits near the end of __cleanup_single_sta(), after the final driver state transition and after PS accounting and queue purging, so it drains the worker only once the state it has to protect has already changed. Before commit d34ba2168a3c (\"mac80211: don't delay station destruction\") cleanup was deferred through the same ordered workqueue as the delivery work, which kept the two ordered.  Cancel the work after setting sta->dead and before moving the driver state, and move the existing cancellation to the start of __cleanup_single_sta(). The first drain closes the driver-lifetime window; driver callbacks during the remaining state transitions can still queue drv_deliver_wk through ieee80211_sta_block_awake(), so retain the second drain at the start of __cleanup_single_sta(). That drain also covers insertion failures, which reach cleanup without setting sta->dead.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98710",
                                "url": "https://ubuntu.com/security/CVE-2026-98710",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: iwlegacy: 3945: free EEPROM data on remove  il3945_pci_probe() calls il_eeprom_init(), which allocates memory for the EEPROM data. The probe failure paths release this allocation with il_eeprom_free(), but the remove path does not free it after a successful probe.  As a result, the EEPROM data is leaked when the PCI device is removed.  Free the EEPROM data in il3945_pci_remove() before releasing the mac80211 hardware structure.  This issue was found by manual code inspection.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98711",
                                "url": "https://ubuntu.com/security/CVE-2026-98711",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: cw1200: fix TX padding OOB read leaking heap data to device  The TX path rounds the transfer size up to the bus alignment (align_size(), up to 511 bytes for SDIO, 1 byte for SPI) but sends the padded length straight from the frame buffer, which has no room reserved for the padding.  cw1200_data_write() therefore reads past the end of the frame and the bus transfer carries those bytes to the device.  A bogus device can collect up to 511 bytes of kernel heap data per TX frame.  The RX path does not have this problem: it allocates the skb with the aligned length (alloc_len) before reading.  Compute the exact padding with the bus align_size() callback, make sure queued TX frames have tailroom for it, and zero the padding bytes before the transfer so nothing past the frame is exposed.  This is not expected to change driver behavior on most cases: frame contents and transfer sizes are unchanged, only the content of the padding bytes (previously undefined stale memory, now zero), which the device never reads since the WSM header carries the real frame length.  The skb expansion can only fail under memory exhaustion, in which case the frame is dropped like on the existing error paths of cw1200_tx().  Discovered by Atuin - Automated Vulnerability Discovery Engine.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98721",
                                "url": "https://ubuntu.com/security/CVE-2026-98721",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  mtd: rawnand: cadence: Initialize IRQ state before requesting IRQ  The Cadence NAND interrupt handler uses both the IRQ lock and completion object. Registering the IRQ before initializing them leaves a window in which a pending interrupt can access uninitialized synchronization state.  Initialize them before registering the handler.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98726",
                                "url": "https://ubuntu.com/security/CVE-2026-98726",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  nvme-multipath: fix underflow in ANA log bounds checks  The number of ANA groups advertised through Identify Controller sizes the ANA log buffer. The ANA log header and group descriptors independently supply the number of groups and namespace IDs to parse.  Both bounds checks subtract an untrusted object size from ana_log_size before comparing the current offset. If the object is larger than the buffer, the size_t subtraction underflows and lets the parser read beyond ana_log_buf.  Check the current offset before the first subtraction and compare each object size with the remaining buffer instead. This rejects inconsistent ANA data before dereferencing a truncated group descriptor or walking an oversized namespace ID array.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98856",
                                "url": "https://ubuntu.com/security/CVE-2026-98856",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  kprobes: Skip disarmed probes when checking optkprobe overlap  On x86, an optkprobe at A replaces five bytes with a jump. If a disabled probe B is at A+2, get_optimized_kprobe() stops at B when arming a new probe C at A+4. It leaves A optimized:                A    A+1  A+2  A+3  A+4   A's jump  | e9 | d0 | d1 | d2 | d3 |   after C   | e9 | d0 | d1 | d2 | cc |  The INT3 for C overwrites the last byte of A's jump displacement, so execution can jump to the wrong address. B can have prepared optinsns while disarmed, but has no jump to unoptimize.  Continue past disarmed and unprepared probes to find the active optimized probe before arming a probe in its jump.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98857",
                                "url": "https://ubuntu.com/security/CVE-2026-98857",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ipvs: bound LBLCR and LBLC cache growth  ip_vs_lblcr_new() and ip_vs_lblc_new() create cache entries for every previously unseen destination address. The table max_size only tells the periodic collector to reclaim entries after the cache has already exceeded the limit. It does not reclaim entries that the attacker continues to use.  Reject new cache entries once either table reaches max_size * 3 / 2. The extra headroom lets the periodic collector catch up while the existing scheduler fallback continues to use the selected destination when cache creation fails. New traffic therefore stays serviceable without growing the tables further.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98732",
                                "url": "https://ubuntu.com/security/CVE-2026-98732",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  Bluetooth: btintel: fix buffer over-read in btintel_hw_error()  The \"Exception info %s\" print uses skb->data + 1, but the 12-byte payload is not guaranteed to be NUL-terminated and can be read past its end.  Bound the print with \"%.*s\" and skb->len - 1.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98735",
                                "url": "https://ubuntu.com/security/CVE-2026-98735",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  Bluetooth: hci_core: Serialize ACL scheduling with channel deletion  hci_chan_sent() selects a channel under RCU but drops the read lock before accessing chan->conn and returning the channel. The ACL and LE schedulers then use its packet queue and update its transmit counters without any protection against channel deletion.  After TX selects a channel and releases RCU, a disconnect command timeout on the separate request workqueue can run hci_conn_failed() and l2cap_conn_del(). hci_chan_del() can then unlink the channel, complete synchronize_rcu(), purge its queue and free it before TX resumes. This causes use-after-free both in hci_chan_sent() and in its callers.  KASAN reported:    BUG: KASAN: slab-use-after-free in hci_chan_sent+0x892/0x9b0   Workqueue: hci0 hci_tx_work   Call Trace:    hci_chan_sent+0x892/0x9b0    hci_tx_work+0x5e6/0xb70   Allocated by task 91:    hci_chan_create+0xe3/0x350    l2cap_conn_add.part.0+0x12/0xa30    l2cap_chan_connect+0x110d/0x1b60    l2cap_sock_connect+0x310/0x530   Freed by task 99:    hci_chan_del+0x11f/0x170    l2cap_conn_del+0x4f1/0x800    l2cap_connect_cfm+0x88c/0xd30    hci_conn_failed+0x150/0x250    hci_abort_conn_sync+0x3e3/0x800    hci_cmd_sync_run+0x7e/0xc0    hci_abort_conn+0x105/0x1f0    disconnect_sync+0x157/0x290    hci_cmd_sync_work+0x13c/0x290  Hold the existing device mutex across channel selection and transmission in both schedulers to serialize them with channel teardown. Keep timeout handling outside the critical sections because hci_link_tx_to() acquires the same mutex. This also permits the transmit path to sleep, unlike extending the RCU read-side critical section across packet submission.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98739",
                                "url": "https://ubuntu.com/security/CVE-2026-98739",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  Bluetooth: RFCOMM: Fix initial port reference race  For RFCOMM_RELEASE_ONHUP devices, rfcomm_tty_install() and __rfcomm_release_dev() both use RFCOMM_TTY_OWNED to decide who drops the initial tty_port reference. The release path tests the bit separately from the install path setting it, so both can drop that reference.  The synchronous hangup does not prevent this race: port->tty is not assigned until tty_port_open(), after installation. The following interleaving is possible:    1. Install and release each obtain a reference with rfcomm_dev_get().   2. Release observes RFCOMM_TTY_OWNED clear.   3. Install sets RFCOMM_TTY_OWNED and drops the initial reference.   4. Release drops the same initial reference again.   5. TTY cleanup drops its reference and frees the device.   6. Release performs its final tty_port_put() on the freed port.  KASAN reported:    BUG: KASAN: slab-use-after-free in tty_port_put+0x22/0x190   Write of size 4 at addr ffff8881001d3d5c by task poc/92    Call Trace:    tty_port_put+0x22/0x190    rfcomm_dev_ioctl+0x1d4/0x1930    sock_do_ioctl+0x110/0x260    sock_ioctl+0x380/0x590    __x64_sys_ioctl+0x134/0x1c0    Allocated by task 88:    rfcomm_dev_ioctl+0x8f6/0x1930    sock_do_ioctl+0x110/0x260    sock_ioctl+0x380/0x590    __x64_sys_ioctl+0x134/0x1c0    Freed by task 65:    kfree+0x131/0x3c0    rfcomm_dev_destruct+0x23b/0x2f0    release_one_tty+0xc1/0x370    process_one_work+0x661/0x1090  Use test_and_set_bit() in both paths so that only the caller that changes RFCOMM_TTY_OWNED from clear to set drops the initial reference. Each path keeps its own lookup reference until release or TTY cleanup, preserving the existing callback ordering and error handling.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98741",
                                "url": "https://ubuntu.com/security/CVE-2026-98741",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ALSA: ua101: reject mismatched capture/playback packet sizes  detect_usb_format() cross-checks bSubframeSize, bBitResolution and tSamFreq between the capture and playback interfaces, but never relates the two endpoints' wMaxPacketSize and bNrChannels.  Each playback URB gets a buffer of ua->playback.max_packet_bytes, while the number of bytes written into it is derived from the capture stream: capture_urb_complete() computes frames from the received capture packet and capture.frame_bytes, and start_usb_playback() and playback_work() multiply that by playback.frame_bytes.  A device declaring a large capture wMaxPacketSize with few capture channels and a small playback wMaxPacketSize with many playback channels therefore memset()s and memcpy()s past the end of the playback buffer, in open() of the PCM node the driver registers during probe. usb_submit_urb() rejects the over-long iso_frame_desc[0].length with -EMSGSIZE, but only after the write.  Reject such descriptors at probe time.  Genuine UA-101/UA-1000 hardware declares proportional packet sizes and is unaffected.    BUG: KASAN: slab-out-of-bounds in start_usb_playback (sound/usb/misc/ua101.c:586)   Write of size 2048 at addr ffff8881098f3c00 by task exploit/5021   Call Trace:    __asan_memset (mm/kasan/shadow.c:84)    start_usb_playback (sound/usb/misc/ua101.c:586)    playback_pcm_open (sound/usb/misc/ua101.c:679)    snd_pcm_open_substream (sound/core/pcm_native.c:2829)    snd_pcm_open (sound/core/pcm_native.c:2865 sound/core/pcm_native.c:2932)    snd_pcm_playback_open (sound/core/pcm_native.c:2891)    snd_open (sound/core/sound.c:166)    chrdev_open (fs/char_dev.c:411)    do_dentry_open (fs/open.c:996)    vfs_open (fs/open.c:1101)    path_openat (fs/namei.c:4837 fs/namei.c:5000)    do_file_open (fs/namei.c:5029)    do_sys_openat2 (fs/open.c:1417)    __x64_sys_openat (fs/open.c:1423 fs/open.c:1439 fs/open.c:1434)    do_syscall_64 (arch/x86/entry/syscall_64.c:61 arch/x86/entry/syscall_64.c:84)    entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:121)    The buggy address belongs to the object at ffff8881098f3c00    which belongs to the cache kmalloc-192 of size 192   The buggy address is located 0 bytes inside of    allocated 168-byte region [ffff8881098f3c00, ffff8881098f3ca8)",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98940",
                                "url": "https://ubuntu.com/security/CVE-2026-98940",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ASoC: qcom: lpass-cpu: use DAI table index for playback constraints  The DAI ID is a hardware port ID and is not necessarily the index of the corresponding entry in variant->dai_driver.  When configuring a DAI with LPAIF_I2SCTL_MODE_QUAD01, the probe code currently uses dai_id to index variant->dai_driver. This is incorrect for platforms where DAI IDs are sparse. For example, the IPQ806x MI2S DAI has ID 4 while it is the only entry in the DAI driver table. If that DAI is configured for QUAD01 and probe reaches this branch, the code writes beyond that single entry via dai_driver[4] instead of updating the DAI being processed.  Use the loop index i when updating the current DAI's playback channel constraints, while retaining dai_id for indexing the hardware-port specific playback SD-line mode array.  This fixes the incorrect DAI table access for platforms where the DAI ID does not match its position in the driver table.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98748",
                                "url": "https://ubuntu.com/security/CVE-2026-98748",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  serial: 8250_bcm7271: fix use-after-free in brcmuart_remove()  brcmuart_handle_irq() starts priv->hrt to work around a receive-timeout quirk of the 8250 core when hardware flow control is enabled; the timer callback brcmuart_hrtimer_func() dereferences priv.  brcmuart_remove() cancels the hrtimer before it unregisters the port, so a receive-timeout interrupt that arrives in between re-arms the timer. After devm frees priv, the callback runs on freed memory.  Unregister the port before cancelling the hrtimer. serial8250_unregister_port() shuts the port down and frees its IRQ, so brcmuart_handle_irq() can no longer restart the timer, and the final hrtimer_cancel() drains any timer that was armed before or during the unregister.  This issue was found by an in-house static analysis tool.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98754",
                                "url": "https://ubuntu.com/security/CVE-2026-98754",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  tty: vcc: hold port lock when clearing tty pointer in vcc_cleanup  vcc_cleanup() sets port->tty to NULL without holding port->lock, racing with vcc_event() LDC callbacks that read port->tty under port->lock and then use tty->port. This can cause a use-after-free when the callback dereferences tty->port after cleanup has already destroyed and freed it.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98755",
                                "url": "https://ubuntu.com/security/CVE-2026-98755",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  tty: vcc: zero-initialize control packet in vcc_send_ctl()  The stack-allocated struct vio_vcc pkt was partially initialized, leaving the tag.stype_env field uninitialized before being sent via ldc_write(), potentially leaking kernel stack data to the LDC peer.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98756",
                                "url": "https://ubuntu.com/security/CVE-2026-98756",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  usb: cdns3: Fix NULL pointer dereference in cdns3_pci_probe  The Cadence USBSS controller is a two-function PCI device. The first probed function allocates the driver data and stores it with pci_set_drvdata(), while the second function reuses it via pci_get_drvdata() when pci_is_enabled() reports that the first function has already been probed.  When the second function is probed while the first one has been enabled but has not yet set its driver data, pci_get_drvdata() returns NULL, and the subsequent wrap->devfn assignment dereferences a NULL pointer and crashes the kernel. logs: Call trace:   cdns3_pci_probe+0xa4/0x300   local_pci_probe+0x44/0xa8   pci_call_probe+0x54/0x158   pci_device_probe+0x84/0x100   really_probe+0x184/0x3d0   __driver_probe_device+0x80/0x178   driver_probe_device+0x44/0xe8   __driver_attach+0xec/0x1f8   bus_for_each_dev+0x7c/0xe0   driver_attach+0x28/0x38   bus_add_driver+0x110/0x238   driver_register+0x64/0x128   __pci_register_driver+0x50/0x60   cdns3_pci_driver_init+0x28/0x38   do_one_initcall+0x5c/0x280   do_initcalls+0x104/0x1d8   kernel_init_freeable+0x140/0x218   kernel_init+0x28/0x1f8   ret_from_fork+0x10/0x20  Return -EPROBE_DEFER in this case so that probing is retried after the first function has completed its probe.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98757",
                                "url": "https://ubuntu.com/security/CVE-2026-98757",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  usb: cdns3: fix use-after-free in cdns3_gadget_exit()  cdns3_gadget_start() arms two works on system_freezable_wq: pending_status_wq for the deferred ep0 status stage and aligned_buf_wq for realigned request buffers. Both handlers use the cdns3_device the works are embedded in, and cdns3_pending_setup_status_handler() also calls the ep0 request completion.  cdns3_gadget_exit() does not wait for these works. It frees all endpoints and aligned buffers and drops the last reference to the gadget device, which frees priv_dev, so a work queued before the exit can run after the free.  Fix this by waiting for both works after the gadget driver is unbound and the IRQ is freed, when no new work can be queued, and before the endpoints and buffers are released.  This issue was found by an in-house static analysis tool.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98760",
                                "url": "https://ubuntu.com/security/CVE-2026-98760",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  usb: typec: tipd: fix uninitialized typec_partner_desc in tps6598x_connect()  tps6598x_connect() passes a stack-allocated typec_partner_desc to typec_register_partner() after initializing only usb_pd, accessory and identity.  typec_register_partner() copies attach and deattach from the descriptor into the partner. With those fields left unset, garbage function pointers may be stored and later invoked from typec_partner_link_device() when a USB device is linked to the port. Uninitialized pd_revision and usb_capability similarly leak stack data through partner sysfs.  Zero-initialize the descriptor so optional callbacks remain NULL and the remaining fields are zero.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98761",
                                "url": "https://ubuntu.com/security/CVE-2026-98761",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  usb: typec: tcpm: recover after failure to start the frs ams  Reset the port if the tcpm fails to start the FAST_ROLE_SWAP AMS by initiating error recovery on it.  This helps in cases where some cables (incorrectly) signal an FRS to an FRS capable port during disconnection. The TCPC autonomously starts sourcing VBUS on detecting the FRS signal. However, the VBUS sourcing is left on when the FAST_ROLE_SWAP AMS fails to start (as tcpm_sink_tx_ok is 0 as CC is open due to the cable disconnect). This is because the code sets the state to INVALID_STATE without resetting the port state.  Log snippet before changes: [  101.401960] AMS FAST_ROLE_SWAP start [  101.401971] Sink TX No Go [  101.401982] sourcing vbus [  101.401987] VBUS on [  101.402159] VBUS on [  109.257809] CC1: 0 -> 0, CC2: 5 -> 0 [state SNK_READY, polarity 1, disconnected] [  111.267442] VBUS on  After changes: [   70.541211] AMS FAST_ROLE_SWAP start [   70.541220] Sink TX No Go [   70.541228] state change SNK_READY -> ERROR_RECOVERY [rev3 NONE_AMS] [   70.541362] VBUS on [   70.541365] sourcing vbus [   70.541367] VBUS on [   70.541374] state change ERROR_RECOVERY -> PORT_RESET [rev3 NONE_AMS] [   70.541410] disable vbus discharge ret:0 [   70.543028] Setting usb_comm capable false [   70.544009] Setting voltage/current limit 0 mV 0 mA [   70.544034] polarity 0 [   70.544239] Requesting mux state 0, usb-role 0, orientation 0 [   70.555550] cc:=0 [   70.555595] pending state change PORT_RESET -> PORT_RESET_WAIT_OFF @ 100 ms [rev3 NONE_AMS] [   70.555697] VBUS off [   70.555702] VBUS VSAFE0V [   70.555762] CC1: 5 -> 0, CC2: 0 -> 0 [state PORT_RESET, polarity 0, disconnected] [   70.587794] VBUS off [   70.587799] VBUS VSAFE0V [   70.655672] state change PORT_RESET -> PORT_RESET_WAIT_OFF [delayed 100 ms] [   70.655682] state change PORT_RESET_WAIT_OFF -> SNK_UNATTACHED [rev3 NONE_AMS] [   70.655686] Start toggling [   70.656274] CC1: 0 -> 0, CC2: 0 -> 0 [state TOGGLING, polarity 0, disconnected]",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98763",
                                "url": "https://ubuntu.com/security/CVE-2026-98763",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  usb: core: clear both ep_in and ep_out for non-ep0 control endpoints  In usb_enable_endpoint(), non-zero control endpoints (where usb_endpoint_xfer_control(&ep->desc) is true) populate both dev->ep_in[epnum] and dev->ep_out[epnum] with the same struct usb_host_endpoint pointer.  However, usb_disable_endpoint() only clears either dev->ep_out[epnum] or dev->ep_in[epnum] depending on the direction bit of epaddr when reset_hardware is set, leaving the opposite direction's array slot pointing to the disabled/freed endpoint.  Clear both dev->ep_out[epnum] and dev->ep_in[epnum] when disabling a non-ep0 control endpoint with reset_hardware set, and update the function kerneldoc accordingly.  Tested in QEMU against Linux 7.3.0-rc3 using dummy_hcd and raw-gadget to enumerate a USB device with a non-zero control endpoint (bEndpointAddress 0x01, bmAttributes USB_ENDPOINT_XFER_CONTROL), verifying that both dev->ep_in[1] and dev->ep_out[1] are cleared when the interface is disabled.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98764",
                                "url": "https://ubuntu.com/security/CVE-2026-98764",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  usb: gadget: f_fs: Fix NULL pointer dereference in FUNCTIONFS_ENDPOINT_DESC  When user space sets up FunctionFS with only full-speed descriptors (e.g., flags = FUNCTIONFS_HAS_FS_DESC) and the gadget operates at a higher speed (such as USB_SPEED_HIGH or USB_SPEED_SUPER), config_ep_by_speed() detects that the function lacks descriptors for the current speed, logs a warning, and falls back to full-speed descriptors. The endpoint is then successfully enabled via usb_ep_enable(), and epfile->ep becomes valid.  However, when user space subsequently issues the FUNCTIONFS_ENDPOINT_DESC ioctl to query the endpoint descriptor, ffs_epfile_ioctl() selects the descriptor index solely based on gadget->speed:  \tswitch (epfile->ffs->gadget->speed) { \tcase USB_SPEED_SUPER: \tcase USB_SPEED_SUPER_PLUS: \t\tdesc_idx = 2; \t\tbreak; \tcase USB_SPEED_HIGH: \t\tdesc_idx = 1; \t\tbreak; \tdefault: \t\tdesc_idx = 0; \t} \tdesc = epfile->ep->descs[desc_idx]; \tmemcpy(&desc1, desc, desc->bLength);  Because user space only supplied full-speed descriptors, epfile->ep->descs[1] is NULL. Dereferencing desc->bLength triggers an immediate kernel NULL pointer dereference panic.  Fix this by falling back through lower speed descriptors if the current speed descriptor was not supplied, matching the fallback logic in config_ep_by_speed() and historical f_fs behavior. If still missing, fall back to epfile->ep->ep->desc (the active descriptor), and return -EINVAL safely if no valid descriptor is found. In addition, mark desc as const to match struct usb_ep::desc and avoid discarding qualifiers.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98765",
                                "url": "https://ubuntu.com/security/CVE-2026-98765",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  USB: gadget: dummy-hcd: Fix wait for outstanding request completions  The dummy-hcd driver emulates synchronize_irq() by waiting until its private callback_usage counter drops to 0 (with the private lock not held).  This counter is incremented whenever a gadget driver callback occurs (which requires the private lock to be dropped), but not when a request completion handler is called.  This is an oversight.  Request completion is triggered by timer interrupts (emulating device IRQs in a real UDC), and the interrupt handlers are supposed to have completed when the synchronize_irq() emulation routine returns -- they aren't supposed to be in the middle of a completion callback.  If this happens it can lead to a gadget driver's unbind routine running before all outstanding request completions have finished, maybe even allowing the gadget driver's module to be unloaded while a completion handler is still running.  Fix the oversight by incrementing the callback_usage value across request completion callbacks.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98766",
                                "url": "https://ubuntu.com/security/CVE-2026-98766",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  usb: gadget: aspeed-vhub: cancel wake work on device removal  wake_work is armed from the gadget .wakeup callback to resume suspended downstream ports, and it is never cancelled in ast_vhub_remove(), so a work item queued before or during removal can run after devm has freed vhub and its ports, a use-after-free.  Cancelling the work alone is not sufficient: usb_gadget_wakeup() takes no lock and the unbind path never clears wakeup_en, so a remote-wakeup request in flight on another CPU can re-arm the work after the cancel and before vhub is freed.  ast_vhub_del_dev() already clears d->registered under vhub->lock before unregistering the gadget. Refuse the wakeup in ast_vhub_udc_wakeup() once d->registered is clear: the check and the schedule_work() are then atomic against the unbind, so a wakeup that passed before the flag was cleared is drained by the cancel_work_sync() after the del_dev loop, and one that arrives later returns without arming. Also move INIT_WORK() to the top of ast_vhub_probe(), since the probe error path reuses ast_vhub_remove() and would otherwise cancel a never-initialized work item.  This issue was found by an in-house static analysis tool.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98769",
                                "url": "https://ubuntu.com/security/CVE-2026-98769",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  usb: gadget: f_uac1_legacy: validate bRequest index in generic_{set,get}_cmd  generic_set_cmd() and generic_get_cmd() use the low nibble of ctrl->bRequest as an index into con->data[]:      u8 cmd = (ctrl->bRequest & 0x0F);  /* 0 .. 15 */     ...     con->data[cmd] = value;            /* OOB when cmd >= 5 */  struct usb_audio_control (include/linux/usb/audio.h) declares data as a 5-element array, so indices 5 through 15 write (or read) up to 44 bytes past the end of the array on the heap.  A malicious USB host can craft a class-specific SET_CUR / GET_CUR request with an arbitrary bRequest value, triggering the out-of-bounds access from an IRQ completion handler with no further preconditions.  Add an ARRAY_SIZE() guard to both functions.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98771",
                                "url": "https://ubuntu.com/security/CVE-2026-98771",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  usb: storage: sierra_ms: reject short SWoC info transfers  sierra_get_swoc_info() requests sizeof(struct swoc_info) (60) bytes from the device via usb_control_msg(), but its callers only treat a negative return value as failure. A device that answers the vendor-specific GetSwocInfo request with a short IN transfer is therefore accepted, leaving the tail of the freshly allocated (kmalloc(), non-zeroing) swoc_info buffer uninitialized.  truinst_show() subsequently prints swocInfo->rev, swocInfo->LinuxSKU and swocInfo->LinuxVer from that buffer into the world-readable (0444) \"truinst\" sysfs attribute. An emulated/malicious USB device (VID 0x1199, PID 0x0fff) can exploit this to disclose up to 5 bytes of stale kernel heap memory (kmalloc-64) to unprivileged userspace, once per sysfs read, indefinitely. On kernels built without init_on_alloc this leaks recently freed heap contents.  Only accept the transfer when the full structure was received. sierra_ms_init() already retries failed queries, so well-behaved devices are unaffected.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98772",
                                "url": "https://ubuntu.com/security/CVE-2026-98772",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  USB: serial: fix port tear down use-after-free  Some drivers for multiport devices access port driver data from completion handlers of shared URBs submitted at attach() or first open() and stopped at disconnect() or last close(), respectively.  A simple NULL check before accessing the driver data makes sure that a port state container has at least been allocated, but a completion handler can still race with port tear down.  Reorder the disconnect handling so that ports are not deregistered (and their driver data freed) until after all ports have been hung up and the driver disconnect() callback has run so that all I/O has been stopped.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98775",
                                "url": "https://ubuntu.com/security/CVE-2026-98775",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  nitro_enclaves: fix use-after-free on SLOT_ALLOC failure  When ne_create_vm_ioctl() fails the SLOT_ALLOC request after anon_inode_getfile() has succeeded, the error path calls fput(enclave_file) and then frees ne_enclave.  In normal userspace context, fput() defers the final __fput() via task_work. ne_enclave_release() therefore runs after ne_enclave has already been freed and dereferences ne_enclave->slot_uid, causing a use-after-free: KASAN: slab-use-after-free in ne_enclave_release.  The enclave has no slot allocated and is not yet linked into the enclaves list on this error path, so ne_enclave_release() is expected to return early when slot_uid is zero. However, reading slot_uid already accesses the freed object.  Clear enclave_file->private_data before fput() on the error path. ne_enclave_release() then returns immediately when private_data is NULL, leaving the ioctl error path as the sole owner of ne_enclave. This is safe because the file has not been fd_install()'d yet.  Tested on an AWS EC2 m5.2xlarge with CONFIG_KASAN=y. Without the patch, the reproducer triggers a KASAN slab-use-after-free on every SLOT_ALLOC failure. With the patch, no KASAN report is produced and the SLOT_ALLOC error is still returned. Normal enclave creation and teardown are unaffected.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98790",
                                "url": "https://ubuntu.com/security/CVE-2026-98790",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  perf: Fix race between perf_event_exit_task() and perf_pending_task()  A race condition exists between perf_event_exit_task() and perf_pending_task() during begin_new_exec().  During begin_new_exec(), perf_event_exit_task() may be called, and the PF_EXITING flag is not set on task. So perf_sigtrap() continues to execute and triggers WARN_ON_ONCE(event->ctx->task != current).  Since both task exit and exec paths can call perf_event_exit_task() which sets ctx->task to TASK_TOMBSTONE, fix this by explicitly checking if event->ctx->task equals TASK_TOMBSTONE and dropping the redundant PF_EXITING check.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98934",
                                "url": "https://ubuntu.com/security/CVE-2026-98934",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ipv6: sr: use skb_get_hash_net() in seg6_make_flowlabel()  Since commit d58e468b1112 (\"flow_dissector: implements flow dissector BPF hook\") __skb_flow_dissect() needs a net pointer, either from skb->dev, skb->sk, or since commit 3cbf4ffba5ee (\"net: plumb network namespace into __skb_flow_dissect\") a caller provided pointer.  syzbot was able to reach seg6_make_flowlabel() with an skb having neither skb->dev nor skb->sk set: a TIPC UDP bearer sends a discovery message through an IPv4 route using seg6 encap, while net.ipv6.seg6_flowlabel is set to 1.  seg6_make_flowlabel() already has a net pointer, use skb_get_hash_net().  WARNING: net/core/flow_dissector.c:1131 at __skb_flow_dissect+0x910/0x5368 net/core/flow_dissector.c:1126, CPU#0: syz.0.17/4930 Call trace:   __skb_flow_dissect+0x910/0x5368 net/core/flow_dissector.c:1126 (P)   __skb_get_hash_net+0xe0/0x29c net/core/flow_dissector.c:1903   skb_get_hash include/linux/skbuff.h:1663 [inline]   seg6_make_flowlabel+0xcc/0x1ec net/ipv6/seg6_iptunnel.c:132   __seg6_do_srh_encap+0x320/0xbf4 net/ipv6/seg6_iptunnel.c:161   seg6_do_srh+0x4b4/0xa44 net/ipv6/seg6_iptunnel.c:431   seg6_output_core+0x164/0x688 net/ipv6/seg6_iptunnel.c:681   seg6_output+0x44/0x1ac net/ipv6/seg6_iptunnel.c:744   lwtunnel_output+0x3d0/0x664 net/core/lwtunnel.c:356   dst_output include/net/dst.h:470 [inline]   ip_local_out+0x110/0x148 net/ipv4/ip_output.c:131   iptunnel_xmit+0x50c/0xd38 net/ipv4/ip_tunnel_core.c:97   udp_tunnel_xmit_skb+0x220/0x348 net/ipv4/udp_tunnel_core.c:187   tipc_udp_xmit+0x75c/0x9c0 net/tipc/udp_media.c:202   tipc_udp_send_msg+0x214/0x374 net/tipc/udp_media.c:274   tipc_bearer_xmit_skb+0x260/0x3b0 net/tipc/bearer.c:576   tipc_enable_bearer net/tipc/bearer.c:366 [inline]   __tipc_nl_bearer_enable+0xc90/0xfb0 net/tipc/bearer.c:1048   tipc_nl_bearer_enable+0x2c/0x48 net/tipc/bearer.c:1057   genl_family_rcv_msg_doit+0x1e4/0x2d4 net/netlink/genetlink.c:1114",
                                "cve_priority": "negligible",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2022-49622",
                                "url": "https://ubuntu.com/security/CVE-2022-49622",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  netfilter: nf_tables: avoid skb access on nf_stolen  When verdict is NF_STOLEN, the skb might have been freed.  When tracing is enabled, this can result in a use-after-free: 1. access to skb->nf_trace 2. access to skb->mark 3. computation of trace id 4. dump of packet payload  To avoid 1, keep a cached copy of skb->nf_trace in the trace state struct. Refresh this copy whenever verdict is != STOLEN.  Avoid 2 by skipping skb->mark access if verdict is STOLEN.  3 is avoided by precomputing the trace id.  Only dump the packet when verdict is not \"STOLEN\".",
                                "cve_priority": "medium",
                                "cve_public_date": "2025-02-26 07:01:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98794",
                                "url": "https://ubuntu.com/security/CVE-2026-98794",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ipvs: filter some flags received in the backup server  While the IPVS SYNC protocol is not secure by design we can still protect the backup server from messages that can wreak havoc.  This commit addresses problems from received connection flags or their combinations. We now drop messages as follows:  1. the NO_CPORT+TEMPLATE combination allows lookups for normal connections to hit template which can break in many ways. While the master does not sync connections with NO_CPORT flag, i.e. before they are established, we still accept NO_CPORT without TEMPLATE.  2. ONE_PACKET: it is not sent by master, so we do not expect it in backup. Before now it was ignored by IP_VS_CONN_F_BACKUP_MASK for protocol v1 while protocol v0 created connections that are not hashed and dropped immediately. Better to apply the IP_VS_CONN_F_BACKUP_MASK also to the flags from v0 messages for consistency with v1.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98805",
                                "url": "https://ubuntu.com/security/CVE-2026-98805",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  tipc: prevent GCM nonce reuse on peer key changes  TIPC can encrypt traffic between nodes using a different transmit key for each node. In this mode, the AES-GCM nonce for a packet sent to a known peer consists of a 32-bit prefix (a per-key salt XOR the peer's address) followed by a 64-bit counter. That counter is stored in the peer's RX crypto object. When the peer reports a change in which key it uses to receive packets, TIPC resets this counter. The sender can still be using the same TX key and salt, so subsequent packets reuse earlier nonces. This nonce reuse breaks confidentiality and exposes GCM's authentication key. This makes forgeries trivial: an attacker can exploit CTR malleability to alter captured ciphertexts and use the recovered authentication key to compute a valid tag for the modified ciphertext, under the same key and nonce.  Use the TX key's existing aead->seqno counter instead. All encryptions using that key object share the same atomic counter, so concurrent encryptions get distinct nonce counter values. The counter survives key activation and peer reconnection, and peer key-status reports cannot reset it. This prevents those transitions from causing nonce reuse while the same TX key remains installed.  The nonce format is unchanged, and receivers do not require consecutive counter values, so sharing the counter across peers remains compatible with existing receivers. A pre-existing check still invokes key revocation in the unlikely event that the counter wraps to zero.",
                                "cve_priority": "critical",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98811",
                                "url": "https://ubuntu.com/security/CVE-2026-98811",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net/sched: cls_api: reclaim an empty proto on the error path  Two racing tc filter add requests on the same chain/prio of an unlocked classifier both run change() on the shared proto and both can fail: the winner's tcf_chain_tp_delete_empty() attempt gives up because the loser's handle is still in the idr, and the loser's error path drops only its own reference without a second reclamation attempt. The empty proto stays linked in the chain, holding the chain reference, a block reference and the classifier module reference until the chain or block is torn down.  Reclaim the proto on the error path of any failed request that holds a proto reference. The reclamation is emptiness-gated: tcf_chain_tp_delete_empty() unlinks the proto only when delete_empty() admits it is empty, so a live shared proto is never unlinked. A proto the request created is reclaimed unconditionally - it is the only owner, so marking it for deletion is safe even without a delete_empty callback. Classifiers without one (the check marks the proto unconditionally) are rtnl-serialized, so the raced window this guard closes cannot arise for them.  This is a follow-up to commit d4e359b3608a (\"net/sched: cls_api: fix teardown of an adopted proto on insert-race loss\"), which stopped the loser of the insert race from unlinking the winner's live proto but left the empty-proto residual in place.  Conditions to recreate: - CONFIG_NET_CLS_FLOWER=y; veth pair - tc qdisc add dev veth0 ingress - two concurrent `tc filter add dev veth0 ingress protocol ip pref 1   flower skip_sw ... action drop` (both fail in fl_hw_replace_filter   after publishing their handle in the idr); repeat in a loop - an empty flower tp stays linked after both requests fail; visible   as a bare `filter protocol ip pref 1 flower chain 0` header in   `tc filter show` with no filter entries - CAP_NET_ADMIN (namespace-local via unshare -Urn suffices)",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98812",
                                "url": "https://ubuntu.com/security/CVE-2026-98812",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net/mctp: publish the mctp_dev only after it is initialised  mctp_add_dev() links the new mctp_dev into dev->mctp_ptr before mdev->dev is assigned, so a reader that picks the device up in that window dereferences a net_device pointer that is still NULL:  KASAN: null-ptr-deref in range [0x00000000000000b0-0x00000000000000b7] Call Trace:  <TASK>  ? __pfx_mctp_sendmsg (./include/linux/sockptr.h:49)  ? __pfx_mctp_dst_output (net/mctp/route.c:41)  ? selinux_socket_sendmsg (security/selinux/hooks.c:5278)  ____sys_sendmsg (net/socket.c:775 (discriminator 1) net/socket.c:790  (discriminator 1) net/socket.c:2684 (discriminator 1))  ? __pfx_____sys_sendmsg (net/socket.c:1131)  ? __pfx_copy_msghdr_from_user (net/socket.c:2590)  ? update_cfs_rq_load_avg (kernel/sched/fair.c:5478)  ___sys_sendmsg (net/socket.c:2738)  ? __pfx____sys_sendmsg (net/socket.c:2625)  ? perf_event_task_tick (./include/linux/rcupdate.h:838)  ? sched_tick (kernel/sched/core.c:5818)  ? clockevents_program_event (kernel/time/clockevents.c:372)  ? fdget (./include/linux/rcupdate.h:873 fs/file.c:1100)  __sys_sendmsg (net/socket.c:2770)  ? __pfx___sys_sendmsg (net/socket.c:2751)  do_syscall_64 (arch/x86/entry/syscall_64.c:63)  entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:121)  </TASK>  Fix by publishing only once the object is fully initialised: __mctp_dev_get() runs under rcu_read_lock() only and hands this object to readers as soon as mctp_ptr is assigned, so they must never observe mdev->dev == NULL.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98819",
                                "url": "https://ubuntu.com/security/CVE-2026-98819",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  Bluetooth: btintel: validate DDC record lengths  Parse DDC record lengths in unsigned storage so 0xFF does not wrap. Reject records smaller than the mandatory three-byte header, records exceeding U8_MAX, and records exceeding remaining firmware bytes before issuing Intel_Write_DDC.  This issue was reported by Claude Mythos.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98823",
                                "url": "https://ubuntu.com/security/CVE-2026-98823",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: cfg80211: preserve hidden-group beacon IE ownership  A hidden-group probe-response entry borrows its beacon IEs from the group's beacon entry. cfg80211_update_assoc_bss_entry() can pass such an entry to cfg80211_update_known_bss() when merging scan entries after a channel switch.  Copying the borrowed beacon_ies into the associated entry gives the same allocation two owners. Releasing the group's beacon entry can then leave the associated entry pointing to freed IEs, which are freed again when that entry is released.  Skip beacon IE replacement when the source entry belongs to a hidden group. Preserve probe-response processing, the subsequent metadata updates, and the existing rejection path for conflicting hidden beacon updates.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98936",
                                "url": "https://ubuntu.com/security/CVE-2026-98936",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: ath11k: reset ar->num_stations on hardware start  When (multiple) hw restart occurs, we end up in a situation where we cannot accept new stations / mesh peers. This seems to be the 'num_stations' in 'struct ath11k' that did not get reset properly in this case. In ath11k_mac_op_start(), it was indeed the only accounting var that did not get reset so let's clear it too.  This avoids problems like those:  \t[1248828.088023] WARNING: CPU: 0 PID: 12281 at net/mac80211/util.c:1682 ieee80211_reconfig_stations+0x98/0xc0 \t[1248828.088115] Call trace: \t[1248828.088116]  ieee80211_reconfig_stations+0x98/0xc0 (P) \t[1248828.088119]  ieee80211_reconfig+0x774/0x1438 \t[1248828.088123]  ieee80211_restart_work+0x10c/0x178 \t[1248828.088127]  process_one_work+0x178/0x3c0 \t[1248828.088130]  worker_thread+0x280/0x440 \t[1248828.088133]  kthread+0xe0/0xf8 \t[1248828.088137]  ret_from_fork+0x10/0x20 \t[1248828.088141] ---[ end trace 0000000000000000 ]--- \t[1248836.686604] ath11k_pci 0000:04:00.0: refusing to associate station: too many connected already (128) \t[1248836.686609] ath11k_pci 0000:04:00.0: Failed to add station: xx:xx:xx:xx:xx:xx for VDEV: 1  Tested-on: QCN9074 hw1.0 PCI WLAN.HK.2.9.0.1-01977-QCAHKSWPL_SILICONZ-1",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98831",
                                "url": "https://ubuntu.com/security/CVE-2026-98831",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  of/overlay: don't leak fragment references when changeset init fails  init_overlay_changeset() stores the number of initialized fragments in ovcs->count only on full success. When find_target() or the __symbols__ lookup fails partway through, the target and overlay references taken for the fragments initialized so far are never dropped: free_overlay_changeset() bounds its cleanup loop by ovcs->count, which is still 0.  Store the running count on the error path so free_overlay_changeset() puts whatever was set up. The store is guarded by ovcs->fragments because on the allocation-failure path cnt still holds the counting pass total while there is no fragments array; everywhere else cnt only counts fully-initialized fragments.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98833",
                                "url": "https://ubuntu.com/security/CVE-2026-98833",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  mtd: core: call _get_device() with the master MTD  __get_mtd_device() calls the master's _get_device() callback with mtd, which may be a partition. __put_mtd_device() passes the master.  This breaks gluebi partitions because gluebi_get_device() uses container_of() and therefore requires the master MTD. Pass the master to _get_device(), matching _put_device().",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-89860",
                                "url": "https://ubuntu.com/security/CVE-2026-89860",
                                "cve_description": "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 second INIT_WORK() reinitializes a work item that is already queued, which can corrupt the workqueue list and lead to crashes or a looping worker.  Initialize priv->abort_work once at command submission, next to the existing per-command spin_lock_init(&priv->cmd_lock), and leave only schedule_work() in the abort paths. schedule_work() already does nothing when the work item is still pending, so a repeated abort no longer disturbs an in-flight work item. The command is not returned to the transport until the final kref_put()/release callback runs after abort_work has completed, so the work item is idle before priv is reused and the single submission-time INIT_WORK() is safe.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-09-16 11:16:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-53353",
                                "url": "https://ubuntu.com/security/CVE-2026-53353",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  hsr: Remove WARN_ONCE() in hsr_addr_is_self().  syzbot reported the warning [0] in hsr_addr_is_self(), whose assumption is simply wrong.  hsr->self_node is cleared in hsr_del_self_node(), which is called from hsr_dellink().  Since dev->rtnl_link_ops->dellink() is called before unregister_netdevice_many(), there is a window when user can find the device but without hsr->self_node.  Let's remove WARN_ONCE() in hsr_addr_is_self().  [0]: HSR: No self node WARNING: net/hsr/hsr_framereg.c:39 at hsr_addr_is_self+0x211/0x3f0 net/hsr/hsr_framereg.c:39, CPU#0: syz.4.16848/17220 Modules linked in: CPU: 0 UID: 0 PID: 17220 Comm: syz.4.16848 Tainted: G             L     syzkaller #0 PREEMPT_{RT,(full)} Tainted: [L]=SOFTLOCKUP Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/18/2026 RIP: 0010:hsr_addr_is_self+0x211/0x3f0 net/hsr/hsr_framereg.c:39 Code: 33 2f 41 0f b7 dd 89 ee 09 de 31 ff e8 c8 b4 c6 f6 09 dd 74 54 e8 0f b0 c6 f6 31 ed eb 53 e8 06 b0 c6 f6 48 8d 3d 2f 50 9c 04 <67> 48 0f b9 3a 31 ed eb 42 e8 c1 13 1f 00 89 c5 31 ff 89 c6 e8 96 RSP: 0018:ffffc900041c70e0 EFLAGS: 00010283 RAX: ffffffff8afdc6ca RBX: ffffffff8afdc4e6 RCX: 0000000000080000 RDX: ffffc90010493000 RSI: 0000000000000948 RDI: ffffffff8f9a1700 RBP: 0000000000000001 R08: 0000000000000000 R09: 0000000000000000 R10: ffffc900041c71e8 R11: fffff52000838e3f R12: dffffc0000000000 R13: ffff888041f9e3c0 R14: ffff888086ee3802 R15: 0000000000000000 FS:  00007f6fe985d6c0(0000) GS:ffff888126176000(0000) knlGS:0000000000000000 CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f80bd437dac CR3: 0000000025096000 CR4: 00000000003526f0 DR0: ffffffffffffffff DR1: 00000000000001f8 DR2: 0000000000000002 DR3: ffffffffefffff15 DR6: 00000000ffff0ff0 DR7: 0000000000000400 Call Trace:  <TASK>  check_local_dest net/hsr/hsr_forward.c:592 [inline]  fill_frame_info net/hsr/hsr_forward.c:728 [inline]  hsr_forward_skb+0xa11/0x2a80 net/hsr/hsr_forward.c:739  hsr_dev_xmit+0x253/0x370 net/hsr/hsr_device.c:236  __netdev_start_xmit include/linux/netdevice.h:5368 [inline]  netdev_start_xmit include/linux/netdevice.h:5377 [inline]  xmit_one net/core/dev.c:3888 [inline]  dev_hard_start_xmit+0x2df/0x860 net/core/dev.c:3904  __dev_queue_xmit+0x1428/0x3900 net/core/dev.c:4870  neigh_output include/net/neighbour.h:556 [inline]  ip_finish_output2+0xcec/0x10b0 net/ipv4/ip_output.c:237  ip_send_skb net/ipv4/ip_output.c:1510 [inline]  ip_push_pending_frames+0x8b/0x110 net/ipv4/ip_output.c:1530  raw_sendmsg+0x1547/0x1a50 net/ipv4/raw.c:659  sock_sendmsg_nosec net/socket.c:787 [inline]  __sock_sendmsg net/socket.c:802 [inline]  ____sys_sendmsg+0x7da/0x9c0 net/socket.c:2698  ___sys_sendmsg+0x2a5/0x360 net/socket.c:2752  __sys_sendmsg net/socket.c:2784 [inline]  __do_sys_sendmsg net/socket.c:2789 [inline]  __se_sys_sendmsg net/socket.c:2787 [inline]  __x64_sys_sendmsg+0x1c3/0x2a0 net/socket.c:2787  do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]  do_syscall_64+0x15f/0xf80 arch/x86/entry/syscall_64.c:94  entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f6feb62ce59 Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 e8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f6fe985d028 EFLAGS: 00000246 ORIG_RAX: 000000000000002e RAX: ffffffffffffffda RBX: 00007f6feb8a6090 RCX: 00007f6feb62ce59 RDX: 0000000000000000 RSI: 0000200000000000 RDI: 0000000000000004 RBP: 00007f6feb6c2d6f R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007f6feb8a6128 R14: 00007f6feb8a6090 R15: 00007ffcf01cc488  </TASK>",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-07-01 14:16:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98836",
                                "url": "https://ubuntu.com/security/CVE-2026-98836",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ALSA: line6: reject oversized playback packets  Each playback URB is handed a slice of out.buffer that is exactly LINE6_ISO_PACKETS * max_packet_size_out bytes, sized from the OUT endpoint, but the number of bytes written into that slice is never compared against it.  submit_audio_out_urb() takes the frame count from prev_fsize, which audio_in_callback() derived from the *IN* endpoint's received packet length, and rescales it with the playback frame size; when prev_fsize is still zero it synthesizes a length from the sample rate instead.  On a device declaring a large IN wMaxPacketSize and a small OUT wMaxPacketSize, the resulting memcpy(), or the memset() when the playback stream is idle, runs past its slice and, as the reproducer below shows, beyond the allocation.  usb_submit_urb() is not a backstop.  max_packet_size_out comes from usb_maxpacket(), which returns only the low 11 bits of wMaxPacketSize, while USB core validates a high-speed isochronous length against that base scaled by usb_endpoint_maxp_mult().  A length of up to three times the allocated slice is therefore accepted, and even a rejected URB is only rejected after the write.  Reject a packet that does not fit the slice the driver allocated for it. Clamping it instead would silently shorten the capture-derived rate feedback and desynchronize the two streams.    BUG: KASAN: slab-out-of-bounds in submit_audio_out_urb (sound/usb/line6/playback.c:229)   Write of size 1024 at addr ffff888100bbd400 by task kworker/1:2/5002   Workqueue: events line6_startup_work   Call Trace:    __asan_memcpy (mm/kasan/shadow.c:106)    submit_audio_out_urb (sound/usb/line6/playback.c:229)    line6_submit_audio_out_all_urbs (sound/usb/line6/playback.c:291)    line6_stream_start (sound/usb/line6/pcm.c:194)    line6_pcm_acquire (sound/usb/line6/pcm.c:337)    line6_startup_work (sound/usb/line6/driver.c:728)    process_one_work (kernel/workqueue.c:3396)    worker_thread (kernel/workqueue.c:3479 kernel/workqueue.c:3560)    kthread (kernel/kthread.c:436)    ret_from_fork (arch/x86/kernel/process.c:158)    ret_from_fork_asm (arch/x86/entry/entry_64.S:245)    The buggy address belongs to the object at ffff888100bbd400    which belongs to the cache kmalloc-256 of size 256   The buggy address is located 0 bytes inside of    allocated 256-byte region [ffff888100bbd400, ffff888100bbd500)",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98838",
                                "url": "https://ubuntu.com/security/CVE-2026-98838",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  vt: skip screen update for DEC alignment test on backgroup consoles  [BUG] Recently, we encountered a KASAN warning as follows:  BUG: KASAN: slab-out-of-bounds in fb_pad_aligned_buffer+0x11f/0x140 Read of size 1 at addr ff1100015fd9f6a4 by task tty_fbcon_oob/1239 CPU: 7 UID: 0 PID: 1239 Comm: tty_fbcon_oob Not tainted 7.3.0-rc1 #100 PREEMPT(full) Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.17.0-4.fc41 04/01/2014 Call Trace:  <TASK>  ...  kasan_report+0xf0/0x120  fb_pad_aligned_buffer+0x11f/0x140  ccw_putcs+0x86c/0xa80  fbcon_putcs+0x338/0x410  do_update_region+0x21d/0x450  do_con_write+0x1e0e/0x4880  con_write+0x13/0x80  n_tty_write+0x374/0x1010  file_tty_write.isra.0+0x404/0x7a0  ...  reproduce: 1) open /dev/tty0, set a KDFONTOP ioctl with op.op = KD_FONT_OP_SET, op.width = 8 and op.height = 16 (visible VC1) 2) open /dev/tty1, set a KDFONTOP ioctl with op.op = KD_FONT_OP_SET, op.width = 28 and op.height = 24 (invisible VC2) 3) echo 3 > /sys/devices/virtual/graphics/fbcon/rotate_all 4) write EShash8(esc hash8) to tty1  [CAUSE] All VCs render to the framebuffer. setfont only modifies the target VC's font without resizing the framebuffer backing buffer (par->rotated.buf); the buffer is only resized for the visible VC (fbcon_do_set_font -> ... -> vc_do_resize -> update_screen). This relies on the con_should_update() check performed before every update_region().  However, the ESC # 8 path (do_con_trol -> do_update_region) omits the con_should_update() check. After changing the font size of an invisible VC, do_update_region() fills using the new font size against a buffer that was never resized, causing an out-of-bounds access.  [FIX] Only push the update when the console is visible and not blanked, add the con_should_update() check in the do_con_trol() like every other call site of do_update_region() (update_region(), invert_screen(), ...).",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98568",
                                "url": "https://ubuntu.com/security/CVE-2026-98568",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  vxlan: use one headroom snapshot for neighbour replies  vxlan_na_create() samples LL_RESERVED_SPACE() to size the reply skb and then samples it again to reserve headroom. A concurrent vxlan_changelink() can update needed_headroom between the two reads, creating a TOCTOU race. The second value can exceed the allocation and make the Ethernet header write out of bounds.  The race is reproducible on the unpatched kernel. It occurred when vxlan_na_create() generated a neighbour reply while vxlan_changelink() changed the link headroom. KASAN caught a four-byte write two bytes beyond a 704-byte skbuff_small_head allocation.  Snapshot the headroom once and use that value for both allocation and reservation.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2024-49901",
                                "url": "https://ubuntu.com/security/CVE-2024-49901",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  drm/msm/adreno: Assign msm_gpu->pdev earlier to avoid nullptrs  There are some cases, such as the one uncovered by Commit 46d4efcccc68 (\"drm/msm/a6xx: Avoid a nullptr dereference when speedbin setting fails\") where  msm_gpu_cleanup() : platform_set_drvdata(gpu->pdev, NULL);  is called on gpu->pdev == NULL, as the GPU device has not been fully initialized yet.  Turns out that there's more than just the aforementioned path that causes this to happen (e.g. the case when there's speedbin data in the catalog, but opp-supported-hw is missing in DT).  Assigning msm_gpu->pdev earlier seems like the least painful solution to this, therefore do so.  Patchwork: https://patchwork.freedesktop.org/patch/602742/",
                                "cve_priority": "low",
                                "cve_public_date": "2024-10-21 18:15:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98846",
                                "url": "https://ubuntu.com/security/CVE-2026-98846",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  sctp: check RCV_SHUTDOWN after the sendmsg connect wait  sctp_wait_for_connect() drops the socket lock while it sleeps. An out-of-the-blue ABORT can then be processed from the socket backlog and unlink the association. If a concurrent shutdown(fd, SHUT_RD) sets RCV_SHUTDOWN, the waiter breaks with err == 0 before checking asoc->base.dead. Its final sctp_association_put() can then free the association, leaving sctp_sendmsg_to_asoc() to continue with a dangling pointer.  Check RCV_SHUTDOWN along with the wait error in sctp_sendmsg_to_asoc() before using the association again. The check only accesses the socket, so it needs no additional association reference. Return the existing -ESRCH so that sctp_sendmsg() skips freeing a new association that may already have been destroyed.  Keep sctp_wait_for_connect() unchanged to preserve its behavior for the connect() caller.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98847",
                                "url": "https://ubuntu.com/security/CVE-2026-98847",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  rtc: spear: initialize IRQ state before requesting alarm IRQ  devm_request_irq() enables the interrupt before it returns, so the handler may run while probe is still initializing the device. Initialize the MMIO address and spinlock before requesting the alarm IRQ.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98850",
                                "url": "https://ubuntu.com/security/CVE-2026-98850",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net/packet: prevent TX_RING byte count overflow  tpacket_snd() drains every SEND_REQUEST frame in a TX ring and adds each valid packet length to the signed int len_sum. Userspace can recycle completed frames concurrently, so a single blocking send call is not bounded by the ring size.  After enough successful transmissions len_sum wraps into the negative range. In particular, 65536 65535-byte frames followed by a 65007-byte frame produce 0xfffffdef, or -EIOCBQUEUED. sock_sendmsg_nosec() treats that as an impossible return and triggers a BUG. On systems configured to panic on oops, a CAP_NET_RAW holder can panic the host kernel.  Stop before the next frame would make the byte count exceed INT_MAX. The positive short count leaves that frame pending for a later send call.  A two-thread TPACKET_V2 reproducer triggered the BUG on an arm64 build of Linux 7.3-rc4. With this change, the same reproducer returned the expected positive short count without an oops.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98851",
                                "url": "https://ubuntu.com/security/CVE-2026-98851",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  netfilter: nft_flow_offload: drop flowtable reference on init error path  nft_flow_offload_init() bumps the flowtable use count with nft_use_inc() before calling nf_ct_netns_get().  When the latter fails, the error is returned as-is and the reference is leaked.  The upper layers do not balance it either: nf_tables_newexpr() clears expr->ops when the expression init callback fails, so the nft_expr_more() iteration in nft_rule_expr_deactivate() and nf_tables_rule_destroy() stops right before the failed expression and its ->destroy callback, which would drop the reference, never runs.  Each failed rule addition therefore leaks one flowtable reference and the flowtable can no longer be removed: NFT_MSG_DELFLOWTABLE keeps reporting -EBUSY even though no rule references it.  Save the nf_ct_netns_get() return value and undo the nft_use_inc() when it fails, restoring the inc/dec pairing within nft_flow_offload_init() itself.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98854",
                                "url": "https://ubuntu.com/security/CVE-2026-98854",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  of/overlay: only treat a positive changeset id as registered  of_overlay_fdt_apply() stores the idr_alloc() return value in ovcs->id before checking it. On failure the stored id is negative, free_overlay_changeset()'s \"if (ovcs->id)\" check passes, idr_remove() is called with a negative id and list_del() runs on ovcs->ovcs_list, which is not initialized until after the id allocation. An allocation failure at that point dereferences NULL.  Make free_overlay_changeset() treat only a strict-positive id as registered. The rest of the function already copes with a partially-initialized ovcs, so the error path stays a plain goto err_free_ovcs.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98855",
                                "url": "https://ubuntu.com/security/CVE-2026-98855",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  of/overlay: put property on deadprops only after changeset add succeeds  add_changeset_property() links a new property of a not-yet-live target node into the node's deadprops list before handing it to of_changeset_add_property(). If that fails, the error path frees the property but leaves the freed pointer linked in deadprops, and of_node_release() frees it a second time when the aborted overlay's node is released.  Record the changeset entry first and link the property into deadprops only on success. of_changeset_add_property() never looks at the node's property lists, so the order of the two steps is otherwise immaterial, and the error path frees a property that nothing references.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98862",
                                "url": "https://ubuntu.com/security/CVE-2026-98862",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  audit: fix exe mark UAF in kill_rules()  kill_rules() removes mixed AUDIT_DIR and AUDIT_EXE rules when an audit tree is pruned. It drops entry->rule.exe before removing the rule from the RCU-visible filter lists.  After a rule has been installed with AUDIT_ADD_RULE, which requires CAP_AUDIT_CONTROL, removing the watched directory can race with another task that is still evaluating the rule. In that case, fsnotify can free the executable mark before the reader reaches audit_mark_compare(), causing a use-after-free.  KASAN reports:      BUG: KASAN: slab-use-after-free in audit_mark_compare+0x8d/0xa0  Unlink the published rules from the RCU-visible lists and retain them on tree->rules for cleanup. If any rule has an executable mark, wait for a single RCU grace period before removing the marks and scheduling the entries for freeing. Otherwise, call_rcu() already provides the required deferred freeing without a synchronous wait.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98450",
                                "url": "https://ubuntu.com/security/CVE-2026-98450",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  smb: client: close completed creates on compound wait errors  compound_send_recv() waits for responses in order. If a later wait is interrupted, or if a later MID fails during response synchronization, an earlier CREATE may already have opened a remote handle. The earlier mid is then released without invoking handle_cancelled_mid(), leaving the remote handle open because no FID was copied to the caller.  Mark completed earlier mids as cancelled when a compound wait or MID synchronization aborts. Keep their response buffers attached while the MIDs are synchronized, and transfer them only after synchronization of the processed responses, so the release path can inspect successful CREATE responses and queue SMB2_close() after a later failure. Account for a remote open only after the close work is allocated and before it is queued, since the caller has not yet updated num_remote_opens. Mark the create+close compound used by smb2_unlink() so it is not closed again. Non-CREATE responses and compounds that already include a close keep their existing behavior.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:16:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98502",
                                "url": "https://ubuntu.com/security/CVE-2026-98502",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  HID: alps: unregister DualPoint Stick input device on remove  alps_input_configured() allocates a second input device (\"DualPoint Stick\") with input_allocate_device() and registers it, but the alps_driver struct has no .remove handler and input2 is not tracked in hdev->inputs.  The default remove path (hid_hw_stop -> hidinput_disconnect) only iterates hdev->inputs, so input2 is never unregistered and leaks on every device removal.  Add a .remove handler that stops the device first (preventing URB callbacks from touching input2 during teardown) and then unregisters input2.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98456",
                                "url": "https://ubuntu.com/security/CVE-2026-98456",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  Bluetooth: mgmt: fix race in read_unconf_index_list()  read_unconf_index_list() counts unconfigured controllers before allocating its response, then checks the device flags again while filling it.  hci_dev_list_lock stabilizes list membership, but it does not serialize the per-device flags. During asynchronous controller setup, the worker can set HCI_UNCONFIGURED and clear HCI_SETUP between the two passes. A controller omitted from the allocation count can then become eligible for the fill pass, causing an out-of-bounds write to rp->index[].  Allocate space for every device on hci_dev_list. Since list membership cannot change while hci_dev_list_lock is held, the response remains large enough regardless of flag transitions. The reported count and response length still include only eligible unconfigured controllers.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-18 16:16:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98451",
                                "url": "https://ubuntu.com/security/CVE-2026-98451",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  smb: client: use finish_no_open() for non-regular inodes  An O_CREAT open can find an existing symlink or another non-regular inode. cifs_atomic_open() calls finish_open() on it and attaches a cifsFileInfo. Symlink inodes have no CIFS release operation, so the dentry reference held by cifsFileInfo is leaked. FMODE_OPENED also prevents the VFS from following the symlink.  Track whether cifs_do_create() returned an open server handle. For non-regular inodes, close the handle if present, remove the pending open, and call finish_no_open() so the VFS can continue the lookup. Do not set FMODE_CREATED unless a regular file was opened. For O_NOFOLLOW with __O_REGULAR, return -ELOOP before the VFS's -EFTYPE check.  Defer closing a legacy POSIX handle on a non-regular inode until after inode lookup. This avoids closing it again if lookup fails.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-18 16:16:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98484",
                                "url": "https://ubuntu.com/security/CVE-2026-98484",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  netfilter: nf_tables: skip expired catchall elements on insert and delete  nft_setelem_catchall_insert() looks up duplicates with nft_set_elem_active() only, while nft_set_catchall_lookup() and the dump path additionally skip expired elements.  Once a catchall element with a timeout expires, this predicate drift makes it invisible to userspace dumps, yet it still blocks re-insertion: with NLM_F_EXCL the request fails with -EEXIST, and without it the request reports success but silently inserts nothing. The stale entry only goes away when the (user-tunable) gc interval elapses, so the catchall rule may silently stop matching for an arbitrarily long time after its first expiration.  The delete path shows the same drift: nft_setelem_catchall_deactivate() picks the first active-next entry in the catchall list, so with an expired entry still pending GC it retires the stale entry instead of the fresh one, and it deactivates an element that userspace no longer sees instead of failing with -ENOENT.  Align both walks with the lookup and dump predicates: only an element that is active and not expired counts as a duplicate or delete candidate, using the per-netns timestamp taken at transaction start, in line with the set backend .insert/.deactivate and catchall GC sync paths.",
                                "cve_priority": "negligible",
                                "cve_public_date": "2026-10-18 16:16:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98486",
                                "url": "https://ubuntu.com/security/CVE-2026-98486",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net: ena: fix MMIO read buffer leak on probe failure  ena_device_init() initializes the MMIO read mechanism with ena_com_mmio_reg_read_request_init(), which allocates a coherent DMA buffer for MMIO read responses.  The normal removal path releases this buffer through ena_com_mmio_reg_read_request_destroy(). However, if ena_probe() fails after ena_device_init() succeeds, the error path destroys the admin resources and eventually frees ena_dev without destroying the MMIO read request, leaving the coherent DMA buffer allocated.  Call ena_com_mmio_reg_read_request_destroy() in the probe error path before releasing the remaining device resources.  This issue was found by manual code inspection.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:16:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98493",
                                "url": "https://ubuntu.com/security/CVE-2026-98493",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net: ipconfig: bound DHCP option construction  ic_dhcp_init_options() appends the hostname (option 12), vendor-class (option 60) and client-ID (option 61) options into the fixed 312-byte bootp_pkt.exten[] buffer.  Only the client-ID branch checked the remaining space; the hostname and vendor-class writes were unbounded.  A 64-byte hostname together with the maximum 252-byte dhcpclass= identifier needs 18 + (2 + 64) + (2 + 252) = 338 of the 312 available bytes even before the terminating END marker, so the vendor-class memcpy runs past the end of exten[].  With CONFIG_FORTIFY_SOURCE this is reported as a field-spanning write and, when the kernel is booted with panic_on_warn=1, aborts boot with a panic.  Route the optional options through a common helper that makes sure the option, its 2-byte header and the END marker all fit and drops an option that would not.  Configurations with short options keep sending exactly the same bytes as before.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98454",
                                "url": "https://ubuntu.com/security/CVE-2026-98454",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  smb: client: fix create context out-of-bounds reads  smb2_parse_contexts() validates the complete create-context area but does not limit each record to its Next field before dispatching it.  A malformed chain can therefore expose bytes beyond the current context to a handler.  The QFid handler also used a full response-structure cast although it only reads DiskFileId.  The SMB2/SMB3 lease parsers made the same layout assumption: they read LeaseState and LeaseFlags at canonical offsets rather than at DataOffset.  A valid non-canonical DataOffset could therefore yield unrelated in-bounds data, while a short DataLength was still accepted.  Limit each context to its Next value, reject offsets before the context header, and reject malformed chains.  Bound the name range by the current context and do not dispatch a known handler when DataLength is zero.  Read the QFid DiskFileId only when the context data covers that field.  Parse the lease context from DataOffset and require DataLength to match the v1 or v2 lease_context size used by ksmbd.  A size mismatch skips lease parsing without failing the open.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-18 16:16:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98490",
                                "url": "https://ubuntu.com/security/CVE-2026-98490",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net: openvswitch: conntrack: fix helper UAF due to extensions realloc  While calling the helpers, a raw pointer to the extensions area is wired into expectations list:    -> nf_ct_helper()    -> helper->help()     -> nf_ct_expect_related_report()      -> nf_ct_expect_insert()       -> hlist_add_head_rcu(&exp->lnode, &master_help->expectations)  In case the connection is not confirmed yet, more extensions can be added afterwards with *_ext_add() calls reallocating the extension space and leaving the now invalid pointer in the expectations list that is later accessed while removing the expectation.  Make sure that helpers are called at the end after all the other extensions are already added.  Note that the helper rejection now leaves the mark and labels set, but that's not different from how the NAT was handled before or how the mark and the labels were handled on confirmation failure.  And there are no atomicity guarantees provided by the API anyway.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-18 16:16:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98507",
                                "url": "https://ubuntu.com/security/CVE-2026-98507",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  mm/rmap: fix missing barrier between anon_vma init and vma->anon_vma publish  On arm64 server, we find that a task trying to grab the anon_vma lock triggers hungtask.  INFO: task main:2354726 blocked for more than 120 seconds.       Tainted: G            E     5.10.0-0021.aarch64 #1 \"echo 0 > /proc/sys/kernel/hung_task_timeout_secs\" disables this message. task:main            state:D stack:    0 pid:2354726 ppid:2350673 flags:0x00000a01 Call trace:  __switch_to+0x7c/0xbc  __schedule+0x3b4/0x8a0  schedule+0x50/0xe0  rwsem_down_write_slowpath+0x3cc/0x6cc  down_write+0x60/0x260  __anon_vma_prepare+0x6c/0x210  do_anonymous_page+0x258/0x660  handle_pte_fault+0x188/0x214  __handle_mm_fault+0x1b0/0x380  handle_mm_fault+0xf4/0x284  do_page_fault+0x19c/0x494  do_translation_fault+0xcc/0xf8  do_mem_abort+0x48/0xac  el0_da+0x44/0x80  el0_sync_handler+0x88/0xb4  el0_sync+0x160/0x180  After analyzing the vmcore, we found the anon_vma->root->rwsem.count is -1.  There is another anon_vma whose anon_vma->root->rwsem.count is 1, the anon_vma->root->rwsem.owner shows the lock is held, but the stack of the task shows the task doesn't hold the anon_vma lock.  After adding more debugging info, we found __anon_vma_prepare() reuses anon_vma and triggers the UAF of anon_vma->root due to missing memory barrier, leading to locking and unlocking two different anon_vma->root, thus leading to an anon_vma will never be unlocked, and another anon_vma couldn't be locked anymore.  This race requires two adjacent VMAs that are not merged but are anon_vma-compatible (e.g., they differ in VMA_ACCESS_FLAGS that can be changed by mprotect()).  Two threads fault on each VMA concurrently, both calling __anon_vma_prepare() with only mmap_lock held for reading.      THREAD A                             THREAD B __anon_vma_prepare                __anon_vma_prepare  find_mergeable_anon_vma() -> NULL  anon_vma = anon_vma_alloc();    anon_vma->root = anon_vma;  // the two stores may be reordered  vma->anon_vma = anon_vma;                                    // finds A's anon_vma                                    anon_vma = find_mergeable_anon_vma(vma);                                    anon_vma_lock_write(anon_vma);                                      // may still see the old root                                      down_write(&anon_vma->root->rwsem);                                    anon_vma_unlock_write(anon_vma);                                      // see the new root, never unlock old                                      up_write(&anon_vma->root->rwsem);  thread A triggers page fault and calls __anon_vma_prepare() to prepare anon_vma for the faulting vma.  __anon_vma_prepare() allocates and initializes a new anon_vma, and then publishes it to the vma with a plain store.  anon_vma_prepare() only requires the mmap_lock to be held for reading, so two threads can fault on adjacent VMAs at the same time. While thread A publishes a new anon_vma, thread B could find the anon_vma via find_mergeable_anon_vma() and then locks anon_vma->root->rwsem.  The store to anon_vma->root in anon_vma_alloc() and the store to vma->anon_vma can be reordered.  The anon_vma_lock_write() and spin_lock() only provide acquire semantics, which do not prevent prior stores from being reordered after them.  The release semantics of the corresponding spin_unlock() and anon_vma_unlock_write() come too late, the store to vma->anon_vma is already published before they take effect.  As a result, thread B can observe the following order:      vma->anon_vma = anon_vma;     anon_vma->root = anon_vma;  The anon_vma slab is SLAB_TYPESAFE_BY_RCU, so a newly allocated anon_vma may reuse memory from a previously freed one.  The constructor (anon_vma_ctor) does not reset anon_vma->root, and __put_anon_vma() doesn't clear it either, so the old root value persists until anon_vma_alloc() overwrites it.  If that store isn't v ---truncated---",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98519",
                                "url": "https://ubuntu.com/security/CVE-2026-98519",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  drm/amdgpu: Fix runtime PM leak in amdgpu_debugfs_test_ib_show()  amdgpu_debugfs_test_ib_show() resumes the device with pm_runtime_get_sync() before taking the reset domain semaphore with down_write_killable().  If the write lock acquisition is interrupted, the function returns without calling pm_runtime_put_autosuspend(), leaking the runtime PM reference acquired for the device and keeping the GPU awake.  Drop the runtime PM reference on the interrupted down_write_killable() error path before returning.  (cherry picked from commit ec30a576c2d4c0364549e6c04218f50704ef56c8)",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98549",
                                "url": "https://ubuntu.com/security/CVE-2026-98549",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  tcp: prevent collapsing skbs across boundary in rtx queue  tcp_write_collapse_fence() sets TCP_SKB_CB(skb)->eor = 1 on tcp_write_queue_tail(sk) to prevent skbs queued after a switch to device encryption from being collapsed into earlier skbs.  The fence is a no-op if all earlier data has already been transmitted when the switch happens: sk->sk_write_queue is empty. The not yet acknowledged earlier skbs wait in sk->tcp_rtx_queue with eor 0.  On a subsequent retransmit or SACK shift, tcp_retrans_try_collapse() or tcp_shift_skb_data() can then merge an skb queued after the switch into one queued before it.  Both users of the fence are affected:  - psp: devices only encrypt skbs with skb->decrypted set. The merged skb   keeps decrypted = 0 from the earlier skb, so merged data sent after   psp_sock_assoc_set_tx() is retransmitted in cleartext.  - tls device offload: the merged skb straddles the start marker set in   tls_set_device_offload(). The software fallback (fill_sg_in() returns   -EINVAL) and the mlx5, nfp and funeth drivers cannot handle such an   skb and drop it. Every retransmit rebuilds the same skb, so the   connection stalls.  Fix this in two places, for defense in depth:  1. Fall back to tcp_rtx_queue_tail(sk) in tcp_write_collapse_fence()    when tcp_write_queue_tail(sk) is NULL.  2. Check !skb_cmp_decrypted(to, from) in tcp_skb_can_collapse(), as    tcp_skb_can_collapse_rx() does on receive. skb_shift(), which both    collapse paths call, already has a DEBUG_NET_WARN_ON_ONCE() for this    condition.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98544",
                                "url": "https://ubuntu.com/security/CVE-2026-98544",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  bna: prevent IOC timer rearm during teardown  bna: prevent IOC timer rearm during teardown  bnad_pci_remove() and the probe disable_ioceth path call timer_delete_sync() for ioc_timer, sem_timer and hb_timer, but not for iocpf_timer.  bnad_iocpf_timeout() then takes bnad->bna_lock after free_netdev() has freed the struct bnad.  Deleting iocpf_timer last does not fix this.  sem_timer and iocpf_timer rearm each other: bnad_iocpf_sem_timeout() can arm iocpf_timer, and bnad_iocpf_timeout() arms sem_timer from bfa_ioc_hw_sem_get() when the semaphore is busy. timer_delete_sync() only waits out its own callback. bnad_ioceth_disable() can time out and leave that callback live.  Shut all four IOC timers down with timer_shutdown_sync() on both paths, so a later mod_timer() is ignored.  This issue was identified during our ongoing static-analysis research while reviewing kernel code.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98172",
                                "url": "https://ubuntu.com/security/CVE-2026-98172",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  smb: client: fix smbd_connection leak on cifs_get_tcp_session() error  When an RDMA connection is successfully established via smbd_get_connection() but cifs_get_tcp_session() later fails (e.g. kthread_create() returns an error), the error path frees tcp_ses without first destroying the smbd_connection.  Fix this by calling smbd_destroy() in the out_err cleanup path before kfree(tcp_ses).  smbd_destroy() safely handles the case where smbd_conn is NULL, so it can be called unconditionally.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-06 09:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98192",
                                "url": "https://ubuntu.com/security/CVE-2026-98192",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: wcn36xx: Fix potential use-after-free in TX ack timer teardown  wcn36xx_dxe_deinit() tears down the TX ack timer with timer_delete(), which only dequeues the timer and does not wait for a callback that is already executing; the preceding free_irq() calls synchronize the interrupt handlers only. The callback, wcn36xx_dxe_tx_timer(), can therefore be running past the teardown and use the wcn freed along with the ieee80211_hw in wcn36xx_remove(): it takes wcn->dxe_lock, reads wcn->tx_ack_skb and passes wcn->hw to ieee80211_tx_status_irqsafe().  Fix this by using timer_shutdown_sync(), which waits for a running callback and also prevents the timer from being rearmed again. The timer is set up again by wcn36xx_dxe_init() on the next start, so the start/stop cycle is unaffected.  This issue was found by an in-house static analysis tool.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-06 09:18:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98198",
                                "url": "https://ubuntu.com/security/CVE-2026-98198",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  hwmon: (pwm-fan) Stop RPM timer before freeing tach data  sample_timer() rearms the RPM timer and accesses the devm-managed ctx->tachs and ctx->pulses_per_revolution arrays. The cleanup action which stops the timer is registered before those arrays are allocated.  Since devres releases entries in reverse order, driver detach can free the arrays before pwm_fan_cleanup() shuts down the timer. A timer expiry in that window accesses the freed tach data.  With a KASAN kernel, a test-only kprobe delayed entry to pwm_fan_cleanup() while normal sysfs unbind ran. Each of three runs reported three four-byte reads and two four-byte writes in sample_timer() after its backing devm allocations had been freed. The helper did not invoke the timer callback, cleanup actions or free functions.  With the fix, three matching unbind runs completed without KASAN, BUG, WARNING, Oops or panic. Instrumentation confirmed that timer retirement completed before the first timer backing allocation was released.  Split timer retirement from the power cleanup and register its devres action after the timer backing data and IRQ actions are installed. This preserves the early power rollback action while ensuring the timer is retired before its backing data is released. Use timer_shutdown_sync() because the callback can rearm itself.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-06 09:18:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98409",
                                "url": "https://ubuntu.com/security/CVE-2026-98409",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  watchdog: rtd119x: Avoid division by zero  clk_get_rate() could return 0.  Avoid a division by zero panic.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-14 14:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98245",
                                "url": "https://ubuntu.com/security/CVE-2026-98245",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  btrfs: take commit root semaphore when iterating in mark_block_group_to_copy()  mark_block_group_to_copy() iterates over the commit root with skip_locking=true. A concurrent transaction commit can swap and free the commit root during iteration, causing use-after-free when accessing extent buffers.  Fix it by using path->need_commit_sem to protect the commit root search.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-06 09:18:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98264",
                                "url": "https://ubuntu.com/security/CVE-2026-98264",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ALSA: virtio: reset device before deleting virtqueues  virtsnd_remove() and virtsnd_freeze() delete the virtqueues before resetting the device. del_vqs() frees the vring backing, but does not provide a generic device quiesce operation. In particular, modern virtio-pci keeps enabled queues active until the device is reset.  Reset the device before deleting the virtqueues so it can no longer access the vring memory when that memory is released. This also covers probe failures after DRIVER_OK, which unwind through virtsnd_remove().",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-06 09:18:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-97558",
                                "url": "https://ubuntu.com/security/CVE-2026-97558",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  smb: client: fix cifsFileInfo reference leak in deferred close  When cifs_close() defers a close, it hands the cifsFileInfo reference of the closing struct file to the queued work. Each execution of smb2_deferred_work_close() drops one such reference.  deferred_close_scheduled can be false while the work is pending: the workqueue clears PENDING when the callback starts to run, before the callback clears the flag under deferred_lock. A close in that interval requeues the running work, and the callback then clears the flag, leaving the requeued work pending with the flag down. A later cifs_open() can reuse the handle and its cifs_close() reaches the same branch: queue_delayed_work() fails because the work is still pending, but cifs_close() returns without dropping the closing file's reference. The cifsFileInfo count stays pinned and its tlink, dentry and server handle are leaked.  Check the return value and hand off the reference only when work was actually queued. Otherwise, use the shared _cifsFileInfo_put(), like the mod_delayed_work() branch above: the pending execution already owns its reference.  This issue was found by an in-house static analysis tool.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-09-25 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-97616",
                                "url": "https://ubuntu.com/security/CVE-2026-97616",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net/sched: act_api: release all action references on NEWACTION failure  When a batched RTM_NEWACTION request replaces an existing action, tcf_idr_check_alloc() takes a temporary reference on it. If a later action fails to initialize, tcf_action_destroy() uses strict release semantics to clean up the actions initialized so far. For an action bound to a filter, the strict check returns -EPERM without dropping the temporary reference.  This error also makes tcf_action_destroy() return before releasing subsequent entries. Any new action initialized between the bound action and the failing entry is leaked together with its reserved IDR slot, preventing reuse of its index.  Use tcf_idr_release() to drop each reference held by the batch without rejecting bound actions. This allows cleanup to continue through all initialized entries and preserves the module reference release when an action is destroyed. Explicit action deletion and flushing retain their separate bind-count checks.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-09-25 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-97939",
                                "url": "https://ubuntu.com/security/CVE-2026-97939",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ipmr: account multicast table and route memory  A netadmin in a user+net namespace can create many IPv4 and IPv6 multicast routing tables with MRT_TABLE and MRT6_TABLE. Each unseen id allocates an mr_table via the shared mr_table_alloc(), links it into the per-net list, and leaves it until netns teardown. Those objects were not charged to memcg, so the host unreclaimable slab grows with the table count.  Account mr_table allocations with GFP_KERNEL_ACCOUNT and mark the IPv4/IPv6 MFC caches SLAB_ACCOUNT. This matches the established handling of IP addresses, routes and alternate interface names.  Unresolved MFC entries are still allocated from softIRQ with GFP_ATOMIC and are not charged. They expire after 10 seconds and are bounded by the socket receive queue; see commit 0079ad8e8dc3 (\"ipmr: remove hard code cache_resolve_queue_len limit\").",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-09-25 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-89837",
                                "url": "https://ubuntu.com/security/CVE-2026-89837",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  f2fs: fix dentry folio leak in find_in_level  find_in_level() gets a dentry folio with f2fs_find_data_folio() before calling find_in_block().  If find_in_block() returns an error, the function stores the error in res_folio and breaks out of the loop without dropping the dentry folio.  This leaks the folio reference on the find_in_block() error path.  Drop the dentry folio before returning the error to the caller.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-09-16 11:16:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-89838",
                                "url": "https://ubuntu.com/security/CVE-2026-89838",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  f2fs: limit recovery filename logging to stored length  F2FS stores recovery filenames as a length plus a fixed-size i_name buffer.  The buffer is not NUL-terminated, but recover_inode() and recover_dentry() print it with %s.  For a 255-byte filename, recovery logging can read past i_name into the following raw inode fields.  Print the name with a precision bounded by i_namelen and F2FS_NAME_LEN.",
                                "cve_priority": "negligible",
                                "cve_public_date": "2026-09-16 11:16:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-97530",
                                "url": "https://ubuntu.com/security/CVE-2026-97530",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  scsi: qla2xxx: Fix soft lockup polling continuation IOCB signature  qla27xx_copy_multiple_pkt() and qla27xx_copy_fpin_pkt() poll rsp_q->ring_ptr->signature for RESPONSE_PROCESSED (0xDEADDEAD) to decide whether the next continuation IOCB has arrived, spinning on cpu_relax() without advancing the ring or decrementing the entry count while it has not. response_t::signature lives at byte offset 60, but a continuation IOCB (sts_cont_entry_t / struct sts_cont_entry_ext) carries raw FC frame payload at that offset (data[56..59]). A received frame whose payload bytes happen to equal 0xDEADDEAD is therefore misread as \"not yet arrived\", and the loop spins forever in interrupt/DPC context, causing a CPU soft lockup.  The poll is also unnecessary: callers of qla27xx_copy_multiple_pkt() (PT_LS4_UNSOL and the NVMe purls path) already gate on qla_chk_cont_iocb_avail(), which guarantees all entry_count IOCBs are present before copying begins. The sibling helper __qla_copy_purex_to_buffer() already drops the signature poll and relies on the entry_type == STATUS_CONT_TYPE guard instead.  Remove the signature busy-wait from both helpers, keeping the entry_type guard, and gate the FPIN path with qla_chk_cont_iocb_avail() so it defers and re-processes on the next interrupt once all continuation IOCBs have arrived, mirroring the ELS_AUTH_ELS and PT_LS4_UNSOL arms. With this the signature field is never read on a continuation IOCB, eliminating the payload-aliasing lockup.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-09-25 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98386",
                                "url": "https://ubuntu.com/security/CVE-2026-98386",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  scsi: qla2xxx: Use memset_io() to clear QLAFX00 request ring slot  For QLAFX00 the request ring is ioremapped device I/O memory (ha->iobase + req_que_off), not DMA-coherent RAM, which is why the rest of the FX00 path accesses it through memcpy_toio() and the wrt_reg_* helpers. __qla2x00_alloc_iocbs() however zeroed the producer slot with a plain memset(). On architectures such as ARM64 a regular memset() may emit unaligned or block-zeroing instructions (e.g. DC ZVA) that are invalid on Device memory, leading to a synchronous external abort.  Use memset_io() to clear the slot for QLAFX00, matching the I/O accessors used elsewhere on this ring. Other adapters keep the plain memset() on their DMA-coherent rings. The zero-fill is retained for FX00 because its IOCB builders (e.g. qlafx00_fxdisc_iocb()) copy only part of the entry and rely on the unused tail being pre-zeroed.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-14 14:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-89848",
                                "url": "https://ubuntu.com/security/CVE-2026-89848",
                                "cve_description": "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_work, and qla_do_work() -> qla24xx_process_response_queue() dereferences the now-freed rsp->req (LOGINOUT/CT/ELS entries and the status path), a use-after-free.  The cancel_work_sync() added for the qpair teardown lives in the response free path, which runs after the request queue is already freed, so it does not protect rsp->req.  Release the response-queue interrupt and flush qpair->q_work before deleting the request queue, so no late completion can reach the freed request queue. Clearing have_irq makes the subsequent qla25xx_free_rsp_que() skip its free_irq(), and the firmware queue-delete order (request then response) is preserved; the request-delete mailbox completes on the default vector and is unaffected by dropping the qpair response interrupt early.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-09-16 11:16:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-97532",
                                "url": "https://ubuntu.com/security/CVE-2026-97532",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  scsi: qla2xxx: Null out freed pointers in qla2x00_mem_alloc() error path  When qla2x00_mem_alloc() fails, qla2x00_probe_one() jumps to probe_hw_failed and calls qla2x00_mem_free(). Several error labels in qla2x00_mem_alloc() freed adapter members (elsrej.c, purex_dma_pool, flt, sfp_data, loop_id_map, async_pd, sf_init_cb, ex_init_cb, npiv_info) but left the pointers dangling. qla2x00_mem_free() then freed them a second time. Worse, for the dma_pool members it issued dma_pool_free(ha->s_dma_pool, ...) after s_dma_pool had already been destroyed and set to NULL at fail_s_dma_pool, dereferencing a NULL pool.  Clear each freed pointer (and its DMA handle) in the error labels so the subsequent qla2x00_mem_free() skips them.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-09-25 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-89877",
                                "url": "https://ubuntu.com/security/CVE-2026-89877",
                                "cve_description": "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 existing MMIO mapping error path to remove the device from saa7164_devlist and decrement the device count before returning.  Also release BAR0 if it was successfully requested but the BAR2 request fails.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-09-16 11:16:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-93239",
                                "url": "https://ubuntu.com/security/CVE-2026-93239",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  arm64: mm: Fix the lockless page-table walk in show_pte()  show_pte() walks page tables locklessly and can run with interrupts enabled. A concurrent teardown can free a table page while it is being walked. It can also clear a parent entry after show_pte() checked it; the regular pXd_offset() helpers then reread the cleared entry and can derive a bogus lower-level pointer and fault again.  Use the lockless offset helpers with the saved parent entries, as gup_fast() does, and pass the saved PMD to pte_offset_map().  For task page tables, arm64 selects MMU_GATHER_RCU_TABLE_FREE. Disable local interrupts around the walk to hold off RCU-deferred table frees and block the tlb_remove_table_sync_one() IPI until the walk is finished.  Place the IRQ guard after the header print. This does not make the output a consistent snapshot, but prevents the task page-table walk from dereferencing a released table page or deriving a pointer from a different parent value.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-09-24 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-90023",
                                "url": "https://ubuntu.com/security/CVE-2026-90023",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  usb: gadget: f_mass_storage: fix null pointer dereference in fsg_common_set_num_buffers()  Previously fsg_num_buffers_validate() was removed as it was not necessary due to Kconfig setting the limits for n from 2 to 256 with default as 2. However, setting the page content in such a way that kstrtou8() reflects n value as either 0 or 1 bypasses these restrictions leading to a null pointer dereference if n is 0. Fix this by adding a check for n < 2 and returning -EINVAL if n is either 0 or 1 consistent with Kconfig logic.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-09-16 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-93200",
                                "url": "https://ubuntu.com/security/CVE-2026-93200",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  i3c: master: Fix use-after-free of master->this  sysfs attribute callbacks for the master controller device dereference master->this.  However, master->this is freed in i3c_master_detach_free_devs() before the master device itself is released.  As a result, sysfs accesses can dereference a freed master->this pointer, leading to a use-after-free.  Keep master->this alive until i3c_masterdev_release(), which is called after the master device and its sysfs state are being torn down. Do not free master->this as part of the normal device detach path.  On the error path in i3c_master_set_info(), reset master->this and bus.cur_master to NULL before freeing the allocated device.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-09-17 17:18:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-93199",
                                "url": "https://ubuntu.com/security/CVE-2026-93199",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  i3c: master: Do not treat master device as a duplicate target  i3c_master_search_i3c_dev_duplicate() searches the bus for another I3C device with the same PID as the reference device.  The search can match master->this, causing the controller itself to be returned as a duplicate.  Since the controller is not a target device, it cannot be a duplicate of one.  Exclude master->this from matching so that the function only returns real duplicate target devices.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-09-17 17:18:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-89441",
                                "url": "https://ubuntu.com/security/CVE-2026-89441",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  mmc: via-sdmmc: cancel card-detect work on remove  Disabling the device interrupt and freeing the IRQ prevents new card-detect work from being queued, but carddet_work already queued by the handler can still run after via_sd_remove() returns. via_sdc_card_detect() recovers the host through container_of() and dereferences its MMIO base; once remove() returns the host can be freed, so that work would touch freed memory.  Cancel carddet_work after freeing the IRQ and before cancelling finish_bh_work, which the card-detect handler can also queue. carddet_work can re-enable the interrupt through via_reset_pcictrl(); mask it again afterwards.  This issue was found by an in-house static analysis tool and confirmed by manual code review.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-09-11 20:19:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-89465",
                                "url": "https://ubuntu.com/security/CVE-2026-89465",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  power: supply: rt9455: quiesce delayed work before teardown  The threaded IRQ handler can queue pwr_rdy_work, max_charging_time_work and batt_presence_work.  pwr_rdy_work and batt_presence_work can also queue max_charging_time_work, while batt_presence_work can requeue itself.  rt9455_remove() cancels max_charging_time_work before batt_presence_work.  The latter can therefore queue max_charging_time_work after it has already been cancelled:    rt9455_remove()                   workqueue     cancel pwr_rdy_work     cancel max_charging_time_work                                       batt_presence_work queues                                         max_charging_time_work     cancel batt_presence_work     return     devres frees rt9455_info                                       max_charging_time_work dereferences                                         rt9455_info  The IRQ also remains registered until devres cleanup and can queue more work after any of the cancellation calls.  If rt9455_hw_init() fails after the IRQ has been requested, probe returns without cancelling work that may already have been queued.  A pending callback can then access rt9455_info after it has been freed.  Register rt9455_cancel_all_delayed_works() through devm_add_action_or_reset() right after devm_power_supply_register(). devres invokes the action in reverse registration order, after the managed IRQ has been freed and before rt9455_info is released, so the delayed works are drained in both rt9455_remove() and the probe error path.  Cancel pwr_rdy_work and batt_presence_work before max_charging_time_work because both can queue the latter.  This issue was found by an in-house static analysis tool.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-09-11 20:19:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-93231",
                                "url": "https://ubuntu.com/security/CVE-2026-93231",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  lockd: fix swapped arguments in nlmsvc_match_ip()  When releasing locks by server IP address via /proc/fs/nfsd/unlock_ip, nlmsvc_unlock_all_by_ip() calls nlm_traverse_files() with the server sockaddr as the opaque @data argument:  \tnlm_traverse_files(server_addr, nlmsvc_match_ip, NULL);  The match callback is later invoked from nlm_traverse_locks() as:  \tmatch(lockhost, host);  where the first argument is the nlm_host that owns the lock, and the second argument is the @data that was originally passed down (here the server sockaddr).  This is the convention every other match callback relies on (nlmsvc_mark_host(), nlmsvc_same_host(), nlmsvc_is_client()): arg1 is the real nlm_host, arg2 is the caller-supplied reference value.  nlmsvc_match_ip() has had these two arguments reversed ever since the unlock-by-IP feature was introduced in commit 4373ea84c84d (\"lockd: unlock lockd locks associated with a given server ip\"):  \treturn rpc_cmp_addr(nlm_srcaddr(host), datap);  Here @host is actually the server sockaddr, so nlm_srcaddr(host) dereferences a struct sockaddr as a struct nlm_host and reads garbage at the offset of h_srcaddr; meanwhile @datap is actually the lock owner's nlm_host but is compared as a sockaddr.  As a result the comparison practically never matches and locks are not released for the requested IP.  Swap the arguments so the lock owner's source address is compared against the requested server address:  \treturn rpc_cmp_addr(nlm_srcaddr(datap), (struct sockaddr *)host);  [ cel: fix the misleading typedef parameter names too ]",
                                "cve_priority": "low",
                                "cve_public_date": "2026-09-24 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-89552",
                                "url": "https://ubuntu.com/security/CVE-2026-89552",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  params: fix charp corruption on allocation failure  param_set_charp() stores charp parameters in allocated memory after slab is available, and releases the previous value when the parameter is updated.  The previous value is released before the replacement allocation succeeds. If kmalloc_parameter() fails, the setter returns -ENOMEM with the parameter left as NULL.  Failing zswap's compressor update before zswap is initialized can later trigger:    BUG: kernel NULL pointer dereference, address: 0000000000000000   RIP: 0010:strcmp+0x10/0x30   Call Trace:     zswap_setup+0x3b1/0x490     zswap_enabled_param_set+0x5b/0xa0     param_attr_store+0x93/0xe0     module_attr_store+0x1c/0x30     kernfs_fop_write_iter+0x116/0x1f0  Allocate and copy the replacement first, then replace the parameter value only after allocation succeeds.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-09-11 20:19:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-89640",
                                "url": "https://ubuntu.com/security/CVE-2026-89640",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  cifs: fix loff_t underflow in cifs_remap_file_range() when len == 0  With len == 0 (clone to EOF), the effective length is computed as:      len = src_inode->i_size - off;  If off > i_size, this is a negative loff_t, corrupting the ByteCount in the FSCTL_DUPLICATE_EXTENTS_TO_FILE request and inverting the range in filemap_write_and_wait_range().  The existing off >= i_size check fires only after the ioctl has already been sent.  Snapshot i_size_read() once for both the bounds check and the length calculation, eliminating the TOCTOU and 32-bit torn-read risk.  Reject off > src_size with -EINVAL.  Treat off == src_size as a no-op, consistent with __generic_remap_file_range_prep().",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-09-11 20:19:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-89672",
                                "url": "https://ubuntu.com/security/CVE-2026-89672",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  nfsd: gate nfs2 setacl by argp->mask  The NFSACL v2 SETACL path shares the decoder convention used by its v3 sibling: nfsaclsvc_decode_setaclargs() fills in argp->acl_access only when NFS_ACL is set in the request mask and argp->acl_default only when NFS_DFACL is set, leaving the other pointer NULL because the argument buffer is zeroed up to pc_argzero before decode.  nfsacld_proc_setacl() then hands both pointers to set_posix_acl() unconditionally. set_posix_acl(idmap, dentry, type, NULL) is the VFS \"remove this ACL type\" operation, so an omitted arm is indistinguishable from an explicit request to delete that ACL. A SETACL carrying only NFS_ACL silently strips the directory's default ACL; mask=0 strips both.  This is the same defect just fixed in nfsd3_proc_setacl(); apply the same remedy. Gate each set_posix_acl() call on its mask bit and initialize error to 0 so that a request with neither bit set leaves the on-disk ACLs untouched and returns success. The out_drop_lock path and the unconditional posix_acl_release() in nfsaclsvc_release_setacl() already tolerate the skipped arms.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-09-11 20:19:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-89685",
                                "url": "https://ubuntu.com/security/CVE-2026-89685",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  nfsd: fix clock domain mismatch in clients_still_reclaiming()  clients_still_reclaiming() computes a deadline from nn->boot_time (CLOCK_REALTIME, ~1.7 billion) but compares it against ktime_get_boottime_seconds() (CLOCK_BOOTTIME, seconds since boot). The comparison is always false — it would take ~54 years of uptime for BOOTTIME to exceed the REALTIME-derived deadline.  This means any client can hold the server in grace indefinitely by sending CLAIM_PREVIOUS OPEN requests, blocking all non-reclaim operations for all other clients.  Add boot_time_bt (CLOCK_BOOTTIME) alongside the existing boot_time and use it for the deadline computation. boot_time (CLOCK_REALTIME) is preserved for its cl_boot clientid-nonce role.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-09-11 20:19:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-89707",
                                "url": "https://ubuntu.com/security/CVE-2026-89707",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  nfsd: release path refs on follow_down() error  nfsd_cross_mnt() initializes a local struct path with mntget() and dget() before calling follow_down(). On a negative return the error arm jumps to out without releasing those references:      err = follow_down(&path, follow_flags);     if (err < 0)             goto out;  follow_down() never drops the caller's entry-time refs on any error sub-case; for example a pre-cross d_manage() failure leaves path untouched, so the mntget()/dget() taken on entry survive the call.  Every other early-exit arm in nfsd_cross_mnt() (other-namespace return, IS_ERR(exp2), and the success tail after the swap) already calls path_put(&path); the err < 0 arm is the lone omission. The leak inflates mnt_count and d_count on each failed cross-mount, blocking umount and pinning dentries against the shrinker, and is reachable by any authenticated NFS client through nfsd_lookup_dentry or the NFSv4 READDIR encode path.  Fix by calling path_put(&path) before the goto out in the err < 0 arm so the entry-time refs are released on all follow_down() error returns.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-09-11 20:19:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-89719",
                                "url": "https://ubuntu.com/security/CVE-2026-89719",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  zram: fix out-of-bounds access in read_block_state()  read_block_state() calculates nr_pages before taking dev_lock.  If the device is reset and reinitialized with a smaller disksize before lock acquisition, nr_pages still describes the old table.  The subsequent loop can then call slot_lock() past the end of the newly allocated table.  Read disksize after acquiring dev_lock and checking that the device is initialized.  The read lock then keeps the table and its bound stable for the duration of the scan.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-09-11 20:20:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-89763",
                                "url": "https://ubuntu.com/security/CVE-2026-89763",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  KEYS: trusted: Fix TPM teardown ordering  trusted_tpm_exit() drops the TPM chip reference and frees the digest array before unregistering the trusted key type. key_type_lookup() holds key_types_sem for reading until the key operation finishes, while unregister_key_type() takes it for writing. It therefore provides the synchronization point that must precede backend teardown.  The current order permits this interleaving:    CPU 0                              CPU 1   trusted_tpm_exit()                 key_type_lookup(\"trusted\")     put_device(&chip->dev)             trusted_tpm_seal()     kfree(digests)                       pcrlock()     unregister_key_type()                  tpm_pcr_extend(..., digests)  CPU 1 can consequently dereference the freed digest array. The chip can also be released before callbacks stop using it.  KASAN reported:    BUG: KASAN: slab-use-after-free in tpm_pcr_extend+0x1f0/0x200   Read of size 2 at addr ffff88810872d000 by task poc/89   Call Trace:     tpm_pcr_extend+0x1f0/0x200     pcrlock+0x42/0x70 [trusted]     trusted_tpm_seal+0x1b6/0x570 [trusted]     trusted_instantiate+0x293/0x340 [trusted]     __key_instantiate_and_link+0xb2/0x2b0     __key_create_or_update+0x61e/0xb50     __do_sys_add_key+0x1b8/0x310   Allocated by task 88:     __kmalloc_noprof+0x1a7/0x490     do_one_initcall+0xa1/0x390     do_init_module+0x2df/0x840   Freed by task 90:     kfree+0x131/0x3c0     trusted_tpm_exit+0x59/0xa0 [trusted]     __do_sys_delete_module+0x346/0x510  Move unregister_key_type() before releasing either resource. This stops new lookups and waits for in-flight key operations to finish before the backend state is destroyed.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-09-11 20:20:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-80851",
                                "url": "https://ubuntu.com/security/CVE-2026-80851",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  gtp: serialize PDP context updates  PDP contexts can be deleted through GTP_CMD_DELPDP or while the GTP network device is being unregistered. The latter is serialized by RTNL, but the generic-netlink delete path only holds RCU.  Running both paths concurrently can therefore make both paths delete the same PDP context. The issue was found through static analysis and reproduced on a KASAN-enabled kernel by a simple two-thread program racing GTP_CMD_DELPDP against RTM_DELLINK:    Oops: general protection fault, probably for non-canonical address   KASAN: maybe wild-memory-access in range          [0xdead000000000120-0xdead000000000127]   RIP: gtp_genl_del_pdp+0x1c1/0x420 [gtp]   RBP: dead000000000122  The second deletion dereferenced the poisoned hlist pprev pointer.  Serialize gtp_pdp_add(), gtp_genl_del_pdp(), and gtp_dellink() with a shared mutex. Keep the mutex held until the final use of a PDP context in the NEWPDP path, and keep the RCU read-side section around the complete PDP context use in the DELPDP path.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-09-04 16:18:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-80861",
                                "url": "https://ubuntu.com/security/CVE-2026-80861",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  usb: xhci: bail out of setup if the controller is inaccessible  xhci_gen_setup() locates the operational registers using the capability length read from the very first register:  \txhci->op_regs = hcd->regs + \t\tHC_LENGTH(readl(&xhci->cap_regs->hc_capbase));  If the controller is dead or has dropped off the bus, that read returns ~0, HC_LENGTH() truncates it to 0xff, and op_regs ends up 0xff bytes past the page-aligned MMIO base, i.e. unaligned. The first access through it, xhci_halt() -> xhci_handshake() reading op_regs->status, is then an unaligned readl() on device memory. arm64 faults on unaligned device accesses, so instead of xhci_handshake() catching the all-ones value and returning -ENODEV, setup oopses:    xhci-pci-renesas 0005:08:00.0: Unable to change power state from D3cold to D0, device inaccessible   xhci-pci-renesas 0005:08:00.0: xHCI Host Controller   xhci-pci-renesas 0005:08:00.0: new USB bus registered, assigned bus number 1   Unable to handle kernel paging request at virtual address ffff80030a770103     ESR = 0x0000000096000021     FSC = 0x21: alignment fault   Internal error: Oops: 0000000096000021 [#1]  SMP   pc : xhci_halt [xhci_hcd]   Call trace:    xhci_halt    xhci_gen_setup    xhci_pci_setup    usb_add_hcd    usb_hcd_pci_probe    xhci_pci_common_probe    xhci_pci_renesas_probe  This was hit with a Renesas uPD720201 that failed to power up (\"Unable to change power state from D3cold to D0, device inaccessible\") yet still reached the HCD probe path.  Read the capability register once, and if it reads back the all-ones value (as xhci_handshake() and xhci_reset() already test for), abort setup with -ENODEV before op_regs is derived from it. Reading it once also avoids re-reading a register that may change under a concurrent hot-removal.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-09-04 16:18:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98377",
                                "url": "https://ubuntu.com/security/CVE-2026-98377",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  vlan: require the MAC header to be present in __vlan_insert_inner_tag()  __vlan_insert_inner_tag() only guarantees head room via skb_cow_head(), never that mac_len bytes of MAC header are present.  Its ETH_HLEN wrappers - __vlan_insert_tag() under skb_vlan_push(), and vlan_insert_tag() under validate_xmit_vlan() on the generic transmit path - therefore rewrite the first 16 bytes at skb->data: a 12-byte memmove plus two 2-byte stores at +12 and +14.  No caller supplies the bound, while the pop helpers use skb_ensure_writable()/pskb_may_pull().  An IFF_TUN device has hard_header_len == 0, so packet_snd() accepts a one-byte AF_PACKET/SOCK_RAW frame.  The first vlan push only sets a hwaccel tag; the next - clsact \"action vlan push\" or bpf_skb_vlan_push() - enters the helper with skb->len still 1.  The head comes from skbuff_small_head without __GFP_ZERO, so each push drags bytes from beyond skb->tail into the frame.  After three the one-byte send leaves as 13 bytes carrying 11 bytes of uninitialised slab:    0000: 5a b3 62 12 80 88 ff ff 00 b3 62 12 81            `------------------------------'   only 0x5a was sent; the rest is slab, here the top 56 bits of a   linear-map address  Require the MAC header the helper rewrites to be present, so such a frame is dropped rather than transmitted.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-09 08:16:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98170",
                                "url": "https://ubuntu.com/security/CVE-2026-98170",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  smb: client: fix OOB struct field reads in move_smb2_ea_to_cifs()  In move_smb2_ea_to_cifs(), the while (src_size > 0) loop condition is insufficient. It allows iteration to continue even if the remaining src_size is too small to contain a complete smb2_ea_info structure. Consequently, reads of ea_name_length and ea_value_length can occur out-of-bounds.  Fix this by ensuring src_size >= sizeof(*src) before attempting to read any structure fields. Additionally, reject any next_entry_offset that is smaller than sizeof(*src) or that would advance the pointer beyond the available buffer.  Note that for calls where the server returns a malformed EA list, the error returned to userspace changes from -ENODATA (getxattr) or -ERANGE (listxattr) to -EIO. This correctly signals a server protocol error rather than misleadingly indicating \"attribute not present\" or \"output buffer too small\".",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-06 09:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98171",
                                "url": "https://ubuntu.com/security/CVE-2026-98171",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  smb: client: fix next_buffer UAF and NextCommand bounds in compound PDUs  Fix several related bounds checking and pointer lifecycle issues in receive_encrypted_standard()'s handling of compound encrypted frames:  - Clear next_buffer after assigning it to server->bigbuf. A stale   next_buffer pointer can lead to a use-after-free on subsequent   error paths. - Update pdu_length to the decrypted plaintext size (buf_size). Using   the pre-decryption length allows NextCommand to point into stale   ciphertext residue. - Reject next_cmd values smaller than MID_HEADER_SIZE(server). - Fix an integer overflow in the upper bound check by verifying   pdu_length - next_cmd < MID_HEADER_SIZE(server), ensuring the   trailing slice is large enough for a header.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-06 09:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98169",
                                "url": "https://ubuntu.com/security/CVE-2026-98169",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  smb: client: fix potential OOB read in smb3_enum_snapshots()  If snapshot_array_size is smaller than GMT_TOKEN_SIZE, smb3_enum_snapshots() sets ret_data_len to sizeof(struct smb_snapshot_array) without verifying the actual length of the server's reply.  Because SMB2_ioctl() places no lower bound on the server-supplied OutputCount and allocates retbuf to exactly that length, a short reply results in ret_data_len exceeding the size of retbuf. The subsequent copy_to_user() then reads past the end of retbuf, leaking adjacent slab memory to userspace.  The subsequent clamp check is ineffective as it only reduces ret_data_len.  Fix this by rejecting replies shorter than sizeof(struct smb_snapshot_array) with -EIO. Note that the bound is set to the 12-byte struct size rather than the 16-byte MIN_SNAPSHOT_ARRAY_SIZE defined in MS-SMB2 3.3.5.15.1, because 12 bytes is exactly what copy_to_user() attempts to read.",
                                "cve_priority": "negligible",
                                "cve_public_date": "2026-10-06 09:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98193",
                                "url": "https://ubuntu.com/security/CVE-2026-98193",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: libipw: reject TKIP frames without a full MIC  libipw_michael_mic_verify() assumes that an skb contains an eight-byte Michael MIC. A short TKIP frame makes the unsigned payload length wrap, causing michael_mic() to read past the skb.  Check that the MIC is present before verifying it, and use the existing MICHAEL_MIC_LEN constant for all MIC lengths in the verifier.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-06 09:18:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-97555",
                                "url": "https://ubuntu.com/security/CVE-2026-97555",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  smb: client: fix heap overflow in DACL owner/group rewrite  When id_mode_to_cifs_acl rewrites an existing DACL, it allocates a buffer sized according to the on-disk DACL length reported by dacl_ptr->size. However, replace_sids_and_copy_aces may rewrite each ACE with a new owner/group SID obtained from the cifs.idmap upcall. Those SIDs can have up to SID_MAX_SUB_AUTHORITIES (15) sub-authorities, making each ACE up to 76 bytes (sizeof(struct smb_ace)).  If the original DACL contains short SIDs (e.g., 1 sub-authority) while the replacement SIDs are long, the rewritten ACEs overflow the allocation.  Fix this by always budgeting for worst-case SID expansion: allocate sizeof(struct smb_acl) plus num_aces * sizeof(struct smb_ace), which covers the smb_acl header and room for every ACE at maximum SID size. This replaces the previous split logic that used dacl_ptr->size for cifsacl mounts but num_aces * sizeof(struct smb_ace) for mode_from_sid mounts: both paths can trigger the same rewrite and need the same headroom.  KASAN reports this as:   BUG: KASAN: slab-out-of-bounds in build_sec_desc+0x1e8a/0x2680 [cifs]   Write of size 4 at addr ffff8881a5e25374 by task chown/5298   ...   The buggy address is located 0 bytes to the right of    allocated 884-byte region [ffff8881a5e25000, ffff8881a5e25374)",
                                "cve_priority": "high",
                                "cve_public_date": "2026-09-25 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-97557",
                                "url": "https://ubuntu.com/security/CVE-2026-97557",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  smb: client: avoid leaking refcount in cifs_queue_oplock_break()  cifs_queue_oplock_break() unconditionally takes a reference on the target file before queueing cifs_oplock_break(). Only that work item decreases the reference counter again.  If another oplock break arrives while that work is still queued, queue_work() will return false and not queue this second work item. As a result, we will never reach the point to drop the file reference again and are leaking this reference. This can be triggered when interacting with a slow-responding server.  As a result, later unmount operations for this file system will fail with    BUG: Dentry ... still in use (1) [unmount of cifs cifs]   VFS: Busy inodes after unmount of cifs (cifs)   kernel BUG at fs/super.c:777!  Fix this by only incrementing the reference count if the work has been queued successfully. Taking it after queue_work() is safe because all three callers hold tcon->open_file_lock across the call and _cifsFileInfo_put() decrements under that same lock, so a worker that starts the handler in the window cannot drop the reference before it has been taken.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-09-25 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-97564",
                                "url": "https://ubuntu.com/security/CVE-2026-97564",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  smb: client: reject userspace cifs.idmap descriptions  cifs.idmap key descriptions carry authority-bearing fields (owner and group SIDs and uid/gid values in \"os:\"/\"gs:\"/\"oi:\"/\"gi:\" form) that the cifs.idmap upcall helper treats as kernel-originating inputs.  Unlike its sibling cifs.spnego, the cifs.idmap key type has no vet_description hook, so userspace can create keys of this type through request_key(2)/add_key(2) and supply those fields without CIFS origin. A request_key(2) call with a non-NULL callout then drives a root usermodehelper upcall (/sbin/request-key -> cifs.idmap) that consumes the unvetted description in root context.  Only accept cifs.idmap descriptions while CIFS is using its private root_cred to request the key.  id_to_sid()/sid_to_id() already run under override_creds(root_cred), so the kernel-originated path is unaffected.  This mirrors commit 3da1fdf4efbc (\"smb: client: reject userspace cifs.spnego descriptions\"), which applied the same restriction to cifs.spnego.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-09-25 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-97615",
                                "url": "https://ubuntu.com/security/CVE-2026-97615",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net: bridge: use option bits for CFM/MRP frame handlers  CFM and MRP register a global br_frame_type whose hlist_node is linked into the per-bridge frame_type_list when the first MEP/MRP instance is created. Enabling the protocol on multiple bridges therefore inserts the same node into multiple lists. Unregistering it on one bridge then corrupts list state belonging to another.  These handlers can only be installed once per bridge, and they are uncommon. Track their per-bridge enable state with net_bridge option bits, which already live on the Rx hot cache line, and dispatch the matching handler directly from the receive path. Check both bits together first as an unlikely case.  Remove the generic frame_type_list and br_frame_type helpers, which have had no other users since CFM and MRP were added. That shrinks struct net_bridge by 8 bytes and drops the list walk from the fast path. When neither protocol is compiled in, BR_CFM_MRP_OPTS is 0 and the compiler prunes the branch.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-09-25 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-97901",
                                "url": "https://ubuntu.com/security/CVE-2026-97901",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  genetlink: pin family module during policy dump  The generic netlink controller's policy dump keeps pointers to the target family's operation and policy tables in its callback state.  A dump may be split across multiple skbs and remain pending after the initial request.  Netlink pins the module which owns the dump callback, but in this case that is the controller's owner rather than the target family's owner.  The target family can consequently be unregistered and its module unloaded while a policy dump is pending.  Advancing the dump then dereferences policy memory from the unloaded module.  Take a reference to the target family's module when the dump starts. Drop it from the error and done paths.  This matches the lifetime for which the dump context retains the family and policy pointers.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-09-25 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-97908",
                                "url": "https://ubuntu.com/security/CVE-2026-97908",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  Bluetooth: btqcomsmd: destroy RPMsg endpoints before freeing hci_dev  The command and ACL RPMsg endpoints store struct btqcomsmd as their callback private data. The receive callbacks dereference btq->hdev without taking an hci_dev reference.  The current teardown order frees the hci_dev before destroying the RPMsg endpoints in both the hci_register_dev() error path and the driver remove path. If WCNSS delivers data in that window, the endpoint callback can run with an already freed hci_dev and pass it to the Bluetooth core.  For qcom_smd endpoints, rpmsg_destroy_ept() closes the channel and clears the callback under the channel recv_lock. The receive path holds the same lock while invoking the callback, so destroying the endpoints first both prevents new callbacks and serializes with any callback already running.  Destroy the command and ACL endpoints before hci_free_dev(). Keep hci_unregister_dev() first during remove so the HCI core stops issuing operations before the transport endpoints are shut down. In the full registration-error cleanup path, return directly after freeing the hci_dev to avoid falling through to the partial-construction labels and destroying the endpoints twice.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-09-25 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-97925",
                                "url": "https://ubuntu.com/security/CVE-2026-97925",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  tick/broadcast: Plug clockevents replacement race  朱恺乾 reported and decoded the following race condition when a broadcast device is replaced:  CPUA\t\t\t\t\tCPUB  __tick_broadcast_oneshot_control()    bc = tick_broadcast_device.evtdev; \t\t\t\t\ttick_install_broadcast_device(dev)         \t\t\t\tclockevents_exchange_device(cur, dev) \t\t\t\t\t   shutdown(cur); \t\t\t\t\t   detach(cur); \t\t\t\t\t   cur->handler = noop; \t\t\t\t\t   tick_broadcast_device.evtdev = dev;    tick_broadcast_set_event(bc, next_event); <- FAIL: arms a detached device.  If the original broadcast device has a restricted interrupt affinity mask and the last CPU in that mask goes offline then the BUG() in tick_cleanup_dead_cpu() triggers because the clockevent device is not in detached state.  The reason for this is that tick_install_broadcast_device() is not serialized vs. tick broadcast operations.  The obvious cure is to serialize tick_install_broadcast_device() with tick_broadcast_lock against a concurrent tick broadcast operation.  That requires to split clockevents_exchange_device() into two parts, one which does the exchange, shutdown and detach operation and the other which drops the module reference count. This is required because the module reference cannot be dropped while holding tick_broadcast_lock.  Let clockevents_exchange_device() do both operations as before, but let the broadcast device code take the two step approach and do the device exchange under tick_broadcast_lock and drop the module reference count after releasing it.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-09-25 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-93285",
                                "url": "https://ubuntu.com/security/CVE-2026-93285",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  f2fs: embed f2fs_gc_kthread in f2fs_sb_info  Instead of allocating f2fs_gc_kthread dynamically, embed it in f2fs_sb_info. This simplifies lifetime management and prepares for fixing race conditions during teardown.  - __sbi_store\t\t\t- remount|shutdown \t\t\t\t - f2fs_stop_gc_thread  - access sbi->gc_thread \t\t\t\t  - sbi->gc_thread = NULL  - access sbi->gc_thread->f2fs_gc_task",
                                "cve_priority": "low",
                                "cve_public_date": "2026-09-24 17:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-97529",
                                "url": "https://ubuntu.com/security/CVE-2026-97529",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  scsi: qla2xxx: Validate BSG request_len before reading vendor_cmd[]  The FC BSG transport allocates job->request via memdup_user() using the exact user-supplied request_len. For FC_BSG_HST_VENDOR, fc_bsg_host_dispatch() only guarantees request_len covers msgcode and vendor_id; it does not account for the vendor_cmd[] flexible array.  qla2xxx then reads the command selector vendor_cmd[0] and, in several sub-handlers, vendor_cmd[1]/[2] or structures overlaid on the vendor command area without verifying request_len. A caller holding CAP_SYS_RAWIO can submit a short request whose vendor_id matches the host, triggering out-of-bounds heap reads (KASAN-detectable, and able to mis-select a command or panic).  Add a central guard in qla2x00_process_vendor_specific() so the selector is always in bounds, restrict the early vendor_cmd[0] read in qla24xx_bsg_request() to sufficiently long vendor messages, and add request_len checks to the sub-handlers that read further: qla24xx_proc_fcp_prio_cfg_cmd(), qla2x00_process_loopback(), qla84xx_reset(), qla84xx_updatefw(), qla2x00_read_optrom(), qla2x00_update_optrom(), qlafx00_mgmt_cmd() and qla28xx_validate_flash_image().",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-09-25 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-97536",
                                "url": "https://ubuntu.com/security/CVE-2026-97536",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  scsi: qla2xxx: Fix use-after-free of qpair work on queue teardown  The response queue MSI-X handler qla2xxx_msix_rsp_q() schedules qla_do_work() via queue_work(ha->wq, &qpair->q_work). qla_do_work() dereferences the qpair (vha, rsp) and takes qpair->qp_lock.  During teardown, qla2xxx_delete_qpair() deletes the response queue, which calls free_irq() in qla25xx_free_rsp_que(), and then frees the queue and the qpair. free_irq() waits for running hardirq handlers but does not cancel work already placed on ha->wq. A still-pending q_work then runs qla_do_work() against the freed qpair and response queue, causing a use-after-free. This is especially likely during full adapter teardown, where destroy_workqueue(ha->wq) forces pending work to run after the queue pairs have been freed.  Flush the work item with cancel_work_sync() in qla25xx_free_rsp_que() after free_irq() has released the interrupt (so no new work can be queued) and before the response queue and qpair memory are freed (so the flushed handler still sees valid memory). Guard on rsp->qpair and ha->wq to match the INIT_WORK() condition and avoid operating on an uninitialized work_struct.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-09-25 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-97537",
                                "url": "https://ubuntu.com/security/CVE-2026-97537",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  scsi: qla2xxx: Fix queue teardown NULL dma_free and bitmap locking  qla25xx_free_req_que() and qla25xx_free_rsp_que() have two pre-existing bugs exposed on the error path of qla25xx_create_{req,rsp}_que():   1. When dma_alloc_coherent() fails during queue creation, the error     path calls the free function with req->ring / rsp->ring still NULL     (from kzalloc).  The unconditional dma_free_coherent() with a NULL     cpu_addr is undefined behavior and can panic.   2. The free functions clear req_qid_map / rsp_qid_map under vport_lock,     but the create functions protect the same bitmaps with mq_lock.     This provides no mutual exclusion.  Additionally, the create error     path clears the bit and releases mq_lock before calling the free     function, creating a window where another thread can allocate the     same que_id and have its ha->req_q_map entry clobbered by the     subsequent lockless NULL assignment in the free function.  Fix by:   - Guarding dma_free_coherent() with a NULL check on the ring pointer.   - Using mq_lock (the lock held by all creators) in the free functions    to atomically NULL the map entry and clear the bitmap bit.   - Removing the now-redundant clear_bit blocks from the create error    paths since the free functions handle it atomically.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-09-25 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-89859",
                                "url": "https://ubuntu.com/security/CVE-2026-89859",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  scsi: qla2xxx: Zero dport diagnostics buffer to avoid info leak  qla2x00_do_dport_diagnostics() allocates the qla_dport_diag response buffer with kmalloc_obj() (non-zeroing) and, on success, copies the full sizeof(*dd) back to user space via sg_copy_from_buffer(). The inbound sg_copy_to_buffer() only fills as many bytes as the user request payload provides, and qla26xx_dport_diagnostics() zeroes only dd->buf. The options and unused[] fields are therefore copied out uninitialized, leaking kernel heap contents to user space.  Allocate with kzalloc_obj(), matching qla2x00_do_dport_diagnostics_v2().",
                                "cve_priority": "low",
                                "cve_public_date": "2026-09-16 11:16:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-89921",
                                "url": "https://ubuntu.com/security/CVE-2026-89921",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  KVM: s390: Zero initialize data structures for inject_pfault_token  __kvm_inject_pfault_token() only sets .type and .u.ext.ext_params2 of the on-stack struct kvm_s390_irq but the full ext substructure is copied into the cpu local variable on inject. ext_params and pad contain stale stack values.  Interrupt delivery only uses ext_params2, so nothing leaks to the guest, but a host user can use the migration ioctls to get to the data.  Fix by zero-initializing the irq struct. Do the same for the inti data structure.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-09-16 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-89972",
                                "url": "https://ubuntu.com/security/CVE-2026-89972",
                                "cve_description": "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 reference to ns when kfree(ns) runs.  The normal removal path in nvme_ns_remove() correctly calls synchronize_srcu(&ns->head->srcu) after list_del_rcu() to wait for in-progress readers. Add the same grace period in the error path.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-09-16 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-89988",
                                "url": "https://ubuntu.com/security/CVE-2026-89988",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  kprobes: Protect kprobe_blacklist with RCU  __within_kprobe_blacklist() traverses kprobe_blacklist without holding kprobe_mutex. When a module is unloaded, kprobe_remove_area_blacklist() removes blacklist entries and immediately frees them with kfree(). A concurrent call to within_kprobe_blacklist() can therefore dereference freed memory.  Furthermore, within_kprobe_blacklist() can be called in atomic or non-preemptible contexts where the sleeping kprobe_mutex cannot be taken.  Protect kprobe_blacklist with RCU. Use guard(rcu)() and list_for_each_entry_rcu() for traversal, list_add_tail_rcu() for insertions, list_del_rcu() for deletions, and kfree_rcu() to reclaim entries safely after a grace period.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-09-16 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-90002",
                                "url": "https://ubuntu.com/security/CVE-2026-90002",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ftrace: Take trace_array reference before accessing its ftrace_ops  The trace instance files set_ftrace_filter and set_ftrace_notrace was updated to work with specific trace instances (trace_arrays). The issue is that when these files are opened, there is a small race window where it will use the ftrace_ops from the inode->private pointer to get a reference to the trace_array and then take its reference. The problem is that the ftrace_ops itself could be freed. If the rmdir on the instance happens at the same time the set_ftrace_filter file is opened, the rmdir could have also freed the ftrace_ops and referencing it will cause a use-after-free bug and crash the kernel.  Instead, pass in the trace_array as the file private data (NULL for the top level instance), and then pass both the trace_array and the ftrace_ops to the ftrace_regex_open() function. If the trace_array is NULL, then it just uses the ftrace_ops without the need to take its reference (like normal). If the ftrace_ops is NULL, that is only the case for the top level instance and the global_ops can be used.  This allows the trace_array to have its reference incremented before touching the ftrace_ops that could also be freed when the instance is.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-09-16 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-90016",
                                "url": "https://ubuntu.com/security/CVE-2026-90016",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  staging: rtl8723bs: fix OOB read in rtw_restruct_wmm_ie()  rtw_restruct_wmm_ie() scans in_ie for a WMM IE with:  \twhile (i < in_len) { \t\t... \t\tif (i + 5 < in_len && in_ie[i] == 0xDD && ...) { \t\t\t... \t\t\tbreak; \t\t} \t\ti += (in_ie[i + 1] + 2); /* to the next IE element */ \t}  When the \"i + 5 < in_len\" match check fails simply because i is within 5 bytes of the end of the buffer (i.e. no WMM IE was found near the tail of in_ie), execution falls through to \"i += (in_ie[i + 1] + 2)\", which reads in_ie[i + 1]. If i == in_len - 1 at that point, this is a 1-byte out-of-bounds read of an attacker-influenced IE buffer built from association/scan data.  Commit a75281626fc8f (\"staging: rtl8723bs: fix potential out-of-bounds read in rtw_restruct_wmm_ie\") added the \"i + 5 < in_len\" guard to the match condition itself, but did not add an equivalent guard before the fallthrough advance, so the same class of OOB read remained reachable through the non-matching path.  Add an explicit bounds check before advancing to the next IE.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-09-16 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-90029",
                                "url": "https://ubuntu.com/security/CVE-2026-90029",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  usb: storage: realtek_cr: fix use-after-free on disconnect  realtek_cr_destructor() calls timer_delete() before the chip containing the timer is freed. The timer callback may still be running and can rearm itself, resulting in a use-after-free.  Use timer_shutdown_sync() to wait for the callback and prevent further rearming. Do this unconditionally because ss_en may be changed after the timer is armed.  Move timer_setup() into init_realtek_cr() so the timer is initialized before any failure path can invoke the destructor.  Found by static analysis.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-09-16 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-80947",
                                "url": "https://ubuntu.com/security/CVE-2026-80947",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: rtl8xxxu: fix use-after-free from rx_urb_wq on stop  rtl8xxxu arms rx_urb_wq from the RX completion path: rtl8xxxu_rx_complete() hands the URB to rtl8xxxu_queue_rx_urb(), which queues it on rx_urb_pending_list and, once the list grows past RTL8XXXU_RX_URB_PENDING_WATER, schedules rx_urb_wq.  The worker rtl8xxxu_rx_urb_work() drains rx_urb_pending_list, recovers priv through container_of, and resubmits each URB through rtl8xxxu_submit_rx_urb(), which anchors it on rx_anchor and dereferences priv->udev.  rtl8xxxu_stop() cancels the sibling work items (c2hcmd_work, ra_watchdog, update_beacon_work) but never cancels rx_urb_wq, so a worker armed during the last burst of RX traffic can run rtl8xxxu_rx_urb_work() after rtl8xxxu_disconnect() has called ieee80211_free_hw(), which frees priv, producing a use-after-free.  The window opens under active RX traffic (pending count above the watermark) followed by a disconnect.  There are two teardown races to close:    * rtl8xxxu_queue_rx_urb() decided whether to enqueue under rx_urb_lock     but called schedule_work() after dropping the lock.  A completion     that observed shutdown == false and released the lock could then call     schedule_work() after rtl8xxxu_stop() had set shutdown and     cancel_work_sync() had already returned, arming the worker to run     after the teardown.  Move schedule_work() under the same !shutdown     branch so the arming decision is atomic with the shutdown check.    * rtl8xxxu_rx_urb_work() anchors every URB it drained back onto     rx_anchor through rtl8xxxu_submit_rx_urb().  A worker still running     when usb_kill_anchored_urbs(&priv->rx_anchor) returned would submit a     URB that escaped the kill.  In rtl8xxxu_stop(), call     cancel_work_sync(&priv->rx_urb_wq) before the kill so the worker is     drained first.  After priv->shutdown is set under rx_urb_lock, completions can no longer queue rx_urb_wq. cancel_work_sync() then drains the last queued or running worker, and the following usb_kill_anchored_urbs() kills the URBs it may have submitted.  rtl8xxxu_disconnect() is covered because ieee80211_unregister_hw() guarantees .stop() runs for a live interface before ieee80211_free_hw() frees priv.  The probe error path needs no cancel: rx_urb_wq is INIT_WORK()'d there but cannot have been scheduled, since no URB is submitted before ieee80211_register_hw() succeeds.  This bug was found by static analysis.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-09-11 20:19:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-89481",
                                "url": "https://ubuntu.com/security/CVE-2026-89481",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  nvme-tcp: fix host memory disclosure on R2T for a read command  nvme_tcp_handle_r2t() does not check the direction of the request the R2T refers to. A malicious controller can send an R2T for a READ and the host will answer it: nvme_tcp_setup_h2c_data_pdu() builds the H2CData header and nvme_tcp_try_send_data() sends the request's data buffer. That buffer is the READ destination, so its contents go to the controller.  The command then completes normally and nothing is logged.  Against a test controller that answers every READ with an R2T, a 4096 byte buffered read returned all 4096 bytes, split over two R2Ts. The pages contained stale kernel data, including an array of struct page pointers.  Reject an R2T for a request that is not a write.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-09-11 20:19:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-89492",
                                "url": "https://ubuntu.com/security/CVE-2026-89492",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ocfs2: validate directory-index entry counts when reading metadata  ocfs2_validate_dx_leaf() and ocfs2_validate_dx_root() check the ECC and signature of an indexed-directory block before it reaches higher-level callers, but neither validator bounds the ocfs2_dx_entry_list counts against the capacity of the block that holds them.  ocfs2_dx_dir_search() then walks  \tfor (i = 0; i < le16_to_cpu(entry_list->de_num_used); i++) \t\tdx_entry = &entry_list->de_entries[i];  over de_num_used entries with no bounds check.  entry_list is either dx_leaf->dl_list (from ocfs2_read_dx_leaf) or, for an inline root, dx_root->dr_entries.  A crafted on-disk image can set de_num_used (and de_count, which is the __counted_by_le() bound of de_entries) to 0xffff and make the walk read far past the end of the 4KB metadata block, giving a slab out-of-bounds read reachable from any path lookup, stat() or open() on an indexed directory once the image is mounted.  Commit 775c17386a6f (\"ocfs2: validate dx_root extent list fields during block read\") already bounds dr_list for the non-inline dx_root, but left the inline dr_entries path and the dx_leaf dl_list unchecked.  Add the same read-time validation for both entry lists: de_count must equal the capacity of the block (ocfs2_dx_entries_per_leaf()/per_root()) and de_num_used must not exceed de_count, rejecting corrupted metadata with -EFSCORRUPTED before ocfs2_dx_dir_search() can walk an out-of-range entry array.  de_count is always written as exactly the block capacity when a leaf or inline root is formatted, so the equality check does not reject any valid image.  Found by 0sec automated security-research tooling (https://0sec.ai).",
                                "cve_priority": "high",
                                "cve_public_date": "2026-09-11 20:19:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-89553",
                                "url": "https://ubuntu.com/security/CVE-2026-89553",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  nouveau/gem: reserve the bo in the info ioctl around the vma lookup  In the non-uvmm path, there could be a race between the info lookup finding the vma, and the gem close path closing the vma leading to a use-after-free.  Spotted with the help of Opus 4.6.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-09-11 20:19:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-89625",
                                "url": "https://ubuntu.com/security/CVE-2026-89625",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  HID: sony: fix UAF of ghl_poke_timer / ghl_urb at driver unbind  For GHL (Guitar Hero Live) dongles, sony_probe() arms a periodic timer: ghl_magic_poke() (the timer callback) submits sc->ghl_urb, and the URB completion ghl_magic_poke_cb() re-arms the timer with mod_timer().  sony_remove() drained the timer with timer_delete_sync() and then freed the URB with usb_free_urb():  \ttimer_delete_sync(&sc->ghl_poke_timer); \tusb_free_urb(sc->ghl_urb);  timer_delete_sync() does not block re-arming, and while the URB is in flight the timer is not pending, so the sync delete is a no-op. A URB completion that runs after the delete re-arms the timer, and usb_free_urb() only drops a reference -- it does not kill an in-flight URB. sc is allocated with devm_kzalloc() and freed once sony_remove() returns, so the re-armed ghl_poke_timer (embedded in sc) then fires on freed memory, a use-after-free from timer softirq. This is a disconnect/rmmod race.  Poison the URB first, then shut the timer down, before freeing the URB. usb_poison_urb() kills any in-flight URB and permanently rejects further submissions, so a poke timer that is still pending cannot re-submit the URB from ghl_magic_poke() in the window before timer_shutdown_sync() runs. usb_kill_urb() would not suffice: it only cancels the in-flight URB and leaves it submittable once it returns, so the pending timer could re-submit it and put a fresh URB in flight over the freed sc. timer_shutdown_sync() then drains any last callback and blocks re-arming. The probe error path is unaffected: it is only reached before the timer is armed.  Reproduced under KASAN on next-20260710 via dummy_hcd + raw-gadget emulation of the GHL PS4 dongle (VID 0x1430 / PID 0x07bb): hid-sony binds and arms the poke timer, the poke URB is held in flight, the driver is unbound (freeing sc), then the URB is released. The completion re-arms the timer on the freed sc, and the re-armed timer fires ~8 s later:    BUG: KASAN: slab-use-after-free in ghl_magic_poke+0x98/0xb0   Read of size 8 at addr ffff88810b02fd50 by task swapper/0/0    ghl_magic_poke+0x98/0xb0    call_timer_fn+0x35/0x2b0    __run_timers+0x69c/0x9a0    run_timer_softirq+0x173/0x2a0   Allocated by task 169:  sony_probe   Freed by task 338:      devres_release_group <- hid_device_remove (sony_remove)  Found by 0sec (https://0sec.ai) using automated source analysis.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-09-11 20:19:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-89633",
                                "url": "https://ubuntu.com/security/CVE-2026-89633",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  smb: client: fix OOB read/write from unvalidated DataOffset in coalesce_t2()  coalesce_t2() computes data pointers directly from server-supplied DataOffset fields with no validation against buffer bounds:    data_area_of_tgt = (char *)&pSMBt->hdr.Protocol +                      get_unaligned_le16(&pSMBt->t2_rsp.DataOffset);   data_area_of_src = (char *)&pSMBs->hdr.Protocol +                      get_unaligned_le16(&pSMBs->t2_rsp.DataOffset);   data_area_of_tgt += total_in_tgt;   ...   memcpy(data_area_of_tgt, data_area_of_src, total_in_src);  A small DataOffset can push a pointer below the actual byte area, overwriting header fields; a large one can push it past the buffer end, causing out-of-bounds heap reads (source) or writes (target). The BCC overflow guard does not prevent this: BCC reflects how much data is present, while DataOffset controls where in the buffer it starts.  The \"validate target area\" comment present since the function was first written in 2005 was a placeholder that was never implemented.  Add lower- and upper-bound checks for both data pointers before the memcpy, and before any target header fields are modified.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-09-11 20:19:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-89652",
                                "url": "https://ubuntu.com/security/CVE-2026-89652",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ceph: bound copied dentry name length in NFS export get_name  ceph_get_name() copies the MDS-supplied name into the caller's NAME_MAX-sized buffer with memcpy(name, rinfo->dname, rinfo->dname_len) and then writes name[rinfo->dname_len] = 0, without checking dname_len against NAME_MAX. A malicious or buggy MDS that returns a LOOKUPNAME reply with dname_len > NAME_MAX overflows the buffer. __get_snap_name() copies rde->name / rde->name_len the same unchecked way.  Impact: a malicious or compromised Ceph MDS overflows the NAME_MAX name buffer in a client's NFS-export get_name path, a slab out-of-bounds write reported by KASAN. Reachable when a CephFS mount is re-exported over NFS.  Add ceph_export_copy_name(), which rejects lengths above NAME_MAX with -ENAMETOOLONG before the copy, and use it in both ceph_get_name() and __get_snap_name().",
                                "cve_priority": "critical",
                                "cve_public_date": "2026-09-11 20:19:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-89680",
                                "url": "https://ubuntu.com/security/CVE-2026-89680",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  nfsd: fix nfsd_file leak on inter-server COPY setup failure  When nfsd4_setup_inter_ssc() fails, nfsd4_copy() returns nfserr_offload_denied directly, bypassing the out: label where release_copy_files() would drop the nf_dst reference taken by nfs4_preprocess_stateid_op(). Each failed inter-server COPY leaks one nfsd_file, pinning file/inode/dentry/vfsmount.  Fix by setting status and jumping to out: instead of returning directly.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-09-11 20:19:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-89761",
                                "url": "https://ubuntu.com/security/CVE-2026-89761",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  apparmor: fix out-of-bounds write when null terminating a label vec  aa_vec_unique() null terminates at vec[n - dups] when VEC_FLAG_TERMINATE is passed. If the components are all distinct no duplicates are dropped, dups is 0 and the terminator goes to vec[n], so the caller has to provide room for n + 1 entries.  aa_label_strn_parse() sets up its vector with vec_setup(profile, vec, len, gfp) and then calls aa_vec_unique(vec, len, VEC_FLAG_TERMINATE), but vec_setup() does not reserve the terminator entry. Up to LOCAL_VEC_ENTRIES it uses the local array of LOCAL_VEC_ENTRIES pointers, above that it allocates exactly len pointers. The terminator therefore lands one entry past the end of the local array when len is LOCAL_VEC_ENTRIES, and one entry past the end of the allocation when len is larger.  len comes from the number of \"//&\" separated components in the label name and label_count_strn_entries() does not bound it. An unprivileged task reaches the parse by writing to /proc/self/attr/apparmor/current or through lsm_set_self_attr(2), both of which go through do_setattr(), and the name is parsed before the change_profile permission is checked. The query_label() path behind the securityfs .access file, which is mode 0666, performs no permission check at all. Every component has to resolve to a loaded profile, so a system with policy loaded is required.  The other two VEC_FLAG_TERMINATE users work on a label vec that aa_label_alloc() has already sized with \"+ 1 for null terminator entry on vec\". Reserve the same entry in vec_setup() and DEFINE_VEC(). Passing len + 1 from the caller instead would move len == LOCAL_VEC_ENTRIES out of the local array and into kzalloc().",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-09-11 20:20:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-80852",
                                "url": "https://ubuntu.com/security/CVE-2026-80852",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  tls: device: fix out-of-bounds write in tls_append_frag()  Found with syzkaller and a local syzbot instance running on top of a netdevsim TLS offload emulation; tls_device.c is otherwise only reachable on a machine with a NIC that implements the offload.  tls_push_data() only checks whether the open record still has room for another frag at the bottom of its loop, and the MSG_MORE early break skips that check.  The record survives to the next syscall with the frag count it already had, and tls_append_frag() does not check either, so with TLS_TX_ZEROCOPY_RO every splice(SPLICE_F_MORE) of a byte or two adds a non-coalescing pipe page and num_frags walks off the end of tls_record_info.frags[MAX_SKB_FRAGS].  Once the record is pushed, tls_push_record() runs the same index over sg_tx_data[MAX_SKB_FRAGS] and the sg_set_page() writes land on the destruct_work that follows it, which the workqueue then calls.  The byte limit is fine because copy drops to 0 and the loop falls through to the same check; the frag count has no such feedback.  Push the record rather than keep a full one open, which is what a plain TCP socket does - tcp_sendmsg_locked() uses tcp_mark_push() and new_segment in both the copy and the MSG_SPLICE_PAGES paths, and tls_sw already sets full_record when the sk_msg ring fills up, MSG_MORE or not.    BUG: KASAN: slab-out-of-bounds in tls_append_frag ( net/tls/tls_device.c:269)   Write of size 8 at addr ffff8881104d1530 by task tls_oob/450    CPU: 2 UID: 0 PID: 450 Comm: tls_oob Not tainted 7.2.0-rc7+ #329 PREEMPT   Call Trace:    <TASK>    dump_stack_lvl (lib/dump_stack.c:94 lib/dump_stack.c:120)    print_report (mm/kasan/report.c:378 mm/kasan/report.c:482)    kasan_report (mm/kasan/report.c:595)    tls_append_frag (net/tls/tls_device.c:269)    tls_push_data (net/tls/tls_device.c:518)    tls_device_sendmsg (net/tls/tls_device.c:583)    inet_sendmsg (net/ipv4/af_inet.c:865)    sock_sendmsg (net/socket.c:775 net/socket.c:790 net/socket.c:813)    splice_to_socket (fs/splice.c:884)    do_splice (fs/splice.c:936 fs/splice.c:1349)    __do_splice (fs/splice.c:1431)    __x64_sys_splice (fs/splice.c:1634 fs/splice.c:1616)    do_syscall_64 (arch/x86/entry/syscall_64.c:63 arch/x86/entry/syscall_64.c:94)    entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:121)    </TASK>  and, once the record is pushed:    UBSAN: array-index-out-of-bounds in net/tls/tls_device.c:300:24   index 18 is out of range for type 'skb_frag_t [17]'   UBSAN: array-index-out-of-bounds in net/tls/tls_device.c:301:41   index 18 is out of range for type 'scatterlist [17]'   UBSAN: array-index-out-of-bounds in net/tls/tls_device.c:302:39   index 18 is out of range for type 'scatterlist [17]'   UBSAN: array-index-out-of-bounds in net/tls/tls_device.c:307:38   index 26 is out of range for type 'scatterlist [17]'    kernel tried to execute NX-protected page - exploit attempt? (uid: 0)   BUG: unable to handle page fault for address: ffffea000411a680   #PF: supervisor instruction fetch in kernel mode   #PF: error_code(0x0011) - permissions violation   Oops: Oops: 0011 [#1] SMP KASAN PTI   Workqueue: ktls_device_destruct 0xffffea000411a680   RIP: 0010:0xffffea000411a680   Call Trace:    <TASK>    worker_thread (kernel/workqueue.c:3405 kernel/workqueue.c:3486)    kthread (kernel/kthread.c:436)    ret_from_fork (arch/x86/kernel/process.c:158)    ret_from_fork_asm (arch/x86/entry/entry_64.S:245)    </TASK>",
                                "cve_priority": "high",
                                "cve_public_date": "2026-09-04 16:18:00 UTC"
                            }
                        ],
                        "log": [
                            "",
                            "  * jammy/linux-kvm: 5.15.0-1113.118 -proposed tracker (LP: #2173211)",
                            "",
                            "  [ Ubuntu: 5.15.0-204.214 ]",
                            "",
                            "  * jammy/linux: 5.15.0-204.214 -proposed tracker (LP: #2173225)",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857)",
                            "    - device property: Add cleanup.h based fwnode_handle_put() scope based",
                            "      cleanup.",
                            "    - device property: fix infinite loop in fwnode_for_each_child_node()",
                            "    - ocfs2: validate dx_root extent list fields during block read",
                            "    - nvme-tcp: validate R2T PDU in nvme_tcp_handle_r2t()",
                            "    - staging: rtl8723bs: fix spacing around operators",
                            "    - Bluetooth: btqcomsmd: Convert to platform remove callback returning void",
                            "    - io_uring/rw: end write accounting from ->ki_complete",
                            "    - ALSA: usb-audio: Optimize the copy of packet sizes for implicit fb",
                            "      handling",
                            "    - ALSA: usb-audio: Clamp implicit feedback packet count to URB capacity",
                            "    - perf tools: Fix a asan issue in parse_events_multi_pmu_add()",
                            "    - perf test bpf: Address error about non-null argument for epoll_pwait 2nd",
                            "      arg",
                            "    - zram: fixup read_block_state()",
                            "    - nfsd: size fh_verify server sockaddr slot by xpt_locallen",
                            "    - nfsd: check nfsd4_acl_to_attr() return value in nfsd4_create()",
                            "    - coresight: etm3x: Fix cntr_val_show() to match cntr_val_store() behavior",
                            "    - kernel/params.c: Use kstrtobool() instead of strtobool()",
                            "    - params: Do not go over the limit when getting the string length",
                            "    - params: Use size_add() for kmalloc()",
                            "    - params: Sort headers",
                            "    - params: Fix multi-line comment style",
                            "    - dmaengine: Add devm_dma_request_chan()",
                            "    - i2c: mxs: fix DMA channel leak on probe error",
                            "    - power: supply: rt9455: Convert to i2c's .probe_new()",
                            "    - i2c: core: Introduce i2c_client_get_device_id helper function",
                            "    - power: supply: max17040: Convert to i2c's .probe_new()",
                            "    - power: supply: max17040: drop incorrect I2C functionality check",
                            "    - hwrng: stm32 - Fix runtime PM cleanup on registration failure",
                            "    - spi: bcm63xx: disable clock on resume failure",
                            "    - staging: sm750fb: fix mono image source stride mismatch in",
                            "      lynxfb_ops_imageblit()",
                            "    - ftrace: Synchronize the initialization of ftrace_ops",
                            "    - arm64: allow pte_offset_map() to fail",
                            "    - mm/mremap: reset unfaulted VMA page offset for MREMAP_DONTUNMAP",
                            "    - media: rkvdec: Propagate platform_get_irq() errors",
                            "    - media: zoran: Avoid freeing a registered video_device twice",
                            "    - scsi: qla2xxx: Fix 64G link speed reporting in get_data_rate",
                            "    - ring-buffer: Acquire the lock with irqsave in rb_wake_up_waiters()",
                            "    - smb: client: fix file type corruption in cifs_reparse_point_to_fattr()",
                            "    - smb: client: avoid leaking refcount when cifs_sb_tlink() fails",
                            "    - watchdog: rtd119x: Use devm_clk_get_enabled() helper",
                            "    - perf/x86/intel: Remove anythread_deprecated bit from perf_capabilities",
                            "    - smb3: make query_on_disk_id open context consistent and move to common",
                            "      code",
                            "    - net: ipconfig: Remove outdated comment and indent code block",
                            "    - pinctrl: sunxi: Refactor register/offset calculation",
                            "    - pinctrl: sunxi: Use devm_clk_get_enabled() helpers",
                            "    - pinctrl: sunxi: keep a shadow copy of the data register output latches",
                            "    - net: ena: Remove autopolling mode",
                            "    - netfilter: nf_tables: set->ops->insert returns opaque set element in",
                            "      case of EEXIST",
                            "    - smb: client: validate POSIX create context length",
                            "    - Bluetooth: btusb: Add IMC Networks QCA9377 to quirks table",
                            "    - HID: core: remove #ifdef CONFIG_PM from hid_driver",
                            "    - HID: hid-alps: use default remove for hid device",
                            "    - HID: hid-alps: Use pm_ptr instead of #ifdef CONFIG_PM",
                            "    - smb/client: use stack-allocated smb2_file_all_info in",
                            "      smb3_query_mf_symlink()",
                            "    - smb/client: pass cifs_open_info_data to SMB2_open()",
                            "    - smb: client: close handle after create-context parsing failure",
                            "    - ALSA: usb-audio: Apply IGNORE_CTL_ERROR quirk to all Audient devices",
                            "    - of/irq: Fix remaining refcount leaks in of_irq_init()",
                            "    - wifi: cfg80211: avoid double free if updating BSS fails",
                            "    - drm/msm/a6xx: Avoid a nullptr dereference when speedbin setting fails",
                            "    - openvswitch: add nf_ct_is_confirmed check before assigning the helper",
                            "    - rds_tcp: close NULL deref window in rds_tcp_set_callbacks",
                            "    - of/irq: add missing of_node_put() for interrupt parent node",
                            "    - ALSA: caiaq: unregister the input device when probe fails",
                            "    - perf/core: Fix WARN in perf_sigtrap()",
                            "    - scsi: qla2xxx: Fix NVMe abort reference leak on repeated abort",
                            "    - mtd: core: clear out unregistered devices a bit more",
                            "    - mtd: core: Drop duplicate NULL checks around nvmem_unregister()",
                            "    - mtd: core: Fix refcount error in del_mtd_device()",
                            "    - mtd: use refcount to prevent corruption",
                            "    - mtd: call external _get and _put in right order",
                            "    - nvmet: preserve device path on allocation failure",
                            "    - of/overlay: don't create \"//\" paths for fragments targeting the root",
                            "    - ASoC: wm8903: Move the DRC QR threshold to the register that holds it",
                            "    - ASoC: codecs: rt274: Fix format setting for 44100 rate",
                            "    - Bluetooth: hci_core: free the HCI ID if naming fails",
                            "    - netfilter: ipset: do not update comments from kernel-side adds",
                            "    - net: systemport: Fix RUNT MIB counter register offset calculation",
                            "    - net/sched: fq_codel: match the no-drop threshold to the packet size",
                            "    - net/sched: sch_codel: match the no-drop threshold to the packet size",
                            "    - tcp: refresh TS.Recent for accepted old ACKs",
                            "    - ipvs: fix missing counter decrement in lblc",
                            "    - ipvs: do not create invisible templates",
                            "    - net: add and use skb_get_hash_net",
                            "    - i2c: at91: release DMA channels when probe defers",
                            "    - PCI: Accept AtomicOps already enabled by the hypervisor",
                            "    - drm/radeon: Read the VRAM VBIOS signature with readb()",
                            "    - kgdboc: Fix tty driver reference leak in configure_kgdboc()",
                            "    - Input: atkbd - skip deactivate for Lenovo IdeaPad Slim 3 15IWC11",
                            "    - Input: i8042 - add nomux quirk for Fujitsu LIFEBOOK U7410",
                            "    - Input: synaptics - add LEN205b entry to smbus_pnp_ids for ThinkPad T490",
                            "    - Input: synaptics - limit T440p InterTouch quirk to LEN0036",
                            "    - USB: cdc-acm: fix racy TIOCMIWAIT implementation",
                            "    - usb: hub: use shorter 120ms post resume hold for SS root hubs",
                            "    - usb: ohci-da8xx: disable controller wakeup on cleanup",
                            "    - usb: ohci-s3c2410: disable controller wakeup on removal",
                            "    - usb: ohci-st: disable controller wakeup on removal",
                            "    - usb: typec: ucsi: Get the connector fwnode based on reg value",
                            "    - usb: typec: ucsi: displayport: Current CAM OOB index fixup",
                            "    - tty: amiserial: fix broken TIOCMIWAIT",
                            "    - tty: serial: qcom_geni_serial: Keep console RX functional after deep",
                            "      idle",
                            "    - serial: tegra: don't clear the Tx FIFO on an Rx-only reset",
                            "    - serial: vt8500: Fix clock reference leak in vt8500_serial_probe()",
                            "    - Bluetooth: hci_core: Fix inquiry cache timestamps on 64-bit systems",
                            "    - mtd: rawnand: vf610_nfc: fix reads on chips with more than 64 bytes of",
                            "      OOB",
                            "    - mtd: spinand: fix zero oobavail when no ECC engine is used",
                            "    - USB: serial: cp210x: add Corsair AX1500i Power Supply",
                            "    - USB: serial: quatech2: fix baud rate overflow",
                            "    - USB: serial: ssu100: fix baud rate overflow",
                            "    - USB: serial: option: add support for SIMCom SIM8260C",
                            "    - USB: serial: option: add Quectel EG060W",
                            "    - USB: serial: option: add Compal EXM-G1x support",
                            "    - USB: serial: option: add Quectel RG660QB",
                            "    - USB: serial: option: add Compal EXC-T1 support",
                            "    - iio: accel: sca3000: fix frequency divider condition check",
                            "    - iio: adc: sun4i-gpadc-iio: drop underflowing pm_runtime_put() calls",
                            "    - iio: proximity: isl29501: Fix return type of isl29501_register_write",
                            "    - iio: proximity: vcnl3020: fix ISR bitmask check in IRQ handler",
                            "    - iio: trigger: cancel reenable_work before freeing trigger",
                            "    - Revert \"scsi: sd: sd_zbc: Use logical blocks as unit when querying",
                            "      zones\"",
                            "    - SUNRPC: fix gssx_dec_option_array error path bugs",
                            "    - vc_screen: reload vc pointer before if (ret) in vcs_write() to avoid UAF",
                            "    - mtd: rawnand: vf610_nfc: fix false bitflips on reads of erased pages",
                            "    - wifi: wl12xx: Drop if with an always false condition",
                            "    - wifi: wlcore: Convert to platform remove callback returning void",
                            "    - wifi: wlcore: Fix runtime PM leak in wlcore_remove()",
                            "    - net: usb: qmi_wwan: add Quectel EG120K-EA",
                            "    - serial: imx: Convert to platform remove callback returning void",
                            "    - usb: gadget: at91_udc: Convert to platform remove callback returning",
                            "      void",
                            "    - usb: typec: tcpm: fix debug accessory mode detection for sink ports",
                            "    - usb: typec: tcpm: constrain TCPM_SOURCING_VBUS event handling",
                            "    - drm/amd/pm/si: Check AMD_IS_MOBILITY flag for PPSMC_SYSTEMFLAG_GPIO_DC",
                            "    - soc: qcom: geni-se: Correct QUP Core ICC vote constants",
                            "    - usb: dwc3: gadget: fix IRQ storm on invalid event buffer count",
                            "    - arm64: errata: Factor out broken AMU const counter cap",
                            "    - [Config] enable ARM64_WORKAROUND_BROKEN_AMU_CONSTCNT",
                            "    - arm64: errata: Add Cortex-A725 erratum 3821522 workaround",
                            "    - [Config] arm64: errata: Add Cortex-A725 erratum 3821522 workaround",
                            "    - iio: buffer: serialize buffer teardown with mode claims",
                            "    - KVM: arm64: Don't use the VMA to size stage-2 block mappings for",
                            "      VM_PFNMAP",
                            "    - fsverity: add dependency on 64K or smaller pages",
                            "    - drm/amd/display: check dc_state_create_copy() for NULL in dm_suspend",
                            "    - drm/amd/pm/si: Fix updating clock limits on AC/DC",
                            "    - drm/amdgpu: reset VI ASIC on MacBookPro15,1",
                            "    - drm/amdgpu: reset VI ASIC on MacBookPro14,3",
                            "    - drm/amdgpu: fix for coding style issues",
                            "    - usb: octeon-hcd: fix the FIFO-flush timeout computation",
                            "    - usb: ohci-spear: Remove unnecessary NULL check before",
                            "      clk_disable_unprepare()",
                            "    - usb: ohci-spear: disable controller wakeup on removal",
                            "    - usb: typec: ucsi: acpi: Assume UCSI 1.2 on Acer Nitro ANV15-41",
                            "    - tty: reformat kernel-doc in tty_io.c",
                            "    - Input: s6sy761 - fix resume ordering and restore sensing",
                            "    - tty: vt: fix memory leak in vc_allocate()",
                            "    - serial: fix TIOCMIWAIT race",
                            "    - drm/amd/display: Mark DCE 6.4 as not APU",
                            "    - mtd: spinand: Enable QE on all dies",
                            "    - USB: serial: clean up core error labels",
                            "    - tty: introduce and use tty_port_tty_vhangup() helper",
                            "    - mm/hugetlb: fix avoid_reserve to allow taking folio from subpool",
                            "    - iio: adc: aspeed: propagate reset deassert errors",
                            "    - iio: adc: max1363: sign-extend bipolar differential channel reads",
                            "    - HID: core: introduce hid_safe_input_report()",
                            "    - HID: uhid: convert to hid_safe_input_report()",
                            "    - crypto: drbg - Fix ineffective sanity check",
                            "    - ipv4: stop PMTU walk when nexthop group shrinks",
                            "    - Revert \"wifi: libertas: reject short monitor TX frames\"",
                            "    - sctp: copy zeroed stats to user in sctp_getsockopt_pr_streamstatus()",
                            "      when !streamoute",
                            "    - keys: finalize persistent keyring timeout after link attempt",
                            "    - dm-snap: reject the transient exception store for snapshot-merge",
                            "    - mmc: cavium-octeon: destroy slot platform devices on remove",
                            "    - mmc: cavium-thunderx: destroy slot platform devices on remove",
                            "    - net: usb: ax88179_178a: fix rx frame length for non-last packets",
                            "    - nvme: fix swapped ZRASF zone state values for full and read only",
                            "    - scsi: qedi: Initialize callback state before registration",
                            "    - drm/gud: don't keep a connector without a CRTC as connector_state",
                            "    - drm/amdgpu: make Mac FB workaround generic",
                            "    - fs: refuse fspick() on internal superblocks",
                            "    - drm/dp: don't mark the AUX backlight enabled when enabling failed",
                            "    - drm/aspeed: Balance the display clock enable on teardown",
                            "    - ASoC: adau1372: fix invalid default state of output ASRC and DAC muxes",
                            "    - net/mlx5e: Order ICOSQ cc update after CQ doorbell",
                            "    - mtd: fix use-after-free in mtd release",
                            "    - mtd: Clean refcounting with MTD_PARTITIONED_MASTER",
                            "    - mtd: maps: vmu-flash: Fix the (mtd core) switch to ref counters",
                            "    - mtd: fix double free and WARN_ON in add_mtd_device() error paths",
                            "    - dlm: validate length in dlm_search_rsb_tree",
                            "    - openvswitch: vport: fix self-deadlock on release of tunnel ports",
                            "    - smb: client: reject short Next offsets in parse_server_interfaces()",
                            "    - can: fix unique skb identifier regression under RPS",
                            "    - drm/amd/display: Don't replace a sink mode that shares the native totals",
                            "    - HID: hid-steam: Fix cleanup in probe()",
                            "    - HID: hid-steam: Make client_opened a counter",
                            "    - HID: steam: Fully unregister controller when hidraw is opened",
                            "    - HID: steam: Clean up locking",
                            "    - selinux: fix data race on AVC latest_notif",
                            "    - EDAC/amd64: Mask UMC chip select to the four implemented selects",
                            "    - mm/mremap: fix locked_vm leak by splitting VMA for MREMAP_DONTUNMAP",
                            "    - mm/mremap: fix locked_vm leak from MREMAP_DONTUNMAP self-merge",
                            "    - netfilter: nf_tables: fix bidirectional offload regression",
                            "    - net: team: Remove unused team_mode_op, port_enabled",
                            "    - net: team: Rename port_disabled team mode op to port_tx_disabled",
                            "    - Bluetooth: RFCOMM: connect the session socket without rfcomm_mutex",
                            "    - pmdomain: rockchip: fix clock leak on domain probe failure",
                            "    - pmdomain: rockchip: don't ignore clock lookup errors on attach",
                            "    - pmdomain: rockchip: propagate subdomain add errors",
                            "    - drm/amdgpu: copy debugfs register data outside the GRBM/SRBM locks",
                            "    - namespace: check the target before walking it in do_mount_setattr()",
                            "    - fcntl: refuse F_SET_RW_HINT on an immutable inode",
                            "    - netfilter: nf_tables: fix crash when nf_trace is enabled",
                            "    - tty: finish kernel-doc of tty_struct members",
                            "    - tty: add break_wait kernel-doc",
                            "    - xfrm: prevent policy_hthresh.work from racing with netns teardown",
                            "    - xfs: log items should have a xlog pointer, not a mount",
                            "    - xfs: aborting inodes on shutdown may need buffer lock",
                            "    - xfs: fix super block buf log item UAF during force shutdown",
                            "    - xfs: buffer pins need to hold a buffer reference",
                            "    - xfs: xfs_ifree_cluster vs xfs_iflush_shutdown_abort deadlock",
                            "    - xfs: catch stale AGF/AGF metadata",
                            "    - xfs: rearrange code in xfs_buf_item.c",
                            "    - xfs: factor out stale buffer item completion",
                            "    - xfs: fix unmount hang with unflushable inodes stuck in the AIL",
                            "    - power: supply: ds2780: Fix ds2780_get_capacity() returning raw value",
                            "    - ASoC: stm32: spdifrx: fix synchronization state check",
                            "    - ASoC: cs42l56: Put the Limiter Cushion control on the limiter register",
                            "    - ASoC: cs42l52: Fix the NG Type Switch bit",
                            "    - ASoC: pcm3168a: Fix the DAC zero flag polarity bit",
                            "    - ASoC: max98371: Fix the Speaker DHT Min Volume bits",
                            "    - ASoC: wm8978: Fix the 128x oversampling switch bits",
                            "    - ASoC: nau8822: Fix the 128x oversampling switch bits",
                            "    - netlink: remove netlink_broadcast_filtered",
                            "    - netlink: Reverse the patch which removed filtering",
                            "    - nios2: fix __wsum type degradation in csum_fold()",
                            "    - scsi: st: Save the visited block for the partition the drive is in",
                            "    - samples: pidfd: fix userprogs typo",
                            "    - clone: add CLONE_AUTOREAP",
                            "    - exit: fix lost-update race on the child_subreaper bitfields",
                            "    - tools: gpio: fix building from the top level with O=",
                            "    - i2c: qcom-cci: Fix HALT_ACK reset request being dropped",
                            "    - drm/amdgpu/sdma3: Work around POLL_REGMEM / FENCE hang",
                            "    - tracing: Fix the shift out of bounds in the log2 histogram modifier",
                            "    - cgroup: fix spurious SIGKILL of CLONE_INTO_CGROUP children",
                            "    - dm cache: fix demotion stats in passthrough mode",
                            "    - dm cache: fix issue with background work locking",
                            "    - dm-ebs: fix incorrect device offset check in ebs_ctr()",
                            "    - tipc: protect node reset trace dump with node lock",
                            "    - drm/amdgpu: Fix VCE 3 ring align_mask",
                            "    - KVM: x86/mmu: Preserve nested TDP shadow page tables if they are used as",
                            "      roots",
                            "    - tracing/histograms: Reject non-stacktrace fields for synthetic",
                            "      stacktrace fields",
                            "    - dm-integrity: require stable writes for internal hash modes",
                            "    - cifs: add revalidation on FSCTL failure in smb2_duplicate_extents()",
                            "    - SAUCE: Revert \"md: move initialization and destruction of 'io_acct_set'",
                            "      to md.c\"",
                            "    - md: move initialization and destruction of 'io_acct_set' to md.c",
                            "    - net_sched: codel: fix stale state for empty flows in fq_codel",
                            "    - Bluetooth: L2CAP: access chan->conn safely in get/setsockopt",
                            "    - Bluetooth: L2CAP: refuse __l2cap_chan_add if chan already has conn",
                            "    - tracing: Reject incomplete event filter expressions",
                            "    - tracing: Save the event file instead of the compatible histogram",
                            "    - tracing: Unregister field variable histograms when the command fails",
                            "    - tracing: Fix 64-bit and signed histogram fields on 32-bit kernels",
                            "    - keys: Avoid the owner account dereference in named keyring lookup",
                            "    - keys: Check the authorization payload in process keyring searches",
                            "    - keys: Protect the type name while describing a key",
                            "    - keys: make keyring indexes independent of kernel addresses",
                            "    - keys: Protect the read method check against type removal",
                            "    - KEYS: Fix key_reject_and_link() race with keyring restriction",
                            "    - KEYS: trusted: Fix blob allocation size in tpm2_key_decode()",
                            "    - keys/trusted_keys: return immediately after TPM unseal failure",
                            "    - io-wq: order the exit bit against worker creation task work",
                            "    - signal: don't retarget shared signals in a dying thread group",
                            "    - Linux 5.15.224",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99115",
                            "    - ksmbd: fill in FileSysIdentifier in FS_POSIX_INFORMATION",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99113",
                            "    - ksmbd: zero the FS_OBJECT_ID_INFORMATION buffer before filling it in",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99114",
                            "    - ksmbd: initialize FileSystemControlFlags in FS_CONTROL_INFORMATION",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99132",
                            "    - xfs: don't hold buffer locks across sync transaction commit in",
                            "      xfs_sync_sb_buf",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99135",
                            "    - dm-integrity: fix infinite loop on discard with large tag size",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99118",
                            "    - drm/i915/dmc: Harden DMC firmware payload parsing",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99169",
                            "    - futex: Fix mm reuse handling for FUT_OFF_MMSHARED",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99161",
                            "    - i2c: viai2c-wmt: Fix clock leak in wmt_i2c_probe()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99077",
                            "    - ipv4: udp: Create exceptions before socket matching",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99123",
                            "    - vsock/virtio: validate packet source for connected sockets",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-89987",
                            "    - mm/huge_memory: transfer the pmd dirty bit to the folio on zap",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-80572",
                            "    - Input: byd - synchronize timer deletion before freeing private data",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99180",
                            "    - unicode: free the map after a grace period",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99179",
                            "    - watch_queue: Fix note pool publication race in watch_queue_set_size()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-89912",
                            "    - KVM: arm64: vgic-its: Don't dereference a NULL collection on ITT save",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99156",
                            "    - scsi: st: Fix use-after-free race between st_remove() and st_open()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99112",
                            "    - net/sched: cls_flower: validate mask pointer after nla_next()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99117",
                            "    - net: bridge: mcast: don't truncate the port group walk on teardown",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-74405",
                            "    - OPP: Fix race between OPP addition and lookup",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-74739",
                            "    - net/sched: cls_u32: skip hash tables in u32_bind_class()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-64015",
                            "    - security/keys: fix missed RCU read section on lookup",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-74672",
                            "    - mm/vmalloc: acquire init_mm lock on huge vmap to avoid ptdump UAF",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99121",
                            "    - ipv4: avoid divide by zero in fib_rebalance",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99124",
                            "    - s390/pci: Fix leak of uninitialized kernel data in SCLP report",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99126",
                            "    - s390/ctcm: Prevent XID null dereference",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99127",
                            "    - page_pool: keep frag_offset aligned for odd-sized requests",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99128",
                            "    - sctp: validate chunk length in the inqueue parser",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99133",
                            "    - net/iucv: fix the recvmsg window update",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99136",
                            "    - dm-crypt: fix a tiny race condition in crypt_dec_pending",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99138",
                            "    - tcp: fix use-after-free in do_tcp_getsockopt(TCP_CC_INFO)",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99100",
                            "    - wifi: p54: validate firmware record lengths",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99140",
                            "    - tracing: Fix hist trigger timestamps for buffered events",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99150",
                            "    - drm/amdgpu: don't drop the runtime PM reference twice in amdgpu_gpr",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99152",
                            "    - scsi: libiscsi: Validate the task named by a management response",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99153",
                            "    - scsi: libiscsi: Validate the ITT reflected in a Reject PDU",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99154",
                            "    - scsi: libiscsi: Reject a negative task index from parse_pdu_itt",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99165",
                            "    - sctp: revalidate output stream after association connect wait",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99166",
                            "    - net: rds: fix uninitialized trans dereference in CM event handler",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99167",
                            "    - net/sched: fix use-after-free in __tcf_action_put()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99175",
                            "    - fsnotify: prevent mark additions during connector teardown",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99176",
                            "    - KVM: nVMX: Reset MMU back to the root MMU if loading L2 state fails for",
                            "      !VM-Entry",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99181",
                            "    - autofs: ignore notification errors from a replaced pipe",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99201",
                            "    - netlink: avoid hashing the network namespace pointer",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99203",
                            "    - pipe: preserve existing fasync readers on writer setup failure",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99204",
                            "    - ocfs2/dlm: Protect the recovery list during debugfs reads",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99206",
                            "    - scsi: target: iscsi: Fix race in discovery auth updates",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99211",
                            "    - netlink: reset skb headers before unicast and multicast filtering",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99212",
                            "    - net/rds: don't let the rdma_cm destroy an id RDS still owns on route",
                            "      failure",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99213",
                            "    - vsock: treat TCP_CLOSING as once-established",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99216",
                            "    - Drivers: hv: Don't reset VMBus connection state on error/exit paths",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2022-50167",
                            "    - bpf: fix potential 32-bit overflow when accessing ARRAY map element",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99082",
                            "    - KVM: x86: Use active memslots for the per-vCPU MMIO cache",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99083",
                            "    - ksmbd: fix heap out-of-bounds write in krb5_authenticate()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98977",
                            "    - namespace: handle mount locking for automounts correctly",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98992",
                            "    - namespace: don't copy an unmounted mount tree",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98981",
                            "    - namespace: unhash a dentry before detaching the mounts on it",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99005",
                            "    - drm/i915/gt: Unmask interrupts only when ACTIVE is true",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99007",
                            "    - drm/fb-helper: defer setup when fbdev_probe() fails, not just on -EAGAIN",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99019",
                            "    - scsi: ch: Do not keep references to data transfer element devices",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99024",
                            "    - optee: register TEE devices only once fully initialized",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99036",
                            "    - dm: fix reading free memory in do_resume",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98985",
                            "    - namespace: check the mounts before reading their parents in pivot_root()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98993",
                            "    - namespace: don't inherit MNT_UMOUNT in clone_mnt()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99002",
                            "    - drm/vmwgfx: validate pitch coming from userspace",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99027",
                            "    - net: team: stop reusing skb after queue override",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-64190",
                            "    - net: team: fix NULL pointer dereference in team_xmit during mode change",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99041",
                            "    - ip6_gre: remove obsolete ERSPAN PMTU update",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-97935",
                            "    - tracing: Set the trace clock before registering the histogram trigger",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98944",
                            "    - HID: steam: Refactor registration",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98945",
                            "    - HID: steam: Rearrange teardown sequence",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2025-40135",
                            "    - ipv6: use RCU in ip6_xmit()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2025-38728",
                            "    - smb3: fix for slab out of bounds on mount to ksmbd",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-31678",
                            "    - openvswitch: defer tunnel netdev_put to RCU release",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99088",
                            "    - net: openvswitch: validate transport header presence in set_ipv6_addr",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98950",
                            "    - flow_dissector: avoid u16 truncation of hlen in bpf_flow_dissect()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98955",
                            "    - flow_dissector: avoid u16 truncation of skb->len when computing thoff",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99089",
                            "    - ASoC: samsung: i2s: enable op_clk in probe to balance runtime PM",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98956",
                            "    - ASoC: adau1372: allow sleepy powerdown GPIOs",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98964",
                            "    - nvmet: use the local P2P device on metadata allocation failure",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98967",
                            "    - cxgb4/ch_ktls: disable softirqs around tid_list erases",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98969",
                            "    - net/sched: em_text: reject unterminated algo before autoload",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98970",
                            "    - drm/vc4: Free the BO cache size list on teardown",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98971",
                            "    - gpio: exar: initialize the ID before registering its cleanup",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98979",
                            "    - namespace: refuse an automount below a mount that is in no namespace",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98984",
                            "    - dcache: don't put a mountpoint on a dentry that's being removed",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98990",
                            "    - namespace: check a submount for references right before unmounting it",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99095",
                            "    - drm/vc4: drain the hangcheck timer and works on V3D unbind",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99006",
                            "    - drm/i915/gem: Prevent overstepping exec array boundary",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99008",
                            "    - Bluetooth: RFCOMM: Fix NULL tty_dev dereference in rfcomm_dev_shutdown",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99010",
                            "    - Bluetooth: RFCOMM: free the skb when the DLC has no owner",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99015",
                            "    - Bluetooth: hci_sock: Serialize dead-device detachment",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99022",
                            "    - regulator: ltc3676: don't read the write-only HRST and CLIRQ registers",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99025",
                            "    - openvswitch: fix soft lockup in the netlink flow dump",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99031",
                            "    - net: bridge: avoid recursive multicast port cleanup",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99032",
                            "    - net/smc: protect clcsock lifetime in smc_getname",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99033",
                            "    - net/packet: guard the ll header push in packet_rcv_spkt()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99034",
                            "    - mmc: sdhci-sprd: disable runtime PM on remove",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99035",
                            "    - mmc: mtk-sd: Cancel request timeout work on remove",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99037",
                            "    - dm-crypt: reject the lmk IV mode with AEAD ciphers",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99038",
                            "    - memstick: rtsx_usb_ms: complete requests after eject instead of dropping",
                            "      them",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99039",
                            "    - memstick: core: wait for request completion before freeing card",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99040",
                            "    - KEYS: Fix add_key() race with keyring restriction",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99045",
                            "    - ibmveth: h_free logical LAN on open-fail after register",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99049",
                            "    - gpio: xilinx: fix runtime PM leak on request error path",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99052",
                            "    - selinux: preserve NATIVE_LABELS on already-initialized sb in",
                            "      set_mnt_opts",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99053",
                            "    - tipc: hold a reference to nodes found by link name",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99054",
                            "    - tipc: destroy topsrv workqueues before closing connections",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99056",
                            "    - strparser: make sure __strp_recv isn't running before tearing down the",
                            "      parser",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99057",
                            "    - xen/netfront: don't leak the skb when xennet_fill_frags() fails",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99058",
                            "    - workqueue: Fix NULL current_pwq deref in chained work check",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99059",
                            "    - wireguard: noise: reject response consumption after intermediate",
                            "      initiation",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99061",
                            "    - wifi: brcmfmac: fix P2P device removal race in brcmf_detach()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99063",
                            "    - dm ioctl: don't let data_start run past the buffer",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99067",
                            "    - btrfs: scrub: fix local_root reference leak in",
                            "      scrub_print_warning_inode()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99070",
                            "    - ipv6: do not warn on route notification size race",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99071",
                            "    - ipv4: do not warn on route notification size race",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99072",
                            "    - ipv4: stop route notification sizing when nexthop group shrinks",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98686",
                            "    - smb: client: discard post-EOF pagecache when extending a file via zero",
                            "      range",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98700",
                            "    - wifi: mac80211: set info->band for 802.3 encap offload frames",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98716",
                            "    - KVM: SVM: Use the active VMCB's MSR bitmap when checking if MSR is",
                            "      intercepted",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99080",
                            "    - fs: Free any excess xarray nodes in clear_inode()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98709",
                            "    - wifi: mac80211: count only matching reservations in reserved switch",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98708",
                            "    - wifi: mac80211: keep paired old chanctx alive",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98752",
                            "    - tty: port: fix tty_port_tty_vhangup() race",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99081",
                            "    - bnxt_en: fix DMA mapping length for padded small packets",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98696",
                            "    - USB: serial: fix driver deregistration order",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98705",
                            "    - wifi: mac80211: account proxy paths against the mesh path limit",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98722",
                            "    - mtd: block2mtd: Fix divide error when erase_size is zero",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98695",
                            "    - USB: serial: fix ioctl hangup race",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98694",
                            "    - thunderbolt: Fix KASAN reported use-after-free when request is canceled",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98704",
                            "    - wifi: mac80211: keep fallback association elements alive",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98707",
                            "    - wifi: mac80211: shut down RX BA session timer on teardown",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98749",
                            "    - tty: serial: max3100: shut down timer before freeing port",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98751",
                            "    - tty: abort break signalling on hangup",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98753",
                            "    - tty: tty_port: restore TTY_IO_ERROR on activation failure",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98762",
                            "    - USB: dwc2: shut down wakeup timer before freeing HCD state",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98784",
                            "    - drm/amdgpu/gfx6: fix firmware leak on teardown",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98779",
                            "    - drm/amdgpu: fix ACP MFD device leak on init failure",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98742",
                            "    - ALSA: seq: Serialize compat port-info ioctls",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98655",
                            "    - perf: Require kernel access for text poke events",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98750",
                            "    - tty: fix saved termios reset race",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-89638",
                            "    - smb: client: clear setuid/setgid bit on write with",
                            "      cifsacl/modefromsid/posix extensions",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98375",
                            "    - xen/netfront: drop RX packets with a short Ethernet header",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-89738",
                            "    - usb: gadget: at91_udc: drain polled-VBUS timer/work before udc is freed",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-89740",
                            "    - serial: imx: serialize imx_uart_ports[] lifetime",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-74341",
                            "    - wifi: wcn36xx: fix heap overflow from oversized firmware HAL response",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-74406",
                            "    - vxlan: Fix potential null-ptr-deref in vxlan_gro_prepare_receive().",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-46265",
                            "    - RDMA/hns: Fix WQ_MEM_RECLAIM warning",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98681",
                            "    - smb: client: split cifsFileInfo bitfields to avoid shared-byte RMW races",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-89539",
                            "    - SUNRPC: reject duplicate CREDS_VALUE options",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-93179",
                            "    - drm/amd/powerplay: fix VoltageObjectInfo zero-stride loop and OOB read",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2023-52561",
                            "    - arm64: dts: qcom: sdm845-db845c: Mark cont splash memory region as",
                            "      reserved",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2023-53651",
                            "    - Input: exc3000 - properly stop timer on shutdown",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2023-53733",
                            "    - net: sched: cls_u32: Undo tcf_bind_filter if u32_replace_hw_knode",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98657",
                            "    - iio: proximity: pulsedlight: fix iio_device left registered on PM setup",
                            "      failure",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98662",
                            "    - iio: light: gp2ap020a00f: drain irq_work after free_irq",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98663",
                            "    - iio: imu: adis16480: fix unprotected debugfs reads",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98664",
                            "    - iio: imu: adis16400: fix unprotected debugfs reads",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98666",
                            "    - iio: gyro: adis16136: fix unprotected debugfs reads",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98671",
                            "    - iio: adc: sun4i-gpadc-iio: clean up on thermal zone registration failure",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98679",
                            "    - iio: accel: kxcjk-1013: reject duplicate event disable",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98687",
                            "    - thunderbolt: Reject oversized XDomain properties responses",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98697",
                            "    - USB: serial: fix dynamic id driver deregistration race",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98698",
                            "    - wifi: mac80211: handle empty FILS association request payload",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98701",
                            "    - wifi: mac80211: release mesh path quota on failed additions",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98703",
                            "    - wifi: mac80211: minstrel_ht: validate fixed rate index",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98706",
                            "    - wifi: mac80211: drain PS delivery work during station teardown",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98710",
                            "    - wifi: iwlegacy: 3945: free EEPROM data on remove",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98711",
                            "    - wifi: cw1200: fix TX padding OOB read leaking heap data to device",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98721",
                            "    - mtd: rawnand: cadence: Initialize IRQ state before requesting IRQ",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98726",
                            "    - nvme-multipath: fix underflow in ANA log bounds checks",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98856",
                            "    - kprobes: Skip disarmed probes when checking optkprobe overlap",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98857",
                            "    - ipvs: bound LBLCR and LBLC cache growth",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98732",
                            "    - Bluetooth: btintel: fix buffer over-read in btintel_hw_error()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98735",
                            "    - Bluetooth: hci_core: Serialize ACL scheduling with channel deletion",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98739",
                            "    - Bluetooth: RFCOMM: Fix initial port reference race",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98741",
                            "    - ALSA: ua101: reject mismatched capture/playback packet sizes",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98940",
                            "    - ASoC: qcom: lpass-cpu: use DAI table index for playback constraints",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98748",
                            "    - serial: 8250_bcm7271: fix use-after-free in brcmuart_remove()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98754",
                            "    - tty: vcc: hold port lock when clearing tty pointer in vcc_cleanup",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98755",
                            "    - tty: vcc: zero-initialize control packet in vcc_send_ctl()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98756",
                            "    - usb: cdns3: Fix NULL pointer dereference in cdns3_pci_probe",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98757",
                            "    - usb: cdns3: fix use-after-free in cdns3_gadget_exit()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98760",
                            "    - usb: typec: tipd: fix uninitialized typec_partner_desc in",
                            "      tps6598x_connect()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98761",
                            "    - usb: typec: tcpm: recover after failure to start the frs ams",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98763",
                            "    - usb: core: clear both ep_in and ep_out for non-ep0 control endpoints",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98764",
                            "    - usb: gadget: f_fs: Fix NULL pointer dereference in",
                            "      FUNCTIONFS_ENDPOINT_DESC",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98765",
                            "    - USB: gadget: dummy-hcd: Fix wait for outstanding request completions",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98766",
                            "    - usb: gadget: aspeed-vhub: cancel wake work on device removal",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98769",
                            "    - usb: gadget: f_uac1_legacy: validate bRequest index in",
                            "      generic_{set,get}_cmd",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98771",
                            "    - usb: storage: sierra_ms: reject short SWoC info transfers",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98772",
                            "    - USB: serial: fix port tear down use-after-free",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98775",
                            "    - nitro_enclaves: fix use-after-free on SLOT_ALLOC failure",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98790",
                            "    - perf: Fix race between perf_event_exit_task() and perf_pending_task()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98934",
                            "    - ipv6: sr: use skb_get_hash_net() in seg6_make_flowlabel()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2022-49622",
                            "    - netfilter: nf_tables: avoid skb access on nf_stolen",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98794",
                            "    - ipvs: filter some flags received in the backup server",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98805",
                            "    - tipc: prevent GCM nonce reuse on peer key changes",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98811",
                            "    - net/sched: cls_api: reclaim an empty proto on the error path",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98812",
                            "    - net/mctp: publish the mctp_dev only after it is initialised",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98819",
                            "    - Bluetooth: btintel: validate DDC record lengths",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98823",
                            "    - wifi: cfg80211: preserve hidden-group beacon IE ownership",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98936",
                            "    - wifi: ath11k: reset ar->num_stations on hardware start",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98831",
                            "    - of/overlay: don't leak fragment references when changeset init fails",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98833",
                            "    - mtd: core: call _get_device() with the master MTD",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-89860",
                            "    - scsi: qla2xxx: Initialize NVMe abort_work once at submission",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-53353",
                            "    - hsr: Remove WARN_ONCE() in hsr_addr_is_self().",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98836",
                            "    - ALSA: line6: reject oversized playback packets",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98838",
                            "    - vt: skip screen update for DEC alignment test on backgroup consoles",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98568",
                            "    - vxlan: use one headroom snapshot for neighbour replies",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2024-49901",
                            "    - drm/msm/adreno: Assign msm_gpu->pdev earlier to avoid nullptrs",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98846",
                            "    - sctp: check RCV_SHUTDOWN after the sendmsg connect wait",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98847",
                            "    - rtc: spear: initialize IRQ state before requesting alarm IRQ",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98850",
                            "    - net/packet: prevent TX_RING byte count overflow",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98851",
                            "    - netfilter: nft_flow_offload: drop flowtable reference on init error path",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98854",
                            "    - of/overlay: only treat a positive changeset id as registered",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98855",
                            "    - of/overlay: put property on deadprops only after changeset add succeeds",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98862",
                            "    - audit: fix exe mark UAF in kill_rules()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98450",
                            "    - smb: client: close completed creates on compound wait errors",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98502",
                            "    - HID: alps: unregister DualPoint Stick input device on remove",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98456",
                            "    - Bluetooth: mgmt: fix race in read_unconf_index_list()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98451",
                            "    - smb: client: use finish_no_open() for non-regular inodes",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98484",
                            "    - netfilter: nf_tables: skip expired catchall elements on insert and",
                            "      delete",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98486",
                            "    - net: ena: fix MMIO read buffer leak on probe failure",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98493",
                            "    - net: ipconfig: bound DHCP option construction",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98454",
                            "    - smb: client: fix create context out-of-bounds reads",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98490",
                            "    - net: openvswitch: conntrack: fix helper UAF due to extensions realloc",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98507",
                            "    - mm/rmap: fix missing barrier between anon_vma init and vma->anon_vma",
                            "      publish",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98519",
                            "    - drm/amdgpu: Fix runtime PM leak in amdgpu_debugfs_test_ib_show()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98549",
                            "    - tcp: prevent collapsing skbs across boundary in rtx queue",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98544",
                            "    - bna: prevent IOC timer rearm during teardown",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98172",
                            "    - smb: client: fix smbd_connection leak on cifs_get_tcp_session() error",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98192",
                            "    - wifi: wcn36xx: Fix potential use-after-free in TX ack timer teardown",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98198",
                            "    - hwmon: (pwm-fan) Stop RPM timer before freeing tach data",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98409",
                            "    - watchdog: rtd119x: Avoid division by zero",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98245",
                            "    - btrfs: take commit root semaphore when iterating in",
                            "      mark_block_group_to_copy()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98264",
                            "    - ALSA: virtio: reset device before deleting virtqueues",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-97558",
                            "    - smb: client: fix cifsFileInfo reference leak in deferred close",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-97616",
                            "    - net/sched: act_api: release all action references on NEWACTION failure",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-97939",
                            "    - ipmr: account multicast table and route memory",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-89837",
                            "    - f2fs: fix dentry folio leak in find_in_level",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-89838",
                            "    - f2fs: limit recovery filename logging to stored length",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-97530",
                            "    - scsi: qla2xxx: Fix soft lockup polling continuation IOCB signature",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98386",
                            "    - scsi: qla2xxx: Use memset_io() to clear QLAFX00 request ring slot",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-89848",
                            "    - scsi: qla2xxx: Quiesce response IRQ before freeing request queue",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-97532",
                            "    - scsi: qla2xxx: Null out freed pointers in qla2x00_mem_alloc() error path",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-89877",
                            "    - media: saa7164: fix cleanup on resource allocation failure",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-93239",
                            "    - arm64: mm: Fix the lockless page-table walk in show_pte()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-90023",
                            "    - usb: gadget: f_mass_storage: fix null pointer dereference in",
                            "      fsg_common_set_num_buffers()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-93200",
                            "    - i3c: master: Fix use-after-free of master->this",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-93199",
                            "    - i3c: master: Do not treat master device as a duplicate target",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-89441",
                            "    - mmc: via-sdmmc: cancel card-detect work on remove",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-89465",
                            "    - power: supply: rt9455: quiesce delayed work before teardown",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-93231",
                            "    - lockd: fix swapped arguments in nlmsvc_match_ip()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-89552",
                            "    - params: fix charp corruption on allocation failure",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-89640",
                            "    - cifs: fix loff_t underflow in cifs_remap_file_range() when len == 0",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-89672",
                            "    - nfsd: gate nfs2 setacl by argp->mask",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-89685",
                            "    - nfsd: fix clock domain mismatch in clients_still_reclaiming()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-89707",
                            "    - nfsd: release path refs on follow_down() error",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-89719",
                            "    - zram: fix out-of-bounds access in read_block_state()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-89763",
                            "    - KEYS: trusted: Fix TPM teardown ordering",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-80851",
                            "    - gtp: serialize PDP context updates",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-80861",
                            "    - usb: xhci: bail out of setup if the controller is inaccessible",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98377",
                            "    - vlan: require the MAC header to be present in __vlan_insert_inner_tag()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98170",
                            "    - smb: client: fix OOB struct field reads in move_smb2_ea_to_cifs()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98171",
                            "    - smb: client: fix next_buffer UAF and NextCommand bounds in compound PDUs",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98169",
                            "    - smb: client: fix potential OOB read in smb3_enum_snapshots()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98193",
                            "    - wifi: libipw: reject TKIP frames without a full MIC",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-97555",
                            "    - smb: client: fix heap overflow in DACL owner/group rewrite",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-97557",
                            "    - smb: client: avoid leaking refcount in cifs_queue_oplock_break()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-97564",
                            "    - smb: client: reject userspace cifs.idmap descriptions",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-97615",
                            "    - net: bridge: use option bits for CFM/MRP frame handlers",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-97901",
                            "    - genetlink: pin family module during policy dump",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-97908",
                            "    - Bluetooth: btqcomsmd: destroy RPMsg endpoints before freeing hci_dev",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-97925",
                            "    - tick/broadcast: Plug clockevents replacement race",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-93285",
                            "    - f2fs: embed f2fs_gc_kthread in f2fs_sb_info",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-97529",
                            "    - scsi: qla2xxx: Validate BSG request_len before reading vendor_cmd[]",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-97536",
                            "    - scsi: qla2xxx: Fix use-after-free of qpair work on queue teardown",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-97537",
                            "    - scsi: qla2xxx: Fix queue teardown NULL dma_free and bitmap locking",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-89859",
                            "    - scsi: qla2xxx: Zero dport diagnostics buffer to avoid info leak",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-89921",
                            "    - KVM: s390: Zero initialize data structures for inject_pfault_token",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-89972",
                            "    - nvme: add missing SRCU grace period in error path",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-89988",
                            "    - kprobes: Protect kprobe_blacklist with RCU",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-90002",
                            "    - ftrace: Take trace_array reference before accessing its ftrace_ops",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-90016",
                            "    - staging: rtl8723bs: fix OOB read in rtw_restruct_wmm_ie()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-90029",
                            "    - usb: storage: realtek_cr: fix use-after-free on disconnect",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-80947",
                            "    - wifi: rtl8xxxu: fix use-after-free from rx_urb_wq on stop",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-89481",
                            "    - nvme-tcp: fix host memory disclosure on R2T for a read command",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-89492",
                            "    - ocfs2: validate directory-index entry counts when reading metadata",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-89553",
                            "    - nouveau/gem: reserve the bo in the info ioctl around the vma lookup",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-89625",
                            "    - HID: sony: fix UAF of ghl_poke_timer / ghl_urb at driver unbind",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-89633",
                            "    - smb: client: fix OOB read/write from unvalidated DataOffset in",
                            "      coalesce_t2()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-89652",
                            "    - ceph: bound copied dentry name length in NFS export get_name",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-89680",
                            "    - nfsd: fix nfsd_file leak on inter-server COPY setup failure",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-89761",
                            "    - apparmor: fix out-of-bounds write when null terminating a label vec",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-80852",
                            "    - tls: device: fix out-of-bounds write in tls_append_frag()",
                            ""
                        ],
                        "package": "linux-kvm",
                        "version": "5.15.0-1113.118",
                        "urgency": "medium",
                        "distributions": "jammy",
                        "launchpad_bugs_fixed": [
                            2173211,
                            2173225,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857
                        ],
                        "author": "Ubuntu Kernel Preparation Bot <ubuntu-kernel-bot@canonical.com>",
                        "date": "Mon, 09 Nov 2026 16:21:29 +0000"
                    }
                ],
                "notes": "linux-headers-5.15.0-1113-kvm version '5.15.0-1113.118' (source package linux-kvm version '5.15.0-1113.118') was added. linux-headers-5.15.0-1113-kvm version '5.15.0-1113.118' has the same source package name, linux-kvm, as removed package linux-headers-5.15.0-1112-kvm. As such we can use the source package version of the removed package, '5.15.0-1112.117', as the starting point in our changelog diff. Kernel packages are an example of where the binary package name changes for the same source package. Using the removed package source package version as our starting point means we can still get meaningful changelog diffs even for what appears to be a new package.",
                "is_version_downgrade": false
            },
            {
                "name": "linux-image-5.15.0-1113-kvm",
                "from_version": {
                    "source_package_name": "linux-signed-kvm",
                    "source_package_version": "5.15.0-1112.117",
                    "version": null
                },
                "to_version": {
                    "source_package_name": "linux-signed-kvm",
                    "source_package_version": "5.15.0-1113.118",
                    "version": "5.15.0-1113.118"
                },
                "cves": [],
                "launchpad_bugs_fixed": [
                    1786013
                ],
                "changes": [
                    {
                        "cves": [],
                        "log": [
                            "",
                            "  * Main version: 5.15.0-1113.118",
                            "",
                            "  * Packaging resync (LP: #1786013)",
                            "    - [Packaging] debian/tracking-bug -- resync from main package",
                            ""
                        ],
                        "package": "linux-signed-kvm",
                        "version": "5.15.0-1113.118",
                        "urgency": "medium",
                        "distributions": "jammy",
                        "launchpad_bugs_fixed": [
                            1786013
                        ],
                        "author": "Ubuntu Kernel Preparation Bot <ubuntu-kernel-bot@canonical.com>",
                        "date": "Mon, 09 Nov 2026 16:21:56 +0000"
                    }
                ],
                "notes": "linux-image-5.15.0-1113-kvm version '5.15.0-1113.118' (source package linux-signed-kvm version '5.15.0-1113.118') was added. linux-image-5.15.0-1113-kvm version '5.15.0-1113.118' has the same source package name, linux-signed-kvm, as removed package linux-image-5.15.0-1112-kvm. As such we can use the source package version of the removed package, '5.15.0-1112.117', as the starting point in our changelog diff. Kernel packages are an example of where the binary package name changes for the same source package. Using the removed package source package version as our starting point means we can still get meaningful changelog diffs even for what appears to be a new package.",
                "is_version_downgrade": false
            },
            {
                "name": "linux-kvm-headers-5.15.0-1113",
                "from_version": {
                    "source_package_name": "linux-kvm",
                    "source_package_version": "5.15.0-1112.117",
                    "version": null
                },
                "to_version": {
                    "source_package_name": "linux-kvm",
                    "source_package_version": "5.15.0-1113.118",
                    "version": "5.15.0-1113.118"
                },
                "cves": [
                    {
                        "cve": "CVE-2026-99115",
                        "url": "https://ubuntu.com/security/CVE-2026-99115",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ksmbd: fill in FileSysIdentifier in FS_POSIX_INFORMATION  smb2_get_info_filesystem() reports 56 bytes for FS_POSIX_INFORMATION, that is the whole of FILE_SYSTEM_POSIX_INFO, but never assigns FileSysIdentifier.  Those eight bytes go to the client as they are found in the response buffer.  The buffer is zeroed on allocation, so a standalone request leaks nothing.  A compound request can leak: the offset of the next response is advanced by the length pinned for the previous one, so a reply that was written into the buffer and then dropped in favour of the short error response of smb2_set_err_rsp() stays there, and the next reply is laid over it with only the header cleared.  Report the file system id statfs() returned, which is what the field is for.  FileSysIdentifier is __le64 and f_fsid is a pair of ints, so assemble the value first, val[0] as the low half, and convert it on the way out.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99113",
                        "url": "https://ubuntu.com/security/CVE-2026-99113",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ksmbd: zero the FS_OBJECT_ID_INFORMATION buffer before filling it in  smb2_get_info_filesystem() reports 64 bytes for FS_OBJECT_ID_INFORMATION, that is the whole of struct object_id_info, but writes only 46 of them:   - objid[] is 16 bytes, and when the volume UUID is not available only    sizeof(stfs.f_fsid) (8) bytes are copied into it;  - extended_info.version_string[] is STRING_LENGTH (28) bytes, and only    strlen(\"1.1.0\") (5) bytes are copied into it.  The response buffer is zeroed on allocation (kvzalloc() in smb2_allocate_rsp_buf()), so for a standalone request the remaining 31 bytes are zero.  In a compound request they need not be.  The offset of the next response is advanced by the length pinned for the previous one, so if a preceding command wrote its reply into the buffer and then failed, smb2_set_err_rsp() pins only the short error response and the next reply lands inside the area that has already been written.  Only the header is cleared there:  \tmemset((char *)rsp_hdr, 0, sizeof(struct smb2_hdr) + 2);  The client then receives up to 31 bytes of a response it was not meant to see, including one that failed with an access denied error.  Clear the structure before filling it in.  As a side effect version_string is now NUL terminated.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99114",
                        "url": "https://ubuntu.com/security/CVE-2026-99114",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ksmbd: initialize FileSystemControlFlags in FS_CONTROL_INFORMATION  smb2_get_info_filesystem() reports 48 bytes for FS_CONTROL_INFORMATION, that is the whole of struct smb2_fs_control_info, but never assigns FileSystemControlFlags.  Those four bytes go to the client as they are found in the response buffer.  The buffer is zeroed on allocation, so a standalone request leaks nothing.  A compound request can leak: the offset of the next response is advanced by the length pinned for the previous one, so a reply that was written into the buffer and then dropped in favour of the short error response of smb2_set_err_rsp() stays there, and the next reply is laid over it with only the header cleared.  ksmbd does not implement quota tracking, so report no control flags.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99132",
                        "url": "https://ubuntu.com/security/CVE-2026-99132",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  xfs: don't hold buffer locks across sync transaction commit in xfs_sync_sb_buf  xfs_sync_sb_buf() holds sb/rtsb buffer locks across a synchronous xfs_trans_commit(), which flushes the CIL push workqueue internally. If shutdown occurs during the CIL push, xfs_buf_item_unpin() needs to lock these buffers to fail them, causing a deadlock:    setlabel:          holds buf lock -> flush_workqueue(xfs-cil)   CIL push worker:   xfs_buf_item_unpin -> xfs_buf_lock(same buf)  Remove the xfs_trans_bhold() calls so that commit releases the buffer locks normally.  After the sync commit, re-acquire the buffers via mp->m_sb_bp / mp->m_rtsb_bp for the on-disk writeback.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99135",
                        "url": "https://ubuntu.com/security/CVE-2026-99135",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  dm-integrity: fix infinite loop on discard with large tag size  When integrity_metadata handles a discard, it fills a buffer with DISCARD_FILLER and writes it over the tags, max_blocks blocks at a time. If the kmalloc fails, the buffer is the on-stack array checksums_onstack and max_size is set to HASH_MAX_DIGESTSIZE. So if the tag size is larger than HASH_MAX_DIGESTSIZE, max_blocks is zero, bi_size is never decremented and the loop never terminates.  Fix this by using sizeof(checksums_onstack) as max_size. The array has MAX_TAG_SIZE bytes since commit b93b6643e9b5 (\"dm integrity: fix a crash with unusually large tag size\"), so max_blocks is at least 1.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99118",
                        "url": "https://ubuntu.com/security/CVE-2026-99118",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  drm/i915/dmc: Harden DMC firmware payload parsing  Validate the conversion of the DMC firmware size from dwords to bytes using check_mul_overflow() before calculating the firmware payload size.  Reject zero-length payloads and zero MMIO counts in the DMC firmware header so malformed firmware is caught early. Also set dmc_fw_size only after the payload allocation succeeds.  (cherry picked from commit efde6601a1f1daedfe3dcc2816c934ddb44e3eef)",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99169",
                        "url": "https://ubuntu.com/security/CVE-2026-99169",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  futex: Fix mm reuse handling for FUT_OFF_MMSHARED  A FUT_OFF_MMSHARED futex is a shared futex that refers to an MM. It is possible for a process to wait on a shared futex with a different MM because a FUT_OFF_INODE waiter can be requeued onto a FUT_OFF_MMSHARED futex by another process. This can cause FUT_OFF_MMSHARED waiters on a freed MM to consume wakeups intended for a newly allocated MM at the same address.  Fix it by keying FUT_OFF_MMSHARED using a unique 64-bit per-MM ID. Leave private futexes as before to avoid influencing the performance of the hotpath.  (Multi-threaded processes typically implicitly use FUT_OFF_MMSHARED by setting clear_child_tid such that it points into anonymous memory, which causes mm_release() in a multi-threaded mm to perform FUTEX_WAKE.)",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99161",
                        "url": "https://ubuntu.com/security/CVE-2026-99161",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  i2c: viai2c-wmt: Fix clock leak in wmt_i2c_probe()  In wmt_i2c_probe(), i2c->clk is acquired using of_clk_get(). If any subsequent operation fails or when the module is unloaded, the clock reference count is never decremented via clk_put(), leading to a resource leak.  Switch to devm_clk_get() so that the clock is automatically managed and released.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99077",
                        "url": "https://ubuntu.com/security/CVE-2026-99077",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ipv4: udp: Create exceptions before socket matching  Currently, when ICMP Fragmentation Needed and Redirect Message packets are locally delivered and quote a UDP packet, a FIB nexthop exception (FNHE) is only created if the kernel can match the UDP packet to an existing socket.  This behavior allows off-path attackers to conduct a side-channel attack on the FNHE cache in order to discover the ephemeral port used by a connected UDP socket.  Commit 6457378fe796 (\"ipv4: use siphash instead of Jenkins in fnhe_hashfun()\") and commit 67d6d681e15b (\"ipv4: make exception cache less predictible\") tried to mitigate such attacks by making it harder for attackers to discover hash collisions in the FNHE cache and by randomizing the number of exceptions a hash bucket can hold, respectively. Unfortunately, both of the mitigations can be bypassed.  Instead, mitigate such attacks by always creating a FNHE, even before trying to find a matching socket. Do that by calling ipv4_update_pmtu() and ipv4_redirect(), the helpers used when the quoted packet did not originate from a socket.  This means that guesses (right or wrong) from an off-path attacker will always result in a FNHE being created or updated in the cache that the attacker can observe.  Pass an oif of 0, in a similar fashion to icmp_err(). This is also the oif used by the socket path for sockets that are not bound to a device.  Note that this does not allow attackers to create FNHEs that they could not create before, as both helpers can already be reached with little to no validation. For example, by sending an ICMP error that quotes an ICMP Echo Reply or one that quotes a UDP source port that matches a wildcard socket.  Also note that in the good case (matched socket) the above scheme comes at the cost of an extra route lookup, as the no socket helpers perform their own lookup before the one performed by ipv4_sk_update_pmtu() / ipv4_sk_redirect(). When the two resolve to different nexthops, it also results in two exceptions being created for the same destination IP. One in the FNHE cache of the nexthop resolved by the no socket helpers and another in the FNHE cache of the nexthop used by the socket.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99123",
                        "url": "https://ubuntu.com/security/CVE-2026-99123",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  vsock/virtio: validate packet source for connected sockets  virtio_transport_recv_pkt() looks up sockets first by the full source and destination tuple, then by destination only in the bound table. The fallback is needed for listening and connecting sockets, but sockets remain in the bound table after connect(), so it can also return a non-listening socket.  The fallback does not validate the source address. In TCP_SYN_SENT, a RESPONSE from an unrelated source can transition the victim socket to TCP_ESTABLISHED while its stored remote address remains unchanged. Subsequent RW packets from that source are delivered through the same destination-only fallback.  This was reproduced with capability-empty processes under different UIDs. The attacker discovered the target tuple through unprivileged AF_VSOCK sock_diag and caused the victim socket to read 16 attacker-chosen bytes; the intended peer-side socket read 0 of those 16 bytes.  Add vsock_check_source() to validate the transport, source port and source CID against the peer stored in a non-listening socket. The local transport is the CID exception because its packets are generated internally with VMADDR_CID_LOCAL as their source, including connections using CID aliases.  Use the helper after lock_sock() in the virtio receive path.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-89987",
                        "url": "https://ubuntu.com/security/CVE-2026-89987",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  mm/huge_memory: transfer the pmd dirty bit to the folio on zap  zap_huge_pmd_folio() propagates the pmd young bit to the folio for the file case, but not the dirty bit.  The pte path does propagate it, in zap_present_folio_ptes() and so does the pmd split path, in __split_huge_pmd_locked().  For most file mappings the omission is harmless, because writing to a shared file mapping goes through page_mkwrite(), which dirties the folio. tmpfs is different: it has no page_mkwrite(), and vma_wants_writenotify() is false for it, so a *read* fault on a MAP_SHARED tmpfs mapping installs a writable pmd via do_read_fault().  do_read_fault() does not call fault_dirty_shared_page(), so subsequent stores through that mapping set only the hardware dirty bit in the pmd and never call folio_mark_dirty(). A shmem folio allocated by a fault is marked uptodate but not dirty (see the clear: block in shmem_get_folio_gfp()), so PG_dirty is never set at all.  Unmapping such a folio - munmap(), or exit_mmap() when the process dies - then loses the only record that it was written, because zap_huge_pmd() drops the pmd without transferring the dirty bit.  Reclaim afterwards sees a clean shmem folio: the whole swap-out block in shrink_folio_list() is inside \"if (folio_test_dirty(folio))\", so pageout() is skipped and the folio falls into __remove_mapping().  There, folio_is_file_lru() is false for a swapbacked folio, so no shadow entry is created and __filemap_remove_folio(folio, NULL) simply empties the i_pages slot.  The data is freed without ever being written to swap, and the next fault on that index returns a freshly zeroed folio.  This is silent data loss for any process that keeps state in a MAP_SHARED tmpfs segment across an unmap - for example a cache handed from one process generation to the next through /dev/shm.  It requires the folio to be PMD-mapped, so it only shows up once shmem THP is enabled (which is what we did in Meta fleet and started noticing crashes); with THP off the pte path transfers the dirty bit correctly.  It also only becomes visible when swap is enabled, because with no swap device shmem folios (which are on the anon LRU) are not scanned by reclaim at all, so the clean folio is never dropped.  Reproduced on x86_64 with a tmpfs mounted huge=within_size: read-fault a 2MB-backed region, write a known pattern through the resulting mapping, munmap, force reclaim of the cgroup, then re-map and read back.  Without this patch the region reads back as zeros and vmstat shows zswpout 0 - the data was discarded rather than swapped.  With this patch the region reads back correctly and the pages are swapped out as expected.  With huge=never, or when the first touch is a write, the test passes either way.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-09-16 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-80572",
                        "url": "https://ubuntu.com/security/CVE-2026-80572",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  Input: byd - synchronize timer deletion before freeing private data  byd_disconnect() uses timer_delete() before freeing the driver's private data.  This does not wait for a running byd_clear_touch() callback, which dereferences the private data and its psmouse pointer.  A callback racing with disconnect can therefore access the private data after it has been freed.  The timer can also still be re-armed by byd_process_byte() while the disconnect is in progress.  Use timer_shutdown_sync() before freeing the private data: it waits for a running callback and turns any later re-arm attempt into a no-op.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-08-26 15:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99180",
                        "url": "https://ubuntu.com/security/CVE-2026-99180",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  unicode: free the map after a grace period  generic_ci_d_hash() and generic_ci_d_compare() read sb->s_encoding and dereference the unicode map while a pathwalk in rcu mode holds nothing but rcu_read_lock(). The filesystems that use them, ext4, f2fs and tmpfs, drop the map with utf8_unload() from ->put_super(), which runs when the last reference to the mount goes away. A lookup that is still inside such a filesystem at that point reads a freed map.  With a pathwalk held up in utf8_casefold_hash() while the last reference to a casefolded tmpfs goes away:    BUG: KASAN: slab-use-after-free in utf8nlookup+0x74c/0x950   Read of size 8 at addr ff110001030fe658 by task walker/98   Call Trace:    <TASK>    utf8nlookup+0x74c/0x950    utf8byte+0x160/0x1560    utf8_casefold_hash+0x167/0x230    generic_ci_d_hash+0xdd/0x1c0    link_path_walk+0x11ad/0x1d30    path_lookupat+0x63/0xb00    filename_lookup+0x1f1/0x5b0    vfs_statx+0xd7/0x3b0   [...]   Allocated by task 94:    __kmalloc_cache_noprof+0x249/0x560    utf8_load+0x4e/0x570    shmem_parse_opt_casefold.isra.0+0x92/0x270   [...]   Freed by task 97:    kfree+0x1db/0x5b0    shmem_put_super+0x72/0x170    generic_shutdown_super+0x14c/0x530    kill_anon_super+0x3a/0x60    deactivate_locked_super+0x9c/0xf0    cleanup_mnt+0x9f/0x130  So far that has been hard to hit. umount(2) waits for a grace period in namespace_unlock() before it drops the mount, so only a mount whose last reference goes away elsewhere, like the close of a file or a chdir out of a lazily unmounted directory, can race a walker. So it is reachable.  Delay the free until a grace period has passed. The map and the data table it holds a reference to then outlive any pathwalk that found the superblock before the mount went away. The reference on the data table module is dropped from the rcu callback as well. utf8-core is built in whenever CONFIG_UNICODE is set, so there is no module exit that would have to wait for the callbacks.  Overlayfs points the s_encoding of an overlay at the map of its first layer without taking a reference of its own. That stays correct. The layer is held by the overlay, so its map is dropped only after the overlay is gone.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99179",
                        "url": "https://ubuntu.com/security/CVE-2026-99179",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  watch_queue: Fix note pool publication race in watch_queue_set_size()  There is a race between watch_queue_set_size() and post_one_notification(). watch_queue_set_size() publishes wqueue->notes, notes_bitmap, nr_pages and nr_notes with plain stores, and post_one_notification() reads them with plain loads under a different lock, so nothing orders the four stores against the poster's loads: depending on the build, notes can be stored last (gcc 14 on x86-64 does this).  Since keyctl_watch_key() lets a watch attach to a queue before it is sized, post_one_notification() can already be running on another CPU at that moment: it reads nr_notes > 0, passes its bounds check, and then reads notes while it is still NULL, dereferencing notes[0].  An unprivileged user triggers this reliably by watching one of its own keys through a notification pipe and racing ioctl(IOC_WATCH_QUEUE_SET_SIZE) on that pipe against keyctl(KEYCTL_SETPERM) on the key from another CPU, triggering:    BUG: kernel NULL pointer dereference, address: 0000000000000000   RIP: 0010:post_one_notification.isra.0+0xa2/0x1e0   Call Trace:    __post_watch_notification+0x148/0x180    keyctl_setperm_key+0x119/0x130    do_syscall_64+0x108/0x4c0    entry_SYSCALL_64_after_hwframe+0x77/0x7f   Kernel panic - not syncing: Fatal exception in interrupt  Fix this by publishing nr_notes last with smp_store_release(), and by reading it once with smp_load_acquire() in post_one_notification() before the bitmap and the page array are touched.  A poster that observes a non-zero nr_notes then also observes the pool behind it; one that observes zero drops the notification as before.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-89912",
                        "url": "https://ubuntu.com/security/CVE-2026-89912",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  KVM: arm64: vgic-its: Don't dereference a NULL collection on ITT save  MAPC with V=0 drops ite->collection but leaves the ITE on the device's ITT list, and vgic_its_save_ite() dereferences it unconditionally. A guest that issues MAPD, MAPTI and then MAPC(V=0) therefore oopses the host when the VMM issues KVM_DEV_ARM_ITS_SAVE_TABLES to migrate it. That sequence is UNPREDICTABLE per the architecture, but KVM already handles the resulting state in the translate, MOVI and DISCARD paths.  Save a zeroed entry, which vgic_its_restore_ite() reads back as invalid. Skipping the ITE instead would leave the ITT slot holding whatever is in guest memory, and restore rejects an entry naming a collection the restored collection table does not have.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-09-16 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99156",
                        "url": "https://ubuntu.com/security/CVE-2026-99156",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  scsi: st: Fix use-after-free race between st_remove() and st_open()  st_remove() drops the probe reference on the scsi_tape with kref_put() and only afterwards removes its index from st_index_idr. If that was the last reference, scsi_tape_release() frees the structure while it is still published in the idr.  scsi_tape_get(), called from st_open(), looks up the tape in st_index_idr and takes a reference under st_ref_mutex and st_index_lock. remove_cdevs() does not wait for opens that are already past chrdev_open(), so an open that is blocked on st_ref_mutex while st_remove() holds it can take the mutex as soon as st_remove() drops it, find the freed tpnt in the idr and call kref_get() on it:    BUG: KASAN: slab-use-after-free in st_open   Write of size 4 ...    st_open (drivers/scsi/st.c:254 drivers/scsi/st.c:1291)    chrdev_open   ...   Freed by task ...:    kfree    st_remove (drivers/scsi/st.c:4512)  Remove the index from the idr before dropping the reference, all under st_ref_mutex. A concurrent scsi_tape_get() now either runs first and holds a valid reference that keeps the tape alive, or runs afterwards and finds nothing, so st_open() fails with -ENXIO.  This restores the ordering st_remove() had before the conversion to st_index_idr, where the tape was unpublished from scsi_tapes[] before the final kref_put().",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99112",
                        "url": "https://ubuntu.com/security/CVE-2026-99112",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net/sched: cls_flower: validate mask pointer after nla_next()  fl_set_enc_opt() iterates the key's nested tunnel-option attributes with nla_for_each_attr() while advancing a single mask pointer via nla_next() at the bottom of each loop, so the mask cursor is driven by the number of key attributes rather than by the mask's own attributes.  The nla_ok() added by commit c96adff956191 (\"cls_flower: call nla_ok() before nla_next()\") only validates the mask pointer that was just consumed; the pointer produced by nla_next() is used by the next iteration (fl_set_geneve_opt() and siblings) without any validation.  The mask's nested attributes are validated with NL_VALIDATE_LIBERAL, which merely warns on trailing bytes that do not form a complete attribute.  A mask carrying one valid attribute plus 1-3 residue bytes (or a non-aligned attribute length making msk_depth negative) therefore reaches the next iteration with msk_depth != 0, so neither the !msk_depth check in fl_set_enc_opt() nor the !depth check in the per-type helpers fires.  nla_type() then reads past the mask payload and nla_parse_nested_deprecated() iterates with an nla_len taken from those bytes, reading well beyond the mask attribute (KASAN: slab-out-of-bounds read in __nla_validate_parse from fl_change()).  Validate the advanced mask pointer as well: when the mask is not legitimately exhausted (msk_depth != 0) and the new pointer fails nla_ok(), reject the filter with -EINVAL.  An exactly exhausted mask still skips the check, preserving exact-match behaviour for the remaining key attributes.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99117",
                        "url": "https://ubuntu.com/security/CVE-2026-99117",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net: bridge: mcast: don't truncate the port group walk on teardown  __br_multicast_disable_port_ctx() and br_multicast_del_port() walk port->mglist with hlist_for_each_entry_safe(). However, br_multicast_find_del_pg() can also delete other entries from the same list through br_multicast_fwd_src_remove() or __fwd_del_star_excl().  If such an entry is the iterator's saved next node, hlist_del_init() clears its ->next and terminates the walk early. The reproducer triggers this in both teardown walks, leaving port groups in the bridge mdb with a dangling ->key.port after del_nbp() frees the port:    BUG: KASAN: slab-use-after-free in __mdb_fill_info+0x1191/0x1320    __mdb_fill_info+0x1191/0x1320    br_mdb_dump+0x594/0xe40    rtnl_mdb_dump+0x1cf/0x5d0  Use hlist_del_init_rcu() to unlink the group while preserving ->next. br_multicast_del_pg() and the teardown walks run under br->multicast_lock. The GC worker must acquire the same lock before detaching the group for destruction, so the node remains alive while the walk uses the preserved pointer.  Preserving ->next means a walk can now reach a group that an earlier iteration already deleted as a side effect. That group is off mp->ports, so br_multicast_find_del_pg() would fall through its port scan and hit the trailing WARN_ON(1). Skip such groups at the top of that helper: a port group is put on port->mglist when it is created and only unlinked when it is deleted, so hlist_unhashed() identifies exactly this case.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-74405",
                        "url": "https://ubuntu.com/security/CVE-2026-74405",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  OPP: Fix race between OPP addition and lookup  A race exists between dev_pm_opp_add_dynamic() and dev_pm_opp_find_freq_exact():    CPU0 (add)                          CPU1 (lookup)   -------------------------------     ------------------------------   _opp_add()     mutex_lock()     list_add(&new_opp->node, head)     mutex_unlock()                    _opp_table_find_key()                                         mutex_lock()                                         dev_pm_opp_get(opp)                                           kref_get()                                         mutex_unlock()     kref_init(&new_opp->kref)                                       dev_pm_opp_put()                                         kref_put_mutex()  The newly added OPP is inserted into the list before its kref is initialized. A concurrent lookup can find this OPP and increment its reference count while it is still uninitialized, leading to refcount corruption and a potential premature free.  Fix this by initializing ->kref and ->opp_table before making the OPP visible via list_add(). This ensures any concurrent lookup observes a fully initialized object.  [ Viresh: Updated commit log ]",
                        "cve_priority": "low",
                        "cve_public_date": "2026-08-15 06:22:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-74739",
                        "url": "https://ubuntu.com/security/CVE-2026-74739",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net/sched: cls_u32: skip hash tables in u32_bind_class()  u32_walk() enumerates both struct tc_u_hnode and struct tc_u_knode through the walker callback. u32_bind_class() unconditionally casts the passed fh to tc_u_knode and accesses &n->res, so when fh is actually a tc_u_hnode, which has no tcf_result member, this results in a slab-out-of-bounds read of res->classid in tc_cls_bind_class().  The issue can be reproduced with the following commands:      tc qdisc add dev lo root handle 1: hfsc     tc class add dev lo parent 1: classid 1:1 hfsc sc rate 1000kbit     tc filter add dev lo parent 1:1 protocol ip prio 1 u32 match u32 0 0 flowid 1:1     tc class add dev lo parent 1: classid 1:2 hfsc sc rate 2000kbit  Fix this by skipping hash tables via the TC_U32_KEY(handle) check.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-08-26 15:16:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-64015",
                        "url": "https://ubuntu.com/security/CVE-2026-64015",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  security/keys: fix missed RCU read section on lookup  Nicholas Carlini reports that the keyring code calls assoc_array_find() in find_key_to_update() without holding the RCU read lock, while the assoc_array_gc() code really is designed around removing the node from the tree and then freeing it after an RCU grace-period.  The regular key handling doesn't see this because holding the keyring semaphore hides any lifetime issues, but the persistent key handling uses a different model.  Instead of extending the keyring locking, just do the simple RCU locking that the assoc_array was designed for.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-07-19 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-74672",
                        "url": "https://ubuntu.com/security/CVE-2026-74672",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  mm/vmalloc: acquire init_mm lock on huge vmap to avoid ptdump UAF  Patch series \"mm: fix UAF caused by race between ptdump and vmap pgtable freeing\", v6.  Kernel page table walkers fall into two broad categories - those ranges where no exclusion is required via walk_kernel_page_table_range_lockless() and those where exclusion is required via walk_kernel_page_table_range() or walk_page_range_debug().  The former category is used only by arm64 arch code operating on ranges it both wholly owns and does not concurrently write.  The latter category consists of kernel page table walkers operating on ranges that are wholly owned (but which need exclusion against concurrent writers).  The lock used for exclusion is the mmap lock, and for kernel ranges this is the mmap lock on init_mm.  ptdump is a special case being both the only user of walk_page_range_debug(), and the only case in which it walks ranges it does not own.  This presents a problem, as page tables may be freed under ptdump.  And indeed there is a use-after-free bug in the kernel as a result, which this series addresses.  vmap promotes page tables to huge leaf entries where possible, freeing the lower page table when it does.  It does this with no meaningful locks held against concurrent ptdump walks.  As a result, use-after-free can currently occur.  This series addresses the issue by having the vmap huge promotion logic acquire the mmap read lock while both setting the huge page table entry and freeing the prior leaf page table.  The ptdump code already acquires the mmap write lock, so by doing so we ensure that the ptdump walker only ever observes either the huge page table entry or the existing page table entry, and nothing is freed underneath it.  A mitigation for this issue was already applied for arm64 in commit fa93b45fd397 (\"arm64: Enable vmalloc-huge with ptdump\"), which this series has to deal with carefully.  This mitigation resolves the issue by acquiring the mmap read lock on init_mm on vmap page table free if a ptdump is in progress.  However the fix in this series would cause a deadlock if we were to simply apply it for arm64 without also reverting the change.  This is because vmap may acquire the read lock before ptdump attempts to acquire the write lock, which then gets queued, and rwsem starvation rules mean that the (unacknowledged) nested mmap read lock in the arm64 code would also block, meaning the original read lock is never released and thus deadlock.  This series works around this by #ifndef CONFIG_ARM64'ing the mmap read lock in vmap logic, then partially reverting commit fa93b45fd397 (\"arm64: Enable vmalloc-huge with ptdump\"), keeping the enablement of huge vmap support, and removing the ifdeffery with the partial revert patch.  There are related issues that are also addressed in this series:  * x86 page attribute logic, specifically Change Page Attributes (CPA),   implements a feature whereby huge ranges can be collapsed into huge leaf   entries. This can similarly cause a UAF when done in parallel with a   ptdump walk, so similarly acquire the init_mm mmap lock to avoid this.  * The CPA logic allows concurrent page table manipulation and CPA   collapse, meaning the former risks accessing a page table the latter   frees. Fix this by acquiring mmap write lock on init_mm across the   whole CPA collapse operation and read lock on the page table   manipulation.  * x86 and arm64 permit walks of non-kernel mm's (both allowing efi mm   walks, and in x86's case arbitrary mm's), so we ensure kernel mappings   remain stable by locking the init_mm as well as the mm being walked.  The ordering of patches is established for both strict dependencies (the arm64 partial revert in particular has to be done after the vmap changes) and logical ones (the non-kernel mm fix only makes sense once the vmap/CPA fixes are in place).   This patch (of 3):  Currently there is a nasty ra ---truncated---",
                        "cve_priority": "low",
                        "cve_public_date": "2026-08-22 16:16:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99121",
                        "url": "https://ubuntu.com/security/CVE-2026-99121",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ipv4: avoid divide by zero in fib_rebalance  fib_rebalance() computes the total eligible nexthop weight in one pass and programs upper bounds in a second pass. A concurrent change to ignore_routes_with_linkdown can make the first pass return zero while the second pass sees an eligible nexthop, resulting in division by zero.  If the first pass reports a zero total, set each nexthop upper bound to -1 and skip the division. This matches the IPv6 fix in commit d2c26c2911dd (\"ipv6: avoid divide by zero in rt6_multipath_rebalance\") and preserves the lock-free rebalance path.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99124",
                        "url": "https://ubuntu.com/security/CVE-2026-99124",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  s390/pci: Fix leak of uninitialized kernel data in SCLP report  While report_error_write() checks that the provided buffer is at least as large as the header struct, but not that it is large enough to contain the report with the length claimed by report->length. If user-space provides a short buffer, meaning a larger report->length than the actually written payload, up to around 4K of kernel data from past the kmalloc(len + 1) sized buffer allocated in kernfs_fop_write_iter() will leak into the SCLP report.  However, as the entity processing the SCLP is privileged and able to access at least the page including the report, this does not leak data that entity could not access but it is still an out of bounds read and a malformed error report that should be rejected.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99126",
                        "url": "https://ubuntu.com/security/CVE-2026-99126",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  s390/ctcm: Prevent XID null dereference  The mpc_validate_xid() function sets grp->saved_xid2->xid2_flag2 to 0x40 to signal XID validation error. If peer XID is NULL or r/w channel pairing mismatch happens, grp->saved_xid2 is never initialized. An attempt to set the flag in such case leads to NULL dereference.  Fix this by using the always available priv->xid->xid2_flag2 instead of grp->saved_xid2->xid2_flag2 for validation errors.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99127",
                        "url": "https://ubuntu.com/security/CVE-2026-99127",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  page_pool: keep frag_offset aligned for odd-sized requests  page_pool_alloc_frag_netmem() rounds the requested fragment size with  \tsize = ALIGN(size, dma_get_cache_alignment());  dma_get_cache_alignment() returns 1 unless the architecture defines ARCH_DMA_MINALIGN, which DMA-coherent architectures such as x86 do not. There the ALIGN() is a no-op and pool->frag_offset advances by the raw, unrounded size.  A single caller asking for an odd size then leaves frag_offset misaligned for every fragment carved out of that page afterwards.  The pool is shared, so the damage is not confined to the caller that caused it.  The per-cpu system_page_pool used by generic XDP hits this. skb_pp_cow_data() allocates its fragments with the raw packet length:  \tsize = min_t(u32, len, PAGE_SIZE); \ttruesize = size; \tpage = page_pool_dev_alloc(pool, &page_off, &truesize);  leaving frag_offset odd for whatever is carved out of that page next.  Its own head allocation is already aligned -- SKB_HEAD_ALIGN(size) plus the XDP_PACKET_HEADROOM its callers pass -- so it is a later user of the shared pool that pays: page_pool_dev_alloc_va() returns a misaligned buffer, napi_build_skb() installs it as skb->head, and skb_shinfo(skb) == skb->head + skb->end is misaligned with it.  skb_shinfo()->dataref is a 4-byte atomic_t at offset 0x20, so the atomic_inc() in __skb_clone() straddles a cache line.  On x86 with split lock detection -- fatal for kernel split locks by default -- this panics the machine:    Oops: Split lock detected   RIP: 0010:skb_clone+0x154/0x1e0   Call Trace:    <IRQ>    raw_local_deliver+0x1ed/0x2c0    ip_protocol_deliver_rcu+0x54/0x1c0    ip_local_deliver_finish+0x85/0x100    ip_local_deliver+0x67/0x100    __netif_receive_skb_one_core+0x85/0xa0    process_backlog+0x87/0x130  Reproduced by attaching any generic-mode XDP program to loopback and opening a RAW IPPROTO_UDP socket, which makes raw_local_deliver() clone every locally delivered UDP packet; ordinary DNS traffic then triggers it, roughly once per 2500 clones.  Observed on 6.12.101 and 7.1.8.  Tracing page_pool_alloc_frag_netmem() over one such run shows the amplification -- two odd-sized requests, nine misaligned offsets:    requested size & 7:   0: 17035    5: 1    7: 1   frag_offset & 7:      0: 17028    3: 1    4: 1    5: 1    6: 1    7: 5  and skb_pp_cow_data() returning heads that were aligned on entry:    head 0xffff8f4c86aeac00 -> 0xffff8f4c53a9a9c4 (&7=4)   head 0xffff8f4d6a8a42c0 -> 0xffff8f4c4f7b7a45 (&7=5)  Round the fragment size up to at least the alignment struct skb_shared_info requires, so fragments are always suitably aligned for the objects callers build on them.  Architectures needing a larger DMA alignment keep it.  This also makes the remainder computed in page_pool_alloc_netmem(),  \t*size = max_size - *offset;  aligned, since max_size is a power of two -- which fixes the matching misalignment of skb->end.  Verified with a controlled A/B under QEMU/KVM: same tree, same config, same compiler, same rootfs and identical traffic, differing only by this patch.  A SEC(\"xdp.frags\") XDP_PASS program on lo plus UDP datagrams larger than max_head_size drives skb_pp_cow_data()'s fragment loop, which passes raw packet lengths to the pool.  Measured at the return of skb_pp_cow_data():                            unpatched   patched   skb_pp_cow_data calls       40800     40800   misaligned skb->head         1120         0   dataref at line offset >60     80         0  The last row counts the accesses that actually fault: skb_shinfo()->dataref sits at head+end+0x20 and is a 4-byte atomic, so `lock incl` splits a 64-byte cache line only when that address lands at offset 61..63.  All 80 occurrences were at offset 61; the panic reported above was at offset 62.  Eliminating the misalignment removes every one of them.  Same class of bug as commit 3bed3cc4156e (\"net: Do not allocate page fragments t ---truncated---",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99128",
                        "url": "https://ubuntu.com/security/CVE-2026-99128",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  sctp: validate chunk length in the inqueue parser  SCTP chunks always include a four-byte generic header, but sctp_inq_pop() currently accepts shorter declared lengths. A zero-length chunk leaves chunk_end at the current header.  When ASCONF is covered by the association's SCTP-AUTH policy, sctp_assoc_bh_rcv() can continue before the state machine performs its normal chunk-length check. sctp_inq_pop() then returns the same malformed chunk repeatedly and the receive softirq can lock up.  A remote SCTP peer can trigger this after establishing an association on a kernel built with CONFIG_IP_SCTP and configured with net.sctp.addip_enable=1 and net.sctp.auth_enable=1. The reproducer did not require application credentials, a shared SCTP AUTH key, or net.sctp.addip_noauth_enable=1.  On commit f967455fb2a5 (\"seg6: reset IP6CB after IPv6 decapsulation\"), one zero-length ASCONF caused repeated watchdog soft-lockup reports in a two-vCPU KVM guest. All 3 pre-trigger health probes succeeded, while 36 of 37 post-trigger probes failed. With this change, all 37 post-trigger probes succeeded and no equivalent soft-lockup signature appeared.  Reject chunks shorter than the generic SCTP header at the shared inqueue parser boundary. Mark the packet for discard before either caller can continue processing it, while preserving the four-byte generic minimum. Declared-length 1 through 4 controls and kernel-generated ASCONF traffic remained healthy. The patched sctp_hello selftest passed for IPv4 and IPv6.  The complete private reproducer and validation evidence are available directly to maintainers on request.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99133",
                        "url": "https://ubuntu.com/security/CVE-2026-99133",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net/iucv: fix the recvmsg window update  iucv_sock_recvmsg() sends the HiperSockets-only AF_IUCV_FLAG_WIN without testing the transport, so on a classic z/VM socket iucv_send_ctrl() sizes the skb through a NULL iucv->hs_dev. SO_MSGLIMIT accepts 1, so msglimit / 2 is zero and one recvmsg() on its own socket is enough for an unprivileged process to take a spurious disconnect.  It also calls iucv_send_ctrl() under spin_lock_bh(&message_q.lock), which allocates GFP_KERNEL inside a section the code treats as atomic. Sending outside that lock lets two recvmsg() reach afiucv_hs_send() at once, where msg_recv is sampled for the advertised window and subtracted after dev_queue_xmit() -- and sendmsg reaches that counter under lock_sock() while recvmsg holds no socket lock, so both can subtract the same value, the counter goes negative and the credit reaches the peer twice.  Test the transport, claim the credit with atomic_xchg() after the last error exit and hand it back if the transmit fails, and send once the lock is dropped.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99136",
                        "url": "https://ubuntu.com/security/CVE-2026-99136",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  dm-crypt: fix a tiny race condition in crypt_dec_pending  crypt_dec_pending reads io->error before calling atomic_dec_and_test. Another context, for example crypt_endio called from an interrupt, may set io->error and drop its reference between the read and the decrement. crypt_dec_pending then drops the last reference and completes the bio with the stale status - so a read that failed and was never decrypted, or a write that failed, is reported as successful.  The read was placed before the decrement by commit b35f8caa0890 (\"dm crypt: wait for endio to complete before destruction\"), because that commit freed dm_crypt_io before calling bio_endio. This is no longer the case, dm_crypt_io lives in the per-bio data now.  Read io->error after atomic_dec_and_test instead. atomic_dec_and_test is fully ordered, so no additional barrier is needed.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99138",
                        "url": "https://ubuntu.com/security/CVE-2026-99138",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  tcp: fix use-after-free in do_tcp_getsockopt(TCP_CC_INFO)  do_tcp_getsockopt() reads icsk->icsk_ca_ops and dereferences the get_info function pointer without rcu_read_lock(). With BPF struct_ops congestion control, ca_ops can point to dynamically allocated memory that is freed concurrently, resulting in a use-after-free when the kernel dereferences or calls through the stale pointer.    BUG: KASAN: slab-use-after-free in do_tcp_getsockopt+0x2037/0x23e0   Read of size 8 at addr ffff888013701258 by task exploit/149    do_tcp_getsockopt+0x2037/0x23e0 (net/ipv4/tcp.c:4564)    tcp_getsockopt+0x91/0xf0    __sys_getsockopt+0xf7/0x170  Fix this by wrapping the ca_ops load and get_info call within rcu_read_lock()/rcu_read_unlock(), and using READ_ONCE() to load the icsk_ca_ops pointer.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99100",
                        "url": "https://ubuntu.com/security/CVE-2026-99100",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: p54: validate firmware record lengths  The p54 firmware parser accesses component ID and component version records without checking that their lengths cover the fields being read. A malformed record can therefore make the parser read past the record.  Validate the component ID and component version record lengths before accessing their data. The descriptor record is also checked against the shortest descriptor length found in the supported firmware images.  Reject descriptor values that underflow the RX offset or produce an empty RX range before updating the driver state.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-28 04:18:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99140",
                        "url": "https://ubuntu.com/security/CVE-2026-99140",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  tracing: Fix hist trigger timestamps for buffered events  Syzkaller triggered a WARN_ON_ONCE(!nest) warning:    WARNING: kernel/trace/ring_buffer.c:821 at ring_buffer_event_time_stamp   Call trace:     ring_buffer_event_time_stamp     hist_field_timestamp     hist_fn_call     event_hist_trigger     event_triggers_call     __event_trigger_test_discard     trace_event_buffer_commit     do_trace_event_raw_event_sched_switch     trace_event_raw_event_sched_switch  The warning is probabilistically reproducible and is related to syzkaller executing the following commands:    echo 'prev_pid == 999999' > events/sched/sched_switch/filter   echo 'hist:keys=common_timestamp' > events/sched/sched_switch/trigger  The specific triggering process is as follows:  CPU 0                                           CPU 1 (context switching)                             (echo 'hist:keys=common_timestamp' > \\                                                        events/sched/sched_switch/trigger) do_trace_event_raw_event_##call   trace_event_buffer_lock_reserve     if (!tr->no_filter_buffering_ref &&         trace_file->flags & EVENT_FILE_FL_FILTERED)         return entry;  // return directly                                                 event_hist_trigger_parse                                                   hist_register_trigger                                                    tracing_set_filter_buffering(file->tr, true);                                                      tr->no_filter_buffering_ref++;     __trace_buffer_lock_reserve       rb_start_commit         local_inc(&cpu_buffer->committing);  // skipped and not executed   trace_event_buffer_commit     __event_trigger_test_discard       event_triggers_call         event_hist_trigger           hist_fn_call             hist_field_timestamp               ring_buffer_event_time_stamp                 nest = local_read(&cpu_buffer->committing);                 WARN_ON_ONCE(!nest)  // trigger warning  The root cause is that when an event file has a filter attached and the hist trigger has not yet been attached, trace_event_buffer_lock_reserve() writes the event into the per-CPU trace_buffered_event temp buffer instead of reserving it in the ring buffer, so cpu_buffer->committing is not incremented. When the event is later processed at commit time by a hist trigger, hist_field_timestamp() -> ring_buffer_event_time_stamp() sees a zero committing count, triggering WARN_ON_ONCE(!nest).  tracing_event_time_stamp() was added by commit d8279bfc5e959 (\"tracing: Add tracing_event_time_stamp() API\") for exactly this case: if the event is the per-CPU trace_buffered_event, it returns the current ring buffer timestamp. But it never gained a caller. Use it in hist_field_timestamp(), so that a hist trigger that races onto a buffered event records the current time, which is only marginally later than when the event was recorded, instead of warning and recording a bogus timestamp.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99150",
                        "url": "https://ubuntu.com/security/CVE-2026-99150",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  drm/amdgpu: don't drop the runtime PM reference twice in amdgpu_gpr  amdgpu_debugfs_gpr_read() drops its runtime PM reference right after reading the wave registers. When copying them to userspace fails, it jumps to the err label, which drops the reference a second time. A read into a bad buffer on Navi31 either steals a reference somebody else holds (power/runtime_usage goes from 1 to 0) or underflows the count:    amdgpu 0000:03:00.0: Runtime PM usage count underflow!  The registers are already in the kernel buffer at that point, so finish the hardware access first and copy the buffer with a single copy_to_user() instead of the put_user() loop with its own error path.  (cherry picked from commit 31035bbd74f7c3e10c163db875b8e67f8b50ee6a)",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99152",
                        "url": "https://ubuntu.com/security/CVE-2026-99152",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  scsi: libiscsi: Validate the task named by a management response  __iscsi_complete_pdu() fetches the task for five response types from one place and checks only that the index resolved:        case ISCSI_OP_LOGOUT_RSP:       case ISCSI_OP_LOGIN_RSP:       case ISCSI_OP_TEXT_RSP:       case ISCSI_OP_SCSI_TMFUNC_RSP:       case ISCSI_OP_NOOP_IN:               task = iscsi_itt_to_task(conn, hdr->itt);               if (!task)                       return ISCSI_ERR_BAD_ITT;  iscsi_itt_to_task() bounds the index against cmds_max and looks at nothing else, so a target can name any slot in the pool, including one that has never been used. task->conn is then NULL, and both iscsi_nop_out_rsp() and iscsi_complete_task() dereference it. One unsolicited NOP-In is enough; a Text Response carrying the same ITT crashes in iscsi_complete_task() instead.  Require the task to be in flight and not a SCSI command, the way iscsi_itt_to_ctask() does for the command opcodes.  [    6.298634] Oops: general protection fault, probably for non-canonical address 0xdffffc000000000c: 0000 [#1] SMP KASAN NOPTI [    6.298642] KASAN: null-ptr-deref in range [0x0000000000000060-0x0000000000000067] [    6.298652] CPU: 1 UID: 0 PID: 111 Comm: iscsistart Not tainted 7.2.0-rc5-ISCSI1-gf5098b6bae76 #1 PREEMPT(lazy) [    6.298654] Hardware name: QEMU Ubuntu 24.04 PC v2 (i440FX + PIIX, arch_caps fix, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 [    6.298656] RIP: 0010:iscsi_nop_out_rsp.constprop.0+0x46/0x160 [    6.298691] Code: c1 ea 03 48 83 ec 08 80 3c 02 00 0f 85 f5 00 00 00 48 b8 00 00 00 00 00 fc ff df 48 8b 6b 58 48 8d 7d 60 48 89 fa 48 c1 ea 03 <80> 3c 02 00 0f 85 c0 00 00 00 48 8b 45 60 48 39 c3 74 50 48 b8 00 [    6.298698] RSP: 0018:ffff88806c907be8 EFLAGS: 00010206 [    6.298701] RAX: dffffc0000000000 RBX: ffff888006116800 RCX: 0000000000000020 [    6.298702] RDX: 000000000000000c RSI: ffff88800525d578 RDI: 0000000000000060 [    6.298703] RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000 [    6.298706] R10: 0000000000000020 R11: 0000000000000000 R12: 0000000000000000 [    6.298706] R13: 000000000000002e R14: ffff8880056eb440 R15: ffff888006116800 [    6.298707] FS:  00007fc02d1c2740(0000) GS:ffff8880b29bc000(0000) knlGS:0000000000000000 [    6.298710] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [    6.298711] CR2: 000055fe3b56ddf8 CR3: 00000000053b9004 CR4: 0000000000770ef0 [    6.298712] PKRU: 55555554 [    6.298713] Call Trace: [    6.298714]  <IRQ> [    6.298714]  __iscsi_complete_pdu+0x13a8/0x22a0 [    6.298758]  iscsi_complete_pdu+0x54/0xa0 [    6.298759]  iscsi_tcp_hdr_recv_done+0x870/0x2c80 [    6.298778]  iscsi_tcp_recv_skb+0x31e/0xec0 [    6.298800]  iscsi_sw_tcp_recv+0x12f/0x390 [    6.298804]  __tcp_read_sock+0x1ab/0x810 [    6.298812]  iscsi_sw_tcp_data_ready+0x18b/0x510 [    6.298814]  tcp_rcv_established+0x1f56/0x3a00 [    6.298842]  tcp_v4_do_rcv+0x449/0x960 [    6.298847]  tcp_v4_rcv+0x2245/0x3bc0",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99153",
                        "url": "https://ubuntu.com/security/CVE-2026-99153",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  scsi: libiscsi: Validate the ITT reflected in a Reject PDU  A Reject PDU carries a copy of the header it rejects, and iscsi_handle_reject() takes the ITT out of that copy to find the task to clean up:        memcpy(&rejected_pdu, data, sizeof(struct iscsi_hdr));       ...       task = iscsi_itt_to_task(conn, rejected_pdu.itt);  That value is whatever the target put there. iscsi_itt_to_task() bounds the index against cmds_max and checks nothing else, so any task in the pool can be named, and iscsi_nop_out_rsp() then completes it.  An index that has never been used gives a NULL task->conn: the pool is zeroed at session setup and conn is assigned only when a task is allocated. If the task was used and returned, iscsi_complete_task() hits its WARN_ON_ONCE(task->state == ISCSI_TASK_FREE) and the refcount underflows. An in-flight SCSI command is completed as successful - a 1 MiB read returned 1048576 with none of its buffer written and no warning.  Validate the reflected ITT the way iscsi_itt_to_ctask() validates a command ITT, and require the task to be in flight and not a SCSI command.  [    6.248477] Oops: general protection fault, probably for non-canonical address 0xdffffc000000000c: 0000 [#1] SMP KASAN NOPTI [    6.249357] KASAN: null-ptr-deref in range [0x0000000000000060-0x0000000000000067] [    6.249951] CPU: 1 UID: 0 PID: 0 Comm: swapper/1 Not tainted 7.2.0-rc5-ISCSI1-gf5098b6bae76 #1 PREEMPT(lazy) [    6.250718] Hardware name: QEMU Ubuntu 24.04 PC v2 (i440FX + PIIX, arch_caps fix, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 [    6.251616] RIP: 0010:iscsi_nop_out_rsp.constprop.0+0x46/0x160 [    6.252043] Code: c1 ea 03 48 83 ec 08 80 3c 02 00 0f 85 f5 00 00 00 48 b8 00 00 00 00 00 fc ff df 48 8b 6b 58 48 8d 7d 60 48 89 fa 48 c1 ea 03 <80> 3c 02 00 0f 85 c0 00 00 00 48 8b 45 60 48 39 c3 74 50 48 b8 00 [    6.252813] RSP: 0018:ffff88806c907b80 EFLAGS: 00010206 [    6.253042] RAX: dffffc0000000000 RBX: ffff88800607e000 RCX: ffffffff8d571a25 [    6.253345] RDX: 000000000000000c RSI: ffff88806c907c38 RDI: 0000000000000060 [    6.253642] RBP: 0000000000000000 R08: 0000000000000000 R09: fffffbfff235a504 [    6.253947] R10: 0000000000000003 R11: 7463656e6e6f6320 R12: 0000000000000000 [    6.254251] R13: 0000000000000000 R14: ffff88806c907c38 R15: 0000000000000000 [    6.254549] FS:  0000000000000000(0000) GS:ffff8880d95bc000(0000) knlGS:0000000000000000 [    6.254887] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [    6.255140] CR2: 00007fc393e8ffc0 CR3: 0000000005252006 CR4: 0000000000770ef0 [    6.255439] PKRU: 55555554 [    6.255564] Call Trace: [    6.255674]  <IRQ> [    6.255768]  __iscsi_complete_pdu+0x18bf/0x22a0 [    6.256733]  iscsi_complete_pdu+0x54/0xa0 [    6.256905]  iscsi_tcp_data_recv_done+0xf4/0x250 [    6.257103]  iscsi_tcp_recv_skb+0x31e/0xec0 [    6.257680]  iscsi_sw_tcp_recv+0x12f/0x390 [    6.258061]  __tcp_read_sock+0x1ab/0x810 [    6.258853]  iscsi_sw_tcp_data_ready+0x18b/0x510 [    6.259808]  tcp_data_queue+0x1f13/0x4cd0 [    6.260567]  tcp_rcv_established+0x8a5/0x3a00 [    6.261931]  tcp_v4_do_rcv+0x449/0x960 [    6.262269]  tcp_v4_rcv+0x2245/0x3bc0",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99154",
                        "url": "https://ubuntu.com/security/CVE-2026-99154",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  scsi: libiscsi: Reject a negative task index from parse_pdu_itt  A transport that implements parse_pdu_itt hands libiscsi an index taken from the PDU, and both lookups bound it from above only:        if (i >= session->cmds_max)  i and cmds_max are both int, so a negative index passes and session->cmds[i] is read from before the array.  be2iscsi produces one. beiscsi_parse_pdu() assigns the raw tag,        *index = (int)itt;  and beiscsi_complete_pdu() forwards an unsolicited NOP-In from the hardware async ring without replacing its ITT, so the value is the target's. It also reports the session's own age rather than the one in the tag, which leaves the age comparison in iscsi_verify_itt() with nothing to reject.  Bound the index from below in both lookups.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99165",
                        "url": "https://ubuntu.com/security/CVE-2026-99165",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  sctp: revalidate output stream after association connect wait  When message interleaving is enabled, the first send waits for association establishment before building its data chunks.  The wait drops the socket lock, and handshake processing can reduce the output stream count to the peer-advertised inbound stream count.  sctp_stream_init() then frees the extension of every removed stream.  The sender resumes with the stream that it checked before the wait.  If the peer removed that stream, sctp_outq_tail() later dereferences its NULL extension.  Fatal-oops policies then panic the host.  KASAN: null-ptr-deref in range [0x38-0x3f] RIP: sctp_outq_tail+0x49e/0xaa0 Call Trace:  sctp_primitive_SEND  sctp_sendmsg_to_asoc  sctp_sendmsg  A range check alone is insufficient.  Stream reconfiguration can grow the output count again while the lock is released without recreating extensions freed by the earlier shrink.  The stream can then be in range while its extension remains NULL.  The send-buffer wait has the same issue.  Factor the range and extension checks into a helper and repeat both after each send-path wait that drops the socket lock.  Once the lock is reacquired, the validation remains stable through data creation and queueing.  If validation fails after the connect wait, the auto-created association is already established.  Return ESRCH so the existing caller path keeps it under state-machine ownership instead of freeing it directly, which would leave protocol, counter and socket state inconsistent.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99166",
                        "url": "https://ubuntu.com/security/CVE-2026-99166",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net: rds: fix uninitialized trans dereference in CM event handler  rds_rdma_cm_event_handler_cmn() assigns trans only when the RDMA device is an InfiniBand CA (RDMA_NODE_IB_CA).  On any other device type, e.g. an iWARP RNIC such as siw, trans stays uninitialized, but the event switch dereferences it: unconditionally in the RDMA_CM_EVENT_CONNECT_REQUEST case via trans->cm_handle_connect(), and (with a connection context) in the ROUTE_RESOLVED and ESTABLISHED cases.  An RDS listener on an iWARP device therefore crashes the kernel as soon as a connect request arrives: with CONFIG_INIT_STACK_ALL_ZERO the wild load becomes a NULL dereference at offset 0xa0 (&trans->cm_handle_connect) in the iw_cm_wq workqueue.  GCC masks the bug in default builds by folding the uninitialized load into &rds_ib_transport; Clang-built kernels take the real uninitialized path and oops.  The active side can land on a non-IB device too: the id that rds_ib_conn_path_connect() creates is not restricted to a node type, so rdma_resolve_addr() binds it to whichever device serves the local address, and an iWARP RNIC on the same netdev qualifies.  The crash there is different: resolving a route on an iWARP id never fills in cm_id->route.path_rec, and the ROUTE_RESOLVED case writes path_rec[0].sl before it calls into the transport.  The iWARP transport was dropped long ago and IB is the only transport left, so make that explicit: initialize trans to &rds_ib_transport at declaration, drop the conditional assignment, reject a connect request that arrives on a non-IB device, and drop a connection whose address resolved to one instead of resolving a route on it.  The rejection is limited to RDMA_CM_EVENT_CONNECT_REQUEST on purpose: a non-zero return from the handler makes rdma_cm destroy the id the event was delivered on, which is right for the request's freshly created id but would free a connection id that RDS still owns for any other event.  On the active side the id stays ic->i_cm_id and the connection's shutdown destroys it, so that case returns 0.  [achender: reject only on RDMA_CM_EVENT_CONNECT_REQUEST instead of  bailing out for every event on a non-IB device, so that rdma_cm does  not destroy connection ids RDS still tracks; drop a connection whose  address resolved to a non-IB device before a route is resolved on it;  changelog adjusted]",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99167",
                        "url": "https://ubuntu.com/security/CVE-2026-99167",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net/sched: fix use-after-free in __tcf_action_put()  __tcf_action_put() decrements the reference count before decrementing the binding count. Another thread can free the action between these operations, causing the binding-count update to access freed memory. KASAN reports it as:    BUG: KASAN: slab-use-after-free in __tcf_action_put+0x327/0x340   Write of size 4 at addr ff11000000d46420 by task tc-put-pause/64  Hold the action IDR mutex across both counter updates and IDR removal, keeping cleanup outside the lock.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99175",
                        "url": "https://ubuntu.com/security/CVE-2026-99175",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  fsnotify: prevent mark additions during connector teardown  fsnotify_destroy_marks() keeps a reference to its current mark while it drops conn->lock to destroy the mark. This stabilizes the forward-walk cursor, but does not prevent a new mark from being inserted before it. For example, an inotify watch re-added after IN_IGNORED sorts before the old, detached mark for the same group. The walk can miss the replacement and then detach the entire connector from the object.  The replacement is still on its group's marks_list and, for inotify, in the watch IDR. The group mutex no longer protects the connector's object from disappearing. An unprivileged fdinfo read racing the final detach can consequently call igrab(NULL):    BUG: KASAN: null-ptr-deref in igrab+0x24/0x100   Write of size 4 at addr 0000000000000148   Call Trace:    igrab+0x24/0x100    inotify_show_fdinfo+0x1dc/0x5e0    seq_show+0x397/0x690  Set a DESTROYING flag under conn->lock before starting the walk, and reject new marks on that connector with -ENOENT. The existing add-mark error paths undo the temporary group-list entry and the backend's watch allocation. Do not wait for teardown while holding the group mutex, which the destroyer needs. Once the old connector is detached, an add can install a fresh connector as before.  This closes the insertion race for all object types using the common connector teardown, without changing the mark reference or SRCU lifetime rules.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99176",
                        "url": "https://ubuntu.com/security/CVE-2026-99176",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  KVM: nVMX: Reset MMU back to the root MMU if loading L2 state fails for !VM-Entry  Reset the vCPU's MMU pointer back to the root MMU if loading L2 state fails in the \"not from VM-Entry\" case, i.e. when emulating RSM or handling KVM_SET_NESTED_STATE.  Failure to unwind the MMU pointer results in KVM trying to run L1 with a nested MMU, and is especially problematic if the vCPU manages to free its nested state before the VM crashes.  Constructing the root for a nested EPT MMU goes through vmcs12, which is dynamically allocated/freed when nVMX is enabled/disabled.  And so if the nested state is freed with the MMU still pointing at the nested MMU, KVM will hit a NULL pointer deref when attempting to get L1=>L2 EPTP.    BUG: kernel NULL pointer dereference, address: 0000000000000078   #PF: supervisor read access in kernel mode   #PF: error_code(0x0000) - not-present page   PGD 114a2d067 P4D 111743067 PUD 11141f067 PMD 0   Oops: Oops: 0000 [#1] SMP   CPU: 20 UID: 1000 PID: 1272 Comm: nested_tdp_faul Not tainted 7.3.0-rc4-8c89f11d1a99b-sink-vm #1914 PREEMPTLAZY   Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015   RIP: 0010:nested_ept_get_eptp+0xb/0x10 [kvm_intel]   Call Trace:    <TASK>    kvm_mmu_load+0xcd/0x870 [kvm]    kvm_arch_vcpu_ioctl_run+0x18f5/0x1f80 [kvm]    kvm_vcpu_ioctl+0x2c7/0x970 [kvm]    __x64_sys_ioctl+0x90/0xd0    do_syscall_64+0x9c/0x4d0    entry_SYSCALL_64_after_hwframe+0x4b/0x53   RIP: 0033:0x47491b    </TASK>   Modules linked in: kvm_intel kvm irqbypass   CR2: 0000000000000078   ---[ end trace 0000000000000000 ]---   RIP: 0010:nested_ept_get_eptp+0xb/0x10 [kvm_intel]  [sean: write changelog]",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99181",
                        "url": "https://ubuntu.com/security/CVE-2026-99181",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  autofs: ignore notification errors from a replaced pipe  autofs_notify_daemon() takes a reference to the current notification pipe under wq_mutex, then drops the mutex before writing the request. The write can block while the daemon enters catatonic mode and installs a replacement pipe.  If the old pipe's reader is then closed, the delayed write returns -EPIPE and the generic error path enters catatonic mode again. That transition acts on the current superblock state, closes the replacement pipe, and releases the new daemon generation's wait queues.  Only enter catatonic mode when the pipe which failed is still the current pipe. Factor the already-locked transition so the identity check and state change are atomic with respect to another replacement.  This was reproduced on v7.3-rc5-337-gff47652a4b66c in a local QEMU guest. An unprivileged UID 65534 lookup filled the old packet pipe before a normal CATATONIC/SETPIPEFD restart. On the unmodified kernel, the new pipe received HUP and both a pending victim lookup and a later lookup failed with ENOENT in two out of two fresh-mount runs.  With this change, the new pipe remained active, received an intact 304-byte request, and both victim lookups completed in two out of two runs. Normal lookup and restart-without-a-blocked-writer controls passed. No KASAN, oops, refcount, or lock diagnostic was observed. A source reproducer and complete local logs are available privately on request.  The demonstrated impact is limited to denial of a shared autofs service during a legitimate daemon restart. No memory corruption, information leak, privilege escalation, or code execution primitive was observed.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99201",
                        "url": "https://ubuntu.com/security/CVE-2026-99201",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  netlink: avoid hashing the network namespace pointer  The netlink rhashtable key includes a raw struct net pointer and a user-controlled port ID. Both /proc/net/netlink and socket diagnostics expose the table's bucket order. By binding and rebinding chosen NETLINK_USERSOCK port IDs, an unprivileged reader can distinguish equal buckets and recover the low bits of the Jenkins hash. Its 32-bit seed and the limited set of kernel-image slides can then be searched offline to recover the address of init_net.  Use the namespace's unique, non-address net_cookie in the comparison key instead. It is assigned before the per-net initializers run and remains unchanged for the namespace's lifetime. The lookup key and object hash are still built by netlink_compare_arg_init(), keeping lookup, insertion, removal and rehashing consistent while preserving namespace separation. Neither public table walker needs to change.  Reading the socket's namespace cookie in netlink_compare() is safe under RCU, including during namespace teardown. netlink_release() removes the socket from the hash table and defers its final put with call_rcu(). cleanup_net() runs the per-net exit methods and waits for outstanding RCU callbacks with rcu_barrier() before freeing namespace storage.  Unlike ns.ns_id, net_cookie is also available and initialized during setup_net() in older stable kernels, making the change straightforward to backport to v5.15 and later.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99203",
                        "url": "https://ubuntu.com/security/CVE-2026-99203",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  pipe: preserve existing fasync readers on writer setup failure  F_SETFL and FIOASYNC decide whether to invoke ->fasync() before pipe_fasync() takes pipe->mutex. Two enables of one O_RDWR FIFO can therefore both enter the callback.  fasync_helper() allocates before checking for an existing entry. If the first enable installs both entries, a second enable can update the reader entry and then fail the allocation for the writer entry. The error path removes the pre-existing reader entry, clearing FASYNC while the writer entry remains registered. __fput() then skips ->fasync(), so a later pipe notification can dereference the freed file or its f_owner. An unprivileged memory-pressure reproducer triggers a KASAN slab-use-after-free in send_sigio() through this path.  Keep the reader helper's result and undo the registration only if this call added it. The pipe mutex serializes changes to both lists, so a failed new registration still removes its reader, while a failed duplicate preserves the existing registrations and FASYNC. Successful duplicate enables continue to update fa_fd as before.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99204",
                        "url": "https://ubuntu.com/security/CVE-2026-99204",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ocfs2/dlm: Protect the recovery list during debugfs reads  Recovery participant records must remain alive while debug_state_print() walks reco.node_data and formats their fields. The formatter holds dlm->spinlock, but the recovery participant list is protected by dlm_reco_state_lock. In particular, dlm_destroy_recovery_area() detaches the list under dlm_reco_state_lock and frees the detached records after releasing it. A concurrent debugfs open can therefore read freed memory.  Protect the participant traversal and field reads in debug_state_print() with dlm_reco_state_lock, matching the existing list writers. This also serializes the traversal against list_add_tail() during recovery-area initialization. Make the existing lock available to the debug code through dlmcommon.h; the lock remains internal to the OCFS2 DLM module.  Release dlm->spinlock after formatting the other domain state and before acquiring dlm_reco_state_lock, so the debug reader does not nest the two locks. Leave recovery list insertion, detachment and freeing unchanged.  KASAN report as below:      BUG: KASAN: slab-use-after-free in debug_state_open+0x1169/0x12d0     Read of size 4 at addr ffff88810662ef80 by task dlm-state-stres/896      CPU: 1 UID: 0 PID: 896 Comm: dlm-state-stres Not tainted 7.3.0-rc4-next-20260921-pmb-ocfs2-functional-v1+ #1 PREEMPT(lazy)     Hardware name: QEMU Ubuntu 24.04 PC v2 (i440FX + PIIX, arch_caps fix, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014     Call Trace:      <TASK>      dump_stack_lvl+0x93/0xd0      print_report+0xce/0x630      ? debug_state_open+0x1169/0x12d0      ? srso_alias_return_thunk+0x5/0xfbef5      ? __virt_addr_valid+0x20e/0x420      ? debug_state_open+0x1169/0x12d0      kasan_report+0xe0/0x110      ? debug_state_open+0x1169/0x12d0      debug_state_open+0x1169/0x12d0      ? __pfx_debug_state_open+0x10/0x10      full_proxy_open_regular+0x193/0x310      do_dentry_open+0x595/0x12d0      ? __pfx_full_proxy_open_regular+0x10/0x10      vfs_open_consume+0xd1/0x400      ? srso_alias_return_thunk+0x5/0xfbef5      path_openat+0x18d0/0x2020      ? __pfx_path_openat+0x10/0x10      do_file_open+0x21e/0x470      ? __pfx_do_file_open+0x10/0x10      ? _raw_spin_unlock+0x23/0x40      ? srso_alias_return_thunk+0x5/0xfbef5      ? alloc_fd+0x3a6/0x6b0      do_sys_openat2+0xf4/0x1b0      ? __pfx_do_sys_openat2+0x10/0x10      ? srso_alias_return_thunk+0x5/0xfbef5      ? __fput+0x5b5/0xa60      __x64_sys_openat+0x136/0x1e0      ? __pfx___x64_sys_openat+0x10/0x10      do_syscall_64+0x114/0x620      entry_SYSCALL_64_after_hwframe+0x77/0x7f     [Register dump omitted.]      </TASK>      Allocated by task 880:      kasan_save_stack+0x33/0x60      kasan_save_track+0x14/0x30      __kasan_kmalloc+0xaa/0xb0      __kmalloc_cache_noprof+0x28d/0x610      dlm_remaster_locks+0x147/0x1d90      dlm_do_recovery+0xde1/0x1580      dlm_recovery_thread+0x109/0x300      kthread+0x351/0x460      ret_from_fork+0x659/0x940      ret_from_fork_asm+0x1a/0x30      Freed by task 880:      kasan_save_stack+0x33/0x60      kasan_save_track+0x14/0x30      kasan_save_free_info+0x3b/0x60      __kasan_slab_free+0x5f/0x80      kfree+0x308/0x580      dlm_destroy_recovery_area+0x285/0x460      dlm_remaster_locks+0x17c4/0x1d90      dlm_do_recovery+0xde1/0x1580      dlm_recovery_thread+0x109/0x300      kthread+0x351/0x460      ret_from_fork+0x659/0x940      ret_from_fork_asm+0x1a/0x30      The buggy address belongs to the object at ffff88810662ef80      which belongs to the cache kmalloc-32 of size 32     The buggy address is located 0 bytes inside of      freed 32-byte region [ffff88810662ef80, ffff88810662efa0)      [Page and memory-state dumps omitted.]",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99206",
                        "url": "https://ubuntu.com/security/CVE-2026-99206",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  scsi: target: iscsi: Fix race in discovery auth updates  Separate configfs opens can concurrently update the discovery AuthMethod parameter. Both callers may free the same value in iscsi_update_param_value(), causing a double-free.  Protect the lookup and replacement with the discovery TPG access lock, as used by the other TPG configfs parameter updates.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99211",
                        "url": "https://ubuntu.com/security/CVE-2026-99211",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  netlink: reset skb headers before unicast and multicast filtering  Socket filters can use SKF_NET_OFF and SKF_LL_OFF to read relative to an skb's network and MAC headers. Netlink producers may reserve headroom without resetting those headers, allowing a receiving socket's filter to read data before the initialized message.  For example, IWPM HELLO replies are allocated with dev_alloc_skb(), which reserves NET_SKB_PAD bytes. An unprivileged NETLINK_RDMA user can attach a classic socket filter and disclose this headroom through the length of the delivered reply. The resets in netlink_dump() do not help because IWPM sends a separately allocated skb through netlink_unicast().  Reset both headers before running the receiver's filter in unicast and broadcast delivery, as is already done for dump skbs. This also covers other netlink producers that reserve headroom without changing their allocation or message-building code.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99212",
                        "url": "https://ubuntu.com/security/CVE-2026-99212",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net/rds: don't let the rdma_cm destroy an id RDS still owns on route failure  rds_rdma_cm_event_handler_cmn() hands the return value of rdma_resolve_route() straight back to the rdma_cm on RDMA_CM_EVENT_ADDR_RESOLVED.  A synchronous failure there - -ENOMEM from the route work allocation, an SA query that cannot be set up, a RoCE route with no usable device - makes addr_handler() destroy the id the event was delivered on.  That id is ic->i_cm_id, and nothing clears the pointer: the connection sits in RDS_CONN_CONNECTING with a freed id until its shutdown calls rdma_disconnect() and rdma_destroy_id() on it.  The ROUTE_RESOLVED case already avoids this: rds_ib_cm_initiate_connect() forces a zero return while ic->i_cm_id == cm_id, as the comment there explains.  Do the same here - drop the connection and return 0 - so the id stays RDS's to destroy from the shutdown, and the reconnect gets a fresh one.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99213",
                        "url": "https://ubuntu.com/security/CVE-2026-99213",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  vsock: treat TCP_CLOSING as once-established  Handle the TCP_ESTABLISHED -> TCP_CLOSING transition on OP_RST, which can race with the connect loop. Immediately break and return 0 on ESTABLISHED/CLOSING. The return value of connect() should reflect what happened up to the point the connection was established or failed. Events that occur afterwards must not affect it. E.g. even if OP_RW has already set sk_err, connect() should still return 0, not ENOBUFS because of it. Adapt the inaccurate comment above signal_pending().  Resetting a socket that is still present in connected_table can lead to memory corruption. The reporter noted lost transports for in-flight skbs, and I have reproduced crashes caused by re-insertion into connected_table.    list_add double add: new=, prev=, next=.   kernel BUG at lib/list_debug.c:35!   Oops: invalid opcode: 0000 [#1] SMP KASAN NOPTI   Workqueue: vsock-loopback vsock_loopback_work   RIP: 0010:__list_add_valid_or_report+0x11f/0x130   Call Trace:    vsock_insert_connected.cold+0xe/0x13    virtio_transport_recv_pkt+0x10e9/0x1460    vsock_loopback_work+0x305/0x480    process_one_work+0xe4c/0x1560    worker_thread+0x4f1/0xd60    kthread+0x36e/0x470    ret_from_fork+0x47b/0x6b0    ret_from_fork_asm+0x1a/0x30  This fix is supplementary to commit 002541ef650b (\"vsock: Ignore signal/timeout on connect() if already established\"). Details under Link.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99216",
                        "url": "https://ubuntu.com/security/CVE-2026-99216",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  Drivers: hv: Don't reset VMBus connection state on error/exit paths  In two places, current code forces vmbus_connection.conn_state to DISCONNECTED prior to calling vmbus_disconnect(). But vmbus_disconnect() calls vmbus_initiate_unload(), which unloads the VMBus connection only if the conn_state is CONNECTED. Consequently, the connection remains and the Hyper-V host might continue to send messages or post VMBus interrupts.  The problem was introduced in commit 74347a99e73ae (\"x86/Hyper-V: Unload vmbus channel in hv panic callback\"), in that vmbus_initiate_unload() started checking the current connection state before doing the unload. This commit removed some occurrences where conn_state was forced to DISCONNECTED, but these two remained, apparently due to an oversight at the time.  Fix this by not forcing conn_state to DISCONNECTED during VMBus exit, or if a failure occurs when establishing the connection in the first place. Whatever value conn_state has at the time is then read by vmbus_initiate_unload() to determine if there is a connection to be unloaded.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2022-50167",
                        "url": "https://ubuntu.com/security/CVE-2022-50167",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  bpf: fix potential 32-bit overflow when accessing ARRAY map element  If BPF array map is bigger than 4GB, element pointer calculation can overflow because both index and elem_size are u32. Fix this everywhere by forcing 64-bit multiplication. Extract this formula into separate small helper and use it consistently in various places.  Speculative-preventing formula utilizing index_mask trick is left as is, but explicit u64 casts are added in both places.",
                        "cve_priority": "high",
                        "cve_public_date": "2025-06-18 11:15:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99082",
                        "url": "https://ubuntu.com/security/CVE-2026-99082",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  KVM: x86: Use active memslots for the per-vCPU MMIO cache  KVM tags the per-vCPU MMIO cache with a memslot generation so that a memslot update invalidates cached MMIO information.  Both the fill and validation paths use kvm_memslots(), which unconditionally selects address space 0, even when the vCPU is running in SMM and using address space 1.  Commit 56f17dd3fbc4 (\"kvm: x86: fix stale mmio cache bug\") added the memslot generation to the cache key so that a memslot update could not leave a stale entry valid.  When commit 699023e23965 (\"KVM: x86: add SMM to the MMU role, support SMRAM address space\") added the SMM address space, these helpers were not converted to use the active memslots.  Consequently, an update to the SMM memslots can leave an entry from the old SMM address space apparently valid after the vCPU returns to the normal address space.  A guest can then cause an access to valid RAM at the same GFN to be returned to userspace as KVM_EXIT_MMIO.  Completing that exit through the VMM's RAM address space writes the backing page without going through KVM's write-tracking path.  If the page backs a nested EPT table, KVM can continue using shadow translations derived from the old contents.  The WARN_ON_ONCE() in kvm_mmu_write_protect_fault() catches this invalid cache and memslot combination.  Use the vCPU's active memslots when caching and validating the entry. Memslot generations are unique across address spaces, so the generation also distinguishes the normal and SMM views.  This matches the MMIO SPTE cache, which already uses kvm_vcpu_memslots().  On an unpatched current-mainline kernel, a regression test that fills the cache in SMM and updates only the SMM memslots fails the intended RAM write and triggers the kvm_mmu_write_protect_fault() warning.  With this change, the same test completes the RAM write without a warning.  The x86/smm_test, set_memory_region_test, and memslot_modification_stress_test selftests also pass.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99083",
                        "url": "https://ubuntu.com/security/CVE-2026-99083",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ksmbd: fix heap out-of-bounds write in krb5_authenticate()  In krb5_authenticate(), out_len is calculated to determine available headroom in response_buf for the incoming Kerberos AP-REP token. However, when SMB2_SESSION_SETUP is processed as a non-first element of a compounded SMB2 request, the calculation omits work->next_smb2_rsp_hdr_off.  This causes out_len to overstate remaining buffer headroom by the cumulative size of prior responses in the compound chain. Consequently, the length check in ksmbd_krb5_authenticate() (*out_len <= resp->spnego_blob_len) passes erroneously, allowing memcpy() to write the AP-REP blob past the end of response_buf into adjacent kernel heap memory.  Fix this by subtracting work->next_smb2_rsp_hdr_off when computing out_len, ensuring it accurately reflects physical remaining buffer space.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98977",
                        "url": "https://ubuntu.com/security/CVE-2026-98977",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  namespace: handle mount locking for automounts correctly  If mounts are propagated across user namespaces, attach_recursive_mnt() locks every copy of the source mount to protect overmounts from vanishing and revealing the underlying files or directories.  The user namespace is taken from the caller's mount namespaces since this is where the mounts end up. Except, that's not always true. Automounts may legitimately get popped in by tasks located in a different mount and user namespace during path lookup.  Then check doesn't make sense at that point. The copy in the namespace of the parent - which may be the host's - is now locked and the host cannot change the flags of its own mounts anymore.  Here's the reproducer:  - host has debugfs mounted nosuid,nodev,noexec and shared - tracefs automount below it is not yet active - hand a child process a directory descriptor on that mount - child process enters auser and mount namespace - child process' namespace now holds a locked copy of the host's debugfs   mount that receives propagation from it - child process stats \"tracing/.\" through the descriptor - lookup runs on the host's mount so the automount lands below the host's mount - propagation puts a copy below the child's copy - both try to clear the flags on the mount they got, with a bind remount:      host, on its own automount:            MS_REMOUNT|MS_BIND = EPERM     child, on the copy in its namespace:   MS_REMOUNT|MS_BIND = 0  So the lock landed on the host's mount instead of the child's copy. Congrats. So we need to compare with the owner of the namespace the mount actually gets mounted on. For all regular cases that is the caller's mount namespace and so nothing changes.  Detached trees in anonymous mount namespaces by be handed over via SCM_RIGHTS or inherited in other ways on purpose so the attaching task's mount namespace is authoritative, not the creator of the detached tree.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98992",
                        "url": "https://ubuntu.com/security/CVE-2026-98992",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  namespace: don't copy an unmounted mount tree  may_copy_tree() accepts a mount whose root is an nsfs or pidfs file before it checks whether that mount is mounted. This exception exists for nsfs and pidfs mounts. They are part of no mount namespace so neither check_mnt() nor is_mounted() would let them through and bind-mounting a nsfsfd or a pidfd wouldn't work.  Problem is that exception also admits a bind mount of such a file when it was lazily unmounted and is only kept alive by a file descriptor:    mount --bind /proc/self/ns/net /tmp/x   exec 3< /tmp/x   umount -l /tmp/x   mount --rbind /proc/self/fd/3 /tmp/y  With MS_REC or AT_RECURSIVE copy_tree() doesn't stop at the unmounted mount. It copies every mount that stayed attached to it as well. So if you have a bunch of overmounts over the nsfsfd or the pidfd the whole unmounted stack is copied. That's a bug.  So refuse to walk an unmounted tree. Copying its root alone stays possible. So a bind mount of a namespace that is gone can still be recreated from a file descriptor on the old one. The file descriptor pins that mount and its root and __has_locked_children() only reads the direct children which don't leave the parent's list without namespace_sem. The internal mounts carry MNT_NS_INTERNAL instead of NULL and are still walked. Copying an unmounted tree recursively fails with EINVAL.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98981",
                        "url": "https://ubuntu.com/security/CVE-2026-98981",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  namespace: unhash a dentry before detaching the mounts on it  unlink(), rmdir() and rename() remove the entry from the filesystem, call detach_mounts() on the entry with the inode locked and then call d_delete() once the inode is unlocked.  The thing is that between detach_mounts() and d_delete() the dentry is still hashed and positive. But after detach_mounts() nothing covers the dentry anymore. A lookup that finds this dentry in the dcache can uncover what the mounts hid.  That's a problem when unlinking files or directories that are mountpoints in other mount namespaces. Everybody who had the underlying entry covered can race the detach_mount() call until d_delete() has run.  The race window isn't all that small. It encompasses namespace_unlock() with a full synchronize_rcu_expedited() grace period and the inode_unlock() of the entry.  In my experiments three walkers that kept trying read an overmounted file in 11938 of the 16140 unlinks that removed its mountpoint from a bind mount of the filesystem within a minute.  Fun fact, d_invalidate() has the same ordering problem but gets it right. It unhashes the dentry first and detaches the mounts afterwards. Let's do the same in __detach_mounts():  - A lookup that hasn't found the dentry yet misses it in the dcache and   waits for the directory lock that the caller holds until the name is   gone for good.  - A lockless lookup that found it already fails the mount_lock check   while the dentry still counts as a mountpoint and the d_seq check once   it doesn't, and retries.  This fixes the lockless path. We still need to fix the reference count lookup in a follow-up patch.  So d_drop() the dentry. The dentry stays positive and held but can't be found anymore. Then proceed with the detach and unlink.  Reproducer:  The reads were counted with the program below, three walkers for 60 s in a VM with 4 CPUs. The race window is stretched with the debug patch pasted here. fs.detach_race_walk_us sleeps in lookup_fast() once it found a mountpoint dentry and before its mounts are crossed. fs.detach_race_unlink_us sleeps in vfs_unlink() between detach_mounts() and d_delete().    // SPDX-License-Identifier: GPL-2.0   /*    * unlink_covered: unlink a file that is a mountpoint in a detached copy of    * its mount, against lookups that open it through that copy.    *    * A is a tmpfs with the file f1 (content SECRET_F) and the plain file    * MARK_A. A' is an open_tree(OPEN_TREE_CLONE) copy of A with MARK_A bound    * on A'/f1, held through an O_PATH fd on its root once the tree fd is    * closed. Walkers open f1 through that fd while the driver unlinks A/f1,    * where nothing is mounted on it. A walker may read MARK_A or get ENOENT.    * A read of SECRET_F is a hit: the name was found after its mount was    * gone. The lockless walks use openat2(RESOLVE_CACHED).    *    * usage: unlink_covered [-t seconds] [-w walkers]    */   #ifndef _GNU_SOURCE   #define _GNU_SOURCE   #endif   #include <errno.h>   #include <fcntl.h>   #include <pthread.h>   #include <stdatomic.h>   #include <stdio.h>   #include <stdlib.h>   #include <string.h>   #include <unistd.h>   #include <sys/mount.h>   #include <sys/stat.h>   #include <sys/syscall.h>   #include <linux/openat2.h>    #ifndef __NR_open_tree   #define __NR_open_tree 428   #endif   #ifndef __NR_move_mount   #define __NR_move_mount 429   #endif   #ifndef __NR_openat2   #define __NR_openat2 437   #endif   #ifndef OPEN_TREE_CLONE   #define OPEN_TREE_CLONE 1   #endif   #ifndef OPEN_TREE_CLOEXEC   #define OPEN_TREE_CLOEXEC O_CLOEXEC   #endif   #ifndef MOVE_MOUNT_F_EMPTY_PATH   #define MOVE_MOUNT_F_EMPTY_PATH 0x00000004   #endif    #define WORK \"/tmp/uc\"   #define ADIR WORK \"/A\"    static int duration = 60, nwalkers = 3;   static atomic_int stop, writer_waiting;   static pthread_rwlock_t cur_lock = PTHREAD_RWLOCK_INITIALIZER;   static int cur_fd = -1;\t\t/* the root of A', -1 wh ---truncated---",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99005",
                        "url": "https://ubuntu.com/security/CVE-2026-99005",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  drm/i915/gt: Unmask interrupts only when ACTIVE is true  There is a small race window between intel_rps_boost() reading a stale ACTIVE state and queuing rps->work, where ACTIVE may be changed via asynchronous calls triggered by wakeref drop. This means that rps_work() could be triggered after the GT has been parked, so unmasking RPS PM interrupts would happen without holding PM wakelock. This sequence of events may be observed during live_rc6_ctx_wa() selftest:  1) live_rc6_ctx_wa()    -> intel_engine_pm_put()       -> wakeref_put()  ASYNC1) wakeref_put() callback           -> __engine_park()              -> intel_gt_pm_put_async()                 -> intel_gt_pm_put_async_untracked()                    -> intel_wakeref_put_async()  ASYNC2) wakeref_put_async() callback           -> __gt_park()              -> intel_rps_park()                 -> intel_rps_clear_active() [clear ACTIVE]                 WITH INTERRUPTS:                 -> rps_disable_interrupts()                    -> cancel_work_sync(rps->work)                    -> rps_reset_interrupts() [rps->pm_iir = 0]                 WITHOUT INTERRUPTS (TIMER mode):                 -> rps_stop_timer()                    -> cancel_work_sync(rps->work)  2) live_rc6_ctx_wa()    -> intel_gt_wait_for_idle()       -> intel_gt_retire_requests_timeout()          -> dma_fence_wait_timeout()             -> ops->wait() [i915_fence_wait()]                -> i915_request_wait_timeout()                   -> intel_rps_boost()                      -> intel_rps_is_active() [check ACTIVE]                         [OPEN RACE WINDOW]                      -> queue_work(rps->work)          -> retire_requests()             -> i915_request_retire()                -> intel_rps_dec_waiters() [from 1 to 0]  If ASYNC1 and ASYNC2 would execute during [OPEN RACE WINDOW], then:  3) rps_work() executes from the workqueue and may satisfy    \"(!pm_iir && !client_boost)\" test (in TIMER mode rps->pm_iir    is zeroed by an earlier rps_work() call or never gets a new    value after previous intel_rps_unpark() event), so it jumps    to \"out\" label, bypassing intel_rps_is_active() guard and    executes gen6_gt_pm_unmask_irq();  4) GT is parked and runtime PM wakelock is dropped, so only    a raw reference in __gt_park() ->    intel_display_power_put_async() remains for 100ms, then the    MMIO write in gen6_gt_pm_unmask_irq() detects missing    wakelock via assert_rpm_wakelock_held() and emits    \"RPM wakelock ref not held during HW access\" tainting kernel.  Commit 3e7abf814193 (\"drm/i915: Extract GT render power state management\") dropped the \"if (rps->interrupts_enabled)\" guard that gen6_pm_rps_work() had around this unmask in i915_irq.c. INTEL_RPS_ACTIVE brackets the same window, since it is set in intel_rps_unpark() before rps_enable_interrupts() and rps_start_timer() and cleared in intel_rps_park() before rps_stop_timer() and rps_disable_interrupts().  Skip unmasking when RPS is no longer active (reaching unmask operation is independent of INTERRUPT mode). This does not prevent RPS operation from resuming on the next unpark. In interrupt mode, intel_rps_unpark() calls rps_enable_interrupts(), which enables and unmasks the PM interrupts. In timer mode, it calls rps_start_timer(), restarting periodic engine-busyness evaluation. The timer generates software RPS events and queues rps_work() directly, independently of PM interrupt delivery. Neither mode requires the late worker to unmask interrupts while the GT is parked  (cherry picked from commit ca4a6deadad15b91ee083afe445fa6bdbfb68206)",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99007",
                        "url": "https://ubuntu.com/security/CVE-2026-99007",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  drm/fb-helper: defer setup when fbdev_probe() fails, not just on -EAGAIN  __drm_fb_helper_initial_config_and_unlock() calls drm_client_modeset_probe() first, which already fills in each mode_set->mode/num_connectors for every connected output, and only afterwards calls drm_fb_helper_single_fb_probe() to create fb_helper->fb and wire it into those mode_sets via drm_setup_crtcs_fb().  If drm_fb_helper_single_fb_probe() fails with anything other than -EAGAIN (e.g. dev->driver->fbdev_probe() itself fails), the function bails out before drm_setup_crtcs_fb() runs and before setting fb_helper->deferred_setup. The client is left with mode_sets that have a mode and connectors but mode_set->fb == NULL, and nothing marks this fb_helper as needing a retry.  __drm_fb_helper_restore_fbdev_mode_unlocked() only skips committing when fb_helper->deferred_setup is set, so a later .restore() call (drm_lastclose() on process exit, in this report) commits the stale mode_set through drm_client_modeset_commit() -> drm_client_modeset_commit_atomic() -> __drm_atomic_helper_set_config(), which hits WARN_ON(!set->fb).  Mark fb_helper->deferred_setup on any drm_fb_helper_single_fb_probe() failure, not just -EAGAIN, so restore keeps skipping the commit until a later hotplug event successfully re-probes and re-populates mode_set->fb. The real error code is still returned to the caller unchanged.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99019",
                        "url": "https://ubuntu.com/security/CVE-2026-99019",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  scsi: ch: Do not keep references to data transfer element devices  ch_readconfig() looks up the scsi_device of every data transfer element whose SCSI id the changer reports in READ ELEMENT STATUS, and stores it in ch->dt[]. scsi_device_lookup() takes a reference, and nothing ever drops it: ch_destroy() frees the array with kfree(). ch->dt[] is read nowhere else - it only supplies the vendor, model and revision printed in the same loop.  Once such a drive is removed, its scsi_device can never be released. It stays on the host's device list at its address, so a new device there is refused by anything that walks the list - target_core_pscsi reports \"scsi_device_get() failed for H:C:T:L\" - and the low-level driver's module can no longer be unloaded. Only a reboot recovers.  It shows with any changer that reports its drives' ids; with the mhvtl virtual library (IBM 3573-TL personality), each create and remove of a library with four drives leaves four references behind, counted by the module's use count in lsmod. With ch not bound the count is unchanged, and with this patch applied it is unchanged too.  Drop the reference as soon as the name has been printed, and remove the now unused dt[] array. That also removes the array leaked when ch_probe() fails after ch_readconfig().  The same leak was reported with an RFC patch in 2022, which was not merged.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99024",
                        "url": "https://ubuntu.com/security/CVE-2026-99024",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  optee: register TEE devices only once fully initialized  optee_probe() called tee_device_register() on both the client and the supplicant device before the rest of struct optee had been initialized.  tee_device_register() calls cdev_device_add(), which does two things at once: it creates /dev/tee0 and /dev/teepriv0, and it links the device into the tee class so that class_find_device() can find it. From that moment on the device is reachable both from user space via tee_open() and from kernel space via tee_client_open_context(). The only gate in teedev_open() is tee_device_get(), which merely checks that teedev->desc is non-NULL, which was already set by tee_device_alloc(). Therefore, there is effectively no gate at all.  A context opened in that window can run against a struct optee where    - optee->call_queue.mutex is not initialized by optee_cq_init()   - optee->supp mutex and completions is not initialized by     optee_supp_init()   - optee->rpmb_dev_mutex is not initialized yet,   - the message argument cache is not initialized by     optee_shm_arg_cache_init()   - optee->ctx is still NULL  Any open session or invoke during this window takes uninitialized mutexes and dereferences a NULL pointer.  Fix it by moving both tee_device_register() calls down to the point where all of struct optee is set up.  [JW: adding fixes and cc]",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99036",
                        "url": "https://ubuntu.com/security/CVE-2026-99036",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  dm: fix reading free memory in do_resume  When do_resume calls dm_table_get_mode(new_map), the call is done without holding any locks (it only holds a reference to the md). It may be possible that another concurrent ioctl on the same device will swap table after dm_swap_table and before dm_table_get_mode. In this case, dm_table_get_mode(new_map) reads freed memory.  This race condition was triggered by syzbot.  This commit fixes the race by reading mode of the new table before dm_swap_table. Note that new_map is also passed to dm_ima_need_measure, but this function doesn't attempt to dereference it, so this call should be safe.  Note that this is not a security bug because only root can trigger it and the commonly used tools such as lvm or cryptsetup do not call the ioctls concurrently, so that they can't trigger it acceidentally.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98985",
                        "url": "https://ubuntu.com/security/CVE-2026-98985",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  namespace: check the mounts before reading their parents in pivot_root()  path_pivot_root() reads the parents of new_root and of the caller's root and checks whether they are shared before it checks that either mount is in the caller's mount namespace. Only namespace_sem is held. That's fine for a mount that is in the caller's mount namespace.  But new_root can be a file descriptor to a mount that has been unmounted and that only the file descriptor keeps alive. If that mount stayed attached to its parent when it was unmounted nothing pins the parent for it. The final mntput() of the parent unhooks the children under mount_lock alone and frees the parent afterwards:    pivot_root()                     close(fd), last ref on the parent   ------------                     ---------------------------------   ex_parent = new_mnt->mnt_parent                                    mntput_no_expire_slowpath()                                      __umount_mnt(new_mnt)                                    cleanup_mnt()                                      call_rcu()   IS_MNT_SHARED(ex_parent)    BUG: KASAN: slab-use-after-free in path_pivot_root+0xf1a/0x1840   Read of size 4 at addr ffff8881047382f8 by task pivot_widen/157    path_pivot_root+0xf1a/0x1840    __x64_sys_pivot_root+0x165/0x190  The same goes for the caller's root via chroot(). Both outcomes of the check end in EINVAL so nothing but the read itself goes wrong. It's the same thing commit bb4609405752 (\"statmount: read the parent of an unmounted mount under mount_lock\") fixed for statmount().  Check that both mounts are in the caller's namespace before their parents are read. Every path returns EINVAL either way.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98993",
                        "url": "https://ubuntu.com/security/CVE-2026-98993",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  namespace: don't inherit MNT_UMOUNT in clone_mnt()  MNT_UMOUNT gets raised on a mount that umount_tree() or umount_one() has taken out of its namespace. It's never cleared. __detach_mounts() unhooks a mount that carries it instead of unmounting it.  disconnect_mount() lets an unmounted child stay attached only if its parent carries it. propagate_umount() takes it as the sign that a mount is going to be unmounted when it decides what else can be unmounted, where a chain of locked mounts ends and where a for reparenting an overmount.  clone_mnt() copies the flags of the source and only masks MNT_INTERNAL_FLAGS which doesn't include MNT_UMOUNT. A mount that was lazily unmounted but is kept alive by a file descriptor can still be copied when its root is an nsfs or pidfs file because may_copy_tree() accepts those before checking whether the source is mounted at all:    mount --bind /proc/self/ns/net /tmp/x   exec 3< /tmp/x   umount -l /tmp/x   mount --bind /proc/self/fd/3 /tmp/y  The mount on /tmp/y is attached to the caller's namespace with MNT_UMOUNT already set and every copy of it inherits the flag again.  That causes a number of bugs:  - Unlink its mountpoint from a mount namespace where it isn't one.   __detach_mounts() takes it for a mount that was unmounted earlier,   unhooks it from its parent and drops the reference the namespace   holds on it. It stays in the namespace with one reference too few   and as its own parent, so it can't be unmounted through the file   descriptor anymore and the namespace never finds it again. When the   namespace goes away it's leaked and points to a freed struct   mnt_namespace that may_change_propagation() and anon_ns_root() read   on the next propagation change or mount_setattr() through the file   descriptor.  - Make it shared and unmount a peer. trace_transfers() follows the   flag from the peer into it and strips it from its peer group.  - Let a propagated umount reach it. gather_candidates() marks it with   T_UMOUNT_CANDIDATE but never puts it on the candidate list, so the   mark is never cleared and every later propagated umount skips it. If   it's the parent of a locked mount handle_locked() takes it as the   cutoff and commits the locked child that should have stayed and   disconnect_mount() leaves that child attached to it, unmounted under   a mounted parent, which is what disconnect_mount() exists to   prevent. When the namespace goes away umount_tree() visits the child   a second time. And once __detach_mounts() has made it its own parent   reparent() never finds the end of the chain of unmounted parents.  A clone is a new mount that has never been unmounted. Add MNT_UMOUNT to MNT_INTERNAL_FLAGS so clone_mnt() never copies it. And warn when umount_tree() reaches a mount that already has it set.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99002",
                        "url": "https://ubuntu.com/security/CVE-2026-99002",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  drm/vmwgfx: validate pitch coming from userspace  Validate the pitch, alongside the box dimensions before trying to copy data from the underlying surface. Fixes possible out of bounds reads with cursor snooping.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99027",
                        "url": "https://ubuntu.com/security/CVE-2026-99027",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net: team: stop reusing skb after queue override  A nonzero dev_queue_xmit() result does not return ownership of the skb. When an override port's qdisc drops it, the queue override helper used to try another port or the mode transmit op with the freed skb.  Return the handoff decision separately from transmit success. Select only the first override port under RCU and stop after handing it the skb, regardless of the lower transmit result. Keep the existing success and drop accounting.    BUG: KASAN: slab-use-after-free in sk_skb_reason_drop   Write of size 4 by task poc/5040   sk_skb_reason_drop (net/core/skbuff.c:1240)   dev_kfree_skb_any_reason (net/core/dev.c:3470)   ab_transmit (drivers/net/team/team_mode_activebackup.c:49)   team_xmit (drivers/net/team/team_core.c:1849)   __dev_direct_xmit (net/core/dev.c:4934)   Freed by task 5040:   __tcf_kfree_skb_list (net/sched/sch_generic.c:43)   __dev_queue_xmit (net/core/dev.c:4831)   team_xmit (drivers/net/team/team_core.c:1846)   Kernel panic - not syncing: KASAN: panic_on_warn set ...",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-64190",
                        "url": "https://ubuntu.com/security/CVE-2026-64190",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net: team: fix NULL pointer dereference in team_xmit during mode change  __team_change_mode() clears team->ops with memset() before restoring safe dummy handlers via team_adjust_ops(). A concurrent team_xmit() running under RCU on another CPU can read team->ops.transmit during this window and call a NULL function pointer, crashing the kernel.  The race requires a mode change (CAP_NET_ADMIN) concurrent with transmit on the team device.   BUG: kernel NULL pointer dereference, address: 0000000000000000  Oops: 0010 [#1] SMP KASAN NOPTI  RIP: 0010:0x0  Call Trace:   team_xmit (drivers/net/team/team_core.c:1853)   dev_hard_start_xmit (net/core/dev.c:3904)   __dev_queue_xmit (net/core/dev.c:4871)   packet_sendmsg (net/packet/af_packet.c:3109)   __sys_sendto (net/socket.c:2265)  The original code assumed that no ports means no traffic, so mode changes could freely memset()/memcpy() the ops.  AF_PACKET with forced carrier breaks that assumption.  Prevent the race instead of making it safe: replace memset()/memcpy() with per-field updates that never touch transmit or receive.  Those two handlers are managed solely by team_adjust_ops(), which already installs dummies when tx_en_port_count == 0 (always true during mode change since no ports are present).  WRITE_ONCE/READ_ONCE prevent store/load tearing on the handler pointers.  synchronize_net() before exit_op() drains in-flight readers that may still reference old mode state from before port removal switched the handlers to dummies.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-07-20 17:18:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99041",
                        "url": "https://ubuntu.com/security/CVE-2026-99041",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ip6_gre: remove obsolete ERSPAN PMTU update  A tc tunnel_key action can attach a METADATA_IP_TUNNEL dst to an skb, and mirred can redirect it to a native ip6erspan device. The legacy PMTU update in ip6erspan_tunnel_xmit() treats that metadata dst as a route. Since it has no output device, dst_dev(dst)->mtu dereferences NULL.  On v7.2 with KASAN, an initial UID/GID 65534 process with CapEff 0 used self-created user and network namespaces to trigger:    KASAN: null-ptr-deref   RIP: ip6erspan_tunnel_xmit+0x10fc/0x2cc0   Kernel panic - not syncing: Fatal exception in interrupt  The update is obsolete. Commit fe1a4ca0a2b7 (\"ip6_gre: process toobig in a better way\") changed IPv6 GRE Too Big handling to update the underlay route and removed the equivalent block from __gre6_xmit(). ip6_tnl_xmit() then propagates the underlay PMTU to the overlay route.  Remove the stale ERSPAN copy and its now-unused dst variable. This eliminates the metadata-dst dereference and keeps ERSPAN aligned with IPv6 GRE PMTU handling.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-97935",
                        "url": "https://ubuntu.com/security/CVE-2026-97935",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  tracing: Set the trace clock before registering the histogram trigger  hist_register_trigger() puts the trigger on the global named_triggers list in cmd_ops->init(), and only then sets the trace clock:  \tif (data->cmd_ops->init) { \t\tret = data->cmd_ops->init(data); \t\tif (ret < 0) \t\t\tgoto out; \t}  \tif (hist_data->enable_timestamps) { \t\tret = tracing_set_clock(file->tr, hist_data->attrs->clock); \t\tif (ret) { \t\t\thist_err(tr, HIST_ERR_SET_CLOCK_FAIL, errpos(clock)); \t\t\tgoto out; \t\t}  The clock string is not checked anywhere before that call, so a named trigger using common_timestamp with an unknown clock fails after it has already become findable. event_hist_trigger_parse() then frees it without taking it off the list, and the next lookup by name reads the freed object:   ~# cd /sys/kernel/tracing/events/sched/sched_switch  ~# echo 'hist:name=foo:keys=common_pid:ts=common_timestamp:clock=bogus' > trigger  bash: echo: write error: Invalid argument  ~# echo 'hist:name=foo:keys=common_pid' > trigger    BUG: KASAN: slab-use-after-free in find_named_trigger+0xac/0xc0   Read of size 8 at addr ffff88800915d760 by task init/1    find_named_trigger+0xac/0xc0    hist_register_trigger+0xc1/0x900    event_hist_trigger_parse+0x3146/0x6af0    event_trigger_write+0xce/0x160   Freed by task 63:    kfree+0x154/0x420    trigger_kthread_fn+0xfd/0x160  Set the clock before the trigger is registered, so that nothing which can fail runs after it is published, the way commit 6f86bdeab633 (\"tracing: Fix bad hist from corrupting named_triggers list\") moved the registration below the rest of the setup.  tracing_set_filter_buffering() is reference counted, so the init failure path has to drop the reference that the clock block now takes first.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-09-25 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98944",
                        "url": "https://ubuntu.com/security/CVE-2026-98944",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  HID: steam: Refactor registration  This refactors and simplifies the registration/unregistration flow. Since we now only perform registration when the client isn't opened anymore, the logic for handling that can be removed, and the rest of the function streamlined.  We also remove the previous assumption that we have a serial number to show we're registered, replacing it with a single purpose boolean.  In a previous refactor the code for unregistering a battery if later registration steps failed was accidentally left out. As a result, a lingering power_supply object could get left over after the steam object was torn down. This is also fixed here.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98945",
                        "url": "https://ubuntu.com/security/CVE-2026-98945",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  HID: steam: Rearrange teardown sequence  This fixes a narrow window during the teardown sequence where callbacks could still be scheduled during cleanup that would then have a dangling pointer to the now-freed steam struct.  This also puts work canceling for rumble and mode switch in steam_unregister, as that shouldn't persist while the client hdev is open.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2025-40135",
                        "url": "https://ubuntu.com/security/CVE-2025-40135",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ipv6: use RCU in ip6_xmit()  Use RCU in ip6_xmit() in order to use dst_dev_rcu() to prevent possible UAF.",
                        "cve_priority": "high",
                        "cve_public_date": "2025-11-12 11:15:00 UTC"
                    },
                    {
                        "cve": "CVE-2025-38728",
                        "url": "https://ubuntu.com/security/CVE-2025-38728",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  smb3: fix for slab out of bounds on mount to ksmbd  With KASAN enabled, it is possible to get a slab out of bounds during mount to ksmbd due to missing check in parse_server_interfaces() (see below):   BUG: KASAN: slab-out-of-bounds in  parse_server_interfaces+0x14ee/0x1880 [cifs]  Read of size 4 at addr ffff8881433dba98 by task mount/9827   CPU: 5 UID: 0 PID: 9827 Comm: mount Tainted: G  OE       6.16.0-rc2-kasan #2 PREEMPT(voluntary)  Tainted: [O]=OOT_MODULE, [E]=UNSIGNED_MODULE  Hardware name: Dell Inc. Precision Tower 3620/0MWYPT,  BIOS 2.13.1 06/14/2019  Call Trace:   <TASK>  dump_stack_lvl+0x9f/0xf0  print_report+0xd1/0x670  __virt_addr_valid+0x22c/0x430  ? parse_server_interfaces+0x14ee/0x1880 [cifs]  ? kasan_complete_mode_report_info+0x2a/0x1f0  ? parse_server_interfaces+0x14ee/0x1880 [cifs]    kasan_report+0xd6/0x110    parse_server_interfaces+0x14ee/0x1880 [cifs]    __asan_report_load_n_noabort+0x13/0x20    parse_server_interfaces+0x14ee/0x1880 [cifs]  ? __pfx_parse_server_interfaces+0x10/0x10 [cifs]  ? trace_hardirqs_on+0x51/0x60  SMB3_request_interfaces+0x1ad/0x3f0 [cifs]  ? __pfx_SMB3_request_interfaces+0x10/0x10 [cifs]  ? SMB2_tcon+0x23c/0x15d0 [cifs]  smb3_qfs_tcon+0x173/0x2b0 [cifs]  ? __pfx_smb3_qfs_tcon+0x10/0x10 [cifs]  ? cifs_get_tcon+0x105d/0x2120 [cifs]  ? do_raw_spin_unlock+0x5d/0x200  ? cifs_get_tcon+0x105d/0x2120 [cifs]  ? __pfx_smb3_qfs_tcon+0x10/0x10 [cifs]  cifs_mount_get_tcon+0x369/0xb90 [cifs]  ? dfs_cache_find+0xe7/0x150 [cifs]  dfs_mount_share+0x985/0x2970 [cifs]  ? check_path.constprop.0+0x28/0x50  ? save_trace+0x54/0x370  ? __pfx_dfs_mount_share+0x10/0x10 [cifs]  ? __lock_acquire+0xb82/0x2ba0  ? __kasan_check_write+0x18/0x20  cifs_mount+0xbc/0x9e0 [cifs]  ? __pfx_cifs_mount+0x10/0x10 [cifs]  ? do_raw_spin_unlock+0x5d/0x200  ? cifs_setup_cifs_sb+0x29d/0x810 [cifs]  cifs_smb3_do_mount+0x263/0x1990 [cifs]",
                        "cve_priority": "high",
                        "cve_public_date": "2025-09-04 16:15:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-31678",
                        "url": "https://ubuntu.com/security/CVE-2026-31678",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  openvswitch: defer tunnel netdev_put to RCU release  ovs_netdev_tunnel_destroy() may run after NETDEV_UNREGISTER already detached the device. Dropping the netdev reference in destroy can race with concurrent readers that still observe vport->dev.  Do not release vport->dev in ovs_netdev_tunnel_destroy(). Instead, let vport_netdev_free() drop the reference from the RCU callback, matching the non-tunnel destroy path and avoiding additional synchronization under RTNL.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-04-25 09:16:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99088",
                        "url": "https://ubuntu.com/security/CVE-2026-99088",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net: openvswitch: validate transport header presence in set_ipv6_addr  When executing IPv6 address rewrite actions on IPv6 fragments, set_ipv6_addr() calls update_ipv6_checksum(). If parse_ipv6hdr() processes a non-first IPv6 fragment, it sets key->ip.proto to NEXTHDR_FRAGMENT and returns early without calling skb_set_transport_header().  update_ipv6_checksum() unconditionally evaluates skb_transport_offset() on entry before checking l4_proto.  Because skb->transport_header is uninitialized, this triggers a warning under CONFIG_DEBUG_NET=y although it is completely harmless.  Fix this by returning early in update_ipv6_checksum() if l4_proto is NEXTHDR_FRAGMENT. This avoids reading the uninitialized transport offset for fragments while preserving the debug warning for any other protocol where the transport header is unexpectedly missing.  See the syzbot trace:  !skb_transport_header_was_set(skb) WARNING: ./include/linux/skbuff.h:3075 at skb_transport_header include/linux/skbuff.h:3075 [inline], CPU#1: syz-executor463/5635 WARNING: ./include/linux/skbuff.h:3075 at skb_transport_offset include/linux/skbuff.h:3250 [inline], CPU#1: syz-executor463/5635 WARNING: ./include/linux/skbuff.h:3075 at update_ipv6_checksum net/openvswitch/actions.c:361 [inline], CPU#1: syz-executor463/5635 WARNING: ./include/linux/skbuff.h:3075 at set_ipv6_addr+0x462/0x660 net/openvswitch/actions.c:399, CPU#1: syz-executor463/5635 [...] RIP: 0010:skb_transport_header include/linux/skbuff.h:3075 [inline] RIP: 0010:skb_transport_offset include/linux/skbuff.h:3250 [inline] RIP: 0010:update_ipv6_checksum net/openvswitch/actions.c:361 [inline] RIP: 0010:set_ipv6_addr+0x462/0x660 net/openvswitch/actions.c:399 [...] Call Trace:  <TASK>  set_ipv6 net/openvswitch/actions.c:531 [inline]  do_execute_actions+0x557e/0x8600 net/openvswitch/actions.c:1366  ovs_execute_actions+0xde/0x520 net/openvswitch/actions.c:1592  ovs_packet_cmd_execute+0xb4f/0xf10 net/openvswitch/datapath.c:705  genl_family_rcv_msg_doit+0x233/0x340 net/netlink/genetlink.c:1114  genl_rcv_msg+0x614/0x7a0 net/netlink/genetlink.c:1209  netlink_rcv_skb+0x226/0x4a0 net/netlink/af_netlink.c:2572  genl_rcv+0x28/0x40 net/netlink/genetlink.c:1218  netlink_unicast+0x7bd/0x940 net/netlink/af_netlink.c:1361  netlink_sendmsg+0x813/0xb40 net/netlink/af_netlink.c:1916  sock_sendmsg_nosec+0x14e/0x190 net/socket.c:800",
                        "cve_priority": "negligible",
                        "cve_public_date": "2026-10-26 15:16:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98950",
                        "url": "https://ubuntu.com/security/CVE-2026-98950",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  flow_dissector: avoid u16 truncation of hlen in bpf_flow_dissect()  bpf_flow_dissect() sanitizes the offsets returned by the BPF program with clamp_t(u16, ..., hlen).  If hlen is bigger than 65535, the upper bound is truncated before the comparison. For instance, with hlen == 65536, both nhoff and thoff are forced to zero, even if the program returned sane values.  This is the same class of bug as the one fixed in commit 99bda1ecbd56 (\"flow_dissector: avoid u16 truncation of skb->len when computing thoff\"). That fix does not cover the BPF path, because __skb_flow_dissect() returns early when a BPF flow dissector handles the packet.  struct bpf_flow_keys stores nhoff and thoff as u16, so cap hlen to U16_MAX before clamping.  Found by sashiko while reviewing the commit above.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98955",
                        "url": "https://ubuntu.com/security/CVE-2026-98955",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  flow_dissector: avoid u16 truncation of skb->len when computing thoff  __skb_flow_dissect() computes key_control->thoff using:    key_control->thoff = min_t(u16, nhoff, skb ? skb->len : hlen);  min_t(u16, ...) casts both arguments to u16 before comparing them. Whenever skb->len (or hlen) modulo 65536 is smaller than nhoff, the truncated length wins and thoff is set to a bogus small value, even when the dissection succeeded. For example, an IPv4/TCP frame with skb->len == 65540 and nhoff == 34 gets thoff == 4, so callers such as skb_probe_transport_header() point the transport header inside the Ethernet header.  Such skbs are not exotic: - At the time of commit d0c081b49137 (\"flow_dissector: properly cap   thoff field\"), AF_PACKET with PACKET_VNET_HDR could already build GSO   skbs larger than 64KB (MTU checks are skipped for GSO, and   alloc_skb_with_frags() accepted up to MAX_SKB_FRAGS (17) order-0   pages on top of the linear part). - BIG TCP now makes skbs larger than 64KB common. - The following patch makes tun_get_user() dissect IFF_TAP frames   before eth_type_trans() pulls the Ethernet header, so a GSO frame   carrying a 65522..65535 byte L3 packet will be dissected with   skb->len in [65536, 65549].  Compare as u32 instead. If the resulting offset cannot be represented in the u16 key_control->thoff, cap it to U16_MAX and report the dissection as failed rather than silently returning a wrong transport offset. thoff is still set on failure, as some callers (such as eth_get_headlen()) use it regardless of the return value.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99089",
                        "url": "https://ubuntu.com/security/CVE-2026-99089",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ASoC: samsung: i2s: enable op_clk in probe to balance runtime PM  The probe function puts the device into the runtime PM active state with only the \"iis\" bus clock enabled, but it also sets priv->op_clk to the parent of the RCLK_SRC mux without enabling it. The runtime PM suspend callback disables both clocks, so the first runtime suspend after probe disables op_clk once more than it was enabled.  On Exynos5250 Arndale both clocks resolve to the same EXYNOS_I2S_BUS gate, so this triggers the following warning during boot:   WARNING: drivers/clk/clk.c:1270 at clk_core_disable+0xe4/0x23c, CPU#0: kworker/u8:3/45  i2s_bus already disabled  ...  Workqueue: pm pm_runtime_work  Call trace:   ...   clk_core_disable from clk_disable+0x28/0x34   clk_disable from i2s_runtime_suspend+0x58/0x68 [snd_soc_i2s]   i2s_runtime_suspend [snd_soc_i2s] from genpd_runtime_suspend+0xc4/0x298   genpd_runtime_suspend from __rpm_callback+0x48/0x18c   __rpm_callback from rpm_callback+0x4c/0x50   rpm_callback from rpm_suspend+0xf4/0x718   rpm_suspend from pm_runtime_work+0x9c/0xa0   ...  Fix this by enabling op_clk in probe right after getting it, so the clock state matches the runtime PM active state, and by disabling it in remove.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-26 15:16:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98956",
                        "url": "https://ubuntu.com/security/CVE-2026-98956",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ASoC: adau1372: allow sleepy powerdown GPIOs  gpiod_set_value() emits a WARN when the GPIO provider indicates that it can sleep, as is typical for I2C controlled GPIO expanders. Since the powerdown GPIO is only manipulated in process context, use the _cansleep variant instead. This lets the driver use sleepy GPIOs to power off the chip.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98964",
                        "url": "https://ubuntu.com/security/CVE-2026-98964",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  nvmet: use the local P2P device on metadata allocation failure  nvmet_req_alloc_p2pmem_sgls() assigns req->p2p_dev only after the data and metadata SGL allocations succeed. If the data allocation succeeds but the metadata allocation fails, out_free_sg passes req->p2p_dev to pci_p2pmem_free_sgl() before that assignment has taken place.  Pass the local p2p_dev argument instead, so cleanup uses the same PCI device as the successful data allocation.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98967",
                        "url": "https://ubuntu.com/security/CVE-2026-98967",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  cxgb4/ch_ktls: disable softirqs around tid_list erases  chcr_ktls_cpl_act_open_rpl() inserts into tid_list from the receive path using xa_insert_bh().  The array is shared by the adapter's connections and initialized with XA_FLAGS_LOCK_BH.  However, chcr_ktls_dev_del() and the chcr_ktls_dev_add() error path use xa_erase(), which takes the XArray lock without disabling softirqs.  When cleanup runs with softirqs enabled, a receive softirq for another connection on the same CPU can interrupt the erase and spin on the lock held by the interrupted task.  Use xa_erase_bh() at both sites to match the insertion path.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98969",
                        "url": "https://ubuntu.com/security/CVE-2026-98969",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net/sched: em_text: reject unterminated algo before autoload  This is a follow-up to commit 9c572a83037a (\"net/sched: fix potential stack infoleak in em_text_dump()\"), which zero-initialised the dump-side struct. Sashiko pointed at a pre-existing bug that exposed the change-side input-validation gap open.  em_text_change() casts the raw netlink attribute payload to struct tcf_em_text and passes conf->algo, a 16-byte array with no enforced NUL terminator, to textsearch_prepare().  On the TS_AUTOLOAD retry textsearch_prepare() calls request_module(\"ts_%s\", algo); vsnprintf() walks %s until it finds a NUL, so an algo[] with no NUL reads past the array into the adjacent struct fields and payload and feeds those bytes to the usermode helper command line.  This is an out-of-bounds read and a kernel memory disclosure.  Reject the attribute when no NUL exists within TC_EM_TEXT_ALGOSIZ bytes, matching the check xt_string has had since 3ab720881b6e.  Conditions to recreate the bug: - CAP_NET_ADMIN on the target netns (namespace-local via unshare -Urn   is enough) - install clsact on an interface, then add a basic filter with one text   ematch whose algo[] is 16 bytes with no NUL (e.g. \"A\"*16) and   pattern_len at least 1 - the add fails with -ENOENT and the kernel invokes modprobe with a   module name made of \"ts_\" plus the 16 bytes and the adjacent payload",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98970",
                        "url": "https://ubuntu.com/security/CVE-2026-98970",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  drm/vc4: Free the BO cache size list on teardown  vc4_bo_cache_destroy() purges the cached BOs but never frees the size list, leaking it on every unbind.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98971",
                        "url": "https://ubuntu.com/security/CVE-2026-98971",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  gpio: exar: initialize the ID before registering its cleanup  devm_add_action_or_reset() invokes the cleanup action immediately when registering the action fails.  gpio_exar_probe() currently stores the allocated ID in exar_gpio only after registering the action, so that failure makes exar_devm_ida_free() release ID 0.  If the allocated ID is nonzero, this leaks that ID and can free ID 0 belonging to another device.  Store the ID before registering the cleanup action so both the immediate failure path and normal device teardown release the correct allocation.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98979",
                        "url": "https://ubuntu.com/security/CVE-2026-98979",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  namespace: refuse an automount below a mount that is in no namespace  It's possible to add autmounts even when the parent mount isn't in the mount namespace of the caller. The only requirement we have is that the parent mount namespace must not be NULL, i.e., unmounted.  Problem is that clone_private_mount() has MNT_NS_INTERNAL which makes that trivially true. So that passes the test and attach_recursive_mnt() accepts that as a mount point and funny enough, count_mounts() dereferences MNT_NS_INTERNAL. The problem is it is an error pointer...  So we can reach this in userspace via fanotify. A filesystem mark on the lower filesystem of an overlay reports paths on the layer clone and reading the event hands out a descriptor on it. For example with debugfs as the lower layer it goes kaboom:    openat(evfd, \"tracing\", O_DIRECTORY)    Oops: general protection fault   KASAN: null-ptr-deref in range [0x1d0-0x1d7]   RIP: 0010:count_mounts+0x35/0x200    attach_recursive_mnt    finish_automount  And since that sleeping beauty happens under namespace_sem held for writing every mount operation on the system blocks from then on. Congrats.  Use is_mounted() instead which rejects unmounted and internal mounts alike. The open fails with EINVAL just as it did before clone_private_mount() used MNT_NS_INTERNAL.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98984",
                        "url": "https://ubuntu.com/security/CVE-2026-98984",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  dcache: don't put a mountpoint on a dentry that's being removed  rmdir(), unlink() and rename() call dont_mount() on the victim and then detach_mounts() with the victim's inode locked. do_lock_mount() takes the inode lock of the mountpoint and checks cant_mount() so a mount can't show up after detach_mounts().  But attach_recursive_mnt() makes a second mountpoint for the root of the source mount so that the mounts already located at the destination can be put on top of it. No inode is locked for that one and d_set_mounted() only refuses a dentry that is unlinked. Between detach_mounts() and d_delete() the victim is still hashed:    rmrace: b passed dont_mount() and detach_mounts(), sleeping   T2: move_mount(S, /tmp/plcant/x, BENEATH) = 0 errno 0 ()   T1: rmdir(/tmp/plcant/d/b) = 0 errno 0       109 107 0:61 /d/b//deleted /tmp/plcant/x rw,relatime - tmpfs tmpfs rw       108 109 0:63 / /tmp/plcant/x rw,relatime - tmpfs T rw  A bind mount of the directory that's being removed is moved beneath an existing mount while the rmdir() is located between the two calls. The mount ends up on the removed directory and nothing will ever detach it.  Check cant_mount() in d_set_mounted() as well. dont_mount() raises the flag under d_lock before detach_mounts() runs so either the mountpoint is set first and detach_mounts() finds the mount or the flag is seen and the mount is refused.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98990",
                        "url": "https://ubuntu.com/security/CVE-2026-98990",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  namespace: check a submount for references right before unmounting it  shrink_submounts() and mark_mounts_for_expiry() first collect all the mounts they are allowed to unmount and then unmount them.  Whether a mount is busy is decided by propagate_mount_busy() on the tree. But unmounting the first mount changes the tree that the second one propagates into. propagate_umount() moves a surviving overmount off a copy it unmounts and mounts it where the copy was mounted. If that's where the propagated copy of the second victim is looked up the overmount becomes a candidate of the second umount_tree(). It's childless and so trim_one() commits it without looking at its reference count.  So a synchronous umount pulls out a busy mount that is in use somewhere else and marks it MNT_SYNC_UMOUNT while it has users:    umount2(/tmp/plshrink/p1, 0) = 0 errno 0   cwd is (unreachable)  The same two umounts requested one after the other fail with EBUSY. This needs a mount with MNT_SHRINKABLE, i.e., automounted submounts of NFS, AFS and CIFS or the tracefs mount below debugfs. Bind mounts inherit the flag.  Check each mount right before it is unmounted under the same hold of namespace_sem and mount_lock as the umount itself. Make sure that the algorithm stays linear.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99095",
                        "url": "https://ubuntu.com/security/CVE-2026-99095",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  drm/vc4: drain the hangcheck timer and works on V3D unbind  Nothing stops the hangcheck timer that submitted jobs arm, or the job_done_work that the render-done interrupt queues, at teardown: vc4_irq_disable() cancels only overflow_mem_work, and vc4_gem_destroy() runs from the drm-managed release, after vc4_v3d_unbind() has already uninstalled the V3D interrupt and cleared vc4->v3d. A timer still armed by then reads V3D registers through the NULL vc4->v3d pointer, and the late callbacks run on the vc4_dev embedding them after it has been freed.  Drain them in vc4_v3d_unbind(): shut the timer down and cancel reset_work before the interrupt is taken down, because its vc4_irq_reset() re-enables it, then flush job_done_work so that completions queued at teardown still release their jobs.  This issue was found by an in-house static analysis tool.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-26 15:16:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99006",
                        "url": "https://ubuntu.com/security/CVE-2026-99006",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  drm/i915/gem: Prevent overstepping exec array boundary  It is possible for eb_relocate_parse_slow() to call kvfree() on entries outside the original exec array during following scenario inside eb_relocate_parse_slow():  1) eb_copy_relocations() allocates as many as eb->buffer_count    copies for exec entries; 2) eb_parse() appends up to two VMAs, right after incrementing    eb->buffer_count; 3) cleanup under \"out\" label uses this incremented buffer_count    to release relocation pointers from exec array via kvfree(),    not from VMA array.  To amend this problem, ensure that relocation cleanup uses the original exec object count, excluding the VMAs appended by the command parser.  (cherry picked from commit 2a0158925fb943c7ba8f3216e2734952128defc9)",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99008",
                        "url": "https://ubuntu.com/security/CVE-2026-99008",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  Bluetooth: RFCOMM: Fix NULL tty_dev dereference in rfcomm_dev_shutdown  syzbot hit a NULL pointer dereference in rfcomm_dev_shutdown() when an RFCOMM tty is closed.  rfcomm_dev_add() puts the new device on rfcomm_dev_list first and only then registers the tty device and saves it in dev->tty_dev. If that registration fails, dev->tty_dev is never set at all. The device can be looked up in the meantime, so an open() of /dev/rfcommN gets through rfcomm_tty_install() and attaches to it. When that tty is closed again, rfcomm_dev_shutdown() uses dev->tty_dev without checking it:    Oops: general protection fault, probably for non-canonical address   KASAN: null-ptr-deref in range [0x0000000000000040-0x0000000000000047]   RIP: 0010:rfcomm_dev_shutdown+0x48/0xb0 net/bluetooth/rfcomm/tty.c:131   Call Trace:    tty_port_shutdown+0x1bf/0x220 drivers/tty/tty_port.c:372    tty_port_close+0x4e/0x150 drivers/tty/tty_port.c:705    tty_release+0x359/0x1670 drivers/tty/tty_io.c:1718    __fput+0x418/0xa50 fs/file_table.c:512  rfcomm_dev_destruct() already copes with a NULL dev->tty_dev. Add the same check to rfcomm_dev_shutdown(), so the tty device is only moved when it was actually registered.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99010",
                        "url": "https://ubuntu.com/security/CVE-2026-99010",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  Bluetooth: RFCOMM: free the skb when the DLC has no owner  rfcomm_recv_data() hands the skb to d->data_ready() and returns 0 without freeing it, so the callback owns the skb from that point on. The tty implementation frees it when the DLC has been detached from its device:    static void rfcomm_dev_data_ready(struct rfcomm_dlc *dlc,                                     struct sk_buff *skb)   {           struct rfcomm_dev *dev = dlc->owner;            if (!dev) {                   kfree_skb(skb);                   return;           }  The socket implementation returns without freeing it, and the skb is leaked.  A connected DLC can have no owner: rfcomm_sock_destruct() clears d->owner, while the DLC itself stays on the session until it is closed. Data frames that arrive in that window still find d->state == BT_CONNECTED in rfcomm_recv_data() and are handed to the callback, one leaked skb each.  The leak does not stop on its own either.  The remote runs out of credits only once RFCOMM_RX_THROTTLED is set, and for a socket the only place that sets it is rfcomm_sk_data_ready() itself, below the return. rfcomm_process_dlcs() keeps granting credits, so the remote keeps sending and the leak keeps growing.  Free the skb, as the tty side does.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99015",
                        "url": "https://ubuntu.com/security/CVE-2026-99015",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  Bluetooth: hci_sock: Serialize dead-device detachment  Rebinding an HCI socket after its controller is unregistered can race monitor control replay and crash the kernel. hci_sock_bind() clears hci_pi(sk)->hdev and drops the device reference under only the socket lock, whereas send_monitor_control_replay() holds hci_sk_list.lock for reading.  Replay can observe a non-NULL hdev, then bind can clear it and drop the last reference before create_monitor_ctrl_open() reads hdev->id. This can cause a NULL pointer dereference if the pointer is reloaded, or a use-after-free if the old pointer is retained.  The kernel reported:    KASAN: null-ptr-deref in range [0x0000000000000068-0x000000000000006f]   RIP: 0010:create_monitor_ctrl_open+0x579/0x800   Call Trace:    hci_sock_bind+0xd96/0x1190    __sys_bind+0x166/0x200    __x64_sys_bind+0x6d/0xb0    do_syscall_64+0xdd/0x4a0    entry_SYSCALL_64_after_hwframe+0x77/0x7f  The same missing serialization lets hci_send_to_sock() select a socket for the old device and queue its frame after bind has detached the socket or installed a new binding.  Take hci_sk_list.lock for writing when clearing the device pointer and resetting the socket state. This waits for existing replay and delivery readers to finish before detachment and prevents later readers from using the old binding. Keep hci_dev_put() outside the critical section because the final device release can sleep.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99022",
                        "url": "https://ubuntu.com/security/CVE-2026-99022",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  regulator: ltc3676: don't read the write-only HRST and CLIRQ registers  HRST (0x1e) and CLIRQ (0x1f) are write-only command strobes. Writing HRST triggers a hard reset of the chip and writing CLIRQ clears the interrupt; reading them returns nothing useful, and the read itself fires the command.  The result is that a plain register dump resets the board:    cat /sys/kernel/debug/regmap/2-003c/registers  walks every readable register, hits HRST, and the board reboots.  Split the callback back in two so HRST and CLIRQ stay writable but are no longer readable. The readable range is left unchanged (LTC3676_BUCK1 ... LTC3676_IRQSTAT).",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99025",
                        "url": "https://ubuntu.com/security/CVE-2026-99025",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  openvswitch: fix soft lockup in the netlink flow dump  A production compute node carrying a few thousand datapath flows hit a soft lockup inside a single netlink flow dump and panicked.  ovs_flow_cmd_dump() calls ovs_flow_stats_get() for every flow it emits, and that releases stats->lock with spin_unlock_bh() once per CPU that has touched the flow. Every release is a local_bh_enable(), and each one runs the pending softirq backlog in the dumping thread's own context.  The skb bounds the flows one callback emits, but not the softirq work it absorbs. On a CPU that carries the box's packet load the backlog refills as fast as it drains, so the dumping thread becomes that CPU's softirq engine. It never sleeps and it has no reschedule point, so under voluntary preemption nothing can take the CPU away from it: neither the ksoftirqd the kernel woke to take the work over, nor the stopper thread the softlockup detector dispatches to refresh its timestamp.  Hold BH off across the whole callback instead, the way ctnetlink_dump_table() does, so the nested spin_unlock_bh() stop draining softirqs. The loop already runs under rcu_read_lock() and cannot sleep. What it gives up is preemption under CONFIG_PREEMPT, since a BH-off region is not preemptible outside PREEMPT_RT. The region stays short: the skb caps the flows one callback emits, and empty buckets cost no skb space but are each visited once per dump, as the cursor only moves forward. The table grows on insert and shrinks only on flush, so the walk is bounded by the largest flow count the datapath has held. The softirq backlog the callback used to absorb has no bound at all.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99031",
                        "url": "https://ubuntu.com/security/CVE-2026-99031",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net: bridge: avoid recursive multicast port cleanup  br_multicast_sg_del_exclude_ports() removes automatically added STAR_EXCL port groups by calling br_multicast_del_pg(). For S,G entries, that deletion calls back into br_multicast_sg_del_exclude_ports(), so a large number of STAR_EXCL ports consumes one kernel stack frame per port and can hit the stack guard page.  Keep the complete port-group deletion path for cleanup, but suppress the S,G exclude-port cleanup while that helper is already walking the same entry. Normal deletion callers retain the existing behavior.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99032",
                        "url": "https://ubuntu.com/security/CVE-2026-99032",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net/smc: protect clcsock lifetime in smc_getname  smc_getname() dereferences smc->clcsock without holding clcsock_release_lock. Link-group termination can release the CLC socket through smc_close_active_abort() while the SMC socket is still open, for example after shutdown(SHUT_WR).  A getsockname() caller can load smc->clcsock, then the termination worker can clear the pointer and call sock_release() before the caller accesses clcsock->ops or invokes getname(). This causes a use-after-free; if the worker clears the pointer before the load, it causes a NULL dereference. The syscall's file reference keeps the SMC socket alive but does not prevent asynchronous release of its CLC socket.  KASAN reported the following with test-only timing instrumentation:    BUG: KASAN: slab-use-after-free in smc_getname+0x19e/0x1b0   Read of size 8 at addr ffff888109abb4e0 by task poc/103   Call Trace:    smc_getname+0x19e/0x1b0    do_getsockname+0xe5/0x170    __sys_getsockname+0x8c/0x100    Allocated by task 95:    sock_alloc_inode+0x1e/0x280    sock_alloc+0x3d/0x240    __sock_create+0x7e/0x430    smc_create+0x121/0x240    Freed by task 0:    kmem_cache_free+0xcc/0x340    rcu_core+0x50a/0x1850    Last potentially related work creation:    evict+0x446/0x6c0    smc_clcsock_release+0xa8/0xd0    smc_close_active_abort+0x26a/0x3a0    __smc_lgr_terminate.part.0+0x137/0x2e0  Hold clcsock_release_lock across the pointer check and the getname() callback to serialize with smc_clcsock_release(). Return -EBADF if the CLC socket has already been released, preserving the existing peer state check and the callback's return value otherwise.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99033",
                        "url": "https://ubuntu.com/security/CVE-2026-99033",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net/packet: guard the ll header push in packet_rcv_spkt()  packet_rcv_spkt() restores the link layer header with  \tskb_push(skb, skb->data - skb_mac_header(skb));  That subtraction is only meaningful when the device actually has a link layer header.  packet_rcv() and tpacket_rcv() both wrap it in dev_has_header(), which is also the predicate the block comment at the top of the file states the restore in terms of; packet_rcv_spkt() does not.  commit d549699048b4 (\"net/packet: fix packet receive on L3 devices without visible hard header\") introduced the helper and changed the two call sites, and this one stayed behind.  A device without a visible ll header can leave skb->mac_header at the 0xFFFF sentinel that __alloc_skb() initialises it to.  A CAN skb does: init_can_skb() sets pkt_type and ip_summed but does not reset the headers, and commit 9f10374bb024 (\"can: remove private CAN skb headroom infrastructure\") dropped the skb_reset_*_header() calls that used to be there.  skb_mac_header() is then 0xFFFF, the length becomes a large negative number and skb_push() reports it through skb_under_panic() -- from softirq context, so it is a full system panic even with panic_on_oops=0:    skbuff: skb_under_panic: text:ffffffff8bd21bc1 len:-65455 put:-65471 head:... data:... tail:0x50 end:0x180 dev:can0   kernel BUG at net/core/skbuff.c:214!   RIP: 0010:skb_panic+0x50/0x60   Call Trace:    <IRQ>    skb_push+0x38/0x40    packet_rcv_spkt+0xe1/0x170    __netif_receive_skb_core.constprop.0+0x7e8/0xd30    ...   Kernel panic - not syncing: Fatal exception in interrupt  The socket type is reachable: packet_create() accepts SOCK_PACKET alongside SOCK_RAW and SOCK_DGRAM behind the same CAP_NET_RAW check, and neither the socket length nor a capability check keeps it away from a CAN interface.  The missing skb_reset_*_header() calls in init_can_skb() are a regression in their own right and are being fixed separately, but a packet socket should not turn a link layer that did not initialise its mac header into a kernel panic.  Guard the push the way the other two receive paths do.  Tested on v7.3-rc5 under QEMU with a slcan device on a pty, which is the driver RX path: vcan does not reproduce it, because can_send() resets the headers on the way out.  One SOCK_PACKET socket bound to can0 and one frame written into the line discipline panics an unpatched kernel with the trace above; the same image with this patch prints no panic and powers off normally.  Both kernels are this tree, defconfig plus CONFIG_CAN_SLCAN=y, differing only in this hunk.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99034",
                        "url": "https://ubuntu.com/security/CVE-2026-99034",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  mmc: sdhci-sprd: disable runtime PM on remove  sdhci_sprd_probe() enables runtime PM, while sdhci_sprd_remove() does not perform the corresponding runtime PM cleanup.  The probe failure path disables runtime PM before disabling the clocks, but the normal remove path directly disables clocks that are also managed by the runtime PM callbacks. If the device is runtime suspended, those clocks may already be disabled.  Resume the device before removal, disable runtime PM and drop the temporary runtime PM reference before disabling the clocks.  This issue was found by manual code inspection.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99035",
                        "url": "https://ubuntu.com/security/CVE-2026-99035",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  mmc: mtk-sd: Cancel request timeout work on remove  The driver queues req_timeout while a request is active. msdc_request_done() uses cancel_delayed_work(), which does not wait for a timeout callback that has already started.  The timeout callback calls mmc_request_done(), which wakes the request waiter, and then continues to use host->dev_comp and check the SDIO IRQ. During unbind, msdc_drv_remove() can return and the managed mmc_host can be freed before the callback finishes.  KASAN reported use-after-free accesses in msdc_request_done() and msdc_recheck_sdio_irq() in each of three unbind tests.  The same tests completed without a kernel diagnostic after this change.  Call cancel_delayed_work_sync() after mmc_remove_host() has stopped new requests and before the driver releases the host resources.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99037",
                        "url": "https://ubuntu.com/security/CVE-2026-99037",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  dm-crypt: reject the lmk IV mode with AEAD ciphers  A \"capi:\" table line that pairs an AEAD cipher with the lmk IV mode, for example \"capi:gcm(aes)-lmk\" with the integrity:28:aead option, causes an oops when it is loaded. lmk sets tfms_count to 64, but crypt_alloc_tfms_aead only allocates one transform, so crypt_setkey reads past the end of the tfms_aead array and calls crypto_aead_setkey on the values it finds there.  lmk exists for compatibility with Loop-AES, which uses CBC, so refuse it with an AEAD cipher rather than allocate 64 AEAD transforms. The check cannot go in crypt_iv_lmk_ctr with the other lmk checks, because the IV constructor runs after crypt_set_key.  Note that this is not a security bug because the memory corruption can only be triggered by root.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99038",
                        "url": "https://ubuntu.com/security/CVE-2026-99038",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  memstick: rtsx_usb_ms: complete requests after eject instead of dropping them  memstick_check() can pass its host->removing check just before rtsx_usb_ms_drv_remove() sets eject/removing. Its next request is then silently dropped: rtsx_usb_ms_request() skips schedule_work() once eject is set, and drv_remove's cancel_work_sync() can also cancel a queued handle_req before it picks the request up. Nobody completes card->mrq_complete.  Once memstick core waits for requests without a timeout (\"memstick: core: wait for request completion before freeing card\"), this hangs removal: memstick_check() never returns and memstick_remove_host() blocks in flush_workqueue():    INFO: task kworker/u10:3:65 blocked for more than 20 seconds.   Workqueue: kmemstick memstick_check    __wait_for_common    memstick_check    INFO: task kworker/1:1:33 blocked for more than 20 seconds.   Workqueue: usb_hub_wq hub_event    __flush_workqueue    memstick_remove_host    rtsx_usb_ms_drv_remove  Never drop a request. rtsx_usb_ms_request() always schedules handle_req, and handle_req fails requests with -ENOMEDIUM once eject is set, without touching the device. drv_remove flushes handle_req instead of cancelling it, and cancels it only after memstick_remove_host(), when no new request can arrive, so it cannot run on a freed host.  The host_mutex drain in drv_remove is removed: handle_req always leaves host->req NULL when it finishes, so the drain never had anything to do, and it would now race with handle_req.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99039",
                        "url": "https://ubuntu.com/security/CVE-2026-99039",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  memstick: core: wait for request completion before freeing card  In memstick_alloc_card() and memstick_set_rw_addr(), wait_for_completion_timeout() is used to wait for device identification and address configuration requests to complete.  The memstick subsystem does not provide an abort or cancellation callback in struct memstick_host for in-flight requests. If wait_for_completion_timeout() expires (for instance, when a USB transfer or command retry is delayed), memstick_alloc_card() returns an error and frees the memstick_dev structure via kfree(card).  However, the host controller driver (such as rtsx_usb_ms) is still running the request asynchronously in worker context. When the transfer eventually finishes, the driver writes into host->req->data, which points to memory inside the already freed card structure. This leads to a KASAN slab-use-after-free write:    BUG: KASAN: slab-use-after-free in ms_read_bytes+0x8fe/0x990   Write of size 1 at addr ffff88813c188079 by task kworker/1:5/5239   Workqueue: events rtsx_usb_ms_handle_req   Call Trace:    ms_read_bytes+0x8fe/0x990 drivers/memstick/host/rtsx_usb_ms.c:450    rtsx_usb_ms_issue_cmd drivers/memstick/host/rtsx_usb_ms.c:477 [inline]    rtsx_usb_ms_handle_req+0x557/0x1a00 drivers/memstick/host/rtsx_usb_ms.c:531    process_one_work+0xac7/0x1b10 kernel/workqueue.c:3396    worker_thread+0x5ef/0xe50 kernel/workqueue.c:3560    kthread+0x373/0x450 kernel/kthread.c:436    Allocated by task 1662:    memstick_alloc_card drivers/memstick/core/memstick.c:383 [inline]    memstick_check+0x2c1/0x10d0 drivers/memstick/core/memstick.c:452    process_one_work+0xac7/0x1b10 kernel/workqueue.c:3396    Freed by task 1662:    kfree+0x20c/0x650 mm/slub.c:6792    memstick_alloc_card drivers/memstick/core/memstick.c:420 [inline]    memstick_check+0x72b/0x10d0 drivers/memstick/core/memstick.c:452    process_one_work+0xac7/0x1b10 kernel/workqueue.c:3396  Host controller drivers (rtsx_usb_ms, jmb38x_ms, tifm_ms, r592) already implement their own hardware and bus timeouts, and callers in mspro_block and ms_block already rely on wait_for_completion() unconditionally.  Replace wait_for_completion_timeout() with wait_for_completion() in memstick_set_rw_addr() and memstick_alloc_card() so that the card structure is never freed while an asynchronous request is in flight.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99040",
                        "url": "https://ubuntu.com/security/CVE-2026-99040",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  KEYS: Fix add_key() race with keyring restriction  __key_create_or_update() snapshots keyring->restrict_link before taking the destination keyring's semaphore.  keyring_restrict() installs a restriction while holding that semaphore.  This allows a writer to observe no restriction, wait for the keyring owner to install a reject-all restriction and return successfully, and then link a key using the stale NULL snapshot.  The writer only needs write permission on the destination keyring.  Move the restrict_link read after __key_link_lock() and __key_link_begin().  The read and the subsequent restriction check are then serialized with restriction installation by keyring->sem.  The race was reproduced on v7.2.8 in 19 executions where restriction installation returned before the link completed.  All 19 linked the key despite the reject-all restriction.  With this change, 312 executions reached the same ordering and every add_key() call failed with -EPERM.  The issue was found by manual concurrency analysis assisted by AI-based analysis and independently verified with a QEMU reproducer and kernel instrumentation.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99045",
                        "url": "https://ubuntu.com/security/CVE-2026-99045",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ibmveth: h_free logical LAN on open-fail after register  ibmveth_open() registers the logical LAN, then allocates the RX buffer pools. A pool failure jumps to out_free_buffer_pools without h_free_logical_lan(), so PHYP still owns the buffer-list page when it is unmapped. request_irq() failure already issued the hypercall before taking the same label.  Move that h_free to the shared post-register unwind so both paths deregister before the buffer list is unmapped.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99049",
                        "url": "https://ubuntu.com/security/CVE-2026-99049",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  gpio: xilinx: fix runtime PM leak on request error path  pm_runtime_get_sync() leaves the usage counter incremented even when it fails, and xgpio_request() returns the error without dropping it.  gpiolib does not call ->free() when ->request() fails, so xgpio_free(), which holds the only matching pm_runtime_put(), never runs. The reference is leaked and the controller can no longer runtime-suspend, so its clock stays enabled.  Switch to pm_runtime_resume_and_get(), which only increments the usage counter on success.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99052",
                        "url": "https://ubuntu.com/security/CVE-2026-99052",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  selinux: preserve NATIVE_LABELS on already-initialized sb in set_mnt_opts  When an NFSv4 filesystem exported with security_label is mounted a second time, sget_fc() returns the existing superblock and nfs_get_root() calls security_sb_set_mnt_opts() again on it. Since the superblock is already SB_INITIALIZED, selinux_set_mnt_opts() takes an early exit without setting SECURITY_LSM_NATIVE_LABELS in *set_kern_flags. nfs_get_root() then sees kflags without SECURITY_LSM_NATIVE_LABELS set and clears NFS_CAP_SECURITY_LABEL on the shared nfs_server, silently disabling per-file labeling for both the new and the original mount.  Commit 3815a245b501 (\"security/selinux: fix SECURITY_LSM_NATIVE_LABELS on reused superblock\") fixed the same problem in selinux_sb_clone_mnt_opts().  The reused-superblock path for a plain second mount now goes through sb_set_mnt_opts rather than sb_clone_mnt_opts, so it needs the same treatment: on both SE_SBINITIALIZED early exits, set SECURITY_LSM_NATIVE_LABELS in *set_kern_flags when the superblock was already using SECURITY_FS_USE_NATVE.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99053",
                        "url": "https://ubuntu.com/security/CVE-2026-99053",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  tipc: hold a reference to nodes found by link name  tipc_node_find_by_name() returns a node after dropping its RCU read lock without taking a reference.  The LINK_SET, LINK_GET and LINK_RESET_STATS handlers then lock and access the node, racing with timer-driven cleanup of a down peer.  Generic netlink serialization does not exclude the node timer.  The following interleaving can leave a handler using a freed node:    CPU 0: find the node under RCU and release the node read lock   CPU 1: tipc_node_timeout() clears the links and unlinks the down node   CPU 1: drop the list and timer references, queuing tipc_node_free()   CPU 0: leave the RCU read-side critical section   CPU 1: complete the grace period and free the node   CPU 0: acquire the node lock through the stale pointer  LINK_SET also uses the node's media address after releasing the node lock, when passing queued packets to tipc_bearer_xmit().  KASAN on v7.3-rc5 reported:    BUG: KASAN: slab-use-after-free in _raw_read_lock_bh   Write of size 4 at addr ffff88807e06f008 by task poc/92   Call Trace:    _raw_read_lock_bh                 kernel/locking/spinlock.c:287    tipc_nl_node_set_link             net/tipc/node.c:2475    genl_family_rcv_msg_doit          net/netlink/genetlink.c:1114    genl_rcv_msg                      net/netlink/genetlink.c:1209    netlink_rcv_skb                   net/netlink/af_netlink.c:2575    Allocated by task 0:    tipc_node_create                  net/tipc/node.c:539    tipc_node_check_dest              net/tipc/node.c:1196    tipc_disc_rcv                     net/tipc/discover.c:252    Freed by task 92:    kfree                             mm/slub.c:6801    rcu_core                          kernel/rcu/tree.c:2919    Last potentially related work creation:    __call_rcu_common.constprop.0     kernel/rcu/tree.c:3181    tipc_node_timeout                 net/tipc/node.c:814  Acquire a reference to the selected node with kref_get_unless_zero() before leaving RCU, returning NULL if the node has already been released.  Release that reference on every caller exit after the last node access, including transmission in LINK_SET.  Keep the existing link lookup order and locking so concurrent link removal still takes the existing error paths.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99054",
                        "url": "https://ubuntu.com/security/CVE-2026-99054",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  tipc: destroy topsrv workqueues before closing connections  tipc_topsrv_stop() closed subscriber connections while the topology server's send and receive workqueues were still running. Socket callbacks and subscription events could then queue more work, and in-flight send/recv work could drop the last connection reference during the conn_idr walk.  That race produced several teardown failures: refcount_t addition on 0 from conn_get() on a connection whose release was blocked on idr_lock, a subsequent use-after-free in tipc_conn_close(), queue_work() on an already destroyed workqueue from the listener data-ready callback, and an RCU stall in tipc_topsrv_exit_net() while the walk spun under idr_lock.  Clear srv->listener under idr_lock so it acts as a shutdown flag, skip queue_work() once it is NULL, destroy the workqueues to flush in-flight work, and only then close the remaining connections. Refuse tipc_conn_lookup() after that flag is cleared, and drop idr_lock when the teardown walk finds no connection, so an in-flight subscription event cannot pin idr_in_use while the walk holds the lock.  v3 supersedes the narrower in-thread diff Tung Quang Nguyen posted on 2026-09-23. It keeps his teardown order and adds the lookup refusal and the empty-idr unlock.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99056",
                        "url": "https://ubuntu.com/security/CVE-2026-99056",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  strparser: make sure __strp_recv isn't running before tearing down the parser  The comment above strp_done() claims that if strp is stopped, strp_recv will no longer be called. That's only true if the caller has a mechanism (eg locking) to guarantee that strp_recv() calls that started before strp_stop() have completed by the time we call strp_done().  This adds a dummy lock_sock/release_sock pair to guarantee that any in-flight strp_recv() (which runs under either bh_lock_sock or lock_sock, depending if it's called from ->sk_data_ready or strp_work) has completed.  Only espintcp can be affected by this race condition, but this patch makes sure no future user of strp can have the bug.  This could crash on strp->sk (\"general mode\" of strp), but this mode has been here for 9 years and has never been used. It'll be gone soon, no point worrying about it.  Switch the stopped/paused/etc bits to u8's to avoid races between strp_stop() and strp_pause/unpause().  A reproducer has been published and turns the possible UAF into an exploit [1].",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99057",
                        "url": "https://ubuntu.com/security/CVE-2026-99057",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  xen/netfront: don't leak the skb when xennet_fill_frags() fails  When a response chain has more slots than fit in the skb's frags, xennet_fill_frags() returns an error and xennet_poll() jumps to its error path.  That path moves what's left on tmpq to errq to be freed, but the skb being filled was already dequeued from tmpq, so it's never freed.  Each chain that overflows leaks the skb and the pages attached to it as frags, and the backend decides how many slots it sends.  Put the skb back on tmpq before taking the error path, like the xennet_set_skb_gso() failure just above it does.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99058",
                        "url": "https://ubuntu.com/security/CVE-2026-99058",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  workqueue: Fix NULL current_pwq deref in chained work check  current_wq_worker() only tells us that %current is a kworker. It does not guarantee that the worker is currently executing a work item, as worker->current_pwq is populated only while process_one_work() is running the work function.  is_chained_work() can be reached while queueing on a draining or destroying workqueue. If a kworker outside work-item execution reaches that path, current_wq_worker() returns a worker but worker->current_pwq is NULL, and the chained-work test can fault before it emits the intended warning.  Guard the chained-work test with worker->current_pwq. A kworker without current_pwq is not executing work on the target workqueue, so the helper should return false and let the draining/destroying warning fire.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99059",
                        "url": "https://ubuntu.com/security/CVE-2026-99059",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wireguard: noise: reject response consumption after intermediate initiation  Two threads begin processing the identical response message, received twice. The first thread, A, runs. While it's running, the second one, B, gets partway through, and during that slow calculation, or even while blocking on down_write(), A completes and then also a handshake initiation that's already been queued up runs in thread C, which itself takes that same down_write(). The handshake initiation creation succeeds, and sets the state back to waiting-for-response, and calls up_write(), at which point thread B resumes, because either its finished its calculations or was finally allowed to acquire down_write(). Thread B then copies the state back to the peer, and begins a new session, using that state, which is the same session as the one made in thread A.  Thread A\t\t\tThread B\t\t\tThread C  down_read()  sA = handshake->state  memcpy(cA, handshake->crypto) up_read() if (sA != 1)  goto fail slow_crypto(cA) \t\t\t\tdown_read() \t\t\t\t sB = handshake->state \t\t\t\t memcpy(cB, handshake->crypto) \t\t\t\tup_read() \t\t\t\tif (sB != 1) \t\t\t\t goto fail \t\t\t\tslow_crypto(cB) down_write()  if (sA != handshake->state)   goto fail  memcpy(handshake->crypto, cA)  handshake->state = 2 up_write() down_write()  if (handshake->state != 2)   goto fail  derive_session(handshake->crypto) up_write() \t\t\t\t\t\t\t\tdown_write() \t\t\t\t\t\t\t\t slow_crypto(handshake->crypto) \t\t\t\t\t\t\t\t handshake->state = 1 \t\t\t\t\t\t\t\tup_write() \t\t\t\tdown_write() \t\t\t\t if (sB != handshake->state) \t\t\t\t   goto fail \t\t\t\t memcpy(handshake->crypto, cB) \t\t\t\t handshake->state = 2 \t\t\t\tup_write() \t\t\t\tdown_write() \t\t\t\t if (handshake->state != 2) \t\t\t\t  goto fail \t\t\t\t derive_session(handshake->crypto) \t\t\t\tup_write()  This seems basically impossible to hit in a meaningful way in practice, but ensure that it absolutely cannot happen by comparing the ephemeral private key that's on the stack with the latest one that the peer's handshake state has.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99061",
                        "url": "https://ubuntu.com/security/CVE-2026-99061",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: brcmfmac: fix P2P device removal race in brcmf_detach()  When the driver is removed while the user space process that created the P2P device (e.g. wpa_supplicant) is still exiting, the P2P device interface is removed twice and the kernel crashes.  The two paths are:   - wpa_supplicant, on exit, sends NL80211_CMD_DEL_INTERFACE for the P2P    device. nl80211_del_interface() holds RTNL and the wiphy mutex and    calls brcmf_p2p_del_vif(), which disables discovery and waits up to    1.5 s for BRCMF_E_IF_DEL. Then it calls brcmf_remove_interface(),    which unregisters the wdev and frees the vif and the ifp.   - brcmf_detach() sets the bus down, so BRCMF_E_IF_DEL never arrives,    and calls brcmf_remove_interface(ifp, false) for the same ifp.    brcmf_p2p_ifp_removed() reads ifp->vif and then blocks on    rtnl_lock(). When brcmf_p2p_del_vif() releases RTNL, it calls    cfg80211_unregister_wdev() on the wdev that was already unregistered    and freed.  The second list_del_rcu() of wdev->list faults on LIST_POISON2:    brcmfmac: brcmf_p2p_del_vif delete P2P vif   brcmfmac: brcmf_p2p_deinit_discovery enter   brcmfmac: brcmf_p2p_del_vif P2P: GO_NEG_PHASE status cleared   brcmfmac: brcmf_detach Enter   brcmfmac: brcmf_bus_change_state 1 -> 0   brcmfmac: brcmf_remove_interface Enter, bsscfgidx=1, ifidx=0   brcmfmac: brcmf_del_if Enter, bsscfgidx=1, ifidx=0   brcmfmac: brcmf_p2p_ifp_removed P2P: device interface removed   [1.5 s later, brcmf_p2p_del_vif() timed out]   brcmfmac: brcmf_remove_interface Enter, bsscfgidx=1, ifidx=0   brcmfmac: brcmf_del_if Enter, bsscfgidx=1, ifidx=0   brcmfmac: brcmf_p2p_ifp_removed P2P: device interface removed   Unable to handle kernel paging request at virtual address dead000000000122   Internal error: Oops: 96000044 [#1] PREEMPT_RT SMP   pc : _cfg80211_unregister_wdev+0x6c/0x264 [cfg80211]   Call trace:    _cfg80211_unregister_wdev+0x6c/0x264 [cfg80211]    cfg80211_unregister_wdev+0x10/0x1c [cfg80211]    brcmf_p2p_ifp_removed+0x84/0xb0 [brcmfmac]    brcmf_remove_interface+0x1f4/0x254 [brcmfmac]    brcmf_detach+0x88/0x180 [brcmfmac]    brcmf_sdio_remove+0x90/0x7b0 [brcmfmac]    brcmf_sdiod_remove+0x20/0xa0 [brcmfmac]    brcmf_ops_sdio_remove+0xbc/0x12c [brcmfmac]    sdio_bus_remove+0x38/0x144    device_release_driver_internal+0x1e8/0x2c0    device_release_driver+0x14/0x20    brcmf_sdio_bus_remove+0x2c/0x40 [brcmfmac]    brcmf_fwvid_unregister_vendor+0xd8/0x170 [brcmfmac]    __exit_compat+0x18/0x418 [brcmfmac_cyw]    __arm64_sys_delete_module+0x1ac/0x244  The log was taken with debug=0x406 on an i.MX 8M Plus board with a CYW55513 (Sona IF513) on SDIO. The driver is the Ezurio backport of brcmfmac from v6.18.22 on a 5.4-rt kernel. The code involved is the same in mainline.  To reproduce:    1. Start wpa_supplicant on wlan0 and let it associate. It creates the      P2P device (iw dev shows \"type P2P-device\").   2. Stop wpa_supplicant and remove the driver without waiting for      wpa_supplicant to exit:         kill $(pidof wpa_supplicant)        rmmod brcmfmac_cyw brcmfmac  The crash is reproducible on that board.  For the interface without a netdev (the P2P device), take RTNL and the wiphy mutex in brcmf_detach() before reading iflist, and remove it with locked=true. If brcmf_p2p_del_vif() runs first, brcmf_detach() finds the slot empty. If brcmf_detach() runs first, nl80211 does not find the wdev any more. The interfaces with a netdev are removed as before, because brcmf_del_if() takes RTNL on its own for the primary interface.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99063",
                        "url": "https://ubuntu.com/security/CVE-2026-99063",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  dm ioctl: don't let data_start run past the buffer  struct dm_ioctl has seven bytes of trailing padding, so the smallest buffer userspace is allowed to ask for, offsetof(struct dm_ioctl, data), is seven bytes shorter than sizeof(struct dm_ioctl).  get_result_buffer() sets data_start to sizeof(struct dm_ioctl) without looking at how big the buffer actually is. Ask for the minimum and data_start ends up seven bytes past the end. Callers add it to data_size, and ctl_ioctl() copies that much back to userspace:    BUG: KASAN: slab-out-of-bounds in _copy_to_user+0xad/0xd0   Read of size 312 at addr ffff8880169e4c00 by task repro-dm/140    ctl_ioctl+0x5e3/0xcb0    dm_ctl_ioctl+0x25/0x40   allocated 305-byte region [ffff8880169e4c00, ffff8880169e4d31)  A DM_LIST_DEVICES with data_size set to 305 is enough to hit it, and the seven bytes that leak are whatever sat next to the allocation.  Clamp data_start to the buffer size.  Note that this is not a security bug because the out-of-bounds read can only be triggered by root.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99067",
                        "url": "https://ubuntu.com/security/CVE-2026-99067",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  btrfs: scrub: fix local_root reference leak in scrub_print_warning_inode()  When paths_from_inode() fails, scrub_print_warning_inode() jumps to err without dropping the reference taken by btrfs_get_fs_root(), leaking a reference to the root every time path resolution fails while printing scrub warnings.  Every other error and success path of the function drops the reference.  Drop the reference on the paths_from_inode() failure path too.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99070",
                        "url": "https://ubuntu.com/security/CVE-2026-99070",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ipv6: do not warn on route notification size race  fib6_info_hw_flags_set() sizes the skb with rt6_nlmsg_size() and later fills it with rt6_fill_node().  With nexthop compatibility mode enabled, a concurrent replacement can grow the group between these independent snapshots.  rt6_fill_node() can then legitimately return -EMSGSIZE, so the warning does not prove a sizing bug.  Remove the warning.  The existing error path still frees the skb and reports the error to listeners.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99071",
                        "url": "https://ubuntu.com/security/CVE-2026-99071",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ipv4: do not warn on route notification size race  Commit 680aea08e78c (\"net: ipv4: Emit notification when fib hardware flags are changed\") added asynchronous route notifications for hardware flag changes.  fib_alias_hw_flags_set() sizes the skb with fib_nlmsg_size() and later fills it with fib_dump_info() while holding only RCU.  With nexthop compatibility mode enabled, a concurrent replacement can grow the group between these independent snapshots.  fib_dump_info() can then legitimately return -EMSGSIZE, so the warning does not prove a sizing bug.  Remove the warning.  The existing error path still frees the skb and reports the error to listeners.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99072",
                        "url": "https://ubuntu.com/security/CVE-2026-99072",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ipv4: stop route notification sizing when nexthop group shrinks  Commit 680aea08e78c (\"net: ipv4: Emit notification when fib hardware flags are changed\") added an RCU-only fib_nlmsg_size() call for asynchronous hardware flag notifications.  fib_nlmsg_size() checks fib_info_num_path() before each iteration, then fib_info_nhc() independently reloads nh->nh_grp. If RTM_NEWNEXTHOP replaces a group with fewer paths between those loads, fib_info_nhc() returns NULL and fib_nexthop_nlmsg_size() dereferences it.  Stop sizing when the indexed path is absent. Nexthop groups are dense, so the current snapshot has no later path.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98686",
                        "url": "https://ubuntu.com/security/CVE-2026-98686",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  smb: client: discard post-EOF pagecache when extending a file via zero range  smb3_zero_range() removed the pagecache only for the range being zeroed, so when it extends the file the folio straddling the old EOF - which may hold data dirtied past EOF through an mmap - was never dropped and became visible as file content once the file was extended.  Lower the discard boundary to the smaller of the zero-range offset and the old EOF.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98700",
                        "url": "https://ubuntu.com/security/CVE-2026-98700",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: mac80211: set info->band for 802.3 encap offload frames  Unlike the 802.11 TX paths, ieee80211_8023_xmit() does not set info->band from the channel context on non-MLD interfaces. It stays at 0, so ieee80211_get_tx_rates() uses the wrong band for these frames.  Set it the same way as ieee80211_build_hdr(): drop the frame if there is no channel context, and leave the band at 0 on MLD interfaces.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98716",
                        "url": "https://ubuntu.com/security/CVE-2026-98716",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  KVM: SVM: Use the active VMCB's MSR bitmap when checking if MSR is intercepted  Use the MSR permission bitmap of the active VMCB instead of assuming that KVM is always using vmcb02's bitmap when L2 is active, as KVM uses msrpm02 if and only if L1 wants to intercept MSR accesses, i.e. if and only if KVM needs to merge msprm01 with msrpm12.  Don't bother tracking the virtual address of the bitmap that's being used, as __va() is cheap on x86, and caching the virtual address would introduce yet another source of potentially stale information.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99080",
                        "url": "https://ubuntu.com/security/CVE-2026-99080",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  fs: Free any excess xarray nodes in clear_inode()  For many years we've had a hard to hit leak of xarray nodes.  Hugh documented it well in commit 786b31121a2c.  Recently people and syzbot have found ways to force it to happen with madvise.  Rather than fix the leaks where they happen, just call xa_destroy() which has the side-effect of cycling the i_pages lock.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98709",
                        "url": "https://ubuntu.com/security/CVE-2026-98709",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: mac80211: count only matching reservations in reserved switch  ieee80211_vif_use_reserved_switch() validates a replacement by counting assigned links on ctx->replace_ctx and treating reservations too broadly. A link can still be assigned to the old channel context while holding a reservation that belongs to a different replacement operation.  That can make the current replacement appear complete too early. If another link finalizes first, the function can free the WILL_BE_REPLACED chanctx while the unmatched link and driver still use it, leading to a use-after-free in later beacon generation.  Require an in-place reservation to point at the current replacement context, and require the reserved and assigned contexts to be the matching replacement pair, before counting or moving the link.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98708",
                        "url": "https://ubuntu.com/security/CVE-2026-98708",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: mac80211: keep paired old chanctx alive  An in-place replacement keeps reciprocal replace_ctx pointers between the old WILL_BE_REPLACED chanctx and the new REPLACES_OTHER chanctx. However, the early free paths only consider assigned and reserved link users when deciding whether to free the old chanctx.  That lets the old chanctx be freed too early while the replacement partner still points back to it, either when the last assigned link is released or when that link successfully reassigns to another existing context. Later unreserve and switch-finalization paths can then follow a stale replace_ctx pointer.  Keep a paired old chanctx alive until the replacement pair has been torn down. Apply the same check to both __ieee80211_link_release_channel() and ieee80211_link_use_reserved_reassign(). If the replacement is later abandoned, ieee80211_link_unreserve_chanctx() already tears down the pairing before freeing the old chanctx once no users remain.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98752",
                        "url": "https://ubuntu.com/security/CVE-2026-98752",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  tty: port: fix tty_port_tty_vhangup() race  Drivers rely on tty_port_tty_vhangup() to synchronously hang up their ports before tearing down resources as part of deregistration (e.g. on physical disconnect).  If tty_port_tty_vhangup() races with another hangup it may however return before the port has been shut down. This is in turn can lead to use-after-free and NULL-pointer dereferences in racing ioctls (including a synchronous hangup) and in processing of racing asynchronous hangups (carrier loss).  Add the missing serialisation to tty_port_tty_vhangup() and tty_port_hangup() so that the former does not return until the port has been shut down also when there is a racing hangup.  Note that serial core does not use tty_port_hangup(), but it already holds the port mutex when clearing port->tty and shutting down the port in uart_hangup().",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99081",
                        "url": "https://ubuntu.com/security/CVE-2026-99081",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  bnxt_en: fix DMA mapping length for padded small packets  Stefan Fleischmann reported Intel IOMMU DMA Read faults on BCM57412 NetXtreme-E NICs when transmitting packets on VLAN/macvlan interfaces:    DMAR: [DMA Read NO_PASID] Request device [18:00.0] fault addr 0xfc499000         [fault reason 0x06] PTE Read access is not set   bnxt_en 0000:18:00.0 eno1np0: Abandoning msg {0xb4 0x41a} len: 0 due to firmware status: 0x2000001   ...   NETDEV WATCHDOG: eno1np0 (bnxt_en): transmit queue 0 timed out  The fault address (0xfc499000) is on an exact 4KB page boundary, pointing to a DMA read buffer overrun.  In bnxt_start_xmit(), packets smaller than BNXT_MIN_PKT_SIZE (52 bytes), such as 42-byte untagged ARP frames, are padded:      if (length < BNXT_MIN_PKT_SIZE) {         pad = BNXT_MIN_PKT_SIZE - length;         if (skb_pad(skb, pad))             goto tx_kick_pending;         length = BNXT_MIN_PKT_SIZE;     }      mapping = dma_map_single(&pdev->dev, skb->data, len, DMA_TO_DEVICE);     ...     dma_unmap_len_set(tx_buf, len, len);  However, 'len' was initialized earlier to skb_headlen(skb) (e.g. 42 bytes) and is left unadjusted after padding. Consequently, dma_map_single() and dma_unmap_len_set() map and track only 42 bytes.  Later, the hardware TX buffer descriptor is programmed with the padded length:      txbd->tx_bd_len_flags_type =         cpu_to_le32(((len + pad) << TX_BD_LEN_SHIFT) | flags |                     TX_BD_FLAGS_PACKET_END);  The NIC DMA engine is thus instructed to read 52 bytes from a region where only 42 bytes were DMA-mapped. If skb->data ends near the boundary of a 4KB page (within 'pad' bytes of the next page), the hardware DMA read overruns into the unmapped adjacent page, triggering an IOMMU fault.  This issue was exposed after commit 447cbe95ebb9 (\"vlan: fix skb_under_panic and races when toggling HW VLAN offload\") because reserving extra VLAN headroom rounded LL_RESERVED_SPACE from 48 up to 64 bytes, shifting skb->data offsets and potentially causing small frames to land right against page boundaries.  Fix this by using skb_put_padto(skb, BNXT_MIN_PKT_SIZE) in bnxt_start_xmit(), before skb_shinfo(skb)->nr_frags is sampled, because padding might linearize the skb. This ensures skb->len and skb_headlen(skb) reflect the padded size so that dma_map_single() maps the full buffer and the descriptor length is consistent. This also removes the temporary 'pad' variable and masking logic.  The padding is done after the SW USO branch, otherwise bnxt_sw_udp_gso_xmit() would account the padding as UDP payload and send it in extra segments.  Note that SW USO segments are still not padded: with IPv4, a segment carrying less than 10 bytes of UDP payload (small gso_size, or a short last segment) is sent as a frame shorter than BNXT_MIN_PKT_SIZE. This is a separate issue, left for a followup patch.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98696",
                        "url": "https://ubuntu.com/security/CVE-2026-98696",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  USB: serial: fix driver deregistration order  USB serial driver modules register one driver for the USB bus and one or more drivers for the ports on the USB serial bus.  When unloading a driver module, the USB driver must be deregistered before the USB serial bus drivers so that I/O is stopped before unbinding the ports to avoid use-after-free in completion handlers accessing port data.  Note that the \"new_id\" attributes must first be removed to prevent new ids from being added and triggering a probe of the USB driver after it has been deregistered.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98705",
                        "url": "https://ubuntu.com/security/CVE-2026-98705",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: mac80211: account proxy paths against the mesh path limit  Proxy-path churn can drive the interface path counter negative and let later mesh path additions exceed MESH_MAX_MPATHS.  mesh_path_free_rcu() decrements the interface mpaths counter for entries from both the mesh and proxy path tables, but mpp_path_add() never reserves a slot in that counter. Removing or expiring a proxy path therefore returns a slot that was never charged.  mesh_path_add() uses the same counter to enforce MESH_MAX_MPATHS, so once it falls below the number of installed paths the limit no longer holds.  Reserve the shared quota before allocating a proxy path and release it on every unsuccessful addition. Mesh and proxy paths now share one 1024-entry budget, so mpp_path_add() can return -ENOSPC at that limit.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98722",
                        "url": "https://ubuntu.com/security/CVE-2026-98722",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  mtd: block2mtd: Fix divide error when erase_size is zero  The erase size is parsed from the \"block2mtd\" module parameter and can be set to zero. add_device() then evaluates          if (size % erase_size)  with a zero divisor, which triggers a divide error:  divide error: 0000 [#1] PREEMPT SMP PTI RIP: 0010:add_device drivers/mtd/devices/block2mtd.c:296 [inline] RIP: 0010:block2mtd_setup2+0x592/0xda0 drivers/mtd/devices/block2mtd.c:459 Call Trace: block2mtd_setup+0x27/0xe0 drivers/mtd/devices/block2mtd.c:476 param_attr_store+0x214/0x310 kernel/params.c:589 module_attr_store+0x65/0x90 kernel/params.c:904 kernfs_fop_write_iter+0x3a4/0x540 fs/kernfs/file.c:345 ...  Reject a zero erase size before performing the modulo operation so the existing \"erasesize must be a divisor of device size\" error path reports the invalid argument and frees the device.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98695",
                        "url": "https://ubuntu.com/security/CVE-2026-98695",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  USB: serial: fix ioctl hangup race  The tty ioctls can race with hangup and end up calling into a tty driver for a device that is already gone or powered down.  Serialise the callbacks using the tty port mutex and add the missing checks to make sure the port has not been hung up before accessing port driver data or hardware.  This specifically avoids dereferencing a NULL-pointer if a device is disconnected during lengthy break signalling.  Note that TIOCGICOUNT and TIOCMIWAIT do not access port driver data or hardware and are therefore not affected by the race.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98694",
                        "url": "https://ubuntu.com/security/CVE-2026-98694",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  thunderbolt: Fix KASAN reported use-after-free when request is canceled  Alan reported that when doing stress testing sometimes KASAN notices use-after-free during control channel operation (stripped down keeping the relevant parts):   BUG: KASAN: slab-use-after-free in tb_cfg_request_sync+0x240/0x250 [thunderbolt]  Read of size 24 at addr ffff88811067f290 by task kworker/u40:2/1760   <TASK>   tb_cfg_request_sync+0x240/0x250 [thunderbolt]   tb_cfg_read_raw+0x367/0x510 [thunderbolt]   tb_cfg_read+0xec/0x240 [thunderbolt]   tb_port_get_link_generation+0x258/0x420 [thunderbolt]   tb_usb3_consumed_bandwidth+0x1c1/0x2c0 [thunderbolt]   tb_tunnel_consumed_bandwidth+0xfd/0x910 [thunderbolt]   tb_available_bandwidth+0x5f2/0xeb0 [thunderbolt]   tb_recalc_estimated_bandwidth+0x2a0/0x1bc0 [thunderbolt]   tb_handle_dp_bandwidth_request+0x1897/0x5e20 [thunderbolt]   process_one_work+0x675/0x1230   worker_thread+0x5e6/0xf70   kthread+0x365/0x470   ret_from_fork+0x54d/0x710   ret_from_fork_asm+0x1a/0x30   </TASK>   Allocated by task 1760:   __kmalloc_cache_noprof+0x1ee/0x550   tb_cfg_read_raw+0x1d3/0x510 [thunderbolt]   tb_cfg_read+0xec/0x240 [thunderbolt]   tb_port_get_link_generation+0x258/0x420 [thunderbolt]   tb_usb3_consumed_bandwidth+0x1c1/0x2c0 [thunderbolt]   tb_tunnel_consumed_bandwidth+0xfd/0x910 [thunderbolt]   tb_available_bandwidth+0x5f2/0xeb0 [thunderbolt]   tb_recalc_estimated_bandwidth+0x2a0/0x1bc0 [thunderbolt]   tb_handle_dp_bandwidth_request+0x1897/0x5e20 [thunderbolt]   process_one_work+0x675/0x1230   worker_thread+0x5e6/0xf70   kthread+0x365/0x470   ret_from_fork+0x54d/0x710   ret_from_fork_asm+0x1a/0x30   Freed by task 926:   kfree+0x18f/0x4a0   tb_cfg_request_put+0xb7/0xe0 [thunderbolt]   tb_cfg_request_work+0x82/0x120 [thunderbolt]   process_one_work+0x675/0x1230   worker_thread+0x5e6/0xf70   kthread+0x365/0x470   ret_from_fork+0x54d/0x710   ret_from_fork_asm+0x1a/0x30   Second to last potentially related work creation:   __queue_work+0x575/0xd00   queue_work_on+0x77/0x80   tb_cfg_request_cancel+0xc7/0x260 [thunderbolt]   tb_cfg_request_sync+0x1f6/0x250 [thunderbolt]   tb_cfg_read_raw+0x367/0x510 [thunderbolt]   tb_cfg_read+0xec/0x240 [thunderbolt]   tb_port_get_link_generation+0x258/0x420 [thunderbolt]   tb_usb3_consumed_bandwidth+0x1c1/0x2c0 [thunderbolt]   tb_tunnel_consumed_bandwidth+0xfd/0x910 [thunderbolt]   tb_available_bandwidth+0x5f2/0xeb0 [thunderbolt]   tb_recalc_estimated_bandwidth+0x2a0/0x1bc0 [thunderbolt]   tb_handle_dp_bandwidth_request+0x1897/0x5e20 [thunderbolt]   process_one_work+0x675/0x1230   worker_thread+0x5e6/0xf70   kthread+0x365/0x470   ret_from_fork+0x54d/0x710   ret_from_fork_asm+0x1a/0x30  The last stack trace is helpful because it shows that we are cancelling a request and looking at tb_cfg_request_cancel() what might happen is that tb_cfg_request_work() completes right before tb_cfg_request_cancel() starts and because of this it will call schedule_work() queueing the same work to run again. However, it is already removed from the request_queue and reference count is dropped so when tb_cfg_request_work() triggers again it will access memory that is already released.  Fix this so that we first make sure a cancelled request is not handed away from tb_cfg_request_find() or scheduled to run. Then instead of relying on the worker to clean up the request we will do it in tb_cfg_request_cancel() after the work is canceled from running. Make tb_cfg_request_dequeue() release the request only if it was actually removed from the queue.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98704",
                        "url": "https://ubuntu.com/security/CVE-2026-98704",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: mac80211: keep fallback association elements alive  Associating to a non-transmitted MBSSID profile reads freed memory while determining the operating channel and applying HT capabilities.  When an association response omits WMM, HT, or VHT information, ieee80211_assoc_config_link() parses the cached BSS IEs and copies the missing element pointers out of that fallback parse. For a non-transmitted MBSSID profile those pointers refer to merged-profile storage owned by the parse object, and the fallback block frees that object at its end. The copied pointers are used afterwards to determine the operating channel, configure bandwidth, and apply HT capabilities.  Keep the fallback parse result alive until association setup finishes.  [reorder variable declaration]",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98707",
                        "url": "https://ubuntu.com/security/CVE-2026-98707",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: mac80211: shut down RX BA session timer on teardown  Tearing down an RX BA session can leave the session timer queued on a freed tid_rx. Later timer-wheel processing and the timer callback itself then run against freed memory.  An RX BAR handler can dereference tid_rx under RCU before teardown unpublishes it and stay in its read-side critical section while teardown deletes the session timer. The stale handler can then rearm the timer after timer_delete_sync() returns and before the RCU callback frees tid_rx.  Use timer_shutdown_sync() so rearm attempts become ineffective once teardown starts. Keep reorder_timer unchanged: teardown marks the session removed under reorder_lock and its release path checks that state before rearming. session_timer has no equivalent guard because ieee80211_rx_h_ctrl() rearms it before taking reorder_lock.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98749",
                        "url": "https://ubuntu.com/security/CVE-2026-98749",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  tty: serial: max3100: shut down timer before freeing port  max3100_shutdown() stops the polling timer but returns early during system suspend. If the SPI device is unbound before resume, the serial core does not call max3100_shutdown() again, so max3100_remove() frees the port while the timer remains armed. max3100_timeout() may then access the freed port and re-arm the timer.  Add final timer teardown to max3100_remove() and use timer_shutdown_sync() to prevent a racing callback from re-arming it. Also free the IRQ and destroy the workqueue there before freeing the port. Keep timer_delete_sync() in max3100_shutdown() so that a subsequent open() can re-arm the timer.  The workqueue is created before request_irq() and destroyed on both request_irq() failure and normal shutdown. Its presence at remove thus identifies the IRQ left registered when suspend bypasses shutdown.  Free the IRQ before destroying the workqueue, in both max3100_shutdown() and max3100_remove(), and cancel the pending work in between. free_irq() waits for a running interrupt handler to finish and no new handler can start afterwards, so a racing handler cannot queue work on a workqueue that is being destroyed; the force_end_work check in max3100_dowork() only narrows that window, as a handler delayed between the check and queue_work() could still run after the teardown has cleared the workqueue pointer. Cancelling the work also keeps destroy_workqueue() from waiting on a queued work item in case remove() ever runs while the freezable workqueue is still frozen, e.g. device removal during the resume window, before workqueues are thawed.  This issue was found by an in-house static analysis tool.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98751",
                        "url": "https://ubuntu.com/security/CVE-2026-98751",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  tty: abort break signalling on hangup  The break ioctls can race with hangup and end up calling into a tty driver for a device that is already gone or powered down.  Drivers must handle this race, but TCSBRK and TCSBRKP should still be aborted to avoid calling back into the driver after a user-controlled timeout (possibly even after the tty has been reopened).  Note that drivers should disable any break state on shutdown so just return on hangup (calling break_ctl() again is racy and will most likely fail for drivers handling the race).",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98753",
                        "url": "https://ubuntu.com/security/CVE-2026-98753",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  tty: tty_port: restore TTY_IO_ERROR on activation failure  Make sure to restore the TTY_IO_ERROR flag if activation fails to prevent I/O attempts on a port that is gone or powered down.  This specifically avoids issues like kernel panic due to unclocked accesses or NULL-pointer dereferences when accessing powered down or deregistered ports when a TTY ioctl races with hangup and open.  Note that the flag is set again in tty_port_close() but not restoring it on activation failure leaves a window where drivers fail to handle the ioctl-hangup race.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98762",
                        "url": "https://ubuntu.com/security/CVE-2026-98762",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  USB: dwc2: shut down wakeup timer before freeing HCD state  dwc2_wakeup_detected() accesses the DWC2 host state and can rearm the wakeup timer.  dwc2_hcd_free() currently deletes the timer only after freeing host-owned state, and timer_delete() does not synchronize a callback or prevent it from being queued again.  Stop and shut down the timer in dwc2_hcd_release(), before the HCD resources are freed.  This covers both the HCD initialization error path and normal HCD removal.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98784",
                        "url": "https://ubuntu.com/security/CVE-2026-98784",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  drm/amdgpu/gfx6: fix firmware leak on teardown  The firmware requested in gfx_v6_0_init_microcode() is not released when the GFX block is torn down, leaking the firmware resources.  Add gfx_v6_0_free_microcode() and call it from gfx_v6_0_sw_fini() to release the PFP, ME, CE and RLC firmware.  (cherry picked from commit 386e81346f95ab0be5a82c5535de932e7a456924)",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98779",
                        "url": "https://ubuntu.com/security/CVE-2026-98779",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  drm/amdgpu: fix ACP MFD device leak on init failure  acp_hw_init() registers ACP child devices with mfd_add_devices() before attaching them to the ACP power domain and initializing the hardware.  If attaching a child to the power domain fails, or if the ACP reset or clock enable operation times out, the failure path frees only the source cell, resource, and platform-data allocations. The child platform devices already registered by mfd_add_devices() remain registered and are never released.  Remove the children from the power domain and unregister the MFD devices on failures that occur after mfd_add_devices() succeeds. Keep mfd_add_devices() failures on the existing cleanup path since the MFD core already rolls back partially registered children itself.  The issue was identified by a static analysis tool I developed and confirmed by manual review.  (cherry picked from commit 63da68d6a2279ec945581c990c5a59a5ae8b5560)",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98742",
                        "url": "https://ubuntu.com/security/CVE-2026-98742",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ALSA: seq: Serialize compat port-info ioctls  The native sequencer ioctl path serializes handler calls with client->ioctl_mutex, but the translated port-info compat path invokes the same handlers through snd_seq_kernel_client_ctl() without taking that mutex.  This lets concurrent compat CREATE_PORT requests pass the port-count check before any request reaches the serialized insertion. The computed integer port index can then exceed the address field range and wrap to an existing index. Subsequent subscriber teardown can resolve the duplicate address to the wrong port and access a freed subscriber.  Take ioctl_mutex while dispatching converted port-info requests, matching the native ioctl path. All translated port-info commands share this helper, so their accesses to the client port state are serialized as well.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98655",
                        "url": "https://ubuntu.com/security/CVE-2026-98655",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  perf: Require kernel access for text poke events  Perf events with exclude_kernel=1 can be opened without kernel perf access. However, exclude_kernel does not suppress text-poke sideband records. Every PERF_RECORD_TEXT_POKE is marked PERF_RECORD_MISC_KERNEL and contains a raw kernel instruction address.  An unprivileged task can therefore open and mmap a task-local software event with text_poke=1. Both opening a count-only tracepoint event and configuring UDP GRO for ESP-in-UDP cause updates to inline static calls; the observer receives the relocated addresses of the modified instructions. For a known kernel image, any such address reveals the runtime kernel text base despite KASLR.  Call perf_allow_kernel() whenever attr.text_poke is set, regardless of exclude_kernel. Events that neither monitor kernel execution nor request text-poke records retain their existing permissions.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98750",
                        "url": "https://ubuntu.com/security/CVE-2026-98750",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  tty: fix saved termios reset race  Resetting saved termios state on device registration is needed where a minor number can be reused for an entirely different device and where the old settings may prevent the port from even being opened (e.g. when CLOCAL is not set).  Not all TTY drivers guarantee that the minor number is no longer in use when registering devices however, something which can lead to a use-after-free when closing a TTY (and saving its termios) races with re-registration.  Add a new TTY_DRIVER_RESET_SAVED_TERMIOS flag to request that any saved termios state is reset on registration and only set it for drivers that make sure that the minor number is no longer in use.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-89638",
                        "url": "https://ubuntu.com/security/CVE-2026-89638",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  smb: client: clear setuid/setgid bit on write with cifsacl/modefromsid/posix extensions  When a file has the setuid or setgid bit set and is written to, the VFS strips those bits and issues a setattr with ATTR_KILL_SUID/ATTR_KILL_SGID together with an ATTR_MODE carrying the already-cleared mode.  Both cifs_setattr_unix() and cifs_setattr_nounix() unconditionally dropped ATTR_MODE in that case:  \t/* skip mode change if it's just for clearing setuid/setgid */ \tif (attrs->ia_valid & (ATTR_KILL_SUID|ATTR_KILL_SGID)) \t\tattrs->ia_valid &= ~ATTR_MODE;  This is fine for the default mount, where the mode is only emulated via the DOS read-only attribute and cannot represent the setuid/setgid bits anyway.  However, with the \"cifsacl\" or \"modefromsid\" mount options the mode is stored on the server through an ACL (id_mode_to_cifs_acl()), with the SMB3.1.1 POSIX extensions the mode is sent to the server directly, and with the SMB1 Unix extensions (cifs_setattr_unix) the mode is sent via CIFSSMBUnixSetPathInfo().  In all those cases dropping ATTR_MODE means the cleared mode is never pushed to the server, so the setuid/setgid bit survives the write.  This is a security issue: on local filesystems the setuid bit is stripped when a file is written, but over these cifs.ko mounts the bit persists on the server, potentially allowing an unexpected privilege escalation on subsequent execution.  Fix this in two places:    1. cifs_setattr_nounix(): only take the \"skip mode change\" shortcut      when the mode is emulated via the DOS read-only attribute (i.e.      neither cifsacl/modefromsid nor the SMB3.1.1 POSIX extensions are      in effect), so that the cleared mode is propagated to the server      in the ACL / POSIX cases.    2. cifs_setattr_unix(): this function is only called when Unix      extensions are in effect, so the mode is always stored on the      server.  Remove the shortcut entirely so that the cleared mode is      always pushed.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-09-11 20:19:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98375",
                        "url": "https://ubuntu.com/security/CVE-2026-98375",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  xen/netfront: drop RX packets with a short Ethernet header  handle_incoming_queue() pulls pull_to bytes into the head before calling eth_type_trans().  pull_to is the length of the first RX slot, capped at RX_COPY_THRESHOLD, and that length comes from the backend. Nothing checks it against ETH_HLEN.  If the first slot is shorter than ETH_HLEN and more slots follow, the head ends up shorter than an Ethernet header while skb->len is longer, and eth_type_trans() BUG()s in __skb_pull().  If the whole packet is shorter than ETH_HLEN, eth_type_trans() reads the header past the end of the data instead.  Pull at least ETH_HLEN, and drop the packet if that fails, which also drops packets too short to hold an Ethernet header.  This also checks the return value of the pull, which was ignored.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-09 08:16:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-89738",
                        "url": "https://ubuntu.com/security/CVE-2026-89738",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  usb: gadget: at91_udc: drain polled-VBUS timer/work before udc is freed  In polled-VBUS mode (board.vbus_pin && board.vbus_polled), probe arms a self-restarting cycle: at91_vbus_timer() schedules vbus_timer_work, and at91_vbus_timer_work() calls at91_vbus_update() and re-arms the timer via mod_timer(). Both recover the same udc through container_of and dereference it on every iteration.  Neither teardown path cancels this cycle. udc is devm-allocated, so it is freed after at91udc_remove() returns, and is likewise freed when probe fails and devres runs. A timer callback or work item that is pending or running at either point dereferences the freed udc.  Add at91_udc_shutdown_vbus_timer() and call it from at91udc_remove() and from the usb_add_gadget_udc() failure path in probe; the remaining probe error paths fail before the timer is armed. timer_shutdown_sync() waits for a running callback and clears timer->function, which makes the work handler's mod_timer() a permanent no-op; cancel_work_sync() then drains any pending or running work whose re-arm attempt now does nothing. The timer must be shut down first, since cancelling the work alone would let the timer re-queue it. The guard mirrors probe: in IRQ mode the timer and work_struct are never initialized.  This does not require a fault; a normal driver unbind can interleave with an already queued work item.  This issue was found by an in-house static analysis tool.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-09-11 20:20:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-89740",
                        "url": "https://ubuntu.com/security/CVE-2026-89740",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  serial: imx: serialize imx_uart_ports[] lifetime  imx_uart_probe() publishes its devm-allocated port in imx_uart_ports[] before uart_add_one_port() because console setup uses the table. The entry is not cleared when adding the port fails or after removal, leaving a dangling pointer.  A sibling probe can register the shared console through that stale entry. This was reproduced under KASAN on QEMU mcimx6ul-evk by unbinding a sibling UART, unbinding the console UART and rebinding the sibling.  Keep the entry valid through uart_remove_one_port(), then clear it. Protect port addition and removal together with their table updates so sibling operations cannot interleave. Reject an occupied slot rather than clobbering an active port during a duplicate-line probe.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-09-11 20:20:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-74341",
                        "url": "https://ubuntu.com/security/CVE-2026-74341",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: wcn36xx: fix heap overflow from oversized firmware HAL response  The firmware response dispatcher copies all synchronous HAL responses into the 4096-byte hal_buf without validating the response length. A response exceeding WCN36XX_HAL_BUF_SIZE causes a heap buffer overflow with firmware-controlled content.  Add a bounds check on the response length.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-08-15 06:22:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-74406",
                        "url": "https://ubuntu.com/security/CVE-2026-74406",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  vxlan: Fix potential null-ptr-deref in vxlan_gro_prepare_receive().  udp_tunnel_sock_release() could set sk->sk_user_data to NULL while vxlan_gro_prepare_receive() is running.  Let's check if rcu_dereference_sk_user_data() is NULL after skb_gro_remcsum_init().",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-08-15 06:22:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-46265",
                        "url": "https://ubuntu.com/security/CVE-2026-46265",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  RDMA/hns: Fix WQ_MEM_RECLAIM warning  When sunrpc is used, if a reset triggered, our wq may lead the following trace:  workqueue: WQ_MEM_RECLAIM xprtiod:xprt_rdma_connect_worker [rpcrdma] is flushing !WQ_MEM_RECLAIM hns_roce_irq_workq:flush_work_handle [hns_roce_hw_v2] WARNING: CPU: 0 PID: 8250 at kernel/workqueue.c:2644 check_flush_dependency+0xe0/0x144 Call trace:   check_flush_dependency+0xe0/0x144   start_flush_work.constprop.0+0x1d0/0x2f0   __flush_work.isra.0+0x40/0xb0   flush_work+0x14/0x30   hns_roce_v2_destroy_qp+0xac/0x1e0 [hns_roce_hw_v2]   ib_destroy_qp_user+0x9c/0x2b4   rdma_destroy_qp+0x34/0xb0   rpcrdma_ep_destroy+0x28/0xcc [rpcrdma]   rpcrdma_ep_put+0x74/0xb4 [rpcrdma]   rpcrdma_xprt_disconnect+0x1d8/0x260 [rpcrdma]   xprt_rdma_connect_worker+0xc0/0x120 [rpcrdma]   process_one_work+0x1cc/0x4d0   worker_thread+0x154/0x414   kthread+0x104/0x144   ret_from_fork+0x10/0x18  Since QP destruction frees memory, this wq should have the WQ_MEM_RECLAIM.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-06-03 18:16:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98681",
                        "url": "https://ubuntu.com/security/CVE-2026-98681",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  smb: client: split cifsFileInfo bitfields to avoid shared-byte RMW races  The invalidHandle, swapfile, oplock_break_cancelled, offload, and status_file_deleted fields are stored in the same bitfield byte in struct cifsFileInfo, but are updated in different code paths that may run simultaneously, and are protected by different locks.  Since bitfield assignments generate byte-level read-modify-write operations, a modification to one flag can overwrite a concurrent modification to another flag.  To avoid these races, convert these flags from a bitfield to separate bool fields.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-89539",
                        "url": "https://ubuntu.com/security/CVE-2026-89539",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  SUNRPC: reject duplicate CREDS_VALUE options  gssx_dec_option_array() walks the wire-supplied option array and, for every entry whose name matches CREDS_VALUE, calls gssx_dec_linux_creds() on the same struct svc_cred. That helper unconditionally installs a fresh groups_alloc() result into creds->cr_group_info without releasing whatever pointer was already there:      for (i = 0; i < count; i++) {         ... decode name ...         if (length == sizeof(CREDS_VALUE) &&             memcmp(p, CREDS_VALUE, sizeof(CREDS_VALUE)) == 0) {             err = gssx_dec_linux_creds(xdr, creds);             ...         }     }  A reply that carries two CREDS_VALUE entries therefore overwrites cr_group_info on the second iteration and orphans the group_info allocated by the first call. The earlier free_creds path only releases the last cr_group_info via free_svc_cred(), so the first allocation's refcount stays at one and its kvmalloc-backed storage is leaked. No in-tree caller of gssp_accept_sec_context_upcall() expects more than one CREDS_VALUE per reply.  Fix by tracking whether a CREDS_VALUE option has already been decoded and returning -EINVAL on any subsequent match, so the free_creds path releases the single group_info that was installed.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-09-11 20:19:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-93179",
                        "url": "https://ubuntu.com/security/CVE-2026-93179",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  drm/amd/powerplay: fix VoltageObjectInfo zero-stride loop and OOB read  Reject voltage objects whose usSize is smaller than the header or would advance the cursor past the table end, preventing an infinite loop or heap OOB read when the VBIOS supplies a malformed VoltageObjectInfo table.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-09-17 17:18:00 UTC"
                    },
                    {
                        "cve": "CVE-2023-52561",
                        "url": "https://ubuntu.com/security/CVE-2023-52561",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  arm64: dts: qcom: sdm845-db845c: Mark cont splash memory region as reserved  Adding a reserved memory region for the framebuffer memory (the splash memory region set up by the bootloader).  It fixes a kernel panic (arm-smmu: Unhandled context fault at this particular memory region) reported on DB845c running v5.10.y.",
                        "cve_priority": "low",
                        "cve_public_date": "2024-03-02 22:15:00 UTC"
                    },
                    {
                        "cve": "CVE-2023-53651",
                        "url": "https://ubuntu.com/security/CVE-2023-53651",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  Input: exc3000 - properly stop timer on shutdown  We need to stop the timer on driver unbind or probe failures, otherwise we get UAF/Oops.",
                        "cve_priority": "low",
                        "cve_public_date": "2025-10-07 16:15:00 UTC"
                    },
                    {
                        "cve": "CVE-2023-53733",
                        "url": "https://ubuntu.com/security/CVE-2023-53733",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net: sched: cls_u32: Undo tcf_bind_filter if u32_replace_hw_knode  When u32_replace_hw_knode fails, we need to undo the tcf_bind_filter operation done at u32_set_parms.",
                        "cve_priority": "medium",
                        "cve_public_date": "2025-10-24 12:15:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98657",
                        "url": "https://ubuntu.com/security/CVE-2026-98657",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  iio: proximity: pulsedlight: fix iio_device left registered on PM setup failure  pm_runtime_set_active() failing in probe() jumps to error_unreg_buffer, which only calls iio_triggered_buffer_cleanup() -- it does not undo the iio_device_register() that already succeeded a few lines above. probe() then returns the error, the devm-managed indio_dev is freed, but the iio core still has it registered: the sysfs/chardev nodes stay live and point at freed memory.  Add an error_unreg_dev label that unregisters the iio device before falling through to the existing buffer cleanup, mirroring the teardown order already used in lidar_remove().",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98662",
                        "url": "https://ubuntu.com/security/CVE-2026-98662",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  iio: light: gp2ap020a00f: drain irq_work after free_irq  The threaded IRQ handler queues data->work through irq_work_queue() so the trigger is polled from a per-CPU context.  free_irq() does not flush an irq_work the handler already queued, so after gp2ap020a00f_remove() returns that work may still run and call iio_trigger_poll() on data->trig, which the devm cleanup has already freed, causing a use-after-free.  Add irq_work_sync(&data->work) after free_irq() in remove() and in the probe error path, mirroring commit 78601726d4a5 (\"iio: trigger: sysfs: fix use-after-free on remove\").  Found by an in-house static analysis tool, confirmed by manual review.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98663",
                        "url": "https://ubuntu.com/security/CVE-2026-98663",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  iio: imu: adis16480: fix unprotected debugfs reads  The firmware_revision and firmware_date file operations are open coded and never call debugfs_file_get(), which debugfs_create_file_unsafe() requires. debugfs_remove_recursive() therefore does not wait for a read in progress, and unbind frees the iio_dev underneath it.  Use debugfs_create_file() instead.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98664",
                        "url": "https://ubuntu.com/security/CVE-2026-98664",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  iio: imu: adis16400: fix unprotected debugfs reads  adis16400_serial_number_fops is open coded and never calls debugfs_file_get(), so debugfs_remove_recursive() does not wait for a read in progress and unbind frees the iio_dev underneath it.  Commit ae1d37a9bb4b (\"iio: imu: adis16400: use DEFINE_DEBUGFS_ATTRIBUTE instead of DEFINE_SIMPLE_ATTRIBUTE\") converted product_id and flash_count to DEFINE_DEBUGFS_ATTRIBUTE, which protects itself, but moved all three files to debugfs_create_file_unsafe().  serial_number prints three registers as \"%.4x-%.4x-%.4x\" and DEFINE_DEBUGFS_ATTRIBUTE() formats a single u64, so it cannot be converted without changing what the file returns. adis16475 and adis16550 already use debugfs_create_file() for their open coded files. Use it here too.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98666",
                        "url": "https://ubuntu.com/security/CVE-2026-98666",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  iio: gyro: adis16136: fix unprotected debugfs reads  The serial_number file operations are open coded and never call debugfs_file_get(), which debugfs_create_file_unsafe() requires. debugfs_remove_recursive() therefore does not wait for a read in progress, and unbind frees the iio_dev underneath it.  Use debugfs_create_file() instead.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98671",
                        "url": "https://ubuntu.com/security/CVE-2026-98671",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  iio: adc: sun4i-gpadc-iio: clean up on thermal zone registration failure  If devm_thermal_of_zone_register() fails, probe returns without unregistering the IIO map array or disabling runtime PM.  Jump to err_map to release them.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98679",
                        "url": "https://ubuntu.com/security/CVE-2026-98679",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  iio: accel: kxcjk-1013: reject duplicate event disable  The IIO core does not filter duplicate writes to the event enable attribute. kxcjk1013_write_event_config() already ignores repeated enable requests, but a repeated disable request still calls kxcjk1013_set_power_state(data, false), dropping a runtime PM reference that was not acquired for this request. This can underflow the runtime PM usage count and trigger a \"Runtime PM usage count underflow\" warning.  Return early when the requested state already matches ev_enable_state.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98687",
                        "url": "https://ubuntu.com/security/CVE-2026-98687",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  thunderbolt: Reject oversized XDomain properties responses  tb_xdp_properties_request() allocates room for 45 data dwords in its 252-byte response buffer.  The XDomain length field is six bits wide, however, and a malicious peer can set it to 63.  After the fixed response fields are subtracted, the driver treats this as 48 data dwords.  Commit 322e93448d90 (\"thunderbolt: Clamp XDomain response data copy to allocation size\") only bounds the copy against data_len.  If data_len is at least 48, memcpy() reads 192 bytes from the 180-byte res->data array, causing a 12-byte heap out-of-bounds read.  Commit 4db2bd2ed478 (\"thunderbolt: Limit XDomain response copy to actual frame size\") limits the earlier copy but does not constrain this header-derived length.  Reject response data lengths that exceed the allocated source buffer before copying them into the assembled property block.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98697",
                        "url": "https://ubuntu.com/security/CVE-2026-98697",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  USB: serial: fix dynamic id driver deregistration race  Only free the dynamic ids after having deregistered the driver and removed the \"new_id\" attribute to avoid leaking any id added by a racing write to the attribute.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98698",
                        "url": "https://ubuntu.com/security/CVE-2026-98698",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: mac80211: handle empty FILS association request payload  fils_encrypt_assoc_req() accepts a (Re)Association Request frame whose last element is the FILS Session element.  crypt_len is then zero and aes_siv_encrypt() is called with an empty plaintext.  kmemdup() returns ZERO_SIZE_PTR for a zero-length allocation, so the unconditional sg_init_one() puts an invalid page into the scatterlist. With CONFIG_DEBUG_SG this triggers a kernel BUG in sg_set_buf(); without the debug check the bogus page is handed to the crypto backend.  AES-SIV is defined for empty plaintext and the S2V result is then the complete output, so handle this case before the CTR step, which has nothing to encrypt.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98701",
                        "url": "https://ubuntu.com/security/CVE-2026-98701",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: mac80211: release mesh path quota on failed additions  Repeated failed or duplicate mesh path additions can exhaust MESH_MAX_MPATHS while the path table holds fewer paths, which stops new paths to reachable destinations from being created.  mesh_path_add() reserves a slot before allocating and inserting a path. If allocation fails, the function returns without releasing the slot. If the rhashtable insertion reports an error or an existing destination, the function discards its candidate but retains the reservation. No new path is installed in any of these cases.  Release the reservation whenever the candidate is not installed.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98703",
                        "url": "https://ubuntu.com/security/CVE-2026-98703",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: mac80211: minstrel_ht: validate fixed rate index  The fixed_rate_idx debugfs file is a plain u32 attribute, so any value can be written to it.  minstrel_ht_update_stats() then copies the value into mi->max_tp_rate[] and mi->max_prob_rate, and minstrel_ht_set_rate() uses MI_RATE_GROUP()/MI_RATE_IDX() to index minstrel_mcs_groups[] (42 entries) and mi->groups[].rates[] (10 entries) with it.  Writing e.g. 65535 selects group 4095 and rate index 15, far outside both arrays.  The out-of-bounds entries are dereferenced and updated as struct minstrel_rate_stats (retry counts, etc.), so the invalid index corrupts adjacent kernel memory.  With CONFIG_UBSAN_BOUNDS the access is reported as an array-index-out-of-bounds in minstrel_ht_set_rate().  Only a valid group/rate pair, or U32_MAX to disable fixed rate processing, can be used safely, so reject any other value when the debugfs file is written.  The file is only reachable through a root-only debugfs mount, so this is not a privilege boundary.  The out-of-bounds access is still a bug that must not be reachable through a writable debugfs attribute.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98706",
                        "url": "https://ubuntu.com/security/CVE-2026-98706",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: mac80211: drain PS delivery work during station teardown  Removing an AP or mesh station can notify the driver and wake TXQs after the station has already been removed from the driver, and can update num_sta_ps and the power-save queues after station cleanup has purged them.  sta_deliver_ps_frames() tests sta->dead only before it starts delivery. A worker that passes that test can be delayed while teardown sets sta->dead and removes the station from the driver; when it resumes it still runs the full delivery.  The existing cancel_work_sync() sits near the end of __cleanup_single_sta(), after the final driver state transition and after PS accounting and queue purging, so it drains the worker only once the state it has to protect has already changed. Before commit d34ba2168a3c (\"mac80211: don't delay station destruction\") cleanup was deferred through the same ordered workqueue as the delivery work, which kept the two ordered.  Cancel the work after setting sta->dead and before moving the driver state, and move the existing cancellation to the start of __cleanup_single_sta(). The first drain closes the driver-lifetime window; driver callbacks during the remaining state transitions can still queue drv_deliver_wk through ieee80211_sta_block_awake(), so retain the second drain at the start of __cleanup_single_sta(). That drain also covers insertion failures, which reach cleanup without setting sta->dead.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98710",
                        "url": "https://ubuntu.com/security/CVE-2026-98710",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: iwlegacy: 3945: free EEPROM data on remove  il3945_pci_probe() calls il_eeprom_init(), which allocates memory for the EEPROM data. The probe failure paths release this allocation with il_eeprom_free(), but the remove path does not free it after a successful probe.  As a result, the EEPROM data is leaked when the PCI device is removed.  Free the EEPROM data in il3945_pci_remove() before releasing the mac80211 hardware structure.  This issue was found by manual code inspection.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98711",
                        "url": "https://ubuntu.com/security/CVE-2026-98711",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: cw1200: fix TX padding OOB read leaking heap data to device  The TX path rounds the transfer size up to the bus alignment (align_size(), up to 511 bytes for SDIO, 1 byte for SPI) but sends the padded length straight from the frame buffer, which has no room reserved for the padding.  cw1200_data_write() therefore reads past the end of the frame and the bus transfer carries those bytes to the device.  A bogus device can collect up to 511 bytes of kernel heap data per TX frame.  The RX path does not have this problem: it allocates the skb with the aligned length (alloc_len) before reading.  Compute the exact padding with the bus align_size() callback, make sure queued TX frames have tailroom for it, and zero the padding bytes before the transfer so nothing past the frame is exposed.  This is not expected to change driver behavior on most cases: frame contents and transfer sizes are unchanged, only the content of the padding bytes (previously undefined stale memory, now zero), which the device never reads since the WSM header carries the real frame length.  The skb expansion can only fail under memory exhaustion, in which case the frame is dropped like on the existing error paths of cw1200_tx().  Discovered by Atuin - Automated Vulnerability Discovery Engine.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98721",
                        "url": "https://ubuntu.com/security/CVE-2026-98721",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  mtd: rawnand: cadence: Initialize IRQ state before requesting IRQ  The Cadence NAND interrupt handler uses both the IRQ lock and completion object. Registering the IRQ before initializing them leaves a window in which a pending interrupt can access uninitialized synchronization state.  Initialize them before registering the handler.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98726",
                        "url": "https://ubuntu.com/security/CVE-2026-98726",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  nvme-multipath: fix underflow in ANA log bounds checks  The number of ANA groups advertised through Identify Controller sizes the ANA log buffer. The ANA log header and group descriptors independently supply the number of groups and namespace IDs to parse.  Both bounds checks subtract an untrusted object size from ana_log_size before comparing the current offset. If the object is larger than the buffer, the size_t subtraction underflows and lets the parser read beyond ana_log_buf.  Check the current offset before the first subtraction and compare each object size with the remaining buffer instead. This rejects inconsistent ANA data before dereferencing a truncated group descriptor or walking an oversized namespace ID array.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98856",
                        "url": "https://ubuntu.com/security/CVE-2026-98856",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  kprobes: Skip disarmed probes when checking optkprobe overlap  On x86, an optkprobe at A replaces five bytes with a jump. If a disabled probe B is at A+2, get_optimized_kprobe() stops at B when arming a new probe C at A+4. It leaves A optimized:                A    A+1  A+2  A+3  A+4   A's jump  | e9 | d0 | d1 | d2 | d3 |   after C   | e9 | d0 | d1 | d2 | cc |  The INT3 for C overwrites the last byte of A's jump displacement, so execution can jump to the wrong address. B can have prepared optinsns while disarmed, but has no jump to unoptimize.  Continue past disarmed and unprepared probes to find the active optimized probe before arming a probe in its jump.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98857",
                        "url": "https://ubuntu.com/security/CVE-2026-98857",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ipvs: bound LBLCR and LBLC cache growth  ip_vs_lblcr_new() and ip_vs_lblc_new() create cache entries for every previously unseen destination address. The table max_size only tells the periodic collector to reclaim entries after the cache has already exceeded the limit. It does not reclaim entries that the attacker continues to use.  Reject new cache entries once either table reaches max_size * 3 / 2. The extra headroom lets the periodic collector catch up while the existing scheduler fallback continues to use the selected destination when cache creation fails. New traffic therefore stays serviceable without growing the tables further.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98732",
                        "url": "https://ubuntu.com/security/CVE-2026-98732",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  Bluetooth: btintel: fix buffer over-read in btintel_hw_error()  The \"Exception info %s\" print uses skb->data + 1, but the 12-byte payload is not guaranteed to be NUL-terminated and can be read past its end.  Bound the print with \"%.*s\" and skb->len - 1.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98735",
                        "url": "https://ubuntu.com/security/CVE-2026-98735",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  Bluetooth: hci_core: Serialize ACL scheduling with channel deletion  hci_chan_sent() selects a channel under RCU but drops the read lock before accessing chan->conn and returning the channel. The ACL and LE schedulers then use its packet queue and update its transmit counters without any protection against channel deletion.  After TX selects a channel and releases RCU, a disconnect command timeout on the separate request workqueue can run hci_conn_failed() and l2cap_conn_del(). hci_chan_del() can then unlink the channel, complete synchronize_rcu(), purge its queue and free it before TX resumes. This causes use-after-free both in hci_chan_sent() and in its callers.  KASAN reported:    BUG: KASAN: slab-use-after-free in hci_chan_sent+0x892/0x9b0   Workqueue: hci0 hci_tx_work   Call Trace:    hci_chan_sent+0x892/0x9b0    hci_tx_work+0x5e6/0xb70   Allocated by task 91:    hci_chan_create+0xe3/0x350    l2cap_conn_add.part.0+0x12/0xa30    l2cap_chan_connect+0x110d/0x1b60    l2cap_sock_connect+0x310/0x530   Freed by task 99:    hci_chan_del+0x11f/0x170    l2cap_conn_del+0x4f1/0x800    l2cap_connect_cfm+0x88c/0xd30    hci_conn_failed+0x150/0x250    hci_abort_conn_sync+0x3e3/0x800    hci_cmd_sync_run+0x7e/0xc0    hci_abort_conn+0x105/0x1f0    disconnect_sync+0x157/0x290    hci_cmd_sync_work+0x13c/0x290  Hold the existing device mutex across channel selection and transmission in both schedulers to serialize them with channel teardown. Keep timeout handling outside the critical sections because hci_link_tx_to() acquires the same mutex. This also permits the transmit path to sleep, unlike extending the RCU read-side critical section across packet submission.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98739",
                        "url": "https://ubuntu.com/security/CVE-2026-98739",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  Bluetooth: RFCOMM: Fix initial port reference race  For RFCOMM_RELEASE_ONHUP devices, rfcomm_tty_install() and __rfcomm_release_dev() both use RFCOMM_TTY_OWNED to decide who drops the initial tty_port reference. The release path tests the bit separately from the install path setting it, so both can drop that reference.  The synchronous hangup does not prevent this race: port->tty is not assigned until tty_port_open(), after installation. The following interleaving is possible:    1. Install and release each obtain a reference with rfcomm_dev_get().   2. Release observes RFCOMM_TTY_OWNED clear.   3. Install sets RFCOMM_TTY_OWNED and drops the initial reference.   4. Release drops the same initial reference again.   5. TTY cleanup drops its reference and frees the device.   6. Release performs its final tty_port_put() on the freed port.  KASAN reported:    BUG: KASAN: slab-use-after-free in tty_port_put+0x22/0x190   Write of size 4 at addr ffff8881001d3d5c by task poc/92    Call Trace:    tty_port_put+0x22/0x190    rfcomm_dev_ioctl+0x1d4/0x1930    sock_do_ioctl+0x110/0x260    sock_ioctl+0x380/0x590    __x64_sys_ioctl+0x134/0x1c0    Allocated by task 88:    rfcomm_dev_ioctl+0x8f6/0x1930    sock_do_ioctl+0x110/0x260    sock_ioctl+0x380/0x590    __x64_sys_ioctl+0x134/0x1c0    Freed by task 65:    kfree+0x131/0x3c0    rfcomm_dev_destruct+0x23b/0x2f0    release_one_tty+0xc1/0x370    process_one_work+0x661/0x1090  Use test_and_set_bit() in both paths so that only the caller that changes RFCOMM_TTY_OWNED from clear to set drops the initial reference. Each path keeps its own lookup reference until release or TTY cleanup, preserving the existing callback ordering and error handling.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98741",
                        "url": "https://ubuntu.com/security/CVE-2026-98741",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ALSA: ua101: reject mismatched capture/playback packet sizes  detect_usb_format() cross-checks bSubframeSize, bBitResolution and tSamFreq between the capture and playback interfaces, but never relates the two endpoints' wMaxPacketSize and bNrChannels.  Each playback URB gets a buffer of ua->playback.max_packet_bytes, while the number of bytes written into it is derived from the capture stream: capture_urb_complete() computes frames from the received capture packet and capture.frame_bytes, and start_usb_playback() and playback_work() multiply that by playback.frame_bytes.  A device declaring a large capture wMaxPacketSize with few capture channels and a small playback wMaxPacketSize with many playback channels therefore memset()s and memcpy()s past the end of the playback buffer, in open() of the PCM node the driver registers during probe. usb_submit_urb() rejects the over-long iso_frame_desc[0].length with -EMSGSIZE, but only after the write.  Reject such descriptors at probe time.  Genuine UA-101/UA-1000 hardware declares proportional packet sizes and is unaffected.    BUG: KASAN: slab-out-of-bounds in start_usb_playback (sound/usb/misc/ua101.c:586)   Write of size 2048 at addr ffff8881098f3c00 by task exploit/5021   Call Trace:    __asan_memset (mm/kasan/shadow.c:84)    start_usb_playback (sound/usb/misc/ua101.c:586)    playback_pcm_open (sound/usb/misc/ua101.c:679)    snd_pcm_open_substream (sound/core/pcm_native.c:2829)    snd_pcm_open (sound/core/pcm_native.c:2865 sound/core/pcm_native.c:2932)    snd_pcm_playback_open (sound/core/pcm_native.c:2891)    snd_open (sound/core/sound.c:166)    chrdev_open (fs/char_dev.c:411)    do_dentry_open (fs/open.c:996)    vfs_open (fs/open.c:1101)    path_openat (fs/namei.c:4837 fs/namei.c:5000)    do_file_open (fs/namei.c:5029)    do_sys_openat2 (fs/open.c:1417)    __x64_sys_openat (fs/open.c:1423 fs/open.c:1439 fs/open.c:1434)    do_syscall_64 (arch/x86/entry/syscall_64.c:61 arch/x86/entry/syscall_64.c:84)    entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:121)    The buggy address belongs to the object at ffff8881098f3c00    which belongs to the cache kmalloc-192 of size 192   The buggy address is located 0 bytes inside of    allocated 168-byte region [ffff8881098f3c00, ffff8881098f3ca8)",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98940",
                        "url": "https://ubuntu.com/security/CVE-2026-98940",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ASoC: qcom: lpass-cpu: use DAI table index for playback constraints  The DAI ID is a hardware port ID and is not necessarily the index of the corresponding entry in variant->dai_driver.  When configuring a DAI with LPAIF_I2SCTL_MODE_QUAD01, the probe code currently uses dai_id to index variant->dai_driver. This is incorrect for platforms where DAI IDs are sparse. For example, the IPQ806x MI2S DAI has ID 4 while it is the only entry in the DAI driver table. If that DAI is configured for QUAD01 and probe reaches this branch, the code writes beyond that single entry via dai_driver[4] instead of updating the DAI being processed.  Use the loop index i when updating the current DAI's playback channel constraints, while retaining dai_id for indexing the hardware-port specific playback SD-line mode array.  This fixes the incorrect DAI table access for platforms where the DAI ID does not match its position in the driver table.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98748",
                        "url": "https://ubuntu.com/security/CVE-2026-98748",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  serial: 8250_bcm7271: fix use-after-free in brcmuart_remove()  brcmuart_handle_irq() starts priv->hrt to work around a receive-timeout quirk of the 8250 core when hardware flow control is enabled; the timer callback brcmuart_hrtimer_func() dereferences priv.  brcmuart_remove() cancels the hrtimer before it unregisters the port, so a receive-timeout interrupt that arrives in between re-arms the timer. After devm frees priv, the callback runs on freed memory.  Unregister the port before cancelling the hrtimer. serial8250_unregister_port() shuts the port down and frees its IRQ, so brcmuart_handle_irq() can no longer restart the timer, and the final hrtimer_cancel() drains any timer that was armed before or during the unregister.  This issue was found by an in-house static analysis tool.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98754",
                        "url": "https://ubuntu.com/security/CVE-2026-98754",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  tty: vcc: hold port lock when clearing tty pointer in vcc_cleanup  vcc_cleanup() sets port->tty to NULL without holding port->lock, racing with vcc_event() LDC callbacks that read port->tty under port->lock and then use tty->port. This can cause a use-after-free when the callback dereferences tty->port after cleanup has already destroyed and freed it.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98755",
                        "url": "https://ubuntu.com/security/CVE-2026-98755",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  tty: vcc: zero-initialize control packet in vcc_send_ctl()  The stack-allocated struct vio_vcc pkt was partially initialized, leaving the tag.stype_env field uninitialized before being sent via ldc_write(), potentially leaking kernel stack data to the LDC peer.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98756",
                        "url": "https://ubuntu.com/security/CVE-2026-98756",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  usb: cdns3: Fix NULL pointer dereference in cdns3_pci_probe  The Cadence USBSS controller is a two-function PCI device. The first probed function allocates the driver data and stores it with pci_set_drvdata(), while the second function reuses it via pci_get_drvdata() when pci_is_enabled() reports that the first function has already been probed.  When the second function is probed while the first one has been enabled but has not yet set its driver data, pci_get_drvdata() returns NULL, and the subsequent wrap->devfn assignment dereferences a NULL pointer and crashes the kernel. logs: Call trace:   cdns3_pci_probe+0xa4/0x300   local_pci_probe+0x44/0xa8   pci_call_probe+0x54/0x158   pci_device_probe+0x84/0x100   really_probe+0x184/0x3d0   __driver_probe_device+0x80/0x178   driver_probe_device+0x44/0xe8   __driver_attach+0xec/0x1f8   bus_for_each_dev+0x7c/0xe0   driver_attach+0x28/0x38   bus_add_driver+0x110/0x238   driver_register+0x64/0x128   __pci_register_driver+0x50/0x60   cdns3_pci_driver_init+0x28/0x38   do_one_initcall+0x5c/0x280   do_initcalls+0x104/0x1d8   kernel_init_freeable+0x140/0x218   kernel_init+0x28/0x1f8   ret_from_fork+0x10/0x20  Return -EPROBE_DEFER in this case so that probing is retried after the first function has completed its probe.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98757",
                        "url": "https://ubuntu.com/security/CVE-2026-98757",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  usb: cdns3: fix use-after-free in cdns3_gadget_exit()  cdns3_gadget_start() arms two works on system_freezable_wq: pending_status_wq for the deferred ep0 status stage and aligned_buf_wq for realigned request buffers. Both handlers use the cdns3_device the works are embedded in, and cdns3_pending_setup_status_handler() also calls the ep0 request completion.  cdns3_gadget_exit() does not wait for these works. It frees all endpoints and aligned buffers and drops the last reference to the gadget device, which frees priv_dev, so a work queued before the exit can run after the free.  Fix this by waiting for both works after the gadget driver is unbound and the IRQ is freed, when no new work can be queued, and before the endpoints and buffers are released.  This issue was found by an in-house static analysis tool.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98760",
                        "url": "https://ubuntu.com/security/CVE-2026-98760",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  usb: typec: tipd: fix uninitialized typec_partner_desc in tps6598x_connect()  tps6598x_connect() passes a stack-allocated typec_partner_desc to typec_register_partner() after initializing only usb_pd, accessory and identity.  typec_register_partner() copies attach and deattach from the descriptor into the partner. With those fields left unset, garbage function pointers may be stored and later invoked from typec_partner_link_device() when a USB device is linked to the port. Uninitialized pd_revision and usb_capability similarly leak stack data through partner sysfs.  Zero-initialize the descriptor so optional callbacks remain NULL and the remaining fields are zero.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98761",
                        "url": "https://ubuntu.com/security/CVE-2026-98761",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  usb: typec: tcpm: recover after failure to start the frs ams  Reset the port if the tcpm fails to start the FAST_ROLE_SWAP AMS by initiating error recovery on it.  This helps in cases where some cables (incorrectly) signal an FRS to an FRS capable port during disconnection. The TCPC autonomously starts sourcing VBUS on detecting the FRS signal. However, the VBUS sourcing is left on when the FAST_ROLE_SWAP AMS fails to start (as tcpm_sink_tx_ok is 0 as CC is open due to the cable disconnect). This is because the code sets the state to INVALID_STATE without resetting the port state.  Log snippet before changes: [  101.401960] AMS FAST_ROLE_SWAP start [  101.401971] Sink TX No Go [  101.401982] sourcing vbus [  101.401987] VBUS on [  101.402159] VBUS on [  109.257809] CC1: 0 -> 0, CC2: 5 -> 0 [state SNK_READY, polarity 1, disconnected] [  111.267442] VBUS on  After changes: [   70.541211] AMS FAST_ROLE_SWAP start [   70.541220] Sink TX No Go [   70.541228] state change SNK_READY -> ERROR_RECOVERY [rev3 NONE_AMS] [   70.541362] VBUS on [   70.541365] sourcing vbus [   70.541367] VBUS on [   70.541374] state change ERROR_RECOVERY -> PORT_RESET [rev3 NONE_AMS] [   70.541410] disable vbus discharge ret:0 [   70.543028] Setting usb_comm capable false [   70.544009] Setting voltage/current limit 0 mV 0 mA [   70.544034] polarity 0 [   70.544239] Requesting mux state 0, usb-role 0, orientation 0 [   70.555550] cc:=0 [   70.555595] pending state change PORT_RESET -> PORT_RESET_WAIT_OFF @ 100 ms [rev3 NONE_AMS] [   70.555697] VBUS off [   70.555702] VBUS VSAFE0V [   70.555762] CC1: 5 -> 0, CC2: 0 -> 0 [state PORT_RESET, polarity 0, disconnected] [   70.587794] VBUS off [   70.587799] VBUS VSAFE0V [   70.655672] state change PORT_RESET -> PORT_RESET_WAIT_OFF [delayed 100 ms] [   70.655682] state change PORT_RESET_WAIT_OFF -> SNK_UNATTACHED [rev3 NONE_AMS] [   70.655686] Start toggling [   70.656274] CC1: 0 -> 0, CC2: 0 -> 0 [state TOGGLING, polarity 0, disconnected]",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98763",
                        "url": "https://ubuntu.com/security/CVE-2026-98763",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  usb: core: clear both ep_in and ep_out for non-ep0 control endpoints  In usb_enable_endpoint(), non-zero control endpoints (where usb_endpoint_xfer_control(&ep->desc) is true) populate both dev->ep_in[epnum] and dev->ep_out[epnum] with the same struct usb_host_endpoint pointer.  However, usb_disable_endpoint() only clears either dev->ep_out[epnum] or dev->ep_in[epnum] depending on the direction bit of epaddr when reset_hardware is set, leaving the opposite direction's array slot pointing to the disabled/freed endpoint.  Clear both dev->ep_out[epnum] and dev->ep_in[epnum] when disabling a non-ep0 control endpoint with reset_hardware set, and update the function kerneldoc accordingly.  Tested in QEMU against Linux 7.3.0-rc3 using dummy_hcd and raw-gadget to enumerate a USB device with a non-zero control endpoint (bEndpointAddress 0x01, bmAttributes USB_ENDPOINT_XFER_CONTROL), verifying that both dev->ep_in[1] and dev->ep_out[1] are cleared when the interface is disabled.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98764",
                        "url": "https://ubuntu.com/security/CVE-2026-98764",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  usb: gadget: f_fs: Fix NULL pointer dereference in FUNCTIONFS_ENDPOINT_DESC  When user space sets up FunctionFS with only full-speed descriptors (e.g., flags = FUNCTIONFS_HAS_FS_DESC) and the gadget operates at a higher speed (such as USB_SPEED_HIGH or USB_SPEED_SUPER), config_ep_by_speed() detects that the function lacks descriptors for the current speed, logs a warning, and falls back to full-speed descriptors. The endpoint is then successfully enabled via usb_ep_enable(), and epfile->ep becomes valid.  However, when user space subsequently issues the FUNCTIONFS_ENDPOINT_DESC ioctl to query the endpoint descriptor, ffs_epfile_ioctl() selects the descriptor index solely based on gadget->speed:  \tswitch (epfile->ffs->gadget->speed) { \tcase USB_SPEED_SUPER: \tcase USB_SPEED_SUPER_PLUS: \t\tdesc_idx = 2; \t\tbreak; \tcase USB_SPEED_HIGH: \t\tdesc_idx = 1; \t\tbreak; \tdefault: \t\tdesc_idx = 0; \t} \tdesc = epfile->ep->descs[desc_idx]; \tmemcpy(&desc1, desc, desc->bLength);  Because user space only supplied full-speed descriptors, epfile->ep->descs[1] is NULL. Dereferencing desc->bLength triggers an immediate kernel NULL pointer dereference panic.  Fix this by falling back through lower speed descriptors if the current speed descriptor was not supplied, matching the fallback logic in config_ep_by_speed() and historical f_fs behavior. If still missing, fall back to epfile->ep->ep->desc (the active descriptor), and return -EINVAL safely if no valid descriptor is found. In addition, mark desc as const to match struct usb_ep::desc and avoid discarding qualifiers.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98765",
                        "url": "https://ubuntu.com/security/CVE-2026-98765",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  USB: gadget: dummy-hcd: Fix wait for outstanding request completions  The dummy-hcd driver emulates synchronize_irq() by waiting until its private callback_usage counter drops to 0 (with the private lock not held).  This counter is incremented whenever a gadget driver callback occurs (which requires the private lock to be dropped), but not when a request completion handler is called.  This is an oversight.  Request completion is triggered by timer interrupts (emulating device IRQs in a real UDC), and the interrupt handlers are supposed to have completed when the synchronize_irq() emulation routine returns -- they aren't supposed to be in the middle of a completion callback.  If this happens it can lead to a gadget driver's unbind routine running before all outstanding request completions have finished, maybe even allowing the gadget driver's module to be unloaded while a completion handler is still running.  Fix the oversight by incrementing the callback_usage value across request completion callbacks.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98766",
                        "url": "https://ubuntu.com/security/CVE-2026-98766",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  usb: gadget: aspeed-vhub: cancel wake work on device removal  wake_work is armed from the gadget .wakeup callback to resume suspended downstream ports, and it is never cancelled in ast_vhub_remove(), so a work item queued before or during removal can run after devm has freed vhub and its ports, a use-after-free.  Cancelling the work alone is not sufficient: usb_gadget_wakeup() takes no lock and the unbind path never clears wakeup_en, so a remote-wakeup request in flight on another CPU can re-arm the work after the cancel and before vhub is freed.  ast_vhub_del_dev() already clears d->registered under vhub->lock before unregistering the gadget. Refuse the wakeup in ast_vhub_udc_wakeup() once d->registered is clear: the check and the schedule_work() are then atomic against the unbind, so a wakeup that passed before the flag was cleared is drained by the cancel_work_sync() after the del_dev loop, and one that arrives later returns without arming. Also move INIT_WORK() to the top of ast_vhub_probe(), since the probe error path reuses ast_vhub_remove() and would otherwise cancel a never-initialized work item.  This issue was found by an in-house static analysis tool.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98769",
                        "url": "https://ubuntu.com/security/CVE-2026-98769",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  usb: gadget: f_uac1_legacy: validate bRequest index in generic_{set,get}_cmd  generic_set_cmd() and generic_get_cmd() use the low nibble of ctrl->bRequest as an index into con->data[]:      u8 cmd = (ctrl->bRequest & 0x0F);  /* 0 .. 15 */     ...     con->data[cmd] = value;            /* OOB when cmd >= 5 */  struct usb_audio_control (include/linux/usb/audio.h) declares data as a 5-element array, so indices 5 through 15 write (or read) up to 44 bytes past the end of the array on the heap.  A malicious USB host can craft a class-specific SET_CUR / GET_CUR request with an arbitrary bRequest value, triggering the out-of-bounds access from an IRQ completion handler with no further preconditions.  Add an ARRAY_SIZE() guard to both functions.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98771",
                        "url": "https://ubuntu.com/security/CVE-2026-98771",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  usb: storage: sierra_ms: reject short SWoC info transfers  sierra_get_swoc_info() requests sizeof(struct swoc_info) (60) bytes from the device via usb_control_msg(), but its callers only treat a negative return value as failure. A device that answers the vendor-specific GetSwocInfo request with a short IN transfer is therefore accepted, leaving the tail of the freshly allocated (kmalloc(), non-zeroing) swoc_info buffer uninitialized.  truinst_show() subsequently prints swocInfo->rev, swocInfo->LinuxSKU and swocInfo->LinuxVer from that buffer into the world-readable (0444) \"truinst\" sysfs attribute. An emulated/malicious USB device (VID 0x1199, PID 0x0fff) can exploit this to disclose up to 5 bytes of stale kernel heap memory (kmalloc-64) to unprivileged userspace, once per sysfs read, indefinitely. On kernels built without init_on_alloc this leaks recently freed heap contents.  Only accept the transfer when the full structure was received. sierra_ms_init() already retries failed queries, so well-behaved devices are unaffected.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98772",
                        "url": "https://ubuntu.com/security/CVE-2026-98772",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  USB: serial: fix port tear down use-after-free  Some drivers for multiport devices access port driver data from completion handlers of shared URBs submitted at attach() or first open() and stopped at disconnect() or last close(), respectively.  A simple NULL check before accessing the driver data makes sure that a port state container has at least been allocated, but a completion handler can still race with port tear down.  Reorder the disconnect handling so that ports are not deregistered (and their driver data freed) until after all ports have been hung up and the driver disconnect() callback has run so that all I/O has been stopped.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98775",
                        "url": "https://ubuntu.com/security/CVE-2026-98775",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  nitro_enclaves: fix use-after-free on SLOT_ALLOC failure  When ne_create_vm_ioctl() fails the SLOT_ALLOC request after anon_inode_getfile() has succeeded, the error path calls fput(enclave_file) and then frees ne_enclave.  In normal userspace context, fput() defers the final __fput() via task_work. ne_enclave_release() therefore runs after ne_enclave has already been freed and dereferences ne_enclave->slot_uid, causing a use-after-free: KASAN: slab-use-after-free in ne_enclave_release.  The enclave has no slot allocated and is not yet linked into the enclaves list on this error path, so ne_enclave_release() is expected to return early when slot_uid is zero. However, reading slot_uid already accesses the freed object.  Clear enclave_file->private_data before fput() on the error path. ne_enclave_release() then returns immediately when private_data is NULL, leaving the ioctl error path as the sole owner of ne_enclave. This is safe because the file has not been fd_install()'d yet.  Tested on an AWS EC2 m5.2xlarge with CONFIG_KASAN=y. Without the patch, the reproducer triggers a KASAN slab-use-after-free on every SLOT_ALLOC failure. With the patch, no KASAN report is produced and the SLOT_ALLOC error is still returned. Normal enclave creation and teardown are unaffected.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98790",
                        "url": "https://ubuntu.com/security/CVE-2026-98790",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  perf: Fix race between perf_event_exit_task() and perf_pending_task()  A race condition exists between perf_event_exit_task() and perf_pending_task() during begin_new_exec().  During begin_new_exec(), perf_event_exit_task() may be called, and the PF_EXITING flag is not set on task. So perf_sigtrap() continues to execute and triggers WARN_ON_ONCE(event->ctx->task != current).  Since both task exit and exec paths can call perf_event_exit_task() which sets ctx->task to TASK_TOMBSTONE, fix this by explicitly checking if event->ctx->task equals TASK_TOMBSTONE and dropping the redundant PF_EXITING check.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98934",
                        "url": "https://ubuntu.com/security/CVE-2026-98934",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ipv6: sr: use skb_get_hash_net() in seg6_make_flowlabel()  Since commit d58e468b1112 (\"flow_dissector: implements flow dissector BPF hook\") __skb_flow_dissect() needs a net pointer, either from skb->dev, skb->sk, or since commit 3cbf4ffba5ee (\"net: plumb network namespace into __skb_flow_dissect\") a caller provided pointer.  syzbot was able to reach seg6_make_flowlabel() with an skb having neither skb->dev nor skb->sk set: a TIPC UDP bearer sends a discovery message through an IPv4 route using seg6 encap, while net.ipv6.seg6_flowlabel is set to 1.  seg6_make_flowlabel() already has a net pointer, use skb_get_hash_net().  WARNING: net/core/flow_dissector.c:1131 at __skb_flow_dissect+0x910/0x5368 net/core/flow_dissector.c:1126, CPU#0: syz.0.17/4930 Call trace:   __skb_flow_dissect+0x910/0x5368 net/core/flow_dissector.c:1126 (P)   __skb_get_hash_net+0xe0/0x29c net/core/flow_dissector.c:1903   skb_get_hash include/linux/skbuff.h:1663 [inline]   seg6_make_flowlabel+0xcc/0x1ec net/ipv6/seg6_iptunnel.c:132   __seg6_do_srh_encap+0x320/0xbf4 net/ipv6/seg6_iptunnel.c:161   seg6_do_srh+0x4b4/0xa44 net/ipv6/seg6_iptunnel.c:431   seg6_output_core+0x164/0x688 net/ipv6/seg6_iptunnel.c:681   seg6_output+0x44/0x1ac net/ipv6/seg6_iptunnel.c:744   lwtunnel_output+0x3d0/0x664 net/core/lwtunnel.c:356   dst_output include/net/dst.h:470 [inline]   ip_local_out+0x110/0x148 net/ipv4/ip_output.c:131   iptunnel_xmit+0x50c/0xd38 net/ipv4/ip_tunnel_core.c:97   udp_tunnel_xmit_skb+0x220/0x348 net/ipv4/udp_tunnel_core.c:187   tipc_udp_xmit+0x75c/0x9c0 net/tipc/udp_media.c:202   tipc_udp_send_msg+0x214/0x374 net/tipc/udp_media.c:274   tipc_bearer_xmit_skb+0x260/0x3b0 net/tipc/bearer.c:576   tipc_enable_bearer net/tipc/bearer.c:366 [inline]   __tipc_nl_bearer_enable+0xc90/0xfb0 net/tipc/bearer.c:1048   tipc_nl_bearer_enable+0x2c/0x48 net/tipc/bearer.c:1057   genl_family_rcv_msg_doit+0x1e4/0x2d4 net/netlink/genetlink.c:1114",
                        "cve_priority": "negligible",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2022-49622",
                        "url": "https://ubuntu.com/security/CVE-2022-49622",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  netfilter: nf_tables: avoid skb access on nf_stolen  When verdict is NF_STOLEN, the skb might have been freed.  When tracing is enabled, this can result in a use-after-free: 1. access to skb->nf_trace 2. access to skb->mark 3. computation of trace id 4. dump of packet payload  To avoid 1, keep a cached copy of skb->nf_trace in the trace state struct. Refresh this copy whenever verdict is != STOLEN.  Avoid 2 by skipping skb->mark access if verdict is STOLEN.  3 is avoided by precomputing the trace id.  Only dump the packet when verdict is not \"STOLEN\".",
                        "cve_priority": "medium",
                        "cve_public_date": "2025-02-26 07:01:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98794",
                        "url": "https://ubuntu.com/security/CVE-2026-98794",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ipvs: filter some flags received in the backup server  While the IPVS SYNC protocol is not secure by design we can still protect the backup server from messages that can wreak havoc.  This commit addresses problems from received connection flags or their combinations. We now drop messages as follows:  1. the NO_CPORT+TEMPLATE combination allows lookups for normal connections to hit template which can break in many ways. While the master does not sync connections with NO_CPORT flag, i.e. before they are established, we still accept NO_CPORT without TEMPLATE.  2. ONE_PACKET: it is not sent by master, so we do not expect it in backup. Before now it was ignored by IP_VS_CONN_F_BACKUP_MASK for protocol v1 while protocol v0 created connections that are not hashed and dropped immediately. Better to apply the IP_VS_CONN_F_BACKUP_MASK also to the flags from v0 messages for consistency with v1.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98805",
                        "url": "https://ubuntu.com/security/CVE-2026-98805",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  tipc: prevent GCM nonce reuse on peer key changes  TIPC can encrypt traffic between nodes using a different transmit key for each node. In this mode, the AES-GCM nonce for a packet sent to a known peer consists of a 32-bit prefix (a per-key salt XOR the peer's address) followed by a 64-bit counter. That counter is stored in the peer's RX crypto object. When the peer reports a change in which key it uses to receive packets, TIPC resets this counter. The sender can still be using the same TX key and salt, so subsequent packets reuse earlier nonces. This nonce reuse breaks confidentiality and exposes GCM's authentication key. This makes forgeries trivial: an attacker can exploit CTR malleability to alter captured ciphertexts and use the recovered authentication key to compute a valid tag for the modified ciphertext, under the same key and nonce.  Use the TX key's existing aead->seqno counter instead. All encryptions using that key object share the same atomic counter, so concurrent encryptions get distinct nonce counter values. The counter survives key activation and peer reconnection, and peer key-status reports cannot reset it. This prevents those transitions from causing nonce reuse while the same TX key remains installed.  The nonce format is unchanged, and receivers do not require consecutive counter values, so sharing the counter across peers remains compatible with existing receivers. A pre-existing check still invokes key revocation in the unlikely event that the counter wraps to zero.",
                        "cve_priority": "critical",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98811",
                        "url": "https://ubuntu.com/security/CVE-2026-98811",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net/sched: cls_api: reclaim an empty proto on the error path  Two racing tc filter add requests on the same chain/prio of an unlocked classifier both run change() on the shared proto and both can fail: the winner's tcf_chain_tp_delete_empty() attempt gives up because the loser's handle is still in the idr, and the loser's error path drops only its own reference without a second reclamation attempt. The empty proto stays linked in the chain, holding the chain reference, a block reference and the classifier module reference until the chain or block is torn down.  Reclaim the proto on the error path of any failed request that holds a proto reference. The reclamation is emptiness-gated: tcf_chain_tp_delete_empty() unlinks the proto only when delete_empty() admits it is empty, so a live shared proto is never unlinked. A proto the request created is reclaimed unconditionally - it is the only owner, so marking it for deletion is safe even without a delete_empty callback. Classifiers without one (the check marks the proto unconditionally) are rtnl-serialized, so the raced window this guard closes cannot arise for them.  This is a follow-up to commit d4e359b3608a (\"net/sched: cls_api: fix teardown of an adopted proto on insert-race loss\"), which stopped the loser of the insert race from unlinking the winner's live proto but left the empty-proto residual in place.  Conditions to recreate: - CONFIG_NET_CLS_FLOWER=y; veth pair - tc qdisc add dev veth0 ingress - two concurrent `tc filter add dev veth0 ingress protocol ip pref 1   flower skip_sw ... action drop` (both fail in fl_hw_replace_filter   after publishing their handle in the idr); repeat in a loop - an empty flower tp stays linked after both requests fail; visible   as a bare `filter protocol ip pref 1 flower chain 0` header in   `tc filter show` with no filter entries - CAP_NET_ADMIN (namespace-local via unshare -Urn suffices)",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98812",
                        "url": "https://ubuntu.com/security/CVE-2026-98812",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net/mctp: publish the mctp_dev only after it is initialised  mctp_add_dev() links the new mctp_dev into dev->mctp_ptr before mdev->dev is assigned, so a reader that picks the device up in that window dereferences a net_device pointer that is still NULL:  KASAN: null-ptr-deref in range [0x00000000000000b0-0x00000000000000b7] Call Trace:  <TASK>  ? __pfx_mctp_sendmsg (./include/linux/sockptr.h:49)  ? __pfx_mctp_dst_output (net/mctp/route.c:41)  ? selinux_socket_sendmsg (security/selinux/hooks.c:5278)  ____sys_sendmsg (net/socket.c:775 (discriminator 1) net/socket.c:790  (discriminator 1) net/socket.c:2684 (discriminator 1))  ? __pfx_____sys_sendmsg (net/socket.c:1131)  ? __pfx_copy_msghdr_from_user (net/socket.c:2590)  ? update_cfs_rq_load_avg (kernel/sched/fair.c:5478)  ___sys_sendmsg (net/socket.c:2738)  ? __pfx____sys_sendmsg (net/socket.c:2625)  ? perf_event_task_tick (./include/linux/rcupdate.h:838)  ? sched_tick (kernel/sched/core.c:5818)  ? clockevents_program_event (kernel/time/clockevents.c:372)  ? fdget (./include/linux/rcupdate.h:873 fs/file.c:1100)  __sys_sendmsg (net/socket.c:2770)  ? __pfx___sys_sendmsg (net/socket.c:2751)  do_syscall_64 (arch/x86/entry/syscall_64.c:63)  entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:121)  </TASK>  Fix by publishing only once the object is fully initialised: __mctp_dev_get() runs under rcu_read_lock() only and hands this object to readers as soon as mctp_ptr is assigned, so they must never observe mdev->dev == NULL.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98819",
                        "url": "https://ubuntu.com/security/CVE-2026-98819",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  Bluetooth: btintel: validate DDC record lengths  Parse DDC record lengths in unsigned storage so 0xFF does not wrap. Reject records smaller than the mandatory three-byte header, records exceeding U8_MAX, and records exceeding remaining firmware bytes before issuing Intel_Write_DDC.  This issue was reported by Claude Mythos.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98823",
                        "url": "https://ubuntu.com/security/CVE-2026-98823",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: cfg80211: preserve hidden-group beacon IE ownership  A hidden-group probe-response entry borrows its beacon IEs from the group's beacon entry. cfg80211_update_assoc_bss_entry() can pass such an entry to cfg80211_update_known_bss() when merging scan entries after a channel switch.  Copying the borrowed beacon_ies into the associated entry gives the same allocation two owners. Releasing the group's beacon entry can then leave the associated entry pointing to freed IEs, which are freed again when that entry is released.  Skip beacon IE replacement when the source entry belongs to a hidden group. Preserve probe-response processing, the subsequent metadata updates, and the existing rejection path for conflicting hidden beacon updates.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98936",
                        "url": "https://ubuntu.com/security/CVE-2026-98936",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: ath11k: reset ar->num_stations on hardware start  When (multiple) hw restart occurs, we end up in a situation where we cannot accept new stations / mesh peers. This seems to be the 'num_stations' in 'struct ath11k' that did not get reset properly in this case. In ath11k_mac_op_start(), it was indeed the only accounting var that did not get reset so let's clear it too.  This avoids problems like those:  \t[1248828.088023] WARNING: CPU: 0 PID: 12281 at net/mac80211/util.c:1682 ieee80211_reconfig_stations+0x98/0xc0 \t[1248828.088115] Call trace: \t[1248828.088116]  ieee80211_reconfig_stations+0x98/0xc0 (P) \t[1248828.088119]  ieee80211_reconfig+0x774/0x1438 \t[1248828.088123]  ieee80211_restart_work+0x10c/0x178 \t[1248828.088127]  process_one_work+0x178/0x3c0 \t[1248828.088130]  worker_thread+0x280/0x440 \t[1248828.088133]  kthread+0xe0/0xf8 \t[1248828.088137]  ret_from_fork+0x10/0x20 \t[1248828.088141] ---[ end trace 0000000000000000 ]--- \t[1248836.686604] ath11k_pci 0000:04:00.0: refusing to associate station: too many connected already (128) \t[1248836.686609] ath11k_pci 0000:04:00.0: Failed to add station: xx:xx:xx:xx:xx:xx for VDEV: 1  Tested-on: QCN9074 hw1.0 PCI WLAN.HK.2.9.0.1-01977-QCAHKSWPL_SILICONZ-1",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98831",
                        "url": "https://ubuntu.com/security/CVE-2026-98831",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  of/overlay: don't leak fragment references when changeset init fails  init_overlay_changeset() stores the number of initialized fragments in ovcs->count only on full success. When find_target() or the __symbols__ lookup fails partway through, the target and overlay references taken for the fragments initialized so far are never dropped: free_overlay_changeset() bounds its cleanup loop by ovcs->count, which is still 0.  Store the running count on the error path so free_overlay_changeset() puts whatever was set up. The store is guarded by ovcs->fragments because on the allocation-failure path cnt still holds the counting pass total while there is no fragments array; everywhere else cnt only counts fully-initialized fragments.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98833",
                        "url": "https://ubuntu.com/security/CVE-2026-98833",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  mtd: core: call _get_device() with the master MTD  __get_mtd_device() calls the master's _get_device() callback with mtd, which may be a partition. __put_mtd_device() passes the master.  This breaks gluebi partitions because gluebi_get_device() uses container_of() and therefore requires the master MTD. Pass the master to _get_device(), matching _put_device().",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-89860",
                        "url": "https://ubuntu.com/security/CVE-2026-89860",
                        "cve_description": "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 second INIT_WORK() reinitializes a work item that is already queued, which can corrupt the workqueue list and lead to crashes or a looping worker.  Initialize priv->abort_work once at command submission, next to the existing per-command spin_lock_init(&priv->cmd_lock), and leave only schedule_work() in the abort paths. schedule_work() already does nothing when the work item is still pending, so a repeated abort no longer disturbs an in-flight work item. The command is not returned to the transport until the final kref_put()/release callback runs after abort_work has completed, so the work item is idle before priv is reused and the single submission-time INIT_WORK() is safe.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-09-16 11:16:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-53353",
                        "url": "https://ubuntu.com/security/CVE-2026-53353",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  hsr: Remove WARN_ONCE() in hsr_addr_is_self().  syzbot reported the warning [0] in hsr_addr_is_self(), whose assumption is simply wrong.  hsr->self_node is cleared in hsr_del_self_node(), which is called from hsr_dellink().  Since dev->rtnl_link_ops->dellink() is called before unregister_netdevice_many(), there is a window when user can find the device but without hsr->self_node.  Let's remove WARN_ONCE() in hsr_addr_is_self().  [0]: HSR: No self node WARNING: net/hsr/hsr_framereg.c:39 at hsr_addr_is_self+0x211/0x3f0 net/hsr/hsr_framereg.c:39, CPU#0: syz.4.16848/17220 Modules linked in: CPU: 0 UID: 0 PID: 17220 Comm: syz.4.16848 Tainted: G             L     syzkaller #0 PREEMPT_{RT,(full)} Tainted: [L]=SOFTLOCKUP Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/18/2026 RIP: 0010:hsr_addr_is_self+0x211/0x3f0 net/hsr/hsr_framereg.c:39 Code: 33 2f 41 0f b7 dd 89 ee 09 de 31 ff e8 c8 b4 c6 f6 09 dd 74 54 e8 0f b0 c6 f6 31 ed eb 53 e8 06 b0 c6 f6 48 8d 3d 2f 50 9c 04 <67> 48 0f b9 3a 31 ed eb 42 e8 c1 13 1f 00 89 c5 31 ff 89 c6 e8 96 RSP: 0018:ffffc900041c70e0 EFLAGS: 00010283 RAX: ffffffff8afdc6ca RBX: ffffffff8afdc4e6 RCX: 0000000000080000 RDX: ffffc90010493000 RSI: 0000000000000948 RDI: ffffffff8f9a1700 RBP: 0000000000000001 R08: 0000000000000000 R09: 0000000000000000 R10: ffffc900041c71e8 R11: fffff52000838e3f R12: dffffc0000000000 R13: ffff888041f9e3c0 R14: ffff888086ee3802 R15: 0000000000000000 FS:  00007f6fe985d6c0(0000) GS:ffff888126176000(0000) knlGS:0000000000000000 CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f80bd437dac CR3: 0000000025096000 CR4: 00000000003526f0 DR0: ffffffffffffffff DR1: 00000000000001f8 DR2: 0000000000000002 DR3: ffffffffefffff15 DR6: 00000000ffff0ff0 DR7: 0000000000000400 Call Trace:  <TASK>  check_local_dest net/hsr/hsr_forward.c:592 [inline]  fill_frame_info net/hsr/hsr_forward.c:728 [inline]  hsr_forward_skb+0xa11/0x2a80 net/hsr/hsr_forward.c:739  hsr_dev_xmit+0x253/0x370 net/hsr/hsr_device.c:236  __netdev_start_xmit include/linux/netdevice.h:5368 [inline]  netdev_start_xmit include/linux/netdevice.h:5377 [inline]  xmit_one net/core/dev.c:3888 [inline]  dev_hard_start_xmit+0x2df/0x860 net/core/dev.c:3904  __dev_queue_xmit+0x1428/0x3900 net/core/dev.c:4870  neigh_output include/net/neighbour.h:556 [inline]  ip_finish_output2+0xcec/0x10b0 net/ipv4/ip_output.c:237  ip_send_skb net/ipv4/ip_output.c:1510 [inline]  ip_push_pending_frames+0x8b/0x110 net/ipv4/ip_output.c:1530  raw_sendmsg+0x1547/0x1a50 net/ipv4/raw.c:659  sock_sendmsg_nosec net/socket.c:787 [inline]  __sock_sendmsg net/socket.c:802 [inline]  ____sys_sendmsg+0x7da/0x9c0 net/socket.c:2698  ___sys_sendmsg+0x2a5/0x360 net/socket.c:2752  __sys_sendmsg net/socket.c:2784 [inline]  __do_sys_sendmsg net/socket.c:2789 [inline]  __se_sys_sendmsg net/socket.c:2787 [inline]  __x64_sys_sendmsg+0x1c3/0x2a0 net/socket.c:2787  do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]  do_syscall_64+0x15f/0xf80 arch/x86/entry/syscall_64.c:94  entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f6feb62ce59 Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 e8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f6fe985d028 EFLAGS: 00000246 ORIG_RAX: 000000000000002e RAX: ffffffffffffffda RBX: 00007f6feb8a6090 RCX: 00007f6feb62ce59 RDX: 0000000000000000 RSI: 0000200000000000 RDI: 0000000000000004 RBP: 00007f6feb6c2d6f R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007f6feb8a6128 R14: 00007f6feb8a6090 R15: 00007ffcf01cc488  </TASK>",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-07-01 14:16:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98836",
                        "url": "https://ubuntu.com/security/CVE-2026-98836",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ALSA: line6: reject oversized playback packets  Each playback URB is handed a slice of out.buffer that is exactly LINE6_ISO_PACKETS * max_packet_size_out bytes, sized from the OUT endpoint, but the number of bytes written into that slice is never compared against it.  submit_audio_out_urb() takes the frame count from prev_fsize, which audio_in_callback() derived from the *IN* endpoint's received packet length, and rescales it with the playback frame size; when prev_fsize is still zero it synthesizes a length from the sample rate instead.  On a device declaring a large IN wMaxPacketSize and a small OUT wMaxPacketSize, the resulting memcpy(), or the memset() when the playback stream is idle, runs past its slice and, as the reproducer below shows, beyond the allocation.  usb_submit_urb() is not a backstop.  max_packet_size_out comes from usb_maxpacket(), which returns only the low 11 bits of wMaxPacketSize, while USB core validates a high-speed isochronous length against that base scaled by usb_endpoint_maxp_mult().  A length of up to three times the allocated slice is therefore accepted, and even a rejected URB is only rejected after the write.  Reject a packet that does not fit the slice the driver allocated for it. Clamping it instead would silently shorten the capture-derived rate feedback and desynchronize the two streams.    BUG: KASAN: slab-out-of-bounds in submit_audio_out_urb (sound/usb/line6/playback.c:229)   Write of size 1024 at addr ffff888100bbd400 by task kworker/1:2/5002   Workqueue: events line6_startup_work   Call Trace:    __asan_memcpy (mm/kasan/shadow.c:106)    submit_audio_out_urb (sound/usb/line6/playback.c:229)    line6_submit_audio_out_all_urbs (sound/usb/line6/playback.c:291)    line6_stream_start (sound/usb/line6/pcm.c:194)    line6_pcm_acquire (sound/usb/line6/pcm.c:337)    line6_startup_work (sound/usb/line6/driver.c:728)    process_one_work (kernel/workqueue.c:3396)    worker_thread (kernel/workqueue.c:3479 kernel/workqueue.c:3560)    kthread (kernel/kthread.c:436)    ret_from_fork (arch/x86/kernel/process.c:158)    ret_from_fork_asm (arch/x86/entry/entry_64.S:245)    The buggy address belongs to the object at ffff888100bbd400    which belongs to the cache kmalloc-256 of size 256   The buggy address is located 0 bytes inside of    allocated 256-byte region [ffff888100bbd400, ffff888100bbd500)",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98838",
                        "url": "https://ubuntu.com/security/CVE-2026-98838",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  vt: skip screen update for DEC alignment test on backgroup consoles  [BUG] Recently, we encountered a KASAN warning as follows:  BUG: KASAN: slab-out-of-bounds in fb_pad_aligned_buffer+0x11f/0x140 Read of size 1 at addr ff1100015fd9f6a4 by task tty_fbcon_oob/1239 CPU: 7 UID: 0 PID: 1239 Comm: tty_fbcon_oob Not tainted 7.3.0-rc1 #100 PREEMPT(full) Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.17.0-4.fc41 04/01/2014 Call Trace:  <TASK>  ...  kasan_report+0xf0/0x120  fb_pad_aligned_buffer+0x11f/0x140  ccw_putcs+0x86c/0xa80  fbcon_putcs+0x338/0x410  do_update_region+0x21d/0x450  do_con_write+0x1e0e/0x4880  con_write+0x13/0x80  n_tty_write+0x374/0x1010  file_tty_write.isra.0+0x404/0x7a0  ...  reproduce: 1) open /dev/tty0, set a KDFONTOP ioctl with op.op = KD_FONT_OP_SET, op.width = 8 and op.height = 16 (visible VC1) 2) open /dev/tty1, set a KDFONTOP ioctl with op.op = KD_FONT_OP_SET, op.width = 28 and op.height = 24 (invisible VC2) 3) echo 3 > /sys/devices/virtual/graphics/fbcon/rotate_all 4) write EShash8(esc hash8) to tty1  [CAUSE] All VCs render to the framebuffer. setfont only modifies the target VC's font without resizing the framebuffer backing buffer (par->rotated.buf); the buffer is only resized for the visible VC (fbcon_do_set_font -> ... -> vc_do_resize -> update_screen). This relies on the con_should_update() check performed before every update_region().  However, the ESC # 8 path (do_con_trol -> do_update_region) omits the con_should_update() check. After changing the font size of an invisible VC, do_update_region() fills using the new font size against a buffer that was never resized, causing an out-of-bounds access.  [FIX] Only push the update when the console is visible and not blanked, add the con_should_update() check in the do_con_trol() like every other call site of do_update_region() (update_region(), invert_screen(), ...).",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98568",
                        "url": "https://ubuntu.com/security/CVE-2026-98568",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  vxlan: use one headroom snapshot for neighbour replies  vxlan_na_create() samples LL_RESERVED_SPACE() to size the reply skb and then samples it again to reserve headroom. A concurrent vxlan_changelink() can update needed_headroom between the two reads, creating a TOCTOU race. The second value can exceed the allocation and make the Ethernet header write out of bounds.  The race is reproducible on the unpatched kernel. It occurred when vxlan_na_create() generated a neighbour reply while vxlan_changelink() changed the link headroom. KASAN caught a four-byte write two bytes beyond a 704-byte skbuff_small_head allocation.  Snapshot the headroom once and use that value for both allocation and reservation.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2024-49901",
                        "url": "https://ubuntu.com/security/CVE-2024-49901",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  drm/msm/adreno: Assign msm_gpu->pdev earlier to avoid nullptrs  There are some cases, such as the one uncovered by Commit 46d4efcccc68 (\"drm/msm/a6xx: Avoid a nullptr dereference when speedbin setting fails\") where  msm_gpu_cleanup() : platform_set_drvdata(gpu->pdev, NULL);  is called on gpu->pdev == NULL, as the GPU device has not been fully initialized yet.  Turns out that there's more than just the aforementioned path that causes this to happen (e.g. the case when there's speedbin data in the catalog, but opp-supported-hw is missing in DT).  Assigning msm_gpu->pdev earlier seems like the least painful solution to this, therefore do so.  Patchwork: https://patchwork.freedesktop.org/patch/602742/",
                        "cve_priority": "low",
                        "cve_public_date": "2024-10-21 18:15:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98846",
                        "url": "https://ubuntu.com/security/CVE-2026-98846",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  sctp: check RCV_SHUTDOWN after the sendmsg connect wait  sctp_wait_for_connect() drops the socket lock while it sleeps. An out-of-the-blue ABORT can then be processed from the socket backlog and unlink the association. If a concurrent shutdown(fd, SHUT_RD) sets RCV_SHUTDOWN, the waiter breaks with err == 0 before checking asoc->base.dead. Its final sctp_association_put() can then free the association, leaving sctp_sendmsg_to_asoc() to continue with a dangling pointer.  Check RCV_SHUTDOWN along with the wait error in sctp_sendmsg_to_asoc() before using the association again. The check only accesses the socket, so it needs no additional association reference. Return the existing -ESRCH so that sctp_sendmsg() skips freeing a new association that may already have been destroyed.  Keep sctp_wait_for_connect() unchanged to preserve its behavior for the connect() caller.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98847",
                        "url": "https://ubuntu.com/security/CVE-2026-98847",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  rtc: spear: initialize IRQ state before requesting alarm IRQ  devm_request_irq() enables the interrupt before it returns, so the handler may run while probe is still initializing the device. Initialize the MMIO address and spinlock before requesting the alarm IRQ.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98850",
                        "url": "https://ubuntu.com/security/CVE-2026-98850",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net/packet: prevent TX_RING byte count overflow  tpacket_snd() drains every SEND_REQUEST frame in a TX ring and adds each valid packet length to the signed int len_sum. Userspace can recycle completed frames concurrently, so a single blocking send call is not bounded by the ring size.  After enough successful transmissions len_sum wraps into the negative range. In particular, 65536 65535-byte frames followed by a 65007-byte frame produce 0xfffffdef, or -EIOCBQUEUED. sock_sendmsg_nosec() treats that as an impossible return and triggers a BUG. On systems configured to panic on oops, a CAP_NET_RAW holder can panic the host kernel.  Stop before the next frame would make the byte count exceed INT_MAX. The positive short count leaves that frame pending for a later send call.  A two-thread TPACKET_V2 reproducer triggered the BUG on an arm64 build of Linux 7.3-rc4. With this change, the same reproducer returned the expected positive short count without an oops.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98851",
                        "url": "https://ubuntu.com/security/CVE-2026-98851",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  netfilter: nft_flow_offload: drop flowtable reference on init error path  nft_flow_offload_init() bumps the flowtable use count with nft_use_inc() before calling nf_ct_netns_get().  When the latter fails, the error is returned as-is and the reference is leaked.  The upper layers do not balance it either: nf_tables_newexpr() clears expr->ops when the expression init callback fails, so the nft_expr_more() iteration in nft_rule_expr_deactivate() and nf_tables_rule_destroy() stops right before the failed expression and its ->destroy callback, which would drop the reference, never runs.  Each failed rule addition therefore leaks one flowtable reference and the flowtable can no longer be removed: NFT_MSG_DELFLOWTABLE keeps reporting -EBUSY even though no rule references it.  Save the nf_ct_netns_get() return value and undo the nft_use_inc() when it fails, restoring the inc/dec pairing within nft_flow_offload_init() itself.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98854",
                        "url": "https://ubuntu.com/security/CVE-2026-98854",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  of/overlay: only treat a positive changeset id as registered  of_overlay_fdt_apply() stores the idr_alloc() return value in ovcs->id before checking it. On failure the stored id is negative, free_overlay_changeset()'s \"if (ovcs->id)\" check passes, idr_remove() is called with a negative id and list_del() runs on ovcs->ovcs_list, which is not initialized until after the id allocation. An allocation failure at that point dereferences NULL.  Make free_overlay_changeset() treat only a strict-positive id as registered. The rest of the function already copes with a partially-initialized ovcs, so the error path stays a plain goto err_free_ovcs.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98855",
                        "url": "https://ubuntu.com/security/CVE-2026-98855",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  of/overlay: put property on deadprops only after changeset add succeeds  add_changeset_property() links a new property of a not-yet-live target node into the node's deadprops list before handing it to of_changeset_add_property(). If that fails, the error path frees the property but leaves the freed pointer linked in deadprops, and of_node_release() frees it a second time when the aborted overlay's node is released.  Record the changeset entry first and link the property into deadprops only on success. of_changeset_add_property() never looks at the node's property lists, so the order of the two steps is otherwise immaterial, and the error path frees a property that nothing references.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98862",
                        "url": "https://ubuntu.com/security/CVE-2026-98862",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  audit: fix exe mark UAF in kill_rules()  kill_rules() removes mixed AUDIT_DIR and AUDIT_EXE rules when an audit tree is pruned. It drops entry->rule.exe before removing the rule from the RCU-visible filter lists.  After a rule has been installed with AUDIT_ADD_RULE, which requires CAP_AUDIT_CONTROL, removing the watched directory can race with another task that is still evaluating the rule. In that case, fsnotify can free the executable mark before the reader reaches audit_mark_compare(), causing a use-after-free.  KASAN reports:      BUG: KASAN: slab-use-after-free in audit_mark_compare+0x8d/0xa0  Unlink the published rules from the RCU-visible lists and retain them on tree->rules for cleanup. If any rule has an executable mark, wait for a single RCU grace period before removing the marks and scheduling the entries for freeing. Otherwise, call_rcu() already provides the required deferred freeing without a synchronous wait.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98450",
                        "url": "https://ubuntu.com/security/CVE-2026-98450",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  smb: client: close completed creates on compound wait errors  compound_send_recv() waits for responses in order. If a later wait is interrupted, or if a later MID fails during response synchronization, an earlier CREATE may already have opened a remote handle. The earlier mid is then released without invoking handle_cancelled_mid(), leaving the remote handle open because no FID was copied to the caller.  Mark completed earlier mids as cancelled when a compound wait or MID synchronization aborts. Keep their response buffers attached while the MIDs are synchronized, and transfer them only after synchronization of the processed responses, so the release path can inspect successful CREATE responses and queue SMB2_close() after a later failure. Account for a remote open only after the close work is allocated and before it is queued, since the caller has not yet updated num_remote_opens. Mark the create+close compound used by smb2_unlink() so it is not closed again. Non-CREATE responses and compounds that already include a close keep their existing behavior.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:16:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98502",
                        "url": "https://ubuntu.com/security/CVE-2026-98502",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  HID: alps: unregister DualPoint Stick input device on remove  alps_input_configured() allocates a second input device (\"DualPoint Stick\") with input_allocate_device() and registers it, but the alps_driver struct has no .remove handler and input2 is not tracked in hdev->inputs.  The default remove path (hid_hw_stop -> hidinput_disconnect) only iterates hdev->inputs, so input2 is never unregistered and leaks on every device removal.  Add a .remove handler that stops the device first (preventing URB callbacks from touching input2 during teardown) and then unregisters input2.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98456",
                        "url": "https://ubuntu.com/security/CVE-2026-98456",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  Bluetooth: mgmt: fix race in read_unconf_index_list()  read_unconf_index_list() counts unconfigured controllers before allocating its response, then checks the device flags again while filling it.  hci_dev_list_lock stabilizes list membership, but it does not serialize the per-device flags. During asynchronous controller setup, the worker can set HCI_UNCONFIGURED and clear HCI_SETUP between the two passes. A controller omitted from the allocation count can then become eligible for the fill pass, causing an out-of-bounds write to rp->index[].  Allocate space for every device on hci_dev_list. Since list membership cannot change while hci_dev_list_lock is held, the response remains large enough regardless of flag transitions. The reported count and response length still include only eligible unconfigured controllers.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-18 16:16:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98451",
                        "url": "https://ubuntu.com/security/CVE-2026-98451",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  smb: client: use finish_no_open() for non-regular inodes  An O_CREAT open can find an existing symlink or another non-regular inode. cifs_atomic_open() calls finish_open() on it and attaches a cifsFileInfo. Symlink inodes have no CIFS release operation, so the dentry reference held by cifsFileInfo is leaked. FMODE_OPENED also prevents the VFS from following the symlink.  Track whether cifs_do_create() returned an open server handle. For non-regular inodes, close the handle if present, remove the pending open, and call finish_no_open() so the VFS can continue the lookup. Do not set FMODE_CREATED unless a regular file was opened. For O_NOFOLLOW with __O_REGULAR, return -ELOOP before the VFS's -EFTYPE check.  Defer closing a legacy POSIX handle on a non-regular inode until after inode lookup. This avoids closing it again if lookup fails.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-18 16:16:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98484",
                        "url": "https://ubuntu.com/security/CVE-2026-98484",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  netfilter: nf_tables: skip expired catchall elements on insert and delete  nft_setelem_catchall_insert() looks up duplicates with nft_set_elem_active() only, while nft_set_catchall_lookup() and the dump path additionally skip expired elements.  Once a catchall element with a timeout expires, this predicate drift makes it invisible to userspace dumps, yet it still blocks re-insertion: with NLM_F_EXCL the request fails with -EEXIST, and without it the request reports success but silently inserts nothing. The stale entry only goes away when the (user-tunable) gc interval elapses, so the catchall rule may silently stop matching for an arbitrarily long time after its first expiration.  The delete path shows the same drift: nft_setelem_catchall_deactivate() picks the first active-next entry in the catchall list, so with an expired entry still pending GC it retires the stale entry instead of the fresh one, and it deactivates an element that userspace no longer sees instead of failing with -ENOENT.  Align both walks with the lookup and dump predicates: only an element that is active and not expired counts as a duplicate or delete candidate, using the per-netns timestamp taken at transaction start, in line with the set backend .insert/.deactivate and catchall GC sync paths.",
                        "cve_priority": "negligible",
                        "cve_public_date": "2026-10-18 16:16:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98486",
                        "url": "https://ubuntu.com/security/CVE-2026-98486",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net: ena: fix MMIO read buffer leak on probe failure  ena_device_init() initializes the MMIO read mechanism with ena_com_mmio_reg_read_request_init(), which allocates a coherent DMA buffer for MMIO read responses.  The normal removal path releases this buffer through ena_com_mmio_reg_read_request_destroy(). However, if ena_probe() fails after ena_device_init() succeeds, the error path destroys the admin resources and eventually frees ena_dev without destroying the MMIO read request, leaving the coherent DMA buffer allocated.  Call ena_com_mmio_reg_read_request_destroy() in the probe error path before releasing the remaining device resources.  This issue was found by manual code inspection.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:16:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98493",
                        "url": "https://ubuntu.com/security/CVE-2026-98493",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net: ipconfig: bound DHCP option construction  ic_dhcp_init_options() appends the hostname (option 12), vendor-class (option 60) and client-ID (option 61) options into the fixed 312-byte bootp_pkt.exten[] buffer.  Only the client-ID branch checked the remaining space; the hostname and vendor-class writes were unbounded.  A 64-byte hostname together with the maximum 252-byte dhcpclass= identifier needs 18 + (2 + 64) + (2 + 252) = 338 of the 312 available bytes even before the terminating END marker, so the vendor-class memcpy runs past the end of exten[].  With CONFIG_FORTIFY_SOURCE this is reported as a field-spanning write and, when the kernel is booted with panic_on_warn=1, aborts boot with a panic.  Route the optional options through a common helper that makes sure the option, its 2-byte header and the END marker all fit and drops an option that would not.  Configurations with short options keep sending exactly the same bytes as before.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98454",
                        "url": "https://ubuntu.com/security/CVE-2026-98454",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  smb: client: fix create context out-of-bounds reads  smb2_parse_contexts() validates the complete create-context area but does not limit each record to its Next field before dispatching it.  A malformed chain can therefore expose bytes beyond the current context to a handler.  The QFid handler also used a full response-structure cast although it only reads DiskFileId.  The SMB2/SMB3 lease parsers made the same layout assumption: they read LeaseState and LeaseFlags at canonical offsets rather than at DataOffset.  A valid non-canonical DataOffset could therefore yield unrelated in-bounds data, while a short DataLength was still accepted.  Limit each context to its Next value, reject offsets before the context header, and reject malformed chains.  Bound the name range by the current context and do not dispatch a known handler when DataLength is zero.  Read the QFid DiskFileId only when the context data covers that field.  Parse the lease context from DataOffset and require DataLength to match the v1 or v2 lease_context size used by ksmbd.  A size mismatch skips lease parsing without failing the open.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-18 16:16:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98490",
                        "url": "https://ubuntu.com/security/CVE-2026-98490",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net: openvswitch: conntrack: fix helper UAF due to extensions realloc  While calling the helpers, a raw pointer to the extensions area is wired into expectations list:    -> nf_ct_helper()    -> helper->help()     -> nf_ct_expect_related_report()      -> nf_ct_expect_insert()       -> hlist_add_head_rcu(&exp->lnode, &master_help->expectations)  In case the connection is not confirmed yet, more extensions can be added afterwards with *_ext_add() calls reallocating the extension space and leaving the now invalid pointer in the expectations list that is later accessed while removing the expectation.  Make sure that helpers are called at the end after all the other extensions are already added.  Note that the helper rejection now leaves the mark and labels set, but that's not different from how the NAT was handled before or how the mark and the labels were handled on confirmation failure.  And there are no atomicity guarantees provided by the API anyway.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-18 16:16:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98507",
                        "url": "https://ubuntu.com/security/CVE-2026-98507",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  mm/rmap: fix missing barrier between anon_vma init and vma->anon_vma publish  On arm64 server, we find that a task trying to grab the anon_vma lock triggers hungtask.  INFO: task main:2354726 blocked for more than 120 seconds.       Tainted: G            E     5.10.0-0021.aarch64 #1 \"echo 0 > /proc/sys/kernel/hung_task_timeout_secs\" disables this message. task:main            state:D stack:    0 pid:2354726 ppid:2350673 flags:0x00000a01 Call trace:  __switch_to+0x7c/0xbc  __schedule+0x3b4/0x8a0  schedule+0x50/0xe0  rwsem_down_write_slowpath+0x3cc/0x6cc  down_write+0x60/0x260  __anon_vma_prepare+0x6c/0x210  do_anonymous_page+0x258/0x660  handle_pte_fault+0x188/0x214  __handle_mm_fault+0x1b0/0x380  handle_mm_fault+0xf4/0x284  do_page_fault+0x19c/0x494  do_translation_fault+0xcc/0xf8  do_mem_abort+0x48/0xac  el0_da+0x44/0x80  el0_sync_handler+0x88/0xb4  el0_sync+0x160/0x180  After analyzing the vmcore, we found the anon_vma->root->rwsem.count is -1.  There is another anon_vma whose anon_vma->root->rwsem.count is 1, the anon_vma->root->rwsem.owner shows the lock is held, but the stack of the task shows the task doesn't hold the anon_vma lock.  After adding more debugging info, we found __anon_vma_prepare() reuses anon_vma and triggers the UAF of anon_vma->root due to missing memory barrier, leading to locking and unlocking two different anon_vma->root, thus leading to an anon_vma will never be unlocked, and another anon_vma couldn't be locked anymore.  This race requires two adjacent VMAs that are not merged but are anon_vma-compatible (e.g., they differ in VMA_ACCESS_FLAGS that can be changed by mprotect()).  Two threads fault on each VMA concurrently, both calling __anon_vma_prepare() with only mmap_lock held for reading.      THREAD A                             THREAD B __anon_vma_prepare                __anon_vma_prepare  find_mergeable_anon_vma() -> NULL  anon_vma = anon_vma_alloc();    anon_vma->root = anon_vma;  // the two stores may be reordered  vma->anon_vma = anon_vma;                                    // finds A's anon_vma                                    anon_vma = find_mergeable_anon_vma(vma);                                    anon_vma_lock_write(anon_vma);                                      // may still see the old root                                      down_write(&anon_vma->root->rwsem);                                    anon_vma_unlock_write(anon_vma);                                      // see the new root, never unlock old                                      up_write(&anon_vma->root->rwsem);  thread A triggers page fault and calls __anon_vma_prepare() to prepare anon_vma for the faulting vma.  __anon_vma_prepare() allocates and initializes a new anon_vma, and then publishes it to the vma with a plain store.  anon_vma_prepare() only requires the mmap_lock to be held for reading, so two threads can fault on adjacent VMAs at the same time. While thread A publishes a new anon_vma, thread B could find the anon_vma via find_mergeable_anon_vma() and then locks anon_vma->root->rwsem.  The store to anon_vma->root in anon_vma_alloc() and the store to vma->anon_vma can be reordered.  The anon_vma_lock_write() and spin_lock() only provide acquire semantics, which do not prevent prior stores from being reordered after them.  The release semantics of the corresponding spin_unlock() and anon_vma_unlock_write() come too late, the store to vma->anon_vma is already published before they take effect.  As a result, thread B can observe the following order:      vma->anon_vma = anon_vma;     anon_vma->root = anon_vma;  The anon_vma slab is SLAB_TYPESAFE_BY_RCU, so a newly allocated anon_vma may reuse memory from a previously freed one.  The constructor (anon_vma_ctor) does not reset anon_vma->root, and __put_anon_vma() doesn't clear it either, so the old root value persists until anon_vma_alloc() overwrites it.  If that store isn't v ---truncated---",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98519",
                        "url": "https://ubuntu.com/security/CVE-2026-98519",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  drm/amdgpu: Fix runtime PM leak in amdgpu_debugfs_test_ib_show()  amdgpu_debugfs_test_ib_show() resumes the device with pm_runtime_get_sync() before taking the reset domain semaphore with down_write_killable().  If the write lock acquisition is interrupted, the function returns without calling pm_runtime_put_autosuspend(), leaking the runtime PM reference acquired for the device and keeping the GPU awake.  Drop the runtime PM reference on the interrupted down_write_killable() error path before returning.  (cherry picked from commit ec30a576c2d4c0364549e6c04218f50704ef56c8)",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98549",
                        "url": "https://ubuntu.com/security/CVE-2026-98549",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  tcp: prevent collapsing skbs across boundary in rtx queue  tcp_write_collapse_fence() sets TCP_SKB_CB(skb)->eor = 1 on tcp_write_queue_tail(sk) to prevent skbs queued after a switch to device encryption from being collapsed into earlier skbs.  The fence is a no-op if all earlier data has already been transmitted when the switch happens: sk->sk_write_queue is empty. The not yet acknowledged earlier skbs wait in sk->tcp_rtx_queue with eor 0.  On a subsequent retransmit or SACK shift, tcp_retrans_try_collapse() or tcp_shift_skb_data() can then merge an skb queued after the switch into one queued before it.  Both users of the fence are affected:  - psp: devices only encrypt skbs with skb->decrypted set. The merged skb   keeps decrypted = 0 from the earlier skb, so merged data sent after   psp_sock_assoc_set_tx() is retransmitted in cleartext.  - tls device offload: the merged skb straddles the start marker set in   tls_set_device_offload(). The software fallback (fill_sg_in() returns   -EINVAL) and the mlx5, nfp and funeth drivers cannot handle such an   skb and drop it. Every retransmit rebuilds the same skb, so the   connection stalls.  Fix this in two places, for defense in depth:  1. Fall back to tcp_rtx_queue_tail(sk) in tcp_write_collapse_fence()    when tcp_write_queue_tail(sk) is NULL.  2. Check !skb_cmp_decrypted(to, from) in tcp_skb_can_collapse(), as    tcp_skb_can_collapse_rx() does on receive. skb_shift(), which both    collapse paths call, already has a DEBUG_NET_WARN_ON_ONCE() for this    condition.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98544",
                        "url": "https://ubuntu.com/security/CVE-2026-98544",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  bna: prevent IOC timer rearm during teardown  bna: prevent IOC timer rearm during teardown  bnad_pci_remove() and the probe disable_ioceth path call timer_delete_sync() for ioc_timer, sem_timer and hb_timer, but not for iocpf_timer.  bnad_iocpf_timeout() then takes bnad->bna_lock after free_netdev() has freed the struct bnad.  Deleting iocpf_timer last does not fix this.  sem_timer and iocpf_timer rearm each other: bnad_iocpf_sem_timeout() can arm iocpf_timer, and bnad_iocpf_timeout() arms sem_timer from bfa_ioc_hw_sem_get() when the semaphore is busy. timer_delete_sync() only waits out its own callback. bnad_ioceth_disable() can time out and leave that callback live.  Shut all four IOC timers down with timer_shutdown_sync() on both paths, so a later mod_timer() is ignored.  This issue was identified during our ongoing static-analysis research while reviewing kernel code.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98172",
                        "url": "https://ubuntu.com/security/CVE-2026-98172",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  smb: client: fix smbd_connection leak on cifs_get_tcp_session() error  When an RDMA connection is successfully established via smbd_get_connection() but cifs_get_tcp_session() later fails (e.g. kthread_create() returns an error), the error path frees tcp_ses without first destroying the smbd_connection.  Fix this by calling smbd_destroy() in the out_err cleanup path before kfree(tcp_ses).  smbd_destroy() safely handles the case where smbd_conn is NULL, so it can be called unconditionally.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-06 09:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98192",
                        "url": "https://ubuntu.com/security/CVE-2026-98192",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: wcn36xx: Fix potential use-after-free in TX ack timer teardown  wcn36xx_dxe_deinit() tears down the TX ack timer with timer_delete(), which only dequeues the timer and does not wait for a callback that is already executing; the preceding free_irq() calls synchronize the interrupt handlers only. The callback, wcn36xx_dxe_tx_timer(), can therefore be running past the teardown and use the wcn freed along with the ieee80211_hw in wcn36xx_remove(): it takes wcn->dxe_lock, reads wcn->tx_ack_skb and passes wcn->hw to ieee80211_tx_status_irqsafe().  Fix this by using timer_shutdown_sync(), which waits for a running callback and also prevents the timer from being rearmed again. The timer is set up again by wcn36xx_dxe_init() on the next start, so the start/stop cycle is unaffected.  This issue was found by an in-house static analysis tool.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-06 09:18:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98198",
                        "url": "https://ubuntu.com/security/CVE-2026-98198",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  hwmon: (pwm-fan) Stop RPM timer before freeing tach data  sample_timer() rearms the RPM timer and accesses the devm-managed ctx->tachs and ctx->pulses_per_revolution arrays. The cleanup action which stops the timer is registered before those arrays are allocated.  Since devres releases entries in reverse order, driver detach can free the arrays before pwm_fan_cleanup() shuts down the timer. A timer expiry in that window accesses the freed tach data.  With a KASAN kernel, a test-only kprobe delayed entry to pwm_fan_cleanup() while normal sysfs unbind ran. Each of three runs reported three four-byte reads and two four-byte writes in sample_timer() after its backing devm allocations had been freed. The helper did not invoke the timer callback, cleanup actions or free functions.  With the fix, three matching unbind runs completed without KASAN, BUG, WARNING, Oops or panic. Instrumentation confirmed that timer retirement completed before the first timer backing allocation was released.  Split timer retirement from the power cleanup and register its devres action after the timer backing data and IRQ actions are installed. This preserves the early power rollback action while ensuring the timer is retired before its backing data is released. Use timer_shutdown_sync() because the callback can rearm itself.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-06 09:18:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98409",
                        "url": "https://ubuntu.com/security/CVE-2026-98409",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  watchdog: rtd119x: Avoid division by zero  clk_get_rate() could return 0.  Avoid a division by zero panic.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-14 14:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98245",
                        "url": "https://ubuntu.com/security/CVE-2026-98245",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  btrfs: take commit root semaphore when iterating in mark_block_group_to_copy()  mark_block_group_to_copy() iterates over the commit root with skip_locking=true. A concurrent transaction commit can swap and free the commit root during iteration, causing use-after-free when accessing extent buffers.  Fix it by using path->need_commit_sem to protect the commit root search.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-06 09:18:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98264",
                        "url": "https://ubuntu.com/security/CVE-2026-98264",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ALSA: virtio: reset device before deleting virtqueues  virtsnd_remove() and virtsnd_freeze() delete the virtqueues before resetting the device. del_vqs() frees the vring backing, but does not provide a generic device quiesce operation. In particular, modern virtio-pci keeps enabled queues active until the device is reset.  Reset the device before deleting the virtqueues so it can no longer access the vring memory when that memory is released. This also covers probe failures after DRIVER_OK, which unwind through virtsnd_remove().",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-06 09:18:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-97558",
                        "url": "https://ubuntu.com/security/CVE-2026-97558",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  smb: client: fix cifsFileInfo reference leak in deferred close  When cifs_close() defers a close, it hands the cifsFileInfo reference of the closing struct file to the queued work. Each execution of smb2_deferred_work_close() drops one such reference.  deferred_close_scheduled can be false while the work is pending: the workqueue clears PENDING when the callback starts to run, before the callback clears the flag under deferred_lock. A close in that interval requeues the running work, and the callback then clears the flag, leaving the requeued work pending with the flag down. A later cifs_open() can reuse the handle and its cifs_close() reaches the same branch: queue_delayed_work() fails because the work is still pending, but cifs_close() returns without dropping the closing file's reference. The cifsFileInfo count stays pinned and its tlink, dentry and server handle are leaked.  Check the return value and hand off the reference only when work was actually queued. Otherwise, use the shared _cifsFileInfo_put(), like the mod_delayed_work() branch above: the pending execution already owns its reference.  This issue was found by an in-house static analysis tool.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-09-25 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-97616",
                        "url": "https://ubuntu.com/security/CVE-2026-97616",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net/sched: act_api: release all action references on NEWACTION failure  When a batched RTM_NEWACTION request replaces an existing action, tcf_idr_check_alloc() takes a temporary reference on it. If a later action fails to initialize, tcf_action_destroy() uses strict release semantics to clean up the actions initialized so far. For an action bound to a filter, the strict check returns -EPERM without dropping the temporary reference.  This error also makes tcf_action_destroy() return before releasing subsequent entries. Any new action initialized between the bound action and the failing entry is leaked together with its reserved IDR slot, preventing reuse of its index.  Use tcf_idr_release() to drop each reference held by the batch without rejecting bound actions. This allows cleanup to continue through all initialized entries and preserves the module reference release when an action is destroyed. Explicit action deletion and flushing retain their separate bind-count checks.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-09-25 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-97939",
                        "url": "https://ubuntu.com/security/CVE-2026-97939",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ipmr: account multicast table and route memory  A netadmin in a user+net namespace can create many IPv4 and IPv6 multicast routing tables with MRT_TABLE and MRT6_TABLE. Each unseen id allocates an mr_table via the shared mr_table_alloc(), links it into the per-net list, and leaves it until netns teardown. Those objects were not charged to memcg, so the host unreclaimable slab grows with the table count.  Account mr_table allocations with GFP_KERNEL_ACCOUNT and mark the IPv4/IPv6 MFC caches SLAB_ACCOUNT. This matches the established handling of IP addresses, routes and alternate interface names.  Unresolved MFC entries are still allocated from softIRQ with GFP_ATOMIC and are not charged. They expire after 10 seconds and are bounded by the socket receive queue; see commit 0079ad8e8dc3 (\"ipmr: remove hard code cache_resolve_queue_len limit\").",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-09-25 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-89837",
                        "url": "https://ubuntu.com/security/CVE-2026-89837",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  f2fs: fix dentry folio leak in find_in_level  find_in_level() gets a dentry folio with f2fs_find_data_folio() before calling find_in_block().  If find_in_block() returns an error, the function stores the error in res_folio and breaks out of the loop without dropping the dentry folio.  This leaks the folio reference on the find_in_block() error path.  Drop the dentry folio before returning the error to the caller.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-09-16 11:16:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-89838",
                        "url": "https://ubuntu.com/security/CVE-2026-89838",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  f2fs: limit recovery filename logging to stored length  F2FS stores recovery filenames as a length plus a fixed-size i_name buffer.  The buffer is not NUL-terminated, but recover_inode() and recover_dentry() print it with %s.  For a 255-byte filename, recovery logging can read past i_name into the following raw inode fields.  Print the name with a precision bounded by i_namelen and F2FS_NAME_LEN.",
                        "cve_priority": "negligible",
                        "cve_public_date": "2026-09-16 11:16:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-97530",
                        "url": "https://ubuntu.com/security/CVE-2026-97530",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  scsi: qla2xxx: Fix soft lockup polling continuation IOCB signature  qla27xx_copy_multiple_pkt() and qla27xx_copy_fpin_pkt() poll rsp_q->ring_ptr->signature for RESPONSE_PROCESSED (0xDEADDEAD) to decide whether the next continuation IOCB has arrived, spinning on cpu_relax() without advancing the ring or decrementing the entry count while it has not. response_t::signature lives at byte offset 60, but a continuation IOCB (sts_cont_entry_t / struct sts_cont_entry_ext) carries raw FC frame payload at that offset (data[56..59]). A received frame whose payload bytes happen to equal 0xDEADDEAD is therefore misread as \"not yet arrived\", and the loop spins forever in interrupt/DPC context, causing a CPU soft lockup.  The poll is also unnecessary: callers of qla27xx_copy_multiple_pkt() (PT_LS4_UNSOL and the NVMe purls path) already gate on qla_chk_cont_iocb_avail(), which guarantees all entry_count IOCBs are present before copying begins. The sibling helper __qla_copy_purex_to_buffer() already drops the signature poll and relies on the entry_type == STATUS_CONT_TYPE guard instead.  Remove the signature busy-wait from both helpers, keeping the entry_type guard, and gate the FPIN path with qla_chk_cont_iocb_avail() so it defers and re-processes on the next interrupt once all continuation IOCBs have arrived, mirroring the ELS_AUTH_ELS and PT_LS4_UNSOL arms. With this the signature field is never read on a continuation IOCB, eliminating the payload-aliasing lockup.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-09-25 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98386",
                        "url": "https://ubuntu.com/security/CVE-2026-98386",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  scsi: qla2xxx: Use memset_io() to clear QLAFX00 request ring slot  For QLAFX00 the request ring is ioremapped device I/O memory (ha->iobase + req_que_off), not DMA-coherent RAM, which is why the rest of the FX00 path accesses it through memcpy_toio() and the wrt_reg_* helpers. __qla2x00_alloc_iocbs() however zeroed the producer slot with a plain memset(). On architectures such as ARM64 a regular memset() may emit unaligned or block-zeroing instructions (e.g. DC ZVA) that are invalid on Device memory, leading to a synchronous external abort.  Use memset_io() to clear the slot for QLAFX00, matching the I/O accessors used elsewhere on this ring. Other adapters keep the plain memset() on their DMA-coherent rings. The zero-fill is retained for FX00 because its IOCB builders (e.g. qlafx00_fxdisc_iocb()) copy only part of the entry and rely on the unused tail being pre-zeroed.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-14 14:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-89848",
                        "url": "https://ubuntu.com/security/CVE-2026-89848",
                        "cve_description": "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_work, and qla_do_work() -> qla24xx_process_response_queue() dereferences the now-freed rsp->req (LOGINOUT/CT/ELS entries and the status path), a use-after-free.  The cancel_work_sync() added for the qpair teardown lives in the response free path, which runs after the request queue is already freed, so it does not protect rsp->req.  Release the response-queue interrupt and flush qpair->q_work before deleting the request queue, so no late completion can reach the freed request queue. Clearing have_irq makes the subsequent qla25xx_free_rsp_que() skip its free_irq(), and the firmware queue-delete order (request then response) is preserved; the request-delete mailbox completes on the default vector and is unaffected by dropping the qpair response interrupt early.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-09-16 11:16:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-97532",
                        "url": "https://ubuntu.com/security/CVE-2026-97532",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  scsi: qla2xxx: Null out freed pointers in qla2x00_mem_alloc() error path  When qla2x00_mem_alloc() fails, qla2x00_probe_one() jumps to probe_hw_failed and calls qla2x00_mem_free(). Several error labels in qla2x00_mem_alloc() freed adapter members (elsrej.c, purex_dma_pool, flt, sfp_data, loop_id_map, async_pd, sf_init_cb, ex_init_cb, npiv_info) but left the pointers dangling. qla2x00_mem_free() then freed them a second time. Worse, for the dma_pool members it issued dma_pool_free(ha->s_dma_pool, ...) after s_dma_pool had already been destroyed and set to NULL at fail_s_dma_pool, dereferencing a NULL pool.  Clear each freed pointer (and its DMA handle) in the error labels so the subsequent qla2x00_mem_free() skips them.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-09-25 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-89877",
                        "url": "https://ubuntu.com/security/CVE-2026-89877",
                        "cve_description": "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 existing MMIO mapping error path to remove the device from saa7164_devlist and decrement the device count before returning.  Also release BAR0 if it was successfully requested but the BAR2 request fails.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-09-16 11:16:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-93239",
                        "url": "https://ubuntu.com/security/CVE-2026-93239",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  arm64: mm: Fix the lockless page-table walk in show_pte()  show_pte() walks page tables locklessly and can run with interrupts enabled. A concurrent teardown can free a table page while it is being walked. It can also clear a parent entry after show_pte() checked it; the regular pXd_offset() helpers then reread the cleared entry and can derive a bogus lower-level pointer and fault again.  Use the lockless offset helpers with the saved parent entries, as gup_fast() does, and pass the saved PMD to pte_offset_map().  For task page tables, arm64 selects MMU_GATHER_RCU_TABLE_FREE. Disable local interrupts around the walk to hold off RCU-deferred table frees and block the tlb_remove_table_sync_one() IPI until the walk is finished.  Place the IRQ guard after the header print. This does not make the output a consistent snapshot, but prevents the task page-table walk from dereferencing a released table page or deriving a pointer from a different parent value.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-09-24 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-90023",
                        "url": "https://ubuntu.com/security/CVE-2026-90023",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  usb: gadget: f_mass_storage: fix null pointer dereference in fsg_common_set_num_buffers()  Previously fsg_num_buffers_validate() was removed as it was not necessary due to Kconfig setting the limits for n from 2 to 256 with default as 2. However, setting the page content in such a way that kstrtou8() reflects n value as either 0 or 1 bypasses these restrictions leading to a null pointer dereference if n is 0. Fix this by adding a check for n < 2 and returning -EINVAL if n is either 0 or 1 consistent with Kconfig logic.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-09-16 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-93200",
                        "url": "https://ubuntu.com/security/CVE-2026-93200",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  i3c: master: Fix use-after-free of master->this  sysfs attribute callbacks for the master controller device dereference master->this.  However, master->this is freed in i3c_master_detach_free_devs() before the master device itself is released.  As a result, sysfs accesses can dereference a freed master->this pointer, leading to a use-after-free.  Keep master->this alive until i3c_masterdev_release(), which is called after the master device and its sysfs state are being torn down. Do not free master->this as part of the normal device detach path.  On the error path in i3c_master_set_info(), reset master->this and bus.cur_master to NULL before freeing the allocated device.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-09-17 17:18:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-93199",
                        "url": "https://ubuntu.com/security/CVE-2026-93199",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  i3c: master: Do not treat master device as a duplicate target  i3c_master_search_i3c_dev_duplicate() searches the bus for another I3C device with the same PID as the reference device.  The search can match master->this, causing the controller itself to be returned as a duplicate.  Since the controller is not a target device, it cannot be a duplicate of one.  Exclude master->this from matching so that the function only returns real duplicate target devices.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-09-17 17:18:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-89441",
                        "url": "https://ubuntu.com/security/CVE-2026-89441",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  mmc: via-sdmmc: cancel card-detect work on remove  Disabling the device interrupt and freeing the IRQ prevents new card-detect work from being queued, but carddet_work already queued by the handler can still run after via_sd_remove() returns. via_sdc_card_detect() recovers the host through container_of() and dereferences its MMIO base; once remove() returns the host can be freed, so that work would touch freed memory.  Cancel carddet_work after freeing the IRQ and before cancelling finish_bh_work, which the card-detect handler can also queue. carddet_work can re-enable the interrupt through via_reset_pcictrl(); mask it again afterwards.  This issue was found by an in-house static analysis tool and confirmed by manual code review.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-09-11 20:19:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-89465",
                        "url": "https://ubuntu.com/security/CVE-2026-89465",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  power: supply: rt9455: quiesce delayed work before teardown  The threaded IRQ handler can queue pwr_rdy_work, max_charging_time_work and batt_presence_work.  pwr_rdy_work and batt_presence_work can also queue max_charging_time_work, while batt_presence_work can requeue itself.  rt9455_remove() cancels max_charging_time_work before batt_presence_work.  The latter can therefore queue max_charging_time_work after it has already been cancelled:    rt9455_remove()                   workqueue     cancel pwr_rdy_work     cancel max_charging_time_work                                       batt_presence_work queues                                         max_charging_time_work     cancel batt_presence_work     return     devres frees rt9455_info                                       max_charging_time_work dereferences                                         rt9455_info  The IRQ also remains registered until devres cleanup and can queue more work after any of the cancellation calls.  If rt9455_hw_init() fails after the IRQ has been requested, probe returns without cancelling work that may already have been queued.  A pending callback can then access rt9455_info after it has been freed.  Register rt9455_cancel_all_delayed_works() through devm_add_action_or_reset() right after devm_power_supply_register(). devres invokes the action in reverse registration order, after the managed IRQ has been freed and before rt9455_info is released, so the delayed works are drained in both rt9455_remove() and the probe error path.  Cancel pwr_rdy_work and batt_presence_work before max_charging_time_work because both can queue the latter.  This issue was found by an in-house static analysis tool.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-09-11 20:19:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-93231",
                        "url": "https://ubuntu.com/security/CVE-2026-93231",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  lockd: fix swapped arguments in nlmsvc_match_ip()  When releasing locks by server IP address via /proc/fs/nfsd/unlock_ip, nlmsvc_unlock_all_by_ip() calls nlm_traverse_files() with the server sockaddr as the opaque @data argument:  \tnlm_traverse_files(server_addr, nlmsvc_match_ip, NULL);  The match callback is later invoked from nlm_traverse_locks() as:  \tmatch(lockhost, host);  where the first argument is the nlm_host that owns the lock, and the second argument is the @data that was originally passed down (here the server sockaddr).  This is the convention every other match callback relies on (nlmsvc_mark_host(), nlmsvc_same_host(), nlmsvc_is_client()): arg1 is the real nlm_host, arg2 is the caller-supplied reference value.  nlmsvc_match_ip() has had these two arguments reversed ever since the unlock-by-IP feature was introduced in commit 4373ea84c84d (\"lockd: unlock lockd locks associated with a given server ip\"):  \treturn rpc_cmp_addr(nlm_srcaddr(host), datap);  Here @host is actually the server sockaddr, so nlm_srcaddr(host) dereferences a struct sockaddr as a struct nlm_host and reads garbage at the offset of h_srcaddr; meanwhile @datap is actually the lock owner's nlm_host but is compared as a sockaddr.  As a result the comparison practically never matches and locks are not released for the requested IP.  Swap the arguments so the lock owner's source address is compared against the requested server address:  \treturn rpc_cmp_addr(nlm_srcaddr(datap), (struct sockaddr *)host);  [ cel: fix the misleading typedef parameter names too ]",
                        "cve_priority": "low",
                        "cve_public_date": "2026-09-24 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-89552",
                        "url": "https://ubuntu.com/security/CVE-2026-89552",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  params: fix charp corruption on allocation failure  param_set_charp() stores charp parameters in allocated memory after slab is available, and releases the previous value when the parameter is updated.  The previous value is released before the replacement allocation succeeds. If kmalloc_parameter() fails, the setter returns -ENOMEM with the parameter left as NULL.  Failing zswap's compressor update before zswap is initialized can later trigger:    BUG: kernel NULL pointer dereference, address: 0000000000000000   RIP: 0010:strcmp+0x10/0x30   Call Trace:     zswap_setup+0x3b1/0x490     zswap_enabled_param_set+0x5b/0xa0     param_attr_store+0x93/0xe0     module_attr_store+0x1c/0x30     kernfs_fop_write_iter+0x116/0x1f0  Allocate and copy the replacement first, then replace the parameter value only after allocation succeeds.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-09-11 20:19:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-89640",
                        "url": "https://ubuntu.com/security/CVE-2026-89640",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  cifs: fix loff_t underflow in cifs_remap_file_range() when len == 0  With len == 0 (clone to EOF), the effective length is computed as:      len = src_inode->i_size - off;  If off > i_size, this is a negative loff_t, corrupting the ByteCount in the FSCTL_DUPLICATE_EXTENTS_TO_FILE request and inverting the range in filemap_write_and_wait_range().  The existing off >= i_size check fires only after the ioctl has already been sent.  Snapshot i_size_read() once for both the bounds check and the length calculation, eliminating the TOCTOU and 32-bit torn-read risk.  Reject off > src_size with -EINVAL.  Treat off == src_size as a no-op, consistent with __generic_remap_file_range_prep().",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-09-11 20:19:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-89672",
                        "url": "https://ubuntu.com/security/CVE-2026-89672",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  nfsd: gate nfs2 setacl by argp->mask  The NFSACL v2 SETACL path shares the decoder convention used by its v3 sibling: nfsaclsvc_decode_setaclargs() fills in argp->acl_access only when NFS_ACL is set in the request mask and argp->acl_default only when NFS_DFACL is set, leaving the other pointer NULL because the argument buffer is zeroed up to pc_argzero before decode.  nfsacld_proc_setacl() then hands both pointers to set_posix_acl() unconditionally. set_posix_acl(idmap, dentry, type, NULL) is the VFS \"remove this ACL type\" operation, so an omitted arm is indistinguishable from an explicit request to delete that ACL. A SETACL carrying only NFS_ACL silently strips the directory's default ACL; mask=0 strips both.  This is the same defect just fixed in nfsd3_proc_setacl(); apply the same remedy. Gate each set_posix_acl() call on its mask bit and initialize error to 0 so that a request with neither bit set leaves the on-disk ACLs untouched and returns success. The out_drop_lock path and the unconditional posix_acl_release() in nfsaclsvc_release_setacl() already tolerate the skipped arms.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-09-11 20:19:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-89685",
                        "url": "https://ubuntu.com/security/CVE-2026-89685",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  nfsd: fix clock domain mismatch in clients_still_reclaiming()  clients_still_reclaiming() computes a deadline from nn->boot_time (CLOCK_REALTIME, ~1.7 billion) but compares it against ktime_get_boottime_seconds() (CLOCK_BOOTTIME, seconds since boot). The comparison is always false — it would take ~54 years of uptime for BOOTTIME to exceed the REALTIME-derived deadline.  This means any client can hold the server in grace indefinitely by sending CLAIM_PREVIOUS OPEN requests, blocking all non-reclaim operations for all other clients.  Add boot_time_bt (CLOCK_BOOTTIME) alongside the existing boot_time and use it for the deadline computation. boot_time (CLOCK_REALTIME) is preserved for its cl_boot clientid-nonce role.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-09-11 20:19:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-89707",
                        "url": "https://ubuntu.com/security/CVE-2026-89707",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  nfsd: release path refs on follow_down() error  nfsd_cross_mnt() initializes a local struct path with mntget() and dget() before calling follow_down(). On a negative return the error arm jumps to out without releasing those references:      err = follow_down(&path, follow_flags);     if (err < 0)             goto out;  follow_down() never drops the caller's entry-time refs on any error sub-case; for example a pre-cross d_manage() failure leaves path untouched, so the mntget()/dget() taken on entry survive the call.  Every other early-exit arm in nfsd_cross_mnt() (other-namespace return, IS_ERR(exp2), and the success tail after the swap) already calls path_put(&path); the err < 0 arm is the lone omission. The leak inflates mnt_count and d_count on each failed cross-mount, blocking umount and pinning dentries against the shrinker, and is reachable by any authenticated NFS client through nfsd_lookup_dentry or the NFSv4 READDIR encode path.  Fix by calling path_put(&path) before the goto out in the err < 0 arm so the entry-time refs are released on all follow_down() error returns.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-09-11 20:19:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-89719",
                        "url": "https://ubuntu.com/security/CVE-2026-89719",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  zram: fix out-of-bounds access in read_block_state()  read_block_state() calculates nr_pages before taking dev_lock.  If the device is reset and reinitialized with a smaller disksize before lock acquisition, nr_pages still describes the old table.  The subsequent loop can then call slot_lock() past the end of the newly allocated table.  Read disksize after acquiring dev_lock and checking that the device is initialized.  The read lock then keeps the table and its bound stable for the duration of the scan.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-09-11 20:20:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-89763",
                        "url": "https://ubuntu.com/security/CVE-2026-89763",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  KEYS: trusted: Fix TPM teardown ordering  trusted_tpm_exit() drops the TPM chip reference and frees the digest array before unregistering the trusted key type. key_type_lookup() holds key_types_sem for reading until the key operation finishes, while unregister_key_type() takes it for writing. It therefore provides the synchronization point that must precede backend teardown.  The current order permits this interleaving:    CPU 0                              CPU 1   trusted_tpm_exit()                 key_type_lookup(\"trusted\")     put_device(&chip->dev)             trusted_tpm_seal()     kfree(digests)                       pcrlock()     unregister_key_type()                  tpm_pcr_extend(..., digests)  CPU 1 can consequently dereference the freed digest array. The chip can also be released before callbacks stop using it.  KASAN reported:    BUG: KASAN: slab-use-after-free in tpm_pcr_extend+0x1f0/0x200   Read of size 2 at addr ffff88810872d000 by task poc/89   Call Trace:     tpm_pcr_extend+0x1f0/0x200     pcrlock+0x42/0x70 [trusted]     trusted_tpm_seal+0x1b6/0x570 [trusted]     trusted_instantiate+0x293/0x340 [trusted]     __key_instantiate_and_link+0xb2/0x2b0     __key_create_or_update+0x61e/0xb50     __do_sys_add_key+0x1b8/0x310   Allocated by task 88:     __kmalloc_noprof+0x1a7/0x490     do_one_initcall+0xa1/0x390     do_init_module+0x2df/0x840   Freed by task 90:     kfree+0x131/0x3c0     trusted_tpm_exit+0x59/0xa0 [trusted]     __do_sys_delete_module+0x346/0x510  Move unregister_key_type() before releasing either resource. This stops new lookups and waits for in-flight key operations to finish before the backend state is destroyed.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-09-11 20:20:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-80851",
                        "url": "https://ubuntu.com/security/CVE-2026-80851",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  gtp: serialize PDP context updates  PDP contexts can be deleted through GTP_CMD_DELPDP or while the GTP network device is being unregistered. The latter is serialized by RTNL, but the generic-netlink delete path only holds RCU.  Running both paths concurrently can therefore make both paths delete the same PDP context. The issue was found through static analysis and reproduced on a KASAN-enabled kernel by a simple two-thread program racing GTP_CMD_DELPDP against RTM_DELLINK:    Oops: general protection fault, probably for non-canonical address   KASAN: maybe wild-memory-access in range          [0xdead000000000120-0xdead000000000127]   RIP: gtp_genl_del_pdp+0x1c1/0x420 [gtp]   RBP: dead000000000122  The second deletion dereferenced the poisoned hlist pprev pointer.  Serialize gtp_pdp_add(), gtp_genl_del_pdp(), and gtp_dellink() with a shared mutex. Keep the mutex held until the final use of a PDP context in the NEWPDP path, and keep the RCU read-side section around the complete PDP context use in the DELPDP path.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-09-04 16:18:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-80861",
                        "url": "https://ubuntu.com/security/CVE-2026-80861",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  usb: xhci: bail out of setup if the controller is inaccessible  xhci_gen_setup() locates the operational registers using the capability length read from the very first register:  \txhci->op_regs = hcd->regs + \t\tHC_LENGTH(readl(&xhci->cap_regs->hc_capbase));  If the controller is dead or has dropped off the bus, that read returns ~0, HC_LENGTH() truncates it to 0xff, and op_regs ends up 0xff bytes past the page-aligned MMIO base, i.e. unaligned. The first access through it, xhci_halt() -> xhci_handshake() reading op_regs->status, is then an unaligned readl() on device memory. arm64 faults on unaligned device accesses, so instead of xhci_handshake() catching the all-ones value and returning -ENODEV, setup oopses:    xhci-pci-renesas 0005:08:00.0: Unable to change power state from D3cold to D0, device inaccessible   xhci-pci-renesas 0005:08:00.0: xHCI Host Controller   xhci-pci-renesas 0005:08:00.0: new USB bus registered, assigned bus number 1   Unable to handle kernel paging request at virtual address ffff80030a770103     ESR = 0x0000000096000021     FSC = 0x21: alignment fault   Internal error: Oops: 0000000096000021 [#1]  SMP   pc : xhci_halt [xhci_hcd]   Call trace:    xhci_halt    xhci_gen_setup    xhci_pci_setup    usb_add_hcd    usb_hcd_pci_probe    xhci_pci_common_probe    xhci_pci_renesas_probe  This was hit with a Renesas uPD720201 that failed to power up (\"Unable to change power state from D3cold to D0, device inaccessible\") yet still reached the HCD probe path.  Read the capability register once, and if it reads back the all-ones value (as xhci_handshake() and xhci_reset() already test for), abort setup with -ENODEV before op_regs is derived from it. Reading it once also avoids re-reading a register that may change under a concurrent hot-removal.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-09-04 16:18:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98377",
                        "url": "https://ubuntu.com/security/CVE-2026-98377",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  vlan: require the MAC header to be present in __vlan_insert_inner_tag()  __vlan_insert_inner_tag() only guarantees head room via skb_cow_head(), never that mac_len bytes of MAC header are present.  Its ETH_HLEN wrappers - __vlan_insert_tag() under skb_vlan_push(), and vlan_insert_tag() under validate_xmit_vlan() on the generic transmit path - therefore rewrite the first 16 bytes at skb->data: a 12-byte memmove plus two 2-byte stores at +12 and +14.  No caller supplies the bound, while the pop helpers use skb_ensure_writable()/pskb_may_pull().  An IFF_TUN device has hard_header_len == 0, so packet_snd() accepts a one-byte AF_PACKET/SOCK_RAW frame.  The first vlan push only sets a hwaccel tag; the next - clsact \"action vlan push\" or bpf_skb_vlan_push() - enters the helper with skb->len still 1.  The head comes from skbuff_small_head without __GFP_ZERO, so each push drags bytes from beyond skb->tail into the frame.  After three the one-byte send leaves as 13 bytes carrying 11 bytes of uninitialised slab:    0000: 5a b3 62 12 80 88 ff ff 00 b3 62 12 81            `------------------------------'   only 0x5a was sent; the rest is slab, here the top 56 bits of a   linear-map address  Require the MAC header the helper rewrites to be present, so such a frame is dropped rather than transmitted.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-09 08:16:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98170",
                        "url": "https://ubuntu.com/security/CVE-2026-98170",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  smb: client: fix OOB struct field reads in move_smb2_ea_to_cifs()  In move_smb2_ea_to_cifs(), the while (src_size > 0) loop condition is insufficient. It allows iteration to continue even if the remaining src_size is too small to contain a complete smb2_ea_info structure. Consequently, reads of ea_name_length and ea_value_length can occur out-of-bounds.  Fix this by ensuring src_size >= sizeof(*src) before attempting to read any structure fields. Additionally, reject any next_entry_offset that is smaller than sizeof(*src) or that would advance the pointer beyond the available buffer.  Note that for calls where the server returns a malformed EA list, the error returned to userspace changes from -ENODATA (getxattr) or -ERANGE (listxattr) to -EIO. This correctly signals a server protocol error rather than misleadingly indicating \"attribute not present\" or \"output buffer too small\".",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-06 09:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98171",
                        "url": "https://ubuntu.com/security/CVE-2026-98171",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  smb: client: fix next_buffer UAF and NextCommand bounds in compound PDUs  Fix several related bounds checking and pointer lifecycle issues in receive_encrypted_standard()'s handling of compound encrypted frames:  - Clear next_buffer after assigning it to server->bigbuf. A stale   next_buffer pointer can lead to a use-after-free on subsequent   error paths. - Update pdu_length to the decrypted plaintext size (buf_size). Using   the pre-decryption length allows NextCommand to point into stale   ciphertext residue. - Reject next_cmd values smaller than MID_HEADER_SIZE(server). - Fix an integer overflow in the upper bound check by verifying   pdu_length - next_cmd < MID_HEADER_SIZE(server), ensuring the   trailing slice is large enough for a header.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-06 09:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98169",
                        "url": "https://ubuntu.com/security/CVE-2026-98169",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  smb: client: fix potential OOB read in smb3_enum_snapshots()  If snapshot_array_size is smaller than GMT_TOKEN_SIZE, smb3_enum_snapshots() sets ret_data_len to sizeof(struct smb_snapshot_array) without verifying the actual length of the server's reply.  Because SMB2_ioctl() places no lower bound on the server-supplied OutputCount and allocates retbuf to exactly that length, a short reply results in ret_data_len exceeding the size of retbuf. The subsequent copy_to_user() then reads past the end of retbuf, leaking adjacent slab memory to userspace.  The subsequent clamp check is ineffective as it only reduces ret_data_len.  Fix this by rejecting replies shorter than sizeof(struct smb_snapshot_array) with -EIO. Note that the bound is set to the 12-byte struct size rather than the 16-byte MIN_SNAPSHOT_ARRAY_SIZE defined in MS-SMB2 3.3.5.15.1, because 12 bytes is exactly what copy_to_user() attempts to read.",
                        "cve_priority": "negligible",
                        "cve_public_date": "2026-10-06 09:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98193",
                        "url": "https://ubuntu.com/security/CVE-2026-98193",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: libipw: reject TKIP frames without a full MIC  libipw_michael_mic_verify() assumes that an skb contains an eight-byte Michael MIC. A short TKIP frame makes the unsigned payload length wrap, causing michael_mic() to read past the skb.  Check that the MIC is present before verifying it, and use the existing MICHAEL_MIC_LEN constant for all MIC lengths in the verifier.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-06 09:18:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-97555",
                        "url": "https://ubuntu.com/security/CVE-2026-97555",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  smb: client: fix heap overflow in DACL owner/group rewrite  When id_mode_to_cifs_acl rewrites an existing DACL, it allocates a buffer sized according to the on-disk DACL length reported by dacl_ptr->size. However, replace_sids_and_copy_aces may rewrite each ACE with a new owner/group SID obtained from the cifs.idmap upcall. Those SIDs can have up to SID_MAX_SUB_AUTHORITIES (15) sub-authorities, making each ACE up to 76 bytes (sizeof(struct smb_ace)).  If the original DACL contains short SIDs (e.g., 1 sub-authority) while the replacement SIDs are long, the rewritten ACEs overflow the allocation.  Fix this by always budgeting for worst-case SID expansion: allocate sizeof(struct smb_acl) plus num_aces * sizeof(struct smb_ace), which covers the smb_acl header and room for every ACE at maximum SID size. This replaces the previous split logic that used dacl_ptr->size for cifsacl mounts but num_aces * sizeof(struct smb_ace) for mode_from_sid mounts: both paths can trigger the same rewrite and need the same headroom.  KASAN reports this as:   BUG: KASAN: slab-out-of-bounds in build_sec_desc+0x1e8a/0x2680 [cifs]   Write of size 4 at addr ffff8881a5e25374 by task chown/5298   ...   The buggy address is located 0 bytes to the right of    allocated 884-byte region [ffff8881a5e25000, ffff8881a5e25374)",
                        "cve_priority": "high",
                        "cve_public_date": "2026-09-25 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-97557",
                        "url": "https://ubuntu.com/security/CVE-2026-97557",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  smb: client: avoid leaking refcount in cifs_queue_oplock_break()  cifs_queue_oplock_break() unconditionally takes a reference on the target file before queueing cifs_oplock_break(). Only that work item decreases the reference counter again.  If another oplock break arrives while that work is still queued, queue_work() will return false and not queue this second work item. As a result, we will never reach the point to drop the file reference again and are leaking this reference. This can be triggered when interacting with a slow-responding server.  As a result, later unmount operations for this file system will fail with    BUG: Dentry ... still in use (1) [unmount of cifs cifs]   VFS: Busy inodes after unmount of cifs (cifs)   kernel BUG at fs/super.c:777!  Fix this by only incrementing the reference count if the work has been queued successfully. Taking it after queue_work() is safe because all three callers hold tcon->open_file_lock across the call and _cifsFileInfo_put() decrements under that same lock, so a worker that starts the handler in the window cannot drop the reference before it has been taken.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-09-25 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-97564",
                        "url": "https://ubuntu.com/security/CVE-2026-97564",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  smb: client: reject userspace cifs.idmap descriptions  cifs.idmap key descriptions carry authority-bearing fields (owner and group SIDs and uid/gid values in \"os:\"/\"gs:\"/\"oi:\"/\"gi:\" form) that the cifs.idmap upcall helper treats as kernel-originating inputs.  Unlike its sibling cifs.spnego, the cifs.idmap key type has no vet_description hook, so userspace can create keys of this type through request_key(2)/add_key(2) and supply those fields without CIFS origin. A request_key(2) call with a non-NULL callout then drives a root usermodehelper upcall (/sbin/request-key -> cifs.idmap) that consumes the unvetted description in root context.  Only accept cifs.idmap descriptions while CIFS is using its private root_cred to request the key.  id_to_sid()/sid_to_id() already run under override_creds(root_cred), so the kernel-originated path is unaffected.  This mirrors commit 3da1fdf4efbc (\"smb: client: reject userspace cifs.spnego descriptions\"), which applied the same restriction to cifs.spnego.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-09-25 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-97615",
                        "url": "https://ubuntu.com/security/CVE-2026-97615",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net: bridge: use option bits for CFM/MRP frame handlers  CFM and MRP register a global br_frame_type whose hlist_node is linked into the per-bridge frame_type_list when the first MEP/MRP instance is created. Enabling the protocol on multiple bridges therefore inserts the same node into multiple lists. Unregistering it on one bridge then corrupts list state belonging to another.  These handlers can only be installed once per bridge, and they are uncommon. Track their per-bridge enable state with net_bridge option bits, which already live on the Rx hot cache line, and dispatch the matching handler directly from the receive path. Check both bits together first as an unlikely case.  Remove the generic frame_type_list and br_frame_type helpers, which have had no other users since CFM and MRP were added. That shrinks struct net_bridge by 8 bytes and drops the list walk from the fast path. When neither protocol is compiled in, BR_CFM_MRP_OPTS is 0 and the compiler prunes the branch.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-09-25 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-97901",
                        "url": "https://ubuntu.com/security/CVE-2026-97901",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  genetlink: pin family module during policy dump  The generic netlink controller's policy dump keeps pointers to the target family's operation and policy tables in its callback state.  A dump may be split across multiple skbs and remain pending after the initial request.  Netlink pins the module which owns the dump callback, but in this case that is the controller's owner rather than the target family's owner.  The target family can consequently be unregistered and its module unloaded while a policy dump is pending.  Advancing the dump then dereferences policy memory from the unloaded module.  Take a reference to the target family's module when the dump starts. Drop it from the error and done paths.  This matches the lifetime for which the dump context retains the family and policy pointers.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-09-25 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-97908",
                        "url": "https://ubuntu.com/security/CVE-2026-97908",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  Bluetooth: btqcomsmd: destroy RPMsg endpoints before freeing hci_dev  The command and ACL RPMsg endpoints store struct btqcomsmd as their callback private data. The receive callbacks dereference btq->hdev without taking an hci_dev reference.  The current teardown order frees the hci_dev before destroying the RPMsg endpoints in both the hci_register_dev() error path and the driver remove path. If WCNSS delivers data in that window, the endpoint callback can run with an already freed hci_dev and pass it to the Bluetooth core.  For qcom_smd endpoints, rpmsg_destroy_ept() closes the channel and clears the callback under the channel recv_lock. The receive path holds the same lock while invoking the callback, so destroying the endpoints first both prevents new callbacks and serializes with any callback already running.  Destroy the command and ACL endpoints before hci_free_dev(). Keep hci_unregister_dev() first during remove so the HCI core stops issuing operations before the transport endpoints are shut down. In the full registration-error cleanup path, return directly after freeing the hci_dev to avoid falling through to the partial-construction labels and destroying the endpoints twice.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-09-25 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-97925",
                        "url": "https://ubuntu.com/security/CVE-2026-97925",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  tick/broadcast: Plug clockevents replacement race  朱恺乾 reported and decoded the following race condition when a broadcast device is replaced:  CPUA\t\t\t\t\tCPUB  __tick_broadcast_oneshot_control()    bc = tick_broadcast_device.evtdev; \t\t\t\t\ttick_install_broadcast_device(dev)         \t\t\t\tclockevents_exchange_device(cur, dev) \t\t\t\t\t   shutdown(cur); \t\t\t\t\t   detach(cur); \t\t\t\t\t   cur->handler = noop; \t\t\t\t\t   tick_broadcast_device.evtdev = dev;    tick_broadcast_set_event(bc, next_event); <- FAIL: arms a detached device.  If the original broadcast device has a restricted interrupt affinity mask and the last CPU in that mask goes offline then the BUG() in tick_cleanup_dead_cpu() triggers because the clockevent device is not in detached state.  The reason for this is that tick_install_broadcast_device() is not serialized vs. tick broadcast operations.  The obvious cure is to serialize tick_install_broadcast_device() with tick_broadcast_lock against a concurrent tick broadcast operation.  That requires to split clockevents_exchange_device() into two parts, one which does the exchange, shutdown and detach operation and the other which drops the module reference count. This is required because the module reference cannot be dropped while holding tick_broadcast_lock.  Let clockevents_exchange_device() do both operations as before, but let the broadcast device code take the two step approach and do the device exchange under tick_broadcast_lock and drop the module reference count after releasing it.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-09-25 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-93285",
                        "url": "https://ubuntu.com/security/CVE-2026-93285",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  f2fs: embed f2fs_gc_kthread in f2fs_sb_info  Instead of allocating f2fs_gc_kthread dynamically, embed it in f2fs_sb_info. This simplifies lifetime management and prepares for fixing race conditions during teardown.  - __sbi_store\t\t\t- remount|shutdown \t\t\t\t - f2fs_stop_gc_thread  - access sbi->gc_thread \t\t\t\t  - sbi->gc_thread = NULL  - access sbi->gc_thread->f2fs_gc_task",
                        "cve_priority": "low",
                        "cve_public_date": "2026-09-24 17:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-97529",
                        "url": "https://ubuntu.com/security/CVE-2026-97529",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  scsi: qla2xxx: Validate BSG request_len before reading vendor_cmd[]  The FC BSG transport allocates job->request via memdup_user() using the exact user-supplied request_len. For FC_BSG_HST_VENDOR, fc_bsg_host_dispatch() only guarantees request_len covers msgcode and vendor_id; it does not account for the vendor_cmd[] flexible array.  qla2xxx then reads the command selector vendor_cmd[0] and, in several sub-handlers, vendor_cmd[1]/[2] or structures overlaid on the vendor command area without verifying request_len. A caller holding CAP_SYS_RAWIO can submit a short request whose vendor_id matches the host, triggering out-of-bounds heap reads (KASAN-detectable, and able to mis-select a command or panic).  Add a central guard in qla2x00_process_vendor_specific() so the selector is always in bounds, restrict the early vendor_cmd[0] read in qla24xx_bsg_request() to sufficiently long vendor messages, and add request_len checks to the sub-handlers that read further: qla24xx_proc_fcp_prio_cfg_cmd(), qla2x00_process_loopback(), qla84xx_reset(), qla84xx_updatefw(), qla2x00_read_optrom(), qla2x00_update_optrom(), qlafx00_mgmt_cmd() and qla28xx_validate_flash_image().",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-09-25 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-97536",
                        "url": "https://ubuntu.com/security/CVE-2026-97536",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  scsi: qla2xxx: Fix use-after-free of qpair work on queue teardown  The response queue MSI-X handler qla2xxx_msix_rsp_q() schedules qla_do_work() via queue_work(ha->wq, &qpair->q_work). qla_do_work() dereferences the qpair (vha, rsp) and takes qpair->qp_lock.  During teardown, qla2xxx_delete_qpair() deletes the response queue, which calls free_irq() in qla25xx_free_rsp_que(), and then frees the queue and the qpair. free_irq() waits for running hardirq handlers but does not cancel work already placed on ha->wq. A still-pending q_work then runs qla_do_work() against the freed qpair and response queue, causing a use-after-free. This is especially likely during full adapter teardown, where destroy_workqueue(ha->wq) forces pending work to run after the queue pairs have been freed.  Flush the work item with cancel_work_sync() in qla25xx_free_rsp_que() after free_irq() has released the interrupt (so no new work can be queued) and before the response queue and qpair memory are freed (so the flushed handler still sees valid memory). Guard on rsp->qpair and ha->wq to match the INIT_WORK() condition and avoid operating on an uninitialized work_struct.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-09-25 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-97537",
                        "url": "https://ubuntu.com/security/CVE-2026-97537",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  scsi: qla2xxx: Fix queue teardown NULL dma_free and bitmap locking  qla25xx_free_req_que() and qla25xx_free_rsp_que() have two pre-existing bugs exposed on the error path of qla25xx_create_{req,rsp}_que():   1. When dma_alloc_coherent() fails during queue creation, the error     path calls the free function with req->ring / rsp->ring still NULL     (from kzalloc).  The unconditional dma_free_coherent() with a NULL     cpu_addr is undefined behavior and can panic.   2. The free functions clear req_qid_map / rsp_qid_map under vport_lock,     but the create functions protect the same bitmaps with mq_lock.     This provides no mutual exclusion.  Additionally, the create error     path clears the bit and releases mq_lock before calling the free     function, creating a window where another thread can allocate the     same que_id and have its ha->req_q_map entry clobbered by the     subsequent lockless NULL assignment in the free function.  Fix by:   - Guarding dma_free_coherent() with a NULL check on the ring pointer.   - Using mq_lock (the lock held by all creators) in the free functions    to atomically NULL the map entry and clear the bitmap bit.   - Removing the now-redundant clear_bit blocks from the create error    paths since the free functions handle it atomically.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-09-25 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-89859",
                        "url": "https://ubuntu.com/security/CVE-2026-89859",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  scsi: qla2xxx: Zero dport diagnostics buffer to avoid info leak  qla2x00_do_dport_diagnostics() allocates the qla_dport_diag response buffer with kmalloc_obj() (non-zeroing) and, on success, copies the full sizeof(*dd) back to user space via sg_copy_from_buffer(). The inbound sg_copy_to_buffer() only fills as many bytes as the user request payload provides, and qla26xx_dport_diagnostics() zeroes only dd->buf. The options and unused[] fields are therefore copied out uninitialized, leaking kernel heap contents to user space.  Allocate with kzalloc_obj(), matching qla2x00_do_dport_diagnostics_v2().",
                        "cve_priority": "low",
                        "cve_public_date": "2026-09-16 11:16:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-89921",
                        "url": "https://ubuntu.com/security/CVE-2026-89921",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  KVM: s390: Zero initialize data structures for inject_pfault_token  __kvm_inject_pfault_token() only sets .type and .u.ext.ext_params2 of the on-stack struct kvm_s390_irq but the full ext substructure is copied into the cpu local variable on inject. ext_params and pad contain stale stack values.  Interrupt delivery only uses ext_params2, so nothing leaks to the guest, but a host user can use the migration ioctls to get to the data.  Fix by zero-initializing the irq struct. Do the same for the inti data structure.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-09-16 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-89972",
                        "url": "https://ubuntu.com/security/CVE-2026-89972",
                        "cve_description": "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 reference to ns when kfree(ns) runs.  The normal removal path in nvme_ns_remove() correctly calls synchronize_srcu(&ns->head->srcu) after list_del_rcu() to wait for in-progress readers. Add the same grace period in the error path.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-09-16 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-89988",
                        "url": "https://ubuntu.com/security/CVE-2026-89988",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  kprobes: Protect kprobe_blacklist with RCU  __within_kprobe_blacklist() traverses kprobe_blacklist without holding kprobe_mutex. When a module is unloaded, kprobe_remove_area_blacklist() removes blacklist entries and immediately frees them with kfree(). A concurrent call to within_kprobe_blacklist() can therefore dereference freed memory.  Furthermore, within_kprobe_blacklist() can be called in atomic or non-preemptible contexts where the sleeping kprobe_mutex cannot be taken.  Protect kprobe_blacklist with RCU. Use guard(rcu)() and list_for_each_entry_rcu() for traversal, list_add_tail_rcu() for insertions, list_del_rcu() for deletions, and kfree_rcu() to reclaim entries safely after a grace period.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-09-16 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-90002",
                        "url": "https://ubuntu.com/security/CVE-2026-90002",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ftrace: Take trace_array reference before accessing its ftrace_ops  The trace instance files set_ftrace_filter and set_ftrace_notrace was updated to work with specific trace instances (trace_arrays). The issue is that when these files are opened, there is a small race window where it will use the ftrace_ops from the inode->private pointer to get a reference to the trace_array and then take its reference. The problem is that the ftrace_ops itself could be freed. If the rmdir on the instance happens at the same time the set_ftrace_filter file is opened, the rmdir could have also freed the ftrace_ops and referencing it will cause a use-after-free bug and crash the kernel.  Instead, pass in the trace_array as the file private data (NULL for the top level instance), and then pass both the trace_array and the ftrace_ops to the ftrace_regex_open() function. If the trace_array is NULL, then it just uses the ftrace_ops without the need to take its reference (like normal). If the ftrace_ops is NULL, that is only the case for the top level instance and the global_ops can be used.  This allows the trace_array to have its reference incremented before touching the ftrace_ops that could also be freed when the instance is.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-09-16 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-90016",
                        "url": "https://ubuntu.com/security/CVE-2026-90016",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  staging: rtl8723bs: fix OOB read in rtw_restruct_wmm_ie()  rtw_restruct_wmm_ie() scans in_ie for a WMM IE with:  \twhile (i < in_len) { \t\t... \t\tif (i + 5 < in_len && in_ie[i] == 0xDD && ...) { \t\t\t... \t\t\tbreak; \t\t} \t\ti += (in_ie[i + 1] + 2); /* to the next IE element */ \t}  When the \"i + 5 < in_len\" match check fails simply because i is within 5 bytes of the end of the buffer (i.e. no WMM IE was found near the tail of in_ie), execution falls through to \"i += (in_ie[i + 1] + 2)\", which reads in_ie[i + 1]. If i == in_len - 1 at that point, this is a 1-byte out-of-bounds read of an attacker-influenced IE buffer built from association/scan data.  Commit a75281626fc8f (\"staging: rtl8723bs: fix potential out-of-bounds read in rtw_restruct_wmm_ie\") added the \"i + 5 < in_len\" guard to the match condition itself, but did not add an equivalent guard before the fallthrough advance, so the same class of OOB read remained reachable through the non-matching path.  Add an explicit bounds check before advancing to the next IE.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-09-16 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-90029",
                        "url": "https://ubuntu.com/security/CVE-2026-90029",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  usb: storage: realtek_cr: fix use-after-free on disconnect  realtek_cr_destructor() calls timer_delete() before the chip containing the timer is freed. The timer callback may still be running and can rearm itself, resulting in a use-after-free.  Use timer_shutdown_sync() to wait for the callback and prevent further rearming. Do this unconditionally because ss_en may be changed after the timer is armed.  Move timer_setup() into init_realtek_cr() so the timer is initialized before any failure path can invoke the destructor.  Found by static analysis.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-09-16 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-80947",
                        "url": "https://ubuntu.com/security/CVE-2026-80947",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: rtl8xxxu: fix use-after-free from rx_urb_wq on stop  rtl8xxxu arms rx_urb_wq from the RX completion path: rtl8xxxu_rx_complete() hands the URB to rtl8xxxu_queue_rx_urb(), which queues it on rx_urb_pending_list and, once the list grows past RTL8XXXU_RX_URB_PENDING_WATER, schedules rx_urb_wq.  The worker rtl8xxxu_rx_urb_work() drains rx_urb_pending_list, recovers priv through container_of, and resubmits each URB through rtl8xxxu_submit_rx_urb(), which anchors it on rx_anchor and dereferences priv->udev.  rtl8xxxu_stop() cancels the sibling work items (c2hcmd_work, ra_watchdog, update_beacon_work) but never cancels rx_urb_wq, so a worker armed during the last burst of RX traffic can run rtl8xxxu_rx_urb_work() after rtl8xxxu_disconnect() has called ieee80211_free_hw(), which frees priv, producing a use-after-free.  The window opens under active RX traffic (pending count above the watermark) followed by a disconnect.  There are two teardown races to close:    * rtl8xxxu_queue_rx_urb() decided whether to enqueue under rx_urb_lock     but called schedule_work() after dropping the lock.  A completion     that observed shutdown == false and released the lock could then call     schedule_work() after rtl8xxxu_stop() had set shutdown and     cancel_work_sync() had already returned, arming the worker to run     after the teardown.  Move schedule_work() under the same !shutdown     branch so the arming decision is atomic with the shutdown check.    * rtl8xxxu_rx_urb_work() anchors every URB it drained back onto     rx_anchor through rtl8xxxu_submit_rx_urb().  A worker still running     when usb_kill_anchored_urbs(&priv->rx_anchor) returned would submit a     URB that escaped the kill.  In rtl8xxxu_stop(), call     cancel_work_sync(&priv->rx_urb_wq) before the kill so the worker is     drained first.  After priv->shutdown is set under rx_urb_lock, completions can no longer queue rx_urb_wq. cancel_work_sync() then drains the last queued or running worker, and the following usb_kill_anchored_urbs() kills the URBs it may have submitted.  rtl8xxxu_disconnect() is covered because ieee80211_unregister_hw() guarantees .stop() runs for a live interface before ieee80211_free_hw() frees priv.  The probe error path needs no cancel: rx_urb_wq is INIT_WORK()'d there but cannot have been scheduled, since no URB is submitted before ieee80211_register_hw() succeeds.  This bug was found by static analysis.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-09-11 20:19:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-89481",
                        "url": "https://ubuntu.com/security/CVE-2026-89481",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  nvme-tcp: fix host memory disclosure on R2T for a read command  nvme_tcp_handle_r2t() does not check the direction of the request the R2T refers to. A malicious controller can send an R2T for a READ and the host will answer it: nvme_tcp_setup_h2c_data_pdu() builds the H2CData header and nvme_tcp_try_send_data() sends the request's data buffer. That buffer is the READ destination, so its contents go to the controller.  The command then completes normally and nothing is logged.  Against a test controller that answers every READ with an R2T, a 4096 byte buffered read returned all 4096 bytes, split over two R2Ts. The pages contained stale kernel data, including an array of struct page pointers.  Reject an R2T for a request that is not a write.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-09-11 20:19:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-89492",
                        "url": "https://ubuntu.com/security/CVE-2026-89492",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ocfs2: validate directory-index entry counts when reading metadata  ocfs2_validate_dx_leaf() and ocfs2_validate_dx_root() check the ECC and signature of an indexed-directory block before it reaches higher-level callers, but neither validator bounds the ocfs2_dx_entry_list counts against the capacity of the block that holds them.  ocfs2_dx_dir_search() then walks  \tfor (i = 0; i < le16_to_cpu(entry_list->de_num_used); i++) \t\tdx_entry = &entry_list->de_entries[i];  over de_num_used entries with no bounds check.  entry_list is either dx_leaf->dl_list (from ocfs2_read_dx_leaf) or, for an inline root, dx_root->dr_entries.  A crafted on-disk image can set de_num_used (and de_count, which is the __counted_by_le() bound of de_entries) to 0xffff and make the walk read far past the end of the 4KB metadata block, giving a slab out-of-bounds read reachable from any path lookup, stat() or open() on an indexed directory once the image is mounted.  Commit 775c17386a6f (\"ocfs2: validate dx_root extent list fields during block read\") already bounds dr_list for the non-inline dx_root, but left the inline dr_entries path and the dx_leaf dl_list unchecked.  Add the same read-time validation for both entry lists: de_count must equal the capacity of the block (ocfs2_dx_entries_per_leaf()/per_root()) and de_num_used must not exceed de_count, rejecting corrupted metadata with -EFSCORRUPTED before ocfs2_dx_dir_search() can walk an out-of-range entry array.  de_count is always written as exactly the block capacity when a leaf or inline root is formatted, so the equality check does not reject any valid image.  Found by 0sec automated security-research tooling (https://0sec.ai).",
                        "cve_priority": "high",
                        "cve_public_date": "2026-09-11 20:19:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-89553",
                        "url": "https://ubuntu.com/security/CVE-2026-89553",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  nouveau/gem: reserve the bo in the info ioctl around the vma lookup  In the non-uvmm path, there could be a race between the info lookup finding the vma, and the gem close path closing the vma leading to a use-after-free.  Spotted with the help of Opus 4.6.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-09-11 20:19:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-89625",
                        "url": "https://ubuntu.com/security/CVE-2026-89625",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  HID: sony: fix UAF of ghl_poke_timer / ghl_urb at driver unbind  For GHL (Guitar Hero Live) dongles, sony_probe() arms a periodic timer: ghl_magic_poke() (the timer callback) submits sc->ghl_urb, and the URB completion ghl_magic_poke_cb() re-arms the timer with mod_timer().  sony_remove() drained the timer with timer_delete_sync() and then freed the URB with usb_free_urb():  \ttimer_delete_sync(&sc->ghl_poke_timer); \tusb_free_urb(sc->ghl_urb);  timer_delete_sync() does not block re-arming, and while the URB is in flight the timer is not pending, so the sync delete is a no-op. A URB completion that runs after the delete re-arms the timer, and usb_free_urb() only drops a reference -- it does not kill an in-flight URB. sc is allocated with devm_kzalloc() and freed once sony_remove() returns, so the re-armed ghl_poke_timer (embedded in sc) then fires on freed memory, a use-after-free from timer softirq. This is a disconnect/rmmod race.  Poison the URB first, then shut the timer down, before freeing the URB. usb_poison_urb() kills any in-flight URB and permanently rejects further submissions, so a poke timer that is still pending cannot re-submit the URB from ghl_magic_poke() in the window before timer_shutdown_sync() runs. usb_kill_urb() would not suffice: it only cancels the in-flight URB and leaves it submittable once it returns, so the pending timer could re-submit it and put a fresh URB in flight over the freed sc. timer_shutdown_sync() then drains any last callback and blocks re-arming. The probe error path is unaffected: it is only reached before the timer is armed.  Reproduced under KASAN on next-20260710 via dummy_hcd + raw-gadget emulation of the GHL PS4 dongle (VID 0x1430 / PID 0x07bb): hid-sony binds and arms the poke timer, the poke URB is held in flight, the driver is unbound (freeing sc), then the URB is released. The completion re-arms the timer on the freed sc, and the re-armed timer fires ~8 s later:    BUG: KASAN: slab-use-after-free in ghl_magic_poke+0x98/0xb0   Read of size 8 at addr ffff88810b02fd50 by task swapper/0/0    ghl_magic_poke+0x98/0xb0    call_timer_fn+0x35/0x2b0    __run_timers+0x69c/0x9a0    run_timer_softirq+0x173/0x2a0   Allocated by task 169:  sony_probe   Freed by task 338:      devres_release_group <- hid_device_remove (sony_remove)  Found by 0sec (https://0sec.ai) using automated source analysis.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-09-11 20:19:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-89633",
                        "url": "https://ubuntu.com/security/CVE-2026-89633",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  smb: client: fix OOB read/write from unvalidated DataOffset in coalesce_t2()  coalesce_t2() computes data pointers directly from server-supplied DataOffset fields with no validation against buffer bounds:    data_area_of_tgt = (char *)&pSMBt->hdr.Protocol +                      get_unaligned_le16(&pSMBt->t2_rsp.DataOffset);   data_area_of_src = (char *)&pSMBs->hdr.Protocol +                      get_unaligned_le16(&pSMBs->t2_rsp.DataOffset);   data_area_of_tgt += total_in_tgt;   ...   memcpy(data_area_of_tgt, data_area_of_src, total_in_src);  A small DataOffset can push a pointer below the actual byte area, overwriting header fields; a large one can push it past the buffer end, causing out-of-bounds heap reads (source) or writes (target). The BCC overflow guard does not prevent this: BCC reflects how much data is present, while DataOffset controls where in the buffer it starts.  The \"validate target area\" comment present since the function was first written in 2005 was a placeholder that was never implemented.  Add lower- and upper-bound checks for both data pointers before the memcpy, and before any target header fields are modified.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-09-11 20:19:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-89652",
                        "url": "https://ubuntu.com/security/CVE-2026-89652",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ceph: bound copied dentry name length in NFS export get_name  ceph_get_name() copies the MDS-supplied name into the caller's NAME_MAX-sized buffer with memcpy(name, rinfo->dname, rinfo->dname_len) and then writes name[rinfo->dname_len] = 0, without checking dname_len against NAME_MAX. A malicious or buggy MDS that returns a LOOKUPNAME reply with dname_len > NAME_MAX overflows the buffer. __get_snap_name() copies rde->name / rde->name_len the same unchecked way.  Impact: a malicious or compromised Ceph MDS overflows the NAME_MAX name buffer in a client's NFS-export get_name path, a slab out-of-bounds write reported by KASAN. Reachable when a CephFS mount is re-exported over NFS.  Add ceph_export_copy_name(), which rejects lengths above NAME_MAX with -ENAMETOOLONG before the copy, and use it in both ceph_get_name() and __get_snap_name().",
                        "cve_priority": "critical",
                        "cve_public_date": "2026-09-11 20:19:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-89680",
                        "url": "https://ubuntu.com/security/CVE-2026-89680",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  nfsd: fix nfsd_file leak on inter-server COPY setup failure  When nfsd4_setup_inter_ssc() fails, nfsd4_copy() returns nfserr_offload_denied directly, bypassing the out: label where release_copy_files() would drop the nf_dst reference taken by nfs4_preprocess_stateid_op(). Each failed inter-server COPY leaks one nfsd_file, pinning file/inode/dentry/vfsmount.  Fix by setting status and jumping to out: instead of returning directly.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-09-11 20:19:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-89761",
                        "url": "https://ubuntu.com/security/CVE-2026-89761",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  apparmor: fix out-of-bounds write when null terminating a label vec  aa_vec_unique() null terminates at vec[n - dups] when VEC_FLAG_TERMINATE is passed. If the components are all distinct no duplicates are dropped, dups is 0 and the terminator goes to vec[n], so the caller has to provide room for n + 1 entries.  aa_label_strn_parse() sets up its vector with vec_setup(profile, vec, len, gfp) and then calls aa_vec_unique(vec, len, VEC_FLAG_TERMINATE), but vec_setup() does not reserve the terminator entry. Up to LOCAL_VEC_ENTRIES it uses the local array of LOCAL_VEC_ENTRIES pointers, above that it allocates exactly len pointers. The terminator therefore lands one entry past the end of the local array when len is LOCAL_VEC_ENTRIES, and one entry past the end of the allocation when len is larger.  len comes from the number of \"//&\" separated components in the label name and label_count_strn_entries() does not bound it. An unprivileged task reaches the parse by writing to /proc/self/attr/apparmor/current or through lsm_set_self_attr(2), both of which go through do_setattr(), and the name is parsed before the change_profile permission is checked. The query_label() path behind the securityfs .access file, which is mode 0666, performs no permission check at all. Every component has to resolve to a loaded profile, so a system with policy loaded is required.  The other two VEC_FLAG_TERMINATE users work on a label vec that aa_label_alloc() has already sized with \"+ 1 for null terminator entry on vec\". Reserve the same entry in vec_setup() and DEFINE_VEC(). Passing len + 1 from the caller instead would move len == LOCAL_VEC_ENTRIES out of the local array and into kzalloc().",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-09-11 20:20:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-80852",
                        "url": "https://ubuntu.com/security/CVE-2026-80852",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  tls: device: fix out-of-bounds write in tls_append_frag()  Found with syzkaller and a local syzbot instance running on top of a netdevsim TLS offload emulation; tls_device.c is otherwise only reachable on a machine with a NIC that implements the offload.  tls_push_data() only checks whether the open record still has room for another frag at the bottom of its loop, and the MSG_MORE early break skips that check.  The record survives to the next syscall with the frag count it already had, and tls_append_frag() does not check either, so with TLS_TX_ZEROCOPY_RO every splice(SPLICE_F_MORE) of a byte or two adds a non-coalescing pipe page and num_frags walks off the end of tls_record_info.frags[MAX_SKB_FRAGS].  Once the record is pushed, tls_push_record() runs the same index over sg_tx_data[MAX_SKB_FRAGS] and the sg_set_page() writes land on the destruct_work that follows it, which the workqueue then calls.  The byte limit is fine because copy drops to 0 and the loop falls through to the same check; the frag count has no such feedback.  Push the record rather than keep a full one open, which is what a plain TCP socket does - tcp_sendmsg_locked() uses tcp_mark_push() and new_segment in both the copy and the MSG_SPLICE_PAGES paths, and tls_sw already sets full_record when the sk_msg ring fills up, MSG_MORE or not.    BUG: KASAN: slab-out-of-bounds in tls_append_frag ( net/tls/tls_device.c:269)   Write of size 8 at addr ffff8881104d1530 by task tls_oob/450    CPU: 2 UID: 0 PID: 450 Comm: tls_oob Not tainted 7.2.0-rc7+ #329 PREEMPT   Call Trace:    <TASK>    dump_stack_lvl (lib/dump_stack.c:94 lib/dump_stack.c:120)    print_report (mm/kasan/report.c:378 mm/kasan/report.c:482)    kasan_report (mm/kasan/report.c:595)    tls_append_frag (net/tls/tls_device.c:269)    tls_push_data (net/tls/tls_device.c:518)    tls_device_sendmsg (net/tls/tls_device.c:583)    inet_sendmsg (net/ipv4/af_inet.c:865)    sock_sendmsg (net/socket.c:775 net/socket.c:790 net/socket.c:813)    splice_to_socket (fs/splice.c:884)    do_splice (fs/splice.c:936 fs/splice.c:1349)    __do_splice (fs/splice.c:1431)    __x64_sys_splice (fs/splice.c:1634 fs/splice.c:1616)    do_syscall_64 (arch/x86/entry/syscall_64.c:63 arch/x86/entry/syscall_64.c:94)    entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:121)    </TASK>  and, once the record is pushed:    UBSAN: array-index-out-of-bounds in net/tls/tls_device.c:300:24   index 18 is out of range for type 'skb_frag_t [17]'   UBSAN: array-index-out-of-bounds in net/tls/tls_device.c:301:41   index 18 is out of range for type 'scatterlist [17]'   UBSAN: array-index-out-of-bounds in net/tls/tls_device.c:302:39   index 18 is out of range for type 'scatterlist [17]'   UBSAN: array-index-out-of-bounds in net/tls/tls_device.c:307:38   index 26 is out of range for type 'scatterlist [17]'    kernel tried to execute NX-protected page - exploit attempt? (uid: 0)   BUG: unable to handle page fault for address: ffffea000411a680   #PF: supervisor instruction fetch in kernel mode   #PF: error_code(0x0011) - permissions violation   Oops: Oops: 0011 [#1] SMP KASAN PTI   Workqueue: ktls_device_destruct 0xffffea000411a680   RIP: 0010:0xffffea000411a680   Call Trace:    <TASK>    worker_thread (kernel/workqueue.c:3405 kernel/workqueue.c:3486)    kthread (kernel/kthread.c:436)    ret_from_fork (arch/x86/kernel/process.c:158)    ret_from_fork_asm (arch/x86/entry/entry_64.S:245)    </TASK>",
                        "cve_priority": "high",
                        "cve_public_date": "2026-09-04 16:18:00 UTC"
                    }
                ],
                "launchpad_bugs_fixed": [
                    2173211,
                    2173225,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857
                ],
                "changes": [
                    {
                        "cves": [
                            {
                                "cve": "CVE-2026-99115",
                                "url": "https://ubuntu.com/security/CVE-2026-99115",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ksmbd: fill in FileSysIdentifier in FS_POSIX_INFORMATION  smb2_get_info_filesystem() reports 56 bytes for FS_POSIX_INFORMATION, that is the whole of FILE_SYSTEM_POSIX_INFO, but never assigns FileSysIdentifier.  Those eight bytes go to the client as they are found in the response buffer.  The buffer is zeroed on allocation, so a standalone request leaks nothing.  A compound request can leak: the offset of the next response is advanced by the length pinned for the previous one, so a reply that was written into the buffer and then dropped in favour of the short error response of smb2_set_err_rsp() stays there, and the next reply is laid over it with only the header cleared.  Report the file system id statfs() returned, which is what the field is for.  FileSysIdentifier is __le64 and f_fsid is a pair of ints, so assemble the value first, val[0] as the low half, and convert it on the way out.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99113",
                                "url": "https://ubuntu.com/security/CVE-2026-99113",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ksmbd: zero the FS_OBJECT_ID_INFORMATION buffer before filling it in  smb2_get_info_filesystem() reports 64 bytes for FS_OBJECT_ID_INFORMATION, that is the whole of struct object_id_info, but writes only 46 of them:   - objid[] is 16 bytes, and when the volume UUID is not available only    sizeof(stfs.f_fsid) (8) bytes are copied into it;  - extended_info.version_string[] is STRING_LENGTH (28) bytes, and only    strlen(\"1.1.0\") (5) bytes are copied into it.  The response buffer is zeroed on allocation (kvzalloc() in smb2_allocate_rsp_buf()), so for a standalone request the remaining 31 bytes are zero.  In a compound request they need not be.  The offset of the next response is advanced by the length pinned for the previous one, so if a preceding command wrote its reply into the buffer and then failed, smb2_set_err_rsp() pins only the short error response and the next reply lands inside the area that has already been written.  Only the header is cleared there:  \tmemset((char *)rsp_hdr, 0, sizeof(struct smb2_hdr) + 2);  The client then receives up to 31 bytes of a response it was not meant to see, including one that failed with an access denied error.  Clear the structure before filling it in.  As a side effect version_string is now NUL terminated.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99114",
                                "url": "https://ubuntu.com/security/CVE-2026-99114",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ksmbd: initialize FileSystemControlFlags in FS_CONTROL_INFORMATION  smb2_get_info_filesystem() reports 48 bytes for FS_CONTROL_INFORMATION, that is the whole of struct smb2_fs_control_info, but never assigns FileSystemControlFlags.  Those four bytes go to the client as they are found in the response buffer.  The buffer is zeroed on allocation, so a standalone request leaks nothing.  A compound request can leak: the offset of the next response is advanced by the length pinned for the previous one, so a reply that was written into the buffer and then dropped in favour of the short error response of smb2_set_err_rsp() stays there, and the next reply is laid over it with only the header cleared.  ksmbd does not implement quota tracking, so report no control flags.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99132",
                                "url": "https://ubuntu.com/security/CVE-2026-99132",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  xfs: don't hold buffer locks across sync transaction commit in xfs_sync_sb_buf  xfs_sync_sb_buf() holds sb/rtsb buffer locks across a synchronous xfs_trans_commit(), which flushes the CIL push workqueue internally. If shutdown occurs during the CIL push, xfs_buf_item_unpin() needs to lock these buffers to fail them, causing a deadlock:    setlabel:          holds buf lock -> flush_workqueue(xfs-cil)   CIL push worker:   xfs_buf_item_unpin -> xfs_buf_lock(same buf)  Remove the xfs_trans_bhold() calls so that commit releases the buffer locks normally.  After the sync commit, re-acquire the buffers via mp->m_sb_bp / mp->m_rtsb_bp for the on-disk writeback.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99135",
                                "url": "https://ubuntu.com/security/CVE-2026-99135",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  dm-integrity: fix infinite loop on discard with large tag size  When integrity_metadata handles a discard, it fills a buffer with DISCARD_FILLER and writes it over the tags, max_blocks blocks at a time. If the kmalloc fails, the buffer is the on-stack array checksums_onstack and max_size is set to HASH_MAX_DIGESTSIZE. So if the tag size is larger than HASH_MAX_DIGESTSIZE, max_blocks is zero, bi_size is never decremented and the loop never terminates.  Fix this by using sizeof(checksums_onstack) as max_size. The array has MAX_TAG_SIZE bytes since commit b93b6643e9b5 (\"dm integrity: fix a crash with unusually large tag size\"), so max_blocks is at least 1.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99118",
                                "url": "https://ubuntu.com/security/CVE-2026-99118",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  drm/i915/dmc: Harden DMC firmware payload parsing  Validate the conversion of the DMC firmware size from dwords to bytes using check_mul_overflow() before calculating the firmware payload size.  Reject zero-length payloads and zero MMIO counts in the DMC firmware header so malformed firmware is caught early. Also set dmc_fw_size only after the payload allocation succeeds.  (cherry picked from commit efde6601a1f1daedfe3dcc2816c934ddb44e3eef)",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99169",
                                "url": "https://ubuntu.com/security/CVE-2026-99169",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  futex: Fix mm reuse handling for FUT_OFF_MMSHARED  A FUT_OFF_MMSHARED futex is a shared futex that refers to an MM. It is possible for a process to wait on a shared futex with a different MM because a FUT_OFF_INODE waiter can be requeued onto a FUT_OFF_MMSHARED futex by another process. This can cause FUT_OFF_MMSHARED waiters on a freed MM to consume wakeups intended for a newly allocated MM at the same address.  Fix it by keying FUT_OFF_MMSHARED using a unique 64-bit per-MM ID. Leave private futexes as before to avoid influencing the performance of the hotpath.  (Multi-threaded processes typically implicitly use FUT_OFF_MMSHARED by setting clear_child_tid such that it points into anonymous memory, which causes mm_release() in a multi-threaded mm to perform FUTEX_WAKE.)",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99161",
                                "url": "https://ubuntu.com/security/CVE-2026-99161",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  i2c: viai2c-wmt: Fix clock leak in wmt_i2c_probe()  In wmt_i2c_probe(), i2c->clk is acquired using of_clk_get(). If any subsequent operation fails or when the module is unloaded, the clock reference count is never decremented via clk_put(), leading to a resource leak.  Switch to devm_clk_get() so that the clock is automatically managed and released.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99077",
                                "url": "https://ubuntu.com/security/CVE-2026-99077",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ipv4: udp: Create exceptions before socket matching  Currently, when ICMP Fragmentation Needed and Redirect Message packets are locally delivered and quote a UDP packet, a FIB nexthop exception (FNHE) is only created if the kernel can match the UDP packet to an existing socket.  This behavior allows off-path attackers to conduct a side-channel attack on the FNHE cache in order to discover the ephemeral port used by a connected UDP socket.  Commit 6457378fe796 (\"ipv4: use siphash instead of Jenkins in fnhe_hashfun()\") and commit 67d6d681e15b (\"ipv4: make exception cache less predictible\") tried to mitigate such attacks by making it harder for attackers to discover hash collisions in the FNHE cache and by randomizing the number of exceptions a hash bucket can hold, respectively. Unfortunately, both of the mitigations can be bypassed.  Instead, mitigate such attacks by always creating a FNHE, even before trying to find a matching socket. Do that by calling ipv4_update_pmtu() and ipv4_redirect(), the helpers used when the quoted packet did not originate from a socket.  This means that guesses (right or wrong) from an off-path attacker will always result in a FNHE being created or updated in the cache that the attacker can observe.  Pass an oif of 0, in a similar fashion to icmp_err(). This is also the oif used by the socket path for sockets that are not bound to a device.  Note that this does not allow attackers to create FNHEs that they could not create before, as both helpers can already be reached with little to no validation. For example, by sending an ICMP error that quotes an ICMP Echo Reply or one that quotes a UDP source port that matches a wildcard socket.  Also note that in the good case (matched socket) the above scheme comes at the cost of an extra route lookup, as the no socket helpers perform their own lookup before the one performed by ipv4_sk_update_pmtu() / ipv4_sk_redirect(). When the two resolve to different nexthops, it also results in two exceptions being created for the same destination IP. One in the FNHE cache of the nexthop resolved by the no socket helpers and another in the FNHE cache of the nexthop used by the socket.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99123",
                                "url": "https://ubuntu.com/security/CVE-2026-99123",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  vsock/virtio: validate packet source for connected sockets  virtio_transport_recv_pkt() looks up sockets first by the full source and destination tuple, then by destination only in the bound table. The fallback is needed for listening and connecting sockets, but sockets remain in the bound table after connect(), so it can also return a non-listening socket.  The fallback does not validate the source address. In TCP_SYN_SENT, a RESPONSE from an unrelated source can transition the victim socket to TCP_ESTABLISHED while its stored remote address remains unchanged. Subsequent RW packets from that source are delivered through the same destination-only fallback.  This was reproduced with capability-empty processes under different UIDs. The attacker discovered the target tuple through unprivileged AF_VSOCK sock_diag and caused the victim socket to read 16 attacker-chosen bytes; the intended peer-side socket read 0 of those 16 bytes.  Add vsock_check_source() to validate the transport, source port and source CID against the peer stored in a non-listening socket. The local transport is the CID exception because its packets are generated internally with VMADDR_CID_LOCAL as their source, including connections using CID aliases.  Use the helper after lock_sock() in the virtio receive path.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-89987",
                                "url": "https://ubuntu.com/security/CVE-2026-89987",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  mm/huge_memory: transfer the pmd dirty bit to the folio on zap  zap_huge_pmd_folio() propagates the pmd young bit to the folio for the file case, but not the dirty bit.  The pte path does propagate it, in zap_present_folio_ptes() and so does the pmd split path, in __split_huge_pmd_locked().  For most file mappings the omission is harmless, because writing to a shared file mapping goes through page_mkwrite(), which dirties the folio. tmpfs is different: it has no page_mkwrite(), and vma_wants_writenotify() is false for it, so a *read* fault on a MAP_SHARED tmpfs mapping installs a writable pmd via do_read_fault().  do_read_fault() does not call fault_dirty_shared_page(), so subsequent stores through that mapping set only the hardware dirty bit in the pmd and never call folio_mark_dirty(). A shmem folio allocated by a fault is marked uptodate but not dirty (see the clear: block in shmem_get_folio_gfp()), so PG_dirty is never set at all.  Unmapping such a folio - munmap(), or exit_mmap() when the process dies - then loses the only record that it was written, because zap_huge_pmd() drops the pmd without transferring the dirty bit.  Reclaim afterwards sees a clean shmem folio: the whole swap-out block in shrink_folio_list() is inside \"if (folio_test_dirty(folio))\", so pageout() is skipped and the folio falls into __remove_mapping().  There, folio_is_file_lru() is false for a swapbacked folio, so no shadow entry is created and __filemap_remove_folio(folio, NULL) simply empties the i_pages slot.  The data is freed without ever being written to swap, and the next fault on that index returns a freshly zeroed folio.  This is silent data loss for any process that keeps state in a MAP_SHARED tmpfs segment across an unmap - for example a cache handed from one process generation to the next through /dev/shm.  It requires the folio to be PMD-mapped, so it only shows up once shmem THP is enabled (which is what we did in Meta fleet and started noticing crashes); with THP off the pte path transfers the dirty bit correctly.  It also only becomes visible when swap is enabled, because with no swap device shmem folios (which are on the anon LRU) are not scanned by reclaim at all, so the clean folio is never dropped.  Reproduced on x86_64 with a tmpfs mounted huge=within_size: read-fault a 2MB-backed region, write a known pattern through the resulting mapping, munmap, force reclaim of the cgroup, then re-map and read back.  Without this patch the region reads back as zeros and vmstat shows zswpout 0 - the data was discarded rather than swapped.  With this patch the region reads back correctly and the pages are swapped out as expected.  With huge=never, or when the first touch is a write, the test passes either way.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-09-16 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-80572",
                                "url": "https://ubuntu.com/security/CVE-2026-80572",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  Input: byd - synchronize timer deletion before freeing private data  byd_disconnect() uses timer_delete() before freeing the driver's private data.  This does not wait for a running byd_clear_touch() callback, which dereferences the private data and its psmouse pointer.  A callback racing with disconnect can therefore access the private data after it has been freed.  The timer can also still be re-armed by byd_process_byte() while the disconnect is in progress.  Use timer_shutdown_sync() before freeing the private data: it waits for a running callback and turns any later re-arm attempt into a no-op.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-08-26 15:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99180",
                                "url": "https://ubuntu.com/security/CVE-2026-99180",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  unicode: free the map after a grace period  generic_ci_d_hash() and generic_ci_d_compare() read sb->s_encoding and dereference the unicode map while a pathwalk in rcu mode holds nothing but rcu_read_lock(). The filesystems that use them, ext4, f2fs and tmpfs, drop the map with utf8_unload() from ->put_super(), which runs when the last reference to the mount goes away. A lookup that is still inside such a filesystem at that point reads a freed map.  With a pathwalk held up in utf8_casefold_hash() while the last reference to a casefolded tmpfs goes away:    BUG: KASAN: slab-use-after-free in utf8nlookup+0x74c/0x950   Read of size 8 at addr ff110001030fe658 by task walker/98   Call Trace:    <TASK>    utf8nlookup+0x74c/0x950    utf8byte+0x160/0x1560    utf8_casefold_hash+0x167/0x230    generic_ci_d_hash+0xdd/0x1c0    link_path_walk+0x11ad/0x1d30    path_lookupat+0x63/0xb00    filename_lookup+0x1f1/0x5b0    vfs_statx+0xd7/0x3b0   [...]   Allocated by task 94:    __kmalloc_cache_noprof+0x249/0x560    utf8_load+0x4e/0x570    shmem_parse_opt_casefold.isra.0+0x92/0x270   [...]   Freed by task 97:    kfree+0x1db/0x5b0    shmem_put_super+0x72/0x170    generic_shutdown_super+0x14c/0x530    kill_anon_super+0x3a/0x60    deactivate_locked_super+0x9c/0xf0    cleanup_mnt+0x9f/0x130  So far that has been hard to hit. umount(2) waits for a grace period in namespace_unlock() before it drops the mount, so only a mount whose last reference goes away elsewhere, like the close of a file or a chdir out of a lazily unmounted directory, can race a walker. So it is reachable.  Delay the free until a grace period has passed. The map and the data table it holds a reference to then outlive any pathwalk that found the superblock before the mount went away. The reference on the data table module is dropped from the rcu callback as well. utf8-core is built in whenever CONFIG_UNICODE is set, so there is no module exit that would have to wait for the callbacks.  Overlayfs points the s_encoding of an overlay at the map of its first layer without taking a reference of its own. That stays correct. The layer is held by the overlay, so its map is dropped only after the overlay is gone.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99179",
                                "url": "https://ubuntu.com/security/CVE-2026-99179",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  watch_queue: Fix note pool publication race in watch_queue_set_size()  There is a race between watch_queue_set_size() and post_one_notification(). watch_queue_set_size() publishes wqueue->notes, notes_bitmap, nr_pages and nr_notes with plain stores, and post_one_notification() reads them with plain loads under a different lock, so nothing orders the four stores against the poster's loads: depending on the build, notes can be stored last (gcc 14 on x86-64 does this).  Since keyctl_watch_key() lets a watch attach to a queue before it is sized, post_one_notification() can already be running on another CPU at that moment: it reads nr_notes > 0, passes its bounds check, and then reads notes while it is still NULL, dereferencing notes[0].  An unprivileged user triggers this reliably by watching one of its own keys through a notification pipe and racing ioctl(IOC_WATCH_QUEUE_SET_SIZE) on that pipe against keyctl(KEYCTL_SETPERM) on the key from another CPU, triggering:    BUG: kernel NULL pointer dereference, address: 0000000000000000   RIP: 0010:post_one_notification.isra.0+0xa2/0x1e0   Call Trace:    __post_watch_notification+0x148/0x180    keyctl_setperm_key+0x119/0x130    do_syscall_64+0x108/0x4c0    entry_SYSCALL_64_after_hwframe+0x77/0x7f   Kernel panic - not syncing: Fatal exception in interrupt  Fix this by publishing nr_notes last with smp_store_release(), and by reading it once with smp_load_acquire() in post_one_notification() before the bitmap and the page array are touched.  A poster that observes a non-zero nr_notes then also observes the pool behind it; one that observes zero drops the notification as before.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-89912",
                                "url": "https://ubuntu.com/security/CVE-2026-89912",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  KVM: arm64: vgic-its: Don't dereference a NULL collection on ITT save  MAPC with V=0 drops ite->collection but leaves the ITE on the device's ITT list, and vgic_its_save_ite() dereferences it unconditionally. A guest that issues MAPD, MAPTI and then MAPC(V=0) therefore oopses the host when the VMM issues KVM_DEV_ARM_ITS_SAVE_TABLES to migrate it. That sequence is UNPREDICTABLE per the architecture, but KVM already handles the resulting state in the translate, MOVI and DISCARD paths.  Save a zeroed entry, which vgic_its_restore_ite() reads back as invalid. Skipping the ITE instead would leave the ITT slot holding whatever is in guest memory, and restore rejects an entry naming a collection the restored collection table does not have.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-09-16 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99156",
                                "url": "https://ubuntu.com/security/CVE-2026-99156",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  scsi: st: Fix use-after-free race between st_remove() and st_open()  st_remove() drops the probe reference on the scsi_tape with kref_put() and only afterwards removes its index from st_index_idr. If that was the last reference, scsi_tape_release() frees the structure while it is still published in the idr.  scsi_tape_get(), called from st_open(), looks up the tape in st_index_idr and takes a reference under st_ref_mutex and st_index_lock. remove_cdevs() does not wait for opens that are already past chrdev_open(), so an open that is blocked on st_ref_mutex while st_remove() holds it can take the mutex as soon as st_remove() drops it, find the freed tpnt in the idr and call kref_get() on it:    BUG: KASAN: slab-use-after-free in st_open   Write of size 4 ...    st_open (drivers/scsi/st.c:254 drivers/scsi/st.c:1291)    chrdev_open   ...   Freed by task ...:    kfree    st_remove (drivers/scsi/st.c:4512)  Remove the index from the idr before dropping the reference, all under st_ref_mutex. A concurrent scsi_tape_get() now either runs first and holds a valid reference that keeps the tape alive, or runs afterwards and finds nothing, so st_open() fails with -ENXIO.  This restores the ordering st_remove() had before the conversion to st_index_idr, where the tape was unpublished from scsi_tapes[] before the final kref_put().",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99112",
                                "url": "https://ubuntu.com/security/CVE-2026-99112",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net/sched: cls_flower: validate mask pointer after nla_next()  fl_set_enc_opt() iterates the key's nested tunnel-option attributes with nla_for_each_attr() while advancing a single mask pointer via nla_next() at the bottom of each loop, so the mask cursor is driven by the number of key attributes rather than by the mask's own attributes.  The nla_ok() added by commit c96adff956191 (\"cls_flower: call nla_ok() before nla_next()\") only validates the mask pointer that was just consumed; the pointer produced by nla_next() is used by the next iteration (fl_set_geneve_opt() and siblings) without any validation.  The mask's nested attributes are validated with NL_VALIDATE_LIBERAL, which merely warns on trailing bytes that do not form a complete attribute.  A mask carrying one valid attribute plus 1-3 residue bytes (or a non-aligned attribute length making msk_depth negative) therefore reaches the next iteration with msk_depth != 0, so neither the !msk_depth check in fl_set_enc_opt() nor the !depth check in the per-type helpers fires.  nla_type() then reads past the mask payload and nla_parse_nested_deprecated() iterates with an nla_len taken from those bytes, reading well beyond the mask attribute (KASAN: slab-out-of-bounds read in __nla_validate_parse from fl_change()).  Validate the advanced mask pointer as well: when the mask is not legitimately exhausted (msk_depth != 0) and the new pointer fails nla_ok(), reject the filter with -EINVAL.  An exactly exhausted mask still skips the check, preserving exact-match behaviour for the remaining key attributes.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99117",
                                "url": "https://ubuntu.com/security/CVE-2026-99117",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net: bridge: mcast: don't truncate the port group walk on teardown  __br_multicast_disable_port_ctx() and br_multicast_del_port() walk port->mglist with hlist_for_each_entry_safe(). However, br_multicast_find_del_pg() can also delete other entries from the same list through br_multicast_fwd_src_remove() or __fwd_del_star_excl().  If such an entry is the iterator's saved next node, hlist_del_init() clears its ->next and terminates the walk early. The reproducer triggers this in both teardown walks, leaving port groups in the bridge mdb with a dangling ->key.port after del_nbp() frees the port:    BUG: KASAN: slab-use-after-free in __mdb_fill_info+0x1191/0x1320    __mdb_fill_info+0x1191/0x1320    br_mdb_dump+0x594/0xe40    rtnl_mdb_dump+0x1cf/0x5d0  Use hlist_del_init_rcu() to unlink the group while preserving ->next. br_multicast_del_pg() and the teardown walks run under br->multicast_lock. The GC worker must acquire the same lock before detaching the group for destruction, so the node remains alive while the walk uses the preserved pointer.  Preserving ->next means a walk can now reach a group that an earlier iteration already deleted as a side effect. That group is off mp->ports, so br_multicast_find_del_pg() would fall through its port scan and hit the trailing WARN_ON(1). Skip such groups at the top of that helper: a port group is put on port->mglist when it is created and only unlinked when it is deleted, so hlist_unhashed() identifies exactly this case.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-74405",
                                "url": "https://ubuntu.com/security/CVE-2026-74405",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  OPP: Fix race between OPP addition and lookup  A race exists between dev_pm_opp_add_dynamic() and dev_pm_opp_find_freq_exact():    CPU0 (add)                          CPU1 (lookup)   -------------------------------     ------------------------------   _opp_add()     mutex_lock()     list_add(&new_opp->node, head)     mutex_unlock()                    _opp_table_find_key()                                         mutex_lock()                                         dev_pm_opp_get(opp)                                           kref_get()                                         mutex_unlock()     kref_init(&new_opp->kref)                                       dev_pm_opp_put()                                         kref_put_mutex()  The newly added OPP is inserted into the list before its kref is initialized. A concurrent lookup can find this OPP and increment its reference count while it is still uninitialized, leading to refcount corruption and a potential premature free.  Fix this by initializing ->kref and ->opp_table before making the OPP visible via list_add(). This ensures any concurrent lookup observes a fully initialized object.  [ Viresh: Updated commit log ]",
                                "cve_priority": "low",
                                "cve_public_date": "2026-08-15 06:22:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-74739",
                                "url": "https://ubuntu.com/security/CVE-2026-74739",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net/sched: cls_u32: skip hash tables in u32_bind_class()  u32_walk() enumerates both struct tc_u_hnode and struct tc_u_knode through the walker callback. u32_bind_class() unconditionally casts the passed fh to tc_u_knode and accesses &n->res, so when fh is actually a tc_u_hnode, which has no tcf_result member, this results in a slab-out-of-bounds read of res->classid in tc_cls_bind_class().  The issue can be reproduced with the following commands:      tc qdisc add dev lo root handle 1: hfsc     tc class add dev lo parent 1: classid 1:1 hfsc sc rate 1000kbit     tc filter add dev lo parent 1:1 protocol ip prio 1 u32 match u32 0 0 flowid 1:1     tc class add dev lo parent 1: classid 1:2 hfsc sc rate 2000kbit  Fix this by skipping hash tables via the TC_U32_KEY(handle) check.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-08-26 15:16:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-64015",
                                "url": "https://ubuntu.com/security/CVE-2026-64015",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  security/keys: fix missed RCU read section on lookup  Nicholas Carlini reports that the keyring code calls assoc_array_find() in find_key_to_update() without holding the RCU read lock, while the assoc_array_gc() code really is designed around removing the node from the tree and then freeing it after an RCU grace-period.  The regular key handling doesn't see this because holding the keyring semaphore hides any lifetime issues, but the persistent key handling uses a different model.  Instead of extending the keyring locking, just do the simple RCU locking that the assoc_array was designed for.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-07-19 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-74672",
                                "url": "https://ubuntu.com/security/CVE-2026-74672",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  mm/vmalloc: acquire init_mm lock on huge vmap to avoid ptdump UAF  Patch series \"mm: fix UAF caused by race between ptdump and vmap pgtable freeing\", v6.  Kernel page table walkers fall into two broad categories - those ranges where no exclusion is required via walk_kernel_page_table_range_lockless() and those where exclusion is required via walk_kernel_page_table_range() or walk_page_range_debug().  The former category is used only by arm64 arch code operating on ranges it both wholly owns and does not concurrently write.  The latter category consists of kernel page table walkers operating on ranges that are wholly owned (but which need exclusion against concurrent writers).  The lock used for exclusion is the mmap lock, and for kernel ranges this is the mmap lock on init_mm.  ptdump is a special case being both the only user of walk_page_range_debug(), and the only case in which it walks ranges it does not own.  This presents a problem, as page tables may be freed under ptdump.  And indeed there is a use-after-free bug in the kernel as a result, which this series addresses.  vmap promotes page tables to huge leaf entries where possible, freeing the lower page table when it does.  It does this with no meaningful locks held against concurrent ptdump walks.  As a result, use-after-free can currently occur.  This series addresses the issue by having the vmap huge promotion logic acquire the mmap read lock while both setting the huge page table entry and freeing the prior leaf page table.  The ptdump code already acquires the mmap write lock, so by doing so we ensure that the ptdump walker only ever observes either the huge page table entry or the existing page table entry, and nothing is freed underneath it.  A mitigation for this issue was already applied for arm64 in commit fa93b45fd397 (\"arm64: Enable vmalloc-huge with ptdump\"), which this series has to deal with carefully.  This mitigation resolves the issue by acquiring the mmap read lock on init_mm on vmap page table free if a ptdump is in progress.  However the fix in this series would cause a deadlock if we were to simply apply it for arm64 without also reverting the change.  This is because vmap may acquire the read lock before ptdump attempts to acquire the write lock, which then gets queued, and rwsem starvation rules mean that the (unacknowledged) nested mmap read lock in the arm64 code would also block, meaning the original read lock is never released and thus deadlock.  This series works around this by #ifndef CONFIG_ARM64'ing the mmap read lock in vmap logic, then partially reverting commit fa93b45fd397 (\"arm64: Enable vmalloc-huge with ptdump\"), keeping the enablement of huge vmap support, and removing the ifdeffery with the partial revert patch.  There are related issues that are also addressed in this series:  * x86 page attribute logic, specifically Change Page Attributes (CPA),   implements a feature whereby huge ranges can be collapsed into huge leaf   entries. This can similarly cause a UAF when done in parallel with a   ptdump walk, so similarly acquire the init_mm mmap lock to avoid this.  * The CPA logic allows concurrent page table manipulation and CPA   collapse, meaning the former risks accessing a page table the latter   frees. Fix this by acquiring mmap write lock on init_mm across the   whole CPA collapse operation and read lock on the page table   manipulation.  * x86 and arm64 permit walks of non-kernel mm's (both allowing efi mm   walks, and in x86's case arbitrary mm's), so we ensure kernel mappings   remain stable by locking the init_mm as well as the mm being walked.  The ordering of patches is established for both strict dependencies (the arm64 partial revert in particular has to be done after the vmap changes) and logical ones (the non-kernel mm fix only makes sense once the vmap/CPA fixes are in place).   This patch (of 3):  Currently there is a nasty ra ---truncated---",
                                "cve_priority": "low",
                                "cve_public_date": "2026-08-22 16:16:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99121",
                                "url": "https://ubuntu.com/security/CVE-2026-99121",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ipv4: avoid divide by zero in fib_rebalance  fib_rebalance() computes the total eligible nexthop weight in one pass and programs upper bounds in a second pass. A concurrent change to ignore_routes_with_linkdown can make the first pass return zero while the second pass sees an eligible nexthop, resulting in division by zero.  If the first pass reports a zero total, set each nexthop upper bound to -1 and skip the division. This matches the IPv6 fix in commit d2c26c2911dd (\"ipv6: avoid divide by zero in rt6_multipath_rebalance\") and preserves the lock-free rebalance path.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99124",
                                "url": "https://ubuntu.com/security/CVE-2026-99124",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  s390/pci: Fix leak of uninitialized kernel data in SCLP report  While report_error_write() checks that the provided buffer is at least as large as the header struct, but not that it is large enough to contain the report with the length claimed by report->length. If user-space provides a short buffer, meaning a larger report->length than the actually written payload, up to around 4K of kernel data from past the kmalloc(len + 1) sized buffer allocated in kernfs_fop_write_iter() will leak into the SCLP report.  However, as the entity processing the SCLP is privileged and able to access at least the page including the report, this does not leak data that entity could not access but it is still an out of bounds read and a malformed error report that should be rejected.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99126",
                                "url": "https://ubuntu.com/security/CVE-2026-99126",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  s390/ctcm: Prevent XID null dereference  The mpc_validate_xid() function sets grp->saved_xid2->xid2_flag2 to 0x40 to signal XID validation error. If peer XID is NULL or r/w channel pairing mismatch happens, grp->saved_xid2 is never initialized. An attempt to set the flag in such case leads to NULL dereference.  Fix this by using the always available priv->xid->xid2_flag2 instead of grp->saved_xid2->xid2_flag2 for validation errors.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99127",
                                "url": "https://ubuntu.com/security/CVE-2026-99127",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  page_pool: keep frag_offset aligned for odd-sized requests  page_pool_alloc_frag_netmem() rounds the requested fragment size with  \tsize = ALIGN(size, dma_get_cache_alignment());  dma_get_cache_alignment() returns 1 unless the architecture defines ARCH_DMA_MINALIGN, which DMA-coherent architectures such as x86 do not. There the ALIGN() is a no-op and pool->frag_offset advances by the raw, unrounded size.  A single caller asking for an odd size then leaves frag_offset misaligned for every fragment carved out of that page afterwards.  The pool is shared, so the damage is not confined to the caller that caused it.  The per-cpu system_page_pool used by generic XDP hits this. skb_pp_cow_data() allocates its fragments with the raw packet length:  \tsize = min_t(u32, len, PAGE_SIZE); \ttruesize = size; \tpage = page_pool_dev_alloc(pool, &page_off, &truesize);  leaving frag_offset odd for whatever is carved out of that page next.  Its own head allocation is already aligned -- SKB_HEAD_ALIGN(size) plus the XDP_PACKET_HEADROOM its callers pass -- so it is a later user of the shared pool that pays: page_pool_dev_alloc_va() returns a misaligned buffer, napi_build_skb() installs it as skb->head, and skb_shinfo(skb) == skb->head + skb->end is misaligned with it.  skb_shinfo()->dataref is a 4-byte atomic_t at offset 0x20, so the atomic_inc() in __skb_clone() straddles a cache line.  On x86 with split lock detection -- fatal for kernel split locks by default -- this panics the machine:    Oops: Split lock detected   RIP: 0010:skb_clone+0x154/0x1e0   Call Trace:    <IRQ>    raw_local_deliver+0x1ed/0x2c0    ip_protocol_deliver_rcu+0x54/0x1c0    ip_local_deliver_finish+0x85/0x100    ip_local_deliver+0x67/0x100    __netif_receive_skb_one_core+0x85/0xa0    process_backlog+0x87/0x130  Reproduced by attaching any generic-mode XDP program to loopback and opening a RAW IPPROTO_UDP socket, which makes raw_local_deliver() clone every locally delivered UDP packet; ordinary DNS traffic then triggers it, roughly once per 2500 clones.  Observed on 6.12.101 and 7.1.8.  Tracing page_pool_alloc_frag_netmem() over one such run shows the amplification -- two odd-sized requests, nine misaligned offsets:    requested size & 7:   0: 17035    5: 1    7: 1   frag_offset & 7:      0: 17028    3: 1    4: 1    5: 1    6: 1    7: 5  and skb_pp_cow_data() returning heads that were aligned on entry:    head 0xffff8f4c86aeac00 -> 0xffff8f4c53a9a9c4 (&7=4)   head 0xffff8f4d6a8a42c0 -> 0xffff8f4c4f7b7a45 (&7=5)  Round the fragment size up to at least the alignment struct skb_shared_info requires, so fragments are always suitably aligned for the objects callers build on them.  Architectures needing a larger DMA alignment keep it.  This also makes the remainder computed in page_pool_alloc_netmem(),  \t*size = max_size - *offset;  aligned, since max_size is a power of two -- which fixes the matching misalignment of skb->end.  Verified with a controlled A/B under QEMU/KVM: same tree, same config, same compiler, same rootfs and identical traffic, differing only by this patch.  A SEC(\"xdp.frags\") XDP_PASS program on lo plus UDP datagrams larger than max_head_size drives skb_pp_cow_data()'s fragment loop, which passes raw packet lengths to the pool.  Measured at the return of skb_pp_cow_data():                            unpatched   patched   skb_pp_cow_data calls       40800     40800   misaligned skb->head         1120         0   dataref at line offset >60     80         0  The last row counts the accesses that actually fault: skb_shinfo()->dataref sits at head+end+0x20 and is a 4-byte atomic, so `lock incl` splits a 64-byte cache line only when that address lands at offset 61..63.  All 80 occurrences were at offset 61; the panic reported above was at offset 62.  Eliminating the misalignment removes every one of them.  Same class of bug as commit 3bed3cc4156e (\"net: Do not allocate page fragments t ---truncated---",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99128",
                                "url": "https://ubuntu.com/security/CVE-2026-99128",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  sctp: validate chunk length in the inqueue parser  SCTP chunks always include a four-byte generic header, but sctp_inq_pop() currently accepts shorter declared lengths. A zero-length chunk leaves chunk_end at the current header.  When ASCONF is covered by the association's SCTP-AUTH policy, sctp_assoc_bh_rcv() can continue before the state machine performs its normal chunk-length check. sctp_inq_pop() then returns the same malformed chunk repeatedly and the receive softirq can lock up.  A remote SCTP peer can trigger this after establishing an association on a kernel built with CONFIG_IP_SCTP and configured with net.sctp.addip_enable=1 and net.sctp.auth_enable=1. The reproducer did not require application credentials, a shared SCTP AUTH key, or net.sctp.addip_noauth_enable=1.  On commit f967455fb2a5 (\"seg6: reset IP6CB after IPv6 decapsulation\"), one zero-length ASCONF caused repeated watchdog soft-lockup reports in a two-vCPU KVM guest. All 3 pre-trigger health probes succeeded, while 36 of 37 post-trigger probes failed. With this change, all 37 post-trigger probes succeeded and no equivalent soft-lockup signature appeared.  Reject chunks shorter than the generic SCTP header at the shared inqueue parser boundary. Mark the packet for discard before either caller can continue processing it, while preserving the four-byte generic minimum. Declared-length 1 through 4 controls and kernel-generated ASCONF traffic remained healthy. The patched sctp_hello selftest passed for IPv4 and IPv6.  The complete private reproducer and validation evidence are available directly to maintainers on request.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99133",
                                "url": "https://ubuntu.com/security/CVE-2026-99133",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net/iucv: fix the recvmsg window update  iucv_sock_recvmsg() sends the HiperSockets-only AF_IUCV_FLAG_WIN without testing the transport, so on a classic z/VM socket iucv_send_ctrl() sizes the skb through a NULL iucv->hs_dev. SO_MSGLIMIT accepts 1, so msglimit / 2 is zero and one recvmsg() on its own socket is enough for an unprivileged process to take a spurious disconnect.  It also calls iucv_send_ctrl() under spin_lock_bh(&message_q.lock), which allocates GFP_KERNEL inside a section the code treats as atomic. Sending outside that lock lets two recvmsg() reach afiucv_hs_send() at once, where msg_recv is sampled for the advertised window and subtracted after dev_queue_xmit() -- and sendmsg reaches that counter under lock_sock() while recvmsg holds no socket lock, so both can subtract the same value, the counter goes negative and the credit reaches the peer twice.  Test the transport, claim the credit with atomic_xchg() after the last error exit and hand it back if the transmit fails, and send once the lock is dropped.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99136",
                                "url": "https://ubuntu.com/security/CVE-2026-99136",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  dm-crypt: fix a tiny race condition in crypt_dec_pending  crypt_dec_pending reads io->error before calling atomic_dec_and_test. Another context, for example crypt_endio called from an interrupt, may set io->error and drop its reference between the read and the decrement. crypt_dec_pending then drops the last reference and completes the bio with the stale status - so a read that failed and was never decrypted, or a write that failed, is reported as successful.  The read was placed before the decrement by commit b35f8caa0890 (\"dm crypt: wait for endio to complete before destruction\"), because that commit freed dm_crypt_io before calling bio_endio. This is no longer the case, dm_crypt_io lives in the per-bio data now.  Read io->error after atomic_dec_and_test instead. atomic_dec_and_test is fully ordered, so no additional barrier is needed.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99138",
                                "url": "https://ubuntu.com/security/CVE-2026-99138",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  tcp: fix use-after-free in do_tcp_getsockopt(TCP_CC_INFO)  do_tcp_getsockopt() reads icsk->icsk_ca_ops and dereferences the get_info function pointer without rcu_read_lock(). With BPF struct_ops congestion control, ca_ops can point to dynamically allocated memory that is freed concurrently, resulting in a use-after-free when the kernel dereferences or calls through the stale pointer.    BUG: KASAN: slab-use-after-free in do_tcp_getsockopt+0x2037/0x23e0   Read of size 8 at addr ffff888013701258 by task exploit/149    do_tcp_getsockopt+0x2037/0x23e0 (net/ipv4/tcp.c:4564)    tcp_getsockopt+0x91/0xf0    __sys_getsockopt+0xf7/0x170  Fix this by wrapping the ca_ops load and get_info call within rcu_read_lock()/rcu_read_unlock(), and using READ_ONCE() to load the icsk_ca_ops pointer.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99100",
                                "url": "https://ubuntu.com/security/CVE-2026-99100",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: p54: validate firmware record lengths  The p54 firmware parser accesses component ID and component version records without checking that their lengths cover the fields being read. A malformed record can therefore make the parser read past the record.  Validate the component ID and component version record lengths before accessing their data. The descriptor record is also checked against the shortest descriptor length found in the supported firmware images.  Reject descriptor values that underflow the RX offset or produce an empty RX range before updating the driver state.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-28 04:18:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99140",
                                "url": "https://ubuntu.com/security/CVE-2026-99140",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  tracing: Fix hist trigger timestamps for buffered events  Syzkaller triggered a WARN_ON_ONCE(!nest) warning:    WARNING: kernel/trace/ring_buffer.c:821 at ring_buffer_event_time_stamp   Call trace:     ring_buffer_event_time_stamp     hist_field_timestamp     hist_fn_call     event_hist_trigger     event_triggers_call     __event_trigger_test_discard     trace_event_buffer_commit     do_trace_event_raw_event_sched_switch     trace_event_raw_event_sched_switch  The warning is probabilistically reproducible and is related to syzkaller executing the following commands:    echo 'prev_pid == 999999' > events/sched/sched_switch/filter   echo 'hist:keys=common_timestamp' > events/sched/sched_switch/trigger  The specific triggering process is as follows:  CPU 0                                           CPU 1 (context switching)                             (echo 'hist:keys=common_timestamp' > \\                                                        events/sched/sched_switch/trigger) do_trace_event_raw_event_##call   trace_event_buffer_lock_reserve     if (!tr->no_filter_buffering_ref &&         trace_file->flags & EVENT_FILE_FL_FILTERED)         return entry;  // return directly                                                 event_hist_trigger_parse                                                   hist_register_trigger                                                    tracing_set_filter_buffering(file->tr, true);                                                      tr->no_filter_buffering_ref++;     __trace_buffer_lock_reserve       rb_start_commit         local_inc(&cpu_buffer->committing);  // skipped and not executed   trace_event_buffer_commit     __event_trigger_test_discard       event_triggers_call         event_hist_trigger           hist_fn_call             hist_field_timestamp               ring_buffer_event_time_stamp                 nest = local_read(&cpu_buffer->committing);                 WARN_ON_ONCE(!nest)  // trigger warning  The root cause is that when an event file has a filter attached and the hist trigger has not yet been attached, trace_event_buffer_lock_reserve() writes the event into the per-CPU trace_buffered_event temp buffer instead of reserving it in the ring buffer, so cpu_buffer->committing is not incremented. When the event is later processed at commit time by a hist trigger, hist_field_timestamp() -> ring_buffer_event_time_stamp() sees a zero committing count, triggering WARN_ON_ONCE(!nest).  tracing_event_time_stamp() was added by commit d8279bfc5e959 (\"tracing: Add tracing_event_time_stamp() API\") for exactly this case: if the event is the per-CPU trace_buffered_event, it returns the current ring buffer timestamp. But it never gained a caller. Use it in hist_field_timestamp(), so that a hist trigger that races onto a buffered event records the current time, which is only marginally later than when the event was recorded, instead of warning and recording a bogus timestamp.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99150",
                                "url": "https://ubuntu.com/security/CVE-2026-99150",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  drm/amdgpu: don't drop the runtime PM reference twice in amdgpu_gpr  amdgpu_debugfs_gpr_read() drops its runtime PM reference right after reading the wave registers. When copying them to userspace fails, it jumps to the err label, which drops the reference a second time. A read into a bad buffer on Navi31 either steals a reference somebody else holds (power/runtime_usage goes from 1 to 0) or underflows the count:    amdgpu 0000:03:00.0: Runtime PM usage count underflow!  The registers are already in the kernel buffer at that point, so finish the hardware access first and copy the buffer with a single copy_to_user() instead of the put_user() loop with its own error path.  (cherry picked from commit 31035bbd74f7c3e10c163db875b8e67f8b50ee6a)",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99152",
                                "url": "https://ubuntu.com/security/CVE-2026-99152",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  scsi: libiscsi: Validate the task named by a management response  __iscsi_complete_pdu() fetches the task for five response types from one place and checks only that the index resolved:        case ISCSI_OP_LOGOUT_RSP:       case ISCSI_OP_LOGIN_RSP:       case ISCSI_OP_TEXT_RSP:       case ISCSI_OP_SCSI_TMFUNC_RSP:       case ISCSI_OP_NOOP_IN:               task = iscsi_itt_to_task(conn, hdr->itt);               if (!task)                       return ISCSI_ERR_BAD_ITT;  iscsi_itt_to_task() bounds the index against cmds_max and looks at nothing else, so a target can name any slot in the pool, including one that has never been used. task->conn is then NULL, and both iscsi_nop_out_rsp() and iscsi_complete_task() dereference it. One unsolicited NOP-In is enough; a Text Response carrying the same ITT crashes in iscsi_complete_task() instead.  Require the task to be in flight and not a SCSI command, the way iscsi_itt_to_ctask() does for the command opcodes.  [    6.298634] Oops: general protection fault, probably for non-canonical address 0xdffffc000000000c: 0000 [#1] SMP KASAN NOPTI [    6.298642] KASAN: null-ptr-deref in range [0x0000000000000060-0x0000000000000067] [    6.298652] CPU: 1 UID: 0 PID: 111 Comm: iscsistart Not tainted 7.2.0-rc5-ISCSI1-gf5098b6bae76 #1 PREEMPT(lazy) [    6.298654] Hardware name: QEMU Ubuntu 24.04 PC v2 (i440FX + PIIX, arch_caps fix, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 [    6.298656] RIP: 0010:iscsi_nop_out_rsp.constprop.0+0x46/0x160 [    6.298691] Code: c1 ea 03 48 83 ec 08 80 3c 02 00 0f 85 f5 00 00 00 48 b8 00 00 00 00 00 fc ff df 48 8b 6b 58 48 8d 7d 60 48 89 fa 48 c1 ea 03 <80> 3c 02 00 0f 85 c0 00 00 00 48 8b 45 60 48 39 c3 74 50 48 b8 00 [    6.298698] RSP: 0018:ffff88806c907be8 EFLAGS: 00010206 [    6.298701] RAX: dffffc0000000000 RBX: ffff888006116800 RCX: 0000000000000020 [    6.298702] RDX: 000000000000000c RSI: ffff88800525d578 RDI: 0000000000000060 [    6.298703] RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000 [    6.298706] R10: 0000000000000020 R11: 0000000000000000 R12: 0000000000000000 [    6.298706] R13: 000000000000002e R14: ffff8880056eb440 R15: ffff888006116800 [    6.298707] FS:  00007fc02d1c2740(0000) GS:ffff8880b29bc000(0000) knlGS:0000000000000000 [    6.298710] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [    6.298711] CR2: 000055fe3b56ddf8 CR3: 00000000053b9004 CR4: 0000000000770ef0 [    6.298712] PKRU: 55555554 [    6.298713] Call Trace: [    6.298714]  <IRQ> [    6.298714]  __iscsi_complete_pdu+0x13a8/0x22a0 [    6.298758]  iscsi_complete_pdu+0x54/0xa0 [    6.298759]  iscsi_tcp_hdr_recv_done+0x870/0x2c80 [    6.298778]  iscsi_tcp_recv_skb+0x31e/0xec0 [    6.298800]  iscsi_sw_tcp_recv+0x12f/0x390 [    6.298804]  __tcp_read_sock+0x1ab/0x810 [    6.298812]  iscsi_sw_tcp_data_ready+0x18b/0x510 [    6.298814]  tcp_rcv_established+0x1f56/0x3a00 [    6.298842]  tcp_v4_do_rcv+0x449/0x960 [    6.298847]  tcp_v4_rcv+0x2245/0x3bc0",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99153",
                                "url": "https://ubuntu.com/security/CVE-2026-99153",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  scsi: libiscsi: Validate the ITT reflected in a Reject PDU  A Reject PDU carries a copy of the header it rejects, and iscsi_handle_reject() takes the ITT out of that copy to find the task to clean up:        memcpy(&rejected_pdu, data, sizeof(struct iscsi_hdr));       ...       task = iscsi_itt_to_task(conn, rejected_pdu.itt);  That value is whatever the target put there. iscsi_itt_to_task() bounds the index against cmds_max and checks nothing else, so any task in the pool can be named, and iscsi_nop_out_rsp() then completes it.  An index that has never been used gives a NULL task->conn: the pool is zeroed at session setup and conn is assigned only when a task is allocated. If the task was used and returned, iscsi_complete_task() hits its WARN_ON_ONCE(task->state == ISCSI_TASK_FREE) and the refcount underflows. An in-flight SCSI command is completed as successful - a 1 MiB read returned 1048576 with none of its buffer written and no warning.  Validate the reflected ITT the way iscsi_itt_to_ctask() validates a command ITT, and require the task to be in flight and not a SCSI command.  [    6.248477] Oops: general protection fault, probably for non-canonical address 0xdffffc000000000c: 0000 [#1] SMP KASAN NOPTI [    6.249357] KASAN: null-ptr-deref in range [0x0000000000000060-0x0000000000000067] [    6.249951] CPU: 1 UID: 0 PID: 0 Comm: swapper/1 Not tainted 7.2.0-rc5-ISCSI1-gf5098b6bae76 #1 PREEMPT(lazy) [    6.250718] Hardware name: QEMU Ubuntu 24.04 PC v2 (i440FX + PIIX, arch_caps fix, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 [    6.251616] RIP: 0010:iscsi_nop_out_rsp.constprop.0+0x46/0x160 [    6.252043] Code: c1 ea 03 48 83 ec 08 80 3c 02 00 0f 85 f5 00 00 00 48 b8 00 00 00 00 00 fc ff df 48 8b 6b 58 48 8d 7d 60 48 89 fa 48 c1 ea 03 <80> 3c 02 00 0f 85 c0 00 00 00 48 8b 45 60 48 39 c3 74 50 48 b8 00 [    6.252813] RSP: 0018:ffff88806c907b80 EFLAGS: 00010206 [    6.253042] RAX: dffffc0000000000 RBX: ffff88800607e000 RCX: ffffffff8d571a25 [    6.253345] RDX: 000000000000000c RSI: ffff88806c907c38 RDI: 0000000000000060 [    6.253642] RBP: 0000000000000000 R08: 0000000000000000 R09: fffffbfff235a504 [    6.253947] R10: 0000000000000003 R11: 7463656e6e6f6320 R12: 0000000000000000 [    6.254251] R13: 0000000000000000 R14: ffff88806c907c38 R15: 0000000000000000 [    6.254549] FS:  0000000000000000(0000) GS:ffff8880d95bc000(0000) knlGS:0000000000000000 [    6.254887] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [    6.255140] CR2: 00007fc393e8ffc0 CR3: 0000000005252006 CR4: 0000000000770ef0 [    6.255439] PKRU: 55555554 [    6.255564] Call Trace: [    6.255674]  <IRQ> [    6.255768]  __iscsi_complete_pdu+0x18bf/0x22a0 [    6.256733]  iscsi_complete_pdu+0x54/0xa0 [    6.256905]  iscsi_tcp_data_recv_done+0xf4/0x250 [    6.257103]  iscsi_tcp_recv_skb+0x31e/0xec0 [    6.257680]  iscsi_sw_tcp_recv+0x12f/0x390 [    6.258061]  __tcp_read_sock+0x1ab/0x810 [    6.258853]  iscsi_sw_tcp_data_ready+0x18b/0x510 [    6.259808]  tcp_data_queue+0x1f13/0x4cd0 [    6.260567]  tcp_rcv_established+0x8a5/0x3a00 [    6.261931]  tcp_v4_do_rcv+0x449/0x960 [    6.262269]  tcp_v4_rcv+0x2245/0x3bc0",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99154",
                                "url": "https://ubuntu.com/security/CVE-2026-99154",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  scsi: libiscsi: Reject a negative task index from parse_pdu_itt  A transport that implements parse_pdu_itt hands libiscsi an index taken from the PDU, and both lookups bound it from above only:        if (i >= session->cmds_max)  i and cmds_max are both int, so a negative index passes and session->cmds[i] is read from before the array.  be2iscsi produces one. beiscsi_parse_pdu() assigns the raw tag,        *index = (int)itt;  and beiscsi_complete_pdu() forwards an unsolicited NOP-In from the hardware async ring without replacing its ITT, so the value is the target's. It also reports the session's own age rather than the one in the tag, which leaves the age comparison in iscsi_verify_itt() with nothing to reject.  Bound the index from below in both lookups.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99165",
                                "url": "https://ubuntu.com/security/CVE-2026-99165",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  sctp: revalidate output stream after association connect wait  When message interleaving is enabled, the first send waits for association establishment before building its data chunks.  The wait drops the socket lock, and handshake processing can reduce the output stream count to the peer-advertised inbound stream count.  sctp_stream_init() then frees the extension of every removed stream.  The sender resumes with the stream that it checked before the wait.  If the peer removed that stream, sctp_outq_tail() later dereferences its NULL extension.  Fatal-oops policies then panic the host.  KASAN: null-ptr-deref in range [0x38-0x3f] RIP: sctp_outq_tail+0x49e/0xaa0 Call Trace:  sctp_primitive_SEND  sctp_sendmsg_to_asoc  sctp_sendmsg  A range check alone is insufficient.  Stream reconfiguration can grow the output count again while the lock is released without recreating extensions freed by the earlier shrink.  The stream can then be in range while its extension remains NULL.  The send-buffer wait has the same issue.  Factor the range and extension checks into a helper and repeat both after each send-path wait that drops the socket lock.  Once the lock is reacquired, the validation remains stable through data creation and queueing.  If validation fails after the connect wait, the auto-created association is already established.  Return ESRCH so the existing caller path keeps it under state-machine ownership instead of freeing it directly, which would leave protocol, counter and socket state inconsistent.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99166",
                                "url": "https://ubuntu.com/security/CVE-2026-99166",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net: rds: fix uninitialized trans dereference in CM event handler  rds_rdma_cm_event_handler_cmn() assigns trans only when the RDMA device is an InfiniBand CA (RDMA_NODE_IB_CA).  On any other device type, e.g. an iWARP RNIC such as siw, trans stays uninitialized, but the event switch dereferences it: unconditionally in the RDMA_CM_EVENT_CONNECT_REQUEST case via trans->cm_handle_connect(), and (with a connection context) in the ROUTE_RESOLVED and ESTABLISHED cases.  An RDS listener on an iWARP device therefore crashes the kernel as soon as a connect request arrives: with CONFIG_INIT_STACK_ALL_ZERO the wild load becomes a NULL dereference at offset 0xa0 (&trans->cm_handle_connect) in the iw_cm_wq workqueue.  GCC masks the bug in default builds by folding the uninitialized load into &rds_ib_transport; Clang-built kernels take the real uninitialized path and oops.  The active side can land on a non-IB device too: the id that rds_ib_conn_path_connect() creates is not restricted to a node type, so rdma_resolve_addr() binds it to whichever device serves the local address, and an iWARP RNIC on the same netdev qualifies.  The crash there is different: resolving a route on an iWARP id never fills in cm_id->route.path_rec, and the ROUTE_RESOLVED case writes path_rec[0].sl before it calls into the transport.  The iWARP transport was dropped long ago and IB is the only transport left, so make that explicit: initialize trans to &rds_ib_transport at declaration, drop the conditional assignment, reject a connect request that arrives on a non-IB device, and drop a connection whose address resolved to one instead of resolving a route on it.  The rejection is limited to RDMA_CM_EVENT_CONNECT_REQUEST on purpose: a non-zero return from the handler makes rdma_cm destroy the id the event was delivered on, which is right for the request's freshly created id but would free a connection id that RDS still owns for any other event.  On the active side the id stays ic->i_cm_id and the connection's shutdown destroys it, so that case returns 0.  [achender: reject only on RDMA_CM_EVENT_CONNECT_REQUEST instead of  bailing out for every event on a non-IB device, so that rdma_cm does  not destroy connection ids RDS still tracks; drop a connection whose  address resolved to a non-IB device before a route is resolved on it;  changelog adjusted]",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99167",
                                "url": "https://ubuntu.com/security/CVE-2026-99167",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net/sched: fix use-after-free in __tcf_action_put()  __tcf_action_put() decrements the reference count before decrementing the binding count. Another thread can free the action between these operations, causing the binding-count update to access freed memory. KASAN reports it as:    BUG: KASAN: slab-use-after-free in __tcf_action_put+0x327/0x340   Write of size 4 at addr ff11000000d46420 by task tc-put-pause/64  Hold the action IDR mutex across both counter updates and IDR removal, keeping cleanup outside the lock.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99175",
                                "url": "https://ubuntu.com/security/CVE-2026-99175",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  fsnotify: prevent mark additions during connector teardown  fsnotify_destroy_marks() keeps a reference to its current mark while it drops conn->lock to destroy the mark. This stabilizes the forward-walk cursor, but does not prevent a new mark from being inserted before it. For example, an inotify watch re-added after IN_IGNORED sorts before the old, detached mark for the same group. The walk can miss the replacement and then detach the entire connector from the object.  The replacement is still on its group's marks_list and, for inotify, in the watch IDR. The group mutex no longer protects the connector's object from disappearing. An unprivileged fdinfo read racing the final detach can consequently call igrab(NULL):    BUG: KASAN: null-ptr-deref in igrab+0x24/0x100   Write of size 4 at addr 0000000000000148   Call Trace:    igrab+0x24/0x100    inotify_show_fdinfo+0x1dc/0x5e0    seq_show+0x397/0x690  Set a DESTROYING flag under conn->lock before starting the walk, and reject new marks on that connector with -ENOENT. The existing add-mark error paths undo the temporary group-list entry and the backend's watch allocation. Do not wait for teardown while holding the group mutex, which the destroyer needs. Once the old connector is detached, an add can install a fresh connector as before.  This closes the insertion race for all object types using the common connector teardown, without changing the mark reference or SRCU lifetime rules.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99176",
                                "url": "https://ubuntu.com/security/CVE-2026-99176",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  KVM: nVMX: Reset MMU back to the root MMU if loading L2 state fails for !VM-Entry  Reset the vCPU's MMU pointer back to the root MMU if loading L2 state fails in the \"not from VM-Entry\" case, i.e. when emulating RSM or handling KVM_SET_NESTED_STATE.  Failure to unwind the MMU pointer results in KVM trying to run L1 with a nested MMU, and is especially problematic if the vCPU manages to free its nested state before the VM crashes.  Constructing the root for a nested EPT MMU goes through vmcs12, which is dynamically allocated/freed when nVMX is enabled/disabled.  And so if the nested state is freed with the MMU still pointing at the nested MMU, KVM will hit a NULL pointer deref when attempting to get L1=>L2 EPTP.    BUG: kernel NULL pointer dereference, address: 0000000000000078   #PF: supervisor read access in kernel mode   #PF: error_code(0x0000) - not-present page   PGD 114a2d067 P4D 111743067 PUD 11141f067 PMD 0   Oops: Oops: 0000 [#1] SMP   CPU: 20 UID: 1000 PID: 1272 Comm: nested_tdp_faul Not tainted 7.3.0-rc4-8c89f11d1a99b-sink-vm #1914 PREEMPTLAZY   Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015   RIP: 0010:nested_ept_get_eptp+0xb/0x10 [kvm_intel]   Call Trace:    <TASK>    kvm_mmu_load+0xcd/0x870 [kvm]    kvm_arch_vcpu_ioctl_run+0x18f5/0x1f80 [kvm]    kvm_vcpu_ioctl+0x2c7/0x970 [kvm]    __x64_sys_ioctl+0x90/0xd0    do_syscall_64+0x9c/0x4d0    entry_SYSCALL_64_after_hwframe+0x4b/0x53   RIP: 0033:0x47491b    </TASK>   Modules linked in: kvm_intel kvm irqbypass   CR2: 0000000000000078   ---[ end trace 0000000000000000 ]---   RIP: 0010:nested_ept_get_eptp+0xb/0x10 [kvm_intel]  [sean: write changelog]",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99181",
                                "url": "https://ubuntu.com/security/CVE-2026-99181",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  autofs: ignore notification errors from a replaced pipe  autofs_notify_daemon() takes a reference to the current notification pipe under wq_mutex, then drops the mutex before writing the request. The write can block while the daemon enters catatonic mode and installs a replacement pipe.  If the old pipe's reader is then closed, the delayed write returns -EPIPE and the generic error path enters catatonic mode again. That transition acts on the current superblock state, closes the replacement pipe, and releases the new daemon generation's wait queues.  Only enter catatonic mode when the pipe which failed is still the current pipe. Factor the already-locked transition so the identity check and state change are atomic with respect to another replacement.  This was reproduced on v7.3-rc5-337-gff47652a4b66c in a local QEMU guest. An unprivileged UID 65534 lookup filled the old packet pipe before a normal CATATONIC/SETPIPEFD restart. On the unmodified kernel, the new pipe received HUP and both a pending victim lookup and a later lookup failed with ENOENT in two out of two fresh-mount runs.  With this change, the new pipe remained active, received an intact 304-byte request, and both victim lookups completed in two out of two runs. Normal lookup and restart-without-a-blocked-writer controls passed. No KASAN, oops, refcount, or lock diagnostic was observed. A source reproducer and complete local logs are available privately on request.  The demonstrated impact is limited to denial of a shared autofs service during a legitimate daemon restart. No memory corruption, information leak, privilege escalation, or code execution primitive was observed.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99201",
                                "url": "https://ubuntu.com/security/CVE-2026-99201",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  netlink: avoid hashing the network namespace pointer  The netlink rhashtable key includes a raw struct net pointer and a user-controlled port ID. Both /proc/net/netlink and socket diagnostics expose the table's bucket order. By binding and rebinding chosen NETLINK_USERSOCK port IDs, an unprivileged reader can distinguish equal buckets and recover the low bits of the Jenkins hash. Its 32-bit seed and the limited set of kernel-image slides can then be searched offline to recover the address of init_net.  Use the namespace's unique, non-address net_cookie in the comparison key instead. It is assigned before the per-net initializers run and remains unchanged for the namespace's lifetime. The lookup key and object hash are still built by netlink_compare_arg_init(), keeping lookup, insertion, removal and rehashing consistent while preserving namespace separation. Neither public table walker needs to change.  Reading the socket's namespace cookie in netlink_compare() is safe under RCU, including during namespace teardown. netlink_release() removes the socket from the hash table and defers its final put with call_rcu(). cleanup_net() runs the per-net exit methods and waits for outstanding RCU callbacks with rcu_barrier() before freeing namespace storage.  Unlike ns.ns_id, net_cookie is also available and initialized during setup_net() in older stable kernels, making the change straightforward to backport to v5.15 and later.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99203",
                                "url": "https://ubuntu.com/security/CVE-2026-99203",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  pipe: preserve existing fasync readers on writer setup failure  F_SETFL and FIOASYNC decide whether to invoke ->fasync() before pipe_fasync() takes pipe->mutex. Two enables of one O_RDWR FIFO can therefore both enter the callback.  fasync_helper() allocates before checking for an existing entry. If the first enable installs both entries, a second enable can update the reader entry and then fail the allocation for the writer entry. The error path removes the pre-existing reader entry, clearing FASYNC while the writer entry remains registered. __fput() then skips ->fasync(), so a later pipe notification can dereference the freed file or its f_owner. An unprivileged memory-pressure reproducer triggers a KASAN slab-use-after-free in send_sigio() through this path.  Keep the reader helper's result and undo the registration only if this call added it. The pipe mutex serializes changes to both lists, so a failed new registration still removes its reader, while a failed duplicate preserves the existing registrations and FASYNC. Successful duplicate enables continue to update fa_fd as before.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99204",
                                "url": "https://ubuntu.com/security/CVE-2026-99204",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ocfs2/dlm: Protect the recovery list during debugfs reads  Recovery participant records must remain alive while debug_state_print() walks reco.node_data and formats their fields. The formatter holds dlm->spinlock, but the recovery participant list is protected by dlm_reco_state_lock. In particular, dlm_destroy_recovery_area() detaches the list under dlm_reco_state_lock and frees the detached records after releasing it. A concurrent debugfs open can therefore read freed memory.  Protect the participant traversal and field reads in debug_state_print() with dlm_reco_state_lock, matching the existing list writers. This also serializes the traversal against list_add_tail() during recovery-area initialization. Make the existing lock available to the debug code through dlmcommon.h; the lock remains internal to the OCFS2 DLM module.  Release dlm->spinlock after formatting the other domain state and before acquiring dlm_reco_state_lock, so the debug reader does not nest the two locks. Leave recovery list insertion, detachment and freeing unchanged.  KASAN report as below:      BUG: KASAN: slab-use-after-free in debug_state_open+0x1169/0x12d0     Read of size 4 at addr ffff88810662ef80 by task dlm-state-stres/896      CPU: 1 UID: 0 PID: 896 Comm: dlm-state-stres Not tainted 7.3.0-rc4-next-20260921-pmb-ocfs2-functional-v1+ #1 PREEMPT(lazy)     Hardware name: QEMU Ubuntu 24.04 PC v2 (i440FX + PIIX, arch_caps fix, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014     Call Trace:      <TASK>      dump_stack_lvl+0x93/0xd0      print_report+0xce/0x630      ? debug_state_open+0x1169/0x12d0      ? srso_alias_return_thunk+0x5/0xfbef5      ? __virt_addr_valid+0x20e/0x420      ? debug_state_open+0x1169/0x12d0      kasan_report+0xe0/0x110      ? debug_state_open+0x1169/0x12d0      debug_state_open+0x1169/0x12d0      ? __pfx_debug_state_open+0x10/0x10      full_proxy_open_regular+0x193/0x310      do_dentry_open+0x595/0x12d0      ? __pfx_full_proxy_open_regular+0x10/0x10      vfs_open_consume+0xd1/0x400      ? srso_alias_return_thunk+0x5/0xfbef5      path_openat+0x18d0/0x2020      ? __pfx_path_openat+0x10/0x10      do_file_open+0x21e/0x470      ? __pfx_do_file_open+0x10/0x10      ? _raw_spin_unlock+0x23/0x40      ? srso_alias_return_thunk+0x5/0xfbef5      ? alloc_fd+0x3a6/0x6b0      do_sys_openat2+0xf4/0x1b0      ? __pfx_do_sys_openat2+0x10/0x10      ? srso_alias_return_thunk+0x5/0xfbef5      ? __fput+0x5b5/0xa60      __x64_sys_openat+0x136/0x1e0      ? __pfx___x64_sys_openat+0x10/0x10      do_syscall_64+0x114/0x620      entry_SYSCALL_64_after_hwframe+0x77/0x7f     [Register dump omitted.]      </TASK>      Allocated by task 880:      kasan_save_stack+0x33/0x60      kasan_save_track+0x14/0x30      __kasan_kmalloc+0xaa/0xb0      __kmalloc_cache_noprof+0x28d/0x610      dlm_remaster_locks+0x147/0x1d90      dlm_do_recovery+0xde1/0x1580      dlm_recovery_thread+0x109/0x300      kthread+0x351/0x460      ret_from_fork+0x659/0x940      ret_from_fork_asm+0x1a/0x30      Freed by task 880:      kasan_save_stack+0x33/0x60      kasan_save_track+0x14/0x30      kasan_save_free_info+0x3b/0x60      __kasan_slab_free+0x5f/0x80      kfree+0x308/0x580      dlm_destroy_recovery_area+0x285/0x460      dlm_remaster_locks+0x17c4/0x1d90      dlm_do_recovery+0xde1/0x1580      dlm_recovery_thread+0x109/0x300      kthread+0x351/0x460      ret_from_fork+0x659/0x940      ret_from_fork_asm+0x1a/0x30      The buggy address belongs to the object at ffff88810662ef80      which belongs to the cache kmalloc-32 of size 32     The buggy address is located 0 bytes inside of      freed 32-byte region [ffff88810662ef80, ffff88810662efa0)      [Page and memory-state dumps omitted.]",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99206",
                                "url": "https://ubuntu.com/security/CVE-2026-99206",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  scsi: target: iscsi: Fix race in discovery auth updates  Separate configfs opens can concurrently update the discovery AuthMethod parameter. Both callers may free the same value in iscsi_update_param_value(), causing a double-free.  Protect the lookup and replacement with the discovery TPG access lock, as used by the other TPG configfs parameter updates.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99211",
                                "url": "https://ubuntu.com/security/CVE-2026-99211",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  netlink: reset skb headers before unicast and multicast filtering  Socket filters can use SKF_NET_OFF and SKF_LL_OFF to read relative to an skb's network and MAC headers. Netlink producers may reserve headroom without resetting those headers, allowing a receiving socket's filter to read data before the initialized message.  For example, IWPM HELLO replies are allocated with dev_alloc_skb(), which reserves NET_SKB_PAD bytes. An unprivileged NETLINK_RDMA user can attach a classic socket filter and disclose this headroom through the length of the delivered reply. The resets in netlink_dump() do not help because IWPM sends a separately allocated skb through netlink_unicast().  Reset both headers before running the receiver's filter in unicast and broadcast delivery, as is already done for dump skbs. This also covers other netlink producers that reserve headroom without changing their allocation or message-building code.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99212",
                                "url": "https://ubuntu.com/security/CVE-2026-99212",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net/rds: don't let the rdma_cm destroy an id RDS still owns on route failure  rds_rdma_cm_event_handler_cmn() hands the return value of rdma_resolve_route() straight back to the rdma_cm on RDMA_CM_EVENT_ADDR_RESOLVED.  A synchronous failure there - -ENOMEM from the route work allocation, an SA query that cannot be set up, a RoCE route with no usable device - makes addr_handler() destroy the id the event was delivered on.  That id is ic->i_cm_id, and nothing clears the pointer: the connection sits in RDS_CONN_CONNECTING with a freed id until its shutdown calls rdma_disconnect() and rdma_destroy_id() on it.  The ROUTE_RESOLVED case already avoids this: rds_ib_cm_initiate_connect() forces a zero return while ic->i_cm_id == cm_id, as the comment there explains.  Do the same here - drop the connection and return 0 - so the id stays RDS's to destroy from the shutdown, and the reconnect gets a fresh one.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99213",
                                "url": "https://ubuntu.com/security/CVE-2026-99213",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  vsock: treat TCP_CLOSING as once-established  Handle the TCP_ESTABLISHED -> TCP_CLOSING transition on OP_RST, which can race with the connect loop. Immediately break and return 0 on ESTABLISHED/CLOSING. The return value of connect() should reflect what happened up to the point the connection was established or failed. Events that occur afterwards must not affect it. E.g. even if OP_RW has already set sk_err, connect() should still return 0, not ENOBUFS because of it. Adapt the inaccurate comment above signal_pending().  Resetting a socket that is still present in connected_table can lead to memory corruption. The reporter noted lost transports for in-flight skbs, and I have reproduced crashes caused by re-insertion into connected_table.    list_add double add: new=, prev=, next=.   kernel BUG at lib/list_debug.c:35!   Oops: invalid opcode: 0000 [#1] SMP KASAN NOPTI   Workqueue: vsock-loopback vsock_loopback_work   RIP: 0010:__list_add_valid_or_report+0x11f/0x130   Call Trace:    vsock_insert_connected.cold+0xe/0x13    virtio_transport_recv_pkt+0x10e9/0x1460    vsock_loopback_work+0x305/0x480    process_one_work+0xe4c/0x1560    worker_thread+0x4f1/0xd60    kthread+0x36e/0x470    ret_from_fork+0x47b/0x6b0    ret_from_fork_asm+0x1a/0x30  This fix is supplementary to commit 002541ef650b (\"vsock: Ignore signal/timeout on connect() if already established\"). Details under Link.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99216",
                                "url": "https://ubuntu.com/security/CVE-2026-99216",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  Drivers: hv: Don't reset VMBus connection state on error/exit paths  In two places, current code forces vmbus_connection.conn_state to DISCONNECTED prior to calling vmbus_disconnect(). But vmbus_disconnect() calls vmbus_initiate_unload(), which unloads the VMBus connection only if the conn_state is CONNECTED. Consequently, the connection remains and the Hyper-V host might continue to send messages or post VMBus interrupts.  The problem was introduced in commit 74347a99e73ae (\"x86/Hyper-V: Unload vmbus channel in hv panic callback\"), in that vmbus_initiate_unload() started checking the current connection state before doing the unload. This commit removed some occurrences where conn_state was forced to DISCONNECTED, but these two remained, apparently due to an oversight at the time.  Fix this by not forcing conn_state to DISCONNECTED during VMBus exit, or if a failure occurs when establishing the connection in the first place. Whatever value conn_state has at the time is then read by vmbus_initiate_unload() to determine if there is a connection to be unloaded.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2022-50167",
                                "url": "https://ubuntu.com/security/CVE-2022-50167",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  bpf: fix potential 32-bit overflow when accessing ARRAY map element  If BPF array map is bigger than 4GB, element pointer calculation can overflow because both index and elem_size are u32. Fix this everywhere by forcing 64-bit multiplication. Extract this formula into separate small helper and use it consistently in various places.  Speculative-preventing formula utilizing index_mask trick is left as is, but explicit u64 casts are added in both places.",
                                "cve_priority": "high",
                                "cve_public_date": "2025-06-18 11:15:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99082",
                                "url": "https://ubuntu.com/security/CVE-2026-99082",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  KVM: x86: Use active memslots for the per-vCPU MMIO cache  KVM tags the per-vCPU MMIO cache with a memslot generation so that a memslot update invalidates cached MMIO information.  Both the fill and validation paths use kvm_memslots(), which unconditionally selects address space 0, even when the vCPU is running in SMM and using address space 1.  Commit 56f17dd3fbc4 (\"kvm: x86: fix stale mmio cache bug\") added the memslot generation to the cache key so that a memslot update could not leave a stale entry valid.  When commit 699023e23965 (\"KVM: x86: add SMM to the MMU role, support SMRAM address space\") added the SMM address space, these helpers were not converted to use the active memslots.  Consequently, an update to the SMM memslots can leave an entry from the old SMM address space apparently valid after the vCPU returns to the normal address space.  A guest can then cause an access to valid RAM at the same GFN to be returned to userspace as KVM_EXIT_MMIO.  Completing that exit through the VMM's RAM address space writes the backing page without going through KVM's write-tracking path.  If the page backs a nested EPT table, KVM can continue using shadow translations derived from the old contents.  The WARN_ON_ONCE() in kvm_mmu_write_protect_fault() catches this invalid cache and memslot combination.  Use the vCPU's active memslots when caching and validating the entry. Memslot generations are unique across address spaces, so the generation also distinguishes the normal and SMM views.  This matches the MMIO SPTE cache, which already uses kvm_vcpu_memslots().  On an unpatched current-mainline kernel, a regression test that fills the cache in SMM and updates only the SMM memslots fails the intended RAM write and triggers the kvm_mmu_write_protect_fault() warning.  With this change, the same test completes the RAM write without a warning.  The x86/smm_test, set_memory_region_test, and memslot_modification_stress_test selftests also pass.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99083",
                                "url": "https://ubuntu.com/security/CVE-2026-99083",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ksmbd: fix heap out-of-bounds write in krb5_authenticate()  In krb5_authenticate(), out_len is calculated to determine available headroom in response_buf for the incoming Kerberos AP-REP token. However, when SMB2_SESSION_SETUP is processed as a non-first element of a compounded SMB2 request, the calculation omits work->next_smb2_rsp_hdr_off.  This causes out_len to overstate remaining buffer headroom by the cumulative size of prior responses in the compound chain. Consequently, the length check in ksmbd_krb5_authenticate() (*out_len <= resp->spnego_blob_len) passes erroneously, allowing memcpy() to write the AP-REP blob past the end of response_buf into adjacent kernel heap memory.  Fix this by subtracting work->next_smb2_rsp_hdr_off when computing out_len, ensuring it accurately reflects physical remaining buffer space.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98977",
                                "url": "https://ubuntu.com/security/CVE-2026-98977",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  namespace: handle mount locking for automounts correctly  If mounts are propagated across user namespaces, attach_recursive_mnt() locks every copy of the source mount to protect overmounts from vanishing and revealing the underlying files or directories.  The user namespace is taken from the caller's mount namespaces since this is where the mounts end up. Except, that's not always true. Automounts may legitimately get popped in by tasks located in a different mount and user namespace during path lookup.  Then check doesn't make sense at that point. The copy in the namespace of the parent - which may be the host's - is now locked and the host cannot change the flags of its own mounts anymore.  Here's the reproducer:  - host has debugfs mounted nosuid,nodev,noexec and shared - tracefs automount below it is not yet active - hand a child process a directory descriptor on that mount - child process enters auser and mount namespace - child process' namespace now holds a locked copy of the host's debugfs   mount that receives propagation from it - child process stats \"tracing/.\" through the descriptor - lookup runs on the host's mount so the automount lands below the host's mount - propagation puts a copy below the child's copy - both try to clear the flags on the mount they got, with a bind remount:      host, on its own automount:            MS_REMOUNT|MS_BIND = EPERM     child, on the copy in its namespace:   MS_REMOUNT|MS_BIND = 0  So the lock landed on the host's mount instead of the child's copy. Congrats. So we need to compare with the owner of the namespace the mount actually gets mounted on. For all regular cases that is the caller's mount namespace and so nothing changes.  Detached trees in anonymous mount namespaces by be handed over via SCM_RIGHTS or inherited in other ways on purpose so the attaching task's mount namespace is authoritative, not the creator of the detached tree.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98992",
                                "url": "https://ubuntu.com/security/CVE-2026-98992",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  namespace: don't copy an unmounted mount tree  may_copy_tree() accepts a mount whose root is an nsfs or pidfs file before it checks whether that mount is mounted. This exception exists for nsfs and pidfs mounts. They are part of no mount namespace so neither check_mnt() nor is_mounted() would let them through and bind-mounting a nsfsfd or a pidfd wouldn't work.  Problem is that exception also admits a bind mount of such a file when it was lazily unmounted and is only kept alive by a file descriptor:    mount --bind /proc/self/ns/net /tmp/x   exec 3< /tmp/x   umount -l /tmp/x   mount --rbind /proc/self/fd/3 /tmp/y  With MS_REC or AT_RECURSIVE copy_tree() doesn't stop at the unmounted mount. It copies every mount that stayed attached to it as well. So if you have a bunch of overmounts over the nsfsfd or the pidfd the whole unmounted stack is copied. That's a bug.  So refuse to walk an unmounted tree. Copying its root alone stays possible. So a bind mount of a namespace that is gone can still be recreated from a file descriptor on the old one. The file descriptor pins that mount and its root and __has_locked_children() only reads the direct children which don't leave the parent's list without namespace_sem. The internal mounts carry MNT_NS_INTERNAL instead of NULL and are still walked. Copying an unmounted tree recursively fails with EINVAL.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98981",
                                "url": "https://ubuntu.com/security/CVE-2026-98981",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  namespace: unhash a dentry before detaching the mounts on it  unlink(), rmdir() and rename() remove the entry from the filesystem, call detach_mounts() on the entry with the inode locked and then call d_delete() once the inode is unlocked.  The thing is that between detach_mounts() and d_delete() the dentry is still hashed and positive. But after detach_mounts() nothing covers the dentry anymore. A lookup that finds this dentry in the dcache can uncover what the mounts hid.  That's a problem when unlinking files or directories that are mountpoints in other mount namespaces. Everybody who had the underlying entry covered can race the detach_mount() call until d_delete() has run.  The race window isn't all that small. It encompasses namespace_unlock() with a full synchronize_rcu_expedited() grace period and the inode_unlock() of the entry.  In my experiments three walkers that kept trying read an overmounted file in 11938 of the 16140 unlinks that removed its mountpoint from a bind mount of the filesystem within a minute.  Fun fact, d_invalidate() has the same ordering problem but gets it right. It unhashes the dentry first and detaches the mounts afterwards. Let's do the same in __detach_mounts():  - A lookup that hasn't found the dentry yet misses it in the dcache and   waits for the directory lock that the caller holds until the name is   gone for good.  - A lockless lookup that found it already fails the mount_lock check   while the dentry still counts as a mountpoint and the d_seq check once   it doesn't, and retries.  This fixes the lockless path. We still need to fix the reference count lookup in a follow-up patch.  So d_drop() the dentry. The dentry stays positive and held but can't be found anymore. Then proceed with the detach and unlink.  Reproducer:  The reads were counted with the program below, three walkers for 60 s in a VM with 4 CPUs. The race window is stretched with the debug patch pasted here. fs.detach_race_walk_us sleeps in lookup_fast() once it found a mountpoint dentry and before its mounts are crossed. fs.detach_race_unlink_us sleeps in vfs_unlink() between detach_mounts() and d_delete().    // SPDX-License-Identifier: GPL-2.0   /*    * unlink_covered: unlink a file that is a mountpoint in a detached copy of    * its mount, against lookups that open it through that copy.    *    * A is a tmpfs with the file f1 (content SECRET_F) and the plain file    * MARK_A. A' is an open_tree(OPEN_TREE_CLONE) copy of A with MARK_A bound    * on A'/f1, held through an O_PATH fd on its root once the tree fd is    * closed. Walkers open f1 through that fd while the driver unlinks A/f1,    * where nothing is mounted on it. A walker may read MARK_A or get ENOENT.    * A read of SECRET_F is a hit: the name was found after its mount was    * gone. The lockless walks use openat2(RESOLVE_CACHED).    *    * usage: unlink_covered [-t seconds] [-w walkers]    */   #ifndef _GNU_SOURCE   #define _GNU_SOURCE   #endif   #include <errno.h>   #include <fcntl.h>   #include <pthread.h>   #include <stdatomic.h>   #include <stdio.h>   #include <stdlib.h>   #include <string.h>   #include <unistd.h>   #include <sys/mount.h>   #include <sys/stat.h>   #include <sys/syscall.h>   #include <linux/openat2.h>    #ifndef __NR_open_tree   #define __NR_open_tree 428   #endif   #ifndef __NR_move_mount   #define __NR_move_mount 429   #endif   #ifndef __NR_openat2   #define __NR_openat2 437   #endif   #ifndef OPEN_TREE_CLONE   #define OPEN_TREE_CLONE 1   #endif   #ifndef OPEN_TREE_CLOEXEC   #define OPEN_TREE_CLOEXEC O_CLOEXEC   #endif   #ifndef MOVE_MOUNT_F_EMPTY_PATH   #define MOVE_MOUNT_F_EMPTY_PATH 0x00000004   #endif    #define WORK \"/tmp/uc\"   #define ADIR WORK \"/A\"    static int duration = 60, nwalkers = 3;   static atomic_int stop, writer_waiting;   static pthread_rwlock_t cur_lock = PTHREAD_RWLOCK_INITIALIZER;   static int cur_fd = -1;\t\t/* the root of A', -1 wh ---truncated---",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99005",
                                "url": "https://ubuntu.com/security/CVE-2026-99005",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  drm/i915/gt: Unmask interrupts only when ACTIVE is true  There is a small race window between intel_rps_boost() reading a stale ACTIVE state and queuing rps->work, where ACTIVE may be changed via asynchronous calls triggered by wakeref drop. This means that rps_work() could be triggered after the GT has been parked, so unmasking RPS PM interrupts would happen without holding PM wakelock. This sequence of events may be observed during live_rc6_ctx_wa() selftest:  1) live_rc6_ctx_wa()    -> intel_engine_pm_put()       -> wakeref_put()  ASYNC1) wakeref_put() callback           -> __engine_park()              -> intel_gt_pm_put_async()                 -> intel_gt_pm_put_async_untracked()                    -> intel_wakeref_put_async()  ASYNC2) wakeref_put_async() callback           -> __gt_park()              -> intel_rps_park()                 -> intel_rps_clear_active() [clear ACTIVE]                 WITH INTERRUPTS:                 -> rps_disable_interrupts()                    -> cancel_work_sync(rps->work)                    -> rps_reset_interrupts() [rps->pm_iir = 0]                 WITHOUT INTERRUPTS (TIMER mode):                 -> rps_stop_timer()                    -> cancel_work_sync(rps->work)  2) live_rc6_ctx_wa()    -> intel_gt_wait_for_idle()       -> intel_gt_retire_requests_timeout()          -> dma_fence_wait_timeout()             -> ops->wait() [i915_fence_wait()]                -> i915_request_wait_timeout()                   -> intel_rps_boost()                      -> intel_rps_is_active() [check ACTIVE]                         [OPEN RACE WINDOW]                      -> queue_work(rps->work)          -> retire_requests()             -> i915_request_retire()                -> intel_rps_dec_waiters() [from 1 to 0]  If ASYNC1 and ASYNC2 would execute during [OPEN RACE WINDOW], then:  3) rps_work() executes from the workqueue and may satisfy    \"(!pm_iir && !client_boost)\" test (in TIMER mode rps->pm_iir    is zeroed by an earlier rps_work() call or never gets a new    value after previous intel_rps_unpark() event), so it jumps    to \"out\" label, bypassing intel_rps_is_active() guard and    executes gen6_gt_pm_unmask_irq();  4) GT is parked and runtime PM wakelock is dropped, so only    a raw reference in __gt_park() ->    intel_display_power_put_async() remains for 100ms, then the    MMIO write in gen6_gt_pm_unmask_irq() detects missing    wakelock via assert_rpm_wakelock_held() and emits    \"RPM wakelock ref not held during HW access\" tainting kernel.  Commit 3e7abf814193 (\"drm/i915: Extract GT render power state management\") dropped the \"if (rps->interrupts_enabled)\" guard that gen6_pm_rps_work() had around this unmask in i915_irq.c. INTEL_RPS_ACTIVE brackets the same window, since it is set in intel_rps_unpark() before rps_enable_interrupts() and rps_start_timer() and cleared in intel_rps_park() before rps_stop_timer() and rps_disable_interrupts().  Skip unmasking when RPS is no longer active (reaching unmask operation is independent of INTERRUPT mode). This does not prevent RPS operation from resuming on the next unpark. In interrupt mode, intel_rps_unpark() calls rps_enable_interrupts(), which enables and unmasks the PM interrupts. In timer mode, it calls rps_start_timer(), restarting periodic engine-busyness evaluation. The timer generates software RPS events and queues rps_work() directly, independently of PM interrupt delivery. Neither mode requires the late worker to unmask interrupts while the GT is parked  (cherry picked from commit ca4a6deadad15b91ee083afe445fa6bdbfb68206)",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99007",
                                "url": "https://ubuntu.com/security/CVE-2026-99007",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  drm/fb-helper: defer setup when fbdev_probe() fails, not just on -EAGAIN  __drm_fb_helper_initial_config_and_unlock() calls drm_client_modeset_probe() first, which already fills in each mode_set->mode/num_connectors for every connected output, and only afterwards calls drm_fb_helper_single_fb_probe() to create fb_helper->fb and wire it into those mode_sets via drm_setup_crtcs_fb().  If drm_fb_helper_single_fb_probe() fails with anything other than -EAGAIN (e.g. dev->driver->fbdev_probe() itself fails), the function bails out before drm_setup_crtcs_fb() runs and before setting fb_helper->deferred_setup. The client is left with mode_sets that have a mode and connectors but mode_set->fb == NULL, and nothing marks this fb_helper as needing a retry.  __drm_fb_helper_restore_fbdev_mode_unlocked() only skips committing when fb_helper->deferred_setup is set, so a later .restore() call (drm_lastclose() on process exit, in this report) commits the stale mode_set through drm_client_modeset_commit() -> drm_client_modeset_commit_atomic() -> __drm_atomic_helper_set_config(), which hits WARN_ON(!set->fb).  Mark fb_helper->deferred_setup on any drm_fb_helper_single_fb_probe() failure, not just -EAGAIN, so restore keeps skipping the commit until a later hotplug event successfully re-probes and re-populates mode_set->fb. The real error code is still returned to the caller unchanged.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99019",
                                "url": "https://ubuntu.com/security/CVE-2026-99019",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  scsi: ch: Do not keep references to data transfer element devices  ch_readconfig() looks up the scsi_device of every data transfer element whose SCSI id the changer reports in READ ELEMENT STATUS, and stores it in ch->dt[]. scsi_device_lookup() takes a reference, and nothing ever drops it: ch_destroy() frees the array with kfree(). ch->dt[] is read nowhere else - it only supplies the vendor, model and revision printed in the same loop.  Once such a drive is removed, its scsi_device can never be released. It stays on the host's device list at its address, so a new device there is refused by anything that walks the list - target_core_pscsi reports \"scsi_device_get() failed for H:C:T:L\" - and the low-level driver's module can no longer be unloaded. Only a reboot recovers.  It shows with any changer that reports its drives' ids; with the mhvtl virtual library (IBM 3573-TL personality), each create and remove of a library with four drives leaves four references behind, counted by the module's use count in lsmod. With ch not bound the count is unchanged, and with this patch applied it is unchanged too.  Drop the reference as soon as the name has been printed, and remove the now unused dt[] array. That also removes the array leaked when ch_probe() fails after ch_readconfig().  The same leak was reported with an RFC patch in 2022, which was not merged.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99024",
                                "url": "https://ubuntu.com/security/CVE-2026-99024",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  optee: register TEE devices only once fully initialized  optee_probe() called tee_device_register() on both the client and the supplicant device before the rest of struct optee had been initialized.  tee_device_register() calls cdev_device_add(), which does two things at once: it creates /dev/tee0 and /dev/teepriv0, and it links the device into the tee class so that class_find_device() can find it. From that moment on the device is reachable both from user space via tee_open() and from kernel space via tee_client_open_context(). The only gate in teedev_open() is tee_device_get(), which merely checks that teedev->desc is non-NULL, which was already set by tee_device_alloc(). Therefore, there is effectively no gate at all.  A context opened in that window can run against a struct optee where    - optee->call_queue.mutex is not initialized by optee_cq_init()   - optee->supp mutex and completions is not initialized by     optee_supp_init()   - optee->rpmb_dev_mutex is not initialized yet,   - the message argument cache is not initialized by     optee_shm_arg_cache_init()   - optee->ctx is still NULL  Any open session or invoke during this window takes uninitialized mutexes and dereferences a NULL pointer.  Fix it by moving both tee_device_register() calls down to the point where all of struct optee is set up.  [JW: adding fixes and cc]",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99036",
                                "url": "https://ubuntu.com/security/CVE-2026-99036",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  dm: fix reading free memory in do_resume  When do_resume calls dm_table_get_mode(new_map), the call is done without holding any locks (it only holds a reference to the md). It may be possible that another concurrent ioctl on the same device will swap table after dm_swap_table and before dm_table_get_mode. In this case, dm_table_get_mode(new_map) reads freed memory.  This race condition was triggered by syzbot.  This commit fixes the race by reading mode of the new table before dm_swap_table. Note that new_map is also passed to dm_ima_need_measure, but this function doesn't attempt to dereference it, so this call should be safe.  Note that this is not a security bug because only root can trigger it and the commonly used tools such as lvm or cryptsetup do not call the ioctls concurrently, so that they can't trigger it acceidentally.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98985",
                                "url": "https://ubuntu.com/security/CVE-2026-98985",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  namespace: check the mounts before reading their parents in pivot_root()  path_pivot_root() reads the parents of new_root and of the caller's root and checks whether they are shared before it checks that either mount is in the caller's mount namespace. Only namespace_sem is held. That's fine for a mount that is in the caller's mount namespace.  But new_root can be a file descriptor to a mount that has been unmounted and that only the file descriptor keeps alive. If that mount stayed attached to its parent when it was unmounted nothing pins the parent for it. The final mntput() of the parent unhooks the children under mount_lock alone and frees the parent afterwards:    pivot_root()                     close(fd), last ref on the parent   ------------                     ---------------------------------   ex_parent = new_mnt->mnt_parent                                    mntput_no_expire_slowpath()                                      __umount_mnt(new_mnt)                                    cleanup_mnt()                                      call_rcu()   IS_MNT_SHARED(ex_parent)    BUG: KASAN: slab-use-after-free in path_pivot_root+0xf1a/0x1840   Read of size 4 at addr ffff8881047382f8 by task pivot_widen/157    path_pivot_root+0xf1a/0x1840    __x64_sys_pivot_root+0x165/0x190  The same goes for the caller's root via chroot(). Both outcomes of the check end in EINVAL so nothing but the read itself goes wrong. It's the same thing commit bb4609405752 (\"statmount: read the parent of an unmounted mount under mount_lock\") fixed for statmount().  Check that both mounts are in the caller's namespace before their parents are read. Every path returns EINVAL either way.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98993",
                                "url": "https://ubuntu.com/security/CVE-2026-98993",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  namespace: don't inherit MNT_UMOUNT in clone_mnt()  MNT_UMOUNT gets raised on a mount that umount_tree() or umount_one() has taken out of its namespace. It's never cleared. __detach_mounts() unhooks a mount that carries it instead of unmounting it.  disconnect_mount() lets an unmounted child stay attached only if its parent carries it. propagate_umount() takes it as the sign that a mount is going to be unmounted when it decides what else can be unmounted, where a chain of locked mounts ends and where a for reparenting an overmount.  clone_mnt() copies the flags of the source and only masks MNT_INTERNAL_FLAGS which doesn't include MNT_UMOUNT. A mount that was lazily unmounted but is kept alive by a file descriptor can still be copied when its root is an nsfs or pidfs file because may_copy_tree() accepts those before checking whether the source is mounted at all:    mount --bind /proc/self/ns/net /tmp/x   exec 3< /tmp/x   umount -l /tmp/x   mount --bind /proc/self/fd/3 /tmp/y  The mount on /tmp/y is attached to the caller's namespace with MNT_UMOUNT already set and every copy of it inherits the flag again.  That causes a number of bugs:  - Unlink its mountpoint from a mount namespace where it isn't one.   __detach_mounts() takes it for a mount that was unmounted earlier,   unhooks it from its parent and drops the reference the namespace   holds on it. It stays in the namespace with one reference too few   and as its own parent, so it can't be unmounted through the file   descriptor anymore and the namespace never finds it again. When the   namespace goes away it's leaked and points to a freed struct   mnt_namespace that may_change_propagation() and anon_ns_root() read   on the next propagation change or mount_setattr() through the file   descriptor.  - Make it shared and unmount a peer. trace_transfers() follows the   flag from the peer into it and strips it from its peer group.  - Let a propagated umount reach it. gather_candidates() marks it with   T_UMOUNT_CANDIDATE but never puts it on the candidate list, so the   mark is never cleared and every later propagated umount skips it. If   it's the parent of a locked mount handle_locked() takes it as the   cutoff and commits the locked child that should have stayed and   disconnect_mount() leaves that child attached to it, unmounted under   a mounted parent, which is what disconnect_mount() exists to   prevent. When the namespace goes away umount_tree() visits the child   a second time. And once __detach_mounts() has made it its own parent   reparent() never finds the end of the chain of unmounted parents.  A clone is a new mount that has never been unmounted. Add MNT_UMOUNT to MNT_INTERNAL_FLAGS so clone_mnt() never copies it. And warn when umount_tree() reaches a mount that already has it set.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99002",
                                "url": "https://ubuntu.com/security/CVE-2026-99002",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  drm/vmwgfx: validate pitch coming from userspace  Validate the pitch, alongside the box dimensions before trying to copy data from the underlying surface. Fixes possible out of bounds reads with cursor snooping.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99027",
                                "url": "https://ubuntu.com/security/CVE-2026-99027",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net: team: stop reusing skb after queue override  A nonzero dev_queue_xmit() result does not return ownership of the skb. When an override port's qdisc drops it, the queue override helper used to try another port or the mode transmit op with the freed skb.  Return the handoff decision separately from transmit success. Select only the first override port under RCU and stop after handing it the skb, regardless of the lower transmit result. Keep the existing success and drop accounting.    BUG: KASAN: slab-use-after-free in sk_skb_reason_drop   Write of size 4 by task poc/5040   sk_skb_reason_drop (net/core/skbuff.c:1240)   dev_kfree_skb_any_reason (net/core/dev.c:3470)   ab_transmit (drivers/net/team/team_mode_activebackup.c:49)   team_xmit (drivers/net/team/team_core.c:1849)   __dev_direct_xmit (net/core/dev.c:4934)   Freed by task 5040:   __tcf_kfree_skb_list (net/sched/sch_generic.c:43)   __dev_queue_xmit (net/core/dev.c:4831)   team_xmit (drivers/net/team/team_core.c:1846)   Kernel panic - not syncing: KASAN: panic_on_warn set ...",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-64190",
                                "url": "https://ubuntu.com/security/CVE-2026-64190",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net: team: fix NULL pointer dereference in team_xmit during mode change  __team_change_mode() clears team->ops with memset() before restoring safe dummy handlers via team_adjust_ops(). A concurrent team_xmit() running under RCU on another CPU can read team->ops.transmit during this window and call a NULL function pointer, crashing the kernel.  The race requires a mode change (CAP_NET_ADMIN) concurrent with transmit on the team device.   BUG: kernel NULL pointer dereference, address: 0000000000000000  Oops: 0010 [#1] SMP KASAN NOPTI  RIP: 0010:0x0  Call Trace:   team_xmit (drivers/net/team/team_core.c:1853)   dev_hard_start_xmit (net/core/dev.c:3904)   __dev_queue_xmit (net/core/dev.c:4871)   packet_sendmsg (net/packet/af_packet.c:3109)   __sys_sendto (net/socket.c:2265)  The original code assumed that no ports means no traffic, so mode changes could freely memset()/memcpy() the ops.  AF_PACKET with forced carrier breaks that assumption.  Prevent the race instead of making it safe: replace memset()/memcpy() with per-field updates that never touch transmit or receive.  Those two handlers are managed solely by team_adjust_ops(), which already installs dummies when tx_en_port_count == 0 (always true during mode change since no ports are present).  WRITE_ONCE/READ_ONCE prevent store/load tearing on the handler pointers.  synchronize_net() before exit_op() drains in-flight readers that may still reference old mode state from before port removal switched the handlers to dummies.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-07-20 17:18:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99041",
                                "url": "https://ubuntu.com/security/CVE-2026-99041",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ip6_gre: remove obsolete ERSPAN PMTU update  A tc tunnel_key action can attach a METADATA_IP_TUNNEL dst to an skb, and mirred can redirect it to a native ip6erspan device. The legacy PMTU update in ip6erspan_tunnel_xmit() treats that metadata dst as a route. Since it has no output device, dst_dev(dst)->mtu dereferences NULL.  On v7.2 with KASAN, an initial UID/GID 65534 process with CapEff 0 used self-created user and network namespaces to trigger:    KASAN: null-ptr-deref   RIP: ip6erspan_tunnel_xmit+0x10fc/0x2cc0   Kernel panic - not syncing: Fatal exception in interrupt  The update is obsolete. Commit fe1a4ca0a2b7 (\"ip6_gre: process toobig in a better way\") changed IPv6 GRE Too Big handling to update the underlay route and removed the equivalent block from __gre6_xmit(). ip6_tnl_xmit() then propagates the underlay PMTU to the overlay route.  Remove the stale ERSPAN copy and its now-unused dst variable. This eliminates the metadata-dst dereference and keeps ERSPAN aligned with IPv6 GRE PMTU handling.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-97935",
                                "url": "https://ubuntu.com/security/CVE-2026-97935",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  tracing: Set the trace clock before registering the histogram trigger  hist_register_trigger() puts the trigger on the global named_triggers list in cmd_ops->init(), and only then sets the trace clock:  \tif (data->cmd_ops->init) { \t\tret = data->cmd_ops->init(data); \t\tif (ret < 0) \t\t\tgoto out; \t}  \tif (hist_data->enable_timestamps) { \t\tret = tracing_set_clock(file->tr, hist_data->attrs->clock); \t\tif (ret) { \t\t\thist_err(tr, HIST_ERR_SET_CLOCK_FAIL, errpos(clock)); \t\t\tgoto out; \t\t}  The clock string is not checked anywhere before that call, so a named trigger using common_timestamp with an unknown clock fails after it has already become findable. event_hist_trigger_parse() then frees it without taking it off the list, and the next lookup by name reads the freed object:   ~# cd /sys/kernel/tracing/events/sched/sched_switch  ~# echo 'hist:name=foo:keys=common_pid:ts=common_timestamp:clock=bogus' > trigger  bash: echo: write error: Invalid argument  ~# echo 'hist:name=foo:keys=common_pid' > trigger    BUG: KASAN: slab-use-after-free in find_named_trigger+0xac/0xc0   Read of size 8 at addr ffff88800915d760 by task init/1    find_named_trigger+0xac/0xc0    hist_register_trigger+0xc1/0x900    event_hist_trigger_parse+0x3146/0x6af0    event_trigger_write+0xce/0x160   Freed by task 63:    kfree+0x154/0x420    trigger_kthread_fn+0xfd/0x160  Set the clock before the trigger is registered, so that nothing which can fail runs after it is published, the way commit 6f86bdeab633 (\"tracing: Fix bad hist from corrupting named_triggers list\") moved the registration below the rest of the setup.  tracing_set_filter_buffering() is reference counted, so the init failure path has to drop the reference that the clock block now takes first.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-09-25 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98944",
                                "url": "https://ubuntu.com/security/CVE-2026-98944",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  HID: steam: Refactor registration  This refactors and simplifies the registration/unregistration flow. Since we now only perform registration when the client isn't opened anymore, the logic for handling that can be removed, and the rest of the function streamlined.  We also remove the previous assumption that we have a serial number to show we're registered, replacing it with a single purpose boolean.  In a previous refactor the code for unregistering a battery if later registration steps failed was accidentally left out. As a result, a lingering power_supply object could get left over after the steam object was torn down. This is also fixed here.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98945",
                                "url": "https://ubuntu.com/security/CVE-2026-98945",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  HID: steam: Rearrange teardown sequence  This fixes a narrow window during the teardown sequence where callbacks could still be scheduled during cleanup that would then have a dangling pointer to the now-freed steam struct.  This also puts work canceling for rumble and mode switch in steam_unregister, as that shouldn't persist while the client hdev is open.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2025-40135",
                                "url": "https://ubuntu.com/security/CVE-2025-40135",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ipv6: use RCU in ip6_xmit()  Use RCU in ip6_xmit() in order to use dst_dev_rcu() to prevent possible UAF.",
                                "cve_priority": "high",
                                "cve_public_date": "2025-11-12 11:15:00 UTC"
                            },
                            {
                                "cve": "CVE-2025-38728",
                                "url": "https://ubuntu.com/security/CVE-2025-38728",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  smb3: fix for slab out of bounds on mount to ksmbd  With KASAN enabled, it is possible to get a slab out of bounds during mount to ksmbd due to missing check in parse_server_interfaces() (see below):   BUG: KASAN: slab-out-of-bounds in  parse_server_interfaces+0x14ee/0x1880 [cifs]  Read of size 4 at addr ffff8881433dba98 by task mount/9827   CPU: 5 UID: 0 PID: 9827 Comm: mount Tainted: G  OE       6.16.0-rc2-kasan #2 PREEMPT(voluntary)  Tainted: [O]=OOT_MODULE, [E]=UNSIGNED_MODULE  Hardware name: Dell Inc. Precision Tower 3620/0MWYPT,  BIOS 2.13.1 06/14/2019  Call Trace:   <TASK>  dump_stack_lvl+0x9f/0xf0  print_report+0xd1/0x670  __virt_addr_valid+0x22c/0x430  ? parse_server_interfaces+0x14ee/0x1880 [cifs]  ? kasan_complete_mode_report_info+0x2a/0x1f0  ? parse_server_interfaces+0x14ee/0x1880 [cifs]    kasan_report+0xd6/0x110    parse_server_interfaces+0x14ee/0x1880 [cifs]    __asan_report_load_n_noabort+0x13/0x20    parse_server_interfaces+0x14ee/0x1880 [cifs]  ? __pfx_parse_server_interfaces+0x10/0x10 [cifs]  ? trace_hardirqs_on+0x51/0x60  SMB3_request_interfaces+0x1ad/0x3f0 [cifs]  ? __pfx_SMB3_request_interfaces+0x10/0x10 [cifs]  ? SMB2_tcon+0x23c/0x15d0 [cifs]  smb3_qfs_tcon+0x173/0x2b0 [cifs]  ? __pfx_smb3_qfs_tcon+0x10/0x10 [cifs]  ? cifs_get_tcon+0x105d/0x2120 [cifs]  ? do_raw_spin_unlock+0x5d/0x200  ? cifs_get_tcon+0x105d/0x2120 [cifs]  ? __pfx_smb3_qfs_tcon+0x10/0x10 [cifs]  cifs_mount_get_tcon+0x369/0xb90 [cifs]  ? dfs_cache_find+0xe7/0x150 [cifs]  dfs_mount_share+0x985/0x2970 [cifs]  ? check_path.constprop.0+0x28/0x50  ? save_trace+0x54/0x370  ? __pfx_dfs_mount_share+0x10/0x10 [cifs]  ? __lock_acquire+0xb82/0x2ba0  ? __kasan_check_write+0x18/0x20  cifs_mount+0xbc/0x9e0 [cifs]  ? __pfx_cifs_mount+0x10/0x10 [cifs]  ? do_raw_spin_unlock+0x5d/0x200  ? cifs_setup_cifs_sb+0x29d/0x810 [cifs]  cifs_smb3_do_mount+0x263/0x1990 [cifs]",
                                "cve_priority": "high",
                                "cve_public_date": "2025-09-04 16:15:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-31678",
                                "url": "https://ubuntu.com/security/CVE-2026-31678",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  openvswitch: defer tunnel netdev_put to RCU release  ovs_netdev_tunnel_destroy() may run after NETDEV_UNREGISTER already detached the device. Dropping the netdev reference in destroy can race with concurrent readers that still observe vport->dev.  Do not release vport->dev in ovs_netdev_tunnel_destroy(). Instead, let vport_netdev_free() drop the reference from the RCU callback, matching the non-tunnel destroy path and avoiding additional synchronization under RTNL.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-04-25 09:16:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99088",
                                "url": "https://ubuntu.com/security/CVE-2026-99088",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net: openvswitch: validate transport header presence in set_ipv6_addr  When executing IPv6 address rewrite actions on IPv6 fragments, set_ipv6_addr() calls update_ipv6_checksum(). If parse_ipv6hdr() processes a non-first IPv6 fragment, it sets key->ip.proto to NEXTHDR_FRAGMENT and returns early without calling skb_set_transport_header().  update_ipv6_checksum() unconditionally evaluates skb_transport_offset() on entry before checking l4_proto.  Because skb->transport_header is uninitialized, this triggers a warning under CONFIG_DEBUG_NET=y although it is completely harmless.  Fix this by returning early in update_ipv6_checksum() if l4_proto is NEXTHDR_FRAGMENT. This avoids reading the uninitialized transport offset for fragments while preserving the debug warning for any other protocol where the transport header is unexpectedly missing.  See the syzbot trace:  !skb_transport_header_was_set(skb) WARNING: ./include/linux/skbuff.h:3075 at skb_transport_header include/linux/skbuff.h:3075 [inline], CPU#1: syz-executor463/5635 WARNING: ./include/linux/skbuff.h:3075 at skb_transport_offset include/linux/skbuff.h:3250 [inline], CPU#1: syz-executor463/5635 WARNING: ./include/linux/skbuff.h:3075 at update_ipv6_checksum net/openvswitch/actions.c:361 [inline], CPU#1: syz-executor463/5635 WARNING: ./include/linux/skbuff.h:3075 at set_ipv6_addr+0x462/0x660 net/openvswitch/actions.c:399, CPU#1: syz-executor463/5635 [...] RIP: 0010:skb_transport_header include/linux/skbuff.h:3075 [inline] RIP: 0010:skb_transport_offset include/linux/skbuff.h:3250 [inline] RIP: 0010:update_ipv6_checksum net/openvswitch/actions.c:361 [inline] RIP: 0010:set_ipv6_addr+0x462/0x660 net/openvswitch/actions.c:399 [...] Call Trace:  <TASK>  set_ipv6 net/openvswitch/actions.c:531 [inline]  do_execute_actions+0x557e/0x8600 net/openvswitch/actions.c:1366  ovs_execute_actions+0xde/0x520 net/openvswitch/actions.c:1592  ovs_packet_cmd_execute+0xb4f/0xf10 net/openvswitch/datapath.c:705  genl_family_rcv_msg_doit+0x233/0x340 net/netlink/genetlink.c:1114  genl_rcv_msg+0x614/0x7a0 net/netlink/genetlink.c:1209  netlink_rcv_skb+0x226/0x4a0 net/netlink/af_netlink.c:2572  genl_rcv+0x28/0x40 net/netlink/genetlink.c:1218  netlink_unicast+0x7bd/0x940 net/netlink/af_netlink.c:1361  netlink_sendmsg+0x813/0xb40 net/netlink/af_netlink.c:1916  sock_sendmsg_nosec+0x14e/0x190 net/socket.c:800",
                                "cve_priority": "negligible",
                                "cve_public_date": "2026-10-26 15:16:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98950",
                                "url": "https://ubuntu.com/security/CVE-2026-98950",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  flow_dissector: avoid u16 truncation of hlen in bpf_flow_dissect()  bpf_flow_dissect() sanitizes the offsets returned by the BPF program with clamp_t(u16, ..., hlen).  If hlen is bigger than 65535, the upper bound is truncated before the comparison. For instance, with hlen == 65536, both nhoff and thoff are forced to zero, even if the program returned sane values.  This is the same class of bug as the one fixed in commit 99bda1ecbd56 (\"flow_dissector: avoid u16 truncation of skb->len when computing thoff\"). That fix does not cover the BPF path, because __skb_flow_dissect() returns early when a BPF flow dissector handles the packet.  struct bpf_flow_keys stores nhoff and thoff as u16, so cap hlen to U16_MAX before clamping.  Found by sashiko while reviewing the commit above.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98955",
                                "url": "https://ubuntu.com/security/CVE-2026-98955",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  flow_dissector: avoid u16 truncation of skb->len when computing thoff  __skb_flow_dissect() computes key_control->thoff using:    key_control->thoff = min_t(u16, nhoff, skb ? skb->len : hlen);  min_t(u16, ...) casts both arguments to u16 before comparing them. Whenever skb->len (or hlen) modulo 65536 is smaller than nhoff, the truncated length wins and thoff is set to a bogus small value, even when the dissection succeeded. For example, an IPv4/TCP frame with skb->len == 65540 and nhoff == 34 gets thoff == 4, so callers such as skb_probe_transport_header() point the transport header inside the Ethernet header.  Such skbs are not exotic: - At the time of commit d0c081b49137 (\"flow_dissector: properly cap   thoff field\"), AF_PACKET with PACKET_VNET_HDR could already build GSO   skbs larger than 64KB (MTU checks are skipped for GSO, and   alloc_skb_with_frags() accepted up to MAX_SKB_FRAGS (17) order-0   pages on top of the linear part). - BIG TCP now makes skbs larger than 64KB common. - The following patch makes tun_get_user() dissect IFF_TAP frames   before eth_type_trans() pulls the Ethernet header, so a GSO frame   carrying a 65522..65535 byte L3 packet will be dissected with   skb->len in [65536, 65549].  Compare as u32 instead. If the resulting offset cannot be represented in the u16 key_control->thoff, cap it to U16_MAX and report the dissection as failed rather than silently returning a wrong transport offset. thoff is still set on failure, as some callers (such as eth_get_headlen()) use it regardless of the return value.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99089",
                                "url": "https://ubuntu.com/security/CVE-2026-99089",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ASoC: samsung: i2s: enable op_clk in probe to balance runtime PM  The probe function puts the device into the runtime PM active state with only the \"iis\" bus clock enabled, but it also sets priv->op_clk to the parent of the RCLK_SRC mux without enabling it. The runtime PM suspend callback disables both clocks, so the first runtime suspend after probe disables op_clk once more than it was enabled.  On Exynos5250 Arndale both clocks resolve to the same EXYNOS_I2S_BUS gate, so this triggers the following warning during boot:   WARNING: drivers/clk/clk.c:1270 at clk_core_disable+0xe4/0x23c, CPU#0: kworker/u8:3/45  i2s_bus already disabled  ...  Workqueue: pm pm_runtime_work  Call trace:   ...   clk_core_disable from clk_disable+0x28/0x34   clk_disable from i2s_runtime_suspend+0x58/0x68 [snd_soc_i2s]   i2s_runtime_suspend [snd_soc_i2s] from genpd_runtime_suspend+0xc4/0x298   genpd_runtime_suspend from __rpm_callback+0x48/0x18c   __rpm_callback from rpm_callback+0x4c/0x50   rpm_callback from rpm_suspend+0xf4/0x718   rpm_suspend from pm_runtime_work+0x9c/0xa0   ...  Fix this by enabling op_clk in probe right after getting it, so the clock state matches the runtime PM active state, and by disabling it in remove.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-26 15:16:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98956",
                                "url": "https://ubuntu.com/security/CVE-2026-98956",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ASoC: adau1372: allow sleepy powerdown GPIOs  gpiod_set_value() emits a WARN when the GPIO provider indicates that it can sleep, as is typical for I2C controlled GPIO expanders. Since the powerdown GPIO is only manipulated in process context, use the _cansleep variant instead. This lets the driver use sleepy GPIOs to power off the chip.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98964",
                                "url": "https://ubuntu.com/security/CVE-2026-98964",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  nvmet: use the local P2P device on metadata allocation failure  nvmet_req_alloc_p2pmem_sgls() assigns req->p2p_dev only after the data and metadata SGL allocations succeed. If the data allocation succeeds but the metadata allocation fails, out_free_sg passes req->p2p_dev to pci_p2pmem_free_sgl() before that assignment has taken place.  Pass the local p2p_dev argument instead, so cleanup uses the same PCI device as the successful data allocation.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98967",
                                "url": "https://ubuntu.com/security/CVE-2026-98967",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  cxgb4/ch_ktls: disable softirqs around tid_list erases  chcr_ktls_cpl_act_open_rpl() inserts into tid_list from the receive path using xa_insert_bh().  The array is shared by the adapter's connections and initialized with XA_FLAGS_LOCK_BH.  However, chcr_ktls_dev_del() and the chcr_ktls_dev_add() error path use xa_erase(), which takes the XArray lock without disabling softirqs.  When cleanup runs with softirqs enabled, a receive softirq for another connection on the same CPU can interrupt the erase and spin on the lock held by the interrupted task.  Use xa_erase_bh() at both sites to match the insertion path.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98969",
                                "url": "https://ubuntu.com/security/CVE-2026-98969",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net/sched: em_text: reject unterminated algo before autoload  This is a follow-up to commit 9c572a83037a (\"net/sched: fix potential stack infoleak in em_text_dump()\"), which zero-initialised the dump-side struct. Sashiko pointed at a pre-existing bug that exposed the change-side input-validation gap open.  em_text_change() casts the raw netlink attribute payload to struct tcf_em_text and passes conf->algo, a 16-byte array with no enforced NUL terminator, to textsearch_prepare().  On the TS_AUTOLOAD retry textsearch_prepare() calls request_module(\"ts_%s\", algo); vsnprintf() walks %s until it finds a NUL, so an algo[] with no NUL reads past the array into the adjacent struct fields and payload and feeds those bytes to the usermode helper command line.  This is an out-of-bounds read and a kernel memory disclosure.  Reject the attribute when no NUL exists within TC_EM_TEXT_ALGOSIZ bytes, matching the check xt_string has had since 3ab720881b6e.  Conditions to recreate the bug: - CAP_NET_ADMIN on the target netns (namespace-local via unshare -Urn   is enough) - install clsact on an interface, then add a basic filter with one text   ematch whose algo[] is 16 bytes with no NUL (e.g. \"A\"*16) and   pattern_len at least 1 - the add fails with -ENOENT and the kernel invokes modprobe with a   module name made of \"ts_\" plus the 16 bytes and the adjacent payload",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98970",
                                "url": "https://ubuntu.com/security/CVE-2026-98970",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  drm/vc4: Free the BO cache size list on teardown  vc4_bo_cache_destroy() purges the cached BOs but never frees the size list, leaking it on every unbind.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98971",
                                "url": "https://ubuntu.com/security/CVE-2026-98971",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  gpio: exar: initialize the ID before registering its cleanup  devm_add_action_or_reset() invokes the cleanup action immediately when registering the action fails.  gpio_exar_probe() currently stores the allocated ID in exar_gpio only after registering the action, so that failure makes exar_devm_ida_free() release ID 0.  If the allocated ID is nonzero, this leaks that ID and can free ID 0 belonging to another device.  Store the ID before registering the cleanup action so both the immediate failure path and normal device teardown release the correct allocation.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98979",
                                "url": "https://ubuntu.com/security/CVE-2026-98979",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  namespace: refuse an automount below a mount that is in no namespace  It's possible to add autmounts even when the parent mount isn't in the mount namespace of the caller. The only requirement we have is that the parent mount namespace must not be NULL, i.e., unmounted.  Problem is that clone_private_mount() has MNT_NS_INTERNAL which makes that trivially true. So that passes the test and attach_recursive_mnt() accepts that as a mount point and funny enough, count_mounts() dereferences MNT_NS_INTERNAL. The problem is it is an error pointer...  So we can reach this in userspace via fanotify. A filesystem mark on the lower filesystem of an overlay reports paths on the layer clone and reading the event hands out a descriptor on it. For example with debugfs as the lower layer it goes kaboom:    openat(evfd, \"tracing\", O_DIRECTORY)    Oops: general protection fault   KASAN: null-ptr-deref in range [0x1d0-0x1d7]   RIP: 0010:count_mounts+0x35/0x200    attach_recursive_mnt    finish_automount  And since that sleeping beauty happens under namespace_sem held for writing every mount operation on the system blocks from then on. Congrats.  Use is_mounted() instead which rejects unmounted and internal mounts alike. The open fails with EINVAL just as it did before clone_private_mount() used MNT_NS_INTERNAL.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98984",
                                "url": "https://ubuntu.com/security/CVE-2026-98984",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  dcache: don't put a mountpoint on a dentry that's being removed  rmdir(), unlink() and rename() call dont_mount() on the victim and then detach_mounts() with the victim's inode locked. do_lock_mount() takes the inode lock of the mountpoint and checks cant_mount() so a mount can't show up after detach_mounts().  But attach_recursive_mnt() makes a second mountpoint for the root of the source mount so that the mounts already located at the destination can be put on top of it. No inode is locked for that one and d_set_mounted() only refuses a dentry that is unlinked. Between detach_mounts() and d_delete() the victim is still hashed:    rmrace: b passed dont_mount() and detach_mounts(), sleeping   T2: move_mount(S, /tmp/plcant/x, BENEATH) = 0 errno 0 ()   T1: rmdir(/tmp/plcant/d/b) = 0 errno 0       109 107 0:61 /d/b//deleted /tmp/plcant/x rw,relatime - tmpfs tmpfs rw       108 109 0:63 / /tmp/plcant/x rw,relatime - tmpfs T rw  A bind mount of the directory that's being removed is moved beneath an existing mount while the rmdir() is located between the two calls. The mount ends up on the removed directory and nothing will ever detach it.  Check cant_mount() in d_set_mounted() as well. dont_mount() raises the flag under d_lock before detach_mounts() runs so either the mountpoint is set first and detach_mounts() finds the mount or the flag is seen and the mount is refused.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98990",
                                "url": "https://ubuntu.com/security/CVE-2026-98990",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  namespace: check a submount for references right before unmounting it  shrink_submounts() and mark_mounts_for_expiry() first collect all the mounts they are allowed to unmount and then unmount them.  Whether a mount is busy is decided by propagate_mount_busy() on the tree. But unmounting the first mount changes the tree that the second one propagates into. propagate_umount() moves a surviving overmount off a copy it unmounts and mounts it where the copy was mounted. If that's where the propagated copy of the second victim is looked up the overmount becomes a candidate of the second umount_tree(). It's childless and so trim_one() commits it without looking at its reference count.  So a synchronous umount pulls out a busy mount that is in use somewhere else and marks it MNT_SYNC_UMOUNT while it has users:    umount2(/tmp/plshrink/p1, 0) = 0 errno 0   cwd is (unreachable)  The same two umounts requested one after the other fail with EBUSY. This needs a mount with MNT_SHRINKABLE, i.e., automounted submounts of NFS, AFS and CIFS or the tracefs mount below debugfs. Bind mounts inherit the flag.  Check each mount right before it is unmounted under the same hold of namespace_sem and mount_lock as the umount itself. Make sure that the algorithm stays linear.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99095",
                                "url": "https://ubuntu.com/security/CVE-2026-99095",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  drm/vc4: drain the hangcheck timer and works on V3D unbind  Nothing stops the hangcheck timer that submitted jobs arm, or the job_done_work that the render-done interrupt queues, at teardown: vc4_irq_disable() cancels only overflow_mem_work, and vc4_gem_destroy() runs from the drm-managed release, after vc4_v3d_unbind() has already uninstalled the V3D interrupt and cleared vc4->v3d. A timer still armed by then reads V3D registers through the NULL vc4->v3d pointer, and the late callbacks run on the vc4_dev embedding them after it has been freed.  Drain them in vc4_v3d_unbind(): shut the timer down and cancel reset_work before the interrupt is taken down, because its vc4_irq_reset() re-enables it, then flush job_done_work so that completions queued at teardown still release their jobs.  This issue was found by an in-house static analysis tool.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-26 15:16:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99006",
                                "url": "https://ubuntu.com/security/CVE-2026-99006",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  drm/i915/gem: Prevent overstepping exec array boundary  It is possible for eb_relocate_parse_slow() to call kvfree() on entries outside the original exec array during following scenario inside eb_relocate_parse_slow():  1) eb_copy_relocations() allocates as many as eb->buffer_count    copies for exec entries; 2) eb_parse() appends up to two VMAs, right after incrementing    eb->buffer_count; 3) cleanup under \"out\" label uses this incremented buffer_count    to release relocation pointers from exec array via kvfree(),    not from VMA array.  To amend this problem, ensure that relocation cleanup uses the original exec object count, excluding the VMAs appended by the command parser.  (cherry picked from commit 2a0158925fb943c7ba8f3216e2734952128defc9)",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99008",
                                "url": "https://ubuntu.com/security/CVE-2026-99008",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  Bluetooth: RFCOMM: Fix NULL tty_dev dereference in rfcomm_dev_shutdown  syzbot hit a NULL pointer dereference in rfcomm_dev_shutdown() when an RFCOMM tty is closed.  rfcomm_dev_add() puts the new device on rfcomm_dev_list first and only then registers the tty device and saves it in dev->tty_dev. If that registration fails, dev->tty_dev is never set at all. The device can be looked up in the meantime, so an open() of /dev/rfcommN gets through rfcomm_tty_install() and attaches to it. When that tty is closed again, rfcomm_dev_shutdown() uses dev->tty_dev without checking it:    Oops: general protection fault, probably for non-canonical address   KASAN: null-ptr-deref in range [0x0000000000000040-0x0000000000000047]   RIP: 0010:rfcomm_dev_shutdown+0x48/0xb0 net/bluetooth/rfcomm/tty.c:131   Call Trace:    tty_port_shutdown+0x1bf/0x220 drivers/tty/tty_port.c:372    tty_port_close+0x4e/0x150 drivers/tty/tty_port.c:705    tty_release+0x359/0x1670 drivers/tty/tty_io.c:1718    __fput+0x418/0xa50 fs/file_table.c:512  rfcomm_dev_destruct() already copes with a NULL dev->tty_dev. Add the same check to rfcomm_dev_shutdown(), so the tty device is only moved when it was actually registered.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99010",
                                "url": "https://ubuntu.com/security/CVE-2026-99010",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  Bluetooth: RFCOMM: free the skb when the DLC has no owner  rfcomm_recv_data() hands the skb to d->data_ready() and returns 0 without freeing it, so the callback owns the skb from that point on. The tty implementation frees it when the DLC has been detached from its device:    static void rfcomm_dev_data_ready(struct rfcomm_dlc *dlc,                                     struct sk_buff *skb)   {           struct rfcomm_dev *dev = dlc->owner;            if (!dev) {                   kfree_skb(skb);                   return;           }  The socket implementation returns without freeing it, and the skb is leaked.  A connected DLC can have no owner: rfcomm_sock_destruct() clears d->owner, while the DLC itself stays on the session until it is closed. Data frames that arrive in that window still find d->state == BT_CONNECTED in rfcomm_recv_data() and are handed to the callback, one leaked skb each.  The leak does not stop on its own either.  The remote runs out of credits only once RFCOMM_RX_THROTTLED is set, and for a socket the only place that sets it is rfcomm_sk_data_ready() itself, below the return. rfcomm_process_dlcs() keeps granting credits, so the remote keeps sending and the leak keeps growing.  Free the skb, as the tty side does.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99015",
                                "url": "https://ubuntu.com/security/CVE-2026-99015",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  Bluetooth: hci_sock: Serialize dead-device detachment  Rebinding an HCI socket after its controller is unregistered can race monitor control replay and crash the kernel. hci_sock_bind() clears hci_pi(sk)->hdev and drops the device reference under only the socket lock, whereas send_monitor_control_replay() holds hci_sk_list.lock for reading.  Replay can observe a non-NULL hdev, then bind can clear it and drop the last reference before create_monitor_ctrl_open() reads hdev->id. This can cause a NULL pointer dereference if the pointer is reloaded, or a use-after-free if the old pointer is retained.  The kernel reported:    KASAN: null-ptr-deref in range [0x0000000000000068-0x000000000000006f]   RIP: 0010:create_monitor_ctrl_open+0x579/0x800   Call Trace:    hci_sock_bind+0xd96/0x1190    __sys_bind+0x166/0x200    __x64_sys_bind+0x6d/0xb0    do_syscall_64+0xdd/0x4a0    entry_SYSCALL_64_after_hwframe+0x77/0x7f  The same missing serialization lets hci_send_to_sock() select a socket for the old device and queue its frame after bind has detached the socket or installed a new binding.  Take hci_sk_list.lock for writing when clearing the device pointer and resetting the socket state. This waits for existing replay and delivery readers to finish before detachment and prevents later readers from using the old binding. Keep hci_dev_put() outside the critical section because the final device release can sleep.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99022",
                                "url": "https://ubuntu.com/security/CVE-2026-99022",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  regulator: ltc3676: don't read the write-only HRST and CLIRQ registers  HRST (0x1e) and CLIRQ (0x1f) are write-only command strobes. Writing HRST triggers a hard reset of the chip and writing CLIRQ clears the interrupt; reading them returns nothing useful, and the read itself fires the command.  The result is that a plain register dump resets the board:    cat /sys/kernel/debug/regmap/2-003c/registers  walks every readable register, hits HRST, and the board reboots.  Split the callback back in two so HRST and CLIRQ stay writable but are no longer readable. The readable range is left unchanged (LTC3676_BUCK1 ... LTC3676_IRQSTAT).",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99025",
                                "url": "https://ubuntu.com/security/CVE-2026-99025",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  openvswitch: fix soft lockup in the netlink flow dump  A production compute node carrying a few thousand datapath flows hit a soft lockup inside a single netlink flow dump and panicked.  ovs_flow_cmd_dump() calls ovs_flow_stats_get() for every flow it emits, and that releases stats->lock with spin_unlock_bh() once per CPU that has touched the flow. Every release is a local_bh_enable(), and each one runs the pending softirq backlog in the dumping thread's own context.  The skb bounds the flows one callback emits, but not the softirq work it absorbs. On a CPU that carries the box's packet load the backlog refills as fast as it drains, so the dumping thread becomes that CPU's softirq engine. It never sleeps and it has no reschedule point, so under voluntary preemption nothing can take the CPU away from it: neither the ksoftirqd the kernel woke to take the work over, nor the stopper thread the softlockup detector dispatches to refresh its timestamp.  Hold BH off across the whole callback instead, the way ctnetlink_dump_table() does, so the nested spin_unlock_bh() stop draining softirqs. The loop already runs under rcu_read_lock() and cannot sleep. What it gives up is preemption under CONFIG_PREEMPT, since a BH-off region is not preemptible outside PREEMPT_RT. The region stays short: the skb caps the flows one callback emits, and empty buckets cost no skb space but are each visited once per dump, as the cursor only moves forward. The table grows on insert and shrinks only on flush, so the walk is bounded by the largest flow count the datapath has held. The softirq backlog the callback used to absorb has no bound at all.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99031",
                                "url": "https://ubuntu.com/security/CVE-2026-99031",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net: bridge: avoid recursive multicast port cleanup  br_multicast_sg_del_exclude_ports() removes automatically added STAR_EXCL port groups by calling br_multicast_del_pg(). For S,G entries, that deletion calls back into br_multicast_sg_del_exclude_ports(), so a large number of STAR_EXCL ports consumes one kernel stack frame per port and can hit the stack guard page.  Keep the complete port-group deletion path for cleanup, but suppress the S,G exclude-port cleanup while that helper is already walking the same entry. Normal deletion callers retain the existing behavior.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99032",
                                "url": "https://ubuntu.com/security/CVE-2026-99032",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net/smc: protect clcsock lifetime in smc_getname  smc_getname() dereferences smc->clcsock without holding clcsock_release_lock. Link-group termination can release the CLC socket through smc_close_active_abort() while the SMC socket is still open, for example after shutdown(SHUT_WR).  A getsockname() caller can load smc->clcsock, then the termination worker can clear the pointer and call sock_release() before the caller accesses clcsock->ops or invokes getname(). This causes a use-after-free; if the worker clears the pointer before the load, it causes a NULL dereference. The syscall's file reference keeps the SMC socket alive but does not prevent asynchronous release of its CLC socket.  KASAN reported the following with test-only timing instrumentation:    BUG: KASAN: slab-use-after-free in smc_getname+0x19e/0x1b0   Read of size 8 at addr ffff888109abb4e0 by task poc/103   Call Trace:    smc_getname+0x19e/0x1b0    do_getsockname+0xe5/0x170    __sys_getsockname+0x8c/0x100    Allocated by task 95:    sock_alloc_inode+0x1e/0x280    sock_alloc+0x3d/0x240    __sock_create+0x7e/0x430    smc_create+0x121/0x240    Freed by task 0:    kmem_cache_free+0xcc/0x340    rcu_core+0x50a/0x1850    Last potentially related work creation:    evict+0x446/0x6c0    smc_clcsock_release+0xa8/0xd0    smc_close_active_abort+0x26a/0x3a0    __smc_lgr_terminate.part.0+0x137/0x2e0  Hold clcsock_release_lock across the pointer check and the getname() callback to serialize with smc_clcsock_release(). Return -EBADF if the CLC socket has already been released, preserving the existing peer state check and the callback's return value otherwise.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99033",
                                "url": "https://ubuntu.com/security/CVE-2026-99033",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net/packet: guard the ll header push in packet_rcv_spkt()  packet_rcv_spkt() restores the link layer header with  \tskb_push(skb, skb->data - skb_mac_header(skb));  That subtraction is only meaningful when the device actually has a link layer header.  packet_rcv() and tpacket_rcv() both wrap it in dev_has_header(), which is also the predicate the block comment at the top of the file states the restore in terms of; packet_rcv_spkt() does not.  commit d549699048b4 (\"net/packet: fix packet receive on L3 devices without visible hard header\") introduced the helper and changed the two call sites, and this one stayed behind.  A device without a visible ll header can leave skb->mac_header at the 0xFFFF sentinel that __alloc_skb() initialises it to.  A CAN skb does: init_can_skb() sets pkt_type and ip_summed but does not reset the headers, and commit 9f10374bb024 (\"can: remove private CAN skb headroom infrastructure\") dropped the skb_reset_*_header() calls that used to be there.  skb_mac_header() is then 0xFFFF, the length becomes a large negative number and skb_push() reports it through skb_under_panic() -- from softirq context, so it is a full system panic even with panic_on_oops=0:    skbuff: skb_under_panic: text:ffffffff8bd21bc1 len:-65455 put:-65471 head:... data:... tail:0x50 end:0x180 dev:can0   kernel BUG at net/core/skbuff.c:214!   RIP: 0010:skb_panic+0x50/0x60   Call Trace:    <IRQ>    skb_push+0x38/0x40    packet_rcv_spkt+0xe1/0x170    __netif_receive_skb_core.constprop.0+0x7e8/0xd30    ...   Kernel panic - not syncing: Fatal exception in interrupt  The socket type is reachable: packet_create() accepts SOCK_PACKET alongside SOCK_RAW and SOCK_DGRAM behind the same CAP_NET_RAW check, and neither the socket length nor a capability check keeps it away from a CAN interface.  The missing skb_reset_*_header() calls in init_can_skb() are a regression in their own right and are being fixed separately, but a packet socket should not turn a link layer that did not initialise its mac header into a kernel panic.  Guard the push the way the other two receive paths do.  Tested on v7.3-rc5 under QEMU with a slcan device on a pty, which is the driver RX path: vcan does not reproduce it, because can_send() resets the headers on the way out.  One SOCK_PACKET socket bound to can0 and one frame written into the line discipline panics an unpatched kernel with the trace above; the same image with this patch prints no panic and powers off normally.  Both kernels are this tree, defconfig plus CONFIG_CAN_SLCAN=y, differing only in this hunk.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99034",
                                "url": "https://ubuntu.com/security/CVE-2026-99034",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  mmc: sdhci-sprd: disable runtime PM on remove  sdhci_sprd_probe() enables runtime PM, while sdhci_sprd_remove() does not perform the corresponding runtime PM cleanup.  The probe failure path disables runtime PM before disabling the clocks, but the normal remove path directly disables clocks that are also managed by the runtime PM callbacks. If the device is runtime suspended, those clocks may already be disabled.  Resume the device before removal, disable runtime PM and drop the temporary runtime PM reference before disabling the clocks.  This issue was found by manual code inspection.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99035",
                                "url": "https://ubuntu.com/security/CVE-2026-99035",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  mmc: mtk-sd: Cancel request timeout work on remove  The driver queues req_timeout while a request is active. msdc_request_done() uses cancel_delayed_work(), which does not wait for a timeout callback that has already started.  The timeout callback calls mmc_request_done(), which wakes the request waiter, and then continues to use host->dev_comp and check the SDIO IRQ. During unbind, msdc_drv_remove() can return and the managed mmc_host can be freed before the callback finishes.  KASAN reported use-after-free accesses in msdc_request_done() and msdc_recheck_sdio_irq() in each of three unbind tests.  The same tests completed without a kernel diagnostic after this change.  Call cancel_delayed_work_sync() after mmc_remove_host() has stopped new requests and before the driver releases the host resources.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99037",
                                "url": "https://ubuntu.com/security/CVE-2026-99037",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  dm-crypt: reject the lmk IV mode with AEAD ciphers  A \"capi:\" table line that pairs an AEAD cipher with the lmk IV mode, for example \"capi:gcm(aes)-lmk\" with the integrity:28:aead option, causes an oops when it is loaded. lmk sets tfms_count to 64, but crypt_alloc_tfms_aead only allocates one transform, so crypt_setkey reads past the end of the tfms_aead array and calls crypto_aead_setkey on the values it finds there.  lmk exists for compatibility with Loop-AES, which uses CBC, so refuse it with an AEAD cipher rather than allocate 64 AEAD transforms. The check cannot go in crypt_iv_lmk_ctr with the other lmk checks, because the IV constructor runs after crypt_set_key.  Note that this is not a security bug because the memory corruption can only be triggered by root.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99038",
                                "url": "https://ubuntu.com/security/CVE-2026-99038",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  memstick: rtsx_usb_ms: complete requests after eject instead of dropping them  memstick_check() can pass its host->removing check just before rtsx_usb_ms_drv_remove() sets eject/removing. Its next request is then silently dropped: rtsx_usb_ms_request() skips schedule_work() once eject is set, and drv_remove's cancel_work_sync() can also cancel a queued handle_req before it picks the request up. Nobody completes card->mrq_complete.  Once memstick core waits for requests without a timeout (\"memstick: core: wait for request completion before freeing card\"), this hangs removal: memstick_check() never returns and memstick_remove_host() blocks in flush_workqueue():    INFO: task kworker/u10:3:65 blocked for more than 20 seconds.   Workqueue: kmemstick memstick_check    __wait_for_common    memstick_check    INFO: task kworker/1:1:33 blocked for more than 20 seconds.   Workqueue: usb_hub_wq hub_event    __flush_workqueue    memstick_remove_host    rtsx_usb_ms_drv_remove  Never drop a request. rtsx_usb_ms_request() always schedules handle_req, and handle_req fails requests with -ENOMEDIUM once eject is set, without touching the device. drv_remove flushes handle_req instead of cancelling it, and cancels it only after memstick_remove_host(), when no new request can arrive, so it cannot run on a freed host.  The host_mutex drain in drv_remove is removed: handle_req always leaves host->req NULL when it finishes, so the drain never had anything to do, and it would now race with handle_req.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99039",
                                "url": "https://ubuntu.com/security/CVE-2026-99039",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  memstick: core: wait for request completion before freeing card  In memstick_alloc_card() and memstick_set_rw_addr(), wait_for_completion_timeout() is used to wait for device identification and address configuration requests to complete.  The memstick subsystem does not provide an abort or cancellation callback in struct memstick_host for in-flight requests. If wait_for_completion_timeout() expires (for instance, when a USB transfer or command retry is delayed), memstick_alloc_card() returns an error and frees the memstick_dev structure via kfree(card).  However, the host controller driver (such as rtsx_usb_ms) is still running the request asynchronously in worker context. When the transfer eventually finishes, the driver writes into host->req->data, which points to memory inside the already freed card structure. This leads to a KASAN slab-use-after-free write:    BUG: KASAN: slab-use-after-free in ms_read_bytes+0x8fe/0x990   Write of size 1 at addr ffff88813c188079 by task kworker/1:5/5239   Workqueue: events rtsx_usb_ms_handle_req   Call Trace:    ms_read_bytes+0x8fe/0x990 drivers/memstick/host/rtsx_usb_ms.c:450    rtsx_usb_ms_issue_cmd drivers/memstick/host/rtsx_usb_ms.c:477 [inline]    rtsx_usb_ms_handle_req+0x557/0x1a00 drivers/memstick/host/rtsx_usb_ms.c:531    process_one_work+0xac7/0x1b10 kernel/workqueue.c:3396    worker_thread+0x5ef/0xe50 kernel/workqueue.c:3560    kthread+0x373/0x450 kernel/kthread.c:436    Allocated by task 1662:    memstick_alloc_card drivers/memstick/core/memstick.c:383 [inline]    memstick_check+0x2c1/0x10d0 drivers/memstick/core/memstick.c:452    process_one_work+0xac7/0x1b10 kernel/workqueue.c:3396    Freed by task 1662:    kfree+0x20c/0x650 mm/slub.c:6792    memstick_alloc_card drivers/memstick/core/memstick.c:420 [inline]    memstick_check+0x72b/0x10d0 drivers/memstick/core/memstick.c:452    process_one_work+0xac7/0x1b10 kernel/workqueue.c:3396  Host controller drivers (rtsx_usb_ms, jmb38x_ms, tifm_ms, r592) already implement their own hardware and bus timeouts, and callers in mspro_block and ms_block already rely on wait_for_completion() unconditionally.  Replace wait_for_completion_timeout() with wait_for_completion() in memstick_set_rw_addr() and memstick_alloc_card() so that the card structure is never freed while an asynchronous request is in flight.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99040",
                                "url": "https://ubuntu.com/security/CVE-2026-99040",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  KEYS: Fix add_key() race with keyring restriction  __key_create_or_update() snapshots keyring->restrict_link before taking the destination keyring's semaphore.  keyring_restrict() installs a restriction while holding that semaphore.  This allows a writer to observe no restriction, wait for the keyring owner to install a reject-all restriction and return successfully, and then link a key using the stale NULL snapshot.  The writer only needs write permission on the destination keyring.  Move the restrict_link read after __key_link_lock() and __key_link_begin().  The read and the subsequent restriction check are then serialized with restriction installation by keyring->sem.  The race was reproduced on v7.2.8 in 19 executions where restriction installation returned before the link completed.  All 19 linked the key despite the reject-all restriction.  With this change, 312 executions reached the same ordering and every add_key() call failed with -EPERM.  The issue was found by manual concurrency analysis assisted by AI-based analysis and independently verified with a QEMU reproducer and kernel instrumentation.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99045",
                                "url": "https://ubuntu.com/security/CVE-2026-99045",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ibmveth: h_free logical LAN on open-fail after register  ibmveth_open() registers the logical LAN, then allocates the RX buffer pools. A pool failure jumps to out_free_buffer_pools without h_free_logical_lan(), so PHYP still owns the buffer-list page when it is unmapped. request_irq() failure already issued the hypercall before taking the same label.  Move that h_free to the shared post-register unwind so both paths deregister before the buffer list is unmapped.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99049",
                                "url": "https://ubuntu.com/security/CVE-2026-99049",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  gpio: xilinx: fix runtime PM leak on request error path  pm_runtime_get_sync() leaves the usage counter incremented even when it fails, and xgpio_request() returns the error without dropping it.  gpiolib does not call ->free() when ->request() fails, so xgpio_free(), which holds the only matching pm_runtime_put(), never runs. The reference is leaked and the controller can no longer runtime-suspend, so its clock stays enabled.  Switch to pm_runtime_resume_and_get(), which only increments the usage counter on success.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99052",
                                "url": "https://ubuntu.com/security/CVE-2026-99052",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  selinux: preserve NATIVE_LABELS on already-initialized sb in set_mnt_opts  When an NFSv4 filesystem exported with security_label is mounted a second time, sget_fc() returns the existing superblock and nfs_get_root() calls security_sb_set_mnt_opts() again on it. Since the superblock is already SB_INITIALIZED, selinux_set_mnt_opts() takes an early exit without setting SECURITY_LSM_NATIVE_LABELS in *set_kern_flags. nfs_get_root() then sees kflags without SECURITY_LSM_NATIVE_LABELS set and clears NFS_CAP_SECURITY_LABEL on the shared nfs_server, silently disabling per-file labeling for both the new and the original mount.  Commit 3815a245b501 (\"security/selinux: fix SECURITY_LSM_NATIVE_LABELS on reused superblock\") fixed the same problem in selinux_sb_clone_mnt_opts().  The reused-superblock path for a plain second mount now goes through sb_set_mnt_opts rather than sb_clone_mnt_opts, so it needs the same treatment: on both SE_SBINITIALIZED early exits, set SECURITY_LSM_NATIVE_LABELS in *set_kern_flags when the superblock was already using SECURITY_FS_USE_NATVE.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99053",
                                "url": "https://ubuntu.com/security/CVE-2026-99053",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  tipc: hold a reference to nodes found by link name  tipc_node_find_by_name() returns a node after dropping its RCU read lock without taking a reference.  The LINK_SET, LINK_GET and LINK_RESET_STATS handlers then lock and access the node, racing with timer-driven cleanup of a down peer.  Generic netlink serialization does not exclude the node timer.  The following interleaving can leave a handler using a freed node:    CPU 0: find the node under RCU and release the node read lock   CPU 1: tipc_node_timeout() clears the links and unlinks the down node   CPU 1: drop the list and timer references, queuing tipc_node_free()   CPU 0: leave the RCU read-side critical section   CPU 1: complete the grace period and free the node   CPU 0: acquire the node lock through the stale pointer  LINK_SET also uses the node's media address after releasing the node lock, when passing queued packets to tipc_bearer_xmit().  KASAN on v7.3-rc5 reported:    BUG: KASAN: slab-use-after-free in _raw_read_lock_bh   Write of size 4 at addr ffff88807e06f008 by task poc/92   Call Trace:    _raw_read_lock_bh                 kernel/locking/spinlock.c:287    tipc_nl_node_set_link             net/tipc/node.c:2475    genl_family_rcv_msg_doit          net/netlink/genetlink.c:1114    genl_rcv_msg                      net/netlink/genetlink.c:1209    netlink_rcv_skb                   net/netlink/af_netlink.c:2575    Allocated by task 0:    tipc_node_create                  net/tipc/node.c:539    tipc_node_check_dest              net/tipc/node.c:1196    tipc_disc_rcv                     net/tipc/discover.c:252    Freed by task 92:    kfree                             mm/slub.c:6801    rcu_core                          kernel/rcu/tree.c:2919    Last potentially related work creation:    __call_rcu_common.constprop.0     kernel/rcu/tree.c:3181    tipc_node_timeout                 net/tipc/node.c:814  Acquire a reference to the selected node with kref_get_unless_zero() before leaving RCU, returning NULL if the node has already been released.  Release that reference on every caller exit after the last node access, including transmission in LINK_SET.  Keep the existing link lookup order and locking so concurrent link removal still takes the existing error paths.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99054",
                                "url": "https://ubuntu.com/security/CVE-2026-99054",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  tipc: destroy topsrv workqueues before closing connections  tipc_topsrv_stop() closed subscriber connections while the topology server's send and receive workqueues were still running. Socket callbacks and subscription events could then queue more work, and in-flight send/recv work could drop the last connection reference during the conn_idr walk.  That race produced several teardown failures: refcount_t addition on 0 from conn_get() on a connection whose release was blocked on idr_lock, a subsequent use-after-free in tipc_conn_close(), queue_work() on an already destroyed workqueue from the listener data-ready callback, and an RCU stall in tipc_topsrv_exit_net() while the walk spun under idr_lock.  Clear srv->listener under idr_lock so it acts as a shutdown flag, skip queue_work() once it is NULL, destroy the workqueues to flush in-flight work, and only then close the remaining connections. Refuse tipc_conn_lookup() after that flag is cleared, and drop idr_lock when the teardown walk finds no connection, so an in-flight subscription event cannot pin idr_in_use while the walk holds the lock.  v3 supersedes the narrower in-thread diff Tung Quang Nguyen posted on 2026-09-23. It keeps his teardown order and adds the lookup refusal and the empty-idr unlock.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99056",
                                "url": "https://ubuntu.com/security/CVE-2026-99056",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  strparser: make sure __strp_recv isn't running before tearing down the parser  The comment above strp_done() claims that if strp is stopped, strp_recv will no longer be called. That's only true if the caller has a mechanism (eg locking) to guarantee that strp_recv() calls that started before strp_stop() have completed by the time we call strp_done().  This adds a dummy lock_sock/release_sock pair to guarantee that any in-flight strp_recv() (which runs under either bh_lock_sock or lock_sock, depending if it's called from ->sk_data_ready or strp_work) has completed.  Only espintcp can be affected by this race condition, but this patch makes sure no future user of strp can have the bug.  This could crash on strp->sk (\"general mode\" of strp), but this mode has been here for 9 years and has never been used. It'll be gone soon, no point worrying about it.  Switch the stopped/paused/etc bits to u8's to avoid races between strp_stop() and strp_pause/unpause().  A reproducer has been published and turns the possible UAF into an exploit [1].",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99057",
                                "url": "https://ubuntu.com/security/CVE-2026-99057",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  xen/netfront: don't leak the skb when xennet_fill_frags() fails  When a response chain has more slots than fit in the skb's frags, xennet_fill_frags() returns an error and xennet_poll() jumps to its error path.  That path moves what's left on tmpq to errq to be freed, but the skb being filled was already dequeued from tmpq, so it's never freed.  Each chain that overflows leaks the skb and the pages attached to it as frags, and the backend decides how many slots it sends.  Put the skb back on tmpq before taking the error path, like the xennet_set_skb_gso() failure just above it does.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99058",
                                "url": "https://ubuntu.com/security/CVE-2026-99058",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  workqueue: Fix NULL current_pwq deref in chained work check  current_wq_worker() only tells us that %current is a kworker. It does not guarantee that the worker is currently executing a work item, as worker->current_pwq is populated only while process_one_work() is running the work function.  is_chained_work() can be reached while queueing on a draining or destroying workqueue. If a kworker outside work-item execution reaches that path, current_wq_worker() returns a worker but worker->current_pwq is NULL, and the chained-work test can fault before it emits the intended warning.  Guard the chained-work test with worker->current_pwq. A kworker without current_pwq is not executing work on the target workqueue, so the helper should return false and let the draining/destroying warning fire.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99059",
                                "url": "https://ubuntu.com/security/CVE-2026-99059",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wireguard: noise: reject response consumption after intermediate initiation  Two threads begin processing the identical response message, received twice. The first thread, A, runs. While it's running, the second one, B, gets partway through, and during that slow calculation, or even while blocking on down_write(), A completes and then also a handshake initiation that's already been queued up runs in thread C, which itself takes that same down_write(). The handshake initiation creation succeeds, and sets the state back to waiting-for-response, and calls up_write(), at which point thread B resumes, because either its finished its calculations or was finally allowed to acquire down_write(). Thread B then copies the state back to the peer, and begins a new session, using that state, which is the same session as the one made in thread A.  Thread A\t\t\tThread B\t\t\tThread C  down_read()  sA = handshake->state  memcpy(cA, handshake->crypto) up_read() if (sA != 1)  goto fail slow_crypto(cA) \t\t\t\tdown_read() \t\t\t\t sB = handshake->state \t\t\t\t memcpy(cB, handshake->crypto) \t\t\t\tup_read() \t\t\t\tif (sB != 1) \t\t\t\t goto fail \t\t\t\tslow_crypto(cB) down_write()  if (sA != handshake->state)   goto fail  memcpy(handshake->crypto, cA)  handshake->state = 2 up_write() down_write()  if (handshake->state != 2)   goto fail  derive_session(handshake->crypto) up_write() \t\t\t\t\t\t\t\tdown_write() \t\t\t\t\t\t\t\t slow_crypto(handshake->crypto) \t\t\t\t\t\t\t\t handshake->state = 1 \t\t\t\t\t\t\t\tup_write() \t\t\t\tdown_write() \t\t\t\t if (sB != handshake->state) \t\t\t\t   goto fail \t\t\t\t memcpy(handshake->crypto, cB) \t\t\t\t handshake->state = 2 \t\t\t\tup_write() \t\t\t\tdown_write() \t\t\t\t if (handshake->state != 2) \t\t\t\t  goto fail \t\t\t\t derive_session(handshake->crypto) \t\t\t\tup_write()  This seems basically impossible to hit in a meaningful way in practice, but ensure that it absolutely cannot happen by comparing the ephemeral private key that's on the stack with the latest one that the peer's handshake state has.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99061",
                                "url": "https://ubuntu.com/security/CVE-2026-99061",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: brcmfmac: fix P2P device removal race in brcmf_detach()  When the driver is removed while the user space process that created the P2P device (e.g. wpa_supplicant) is still exiting, the P2P device interface is removed twice and the kernel crashes.  The two paths are:   - wpa_supplicant, on exit, sends NL80211_CMD_DEL_INTERFACE for the P2P    device. nl80211_del_interface() holds RTNL and the wiphy mutex and    calls brcmf_p2p_del_vif(), which disables discovery and waits up to    1.5 s for BRCMF_E_IF_DEL. Then it calls brcmf_remove_interface(),    which unregisters the wdev and frees the vif and the ifp.   - brcmf_detach() sets the bus down, so BRCMF_E_IF_DEL never arrives,    and calls brcmf_remove_interface(ifp, false) for the same ifp.    brcmf_p2p_ifp_removed() reads ifp->vif and then blocks on    rtnl_lock(). When brcmf_p2p_del_vif() releases RTNL, it calls    cfg80211_unregister_wdev() on the wdev that was already unregistered    and freed.  The second list_del_rcu() of wdev->list faults on LIST_POISON2:    brcmfmac: brcmf_p2p_del_vif delete P2P vif   brcmfmac: brcmf_p2p_deinit_discovery enter   brcmfmac: brcmf_p2p_del_vif P2P: GO_NEG_PHASE status cleared   brcmfmac: brcmf_detach Enter   brcmfmac: brcmf_bus_change_state 1 -> 0   brcmfmac: brcmf_remove_interface Enter, bsscfgidx=1, ifidx=0   brcmfmac: brcmf_del_if Enter, bsscfgidx=1, ifidx=0   brcmfmac: brcmf_p2p_ifp_removed P2P: device interface removed   [1.5 s later, brcmf_p2p_del_vif() timed out]   brcmfmac: brcmf_remove_interface Enter, bsscfgidx=1, ifidx=0   brcmfmac: brcmf_del_if Enter, bsscfgidx=1, ifidx=0   brcmfmac: brcmf_p2p_ifp_removed P2P: device interface removed   Unable to handle kernel paging request at virtual address dead000000000122   Internal error: Oops: 96000044 [#1] PREEMPT_RT SMP   pc : _cfg80211_unregister_wdev+0x6c/0x264 [cfg80211]   Call trace:    _cfg80211_unregister_wdev+0x6c/0x264 [cfg80211]    cfg80211_unregister_wdev+0x10/0x1c [cfg80211]    brcmf_p2p_ifp_removed+0x84/0xb0 [brcmfmac]    brcmf_remove_interface+0x1f4/0x254 [brcmfmac]    brcmf_detach+0x88/0x180 [brcmfmac]    brcmf_sdio_remove+0x90/0x7b0 [brcmfmac]    brcmf_sdiod_remove+0x20/0xa0 [brcmfmac]    brcmf_ops_sdio_remove+0xbc/0x12c [brcmfmac]    sdio_bus_remove+0x38/0x144    device_release_driver_internal+0x1e8/0x2c0    device_release_driver+0x14/0x20    brcmf_sdio_bus_remove+0x2c/0x40 [brcmfmac]    brcmf_fwvid_unregister_vendor+0xd8/0x170 [brcmfmac]    __exit_compat+0x18/0x418 [brcmfmac_cyw]    __arm64_sys_delete_module+0x1ac/0x244  The log was taken with debug=0x406 on an i.MX 8M Plus board with a CYW55513 (Sona IF513) on SDIO. The driver is the Ezurio backport of brcmfmac from v6.18.22 on a 5.4-rt kernel. The code involved is the same in mainline.  To reproduce:    1. Start wpa_supplicant on wlan0 and let it associate. It creates the      P2P device (iw dev shows \"type P2P-device\").   2. Stop wpa_supplicant and remove the driver without waiting for      wpa_supplicant to exit:         kill $(pidof wpa_supplicant)        rmmod brcmfmac_cyw brcmfmac  The crash is reproducible on that board.  For the interface without a netdev (the P2P device), take RTNL and the wiphy mutex in brcmf_detach() before reading iflist, and remove it with locked=true. If brcmf_p2p_del_vif() runs first, brcmf_detach() finds the slot empty. If brcmf_detach() runs first, nl80211 does not find the wdev any more. The interfaces with a netdev are removed as before, because brcmf_del_if() takes RTNL on its own for the primary interface.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99063",
                                "url": "https://ubuntu.com/security/CVE-2026-99063",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  dm ioctl: don't let data_start run past the buffer  struct dm_ioctl has seven bytes of trailing padding, so the smallest buffer userspace is allowed to ask for, offsetof(struct dm_ioctl, data), is seven bytes shorter than sizeof(struct dm_ioctl).  get_result_buffer() sets data_start to sizeof(struct dm_ioctl) without looking at how big the buffer actually is. Ask for the minimum and data_start ends up seven bytes past the end. Callers add it to data_size, and ctl_ioctl() copies that much back to userspace:    BUG: KASAN: slab-out-of-bounds in _copy_to_user+0xad/0xd0   Read of size 312 at addr ffff8880169e4c00 by task repro-dm/140    ctl_ioctl+0x5e3/0xcb0    dm_ctl_ioctl+0x25/0x40   allocated 305-byte region [ffff8880169e4c00, ffff8880169e4d31)  A DM_LIST_DEVICES with data_size set to 305 is enough to hit it, and the seven bytes that leak are whatever sat next to the allocation.  Clamp data_start to the buffer size.  Note that this is not a security bug because the out-of-bounds read can only be triggered by root.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99067",
                                "url": "https://ubuntu.com/security/CVE-2026-99067",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  btrfs: scrub: fix local_root reference leak in scrub_print_warning_inode()  When paths_from_inode() fails, scrub_print_warning_inode() jumps to err without dropping the reference taken by btrfs_get_fs_root(), leaking a reference to the root every time path resolution fails while printing scrub warnings.  Every other error and success path of the function drops the reference.  Drop the reference on the paths_from_inode() failure path too.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99070",
                                "url": "https://ubuntu.com/security/CVE-2026-99070",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ipv6: do not warn on route notification size race  fib6_info_hw_flags_set() sizes the skb with rt6_nlmsg_size() and later fills it with rt6_fill_node().  With nexthop compatibility mode enabled, a concurrent replacement can grow the group between these independent snapshots.  rt6_fill_node() can then legitimately return -EMSGSIZE, so the warning does not prove a sizing bug.  Remove the warning.  The existing error path still frees the skb and reports the error to listeners.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99071",
                                "url": "https://ubuntu.com/security/CVE-2026-99071",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ipv4: do not warn on route notification size race  Commit 680aea08e78c (\"net: ipv4: Emit notification when fib hardware flags are changed\") added asynchronous route notifications for hardware flag changes.  fib_alias_hw_flags_set() sizes the skb with fib_nlmsg_size() and later fills it with fib_dump_info() while holding only RCU.  With nexthop compatibility mode enabled, a concurrent replacement can grow the group between these independent snapshots.  fib_dump_info() can then legitimately return -EMSGSIZE, so the warning does not prove a sizing bug.  Remove the warning.  The existing error path still frees the skb and reports the error to listeners.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99072",
                                "url": "https://ubuntu.com/security/CVE-2026-99072",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ipv4: stop route notification sizing when nexthop group shrinks  Commit 680aea08e78c (\"net: ipv4: Emit notification when fib hardware flags are changed\") added an RCU-only fib_nlmsg_size() call for asynchronous hardware flag notifications.  fib_nlmsg_size() checks fib_info_num_path() before each iteration, then fib_info_nhc() independently reloads nh->nh_grp. If RTM_NEWNEXTHOP replaces a group with fewer paths between those loads, fib_info_nhc() returns NULL and fib_nexthop_nlmsg_size() dereferences it.  Stop sizing when the indexed path is absent. Nexthop groups are dense, so the current snapshot has no later path.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98686",
                                "url": "https://ubuntu.com/security/CVE-2026-98686",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  smb: client: discard post-EOF pagecache when extending a file via zero range  smb3_zero_range() removed the pagecache only for the range being zeroed, so when it extends the file the folio straddling the old EOF - which may hold data dirtied past EOF through an mmap - was never dropped and became visible as file content once the file was extended.  Lower the discard boundary to the smaller of the zero-range offset and the old EOF.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98700",
                                "url": "https://ubuntu.com/security/CVE-2026-98700",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: mac80211: set info->band for 802.3 encap offload frames  Unlike the 802.11 TX paths, ieee80211_8023_xmit() does not set info->band from the channel context on non-MLD interfaces. It stays at 0, so ieee80211_get_tx_rates() uses the wrong band for these frames.  Set it the same way as ieee80211_build_hdr(): drop the frame if there is no channel context, and leave the band at 0 on MLD interfaces.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98716",
                                "url": "https://ubuntu.com/security/CVE-2026-98716",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  KVM: SVM: Use the active VMCB's MSR bitmap when checking if MSR is intercepted  Use the MSR permission bitmap of the active VMCB instead of assuming that KVM is always using vmcb02's bitmap when L2 is active, as KVM uses msrpm02 if and only if L1 wants to intercept MSR accesses, i.e. if and only if KVM needs to merge msprm01 with msrpm12.  Don't bother tracking the virtual address of the bitmap that's being used, as __va() is cheap on x86, and caching the virtual address would introduce yet another source of potentially stale information.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99080",
                                "url": "https://ubuntu.com/security/CVE-2026-99080",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  fs: Free any excess xarray nodes in clear_inode()  For many years we've had a hard to hit leak of xarray nodes.  Hugh documented it well in commit 786b31121a2c.  Recently people and syzbot have found ways to force it to happen with madvise.  Rather than fix the leaks where they happen, just call xa_destroy() which has the side-effect of cycling the i_pages lock.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98709",
                                "url": "https://ubuntu.com/security/CVE-2026-98709",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: mac80211: count only matching reservations in reserved switch  ieee80211_vif_use_reserved_switch() validates a replacement by counting assigned links on ctx->replace_ctx and treating reservations too broadly. A link can still be assigned to the old channel context while holding a reservation that belongs to a different replacement operation.  That can make the current replacement appear complete too early. If another link finalizes first, the function can free the WILL_BE_REPLACED chanctx while the unmatched link and driver still use it, leading to a use-after-free in later beacon generation.  Require an in-place reservation to point at the current replacement context, and require the reserved and assigned contexts to be the matching replacement pair, before counting or moving the link.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98708",
                                "url": "https://ubuntu.com/security/CVE-2026-98708",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: mac80211: keep paired old chanctx alive  An in-place replacement keeps reciprocal replace_ctx pointers between the old WILL_BE_REPLACED chanctx and the new REPLACES_OTHER chanctx. However, the early free paths only consider assigned and reserved link users when deciding whether to free the old chanctx.  That lets the old chanctx be freed too early while the replacement partner still points back to it, either when the last assigned link is released or when that link successfully reassigns to another existing context. Later unreserve and switch-finalization paths can then follow a stale replace_ctx pointer.  Keep a paired old chanctx alive until the replacement pair has been torn down. Apply the same check to both __ieee80211_link_release_channel() and ieee80211_link_use_reserved_reassign(). If the replacement is later abandoned, ieee80211_link_unreserve_chanctx() already tears down the pairing before freeing the old chanctx once no users remain.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98752",
                                "url": "https://ubuntu.com/security/CVE-2026-98752",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  tty: port: fix tty_port_tty_vhangup() race  Drivers rely on tty_port_tty_vhangup() to synchronously hang up their ports before tearing down resources as part of deregistration (e.g. on physical disconnect).  If tty_port_tty_vhangup() races with another hangup it may however return before the port has been shut down. This is in turn can lead to use-after-free and NULL-pointer dereferences in racing ioctls (including a synchronous hangup) and in processing of racing asynchronous hangups (carrier loss).  Add the missing serialisation to tty_port_tty_vhangup() and tty_port_hangup() so that the former does not return until the port has been shut down also when there is a racing hangup.  Note that serial core does not use tty_port_hangup(), but it already holds the port mutex when clearing port->tty and shutting down the port in uart_hangup().",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99081",
                                "url": "https://ubuntu.com/security/CVE-2026-99081",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  bnxt_en: fix DMA mapping length for padded small packets  Stefan Fleischmann reported Intel IOMMU DMA Read faults on BCM57412 NetXtreme-E NICs when transmitting packets on VLAN/macvlan interfaces:    DMAR: [DMA Read NO_PASID] Request device [18:00.0] fault addr 0xfc499000         [fault reason 0x06] PTE Read access is not set   bnxt_en 0000:18:00.0 eno1np0: Abandoning msg {0xb4 0x41a} len: 0 due to firmware status: 0x2000001   ...   NETDEV WATCHDOG: eno1np0 (bnxt_en): transmit queue 0 timed out  The fault address (0xfc499000) is on an exact 4KB page boundary, pointing to a DMA read buffer overrun.  In bnxt_start_xmit(), packets smaller than BNXT_MIN_PKT_SIZE (52 bytes), such as 42-byte untagged ARP frames, are padded:      if (length < BNXT_MIN_PKT_SIZE) {         pad = BNXT_MIN_PKT_SIZE - length;         if (skb_pad(skb, pad))             goto tx_kick_pending;         length = BNXT_MIN_PKT_SIZE;     }      mapping = dma_map_single(&pdev->dev, skb->data, len, DMA_TO_DEVICE);     ...     dma_unmap_len_set(tx_buf, len, len);  However, 'len' was initialized earlier to skb_headlen(skb) (e.g. 42 bytes) and is left unadjusted after padding. Consequently, dma_map_single() and dma_unmap_len_set() map and track only 42 bytes.  Later, the hardware TX buffer descriptor is programmed with the padded length:      txbd->tx_bd_len_flags_type =         cpu_to_le32(((len + pad) << TX_BD_LEN_SHIFT) | flags |                     TX_BD_FLAGS_PACKET_END);  The NIC DMA engine is thus instructed to read 52 bytes from a region where only 42 bytes were DMA-mapped. If skb->data ends near the boundary of a 4KB page (within 'pad' bytes of the next page), the hardware DMA read overruns into the unmapped adjacent page, triggering an IOMMU fault.  This issue was exposed after commit 447cbe95ebb9 (\"vlan: fix skb_under_panic and races when toggling HW VLAN offload\") because reserving extra VLAN headroom rounded LL_RESERVED_SPACE from 48 up to 64 bytes, shifting skb->data offsets and potentially causing small frames to land right against page boundaries.  Fix this by using skb_put_padto(skb, BNXT_MIN_PKT_SIZE) in bnxt_start_xmit(), before skb_shinfo(skb)->nr_frags is sampled, because padding might linearize the skb. This ensures skb->len and skb_headlen(skb) reflect the padded size so that dma_map_single() maps the full buffer and the descriptor length is consistent. This also removes the temporary 'pad' variable and masking logic.  The padding is done after the SW USO branch, otherwise bnxt_sw_udp_gso_xmit() would account the padding as UDP payload and send it in extra segments.  Note that SW USO segments are still not padded: with IPv4, a segment carrying less than 10 bytes of UDP payload (small gso_size, or a short last segment) is sent as a frame shorter than BNXT_MIN_PKT_SIZE. This is a separate issue, left for a followup patch.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98696",
                                "url": "https://ubuntu.com/security/CVE-2026-98696",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  USB: serial: fix driver deregistration order  USB serial driver modules register one driver for the USB bus and one or more drivers for the ports on the USB serial bus.  When unloading a driver module, the USB driver must be deregistered before the USB serial bus drivers so that I/O is stopped before unbinding the ports to avoid use-after-free in completion handlers accessing port data.  Note that the \"new_id\" attributes must first be removed to prevent new ids from being added and triggering a probe of the USB driver after it has been deregistered.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98705",
                                "url": "https://ubuntu.com/security/CVE-2026-98705",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: mac80211: account proxy paths against the mesh path limit  Proxy-path churn can drive the interface path counter negative and let later mesh path additions exceed MESH_MAX_MPATHS.  mesh_path_free_rcu() decrements the interface mpaths counter for entries from both the mesh and proxy path tables, but mpp_path_add() never reserves a slot in that counter. Removing or expiring a proxy path therefore returns a slot that was never charged.  mesh_path_add() uses the same counter to enforce MESH_MAX_MPATHS, so once it falls below the number of installed paths the limit no longer holds.  Reserve the shared quota before allocating a proxy path and release it on every unsuccessful addition. Mesh and proxy paths now share one 1024-entry budget, so mpp_path_add() can return -ENOSPC at that limit.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98722",
                                "url": "https://ubuntu.com/security/CVE-2026-98722",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  mtd: block2mtd: Fix divide error when erase_size is zero  The erase size is parsed from the \"block2mtd\" module parameter and can be set to zero. add_device() then evaluates          if (size % erase_size)  with a zero divisor, which triggers a divide error:  divide error: 0000 [#1] PREEMPT SMP PTI RIP: 0010:add_device drivers/mtd/devices/block2mtd.c:296 [inline] RIP: 0010:block2mtd_setup2+0x592/0xda0 drivers/mtd/devices/block2mtd.c:459 Call Trace: block2mtd_setup+0x27/0xe0 drivers/mtd/devices/block2mtd.c:476 param_attr_store+0x214/0x310 kernel/params.c:589 module_attr_store+0x65/0x90 kernel/params.c:904 kernfs_fop_write_iter+0x3a4/0x540 fs/kernfs/file.c:345 ...  Reject a zero erase size before performing the modulo operation so the existing \"erasesize must be a divisor of device size\" error path reports the invalid argument and frees the device.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98695",
                                "url": "https://ubuntu.com/security/CVE-2026-98695",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  USB: serial: fix ioctl hangup race  The tty ioctls can race with hangup and end up calling into a tty driver for a device that is already gone or powered down.  Serialise the callbacks using the tty port mutex and add the missing checks to make sure the port has not been hung up before accessing port driver data or hardware.  This specifically avoids dereferencing a NULL-pointer if a device is disconnected during lengthy break signalling.  Note that TIOCGICOUNT and TIOCMIWAIT do not access port driver data or hardware and are therefore not affected by the race.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98694",
                                "url": "https://ubuntu.com/security/CVE-2026-98694",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  thunderbolt: Fix KASAN reported use-after-free when request is canceled  Alan reported that when doing stress testing sometimes KASAN notices use-after-free during control channel operation (stripped down keeping the relevant parts):   BUG: KASAN: slab-use-after-free in tb_cfg_request_sync+0x240/0x250 [thunderbolt]  Read of size 24 at addr ffff88811067f290 by task kworker/u40:2/1760   <TASK>   tb_cfg_request_sync+0x240/0x250 [thunderbolt]   tb_cfg_read_raw+0x367/0x510 [thunderbolt]   tb_cfg_read+0xec/0x240 [thunderbolt]   tb_port_get_link_generation+0x258/0x420 [thunderbolt]   tb_usb3_consumed_bandwidth+0x1c1/0x2c0 [thunderbolt]   tb_tunnel_consumed_bandwidth+0xfd/0x910 [thunderbolt]   tb_available_bandwidth+0x5f2/0xeb0 [thunderbolt]   tb_recalc_estimated_bandwidth+0x2a0/0x1bc0 [thunderbolt]   tb_handle_dp_bandwidth_request+0x1897/0x5e20 [thunderbolt]   process_one_work+0x675/0x1230   worker_thread+0x5e6/0xf70   kthread+0x365/0x470   ret_from_fork+0x54d/0x710   ret_from_fork_asm+0x1a/0x30   </TASK>   Allocated by task 1760:   __kmalloc_cache_noprof+0x1ee/0x550   tb_cfg_read_raw+0x1d3/0x510 [thunderbolt]   tb_cfg_read+0xec/0x240 [thunderbolt]   tb_port_get_link_generation+0x258/0x420 [thunderbolt]   tb_usb3_consumed_bandwidth+0x1c1/0x2c0 [thunderbolt]   tb_tunnel_consumed_bandwidth+0xfd/0x910 [thunderbolt]   tb_available_bandwidth+0x5f2/0xeb0 [thunderbolt]   tb_recalc_estimated_bandwidth+0x2a0/0x1bc0 [thunderbolt]   tb_handle_dp_bandwidth_request+0x1897/0x5e20 [thunderbolt]   process_one_work+0x675/0x1230   worker_thread+0x5e6/0xf70   kthread+0x365/0x470   ret_from_fork+0x54d/0x710   ret_from_fork_asm+0x1a/0x30   Freed by task 926:   kfree+0x18f/0x4a0   tb_cfg_request_put+0xb7/0xe0 [thunderbolt]   tb_cfg_request_work+0x82/0x120 [thunderbolt]   process_one_work+0x675/0x1230   worker_thread+0x5e6/0xf70   kthread+0x365/0x470   ret_from_fork+0x54d/0x710   ret_from_fork_asm+0x1a/0x30   Second to last potentially related work creation:   __queue_work+0x575/0xd00   queue_work_on+0x77/0x80   tb_cfg_request_cancel+0xc7/0x260 [thunderbolt]   tb_cfg_request_sync+0x1f6/0x250 [thunderbolt]   tb_cfg_read_raw+0x367/0x510 [thunderbolt]   tb_cfg_read+0xec/0x240 [thunderbolt]   tb_port_get_link_generation+0x258/0x420 [thunderbolt]   tb_usb3_consumed_bandwidth+0x1c1/0x2c0 [thunderbolt]   tb_tunnel_consumed_bandwidth+0xfd/0x910 [thunderbolt]   tb_available_bandwidth+0x5f2/0xeb0 [thunderbolt]   tb_recalc_estimated_bandwidth+0x2a0/0x1bc0 [thunderbolt]   tb_handle_dp_bandwidth_request+0x1897/0x5e20 [thunderbolt]   process_one_work+0x675/0x1230   worker_thread+0x5e6/0xf70   kthread+0x365/0x470   ret_from_fork+0x54d/0x710   ret_from_fork_asm+0x1a/0x30  The last stack trace is helpful because it shows that we are cancelling a request and looking at tb_cfg_request_cancel() what might happen is that tb_cfg_request_work() completes right before tb_cfg_request_cancel() starts and because of this it will call schedule_work() queueing the same work to run again. However, it is already removed from the request_queue and reference count is dropped so when tb_cfg_request_work() triggers again it will access memory that is already released.  Fix this so that we first make sure a cancelled request is not handed away from tb_cfg_request_find() or scheduled to run. Then instead of relying on the worker to clean up the request we will do it in tb_cfg_request_cancel() after the work is canceled from running. Make tb_cfg_request_dequeue() release the request only if it was actually removed from the queue.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98704",
                                "url": "https://ubuntu.com/security/CVE-2026-98704",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: mac80211: keep fallback association elements alive  Associating to a non-transmitted MBSSID profile reads freed memory while determining the operating channel and applying HT capabilities.  When an association response omits WMM, HT, or VHT information, ieee80211_assoc_config_link() parses the cached BSS IEs and copies the missing element pointers out of that fallback parse. For a non-transmitted MBSSID profile those pointers refer to merged-profile storage owned by the parse object, and the fallback block frees that object at its end. The copied pointers are used afterwards to determine the operating channel, configure bandwidth, and apply HT capabilities.  Keep the fallback parse result alive until association setup finishes.  [reorder variable declaration]",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98707",
                                "url": "https://ubuntu.com/security/CVE-2026-98707",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: mac80211: shut down RX BA session timer on teardown  Tearing down an RX BA session can leave the session timer queued on a freed tid_rx. Later timer-wheel processing and the timer callback itself then run against freed memory.  An RX BAR handler can dereference tid_rx under RCU before teardown unpublishes it and stay in its read-side critical section while teardown deletes the session timer. The stale handler can then rearm the timer after timer_delete_sync() returns and before the RCU callback frees tid_rx.  Use timer_shutdown_sync() so rearm attempts become ineffective once teardown starts. Keep reorder_timer unchanged: teardown marks the session removed under reorder_lock and its release path checks that state before rearming. session_timer has no equivalent guard because ieee80211_rx_h_ctrl() rearms it before taking reorder_lock.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98749",
                                "url": "https://ubuntu.com/security/CVE-2026-98749",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  tty: serial: max3100: shut down timer before freeing port  max3100_shutdown() stops the polling timer but returns early during system suspend. If the SPI device is unbound before resume, the serial core does not call max3100_shutdown() again, so max3100_remove() frees the port while the timer remains armed. max3100_timeout() may then access the freed port and re-arm the timer.  Add final timer teardown to max3100_remove() and use timer_shutdown_sync() to prevent a racing callback from re-arming it. Also free the IRQ and destroy the workqueue there before freeing the port. Keep timer_delete_sync() in max3100_shutdown() so that a subsequent open() can re-arm the timer.  The workqueue is created before request_irq() and destroyed on both request_irq() failure and normal shutdown. Its presence at remove thus identifies the IRQ left registered when suspend bypasses shutdown.  Free the IRQ before destroying the workqueue, in both max3100_shutdown() and max3100_remove(), and cancel the pending work in between. free_irq() waits for a running interrupt handler to finish and no new handler can start afterwards, so a racing handler cannot queue work on a workqueue that is being destroyed; the force_end_work check in max3100_dowork() only narrows that window, as a handler delayed between the check and queue_work() could still run after the teardown has cleared the workqueue pointer. Cancelling the work also keeps destroy_workqueue() from waiting on a queued work item in case remove() ever runs while the freezable workqueue is still frozen, e.g. device removal during the resume window, before workqueues are thawed.  This issue was found by an in-house static analysis tool.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98751",
                                "url": "https://ubuntu.com/security/CVE-2026-98751",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  tty: abort break signalling on hangup  The break ioctls can race with hangup and end up calling into a tty driver for a device that is already gone or powered down.  Drivers must handle this race, but TCSBRK and TCSBRKP should still be aborted to avoid calling back into the driver after a user-controlled timeout (possibly even after the tty has been reopened).  Note that drivers should disable any break state on shutdown so just return on hangup (calling break_ctl() again is racy and will most likely fail for drivers handling the race).",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98753",
                                "url": "https://ubuntu.com/security/CVE-2026-98753",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  tty: tty_port: restore TTY_IO_ERROR on activation failure  Make sure to restore the TTY_IO_ERROR flag if activation fails to prevent I/O attempts on a port that is gone or powered down.  This specifically avoids issues like kernel panic due to unclocked accesses or NULL-pointer dereferences when accessing powered down or deregistered ports when a TTY ioctl races with hangup and open.  Note that the flag is set again in tty_port_close() but not restoring it on activation failure leaves a window where drivers fail to handle the ioctl-hangup race.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98762",
                                "url": "https://ubuntu.com/security/CVE-2026-98762",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  USB: dwc2: shut down wakeup timer before freeing HCD state  dwc2_wakeup_detected() accesses the DWC2 host state and can rearm the wakeup timer.  dwc2_hcd_free() currently deletes the timer only after freeing host-owned state, and timer_delete() does not synchronize a callback or prevent it from being queued again.  Stop and shut down the timer in dwc2_hcd_release(), before the HCD resources are freed.  This covers both the HCD initialization error path and normal HCD removal.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98784",
                                "url": "https://ubuntu.com/security/CVE-2026-98784",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  drm/amdgpu/gfx6: fix firmware leak on teardown  The firmware requested in gfx_v6_0_init_microcode() is not released when the GFX block is torn down, leaking the firmware resources.  Add gfx_v6_0_free_microcode() and call it from gfx_v6_0_sw_fini() to release the PFP, ME, CE and RLC firmware.  (cherry picked from commit 386e81346f95ab0be5a82c5535de932e7a456924)",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98779",
                                "url": "https://ubuntu.com/security/CVE-2026-98779",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  drm/amdgpu: fix ACP MFD device leak on init failure  acp_hw_init() registers ACP child devices with mfd_add_devices() before attaching them to the ACP power domain and initializing the hardware.  If attaching a child to the power domain fails, or if the ACP reset or clock enable operation times out, the failure path frees only the source cell, resource, and platform-data allocations. The child platform devices already registered by mfd_add_devices() remain registered and are never released.  Remove the children from the power domain and unregister the MFD devices on failures that occur after mfd_add_devices() succeeds. Keep mfd_add_devices() failures on the existing cleanup path since the MFD core already rolls back partially registered children itself.  The issue was identified by a static analysis tool I developed and confirmed by manual review.  (cherry picked from commit 63da68d6a2279ec945581c990c5a59a5ae8b5560)",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98742",
                                "url": "https://ubuntu.com/security/CVE-2026-98742",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ALSA: seq: Serialize compat port-info ioctls  The native sequencer ioctl path serializes handler calls with client->ioctl_mutex, but the translated port-info compat path invokes the same handlers through snd_seq_kernel_client_ctl() without taking that mutex.  This lets concurrent compat CREATE_PORT requests pass the port-count check before any request reaches the serialized insertion. The computed integer port index can then exceed the address field range and wrap to an existing index. Subsequent subscriber teardown can resolve the duplicate address to the wrong port and access a freed subscriber.  Take ioctl_mutex while dispatching converted port-info requests, matching the native ioctl path. All translated port-info commands share this helper, so their accesses to the client port state are serialized as well.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98655",
                                "url": "https://ubuntu.com/security/CVE-2026-98655",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  perf: Require kernel access for text poke events  Perf events with exclude_kernel=1 can be opened without kernel perf access. However, exclude_kernel does not suppress text-poke sideband records. Every PERF_RECORD_TEXT_POKE is marked PERF_RECORD_MISC_KERNEL and contains a raw kernel instruction address.  An unprivileged task can therefore open and mmap a task-local software event with text_poke=1. Both opening a count-only tracepoint event and configuring UDP GRO for ESP-in-UDP cause updates to inline static calls; the observer receives the relocated addresses of the modified instructions. For a known kernel image, any such address reveals the runtime kernel text base despite KASLR.  Call perf_allow_kernel() whenever attr.text_poke is set, regardless of exclude_kernel. Events that neither monitor kernel execution nor request text-poke records retain their existing permissions.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98750",
                                "url": "https://ubuntu.com/security/CVE-2026-98750",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  tty: fix saved termios reset race  Resetting saved termios state on device registration is needed where a minor number can be reused for an entirely different device and where the old settings may prevent the port from even being opened (e.g. when CLOCAL is not set).  Not all TTY drivers guarantee that the minor number is no longer in use when registering devices however, something which can lead to a use-after-free when closing a TTY (and saving its termios) races with re-registration.  Add a new TTY_DRIVER_RESET_SAVED_TERMIOS flag to request that any saved termios state is reset on registration and only set it for drivers that make sure that the minor number is no longer in use.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-89638",
                                "url": "https://ubuntu.com/security/CVE-2026-89638",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  smb: client: clear setuid/setgid bit on write with cifsacl/modefromsid/posix extensions  When a file has the setuid or setgid bit set and is written to, the VFS strips those bits and issues a setattr with ATTR_KILL_SUID/ATTR_KILL_SGID together with an ATTR_MODE carrying the already-cleared mode.  Both cifs_setattr_unix() and cifs_setattr_nounix() unconditionally dropped ATTR_MODE in that case:  \t/* skip mode change if it's just for clearing setuid/setgid */ \tif (attrs->ia_valid & (ATTR_KILL_SUID|ATTR_KILL_SGID)) \t\tattrs->ia_valid &= ~ATTR_MODE;  This is fine for the default mount, where the mode is only emulated via the DOS read-only attribute and cannot represent the setuid/setgid bits anyway.  However, with the \"cifsacl\" or \"modefromsid\" mount options the mode is stored on the server through an ACL (id_mode_to_cifs_acl()), with the SMB3.1.1 POSIX extensions the mode is sent to the server directly, and with the SMB1 Unix extensions (cifs_setattr_unix) the mode is sent via CIFSSMBUnixSetPathInfo().  In all those cases dropping ATTR_MODE means the cleared mode is never pushed to the server, so the setuid/setgid bit survives the write.  This is a security issue: on local filesystems the setuid bit is stripped when a file is written, but over these cifs.ko mounts the bit persists on the server, potentially allowing an unexpected privilege escalation on subsequent execution.  Fix this in two places:    1. cifs_setattr_nounix(): only take the \"skip mode change\" shortcut      when the mode is emulated via the DOS read-only attribute (i.e.      neither cifsacl/modefromsid nor the SMB3.1.1 POSIX extensions are      in effect), so that the cleared mode is propagated to the server      in the ACL / POSIX cases.    2. cifs_setattr_unix(): this function is only called when Unix      extensions are in effect, so the mode is always stored on the      server.  Remove the shortcut entirely so that the cleared mode is      always pushed.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-09-11 20:19:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98375",
                                "url": "https://ubuntu.com/security/CVE-2026-98375",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  xen/netfront: drop RX packets with a short Ethernet header  handle_incoming_queue() pulls pull_to bytes into the head before calling eth_type_trans().  pull_to is the length of the first RX slot, capped at RX_COPY_THRESHOLD, and that length comes from the backend. Nothing checks it against ETH_HLEN.  If the first slot is shorter than ETH_HLEN and more slots follow, the head ends up shorter than an Ethernet header while skb->len is longer, and eth_type_trans() BUG()s in __skb_pull().  If the whole packet is shorter than ETH_HLEN, eth_type_trans() reads the header past the end of the data instead.  Pull at least ETH_HLEN, and drop the packet if that fails, which also drops packets too short to hold an Ethernet header.  This also checks the return value of the pull, which was ignored.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-09 08:16:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-89738",
                                "url": "https://ubuntu.com/security/CVE-2026-89738",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  usb: gadget: at91_udc: drain polled-VBUS timer/work before udc is freed  In polled-VBUS mode (board.vbus_pin && board.vbus_polled), probe arms a self-restarting cycle: at91_vbus_timer() schedules vbus_timer_work, and at91_vbus_timer_work() calls at91_vbus_update() and re-arms the timer via mod_timer(). Both recover the same udc through container_of and dereference it on every iteration.  Neither teardown path cancels this cycle. udc is devm-allocated, so it is freed after at91udc_remove() returns, and is likewise freed when probe fails and devres runs. A timer callback or work item that is pending or running at either point dereferences the freed udc.  Add at91_udc_shutdown_vbus_timer() and call it from at91udc_remove() and from the usb_add_gadget_udc() failure path in probe; the remaining probe error paths fail before the timer is armed. timer_shutdown_sync() waits for a running callback and clears timer->function, which makes the work handler's mod_timer() a permanent no-op; cancel_work_sync() then drains any pending or running work whose re-arm attempt now does nothing. The timer must be shut down first, since cancelling the work alone would let the timer re-queue it. The guard mirrors probe: in IRQ mode the timer and work_struct are never initialized.  This does not require a fault; a normal driver unbind can interleave with an already queued work item.  This issue was found by an in-house static analysis tool.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-09-11 20:20:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-89740",
                                "url": "https://ubuntu.com/security/CVE-2026-89740",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  serial: imx: serialize imx_uart_ports[] lifetime  imx_uart_probe() publishes its devm-allocated port in imx_uart_ports[] before uart_add_one_port() because console setup uses the table. The entry is not cleared when adding the port fails or after removal, leaving a dangling pointer.  A sibling probe can register the shared console through that stale entry. This was reproduced under KASAN on QEMU mcimx6ul-evk by unbinding a sibling UART, unbinding the console UART and rebinding the sibling.  Keep the entry valid through uart_remove_one_port(), then clear it. Protect port addition and removal together with their table updates so sibling operations cannot interleave. Reject an occupied slot rather than clobbering an active port during a duplicate-line probe.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-09-11 20:20:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-74341",
                                "url": "https://ubuntu.com/security/CVE-2026-74341",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: wcn36xx: fix heap overflow from oversized firmware HAL response  The firmware response dispatcher copies all synchronous HAL responses into the 4096-byte hal_buf without validating the response length. A response exceeding WCN36XX_HAL_BUF_SIZE causes a heap buffer overflow with firmware-controlled content.  Add a bounds check on the response length.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-08-15 06:22:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-74406",
                                "url": "https://ubuntu.com/security/CVE-2026-74406",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  vxlan: Fix potential null-ptr-deref in vxlan_gro_prepare_receive().  udp_tunnel_sock_release() could set sk->sk_user_data to NULL while vxlan_gro_prepare_receive() is running.  Let's check if rcu_dereference_sk_user_data() is NULL after skb_gro_remcsum_init().",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-08-15 06:22:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-46265",
                                "url": "https://ubuntu.com/security/CVE-2026-46265",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  RDMA/hns: Fix WQ_MEM_RECLAIM warning  When sunrpc is used, if a reset triggered, our wq may lead the following trace:  workqueue: WQ_MEM_RECLAIM xprtiod:xprt_rdma_connect_worker [rpcrdma] is flushing !WQ_MEM_RECLAIM hns_roce_irq_workq:flush_work_handle [hns_roce_hw_v2] WARNING: CPU: 0 PID: 8250 at kernel/workqueue.c:2644 check_flush_dependency+0xe0/0x144 Call trace:   check_flush_dependency+0xe0/0x144   start_flush_work.constprop.0+0x1d0/0x2f0   __flush_work.isra.0+0x40/0xb0   flush_work+0x14/0x30   hns_roce_v2_destroy_qp+0xac/0x1e0 [hns_roce_hw_v2]   ib_destroy_qp_user+0x9c/0x2b4   rdma_destroy_qp+0x34/0xb0   rpcrdma_ep_destroy+0x28/0xcc [rpcrdma]   rpcrdma_ep_put+0x74/0xb4 [rpcrdma]   rpcrdma_xprt_disconnect+0x1d8/0x260 [rpcrdma]   xprt_rdma_connect_worker+0xc0/0x120 [rpcrdma]   process_one_work+0x1cc/0x4d0   worker_thread+0x154/0x414   kthread+0x104/0x144   ret_from_fork+0x10/0x18  Since QP destruction frees memory, this wq should have the WQ_MEM_RECLAIM.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-06-03 18:16:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98681",
                                "url": "https://ubuntu.com/security/CVE-2026-98681",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  smb: client: split cifsFileInfo bitfields to avoid shared-byte RMW races  The invalidHandle, swapfile, oplock_break_cancelled, offload, and status_file_deleted fields are stored in the same bitfield byte in struct cifsFileInfo, but are updated in different code paths that may run simultaneously, and are protected by different locks.  Since bitfield assignments generate byte-level read-modify-write operations, a modification to one flag can overwrite a concurrent modification to another flag.  To avoid these races, convert these flags from a bitfield to separate bool fields.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-89539",
                                "url": "https://ubuntu.com/security/CVE-2026-89539",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  SUNRPC: reject duplicate CREDS_VALUE options  gssx_dec_option_array() walks the wire-supplied option array and, for every entry whose name matches CREDS_VALUE, calls gssx_dec_linux_creds() on the same struct svc_cred. That helper unconditionally installs a fresh groups_alloc() result into creds->cr_group_info without releasing whatever pointer was already there:      for (i = 0; i < count; i++) {         ... decode name ...         if (length == sizeof(CREDS_VALUE) &&             memcmp(p, CREDS_VALUE, sizeof(CREDS_VALUE)) == 0) {             err = gssx_dec_linux_creds(xdr, creds);             ...         }     }  A reply that carries two CREDS_VALUE entries therefore overwrites cr_group_info on the second iteration and orphans the group_info allocated by the first call. The earlier free_creds path only releases the last cr_group_info via free_svc_cred(), so the first allocation's refcount stays at one and its kvmalloc-backed storage is leaked. No in-tree caller of gssp_accept_sec_context_upcall() expects more than one CREDS_VALUE per reply.  Fix by tracking whether a CREDS_VALUE option has already been decoded and returning -EINVAL on any subsequent match, so the free_creds path releases the single group_info that was installed.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-09-11 20:19:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-93179",
                                "url": "https://ubuntu.com/security/CVE-2026-93179",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  drm/amd/powerplay: fix VoltageObjectInfo zero-stride loop and OOB read  Reject voltage objects whose usSize is smaller than the header or would advance the cursor past the table end, preventing an infinite loop or heap OOB read when the VBIOS supplies a malformed VoltageObjectInfo table.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-09-17 17:18:00 UTC"
                            },
                            {
                                "cve": "CVE-2023-52561",
                                "url": "https://ubuntu.com/security/CVE-2023-52561",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  arm64: dts: qcom: sdm845-db845c: Mark cont splash memory region as reserved  Adding a reserved memory region for the framebuffer memory (the splash memory region set up by the bootloader).  It fixes a kernel panic (arm-smmu: Unhandled context fault at this particular memory region) reported on DB845c running v5.10.y.",
                                "cve_priority": "low",
                                "cve_public_date": "2024-03-02 22:15:00 UTC"
                            },
                            {
                                "cve": "CVE-2023-53651",
                                "url": "https://ubuntu.com/security/CVE-2023-53651",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  Input: exc3000 - properly stop timer on shutdown  We need to stop the timer on driver unbind or probe failures, otherwise we get UAF/Oops.",
                                "cve_priority": "low",
                                "cve_public_date": "2025-10-07 16:15:00 UTC"
                            },
                            {
                                "cve": "CVE-2023-53733",
                                "url": "https://ubuntu.com/security/CVE-2023-53733",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net: sched: cls_u32: Undo tcf_bind_filter if u32_replace_hw_knode  When u32_replace_hw_knode fails, we need to undo the tcf_bind_filter operation done at u32_set_parms.",
                                "cve_priority": "medium",
                                "cve_public_date": "2025-10-24 12:15:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98657",
                                "url": "https://ubuntu.com/security/CVE-2026-98657",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  iio: proximity: pulsedlight: fix iio_device left registered on PM setup failure  pm_runtime_set_active() failing in probe() jumps to error_unreg_buffer, which only calls iio_triggered_buffer_cleanup() -- it does not undo the iio_device_register() that already succeeded a few lines above. probe() then returns the error, the devm-managed indio_dev is freed, but the iio core still has it registered: the sysfs/chardev nodes stay live and point at freed memory.  Add an error_unreg_dev label that unregisters the iio device before falling through to the existing buffer cleanup, mirroring the teardown order already used in lidar_remove().",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98662",
                                "url": "https://ubuntu.com/security/CVE-2026-98662",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  iio: light: gp2ap020a00f: drain irq_work after free_irq  The threaded IRQ handler queues data->work through irq_work_queue() so the trigger is polled from a per-CPU context.  free_irq() does not flush an irq_work the handler already queued, so after gp2ap020a00f_remove() returns that work may still run and call iio_trigger_poll() on data->trig, which the devm cleanup has already freed, causing a use-after-free.  Add irq_work_sync(&data->work) after free_irq() in remove() and in the probe error path, mirroring commit 78601726d4a5 (\"iio: trigger: sysfs: fix use-after-free on remove\").  Found by an in-house static analysis tool, confirmed by manual review.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98663",
                                "url": "https://ubuntu.com/security/CVE-2026-98663",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  iio: imu: adis16480: fix unprotected debugfs reads  The firmware_revision and firmware_date file operations are open coded and never call debugfs_file_get(), which debugfs_create_file_unsafe() requires. debugfs_remove_recursive() therefore does not wait for a read in progress, and unbind frees the iio_dev underneath it.  Use debugfs_create_file() instead.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98664",
                                "url": "https://ubuntu.com/security/CVE-2026-98664",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  iio: imu: adis16400: fix unprotected debugfs reads  adis16400_serial_number_fops is open coded and never calls debugfs_file_get(), so debugfs_remove_recursive() does not wait for a read in progress and unbind frees the iio_dev underneath it.  Commit ae1d37a9bb4b (\"iio: imu: adis16400: use DEFINE_DEBUGFS_ATTRIBUTE instead of DEFINE_SIMPLE_ATTRIBUTE\") converted product_id and flash_count to DEFINE_DEBUGFS_ATTRIBUTE, which protects itself, but moved all three files to debugfs_create_file_unsafe().  serial_number prints three registers as \"%.4x-%.4x-%.4x\" and DEFINE_DEBUGFS_ATTRIBUTE() formats a single u64, so it cannot be converted without changing what the file returns. adis16475 and adis16550 already use debugfs_create_file() for their open coded files. Use it here too.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98666",
                                "url": "https://ubuntu.com/security/CVE-2026-98666",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  iio: gyro: adis16136: fix unprotected debugfs reads  The serial_number file operations are open coded and never call debugfs_file_get(), which debugfs_create_file_unsafe() requires. debugfs_remove_recursive() therefore does not wait for a read in progress, and unbind frees the iio_dev underneath it.  Use debugfs_create_file() instead.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98671",
                                "url": "https://ubuntu.com/security/CVE-2026-98671",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  iio: adc: sun4i-gpadc-iio: clean up on thermal zone registration failure  If devm_thermal_of_zone_register() fails, probe returns without unregistering the IIO map array or disabling runtime PM.  Jump to err_map to release them.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98679",
                                "url": "https://ubuntu.com/security/CVE-2026-98679",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  iio: accel: kxcjk-1013: reject duplicate event disable  The IIO core does not filter duplicate writes to the event enable attribute. kxcjk1013_write_event_config() already ignores repeated enable requests, but a repeated disable request still calls kxcjk1013_set_power_state(data, false), dropping a runtime PM reference that was not acquired for this request. This can underflow the runtime PM usage count and trigger a \"Runtime PM usage count underflow\" warning.  Return early when the requested state already matches ev_enable_state.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98687",
                                "url": "https://ubuntu.com/security/CVE-2026-98687",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  thunderbolt: Reject oversized XDomain properties responses  tb_xdp_properties_request() allocates room for 45 data dwords in its 252-byte response buffer.  The XDomain length field is six bits wide, however, and a malicious peer can set it to 63.  After the fixed response fields are subtracted, the driver treats this as 48 data dwords.  Commit 322e93448d90 (\"thunderbolt: Clamp XDomain response data copy to allocation size\") only bounds the copy against data_len.  If data_len is at least 48, memcpy() reads 192 bytes from the 180-byte res->data array, causing a 12-byte heap out-of-bounds read.  Commit 4db2bd2ed478 (\"thunderbolt: Limit XDomain response copy to actual frame size\") limits the earlier copy but does not constrain this header-derived length.  Reject response data lengths that exceed the allocated source buffer before copying them into the assembled property block.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98697",
                                "url": "https://ubuntu.com/security/CVE-2026-98697",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  USB: serial: fix dynamic id driver deregistration race  Only free the dynamic ids after having deregistered the driver and removed the \"new_id\" attribute to avoid leaking any id added by a racing write to the attribute.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98698",
                                "url": "https://ubuntu.com/security/CVE-2026-98698",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: mac80211: handle empty FILS association request payload  fils_encrypt_assoc_req() accepts a (Re)Association Request frame whose last element is the FILS Session element.  crypt_len is then zero and aes_siv_encrypt() is called with an empty plaintext.  kmemdup() returns ZERO_SIZE_PTR for a zero-length allocation, so the unconditional sg_init_one() puts an invalid page into the scatterlist. With CONFIG_DEBUG_SG this triggers a kernel BUG in sg_set_buf(); without the debug check the bogus page is handed to the crypto backend.  AES-SIV is defined for empty plaintext and the S2V result is then the complete output, so handle this case before the CTR step, which has nothing to encrypt.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98701",
                                "url": "https://ubuntu.com/security/CVE-2026-98701",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: mac80211: release mesh path quota on failed additions  Repeated failed or duplicate mesh path additions can exhaust MESH_MAX_MPATHS while the path table holds fewer paths, which stops new paths to reachable destinations from being created.  mesh_path_add() reserves a slot before allocating and inserting a path. If allocation fails, the function returns without releasing the slot. If the rhashtable insertion reports an error or an existing destination, the function discards its candidate but retains the reservation. No new path is installed in any of these cases.  Release the reservation whenever the candidate is not installed.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98703",
                                "url": "https://ubuntu.com/security/CVE-2026-98703",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: mac80211: minstrel_ht: validate fixed rate index  The fixed_rate_idx debugfs file is a plain u32 attribute, so any value can be written to it.  minstrel_ht_update_stats() then copies the value into mi->max_tp_rate[] and mi->max_prob_rate, and minstrel_ht_set_rate() uses MI_RATE_GROUP()/MI_RATE_IDX() to index minstrel_mcs_groups[] (42 entries) and mi->groups[].rates[] (10 entries) with it.  Writing e.g. 65535 selects group 4095 and rate index 15, far outside both arrays.  The out-of-bounds entries are dereferenced and updated as struct minstrel_rate_stats (retry counts, etc.), so the invalid index corrupts adjacent kernel memory.  With CONFIG_UBSAN_BOUNDS the access is reported as an array-index-out-of-bounds in minstrel_ht_set_rate().  Only a valid group/rate pair, or U32_MAX to disable fixed rate processing, can be used safely, so reject any other value when the debugfs file is written.  The file is only reachable through a root-only debugfs mount, so this is not a privilege boundary.  The out-of-bounds access is still a bug that must not be reachable through a writable debugfs attribute.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98706",
                                "url": "https://ubuntu.com/security/CVE-2026-98706",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: mac80211: drain PS delivery work during station teardown  Removing an AP or mesh station can notify the driver and wake TXQs after the station has already been removed from the driver, and can update num_sta_ps and the power-save queues after station cleanup has purged them.  sta_deliver_ps_frames() tests sta->dead only before it starts delivery. A worker that passes that test can be delayed while teardown sets sta->dead and removes the station from the driver; when it resumes it still runs the full delivery.  The existing cancel_work_sync() sits near the end of __cleanup_single_sta(), after the final driver state transition and after PS accounting and queue purging, so it drains the worker only once the state it has to protect has already changed. Before commit d34ba2168a3c (\"mac80211: don't delay station destruction\") cleanup was deferred through the same ordered workqueue as the delivery work, which kept the two ordered.  Cancel the work after setting sta->dead and before moving the driver state, and move the existing cancellation to the start of __cleanup_single_sta(). The first drain closes the driver-lifetime window; driver callbacks during the remaining state transitions can still queue drv_deliver_wk through ieee80211_sta_block_awake(), so retain the second drain at the start of __cleanup_single_sta(). That drain also covers insertion failures, which reach cleanup without setting sta->dead.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98710",
                                "url": "https://ubuntu.com/security/CVE-2026-98710",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: iwlegacy: 3945: free EEPROM data on remove  il3945_pci_probe() calls il_eeprom_init(), which allocates memory for the EEPROM data. The probe failure paths release this allocation with il_eeprom_free(), but the remove path does not free it after a successful probe.  As a result, the EEPROM data is leaked when the PCI device is removed.  Free the EEPROM data in il3945_pci_remove() before releasing the mac80211 hardware structure.  This issue was found by manual code inspection.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98711",
                                "url": "https://ubuntu.com/security/CVE-2026-98711",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: cw1200: fix TX padding OOB read leaking heap data to device  The TX path rounds the transfer size up to the bus alignment (align_size(), up to 511 bytes for SDIO, 1 byte for SPI) but sends the padded length straight from the frame buffer, which has no room reserved for the padding.  cw1200_data_write() therefore reads past the end of the frame and the bus transfer carries those bytes to the device.  A bogus device can collect up to 511 bytes of kernel heap data per TX frame.  The RX path does not have this problem: it allocates the skb with the aligned length (alloc_len) before reading.  Compute the exact padding with the bus align_size() callback, make sure queued TX frames have tailroom for it, and zero the padding bytes before the transfer so nothing past the frame is exposed.  This is not expected to change driver behavior on most cases: frame contents and transfer sizes are unchanged, only the content of the padding bytes (previously undefined stale memory, now zero), which the device never reads since the WSM header carries the real frame length.  The skb expansion can only fail under memory exhaustion, in which case the frame is dropped like on the existing error paths of cw1200_tx().  Discovered by Atuin - Automated Vulnerability Discovery Engine.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98721",
                                "url": "https://ubuntu.com/security/CVE-2026-98721",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  mtd: rawnand: cadence: Initialize IRQ state before requesting IRQ  The Cadence NAND interrupt handler uses both the IRQ lock and completion object. Registering the IRQ before initializing them leaves a window in which a pending interrupt can access uninitialized synchronization state.  Initialize them before registering the handler.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98726",
                                "url": "https://ubuntu.com/security/CVE-2026-98726",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  nvme-multipath: fix underflow in ANA log bounds checks  The number of ANA groups advertised through Identify Controller sizes the ANA log buffer. The ANA log header and group descriptors independently supply the number of groups and namespace IDs to parse.  Both bounds checks subtract an untrusted object size from ana_log_size before comparing the current offset. If the object is larger than the buffer, the size_t subtraction underflows and lets the parser read beyond ana_log_buf.  Check the current offset before the first subtraction and compare each object size with the remaining buffer instead. This rejects inconsistent ANA data before dereferencing a truncated group descriptor or walking an oversized namespace ID array.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98856",
                                "url": "https://ubuntu.com/security/CVE-2026-98856",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  kprobes: Skip disarmed probes when checking optkprobe overlap  On x86, an optkprobe at A replaces five bytes with a jump. If a disabled probe B is at A+2, get_optimized_kprobe() stops at B when arming a new probe C at A+4. It leaves A optimized:                A    A+1  A+2  A+3  A+4   A's jump  | e9 | d0 | d1 | d2 | d3 |   after C   | e9 | d0 | d1 | d2 | cc |  The INT3 for C overwrites the last byte of A's jump displacement, so execution can jump to the wrong address. B can have prepared optinsns while disarmed, but has no jump to unoptimize.  Continue past disarmed and unprepared probes to find the active optimized probe before arming a probe in its jump.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98857",
                                "url": "https://ubuntu.com/security/CVE-2026-98857",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ipvs: bound LBLCR and LBLC cache growth  ip_vs_lblcr_new() and ip_vs_lblc_new() create cache entries for every previously unseen destination address. The table max_size only tells the periodic collector to reclaim entries after the cache has already exceeded the limit. It does not reclaim entries that the attacker continues to use.  Reject new cache entries once either table reaches max_size * 3 / 2. The extra headroom lets the periodic collector catch up while the existing scheduler fallback continues to use the selected destination when cache creation fails. New traffic therefore stays serviceable without growing the tables further.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98732",
                                "url": "https://ubuntu.com/security/CVE-2026-98732",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  Bluetooth: btintel: fix buffer over-read in btintel_hw_error()  The \"Exception info %s\" print uses skb->data + 1, but the 12-byte payload is not guaranteed to be NUL-terminated and can be read past its end.  Bound the print with \"%.*s\" and skb->len - 1.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98735",
                                "url": "https://ubuntu.com/security/CVE-2026-98735",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  Bluetooth: hci_core: Serialize ACL scheduling with channel deletion  hci_chan_sent() selects a channel under RCU but drops the read lock before accessing chan->conn and returning the channel. The ACL and LE schedulers then use its packet queue and update its transmit counters without any protection against channel deletion.  After TX selects a channel and releases RCU, a disconnect command timeout on the separate request workqueue can run hci_conn_failed() and l2cap_conn_del(). hci_chan_del() can then unlink the channel, complete synchronize_rcu(), purge its queue and free it before TX resumes. This causes use-after-free both in hci_chan_sent() and in its callers.  KASAN reported:    BUG: KASAN: slab-use-after-free in hci_chan_sent+0x892/0x9b0   Workqueue: hci0 hci_tx_work   Call Trace:    hci_chan_sent+0x892/0x9b0    hci_tx_work+0x5e6/0xb70   Allocated by task 91:    hci_chan_create+0xe3/0x350    l2cap_conn_add.part.0+0x12/0xa30    l2cap_chan_connect+0x110d/0x1b60    l2cap_sock_connect+0x310/0x530   Freed by task 99:    hci_chan_del+0x11f/0x170    l2cap_conn_del+0x4f1/0x800    l2cap_connect_cfm+0x88c/0xd30    hci_conn_failed+0x150/0x250    hci_abort_conn_sync+0x3e3/0x800    hci_cmd_sync_run+0x7e/0xc0    hci_abort_conn+0x105/0x1f0    disconnect_sync+0x157/0x290    hci_cmd_sync_work+0x13c/0x290  Hold the existing device mutex across channel selection and transmission in both schedulers to serialize them with channel teardown. Keep timeout handling outside the critical sections because hci_link_tx_to() acquires the same mutex. This also permits the transmit path to sleep, unlike extending the RCU read-side critical section across packet submission.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98739",
                                "url": "https://ubuntu.com/security/CVE-2026-98739",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  Bluetooth: RFCOMM: Fix initial port reference race  For RFCOMM_RELEASE_ONHUP devices, rfcomm_tty_install() and __rfcomm_release_dev() both use RFCOMM_TTY_OWNED to decide who drops the initial tty_port reference. The release path tests the bit separately from the install path setting it, so both can drop that reference.  The synchronous hangup does not prevent this race: port->tty is not assigned until tty_port_open(), after installation. The following interleaving is possible:    1. Install and release each obtain a reference with rfcomm_dev_get().   2. Release observes RFCOMM_TTY_OWNED clear.   3. Install sets RFCOMM_TTY_OWNED and drops the initial reference.   4. Release drops the same initial reference again.   5. TTY cleanup drops its reference and frees the device.   6. Release performs its final tty_port_put() on the freed port.  KASAN reported:    BUG: KASAN: slab-use-after-free in tty_port_put+0x22/0x190   Write of size 4 at addr ffff8881001d3d5c by task poc/92    Call Trace:    tty_port_put+0x22/0x190    rfcomm_dev_ioctl+0x1d4/0x1930    sock_do_ioctl+0x110/0x260    sock_ioctl+0x380/0x590    __x64_sys_ioctl+0x134/0x1c0    Allocated by task 88:    rfcomm_dev_ioctl+0x8f6/0x1930    sock_do_ioctl+0x110/0x260    sock_ioctl+0x380/0x590    __x64_sys_ioctl+0x134/0x1c0    Freed by task 65:    kfree+0x131/0x3c0    rfcomm_dev_destruct+0x23b/0x2f0    release_one_tty+0xc1/0x370    process_one_work+0x661/0x1090  Use test_and_set_bit() in both paths so that only the caller that changes RFCOMM_TTY_OWNED from clear to set drops the initial reference. Each path keeps its own lookup reference until release or TTY cleanup, preserving the existing callback ordering and error handling.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98741",
                                "url": "https://ubuntu.com/security/CVE-2026-98741",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ALSA: ua101: reject mismatched capture/playback packet sizes  detect_usb_format() cross-checks bSubframeSize, bBitResolution and tSamFreq between the capture and playback interfaces, but never relates the two endpoints' wMaxPacketSize and bNrChannels.  Each playback URB gets a buffer of ua->playback.max_packet_bytes, while the number of bytes written into it is derived from the capture stream: capture_urb_complete() computes frames from the received capture packet and capture.frame_bytes, and start_usb_playback() and playback_work() multiply that by playback.frame_bytes.  A device declaring a large capture wMaxPacketSize with few capture channels and a small playback wMaxPacketSize with many playback channels therefore memset()s and memcpy()s past the end of the playback buffer, in open() of the PCM node the driver registers during probe. usb_submit_urb() rejects the over-long iso_frame_desc[0].length with -EMSGSIZE, but only after the write.  Reject such descriptors at probe time.  Genuine UA-101/UA-1000 hardware declares proportional packet sizes and is unaffected.    BUG: KASAN: slab-out-of-bounds in start_usb_playback (sound/usb/misc/ua101.c:586)   Write of size 2048 at addr ffff8881098f3c00 by task exploit/5021   Call Trace:    __asan_memset (mm/kasan/shadow.c:84)    start_usb_playback (sound/usb/misc/ua101.c:586)    playback_pcm_open (sound/usb/misc/ua101.c:679)    snd_pcm_open_substream (sound/core/pcm_native.c:2829)    snd_pcm_open (sound/core/pcm_native.c:2865 sound/core/pcm_native.c:2932)    snd_pcm_playback_open (sound/core/pcm_native.c:2891)    snd_open (sound/core/sound.c:166)    chrdev_open (fs/char_dev.c:411)    do_dentry_open (fs/open.c:996)    vfs_open (fs/open.c:1101)    path_openat (fs/namei.c:4837 fs/namei.c:5000)    do_file_open (fs/namei.c:5029)    do_sys_openat2 (fs/open.c:1417)    __x64_sys_openat (fs/open.c:1423 fs/open.c:1439 fs/open.c:1434)    do_syscall_64 (arch/x86/entry/syscall_64.c:61 arch/x86/entry/syscall_64.c:84)    entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:121)    The buggy address belongs to the object at ffff8881098f3c00    which belongs to the cache kmalloc-192 of size 192   The buggy address is located 0 bytes inside of    allocated 168-byte region [ffff8881098f3c00, ffff8881098f3ca8)",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98940",
                                "url": "https://ubuntu.com/security/CVE-2026-98940",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ASoC: qcom: lpass-cpu: use DAI table index for playback constraints  The DAI ID is a hardware port ID and is not necessarily the index of the corresponding entry in variant->dai_driver.  When configuring a DAI with LPAIF_I2SCTL_MODE_QUAD01, the probe code currently uses dai_id to index variant->dai_driver. This is incorrect for platforms where DAI IDs are sparse. For example, the IPQ806x MI2S DAI has ID 4 while it is the only entry in the DAI driver table. If that DAI is configured for QUAD01 and probe reaches this branch, the code writes beyond that single entry via dai_driver[4] instead of updating the DAI being processed.  Use the loop index i when updating the current DAI's playback channel constraints, while retaining dai_id for indexing the hardware-port specific playback SD-line mode array.  This fixes the incorrect DAI table access for platforms where the DAI ID does not match its position in the driver table.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98748",
                                "url": "https://ubuntu.com/security/CVE-2026-98748",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  serial: 8250_bcm7271: fix use-after-free in brcmuart_remove()  brcmuart_handle_irq() starts priv->hrt to work around a receive-timeout quirk of the 8250 core when hardware flow control is enabled; the timer callback brcmuart_hrtimer_func() dereferences priv.  brcmuart_remove() cancels the hrtimer before it unregisters the port, so a receive-timeout interrupt that arrives in between re-arms the timer. After devm frees priv, the callback runs on freed memory.  Unregister the port before cancelling the hrtimer. serial8250_unregister_port() shuts the port down and frees its IRQ, so brcmuart_handle_irq() can no longer restart the timer, and the final hrtimer_cancel() drains any timer that was armed before or during the unregister.  This issue was found by an in-house static analysis tool.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98754",
                                "url": "https://ubuntu.com/security/CVE-2026-98754",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  tty: vcc: hold port lock when clearing tty pointer in vcc_cleanup  vcc_cleanup() sets port->tty to NULL without holding port->lock, racing with vcc_event() LDC callbacks that read port->tty under port->lock and then use tty->port. This can cause a use-after-free when the callback dereferences tty->port after cleanup has already destroyed and freed it.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98755",
                                "url": "https://ubuntu.com/security/CVE-2026-98755",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  tty: vcc: zero-initialize control packet in vcc_send_ctl()  The stack-allocated struct vio_vcc pkt was partially initialized, leaving the tag.stype_env field uninitialized before being sent via ldc_write(), potentially leaking kernel stack data to the LDC peer.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98756",
                                "url": "https://ubuntu.com/security/CVE-2026-98756",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  usb: cdns3: Fix NULL pointer dereference in cdns3_pci_probe  The Cadence USBSS controller is a two-function PCI device. The first probed function allocates the driver data and stores it with pci_set_drvdata(), while the second function reuses it via pci_get_drvdata() when pci_is_enabled() reports that the first function has already been probed.  When the second function is probed while the first one has been enabled but has not yet set its driver data, pci_get_drvdata() returns NULL, and the subsequent wrap->devfn assignment dereferences a NULL pointer and crashes the kernel. logs: Call trace:   cdns3_pci_probe+0xa4/0x300   local_pci_probe+0x44/0xa8   pci_call_probe+0x54/0x158   pci_device_probe+0x84/0x100   really_probe+0x184/0x3d0   __driver_probe_device+0x80/0x178   driver_probe_device+0x44/0xe8   __driver_attach+0xec/0x1f8   bus_for_each_dev+0x7c/0xe0   driver_attach+0x28/0x38   bus_add_driver+0x110/0x238   driver_register+0x64/0x128   __pci_register_driver+0x50/0x60   cdns3_pci_driver_init+0x28/0x38   do_one_initcall+0x5c/0x280   do_initcalls+0x104/0x1d8   kernel_init_freeable+0x140/0x218   kernel_init+0x28/0x1f8   ret_from_fork+0x10/0x20  Return -EPROBE_DEFER in this case so that probing is retried after the first function has completed its probe.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98757",
                                "url": "https://ubuntu.com/security/CVE-2026-98757",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  usb: cdns3: fix use-after-free in cdns3_gadget_exit()  cdns3_gadget_start() arms two works on system_freezable_wq: pending_status_wq for the deferred ep0 status stage and aligned_buf_wq for realigned request buffers. Both handlers use the cdns3_device the works are embedded in, and cdns3_pending_setup_status_handler() also calls the ep0 request completion.  cdns3_gadget_exit() does not wait for these works. It frees all endpoints and aligned buffers and drops the last reference to the gadget device, which frees priv_dev, so a work queued before the exit can run after the free.  Fix this by waiting for both works after the gadget driver is unbound and the IRQ is freed, when no new work can be queued, and before the endpoints and buffers are released.  This issue was found by an in-house static analysis tool.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98760",
                                "url": "https://ubuntu.com/security/CVE-2026-98760",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  usb: typec: tipd: fix uninitialized typec_partner_desc in tps6598x_connect()  tps6598x_connect() passes a stack-allocated typec_partner_desc to typec_register_partner() after initializing only usb_pd, accessory and identity.  typec_register_partner() copies attach and deattach from the descriptor into the partner. With those fields left unset, garbage function pointers may be stored and later invoked from typec_partner_link_device() when a USB device is linked to the port. Uninitialized pd_revision and usb_capability similarly leak stack data through partner sysfs.  Zero-initialize the descriptor so optional callbacks remain NULL and the remaining fields are zero.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98761",
                                "url": "https://ubuntu.com/security/CVE-2026-98761",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  usb: typec: tcpm: recover after failure to start the frs ams  Reset the port if the tcpm fails to start the FAST_ROLE_SWAP AMS by initiating error recovery on it.  This helps in cases where some cables (incorrectly) signal an FRS to an FRS capable port during disconnection. The TCPC autonomously starts sourcing VBUS on detecting the FRS signal. However, the VBUS sourcing is left on when the FAST_ROLE_SWAP AMS fails to start (as tcpm_sink_tx_ok is 0 as CC is open due to the cable disconnect). This is because the code sets the state to INVALID_STATE without resetting the port state.  Log snippet before changes: [  101.401960] AMS FAST_ROLE_SWAP start [  101.401971] Sink TX No Go [  101.401982] sourcing vbus [  101.401987] VBUS on [  101.402159] VBUS on [  109.257809] CC1: 0 -> 0, CC2: 5 -> 0 [state SNK_READY, polarity 1, disconnected] [  111.267442] VBUS on  After changes: [   70.541211] AMS FAST_ROLE_SWAP start [   70.541220] Sink TX No Go [   70.541228] state change SNK_READY -> ERROR_RECOVERY [rev3 NONE_AMS] [   70.541362] VBUS on [   70.541365] sourcing vbus [   70.541367] VBUS on [   70.541374] state change ERROR_RECOVERY -> PORT_RESET [rev3 NONE_AMS] [   70.541410] disable vbus discharge ret:0 [   70.543028] Setting usb_comm capable false [   70.544009] Setting voltage/current limit 0 mV 0 mA [   70.544034] polarity 0 [   70.544239] Requesting mux state 0, usb-role 0, orientation 0 [   70.555550] cc:=0 [   70.555595] pending state change PORT_RESET -> PORT_RESET_WAIT_OFF @ 100 ms [rev3 NONE_AMS] [   70.555697] VBUS off [   70.555702] VBUS VSAFE0V [   70.555762] CC1: 5 -> 0, CC2: 0 -> 0 [state PORT_RESET, polarity 0, disconnected] [   70.587794] VBUS off [   70.587799] VBUS VSAFE0V [   70.655672] state change PORT_RESET -> PORT_RESET_WAIT_OFF [delayed 100 ms] [   70.655682] state change PORT_RESET_WAIT_OFF -> SNK_UNATTACHED [rev3 NONE_AMS] [   70.655686] Start toggling [   70.656274] CC1: 0 -> 0, CC2: 0 -> 0 [state TOGGLING, polarity 0, disconnected]",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98763",
                                "url": "https://ubuntu.com/security/CVE-2026-98763",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  usb: core: clear both ep_in and ep_out for non-ep0 control endpoints  In usb_enable_endpoint(), non-zero control endpoints (where usb_endpoint_xfer_control(&ep->desc) is true) populate both dev->ep_in[epnum] and dev->ep_out[epnum] with the same struct usb_host_endpoint pointer.  However, usb_disable_endpoint() only clears either dev->ep_out[epnum] or dev->ep_in[epnum] depending on the direction bit of epaddr when reset_hardware is set, leaving the opposite direction's array slot pointing to the disabled/freed endpoint.  Clear both dev->ep_out[epnum] and dev->ep_in[epnum] when disabling a non-ep0 control endpoint with reset_hardware set, and update the function kerneldoc accordingly.  Tested in QEMU against Linux 7.3.0-rc3 using dummy_hcd and raw-gadget to enumerate a USB device with a non-zero control endpoint (bEndpointAddress 0x01, bmAttributes USB_ENDPOINT_XFER_CONTROL), verifying that both dev->ep_in[1] and dev->ep_out[1] are cleared when the interface is disabled.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98764",
                                "url": "https://ubuntu.com/security/CVE-2026-98764",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  usb: gadget: f_fs: Fix NULL pointer dereference in FUNCTIONFS_ENDPOINT_DESC  When user space sets up FunctionFS with only full-speed descriptors (e.g., flags = FUNCTIONFS_HAS_FS_DESC) and the gadget operates at a higher speed (such as USB_SPEED_HIGH or USB_SPEED_SUPER), config_ep_by_speed() detects that the function lacks descriptors for the current speed, logs a warning, and falls back to full-speed descriptors. The endpoint is then successfully enabled via usb_ep_enable(), and epfile->ep becomes valid.  However, when user space subsequently issues the FUNCTIONFS_ENDPOINT_DESC ioctl to query the endpoint descriptor, ffs_epfile_ioctl() selects the descriptor index solely based on gadget->speed:  \tswitch (epfile->ffs->gadget->speed) { \tcase USB_SPEED_SUPER: \tcase USB_SPEED_SUPER_PLUS: \t\tdesc_idx = 2; \t\tbreak; \tcase USB_SPEED_HIGH: \t\tdesc_idx = 1; \t\tbreak; \tdefault: \t\tdesc_idx = 0; \t} \tdesc = epfile->ep->descs[desc_idx]; \tmemcpy(&desc1, desc, desc->bLength);  Because user space only supplied full-speed descriptors, epfile->ep->descs[1] is NULL. Dereferencing desc->bLength triggers an immediate kernel NULL pointer dereference panic.  Fix this by falling back through lower speed descriptors if the current speed descriptor was not supplied, matching the fallback logic in config_ep_by_speed() and historical f_fs behavior. If still missing, fall back to epfile->ep->ep->desc (the active descriptor), and return -EINVAL safely if no valid descriptor is found. In addition, mark desc as const to match struct usb_ep::desc and avoid discarding qualifiers.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98765",
                                "url": "https://ubuntu.com/security/CVE-2026-98765",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  USB: gadget: dummy-hcd: Fix wait for outstanding request completions  The dummy-hcd driver emulates synchronize_irq() by waiting until its private callback_usage counter drops to 0 (with the private lock not held).  This counter is incremented whenever a gadget driver callback occurs (which requires the private lock to be dropped), but not when a request completion handler is called.  This is an oversight.  Request completion is triggered by timer interrupts (emulating device IRQs in a real UDC), and the interrupt handlers are supposed to have completed when the synchronize_irq() emulation routine returns -- they aren't supposed to be in the middle of a completion callback.  If this happens it can lead to a gadget driver's unbind routine running before all outstanding request completions have finished, maybe even allowing the gadget driver's module to be unloaded while a completion handler is still running.  Fix the oversight by incrementing the callback_usage value across request completion callbacks.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98766",
                                "url": "https://ubuntu.com/security/CVE-2026-98766",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  usb: gadget: aspeed-vhub: cancel wake work on device removal  wake_work is armed from the gadget .wakeup callback to resume suspended downstream ports, and it is never cancelled in ast_vhub_remove(), so a work item queued before or during removal can run after devm has freed vhub and its ports, a use-after-free.  Cancelling the work alone is not sufficient: usb_gadget_wakeup() takes no lock and the unbind path never clears wakeup_en, so a remote-wakeup request in flight on another CPU can re-arm the work after the cancel and before vhub is freed.  ast_vhub_del_dev() already clears d->registered under vhub->lock before unregistering the gadget. Refuse the wakeup in ast_vhub_udc_wakeup() once d->registered is clear: the check and the schedule_work() are then atomic against the unbind, so a wakeup that passed before the flag was cleared is drained by the cancel_work_sync() after the del_dev loop, and one that arrives later returns without arming. Also move INIT_WORK() to the top of ast_vhub_probe(), since the probe error path reuses ast_vhub_remove() and would otherwise cancel a never-initialized work item.  This issue was found by an in-house static analysis tool.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98769",
                                "url": "https://ubuntu.com/security/CVE-2026-98769",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  usb: gadget: f_uac1_legacy: validate bRequest index in generic_{set,get}_cmd  generic_set_cmd() and generic_get_cmd() use the low nibble of ctrl->bRequest as an index into con->data[]:      u8 cmd = (ctrl->bRequest & 0x0F);  /* 0 .. 15 */     ...     con->data[cmd] = value;            /* OOB when cmd >= 5 */  struct usb_audio_control (include/linux/usb/audio.h) declares data as a 5-element array, so indices 5 through 15 write (or read) up to 44 bytes past the end of the array on the heap.  A malicious USB host can craft a class-specific SET_CUR / GET_CUR request with an arbitrary bRequest value, triggering the out-of-bounds access from an IRQ completion handler with no further preconditions.  Add an ARRAY_SIZE() guard to both functions.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98771",
                                "url": "https://ubuntu.com/security/CVE-2026-98771",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  usb: storage: sierra_ms: reject short SWoC info transfers  sierra_get_swoc_info() requests sizeof(struct swoc_info) (60) bytes from the device via usb_control_msg(), but its callers only treat a negative return value as failure. A device that answers the vendor-specific GetSwocInfo request with a short IN transfer is therefore accepted, leaving the tail of the freshly allocated (kmalloc(), non-zeroing) swoc_info buffer uninitialized.  truinst_show() subsequently prints swocInfo->rev, swocInfo->LinuxSKU and swocInfo->LinuxVer from that buffer into the world-readable (0444) \"truinst\" sysfs attribute. An emulated/malicious USB device (VID 0x1199, PID 0x0fff) can exploit this to disclose up to 5 bytes of stale kernel heap memory (kmalloc-64) to unprivileged userspace, once per sysfs read, indefinitely. On kernels built without init_on_alloc this leaks recently freed heap contents.  Only accept the transfer when the full structure was received. sierra_ms_init() already retries failed queries, so well-behaved devices are unaffected.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98772",
                                "url": "https://ubuntu.com/security/CVE-2026-98772",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  USB: serial: fix port tear down use-after-free  Some drivers for multiport devices access port driver data from completion handlers of shared URBs submitted at attach() or first open() and stopped at disconnect() or last close(), respectively.  A simple NULL check before accessing the driver data makes sure that a port state container has at least been allocated, but a completion handler can still race with port tear down.  Reorder the disconnect handling so that ports are not deregistered (and their driver data freed) until after all ports have been hung up and the driver disconnect() callback has run so that all I/O has been stopped.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98775",
                                "url": "https://ubuntu.com/security/CVE-2026-98775",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  nitro_enclaves: fix use-after-free on SLOT_ALLOC failure  When ne_create_vm_ioctl() fails the SLOT_ALLOC request after anon_inode_getfile() has succeeded, the error path calls fput(enclave_file) and then frees ne_enclave.  In normal userspace context, fput() defers the final __fput() via task_work. ne_enclave_release() therefore runs after ne_enclave has already been freed and dereferences ne_enclave->slot_uid, causing a use-after-free: KASAN: slab-use-after-free in ne_enclave_release.  The enclave has no slot allocated and is not yet linked into the enclaves list on this error path, so ne_enclave_release() is expected to return early when slot_uid is zero. However, reading slot_uid already accesses the freed object.  Clear enclave_file->private_data before fput() on the error path. ne_enclave_release() then returns immediately when private_data is NULL, leaving the ioctl error path as the sole owner of ne_enclave. This is safe because the file has not been fd_install()'d yet.  Tested on an AWS EC2 m5.2xlarge with CONFIG_KASAN=y. Without the patch, the reproducer triggers a KASAN slab-use-after-free on every SLOT_ALLOC failure. With the patch, no KASAN report is produced and the SLOT_ALLOC error is still returned. Normal enclave creation and teardown are unaffected.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98790",
                                "url": "https://ubuntu.com/security/CVE-2026-98790",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  perf: Fix race between perf_event_exit_task() and perf_pending_task()  A race condition exists between perf_event_exit_task() and perf_pending_task() during begin_new_exec().  During begin_new_exec(), perf_event_exit_task() may be called, and the PF_EXITING flag is not set on task. So perf_sigtrap() continues to execute and triggers WARN_ON_ONCE(event->ctx->task != current).  Since both task exit and exec paths can call perf_event_exit_task() which sets ctx->task to TASK_TOMBSTONE, fix this by explicitly checking if event->ctx->task equals TASK_TOMBSTONE and dropping the redundant PF_EXITING check.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98934",
                                "url": "https://ubuntu.com/security/CVE-2026-98934",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ipv6: sr: use skb_get_hash_net() in seg6_make_flowlabel()  Since commit d58e468b1112 (\"flow_dissector: implements flow dissector BPF hook\") __skb_flow_dissect() needs a net pointer, either from skb->dev, skb->sk, or since commit 3cbf4ffba5ee (\"net: plumb network namespace into __skb_flow_dissect\") a caller provided pointer.  syzbot was able to reach seg6_make_flowlabel() with an skb having neither skb->dev nor skb->sk set: a TIPC UDP bearer sends a discovery message through an IPv4 route using seg6 encap, while net.ipv6.seg6_flowlabel is set to 1.  seg6_make_flowlabel() already has a net pointer, use skb_get_hash_net().  WARNING: net/core/flow_dissector.c:1131 at __skb_flow_dissect+0x910/0x5368 net/core/flow_dissector.c:1126, CPU#0: syz.0.17/4930 Call trace:   __skb_flow_dissect+0x910/0x5368 net/core/flow_dissector.c:1126 (P)   __skb_get_hash_net+0xe0/0x29c net/core/flow_dissector.c:1903   skb_get_hash include/linux/skbuff.h:1663 [inline]   seg6_make_flowlabel+0xcc/0x1ec net/ipv6/seg6_iptunnel.c:132   __seg6_do_srh_encap+0x320/0xbf4 net/ipv6/seg6_iptunnel.c:161   seg6_do_srh+0x4b4/0xa44 net/ipv6/seg6_iptunnel.c:431   seg6_output_core+0x164/0x688 net/ipv6/seg6_iptunnel.c:681   seg6_output+0x44/0x1ac net/ipv6/seg6_iptunnel.c:744   lwtunnel_output+0x3d0/0x664 net/core/lwtunnel.c:356   dst_output include/net/dst.h:470 [inline]   ip_local_out+0x110/0x148 net/ipv4/ip_output.c:131   iptunnel_xmit+0x50c/0xd38 net/ipv4/ip_tunnel_core.c:97   udp_tunnel_xmit_skb+0x220/0x348 net/ipv4/udp_tunnel_core.c:187   tipc_udp_xmit+0x75c/0x9c0 net/tipc/udp_media.c:202   tipc_udp_send_msg+0x214/0x374 net/tipc/udp_media.c:274   tipc_bearer_xmit_skb+0x260/0x3b0 net/tipc/bearer.c:576   tipc_enable_bearer net/tipc/bearer.c:366 [inline]   __tipc_nl_bearer_enable+0xc90/0xfb0 net/tipc/bearer.c:1048   tipc_nl_bearer_enable+0x2c/0x48 net/tipc/bearer.c:1057   genl_family_rcv_msg_doit+0x1e4/0x2d4 net/netlink/genetlink.c:1114",
                                "cve_priority": "negligible",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2022-49622",
                                "url": "https://ubuntu.com/security/CVE-2022-49622",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  netfilter: nf_tables: avoid skb access on nf_stolen  When verdict is NF_STOLEN, the skb might have been freed.  When tracing is enabled, this can result in a use-after-free: 1. access to skb->nf_trace 2. access to skb->mark 3. computation of trace id 4. dump of packet payload  To avoid 1, keep a cached copy of skb->nf_trace in the trace state struct. Refresh this copy whenever verdict is != STOLEN.  Avoid 2 by skipping skb->mark access if verdict is STOLEN.  3 is avoided by precomputing the trace id.  Only dump the packet when verdict is not \"STOLEN\".",
                                "cve_priority": "medium",
                                "cve_public_date": "2025-02-26 07:01:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98794",
                                "url": "https://ubuntu.com/security/CVE-2026-98794",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ipvs: filter some flags received in the backup server  While the IPVS SYNC protocol is not secure by design we can still protect the backup server from messages that can wreak havoc.  This commit addresses problems from received connection flags or their combinations. We now drop messages as follows:  1. the NO_CPORT+TEMPLATE combination allows lookups for normal connections to hit template which can break in many ways. While the master does not sync connections with NO_CPORT flag, i.e. before they are established, we still accept NO_CPORT without TEMPLATE.  2. ONE_PACKET: it is not sent by master, so we do not expect it in backup. Before now it was ignored by IP_VS_CONN_F_BACKUP_MASK for protocol v1 while protocol v0 created connections that are not hashed and dropped immediately. Better to apply the IP_VS_CONN_F_BACKUP_MASK also to the flags from v0 messages for consistency with v1.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98805",
                                "url": "https://ubuntu.com/security/CVE-2026-98805",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  tipc: prevent GCM nonce reuse on peer key changes  TIPC can encrypt traffic between nodes using a different transmit key for each node. In this mode, the AES-GCM nonce for a packet sent to a known peer consists of a 32-bit prefix (a per-key salt XOR the peer's address) followed by a 64-bit counter. That counter is stored in the peer's RX crypto object. When the peer reports a change in which key it uses to receive packets, TIPC resets this counter. The sender can still be using the same TX key and salt, so subsequent packets reuse earlier nonces. This nonce reuse breaks confidentiality and exposes GCM's authentication key. This makes forgeries trivial: an attacker can exploit CTR malleability to alter captured ciphertexts and use the recovered authentication key to compute a valid tag for the modified ciphertext, under the same key and nonce.  Use the TX key's existing aead->seqno counter instead. All encryptions using that key object share the same atomic counter, so concurrent encryptions get distinct nonce counter values. The counter survives key activation and peer reconnection, and peer key-status reports cannot reset it. This prevents those transitions from causing nonce reuse while the same TX key remains installed.  The nonce format is unchanged, and receivers do not require consecutive counter values, so sharing the counter across peers remains compatible with existing receivers. A pre-existing check still invokes key revocation in the unlikely event that the counter wraps to zero.",
                                "cve_priority": "critical",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98811",
                                "url": "https://ubuntu.com/security/CVE-2026-98811",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net/sched: cls_api: reclaim an empty proto on the error path  Two racing tc filter add requests on the same chain/prio of an unlocked classifier both run change() on the shared proto and both can fail: the winner's tcf_chain_tp_delete_empty() attempt gives up because the loser's handle is still in the idr, and the loser's error path drops only its own reference without a second reclamation attempt. The empty proto stays linked in the chain, holding the chain reference, a block reference and the classifier module reference until the chain or block is torn down.  Reclaim the proto on the error path of any failed request that holds a proto reference. The reclamation is emptiness-gated: tcf_chain_tp_delete_empty() unlinks the proto only when delete_empty() admits it is empty, so a live shared proto is never unlinked. A proto the request created is reclaimed unconditionally - it is the only owner, so marking it for deletion is safe even without a delete_empty callback. Classifiers without one (the check marks the proto unconditionally) are rtnl-serialized, so the raced window this guard closes cannot arise for them.  This is a follow-up to commit d4e359b3608a (\"net/sched: cls_api: fix teardown of an adopted proto on insert-race loss\"), which stopped the loser of the insert race from unlinking the winner's live proto but left the empty-proto residual in place.  Conditions to recreate: - CONFIG_NET_CLS_FLOWER=y; veth pair - tc qdisc add dev veth0 ingress - two concurrent `tc filter add dev veth0 ingress protocol ip pref 1   flower skip_sw ... action drop` (both fail in fl_hw_replace_filter   after publishing their handle in the idr); repeat in a loop - an empty flower tp stays linked after both requests fail; visible   as a bare `filter protocol ip pref 1 flower chain 0` header in   `tc filter show` with no filter entries - CAP_NET_ADMIN (namespace-local via unshare -Urn suffices)",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98812",
                                "url": "https://ubuntu.com/security/CVE-2026-98812",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net/mctp: publish the mctp_dev only after it is initialised  mctp_add_dev() links the new mctp_dev into dev->mctp_ptr before mdev->dev is assigned, so a reader that picks the device up in that window dereferences a net_device pointer that is still NULL:  KASAN: null-ptr-deref in range [0x00000000000000b0-0x00000000000000b7] Call Trace:  <TASK>  ? __pfx_mctp_sendmsg (./include/linux/sockptr.h:49)  ? __pfx_mctp_dst_output (net/mctp/route.c:41)  ? selinux_socket_sendmsg (security/selinux/hooks.c:5278)  ____sys_sendmsg (net/socket.c:775 (discriminator 1) net/socket.c:790  (discriminator 1) net/socket.c:2684 (discriminator 1))  ? __pfx_____sys_sendmsg (net/socket.c:1131)  ? __pfx_copy_msghdr_from_user (net/socket.c:2590)  ? update_cfs_rq_load_avg (kernel/sched/fair.c:5478)  ___sys_sendmsg (net/socket.c:2738)  ? __pfx____sys_sendmsg (net/socket.c:2625)  ? perf_event_task_tick (./include/linux/rcupdate.h:838)  ? sched_tick (kernel/sched/core.c:5818)  ? clockevents_program_event (kernel/time/clockevents.c:372)  ? fdget (./include/linux/rcupdate.h:873 fs/file.c:1100)  __sys_sendmsg (net/socket.c:2770)  ? __pfx___sys_sendmsg (net/socket.c:2751)  do_syscall_64 (arch/x86/entry/syscall_64.c:63)  entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:121)  </TASK>  Fix by publishing only once the object is fully initialised: __mctp_dev_get() runs under rcu_read_lock() only and hands this object to readers as soon as mctp_ptr is assigned, so they must never observe mdev->dev == NULL.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98819",
                                "url": "https://ubuntu.com/security/CVE-2026-98819",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  Bluetooth: btintel: validate DDC record lengths  Parse DDC record lengths in unsigned storage so 0xFF does not wrap. Reject records smaller than the mandatory three-byte header, records exceeding U8_MAX, and records exceeding remaining firmware bytes before issuing Intel_Write_DDC.  This issue was reported by Claude Mythos.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98823",
                                "url": "https://ubuntu.com/security/CVE-2026-98823",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: cfg80211: preserve hidden-group beacon IE ownership  A hidden-group probe-response entry borrows its beacon IEs from the group's beacon entry. cfg80211_update_assoc_bss_entry() can pass such an entry to cfg80211_update_known_bss() when merging scan entries after a channel switch.  Copying the borrowed beacon_ies into the associated entry gives the same allocation two owners. Releasing the group's beacon entry can then leave the associated entry pointing to freed IEs, which are freed again when that entry is released.  Skip beacon IE replacement when the source entry belongs to a hidden group. Preserve probe-response processing, the subsequent metadata updates, and the existing rejection path for conflicting hidden beacon updates.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98936",
                                "url": "https://ubuntu.com/security/CVE-2026-98936",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: ath11k: reset ar->num_stations on hardware start  When (multiple) hw restart occurs, we end up in a situation where we cannot accept new stations / mesh peers. This seems to be the 'num_stations' in 'struct ath11k' that did not get reset properly in this case. In ath11k_mac_op_start(), it was indeed the only accounting var that did not get reset so let's clear it too.  This avoids problems like those:  \t[1248828.088023] WARNING: CPU: 0 PID: 12281 at net/mac80211/util.c:1682 ieee80211_reconfig_stations+0x98/0xc0 \t[1248828.088115] Call trace: \t[1248828.088116]  ieee80211_reconfig_stations+0x98/0xc0 (P) \t[1248828.088119]  ieee80211_reconfig+0x774/0x1438 \t[1248828.088123]  ieee80211_restart_work+0x10c/0x178 \t[1248828.088127]  process_one_work+0x178/0x3c0 \t[1248828.088130]  worker_thread+0x280/0x440 \t[1248828.088133]  kthread+0xe0/0xf8 \t[1248828.088137]  ret_from_fork+0x10/0x20 \t[1248828.088141] ---[ end trace 0000000000000000 ]--- \t[1248836.686604] ath11k_pci 0000:04:00.0: refusing to associate station: too many connected already (128) \t[1248836.686609] ath11k_pci 0000:04:00.0: Failed to add station: xx:xx:xx:xx:xx:xx for VDEV: 1  Tested-on: QCN9074 hw1.0 PCI WLAN.HK.2.9.0.1-01977-QCAHKSWPL_SILICONZ-1",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98831",
                                "url": "https://ubuntu.com/security/CVE-2026-98831",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  of/overlay: don't leak fragment references when changeset init fails  init_overlay_changeset() stores the number of initialized fragments in ovcs->count only on full success. When find_target() or the __symbols__ lookup fails partway through, the target and overlay references taken for the fragments initialized so far are never dropped: free_overlay_changeset() bounds its cleanup loop by ovcs->count, which is still 0.  Store the running count on the error path so free_overlay_changeset() puts whatever was set up. The store is guarded by ovcs->fragments because on the allocation-failure path cnt still holds the counting pass total while there is no fragments array; everywhere else cnt only counts fully-initialized fragments.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98833",
                                "url": "https://ubuntu.com/security/CVE-2026-98833",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  mtd: core: call _get_device() with the master MTD  __get_mtd_device() calls the master's _get_device() callback with mtd, which may be a partition. __put_mtd_device() passes the master.  This breaks gluebi partitions because gluebi_get_device() uses container_of() and therefore requires the master MTD. Pass the master to _get_device(), matching _put_device().",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-89860",
                                "url": "https://ubuntu.com/security/CVE-2026-89860",
                                "cve_description": "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 second INIT_WORK() reinitializes a work item that is already queued, which can corrupt the workqueue list and lead to crashes or a looping worker.  Initialize priv->abort_work once at command submission, next to the existing per-command spin_lock_init(&priv->cmd_lock), and leave only schedule_work() in the abort paths. schedule_work() already does nothing when the work item is still pending, so a repeated abort no longer disturbs an in-flight work item. The command is not returned to the transport until the final kref_put()/release callback runs after abort_work has completed, so the work item is idle before priv is reused and the single submission-time INIT_WORK() is safe.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-09-16 11:16:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-53353",
                                "url": "https://ubuntu.com/security/CVE-2026-53353",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  hsr: Remove WARN_ONCE() in hsr_addr_is_self().  syzbot reported the warning [0] in hsr_addr_is_self(), whose assumption is simply wrong.  hsr->self_node is cleared in hsr_del_self_node(), which is called from hsr_dellink().  Since dev->rtnl_link_ops->dellink() is called before unregister_netdevice_many(), there is a window when user can find the device but without hsr->self_node.  Let's remove WARN_ONCE() in hsr_addr_is_self().  [0]: HSR: No self node WARNING: net/hsr/hsr_framereg.c:39 at hsr_addr_is_self+0x211/0x3f0 net/hsr/hsr_framereg.c:39, CPU#0: syz.4.16848/17220 Modules linked in: CPU: 0 UID: 0 PID: 17220 Comm: syz.4.16848 Tainted: G             L     syzkaller #0 PREEMPT_{RT,(full)} Tainted: [L]=SOFTLOCKUP Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/18/2026 RIP: 0010:hsr_addr_is_self+0x211/0x3f0 net/hsr/hsr_framereg.c:39 Code: 33 2f 41 0f b7 dd 89 ee 09 de 31 ff e8 c8 b4 c6 f6 09 dd 74 54 e8 0f b0 c6 f6 31 ed eb 53 e8 06 b0 c6 f6 48 8d 3d 2f 50 9c 04 <67> 48 0f b9 3a 31 ed eb 42 e8 c1 13 1f 00 89 c5 31 ff 89 c6 e8 96 RSP: 0018:ffffc900041c70e0 EFLAGS: 00010283 RAX: ffffffff8afdc6ca RBX: ffffffff8afdc4e6 RCX: 0000000000080000 RDX: ffffc90010493000 RSI: 0000000000000948 RDI: ffffffff8f9a1700 RBP: 0000000000000001 R08: 0000000000000000 R09: 0000000000000000 R10: ffffc900041c71e8 R11: fffff52000838e3f R12: dffffc0000000000 R13: ffff888041f9e3c0 R14: ffff888086ee3802 R15: 0000000000000000 FS:  00007f6fe985d6c0(0000) GS:ffff888126176000(0000) knlGS:0000000000000000 CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f80bd437dac CR3: 0000000025096000 CR4: 00000000003526f0 DR0: ffffffffffffffff DR1: 00000000000001f8 DR2: 0000000000000002 DR3: ffffffffefffff15 DR6: 00000000ffff0ff0 DR7: 0000000000000400 Call Trace:  <TASK>  check_local_dest net/hsr/hsr_forward.c:592 [inline]  fill_frame_info net/hsr/hsr_forward.c:728 [inline]  hsr_forward_skb+0xa11/0x2a80 net/hsr/hsr_forward.c:739  hsr_dev_xmit+0x253/0x370 net/hsr/hsr_device.c:236  __netdev_start_xmit include/linux/netdevice.h:5368 [inline]  netdev_start_xmit include/linux/netdevice.h:5377 [inline]  xmit_one net/core/dev.c:3888 [inline]  dev_hard_start_xmit+0x2df/0x860 net/core/dev.c:3904  __dev_queue_xmit+0x1428/0x3900 net/core/dev.c:4870  neigh_output include/net/neighbour.h:556 [inline]  ip_finish_output2+0xcec/0x10b0 net/ipv4/ip_output.c:237  ip_send_skb net/ipv4/ip_output.c:1510 [inline]  ip_push_pending_frames+0x8b/0x110 net/ipv4/ip_output.c:1530  raw_sendmsg+0x1547/0x1a50 net/ipv4/raw.c:659  sock_sendmsg_nosec net/socket.c:787 [inline]  __sock_sendmsg net/socket.c:802 [inline]  ____sys_sendmsg+0x7da/0x9c0 net/socket.c:2698  ___sys_sendmsg+0x2a5/0x360 net/socket.c:2752  __sys_sendmsg net/socket.c:2784 [inline]  __do_sys_sendmsg net/socket.c:2789 [inline]  __se_sys_sendmsg net/socket.c:2787 [inline]  __x64_sys_sendmsg+0x1c3/0x2a0 net/socket.c:2787  do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]  do_syscall_64+0x15f/0xf80 arch/x86/entry/syscall_64.c:94  entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f6feb62ce59 Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 e8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f6fe985d028 EFLAGS: 00000246 ORIG_RAX: 000000000000002e RAX: ffffffffffffffda RBX: 00007f6feb8a6090 RCX: 00007f6feb62ce59 RDX: 0000000000000000 RSI: 0000200000000000 RDI: 0000000000000004 RBP: 00007f6feb6c2d6f R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007f6feb8a6128 R14: 00007f6feb8a6090 R15: 00007ffcf01cc488  </TASK>",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-07-01 14:16:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98836",
                                "url": "https://ubuntu.com/security/CVE-2026-98836",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ALSA: line6: reject oversized playback packets  Each playback URB is handed a slice of out.buffer that is exactly LINE6_ISO_PACKETS * max_packet_size_out bytes, sized from the OUT endpoint, but the number of bytes written into that slice is never compared against it.  submit_audio_out_urb() takes the frame count from prev_fsize, which audio_in_callback() derived from the *IN* endpoint's received packet length, and rescales it with the playback frame size; when prev_fsize is still zero it synthesizes a length from the sample rate instead.  On a device declaring a large IN wMaxPacketSize and a small OUT wMaxPacketSize, the resulting memcpy(), or the memset() when the playback stream is idle, runs past its slice and, as the reproducer below shows, beyond the allocation.  usb_submit_urb() is not a backstop.  max_packet_size_out comes from usb_maxpacket(), which returns only the low 11 bits of wMaxPacketSize, while USB core validates a high-speed isochronous length against that base scaled by usb_endpoint_maxp_mult().  A length of up to three times the allocated slice is therefore accepted, and even a rejected URB is only rejected after the write.  Reject a packet that does not fit the slice the driver allocated for it. Clamping it instead would silently shorten the capture-derived rate feedback and desynchronize the two streams.    BUG: KASAN: slab-out-of-bounds in submit_audio_out_urb (sound/usb/line6/playback.c:229)   Write of size 1024 at addr ffff888100bbd400 by task kworker/1:2/5002   Workqueue: events line6_startup_work   Call Trace:    __asan_memcpy (mm/kasan/shadow.c:106)    submit_audio_out_urb (sound/usb/line6/playback.c:229)    line6_submit_audio_out_all_urbs (sound/usb/line6/playback.c:291)    line6_stream_start (sound/usb/line6/pcm.c:194)    line6_pcm_acquire (sound/usb/line6/pcm.c:337)    line6_startup_work (sound/usb/line6/driver.c:728)    process_one_work (kernel/workqueue.c:3396)    worker_thread (kernel/workqueue.c:3479 kernel/workqueue.c:3560)    kthread (kernel/kthread.c:436)    ret_from_fork (arch/x86/kernel/process.c:158)    ret_from_fork_asm (arch/x86/entry/entry_64.S:245)    The buggy address belongs to the object at ffff888100bbd400    which belongs to the cache kmalloc-256 of size 256   The buggy address is located 0 bytes inside of    allocated 256-byte region [ffff888100bbd400, ffff888100bbd500)",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98838",
                                "url": "https://ubuntu.com/security/CVE-2026-98838",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  vt: skip screen update for DEC alignment test on backgroup consoles  [BUG] Recently, we encountered a KASAN warning as follows:  BUG: KASAN: slab-out-of-bounds in fb_pad_aligned_buffer+0x11f/0x140 Read of size 1 at addr ff1100015fd9f6a4 by task tty_fbcon_oob/1239 CPU: 7 UID: 0 PID: 1239 Comm: tty_fbcon_oob Not tainted 7.3.0-rc1 #100 PREEMPT(full) Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.17.0-4.fc41 04/01/2014 Call Trace:  <TASK>  ...  kasan_report+0xf0/0x120  fb_pad_aligned_buffer+0x11f/0x140  ccw_putcs+0x86c/0xa80  fbcon_putcs+0x338/0x410  do_update_region+0x21d/0x450  do_con_write+0x1e0e/0x4880  con_write+0x13/0x80  n_tty_write+0x374/0x1010  file_tty_write.isra.0+0x404/0x7a0  ...  reproduce: 1) open /dev/tty0, set a KDFONTOP ioctl with op.op = KD_FONT_OP_SET, op.width = 8 and op.height = 16 (visible VC1) 2) open /dev/tty1, set a KDFONTOP ioctl with op.op = KD_FONT_OP_SET, op.width = 28 and op.height = 24 (invisible VC2) 3) echo 3 > /sys/devices/virtual/graphics/fbcon/rotate_all 4) write EShash8(esc hash8) to tty1  [CAUSE] All VCs render to the framebuffer. setfont only modifies the target VC's font without resizing the framebuffer backing buffer (par->rotated.buf); the buffer is only resized for the visible VC (fbcon_do_set_font -> ... -> vc_do_resize -> update_screen). This relies on the con_should_update() check performed before every update_region().  However, the ESC # 8 path (do_con_trol -> do_update_region) omits the con_should_update() check. After changing the font size of an invisible VC, do_update_region() fills using the new font size against a buffer that was never resized, causing an out-of-bounds access.  [FIX] Only push the update when the console is visible and not blanked, add the con_should_update() check in the do_con_trol() like every other call site of do_update_region() (update_region(), invert_screen(), ...).",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98568",
                                "url": "https://ubuntu.com/security/CVE-2026-98568",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  vxlan: use one headroom snapshot for neighbour replies  vxlan_na_create() samples LL_RESERVED_SPACE() to size the reply skb and then samples it again to reserve headroom. A concurrent vxlan_changelink() can update needed_headroom between the two reads, creating a TOCTOU race. The second value can exceed the allocation and make the Ethernet header write out of bounds.  The race is reproducible on the unpatched kernel. It occurred when vxlan_na_create() generated a neighbour reply while vxlan_changelink() changed the link headroom. KASAN caught a four-byte write two bytes beyond a 704-byte skbuff_small_head allocation.  Snapshot the headroom once and use that value for both allocation and reservation.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2024-49901",
                                "url": "https://ubuntu.com/security/CVE-2024-49901",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  drm/msm/adreno: Assign msm_gpu->pdev earlier to avoid nullptrs  There are some cases, such as the one uncovered by Commit 46d4efcccc68 (\"drm/msm/a6xx: Avoid a nullptr dereference when speedbin setting fails\") where  msm_gpu_cleanup() : platform_set_drvdata(gpu->pdev, NULL);  is called on gpu->pdev == NULL, as the GPU device has not been fully initialized yet.  Turns out that there's more than just the aforementioned path that causes this to happen (e.g. the case when there's speedbin data in the catalog, but opp-supported-hw is missing in DT).  Assigning msm_gpu->pdev earlier seems like the least painful solution to this, therefore do so.  Patchwork: https://patchwork.freedesktop.org/patch/602742/",
                                "cve_priority": "low",
                                "cve_public_date": "2024-10-21 18:15:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98846",
                                "url": "https://ubuntu.com/security/CVE-2026-98846",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  sctp: check RCV_SHUTDOWN after the sendmsg connect wait  sctp_wait_for_connect() drops the socket lock while it sleeps. An out-of-the-blue ABORT can then be processed from the socket backlog and unlink the association. If a concurrent shutdown(fd, SHUT_RD) sets RCV_SHUTDOWN, the waiter breaks with err == 0 before checking asoc->base.dead. Its final sctp_association_put() can then free the association, leaving sctp_sendmsg_to_asoc() to continue with a dangling pointer.  Check RCV_SHUTDOWN along with the wait error in sctp_sendmsg_to_asoc() before using the association again. The check only accesses the socket, so it needs no additional association reference. Return the existing -ESRCH so that sctp_sendmsg() skips freeing a new association that may already have been destroyed.  Keep sctp_wait_for_connect() unchanged to preserve its behavior for the connect() caller.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98847",
                                "url": "https://ubuntu.com/security/CVE-2026-98847",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  rtc: spear: initialize IRQ state before requesting alarm IRQ  devm_request_irq() enables the interrupt before it returns, so the handler may run while probe is still initializing the device. Initialize the MMIO address and spinlock before requesting the alarm IRQ.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98850",
                                "url": "https://ubuntu.com/security/CVE-2026-98850",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net/packet: prevent TX_RING byte count overflow  tpacket_snd() drains every SEND_REQUEST frame in a TX ring and adds each valid packet length to the signed int len_sum. Userspace can recycle completed frames concurrently, so a single blocking send call is not bounded by the ring size.  After enough successful transmissions len_sum wraps into the negative range. In particular, 65536 65535-byte frames followed by a 65007-byte frame produce 0xfffffdef, or -EIOCBQUEUED. sock_sendmsg_nosec() treats that as an impossible return and triggers a BUG. On systems configured to panic on oops, a CAP_NET_RAW holder can panic the host kernel.  Stop before the next frame would make the byte count exceed INT_MAX. The positive short count leaves that frame pending for a later send call.  A two-thread TPACKET_V2 reproducer triggered the BUG on an arm64 build of Linux 7.3-rc4. With this change, the same reproducer returned the expected positive short count without an oops.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98851",
                                "url": "https://ubuntu.com/security/CVE-2026-98851",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  netfilter: nft_flow_offload: drop flowtable reference on init error path  nft_flow_offload_init() bumps the flowtable use count with nft_use_inc() before calling nf_ct_netns_get().  When the latter fails, the error is returned as-is and the reference is leaked.  The upper layers do not balance it either: nf_tables_newexpr() clears expr->ops when the expression init callback fails, so the nft_expr_more() iteration in nft_rule_expr_deactivate() and nf_tables_rule_destroy() stops right before the failed expression and its ->destroy callback, which would drop the reference, never runs.  Each failed rule addition therefore leaks one flowtable reference and the flowtable can no longer be removed: NFT_MSG_DELFLOWTABLE keeps reporting -EBUSY even though no rule references it.  Save the nf_ct_netns_get() return value and undo the nft_use_inc() when it fails, restoring the inc/dec pairing within nft_flow_offload_init() itself.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98854",
                                "url": "https://ubuntu.com/security/CVE-2026-98854",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  of/overlay: only treat a positive changeset id as registered  of_overlay_fdt_apply() stores the idr_alloc() return value in ovcs->id before checking it. On failure the stored id is negative, free_overlay_changeset()'s \"if (ovcs->id)\" check passes, idr_remove() is called with a negative id and list_del() runs on ovcs->ovcs_list, which is not initialized until after the id allocation. An allocation failure at that point dereferences NULL.  Make free_overlay_changeset() treat only a strict-positive id as registered. The rest of the function already copes with a partially-initialized ovcs, so the error path stays a plain goto err_free_ovcs.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98855",
                                "url": "https://ubuntu.com/security/CVE-2026-98855",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  of/overlay: put property on deadprops only after changeset add succeeds  add_changeset_property() links a new property of a not-yet-live target node into the node's deadprops list before handing it to of_changeset_add_property(). If that fails, the error path frees the property but leaves the freed pointer linked in deadprops, and of_node_release() frees it a second time when the aborted overlay's node is released.  Record the changeset entry first and link the property into deadprops only on success. of_changeset_add_property() never looks at the node's property lists, so the order of the two steps is otherwise immaterial, and the error path frees a property that nothing references.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98862",
                                "url": "https://ubuntu.com/security/CVE-2026-98862",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  audit: fix exe mark UAF in kill_rules()  kill_rules() removes mixed AUDIT_DIR and AUDIT_EXE rules when an audit tree is pruned. It drops entry->rule.exe before removing the rule from the RCU-visible filter lists.  After a rule has been installed with AUDIT_ADD_RULE, which requires CAP_AUDIT_CONTROL, removing the watched directory can race with another task that is still evaluating the rule. In that case, fsnotify can free the executable mark before the reader reaches audit_mark_compare(), causing a use-after-free.  KASAN reports:      BUG: KASAN: slab-use-after-free in audit_mark_compare+0x8d/0xa0  Unlink the published rules from the RCU-visible lists and retain them on tree->rules for cleanup. If any rule has an executable mark, wait for a single RCU grace period before removing the marks and scheduling the entries for freeing. Otherwise, call_rcu() already provides the required deferred freeing without a synchronous wait.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98450",
                                "url": "https://ubuntu.com/security/CVE-2026-98450",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  smb: client: close completed creates on compound wait errors  compound_send_recv() waits for responses in order. If a later wait is interrupted, or if a later MID fails during response synchronization, an earlier CREATE may already have opened a remote handle. The earlier mid is then released without invoking handle_cancelled_mid(), leaving the remote handle open because no FID was copied to the caller.  Mark completed earlier mids as cancelled when a compound wait or MID synchronization aborts. Keep their response buffers attached while the MIDs are synchronized, and transfer them only after synchronization of the processed responses, so the release path can inspect successful CREATE responses and queue SMB2_close() after a later failure. Account for a remote open only after the close work is allocated and before it is queued, since the caller has not yet updated num_remote_opens. Mark the create+close compound used by smb2_unlink() so it is not closed again. Non-CREATE responses and compounds that already include a close keep their existing behavior.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:16:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98502",
                                "url": "https://ubuntu.com/security/CVE-2026-98502",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  HID: alps: unregister DualPoint Stick input device on remove  alps_input_configured() allocates a second input device (\"DualPoint Stick\") with input_allocate_device() and registers it, but the alps_driver struct has no .remove handler and input2 is not tracked in hdev->inputs.  The default remove path (hid_hw_stop -> hidinput_disconnect) only iterates hdev->inputs, so input2 is never unregistered and leaks on every device removal.  Add a .remove handler that stops the device first (preventing URB callbacks from touching input2 during teardown) and then unregisters input2.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98456",
                                "url": "https://ubuntu.com/security/CVE-2026-98456",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  Bluetooth: mgmt: fix race in read_unconf_index_list()  read_unconf_index_list() counts unconfigured controllers before allocating its response, then checks the device flags again while filling it.  hci_dev_list_lock stabilizes list membership, but it does not serialize the per-device flags. During asynchronous controller setup, the worker can set HCI_UNCONFIGURED and clear HCI_SETUP between the two passes. A controller omitted from the allocation count can then become eligible for the fill pass, causing an out-of-bounds write to rp->index[].  Allocate space for every device on hci_dev_list. Since list membership cannot change while hci_dev_list_lock is held, the response remains large enough regardless of flag transitions. The reported count and response length still include only eligible unconfigured controllers.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-18 16:16:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98451",
                                "url": "https://ubuntu.com/security/CVE-2026-98451",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  smb: client: use finish_no_open() for non-regular inodes  An O_CREAT open can find an existing symlink or another non-regular inode. cifs_atomic_open() calls finish_open() on it and attaches a cifsFileInfo. Symlink inodes have no CIFS release operation, so the dentry reference held by cifsFileInfo is leaked. FMODE_OPENED also prevents the VFS from following the symlink.  Track whether cifs_do_create() returned an open server handle. For non-regular inodes, close the handle if present, remove the pending open, and call finish_no_open() so the VFS can continue the lookup. Do not set FMODE_CREATED unless a regular file was opened. For O_NOFOLLOW with __O_REGULAR, return -ELOOP before the VFS's -EFTYPE check.  Defer closing a legacy POSIX handle on a non-regular inode until after inode lookup. This avoids closing it again if lookup fails.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-18 16:16:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98484",
                                "url": "https://ubuntu.com/security/CVE-2026-98484",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  netfilter: nf_tables: skip expired catchall elements on insert and delete  nft_setelem_catchall_insert() looks up duplicates with nft_set_elem_active() only, while nft_set_catchall_lookup() and the dump path additionally skip expired elements.  Once a catchall element with a timeout expires, this predicate drift makes it invisible to userspace dumps, yet it still blocks re-insertion: with NLM_F_EXCL the request fails with -EEXIST, and without it the request reports success but silently inserts nothing. The stale entry only goes away when the (user-tunable) gc interval elapses, so the catchall rule may silently stop matching for an arbitrarily long time after its first expiration.  The delete path shows the same drift: nft_setelem_catchall_deactivate() picks the first active-next entry in the catchall list, so with an expired entry still pending GC it retires the stale entry instead of the fresh one, and it deactivates an element that userspace no longer sees instead of failing with -ENOENT.  Align both walks with the lookup and dump predicates: only an element that is active and not expired counts as a duplicate or delete candidate, using the per-netns timestamp taken at transaction start, in line with the set backend .insert/.deactivate and catchall GC sync paths.",
                                "cve_priority": "negligible",
                                "cve_public_date": "2026-10-18 16:16:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98486",
                                "url": "https://ubuntu.com/security/CVE-2026-98486",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net: ena: fix MMIO read buffer leak on probe failure  ena_device_init() initializes the MMIO read mechanism with ena_com_mmio_reg_read_request_init(), which allocates a coherent DMA buffer for MMIO read responses.  The normal removal path releases this buffer through ena_com_mmio_reg_read_request_destroy(). However, if ena_probe() fails after ena_device_init() succeeds, the error path destroys the admin resources and eventually frees ena_dev without destroying the MMIO read request, leaving the coherent DMA buffer allocated.  Call ena_com_mmio_reg_read_request_destroy() in the probe error path before releasing the remaining device resources.  This issue was found by manual code inspection.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:16:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98493",
                                "url": "https://ubuntu.com/security/CVE-2026-98493",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net: ipconfig: bound DHCP option construction  ic_dhcp_init_options() appends the hostname (option 12), vendor-class (option 60) and client-ID (option 61) options into the fixed 312-byte bootp_pkt.exten[] buffer.  Only the client-ID branch checked the remaining space; the hostname and vendor-class writes were unbounded.  A 64-byte hostname together with the maximum 252-byte dhcpclass= identifier needs 18 + (2 + 64) + (2 + 252) = 338 of the 312 available bytes even before the terminating END marker, so the vendor-class memcpy runs past the end of exten[].  With CONFIG_FORTIFY_SOURCE this is reported as a field-spanning write and, when the kernel is booted with panic_on_warn=1, aborts boot with a panic.  Route the optional options through a common helper that makes sure the option, its 2-byte header and the END marker all fit and drops an option that would not.  Configurations with short options keep sending exactly the same bytes as before.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98454",
                                "url": "https://ubuntu.com/security/CVE-2026-98454",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  smb: client: fix create context out-of-bounds reads  smb2_parse_contexts() validates the complete create-context area but does not limit each record to its Next field before dispatching it.  A malformed chain can therefore expose bytes beyond the current context to a handler.  The QFid handler also used a full response-structure cast although it only reads DiskFileId.  The SMB2/SMB3 lease parsers made the same layout assumption: they read LeaseState and LeaseFlags at canonical offsets rather than at DataOffset.  A valid non-canonical DataOffset could therefore yield unrelated in-bounds data, while a short DataLength was still accepted.  Limit each context to its Next value, reject offsets before the context header, and reject malformed chains.  Bound the name range by the current context and do not dispatch a known handler when DataLength is zero.  Read the QFid DiskFileId only when the context data covers that field.  Parse the lease context from DataOffset and require DataLength to match the v1 or v2 lease_context size used by ksmbd.  A size mismatch skips lease parsing without failing the open.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-18 16:16:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98490",
                                "url": "https://ubuntu.com/security/CVE-2026-98490",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net: openvswitch: conntrack: fix helper UAF due to extensions realloc  While calling the helpers, a raw pointer to the extensions area is wired into expectations list:    -> nf_ct_helper()    -> helper->help()     -> nf_ct_expect_related_report()      -> nf_ct_expect_insert()       -> hlist_add_head_rcu(&exp->lnode, &master_help->expectations)  In case the connection is not confirmed yet, more extensions can be added afterwards with *_ext_add() calls reallocating the extension space and leaving the now invalid pointer in the expectations list that is later accessed while removing the expectation.  Make sure that helpers are called at the end after all the other extensions are already added.  Note that the helper rejection now leaves the mark and labels set, but that's not different from how the NAT was handled before or how the mark and the labels were handled on confirmation failure.  And there are no atomicity guarantees provided by the API anyway.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-18 16:16:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98507",
                                "url": "https://ubuntu.com/security/CVE-2026-98507",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  mm/rmap: fix missing barrier between anon_vma init and vma->anon_vma publish  On arm64 server, we find that a task trying to grab the anon_vma lock triggers hungtask.  INFO: task main:2354726 blocked for more than 120 seconds.       Tainted: G            E     5.10.0-0021.aarch64 #1 \"echo 0 > /proc/sys/kernel/hung_task_timeout_secs\" disables this message. task:main            state:D stack:    0 pid:2354726 ppid:2350673 flags:0x00000a01 Call trace:  __switch_to+0x7c/0xbc  __schedule+0x3b4/0x8a0  schedule+0x50/0xe0  rwsem_down_write_slowpath+0x3cc/0x6cc  down_write+0x60/0x260  __anon_vma_prepare+0x6c/0x210  do_anonymous_page+0x258/0x660  handle_pte_fault+0x188/0x214  __handle_mm_fault+0x1b0/0x380  handle_mm_fault+0xf4/0x284  do_page_fault+0x19c/0x494  do_translation_fault+0xcc/0xf8  do_mem_abort+0x48/0xac  el0_da+0x44/0x80  el0_sync_handler+0x88/0xb4  el0_sync+0x160/0x180  After analyzing the vmcore, we found the anon_vma->root->rwsem.count is -1.  There is another anon_vma whose anon_vma->root->rwsem.count is 1, the anon_vma->root->rwsem.owner shows the lock is held, but the stack of the task shows the task doesn't hold the anon_vma lock.  After adding more debugging info, we found __anon_vma_prepare() reuses anon_vma and triggers the UAF of anon_vma->root due to missing memory barrier, leading to locking and unlocking two different anon_vma->root, thus leading to an anon_vma will never be unlocked, and another anon_vma couldn't be locked anymore.  This race requires two adjacent VMAs that are not merged but are anon_vma-compatible (e.g., they differ in VMA_ACCESS_FLAGS that can be changed by mprotect()).  Two threads fault on each VMA concurrently, both calling __anon_vma_prepare() with only mmap_lock held for reading.      THREAD A                             THREAD B __anon_vma_prepare                __anon_vma_prepare  find_mergeable_anon_vma() -> NULL  anon_vma = anon_vma_alloc();    anon_vma->root = anon_vma;  // the two stores may be reordered  vma->anon_vma = anon_vma;                                    // finds A's anon_vma                                    anon_vma = find_mergeable_anon_vma(vma);                                    anon_vma_lock_write(anon_vma);                                      // may still see the old root                                      down_write(&anon_vma->root->rwsem);                                    anon_vma_unlock_write(anon_vma);                                      // see the new root, never unlock old                                      up_write(&anon_vma->root->rwsem);  thread A triggers page fault and calls __anon_vma_prepare() to prepare anon_vma for the faulting vma.  __anon_vma_prepare() allocates and initializes a new anon_vma, and then publishes it to the vma with a plain store.  anon_vma_prepare() only requires the mmap_lock to be held for reading, so two threads can fault on adjacent VMAs at the same time. While thread A publishes a new anon_vma, thread B could find the anon_vma via find_mergeable_anon_vma() and then locks anon_vma->root->rwsem.  The store to anon_vma->root in anon_vma_alloc() and the store to vma->anon_vma can be reordered.  The anon_vma_lock_write() and spin_lock() only provide acquire semantics, which do not prevent prior stores from being reordered after them.  The release semantics of the corresponding spin_unlock() and anon_vma_unlock_write() come too late, the store to vma->anon_vma is already published before they take effect.  As a result, thread B can observe the following order:      vma->anon_vma = anon_vma;     anon_vma->root = anon_vma;  The anon_vma slab is SLAB_TYPESAFE_BY_RCU, so a newly allocated anon_vma may reuse memory from a previously freed one.  The constructor (anon_vma_ctor) does not reset anon_vma->root, and __put_anon_vma() doesn't clear it either, so the old root value persists until anon_vma_alloc() overwrites it.  If that store isn't v ---truncated---",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98519",
                                "url": "https://ubuntu.com/security/CVE-2026-98519",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  drm/amdgpu: Fix runtime PM leak in amdgpu_debugfs_test_ib_show()  amdgpu_debugfs_test_ib_show() resumes the device with pm_runtime_get_sync() before taking the reset domain semaphore with down_write_killable().  If the write lock acquisition is interrupted, the function returns without calling pm_runtime_put_autosuspend(), leaking the runtime PM reference acquired for the device and keeping the GPU awake.  Drop the runtime PM reference on the interrupted down_write_killable() error path before returning.  (cherry picked from commit ec30a576c2d4c0364549e6c04218f50704ef56c8)",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98549",
                                "url": "https://ubuntu.com/security/CVE-2026-98549",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  tcp: prevent collapsing skbs across boundary in rtx queue  tcp_write_collapse_fence() sets TCP_SKB_CB(skb)->eor = 1 on tcp_write_queue_tail(sk) to prevent skbs queued after a switch to device encryption from being collapsed into earlier skbs.  The fence is a no-op if all earlier data has already been transmitted when the switch happens: sk->sk_write_queue is empty. The not yet acknowledged earlier skbs wait in sk->tcp_rtx_queue with eor 0.  On a subsequent retransmit or SACK shift, tcp_retrans_try_collapse() or tcp_shift_skb_data() can then merge an skb queued after the switch into one queued before it.  Both users of the fence are affected:  - psp: devices only encrypt skbs with skb->decrypted set. The merged skb   keeps decrypted = 0 from the earlier skb, so merged data sent after   psp_sock_assoc_set_tx() is retransmitted in cleartext.  - tls device offload: the merged skb straddles the start marker set in   tls_set_device_offload(). The software fallback (fill_sg_in() returns   -EINVAL) and the mlx5, nfp and funeth drivers cannot handle such an   skb and drop it. Every retransmit rebuilds the same skb, so the   connection stalls.  Fix this in two places, for defense in depth:  1. Fall back to tcp_rtx_queue_tail(sk) in tcp_write_collapse_fence()    when tcp_write_queue_tail(sk) is NULL.  2. Check !skb_cmp_decrypted(to, from) in tcp_skb_can_collapse(), as    tcp_skb_can_collapse_rx() does on receive. skb_shift(), which both    collapse paths call, already has a DEBUG_NET_WARN_ON_ONCE() for this    condition.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98544",
                                "url": "https://ubuntu.com/security/CVE-2026-98544",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  bna: prevent IOC timer rearm during teardown  bna: prevent IOC timer rearm during teardown  bnad_pci_remove() and the probe disable_ioceth path call timer_delete_sync() for ioc_timer, sem_timer and hb_timer, but not for iocpf_timer.  bnad_iocpf_timeout() then takes bnad->bna_lock after free_netdev() has freed the struct bnad.  Deleting iocpf_timer last does not fix this.  sem_timer and iocpf_timer rearm each other: bnad_iocpf_sem_timeout() can arm iocpf_timer, and bnad_iocpf_timeout() arms sem_timer from bfa_ioc_hw_sem_get() when the semaphore is busy. timer_delete_sync() only waits out its own callback. bnad_ioceth_disable() can time out and leave that callback live.  Shut all four IOC timers down with timer_shutdown_sync() on both paths, so a later mod_timer() is ignored.  This issue was identified during our ongoing static-analysis research while reviewing kernel code.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98172",
                                "url": "https://ubuntu.com/security/CVE-2026-98172",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  smb: client: fix smbd_connection leak on cifs_get_tcp_session() error  When an RDMA connection is successfully established via smbd_get_connection() but cifs_get_tcp_session() later fails (e.g. kthread_create() returns an error), the error path frees tcp_ses without first destroying the smbd_connection.  Fix this by calling smbd_destroy() in the out_err cleanup path before kfree(tcp_ses).  smbd_destroy() safely handles the case where smbd_conn is NULL, so it can be called unconditionally.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-06 09:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98192",
                                "url": "https://ubuntu.com/security/CVE-2026-98192",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: wcn36xx: Fix potential use-after-free in TX ack timer teardown  wcn36xx_dxe_deinit() tears down the TX ack timer with timer_delete(), which only dequeues the timer and does not wait for a callback that is already executing; the preceding free_irq() calls synchronize the interrupt handlers only. The callback, wcn36xx_dxe_tx_timer(), can therefore be running past the teardown and use the wcn freed along with the ieee80211_hw in wcn36xx_remove(): it takes wcn->dxe_lock, reads wcn->tx_ack_skb and passes wcn->hw to ieee80211_tx_status_irqsafe().  Fix this by using timer_shutdown_sync(), which waits for a running callback and also prevents the timer from being rearmed again. The timer is set up again by wcn36xx_dxe_init() on the next start, so the start/stop cycle is unaffected.  This issue was found by an in-house static analysis tool.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-06 09:18:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98198",
                                "url": "https://ubuntu.com/security/CVE-2026-98198",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  hwmon: (pwm-fan) Stop RPM timer before freeing tach data  sample_timer() rearms the RPM timer and accesses the devm-managed ctx->tachs and ctx->pulses_per_revolution arrays. The cleanup action which stops the timer is registered before those arrays are allocated.  Since devres releases entries in reverse order, driver detach can free the arrays before pwm_fan_cleanup() shuts down the timer. A timer expiry in that window accesses the freed tach data.  With a KASAN kernel, a test-only kprobe delayed entry to pwm_fan_cleanup() while normal sysfs unbind ran. Each of three runs reported three four-byte reads and two four-byte writes in sample_timer() after its backing devm allocations had been freed. The helper did not invoke the timer callback, cleanup actions or free functions.  With the fix, three matching unbind runs completed without KASAN, BUG, WARNING, Oops or panic. Instrumentation confirmed that timer retirement completed before the first timer backing allocation was released.  Split timer retirement from the power cleanup and register its devres action after the timer backing data and IRQ actions are installed. This preserves the early power rollback action while ensuring the timer is retired before its backing data is released. Use timer_shutdown_sync() because the callback can rearm itself.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-06 09:18:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98409",
                                "url": "https://ubuntu.com/security/CVE-2026-98409",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  watchdog: rtd119x: Avoid division by zero  clk_get_rate() could return 0.  Avoid a division by zero panic.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-14 14:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98245",
                                "url": "https://ubuntu.com/security/CVE-2026-98245",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  btrfs: take commit root semaphore when iterating in mark_block_group_to_copy()  mark_block_group_to_copy() iterates over the commit root with skip_locking=true. A concurrent transaction commit can swap and free the commit root during iteration, causing use-after-free when accessing extent buffers.  Fix it by using path->need_commit_sem to protect the commit root search.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-06 09:18:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98264",
                                "url": "https://ubuntu.com/security/CVE-2026-98264",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ALSA: virtio: reset device before deleting virtqueues  virtsnd_remove() and virtsnd_freeze() delete the virtqueues before resetting the device. del_vqs() frees the vring backing, but does not provide a generic device quiesce operation. In particular, modern virtio-pci keeps enabled queues active until the device is reset.  Reset the device before deleting the virtqueues so it can no longer access the vring memory when that memory is released. This also covers probe failures after DRIVER_OK, which unwind through virtsnd_remove().",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-06 09:18:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-97558",
                                "url": "https://ubuntu.com/security/CVE-2026-97558",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  smb: client: fix cifsFileInfo reference leak in deferred close  When cifs_close() defers a close, it hands the cifsFileInfo reference of the closing struct file to the queued work. Each execution of smb2_deferred_work_close() drops one such reference.  deferred_close_scheduled can be false while the work is pending: the workqueue clears PENDING when the callback starts to run, before the callback clears the flag under deferred_lock. A close in that interval requeues the running work, and the callback then clears the flag, leaving the requeued work pending with the flag down. A later cifs_open() can reuse the handle and its cifs_close() reaches the same branch: queue_delayed_work() fails because the work is still pending, but cifs_close() returns without dropping the closing file's reference. The cifsFileInfo count stays pinned and its tlink, dentry and server handle are leaked.  Check the return value and hand off the reference only when work was actually queued. Otherwise, use the shared _cifsFileInfo_put(), like the mod_delayed_work() branch above: the pending execution already owns its reference.  This issue was found by an in-house static analysis tool.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-09-25 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-97616",
                                "url": "https://ubuntu.com/security/CVE-2026-97616",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net/sched: act_api: release all action references on NEWACTION failure  When a batched RTM_NEWACTION request replaces an existing action, tcf_idr_check_alloc() takes a temporary reference on it. If a later action fails to initialize, tcf_action_destroy() uses strict release semantics to clean up the actions initialized so far. For an action bound to a filter, the strict check returns -EPERM without dropping the temporary reference.  This error also makes tcf_action_destroy() return before releasing subsequent entries. Any new action initialized between the bound action and the failing entry is leaked together with its reserved IDR slot, preventing reuse of its index.  Use tcf_idr_release() to drop each reference held by the batch without rejecting bound actions. This allows cleanup to continue through all initialized entries and preserves the module reference release when an action is destroyed. Explicit action deletion and flushing retain their separate bind-count checks.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-09-25 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-97939",
                                "url": "https://ubuntu.com/security/CVE-2026-97939",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ipmr: account multicast table and route memory  A netadmin in a user+net namespace can create many IPv4 and IPv6 multicast routing tables with MRT_TABLE and MRT6_TABLE. Each unseen id allocates an mr_table via the shared mr_table_alloc(), links it into the per-net list, and leaves it until netns teardown. Those objects were not charged to memcg, so the host unreclaimable slab grows with the table count.  Account mr_table allocations with GFP_KERNEL_ACCOUNT and mark the IPv4/IPv6 MFC caches SLAB_ACCOUNT. This matches the established handling of IP addresses, routes and alternate interface names.  Unresolved MFC entries are still allocated from softIRQ with GFP_ATOMIC and are not charged. They expire after 10 seconds and are bounded by the socket receive queue; see commit 0079ad8e8dc3 (\"ipmr: remove hard code cache_resolve_queue_len limit\").",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-09-25 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-89837",
                                "url": "https://ubuntu.com/security/CVE-2026-89837",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  f2fs: fix dentry folio leak in find_in_level  find_in_level() gets a dentry folio with f2fs_find_data_folio() before calling find_in_block().  If find_in_block() returns an error, the function stores the error in res_folio and breaks out of the loop without dropping the dentry folio.  This leaks the folio reference on the find_in_block() error path.  Drop the dentry folio before returning the error to the caller.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-09-16 11:16:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-89838",
                                "url": "https://ubuntu.com/security/CVE-2026-89838",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  f2fs: limit recovery filename logging to stored length  F2FS stores recovery filenames as a length plus a fixed-size i_name buffer.  The buffer is not NUL-terminated, but recover_inode() and recover_dentry() print it with %s.  For a 255-byte filename, recovery logging can read past i_name into the following raw inode fields.  Print the name with a precision bounded by i_namelen and F2FS_NAME_LEN.",
                                "cve_priority": "negligible",
                                "cve_public_date": "2026-09-16 11:16:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-97530",
                                "url": "https://ubuntu.com/security/CVE-2026-97530",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  scsi: qla2xxx: Fix soft lockup polling continuation IOCB signature  qla27xx_copy_multiple_pkt() and qla27xx_copy_fpin_pkt() poll rsp_q->ring_ptr->signature for RESPONSE_PROCESSED (0xDEADDEAD) to decide whether the next continuation IOCB has arrived, spinning on cpu_relax() without advancing the ring or decrementing the entry count while it has not. response_t::signature lives at byte offset 60, but a continuation IOCB (sts_cont_entry_t / struct sts_cont_entry_ext) carries raw FC frame payload at that offset (data[56..59]). A received frame whose payload bytes happen to equal 0xDEADDEAD is therefore misread as \"not yet arrived\", and the loop spins forever in interrupt/DPC context, causing a CPU soft lockup.  The poll is also unnecessary: callers of qla27xx_copy_multiple_pkt() (PT_LS4_UNSOL and the NVMe purls path) already gate on qla_chk_cont_iocb_avail(), which guarantees all entry_count IOCBs are present before copying begins. The sibling helper __qla_copy_purex_to_buffer() already drops the signature poll and relies on the entry_type == STATUS_CONT_TYPE guard instead.  Remove the signature busy-wait from both helpers, keeping the entry_type guard, and gate the FPIN path with qla_chk_cont_iocb_avail() so it defers and re-processes on the next interrupt once all continuation IOCBs have arrived, mirroring the ELS_AUTH_ELS and PT_LS4_UNSOL arms. With this the signature field is never read on a continuation IOCB, eliminating the payload-aliasing lockup.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-09-25 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98386",
                                "url": "https://ubuntu.com/security/CVE-2026-98386",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  scsi: qla2xxx: Use memset_io() to clear QLAFX00 request ring slot  For QLAFX00 the request ring is ioremapped device I/O memory (ha->iobase + req_que_off), not DMA-coherent RAM, which is why the rest of the FX00 path accesses it through memcpy_toio() and the wrt_reg_* helpers. __qla2x00_alloc_iocbs() however zeroed the producer slot with a plain memset(). On architectures such as ARM64 a regular memset() may emit unaligned or block-zeroing instructions (e.g. DC ZVA) that are invalid on Device memory, leading to a synchronous external abort.  Use memset_io() to clear the slot for QLAFX00, matching the I/O accessors used elsewhere on this ring. Other adapters keep the plain memset() on their DMA-coherent rings. The zero-fill is retained for FX00 because its IOCB builders (e.g. qlafx00_fxdisc_iocb()) copy only part of the entry and rely on the unused tail being pre-zeroed.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-14 14:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-89848",
                                "url": "https://ubuntu.com/security/CVE-2026-89848",
                                "cve_description": "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_work, and qla_do_work() -> qla24xx_process_response_queue() dereferences the now-freed rsp->req (LOGINOUT/CT/ELS entries and the status path), a use-after-free.  The cancel_work_sync() added for the qpair teardown lives in the response free path, which runs after the request queue is already freed, so it does not protect rsp->req.  Release the response-queue interrupt and flush qpair->q_work before deleting the request queue, so no late completion can reach the freed request queue. Clearing have_irq makes the subsequent qla25xx_free_rsp_que() skip its free_irq(), and the firmware queue-delete order (request then response) is preserved; the request-delete mailbox completes on the default vector and is unaffected by dropping the qpair response interrupt early.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-09-16 11:16:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-97532",
                                "url": "https://ubuntu.com/security/CVE-2026-97532",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  scsi: qla2xxx: Null out freed pointers in qla2x00_mem_alloc() error path  When qla2x00_mem_alloc() fails, qla2x00_probe_one() jumps to probe_hw_failed and calls qla2x00_mem_free(). Several error labels in qla2x00_mem_alloc() freed adapter members (elsrej.c, purex_dma_pool, flt, sfp_data, loop_id_map, async_pd, sf_init_cb, ex_init_cb, npiv_info) but left the pointers dangling. qla2x00_mem_free() then freed them a second time. Worse, for the dma_pool members it issued dma_pool_free(ha->s_dma_pool, ...) after s_dma_pool had already been destroyed and set to NULL at fail_s_dma_pool, dereferencing a NULL pool.  Clear each freed pointer (and its DMA handle) in the error labels so the subsequent qla2x00_mem_free() skips them.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-09-25 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-89877",
                                "url": "https://ubuntu.com/security/CVE-2026-89877",
                                "cve_description": "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 existing MMIO mapping error path to remove the device from saa7164_devlist and decrement the device count before returning.  Also release BAR0 if it was successfully requested but the BAR2 request fails.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-09-16 11:16:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-93239",
                                "url": "https://ubuntu.com/security/CVE-2026-93239",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  arm64: mm: Fix the lockless page-table walk in show_pte()  show_pte() walks page tables locklessly and can run with interrupts enabled. A concurrent teardown can free a table page while it is being walked. It can also clear a parent entry after show_pte() checked it; the regular pXd_offset() helpers then reread the cleared entry and can derive a bogus lower-level pointer and fault again.  Use the lockless offset helpers with the saved parent entries, as gup_fast() does, and pass the saved PMD to pte_offset_map().  For task page tables, arm64 selects MMU_GATHER_RCU_TABLE_FREE. Disable local interrupts around the walk to hold off RCU-deferred table frees and block the tlb_remove_table_sync_one() IPI until the walk is finished.  Place the IRQ guard after the header print. This does not make the output a consistent snapshot, but prevents the task page-table walk from dereferencing a released table page or deriving a pointer from a different parent value.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-09-24 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-90023",
                                "url": "https://ubuntu.com/security/CVE-2026-90023",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  usb: gadget: f_mass_storage: fix null pointer dereference in fsg_common_set_num_buffers()  Previously fsg_num_buffers_validate() was removed as it was not necessary due to Kconfig setting the limits for n from 2 to 256 with default as 2. However, setting the page content in such a way that kstrtou8() reflects n value as either 0 or 1 bypasses these restrictions leading to a null pointer dereference if n is 0. Fix this by adding a check for n < 2 and returning -EINVAL if n is either 0 or 1 consistent with Kconfig logic.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-09-16 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-93200",
                                "url": "https://ubuntu.com/security/CVE-2026-93200",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  i3c: master: Fix use-after-free of master->this  sysfs attribute callbacks for the master controller device dereference master->this.  However, master->this is freed in i3c_master_detach_free_devs() before the master device itself is released.  As a result, sysfs accesses can dereference a freed master->this pointer, leading to a use-after-free.  Keep master->this alive until i3c_masterdev_release(), which is called after the master device and its sysfs state are being torn down. Do not free master->this as part of the normal device detach path.  On the error path in i3c_master_set_info(), reset master->this and bus.cur_master to NULL before freeing the allocated device.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-09-17 17:18:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-93199",
                                "url": "https://ubuntu.com/security/CVE-2026-93199",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  i3c: master: Do not treat master device as a duplicate target  i3c_master_search_i3c_dev_duplicate() searches the bus for another I3C device with the same PID as the reference device.  The search can match master->this, causing the controller itself to be returned as a duplicate.  Since the controller is not a target device, it cannot be a duplicate of one.  Exclude master->this from matching so that the function only returns real duplicate target devices.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-09-17 17:18:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-89441",
                                "url": "https://ubuntu.com/security/CVE-2026-89441",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  mmc: via-sdmmc: cancel card-detect work on remove  Disabling the device interrupt and freeing the IRQ prevents new card-detect work from being queued, but carddet_work already queued by the handler can still run after via_sd_remove() returns. via_sdc_card_detect() recovers the host through container_of() and dereferences its MMIO base; once remove() returns the host can be freed, so that work would touch freed memory.  Cancel carddet_work after freeing the IRQ and before cancelling finish_bh_work, which the card-detect handler can also queue. carddet_work can re-enable the interrupt through via_reset_pcictrl(); mask it again afterwards.  This issue was found by an in-house static analysis tool and confirmed by manual code review.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-09-11 20:19:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-89465",
                                "url": "https://ubuntu.com/security/CVE-2026-89465",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  power: supply: rt9455: quiesce delayed work before teardown  The threaded IRQ handler can queue pwr_rdy_work, max_charging_time_work and batt_presence_work.  pwr_rdy_work and batt_presence_work can also queue max_charging_time_work, while batt_presence_work can requeue itself.  rt9455_remove() cancels max_charging_time_work before batt_presence_work.  The latter can therefore queue max_charging_time_work after it has already been cancelled:    rt9455_remove()                   workqueue     cancel pwr_rdy_work     cancel max_charging_time_work                                       batt_presence_work queues                                         max_charging_time_work     cancel batt_presence_work     return     devres frees rt9455_info                                       max_charging_time_work dereferences                                         rt9455_info  The IRQ also remains registered until devres cleanup and can queue more work after any of the cancellation calls.  If rt9455_hw_init() fails after the IRQ has been requested, probe returns without cancelling work that may already have been queued.  A pending callback can then access rt9455_info after it has been freed.  Register rt9455_cancel_all_delayed_works() through devm_add_action_or_reset() right after devm_power_supply_register(). devres invokes the action in reverse registration order, after the managed IRQ has been freed and before rt9455_info is released, so the delayed works are drained in both rt9455_remove() and the probe error path.  Cancel pwr_rdy_work and batt_presence_work before max_charging_time_work because both can queue the latter.  This issue was found by an in-house static analysis tool.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-09-11 20:19:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-93231",
                                "url": "https://ubuntu.com/security/CVE-2026-93231",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  lockd: fix swapped arguments in nlmsvc_match_ip()  When releasing locks by server IP address via /proc/fs/nfsd/unlock_ip, nlmsvc_unlock_all_by_ip() calls nlm_traverse_files() with the server sockaddr as the opaque @data argument:  \tnlm_traverse_files(server_addr, nlmsvc_match_ip, NULL);  The match callback is later invoked from nlm_traverse_locks() as:  \tmatch(lockhost, host);  where the first argument is the nlm_host that owns the lock, and the second argument is the @data that was originally passed down (here the server sockaddr).  This is the convention every other match callback relies on (nlmsvc_mark_host(), nlmsvc_same_host(), nlmsvc_is_client()): arg1 is the real nlm_host, arg2 is the caller-supplied reference value.  nlmsvc_match_ip() has had these two arguments reversed ever since the unlock-by-IP feature was introduced in commit 4373ea84c84d (\"lockd: unlock lockd locks associated with a given server ip\"):  \treturn rpc_cmp_addr(nlm_srcaddr(host), datap);  Here @host is actually the server sockaddr, so nlm_srcaddr(host) dereferences a struct sockaddr as a struct nlm_host and reads garbage at the offset of h_srcaddr; meanwhile @datap is actually the lock owner's nlm_host but is compared as a sockaddr.  As a result the comparison practically never matches and locks are not released for the requested IP.  Swap the arguments so the lock owner's source address is compared against the requested server address:  \treturn rpc_cmp_addr(nlm_srcaddr(datap), (struct sockaddr *)host);  [ cel: fix the misleading typedef parameter names too ]",
                                "cve_priority": "low",
                                "cve_public_date": "2026-09-24 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-89552",
                                "url": "https://ubuntu.com/security/CVE-2026-89552",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  params: fix charp corruption on allocation failure  param_set_charp() stores charp parameters in allocated memory after slab is available, and releases the previous value when the parameter is updated.  The previous value is released before the replacement allocation succeeds. If kmalloc_parameter() fails, the setter returns -ENOMEM with the parameter left as NULL.  Failing zswap's compressor update before zswap is initialized can later trigger:    BUG: kernel NULL pointer dereference, address: 0000000000000000   RIP: 0010:strcmp+0x10/0x30   Call Trace:     zswap_setup+0x3b1/0x490     zswap_enabled_param_set+0x5b/0xa0     param_attr_store+0x93/0xe0     module_attr_store+0x1c/0x30     kernfs_fop_write_iter+0x116/0x1f0  Allocate and copy the replacement first, then replace the parameter value only after allocation succeeds.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-09-11 20:19:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-89640",
                                "url": "https://ubuntu.com/security/CVE-2026-89640",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  cifs: fix loff_t underflow in cifs_remap_file_range() when len == 0  With len == 0 (clone to EOF), the effective length is computed as:      len = src_inode->i_size - off;  If off > i_size, this is a negative loff_t, corrupting the ByteCount in the FSCTL_DUPLICATE_EXTENTS_TO_FILE request and inverting the range in filemap_write_and_wait_range().  The existing off >= i_size check fires only after the ioctl has already been sent.  Snapshot i_size_read() once for both the bounds check and the length calculation, eliminating the TOCTOU and 32-bit torn-read risk.  Reject off > src_size with -EINVAL.  Treat off == src_size as a no-op, consistent with __generic_remap_file_range_prep().",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-09-11 20:19:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-89672",
                                "url": "https://ubuntu.com/security/CVE-2026-89672",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  nfsd: gate nfs2 setacl by argp->mask  The NFSACL v2 SETACL path shares the decoder convention used by its v3 sibling: nfsaclsvc_decode_setaclargs() fills in argp->acl_access only when NFS_ACL is set in the request mask and argp->acl_default only when NFS_DFACL is set, leaving the other pointer NULL because the argument buffer is zeroed up to pc_argzero before decode.  nfsacld_proc_setacl() then hands both pointers to set_posix_acl() unconditionally. set_posix_acl(idmap, dentry, type, NULL) is the VFS \"remove this ACL type\" operation, so an omitted arm is indistinguishable from an explicit request to delete that ACL. A SETACL carrying only NFS_ACL silently strips the directory's default ACL; mask=0 strips both.  This is the same defect just fixed in nfsd3_proc_setacl(); apply the same remedy. Gate each set_posix_acl() call on its mask bit and initialize error to 0 so that a request with neither bit set leaves the on-disk ACLs untouched and returns success. The out_drop_lock path and the unconditional posix_acl_release() in nfsaclsvc_release_setacl() already tolerate the skipped arms.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-09-11 20:19:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-89685",
                                "url": "https://ubuntu.com/security/CVE-2026-89685",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  nfsd: fix clock domain mismatch in clients_still_reclaiming()  clients_still_reclaiming() computes a deadline from nn->boot_time (CLOCK_REALTIME, ~1.7 billion) but compares it against ktime_get_boottime_seconds() (CLOCK_BOOTTIME, seconds since boot). The comparison is always false — it would take ~54 years of uptime for BOOTTIME to exceed the REALTIME-derived deadline.  This means any client can hold the server in grace indefinitely by sending CLAIM_PREVIOUS OPEN requests, blocking all non-reclaim operations for all other clients.  Add boot_time_bt (CLOCK_BOOTTIME) alongside the existing boot_time and use it for the deadline computation. boot_time (CLOCK_REALTIME) is preserved for its cl_boot clientid-nonce role.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-09-11 20:19:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-89707",
                                "url": "https://ubuntu.com/security/CVE-2026-89707",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  nfsd: release path refs on follow_down() error  nfsd_cross_mnt() initializes a local struct path with mntget() and dget() before calling follow_down(). On a negative return the error arm jumps to out without releasing those references:      err = follow_down(&path, follow_flags);     if (err < 0)             goto out;  follow_down() never drops the caller's entry-time refs on any error sub-case; for example a pre-cross d_manage() failure leaves path untouched, so the mntget()/dget() taken on entry survive the call.  Every other early-exit arm in nfsd_cross_mnt() (other-namespace return, IS_ERR(exp2), and the success tail after the swap) already calls path_put(&path); the err < 0 arm is the lone omission. The leak inflates mnt_count and d_count on each failed cross-mount, blocking umount and pinning dentries against the shrinker, and is reachable by any authenticated NFS client through nfsd_lookup_dentry or the NFSv4 READDIR encode path.  Fix by calling path_put(&path) before the goto out in the err < 0 arm so the entry-time refs are released on all follow_down() error returns.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-09-11 20:19:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-89719",
                                "url": "https://ubuntu.com/security/CVE-2026-89719",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  zram: fix out-of-bounds access in read_block_state()  read_block_state() calculates nr_pages before taking dev_lock.  If the device is reset and reinitialized with a smaller disksize before lock acquisition, nr_pages still describes the old table.  The subsequent loop can then call slot_lock() past the end of the newly allocated table.  Read disksize after acquiring dev_lock and checking that the device is initialized.  The read lock then keeps the table and its bound stable for the duration of the scan.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-09-11 20:20:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-89763",
                                "url": "https://ubuntu.com/security/CVE-2026-89763",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  KEYS: trusted: Fix TPM teardown ordering  trusted_tpm_exit() drops the TPM chip reference and frees the digest array before unregistering the trusted key type. key_type_lookup() holds key_types_sem for reading until the key operation finishes, while unregister_key_type() takes it for writing. It therefore provides the synchronization point that must precede backend teardown.  The current order permits this interleaving:    CPU 0                              CPU 1   trusted_tpm_exit()                 key_type_lookup(\"trusted\")     put_device(&chip->dev)             trusted_tpm_seal()     kfree(digests)                       pcrlock()     unregister_key_type()                  tpm_pcr_extend(..., digests)  CPU 1 can consequently dereference the freed digest array. The chip can also be released before callbacks stop using it.  KASAN reported:    BUG: KASAN: slab-use-after-free in tpm_pcr_extend+0x1f0/0x200   Read of size 2 at addr ffff88810872d000 by task poc/89   Call Trace:     tpm_pcr_extend+0x1f0/0x200     pcrlock+0x42/0x70 [trusted]     trusted_tpm_seal+0x1b6/0x570 [trusted]     trusted_instantiate+0x293/0x340 [trusted]     __key_instantiate_and_link+0xb2/0x2b0     __key_create_or_update+0x61e/0xb50     __do_sys_add_key+0x1b8/0x310   Allocated by task 88:     __kmalloc_noprof+0x1a7/0x490     do_one_initcall+0xa1/0x390     do_init_module+0x2df/0x840   Freed by task 90:     kfree+0x131/0x3c0     trusted_tpm_exit+0x59/0xa0 [trusted]     __do_sys_delete_module+0x346/0x510  Move unregister_key_type() before releasing either resource. This stops new lookups and waits for in-flight key operations to finish before the backend state is destroyed.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-09-11 20:20:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-80851",
                                "url": "https://ubuntu.com/security/CVE-2026-80851",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  gtp: serialize PDP context updates  PDP contexts can be deleted through GTP_CMD_DELPDP or while the GTP network device is being unregistered. The latter is serialized by RTNL, but the generic-netlink delete path only holds RCU.  Running both paths concurrently can therefore make both paths delete the same PDP context. The issue was found through static analysis and reproduced on a KASAN-enabled kernel by a simple two-thread program racing GTP_CMD_DELPDP against RTM_DELLINK:    Oops: general protection fault, probably for non-canonical address   KASAN: maybe wild-memory-access in range          [0xdead000000000120-0xdead000000000127]   RIP: gtp_genl_del_pdp+0x1c1/0x420 [gtp]   RBP: dead000000000122  The second deletion dereferenced the poisoned hlist pprev pointer.  Serialize gtp_pdp_add(), gtp_genl_del_pdp(), and gtp_dellink() with a shared mutex. Keep the mutex held until the final use of a PDP context in the NEWPDP path, and keep the RCU read-side section around the complete PDP context use in the DELPDP path.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-09-04 16:18:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-80861",
                                "url": "https://ubuntu.com/security/CVE-2026-80861",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  usb: xhci: bail out of setup if the controller is inaccessible  xhci_gen_setup() locates the operational registers using the capability length read from the very first register:  \txhci->op_regs = hcd->regs + \t\tHC_LENGTH(readl(&xhci->cap_regs->hc_capbase));  If the controller is dead or has dropped off the bus, that read returns ~0, HC_LENGTH() truncates it to 0xff, and op_regs ends up 0xff bytes past the page-aligned MMIO base, i.e. unaligned. The first access through it, xhci_halt() -> xhci_handshake() reading op_regs->status, is then an unaligned readl() on device memory. arm64 faults on unaligned device accesses, so instead of xhci_handshake() catching the all-ones value and returning -ENODEV, setup oopses:    xhci-pci-renesas 0005:08:00.0: Unable to change power state from D3cold to D0, device inaccessible   xhci-pci-renesas 0005:08:00.0: xHCI Host Controller   xhci-pci-renesas 0005:08:00.0: new USB bus registered, assigned bus number 1   Unable to handle kernel paging request at virtual address ffff80030a770103     ESR = 0x0000000096000021     FSC = 0x21: alignment fault   Internal error: Oops: 0000000096000021 [#1]  SMP   pc : xhci_halt [xhci_hcd]   Call trace:    xhci_halt    xhci_gen_setup    xhci_pci_setup    usb_add_hcd    usb_hcd_pci_probe    xhci_pci_common_probe    xhci_pci_renesas_probe  This was hit with a Renesas uPD720201 that failed to power up (\"Unable to change power state from D3cold to D0, device inaccessible\") yet still reached the HCD probe path.  Read the capability register once, and if it reads back the all-ones value (as xhci_handshake() and xhci_reset() already test for), abort setup with -ENODEV before op_regs is derived from it. Reading it once also avoids re-reading a register that may change under a concurrent hot-removal.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-09-04 16:18:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98377",
                                "url": "https://ubuntu.com/security/CVE-2026-98377",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  vlan: require the MAC header to be present in __vlan_insert_inner_tag()  __vlan_insert_inner_tag() only guarantees head room via skb_cow_head(), never that mac_len bytes of MAC header are present.  Its ETH_HLEN wrappers - __vlan_insert_tag() under skb_vlan_push(), and vlan_insert_tag() under validate_xmit_vlan() on the generic transmit path - therefore rewrite the first 16 bytes at skb->data: a 12-byte memmove plus two 2-byte stores at +12 and +14.  No caller supplies the bound, while the pop helpers use skb_ensure_writable()/pskb_may_pull().  An IFF_TUN device has hard_header_len == 0, so packet_snd() accepts a one-byte AF_PACKET/SOCK_RAW frame.  The first vlan push only sets a hwaccel tag; the next - clsact \"action vlan push\" or bpf_skb_vlan_push() - enters the helper with skb->len still 1.  The head comes from skbuff_small_head without __GFP_ZERO, so each push drags bytes from beyond skb->tail into the frame.  After three the one-byte send leaves as 13 bytes carrying 11 bytes of uninitialised slab:    0000: 5a b3 62 12 80 88 ff ff 00 b3 62 12 81            `------------------------------'   only 0x5a was sent; the rest is slab, here the top 56 bits of a   linear-map address  Require the MAC header the helper rewrites to be present, so such a frame is dropped rather than transmitted.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-09 08:16:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98170",
                                "url": "https://ubuntu.com/security/CVE-2026-98170",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  smb: client: fix OOB struct field reads in move_smb2_ea_to_cifs()  In move_smb2_ea_to_cifs(), the while (src_size > 0) loop condition is insufficient. It allows iteration to continue even if the remaining src_size is too small to contain a complete smb2_ea_info structure. Consequently, reads of ea_name_length and ea_value_length can occur out-of-bounds.  Fix this by ensuring src_size >= sizeof(*src) before attempting to read any structure fields. Additionally, reject any next_entry_offset that is smaller than sizeof(*src) or that would advance the pointer beyond the available buffer.  Note that for calls where the server returns a malformed EA list, the error returned to userspace changes from -ENODATA (getxattr) or -ERANGE (listxattr) to -EIO. This correctly signals a server protocol error rather than misleadingly indicating \"attribute not present\" or \"output buffer too small\".",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-06 09:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98171",
                                "url": "https://ubuntu.com/security/CVE-2026-98171",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  smb: client: fix next_buffer UAF and NextCommand bounds in compound PDUs  Fix several related bounds checking and pointer lifecycle issues in receive_encrypted_standard()'s handling of compound encrypted frames:  - Clear next_buffer after assigning it to server->bigbuf. A stale   next_buffer pointer can lead to a use-after-free on subsequent   error paths. - Update pdu_length to the decrypted plaintext size (buf_size). Using   the pre-decryption length allows NextCommand to point into stale   ciphertext residue. - Reject next_cmd values smaller than MID_HEADER_SIZE(server). - Fix an integer overflow in the upper bound check by verifying   pdu_length - next_cmd < MID_HEADER_SIZE(server), ensuring the   trailing slice is large enough for a header.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-06 09:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98169",
                                "url": "https://ubuntu.com/security/CVE-2026-98169",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  smb: client: fix potential OOB read in smb3_enum_snapshots()  If snapshot_array_size is smaller than GMT_TOKEN_SIZE, smb3_enum_snapshots() sets ret_data_len to sizeof(struct smb_snapshot_array) without verifying the actual length of the server's reply.  Because SMB2_ioctl() places no lower bound on the server-supplied OutputCount and allocates retbuf to exactly that length, a short reply results in ret_data_len exceeding the size of retbuf. The subsequent copy_to_user() then reads past the end of retbuf, leaking adjacent slab memory to userspace.  The subsequent clamp check is ineffective as it only reduces ret_data_len.  Fix this by rejecting replies shorter than sizeof(struct smb_snapshot_array) with -EIO. Note that the bound is set to the 12-byte struct size rather than the 16-byte MIN_SNAPSHOT_ARRAY_SIZE defined in MS-SMB2 3.3.5.15.1, because 12 bytes is exactly what copy_to_user() attempts to read.",
                                "cve_priority": "negligible",
                                "cve_public_date": "2026-10-06 09:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98193",
                                "url": "https://ubuntu.com/security/CVE-2026-98193",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: libipw: reject TKIP frames without a full MIC  libipw_michael_mic_verify() assumes that an skb contains an eight-byte Michael MIC. A short TKIP frame makes the unsigned payload length wrap, causing michael_mic() to read past the skb.  Check that the MIC is present before verifying it, and use the existing MICHAEL_MIC_LEN constant for all MIC lengths in the verifier.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-06 09:18:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-97555",
                                "url": "https://ubuntu.com/security/CVE-2026-97555",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  smb: client: fix heap overflow in DACL owner/group rewrite  When id_mode_to_cifs_acl rewrites an existing DACL, it allocates a buffer sized according to the on-disk DACL length reported by dacl_ptr->size. However, replace_sids_and_copy_aces may rewrite each ACE with a new owner/group SID obtained from the cifs.idmap upcall. Those SIDs can have up to SID_MAX_SUB_AUTHORITIES (15) sub-authorities, making each ACE up to 76 bytes (sizeof(struct smb_ace)).  If the original DACL contains short SIDs (e.g., 1 sub-authority) while the replacement SIDs are long, the rewritten ACEs overflow the allocation.  Fix this by always budgeting for worst-case SID expansion: allocate sizeof(struct smb_acl) plus num_aces * sizeof(struct smb_ace), which covers the smb_acl header and room for every ACE at maximum SID size. This replaces the previous split logic that used dacl_ptr->size for cifsacl mounts but num_aces * sizeof(struct smb_ace) for mode_from_sid mounts: both paths can trigger the same rewrite and need the same headroom.  KASAN reports this as:   BUG: KASAN: slab-out-of-bounds in build_sec_desc+0x1e8a/0x2680 [cifs]   Write of size 4 at addr ffff8881a5e25374 by task chown/5298   ...   The buggy address is located 0 bytes to the right of    allocated 884-byte region [ffff8881a5e25000, ffff8881a5e25374)",
                                "cve_priority": "high",
                                "cve_public_date": "2026-09-25 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-97557",
                                "url": "https://ubuntu.com/security/CVE-2026-97557",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  smb: client: avoid leaking refcount in cifs_queue_oplock_break()  cifs_queue_oplock_break() unconditionally takes a reference on the target file before queueing cifs_oplock_break(). Only that work item decreases the reference counter again.  If another oplock break arrives while that work is still queued, queue_work() will return false and not queue this second work item. As a result, we will never reach the point to drop the file reference again and are leaking this reference. This can be triggered when interacting with a slow-responding server.  As a result, later unmount operations for this file system will fail with    BUG: Dentry ... still in use (1) [unmount of cifs cifs]   VFS: Busy inodes after unmount of cifs (cifs)   kernel BUG at fs/super.c:777!  Fix this by only incrementing the reference count if the work has been queued successfully. Taking it after queue_work() is safe because all three callers hold tcon->open_file_lock across the call and _cifsFileInfo_put() decrements under that same lock, so a worker that starts the handler in the window cannot drop the reference before it has been taken.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-09-25 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-97564",
                                "url": "https://ubuntu.com/security/CVE-2026-97564",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  smb: client: reject userspace cifs.idmap descriptions  cifs.idmap key descriptions carry authority-bearing fields (owner and group SIDs and uid/gid values in \"os:\"/\"gs:\"/\"oi:\"/\"gi:\" form) that the cifs.idmap upcall helper treats as kernel-originating inputs.  Unlike its sibling cifs.spnego, the cifs.idmap key type has no vet_description hook, so userspace can create keys of this type through request_key(2)/add_key(2) and supply those fields without CIFS origin. A request_key(2) call with a non-NULL callout then drives a root usermodehelper upcall (/sbin/request-key -> cifs.idmap) that consumes the unvetted description in root context.  Only accept cifs.idmap descriptions while CIFS is using its private root_cred to request the key.  id_to_sid()/sid_to_id() already run under override_creds(root_cred), so the kernel-originated path is unaffected.  This mirrors commit 3da1fdf4efbc (\"smb: client: reject userspace cifs.spnego descriptions\"), which applied the same restriction to cifs.spnego.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-09-25 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-97615",
                                "url": "https://ubuntu.com/security/CVE-2026-97615",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net: bridge: use option bits for CFM/MRP frame handlers  CFM and MRP register a global br_frame_type whose hlist_node is linked into the per-bridge frame_type_list when the first MEP/MRP instance is created. Enabling the protocol on multiple bridges therefore inserts the same node into multiple lists. Unregistering it on one bridge then corrupts list state belonging to another.  These handlers can only be installed once per bridge, and they are uncommon. Track their per-bridge enable state with net_bridge option bits, which already live on the Rx hot cache line, and dispatch the matching handler directly from the receive path. Check both bits together first as an unlikely case.  Remove the generic frame_type_list and br_frame_type helpers, which have had no other users since CFM and MRP were added. That shrinks struct net_bridge by 8 bytes and drops the list walk from the fast path. When neither protocol is compiled in, BR_CFM_MRP_OPTS is 0 and the compiler prunes the branch.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-09-25 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-97901",
                                "url": "https://ubuntu.com/security/CVE-2026-97901",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  genetlink: pin family module during policy dump  The generic netlink controller's policy dump keeps pointers to the target family's operation and policy tables in its callback state.  A dump may be split across multiple skbs and remain pending after the initial request.  Netlink pins the module which owns the dump callback, but in this case that is the controller's owner rather than the target family's owner.  The target family can consequently be unregistered and its module unloaded while a policy dump is pending.  Advancing the dump then dereferences policy memory from the unloaded module.  Take a reference to the target family's module when the dump starts. Drop it from the error and done paths.  This matches the lifetime for which the dump context retains the family and policy pointers.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-09-25 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-97908",
                                "url": "https://ubuntu.com/security/CVE-2026-97908",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  Bluetooth: btqcomsmd: destroy RPMsg endpoints before freeing hci_dev  The command and ACL RPMsg endpoints store struct btqcomsmd as their callback private data. The receive callbacks dereference btq->hdev without taking an hci_dev reference.  The current teardown order frees the hci_dev before destroying the RPMsg endpoints in both the hci_register_dev() error path and the driver remove path. If WCNSS delivers data in that window, the endpoint callback can run with an already freed hci_dev and pass it to the Bluetooth core.  For qcom_smd endpoints, rpmsg_destroy_ept() closes the channel and clears the callback under the channel recv_lock. The receive path holds the same lock while invoking the callback, so destroying the endpoints first both prevents new callbacks and serializes with any callback already running.  Destroy the command and ACL endpoints before hci_free_dev(). Keep hci_unregister_dev() first during remove so the HCI core stops issuing operations before the transport endpoints are shut down. In the full registration-error cleanup path, return directly after freeing the hci_dev to avoid falling through to the partial-construction labels and destroying the endpoints twice.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-09-25 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-97925",
                                "url": "https://ubuntu.com/security/CVE-2026-97925",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  tick/broadcast: Plug clockevents replacement race  朱恺乾 reported and decoded the following race condition when a broadcast device is replaced:  CPUA\t\t\t\t\tCPUB  __tick_broadcast_oneshot_control()    bc = tick_broadcast_device.evtdev; \t\t\t\t\ttick_install_broadcast_device(dev)         \t\t\t\tclockevents_exchange_device(cur, dev) \t\t\t\t\t   shutdown(cur); \t\t\t\t\t   detach(cur); \t\t\t\t\t   cur->handler = noop; \t\t\t\t\t   tick_broadcast_device.evtdev = dev;    tick_broadcast_set_event(bc, next_event); <- FAIL: arms a detached device.  If the original broadcast device has a restricted interrupt affinity mask and the last CPU in that mask goes offline then the BUG() in tick_cleanup_dead_cpu() triggers because the clockevent device is not in detached state.  The reason for this is that tick_install_broadcast_device() is not serialized vs. tick broadcast operations.  The obvious cure is to serialize tick_install_broadcast_device() with tick_broadcast_lock against a concurrent tick broadcast operation.  That requires to split clockevents_exchange_device() into two parts, one which does the exchange, shutdown and detach operation and the other which drops the module reference count. This is required because the module reference cannot be dropped while holding tick_broadcast_lock.  Let clockevents_exchange_device() do both operations as before, but let the broadcast device code take the two step approach and do the device exchange under tick_broadcast_lock and drop the module reference count after releasing it.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-09-25 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-93285",
                                "url": "https://ubuntu.com/security/CVE-2026-93285",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  f2fs: embed f2fs_gc_kthread in f2fs_sb_info  Instead of allocating f2fs_gc_kthread dynamically, embed it in f2fs_sb_info. This simplifies lifetime management and prepares for fixing race conditions during teardown.  - __sbi_store\t\t\t- remount|shutdown \t\t\t\t - f2fs_stop_gc_thread  - access sbi->gc_thread \t\t\t\t  - sbi->gc_thread = NULL  - access sbi->gc_thread->f2fs_gc_task",
                                "cve_priority": "low",
                                "cve_public_date": "2026-09-24 17:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-97529",
                                "url": "https://ubuntu.com/security/CVE-2026-97529",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  scsi: qla2xxx: Validate BSG request_len before reading vendor_cmd[]  The FC BSG transport allocates job->request via memdup_user() using the exact user-supplied request_len. For FC_BSG_HST_VENDOR, fc_bsg_host_dispatch() only guarantees request_len covers msgcode and vendor_id; it does not account for the vendor_cmd[] flexible array.  qla2xxx then reads the command selector vendor_cmd[0] and, in several sub-handlers, vendor_cmd[1]/[2] or structures overlaid on the vendor command area without verifying request_len. A caller holding CAP_SYS_RAWIO can submit a short request whose vendor_id matches the host, triggering out-of-bounds heap reads (KASAN-detectable, and able to mis-select a command or panic).  Add a central guard in qla2x00_process_vendor_specific() so the selector is always in bounds, restrict the early vendor_cmd[0] read in qla24xx_bsg_request() to sufficiently long vendor messages, and add request_len checks to the sub-handlers that read further: qla24xx_proc_fcp_prio_cfg_cmd(), qla2x00_process_loopback(), qla84xx_reset(), qla84xx_updatefw(), qla2x00_read_optrom(), qla2x00_update_optrom(), qlafx00_mgmt_cmd() and qla28xx_validate_flash_image().",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-09-25 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-97536",
                                "url": "https://ubuntu.com/security/CVE-2026-97536",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  scsi: qla2xxx: Fix use-after-free of qpair work on queue teardown  The response queue MSI-X handler qla2xxx_msix_rsp_q() schedules qla_do_work() via queue_work(ha->wq, &qpair->q_work). qla_do_work() dereferences the qpair (vha, rsp) and takes qpair->qp_lock.  During teardown, qla2xxx_delete_qpair() deletes the response queue, which calls free_irq() in qla25xx_free_rsp_que(), and then frees the queue and the qpair. free_irq() waits for running hardirq handlers but does not cancel work already placed on ha->wq. A still-pending q_work then runs qla_do_work() against the freed qpair and response queue, causing a use-after-free. This is especially likely during full adapter teardown, where destroy_workqueue(ha->wq) forces pending work to run after the queue pairs have been freed.  Flush the work item with cancel_work_sync() in qla25xx_free_rsp_que() after free_irq() has released the interrupt (so no new work can be queued) and before the response queue and qpair memory are freed (so the flushed handler still sees valid memory). Guard on rsp->qpair and ha->wq to match the INIT_WORK() condition and avoid operating on an uninitialized work_struct.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-09-25 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-97537",
                                "url": "https://ubuntu.com/security/CVE-2026-97537",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  scsi: qla2xxx: Fix queue teardown NULL dma_free and bitmap locking  qla25xx_free_req_que() and qla25xx_free_rsp_que() have two pre-existing bugs exposed on the error path of qla25xx_create_{req,rsp}_que():   1. When dma_alloc_coherent() fails during queue creation, the error     path calls the free function with req->ring / rsp->ring still NULL     (from kzalloc).  The unconditional dma_free_coherent() with a NULL     cpu_addr is undefined behavior and can panic.   2. The free functions clear req_qid_map / rsp_qid_map under vport_lock,     but the create functions protect the same bitmaps with mq_lock.     This provides no mutual exclusion.  Additionally, the create error     path clears the bit and releases mq_lock before calling the free     function, creating a window where another thread can allocate the     same que_id and have its ha->req_q_map entry clobbered by the     subsequent lockless NULL assignment in the free function.  Fix by:   - Guarding dma_free_coherent() with a NULL check on the ring pointer.   - Using mq_lock (the lock held by all creators) in the free functions    to atomically NULL the map entry and clear the bitmap bit.   - Removing the now-redundant clear_bit blocks from the create error    paths since the free functions handle it atomically.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-09-25 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-89859",
                                "url": "https://ubuntu.com/security/CVE-2026-89859",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  scsi: qla2xxx: Zero dport diagnostics buffer to avoid info leak  qla2x00_do_dport_diagnostics() allocates the qla_dport_diag response buffer with kmalloc_obj() (non-zeroing) and, on success, copies the full sizeof(*dd) back to user space via sg_copy_from_buffer(). The inbound sg_copy_to_buffer() only fills as many bytes as the user request payload provides, and qla26xx_dport_diagnostics() zeroes only dd->buf. The options and unused[] fields are therefore copied out uninitialized, leaking kernel heap contents to user space.  Allocate with kzalloc_obj(), matching qla2x00_do_dport_diagnostics_v2().",
                                "cve_priority": "low",
                                "cve_public_date": "2026-09-16 11:16:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-89921",
                                "url": "https://ubuntu.com/security/CVE-2026-89921",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  KVM: s390: Zero initialize data structures for inject_pfault_token  __kvm_inject_pfault_token() only sets .type and .u.ext.ext_params2 of the on-stack struct kvm_s390_irq but the full ext substructure is copied into the cpu local variable on inject. ext_params and pad contain stale stack values.  Interrupt delivery only uses ext_params2, so nothing leaks to the guest, but a host user can use the migration ioctls to get to the data.  Fix by zero-initializing the irq struct. Do the same for the inti data structure.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-09-16 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-89972",
                                "url": "https://ubuntu.com/security/CVE-2026-89972",
                                "cve_description": "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 reference to ns when kfree(ns) runs.  The normal removal path in nvme_ns_remove() correctly calls synchronize_srcu(&ns->head->srcu) after list_del_rcu() to wait for in-progress readers. Add the same grace period in the error path.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-09-16 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-89988",
                                "url": "https://ubuntu.com/security/CVE-2026-89988",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  kprobes: Protect kprobe_blacklist with RCU  __within_kprobe_blacklist() traverses kprobe_blacklist without holding kprobe_mutex. When a module is unloaded, kprobe_remove_area_blacklist() removes blacklist entries and immediately frees them with kfree(). A concurrent call to within_kprobe_blacklist() can therefore dereference freed memory.  Furthermore, within_kprobe_blacklist() can be called in atomic or non-preemptible contexts where the sleeping kprobe_mutex cannot be taken.  Protect kprobe_blacklist with RCU. Use guard(rcu)() and list_for_each_entry_rcu() for traversal, list_add_tail_rcu() for insertions, list_del_rcu() for deletions, and kfree_rcu() to reclaim entries safely after a grace period.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-09-16 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-90002",
                                "url": "https://ubuntu.com/security/CVE-2026-90002",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ftrace: Take trace_array reference before accessing its ftrace_ops  The trace instance files set_ftrace_filter and set_ftrace_notrace was updated to work with specific trace instances (trace_arrays). The issue is that when these files are opened, there is a small race window where it will use the ftrace_ops from the inode->private pointer to get a reference to the trace_array and then take its reference. The problem is that the ftrace_ops itself could be freed. If the rmdir on the instance happens at the same time the set_ftrace_filter file is opened, the rmdir could have also freed the ftrace_ops and referencing it will cause a use-after-free bug and crash the kernel.  Instead, pass in the trace_array as the file private data (NULL for the top level instance), and then pass both the trace_array and the ftrace_ops to the ftrace_regex_open() function. If the trace_array is NULL, then it just uses the ftrace_ops without the need to take its reference (like normal). If the ftrace_ops is NULL, that is only the case for the top level instance and the global_ops can be used.  This allows the trace_array to have its reference incremented before touching the ftrace_ops that could also be freed when the instance is.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-09-16 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-90016",
                                "url": "https://ubuntu.com/security/CVE-2026-90016",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  staging: rtl8723bs: fix OOB read in rtw_restruct_wmm_ie()  rtw_restruct_wmm_ie() scans in_ie for a WMM IE with:  \twhile (i < in_len) { \t\t... \t\tif (i + 5 < in_len && in_ie[i] == 0xDD && ...) { \t\t\t... \t\t\tbreak; \t\t} \t\ti += (in_ie[i + 1] + 2); /* to the next IE element */ \t}  When the \"i + 5 < in_len\" match check fails simply because i is within 5 bytes of the end of the buffer (i.e. no WMM IE was found near the tail of in_ie), execution falls through to \"i += (in_ie[i + 1] + 2)\", which reads in_ie[i + 1]. If i == in_len - 1 at that point, this is a 1-byte out-of-bounds read of an attacker-influenced IE buffer built from association/scan data.  Commit a75281626fc8f (\"staging: rtl8723bs: fix potential out-of-bounds read in rtw_restruct_wmm_ie\") added the \"i + 5 < in_len\" guard to the match condition itself, but did not add an equivalent guard before the fallthrough advance, so the same class of OOB read remained reachable through the non-matching path.  Add an explicit bounds check before advancing to the next IE.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-09-16 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-90029",
                                "url": "https://ubuntu.com/security/CVE-2026-90029",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  usb: storage: realtek_cr: fix use-after-free on disconnect  realtek_cr_destructor() calls timer_delete() before the chip containing the timer is freed. The timer callback may still be running and can rearm itself, resulting in a use-after-free.  Use timer_shutdown_sync() to wait for the callback and prevent further rearming. Do this unconditionally because ss_en may be changed after the timer is armed.  Move timer_setup() into init_realtek_cr() so the timer is initialized before any failure path can invoke the destructor.  Found by static analysis.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-09-16 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-80947",
                                "url": "https://ubuntu.com/security/CVE-2026-80947",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: rtl8xxxu: fix use-after-free from rx_urb_wq on stop  rtl8xxxu arms rx_urb_wq from the RX completion path: rtl8xxxu_rx_complete() hands the URB to rtl8xxxu_queue_rx_urb(), which queues it on rx_urb_pending_list and, once the list grows past RTL8XXXU_RX_URB_PENDING_WATER, schedules rx_urb_wq.  The worker rtl8xxxu_rx_urb_work() drains rx_urb_pending_list, recovers priv through container_of, and resubmits each URB through rtl8xxxu_submit_rx_urb(), which anchors it on rx_anchor and dereferences priv->udev.  rtl8xxxu_stop() cancels the sibling work items (c2hcmd_work, ra_watchdog, update_beacon_work) but never cancels rx_urb_wq, so a worker armed during the last burst of RX traffic can run rtl8xxxu_rx_urb_work() after rtl8xxxu_disconnect() has called ieee80211_free_hw(), which frees priv, producing a use-after-free.  The window opens under active RX traffic (pending count above the watermark) followed by a disconnect.  There are two teardown races to close:    * rtl8xxxu_queue_rx_urb() decided whether to enqueue under rx_urb_lock     but called schedule_work() after dropping the lock.  A completion     that observed shutdown == false and released the lock could then call     schedule_work() after rtl8xxxu_stop() had set shutdown and     cancel_work_sync() had already returned, arming the worker to run     after the teardown.  Move schedule_work() under the same !shutdown     branch so the arming decision is atomic with the shutdown check.    * rtl8xxxu_rx_urb_work() anchors every URB it drained back onto     rx_anchor through rtl8xxxu_submit_rx_urb().  A worker still running     when usb_kill_anchored_urbs(&priv->rx_anchor) returned would submit a     URB that escaped the kill.  In rtl8xxxu_stop(), call     cancel_work_sync(&priv->rx_urb_wq) before the kill so the worker is     drained first.  After priv->shutdown is set under rx_urb_lock, completions can no longer queue rx_urb_wq. cancel_work_sync() then drains the last queued or running worker, and the following usb_kill_anchored_urbs() kills the URBs it may have submitted.  rtl8xxxu_disconnect() is covered because ieee80211_unregister_hw() guarantees .stop() runs for a live interface before ieee80211_free_hw() frees priv.  The probe error path needs no cancel: rx_urb_wq is INIT_WORK()'d there but cannot have been scheduled, since no URB is submitted before ieee80211_register_hw() succeeds.  This bug was found by static analysis.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-09-11 20:19:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-89481",
                                "url": "https://ubuntu.com/security/CVE-2026-89481",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  nvme-tcp: fix host memory disclosure on R2T for a read command  nvme_tcp_handle_r2t() does not check the direction of the request the R2T refers to. A malicious controller can send an R2T for a READ and the host will answer it: nvme_tcp_setup_h2c_data_pdu() builds the H2CData header and nvme_tcp_try_send_data() sends the request's data buffer. That buffer is the READ destination, so its contents go to the controller.  The command then completes normally and nothing is logged.  Against a test controller that answers every READ with an R2T, a 4096 byte buffered read returned all 4096 bytes, split over two R2Ts. The pages contained stale kernel data, including an array of struct page pointers.  Reject an R2T for a request that is not a write.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-09-11 20:19:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-89492",
                                "url": "https://ubuntu.com/security/CVE-2026-89492",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ocfs2: validate directory-index entry counts when reading metadata  ocfs2_validate_dx_leaf() and ocfs2_validate_dx_root() check the ECC and signature of an indexed-directory block before it reaches higher-level callers, but neither validator bounds the ocfs2_dx_entry_list counts against the capacity of the block that holds them.  ocfs2_dx_dir_search() then walks  \tfor (i = 0; i < le16_to_cpu(entry_list->de_num_used); i++) \t\tdx_entry = &entry_list->de_entries[i];  over de_num_used entries with no bounds check.  entry_list is either dx_leaf->dl_list (from ocfs2_read_dx_leaf) or, for an inline root, dx_root->dr_entries.  A crafted on-disk image can set de_num_used (and de_count, which is the __counted_by_le() bound of de_entries) to 0xffff and make the walk read far past the end of the 4KB metadata block, giving a slab out-of-bounds read reachable from any path lookup, stat() or open() on an indexed directory once the image is mounted.  Commit 775c17386a6f (\"ocfs2: validate dx_root extent list fields during block read\") already bounds dr_list for the non-inline dx_root, but left the inline dr_entries path and the dx_leaf dl_list unchecked.  Add the same read-time validation for both entry lists: de_count must equal the capacity of the block (ocfs2_dx_entries_per_leaf()/per_root()) and de_num_used must not exceed de_count, rejecting corrupted metadata with -EFSCORRUPTED before ocfs2_dx_dir_search() can walk an out-of-range entry array.  de_count is always written as exactly the block capacity when a leaf or inline root is formatted, so the equality check does not reject any valid image.  Found by 0sec automated security-research tooling (https://0sec.ai).",
                                "cve_priority": "high",
                                "cve_public_date": "2026-09-11 20:19:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-89553",
                                "url": "https://ubuntu.com/security/CVE-2026-89553",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  nouveau/gem: reserve the bo in the info ioctl around the vma lookup  In the non-uvmm path, there could be a race between the info lookup finding the vma, and the gem close path closing the vma leading to a use-after-free.  Spotted with the help of Opus 4.6.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-09-11 20:19:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-89625",
                                "url": "https://ubuntu.com/security/CVE-2026-89625",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  HID: sony: fix UAF of ghl_poke_timer / ghl_urb at driver unbind  For GHL (Guitar Hero Live) dongles, sony_probe() arms a periodic timer: ghl_magic_poke() (the timer callback) submits sc->ghl_urb, and the URB completion ghl_magic_poke_cb() re-arms the timer with mod_timer().  sony_remove() drained the timer with timer_delete_sync() and then freed the URB with usb_free_urb():  \ttimer_delete_sync(&sc->ghl_poke_timer); \tusb_free_urb(sc->ghl_urb);  timer_delete_sync() does not block re-arming, and while the URB is in flight the timer is not pending, so the sync delete is a no-op. A URB completion that runs after the delete re-arms the timer, and usb_free_urb() only drops a reference -- it does not kill an in-flight URB. sc is allocated with devm_kzalloc() and freed once sony_remove() returns, so the re-armed ghl_poke_timer (embedded in sc) then fires on freed memory, a use-after-free from timer softirq. This is a disconnect/rmmod race.  Poison the URB first, then shut the timer down, before freeing the URB. usb_poison_urb() kills any in-flight URB and permanently rejects further submissions, so a poke timer that is still pending cannot re-submit the URB from ghl_magic_poke() in the window before timer_shutdown_sync() runs. usb_kill_urb() would not suffice: it only cancels the in-flight URB and leaves it submittable once it returns, so the pending timer could re-submit it and put a fresh URB in flight over the freed sc. timer_shutdown_sync() then drains any last callback and blocks re-arming. The probe error path is unaffected: it is only reached before the timer is armed.  Reproduced under KASAN on next-20260710 via dummy_hcd + raw-gadget emulation of the GHL PS4 dongle (VID 0x1430 / PID 0x07bb): hid-sony binds and arms the poke timer, the poke URB is held in flight, the driver is unbound (freeing sc), then the URB is released. The completion re-arms the timer on the freed sc, and the re-armed timer fires ~8 s later:    BUG: KASAN: slab-use-after-free in ghl_magic_poke+0x98/0xb0   Read of size 8 at addr ffff88810b02fd50 by task swapper/0/0    ghl_magic_poke+0x98/0xb0    call_timer_fn+0x35/0x2b0    __run_timers+0x69c/0x9a0    run_timer_softirq+0x173/0x2a0   Allocated by task 169:  sony_probe   Freed by task 338:      devres_release_group <- hid_device_remove (sony_remove)  Found by 0sec (https://0sec.ai) using automated source analysis.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-09-11 20:19:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-89633",
                                "url": "https://ubuntu.com/security/CVE-2026-89633",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  smb: client: fix OOB read/write from unvalidated DataOffset in coalesce_t2()  coalesce_t2() computes data pointers directly from server-supplied DataOffset fields with no validation against buffer bounds:    data_area_of_tgt = (char *)&pSMBt->hdr.Protocol +                      get_unaligned_le16(&pSMBt->t2_rsp.DataOffset);   data_area_of_src = (char *)&pSMBs->hdr.Protocol +                      get_unaligned_le16(&pSMBs->t2_rsp.DataOffset);   data_area_of_tgt += total_in_tgt;   ...   memcpy(data_area_of_tgt, data_area_of_src, total_in_src);  A small DataOffset can push a pointer below the actual byte area, overwriting header fields; a large one can push it past the buffer end, causing out-of-bounds heap reads (source) or writes (target). The BCC overflow guard does not prevent this: BCC reflects how much data is present, while DataOffset controls where in the buffer it starts.  The \"validate target area\" comment present since the function was first written in 2005 was a placeholder that was never implemented.  Add lower- and upper-bound checks for both data pointers before the memcpy, and before any target header fields are modified.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-09-11 20:19:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-89652",
                                "url": "https://ubuntu.com/security/CVE-2026-89652",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ceph: bound copied dentry name length in NFS export get_name  ceph_get_name() copies the MDS-supplied name into the caller's NAME_MAX-sized buffer with memcpy(name, rinfo->dname, rinfo->dname_len) and then writes name[rinfo->dname_len] = 0, without checking dname_len against NAME_MAX. A malicious or buggy MDS that returns a LOOKUPNAME reply with dname_len > NAME_MAX overflows the buffer. __get_snap_name() copies rde->name / rde->name_len the same unchecked way.  Impact: a malicious or compromised Ceph MDS overflows the NAME_MAX name buffer in a client's NFS-export get_name path, a slab out-of-bounds write reported by KASAN. Reachable when a CephFS mount is re-exported over NFS.  Add ceph_export_copy_name(), which rejects lengths above NAME_MAX with -ENAMETOOLONG before the copy, and use it in both ceph_get_name() and __get_snap_name().",
                                "cve_priority": "critical",
                                "cve_public_date": "2026-09-11 20:19:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-89680",
                                "url": "https://ubuntu.com/security/CVE-2026-89680",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  nfsd: fix nfsd_file leak on inter-server COPY setup failure  When nfsd4_setup_inter_ssc() fails, nfsd4_copy() returns nfserr_offload_denied directly, bypassing the out: label where release_copy_files() would drop the nf_dst reference taken by nfs4_preprocess_stateid_op(). Each failed inter-server COPY leaks one nfsd_file, pinning file/inode/dentry/vfsmount.  Fix by setting status and jumping to out: instead of returning directly.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-09-11 20:19:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-89761",
                                "url": "https://ubuntu.com/security/CVE-2026-89761",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  apparmor: fix out-of-bounds write when null terminating a label vec  aa_vec_unique() null terminates at vec[n - dups] when VEC_FLAG_TERMINATE is passed. If the components are all distinct no duplicates are dropped, dups is 0 and the terminator goes to vec[n], so the caller has to provide room for n + 1 entries.  aa_label_strn_parse() sets up its vector with vec_setup(profile, vec, len, gfp) and then calls aa_vec_unique(vec, len, VEC_FLAG_TERMINATE), but vec_setup() does not reserve the terminator entry. Up to LOCAL_VEC_ENTRIES it uses the local array of LOCAL_VEC_ENTRIES pointers, above that it allocates exactly len pointers. The terminator therefore lands one entry past the end of the local array when len is LOCAL_VEC_ENTRIES, and one entry past the end of the allocation when len is larger.  len comes from the number of \"//&\" separated components in the label name and label_count_strn_entries() does not bound it. An unprivileged task reaches the parse by writing to /proc/self/attr/apparmor/current or through lsm_set_self_attr(2), both of which go through do_setattr(), and the name is parsed before the change_profile permission is checked. The query_label() path behind the securityfs .access file, which is mode 0666, performs no permission check at all. Every component has to resolve to a loaded profile, so a system with policy loaded is required.  The other two VEC_FLAG_TERMINATE users work on a label vec that aa_label_alloc() has already sized with \"+ 1 for null terminator entry on vec\". Reserve the same entry in vec_setup() and DEFINE_VEC(). Passing len + 1 from the caller instead would move len == LOCAL_VEC_ENTRIES out of the local array and into kzalloc().",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-09-11 20:20:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-80852",
                                "url": "https://ubuntu.com/security/CVE-2026-80852",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  tls: device: fix out-of-bounds write in tls_append_frag()  Found with syzkaller and a local syzbot instance running on top of a netdevsim TLS offload emulation; tls_device.c is otherwise only reachable on a machine with a NIC that implements the offload.  tls_push_data() only checks whether the open record still has room for another frag at the bottom of its loop, and the MSG_MORE early break skips that check.  The record survives to the next syscall with the frag count it already had, and tls_append_frag() does not check either, so with TLS_TX_ZEROCOPY_RO every splice(SPLICE_F_MORE) of a byte or two adds a non-coalescing pipe page and num_frags walks off the end of tls_record_info.frags[MAX_SKB_FRAGS].  Once the record is pushed, tls_push_record() runs the same index over sg_tx_data[MAX_SKB_FRAGS] and the sg_set_page() writes land on the destruct_work that follows it, which the workqueue then calls.  The byte limit is fine because copy drops to 0 and the loop falls through to the same check; the frag count has no such feedback.  Push the record rather than keep a full one open, which is what a plain TCP socket does - tcp_sendmsg_locked() uses tcp_mark_push() and new_segment in both the copy and the MSG_SPLICE_PAGES paths, and tls_sw already sets full_record when the sk_msg ring fills up, MSG_MORE or not.    BUG: KASAN: slab-out-of-bounds in tls_append_frag ( net/tls/tls_device.c:269)   Write of size 8 at addr ffff8881104d1530 by task tls_oob/450    CPU: 2 UID: 0 PID: 450 Comm: tls_oob Not tainted 7.2.0-rc7+ #329 PREEMPT   Call Trace:    <TASK>    dump_stack_lvl (lib/dump_stack.c:94 lib/dump_stack.c:120)    print_report (mm/kasan/report.c:378 mm/kasan/report.c:482)    kasan_report (mm/kasan/report.c:595)    tls_append_frag (net/tls/tls_device.c:269)    tls_push_data (net/tls/tls_device.c:518)    tls_device_sendmsg (net/tls/tls_device.c:583)    inet_sendmsg (net/ipv4/af_inet.c:865)    sock_sendmsg (net/socket.c:775 net/socket.c:790 net/socket.c:813)    splice_to_socket (fs/splice.c:884)    do_splice (fs/splice.c:936 fs/splice.c:1349)    __do_splice (fs/splice.c:1431)    __x64_sys_splice (fs/splice.c:1634 fs/splice.c:1616)    do_syscall_64 (arch/x86/entry/syscall_64.c:63 arch/x86/entry/syscall_64.c:94)    entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:121)    </TASK>  and, once the record is pushed:    UBSAN: array-index-out-of-bounds in net/tls/tls_device.c:300:24   index 18 is out of range for type 'skb_frag_t [17]'   UBSAN: array-index-out-of-bounds in net/tls/tls_device.c:301:41   index 18 is out of range for type 'scatterlist [17]'   UBSAN: array-index-out-of-bounds in net/tls/tls_device.c:302:39   index 18 is out of range for type 'scatterlist [17]'   UBSAN: array-index-out-of-bounds in net/tls/tls_device.c:307:38   index 26 is out of range for type 'scatterlist [17]'    kernel tried to execute NX-protected page - exploit attempt? (uid: 0)   BUG: unable to handle page fault for address: ffffea000411a680   #PF: supervisor instruction fetch in kernel mode   #PF: error_code(0x0011) - permissions violation   Oops: Oops: 0011 [#1] SMP KASAN PTI   Workqueue: ktls_device_destruct 0xffffea000411a680   RIP: 0010:0xffffea000411a680   Call Trace:    <TASK>    worker_thread (kernel/workqueue.c:3405 kernel/workqueue.c:3486)    kthread (kernel/kthread.c:436)    ret_from_fork (arch/x86/kernel/process.c:158)    ret_from_fork_asm (arch/x86/entry/entry_64.S:245)    </TASK>",
                                "cve_priority": "high",
                                "cve_public_date": "2026-09-04 16:18:00 UTC"
                            }
                        ],
                        "log": [
                            "",
                            "  * jammy/linux-kvm: 5.15.0-1113.118 -proposed tracker (LP: #2173211)",
                            "",
                            "  [ Ubuntu: 5.15.0-204.214 ]",
                            "",
                            "  * jammy/linux: 5.15.0-204.214 -proposed tracker (LP: #2173225)",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857)",
                            "    - device property: Add cleanup.h based fwnode_handle_put() scope based",
                            "      cleanup.",
                            "    - device property: fix infinite loop in fwnode_for_each_child_node()",
                            "    - ocfs2: validate dx_root extent list fields during block read",
                            "    - nvme-tcp: validate R2T PDU in nvme_tcp_handle_r2t()",
                            "    - staging: rtl8723bs: fix spacing around operators",
                            "    - Bluetooth: btqcomsmd: Convert to platform remove callback returning void",
                            "    - io_uring/rw: end write accounting from ->ki_complete",
                            "    - ALSA: usb-audio: Optimize the copy of packet sizes for implicit fb",
                            "      handling",
                            "    - ALSA: usb-audio: Clamp implicit feedback packet count to URB capacity",
                            "    - perf tools: Fix a asan issue in parse_events_multi_pmu_add()",
                            "    - perf test bpf: Address error about non-null argument for epoll_pwait 2nd",
                            "      arg",
                            "    - zram: fixup read_block_state()",
                            "    - nfsd: size fh_verify server sockaddr slot by xpt_locallen",
                            "    - nfsd: check nfsd4_acl_to_attr() return value in nfsd4_create()",
                            "    - coresight: etm3x: Fix cntr_val_show() to match cntr_val_store() behavior",
                            "    - kernel/params.c: Use kstrtobool() instead of strtobool()",
                            "    - params: Do not go over the limit when getting the string length",
                            "    - params: Use size_add() for kmalloc()",
                            "    - params: Sort headers",
                            "    - params: Fix multi-line comment style",
                            "    - dmaengine: Add devm_dma_request_chan()",
                            "    - i2c: mxs: fix DMA channel leak on probe error",
                            "    - power: supply: rt9455: Convert to i2c's .probe_new()",
                            "    - i2c: core: Introduce i2c_client_get_device_id helper function",
                            "    - power: supply: max17040: Convert to i2c's .probe_new()",
                            "    - power: supply: max17040: drop incorrect I2C functionality check",
                            "    - hwrng: stm32 - Fix runtime PM cleanup on registration failure",
                            "    - spi: bcm63xx: disable clock on resume failure",
                            "    - staging: sm750fb: fix mono image source stride mismatch in",
                            "      lynxfb_ops_imageblit()",
                            "    - ftrace: Synchronize the initialization of ftrace_ops",
                            "    - arm64: allow pte_offset_map() to fail",
                            "    - mm/mremap: reset unfaulted VMA page offset for MREMAP_DONTUNMAP",
                            "    - media: rkvdec: Propagate platform_get_irq() errors",
                            "    - media: zoran: Avoid freeing a registered video_device twice",
                            "    - scsi: qla2xxx: Fix 64G link speed reporting in get_data_rate",
                            "    - ring-buffer: Acquire the lock with irqsave in rb_wake_up_waiters()",
                            "    - smb: client: fix file type corruption in cifs_reparse_point_to_fattr()",
                            "    - smb: client: avoid leaking refcount when cifs_sb_tlink() fails",
                            "    - watchdog: rtd119x: Use devm_clk_get_enabled() helper",
                            "    - perf/x86/intel: Remove anythread_deprecated bit from perf_capabilities",
                            "    - smb3: make query_on_disk_id open context consistent and move to common",
                            "      code",
                            "    - net: ipconfig: Remove outdated comment and indent code block",
                            "    - pinctrl: sunxi: Refactor register/offset calculation",
                            "    - pinctrl: sunxi: Use devm_clk_get_enabled() helpers",
                            "    - pinctrl: sunxi: keep a shadow copy of the data register output latches",
                            "    - net: ena: Remove autopolling mode",
                            "    - netfilter: nf_tables: set->ops->insert returns opaque set element in",
                            "      case of EEXIST",
                            "    - smb: client: validate POSIX create context length",
                            "    - Bluetooth: btusb: Add IMC Networks QCA9377 to quirks table",
                            "    - HID: core: remove #ifdef CONFIG_PM from hid_driver",
                            "    - HID: hid-alps: use default remove for hid device",
                            "    - HID: hid-alps: Use pm_ptr instead of #ifdef CONFIG_PM",
                            "    - smb/client: use stack-allocated smb2_file_all_info in",
                            "      smb3_query_mf_symlink()",
                            "    - smb/client: pass cifs_open_info_data to SMB2_open()",
                            "    - smb: client: close handle after create-context parsing failure",
                            "    - ALSA: usb-audio: Apply IGNORE_CTL_ERROR quirk to all Audient devices",
                            "    - of/irq: Fix remaining refcount leaks in of_irq_init()",
                            "    - wifi: cfg80211: avoid double free if updating BSS fails",
                            "    - drm/msm/a6xx: Avoid a nullptr dereference when speedbin setting fails",
                            "    - openvswitch: add nf_ct_is_confirmed check before assigning the helper",
                            "    - rds_tcp: close NULL deref window in rds_tcp_set_callbacks",
                            "    - of/irq: add missing of_node_put() for interrupt parent node",
                            "    - ALSA: caiaq: unregister the input device when probe fails",
                            "    - perf/core: Fix WARN in perf_sigtrap()",
                            "    - scsi: qla2xxx: Fix NVMe abort reference leak on repeated abort",
                            "    - mtd: core: clear out unregistered devices a bit more",
                            "    - mtd: core: Drop duplicate NULL checks around nvmem_unregister()",
                            "    - mtd: core: Fix refcount error in del_mtd_device()",
                            "    - mtd: use refcount to prevent corruption",
                            "    - mtd: call external _get and _put in right order",
                            "    - nvmet: preserve device path on allocation failure",
                            "    - of/overlay: don't create \"//\" paths for fragments targeting the root",
                            "    - ASoC: wm8903: Move the DRC QR threshold to the register that holds it",
                            "    - ASoC: codecs: rt274: Fix format setting for 44100 rate",
                            "    - Bluetooth: hci_core: free the HCI ID if naming fails",
                            "    - netfilter: ipset: do not update comments from kernel-side adds",
                            "    - net: systemport: Fix RUNT MIB counter register offset calculation",
                            "    - net/sched: fq_codel: match the no-drop threshold to the packet size",
                            "    - net/sched: sch_codel: match the no-drop threshold to the packet size",
                            "    - tcp: refresh TS.Recent for accepted old ACKs",
                            "    - ipvs: fix missing counter decrement in lblc",
                            "    - ipvs: do not create invisible templates",
                            "    - net: add and use skb_get_hash_net",
                            "    - i2c: at91: release DMA channels when probe defers",
                            "    - PCI: Accept AtomicOps already enabled by the hypervisor",
                            "    - drm/radeon: Read the VRAM VBIOS signature with readb()",
                            "    - kgdboc: Fix tty driver reference leak in configure_kgdboc()",
                            "    - Input: atkbd - skip deactivate for Lenovo IdeaPad Slim 3 15IWC11",
                            "    - Input: i8042 - add nomux quirk for Fujitsu LIFEBOOK U7410",
                            "    - Input: synaptics - add LEN205b entry to smbus_pnp_ids for ThinkPad T490",
                            "    - Input: synaptics - limit T440p InterTouch quirk to LEN0036",
                            "    - USB: cdc-acm: fix racy TIOCMIWAIT implementation",
                            "    - usb: hub: use shorter 120ms post resume hold for SS root hubs",
                            "    - usb: ohci-da8xx: disable controller wakeup on cleanup",
                            "    - usb: ohci-s3c2410: disable controller wakeup on removal",
                            "    - usb: ohci-st: disable controller wakeup on removal",
                            "    - usb: typec: ucsi: Get the connector fwnode based on reg value",
                            "    - usb: typec: ucsi: displayport: Current CAM OOB index fixup",
                            "    - tty: amiserial: fix broken TIOCMIWAIT",
                            "    - tty: serial: qcom_geni_serial: Keep console RX functional after deep",
                            "      idle",
                            "    - serial: tegra: don't clear the Tx FIFO on an Rx-only reset",
                            "    - serial: vt8500: Fix clock reference leak in vt8500_serial_probe()",
                            "    - Bluetooth: hci_core: Fix inquiry cache timestamps on 64-bit systems",
                            "    - mtd: rawnand: vf610_nfc: fix reads on chips with more than 64 bytes of",
                            "      OOB",
                            "    - mtd: spinand: fix zero oobavail when no ECC engine is used",
                            "    - USB: serial: cp210x: add Corsair AX1500i Power Supply",
                            "    - USB: serial: quatech2: fix baud rate overflow",
                            "    - USB: serial: ssu100: fix baud rate overflow",
                            "    - USB: serial: option: add support for SIMCom SIM8260C",
                            "    - USB: serial: option: add Quectel EG060W",
                            "    - USB: serial: option: add Compal EXM-G1x support",
                            "    - USB: serial: option: add Quectel RG660QB",
                            "    - USB: serial: option: add Compal EXC-T1 support",
                            "    - iio: accel: sca3000: fix frequency divider condition check",
                            "    - iio: adc: sun4i-gpadc-iio: drop underflowing pm_runtime_put() calls",
                            "    - iio: proximity: isl29501: Fix return type of isl29501_register_write",
                            "    - iio: proximity: vcnl3020: fix ISR bitmask check in IRQ handler",
                            "    - iio: trigger: cancel reenable_work before freeing trigger",
                            "    - Revert \"scsi: sd: sd_zbc: Use logical blocks as unit when querying",
                            "      zones\"",
                            "    - SUNRPC: fix gssx_dec_option_array error path bugs",
                            "    - vc_screen: reload vc pointer before if (ret) in vcs_write() to avoid UAF",
                            "    - mtd: rawnand: vf610_nfc: fix false bitflips on reads of erased pages",
                            "    - wifi: wl12xx: Drop if with an always false condition",
                            "    - wifi: wlcore: Convert to platform remove callback returning void",
                            "    - wifi: wlcore: Fix runtime PM leak in wlcore_remove()",
                            "    - net: usb: qmi_wwan: add Quectel EG120K-EA",
                            "    - serial: imx: Convert to platform remove callback returning void",
                            "    - usb: gadget: at91_udc: Convert to platform remove callback returning",
                            "      void",
                            "    - usb: typec: tcpm: fix debug accessory mode detection for sink ports",
                            "    - usb: typec: tcpm: constrain TCPM_SOURCING_VBUS event handling",
                            "    - drm/amd/pm/si: Check AMD_IS_MOBILITY flag for PPSMC_SYSTEMFLAG_GPIO_DC",
                            "    - soc: qcom: geni-se: Correct QUP Core ICC vote constants",
                            "    - usb: dwc3: gadget: fix IRQ storm on invalid event buffer count",
                            "    - arm64: errata: Factor out broken AMU const counter cap",
                            "    - [Config] enable ARM64_WORKAROUND_BROKEN_AMU_CONSTCNT",
                            "    - arm64: errata: Add Cortex-A725 erratum 3821522 workaround",
                            "    - [Config] arm64: errata: Add Cortex-A725 erratum 3821522 workaround",
                            "    - iio: buffer: serialize buffer teardown with mode claims",
                            "    - KVM: arm64: Don't use the VMA to size stage-2 block mappings for",
                            "      VM_PFNMAP",
                            "    - fsverity: add dependency on 64K or smaller pages",
                            "    - drm/amd/display: check dc_state_create_copy() for NULL in dm_suspend",
                            "    - drm/amd/pm/si: Fix updating clock limits on AC/DC",
                            "    - drm/amdgpu: reset VI ASIC on MacBookPro15,1",
                            "    - drm/amdgpu: reset VI ASIC on MacBookPro14,3",
                            "    - drm/amdgpu: fix for coding style issues",
                            "    - usb: octeon-hcd: fix the FIFO-flush timeout computation",
                            "    - usb: ohci-spear: Remove unnecessary NULL check before",
                            "      clk_disable_unprepare()",
                            "    - usb: ohci-spear: disable controller wakeup on removal",
                            "    - usb: typec: ucsi: acpi: Assume UCSI 1.2 on Acer Nitro ANV15-41",
                            "    - tty: reformat kernel-doc in tty_io.c",
                            "    - Input: s6sy761 - fix resume ordering and restore sensing",
                            "    - tty: vt: fix memory leak in vc_allocate()",
                            "    - serial: fix TIOCMIWAIT race",
                            "    - drm/amd/display: Mark DCE 6.4 as not APU",
                            "    - mtd: spinand: Enable QE on all dies",
                            "    - USB: serial: clean up core error labels",
                            "    - tty: introduce and use tty_port_tty_vhangup() helper",
                            "    - mm/hugetlb: fix avoid_reserve to allow taking folio from subpool",
                            "    - iio: adc: aspeed: propagate reset deassert errors",
                            "    - iio: adc: max1363: sign-extend bipolar differential channel reads",
                            "    - HID: core: introduce hid_safe_input_report()",
                            "    - HID: uhid: convert to hid_safe_input_report()",
                            "    - crypto: drbg - Fix ineffective sanity check",
                            "    - ipv4: stop PMTU walk when nexthop group shrinks",
                            "    - Revert \"wifi: libertas: reject short monitor TX frames\"",
                            "    - sctp: copy zeroed stats to user in sctp_getsockopt_pr_streamstatus()",
                            "      when !streamoute",
                            "    - keys: finalize persistent keyring timeout after link attempt",
                            "    - dm-snap: reject the transient exception store for snapshot-merge",
                            "    - mmc: cavium-octeon: destroy slot platform devices on remove",
                            "    - mmc: cavium-thunderx: destroy slot platform devices on remove",
                            "    - net: usb: ax88179_178a: fix rx frame length for non-last packets",
                            "    - nvme: fix swapped ZRASF zone state values for full and read only",
                            "    - scsi: qedi: Initialize callback state before registration",
                            "    - drm/gud: don't keep a connector without a CRTC as connector_state",
                            "    - drm/amdgpu: make Mac FB workaround generic",
                            "    - fs: refuse fspick() on internal superblocks",
                            "    - drm/dp: don't mark the AUX backlight enabled when enabling failed",
                            "    - drm/aspeed: Balance the display clock enable on teardown",
                            "    - ASoC: adau1372: fix invalid default state of output ASRC and DAC muxes",
                            "    - net/mlx5e: Order ICOSQ cc update after CQ doorbell",
                            "    - mtd: fix use-after-free in mtd release",
                            "    - mtd: Clean refcounting with MTD_PARTITIONED_MASTER",
                            "    - mtd: maps: vmu-flash: Fix the (mtd core) switch to ref counters",
                            "    - mtd: fix double free and WARN_ON in add_mtd_device() error paths",
                            "    - dlm: validate length in dlm_search_rsb_tree",
                            "    - openvswitch: vport: fix self-deadlock on release of tunnel ports",
                            "    - smb: client: reject short Next offsets in parse_server_interfaces()",
                            "    - can: fix unique skb identifier regression under RPS",
                            "    - drm/amd/display: Don't replace a sink mode that shares the native totals",
                            "    - HID: hid-steam: Fix cleanup in probe()",
                            "    - HID: hid-steam: Make client_opened a counter",
                            "    - HID: steam: Fully unregister controller when hidraw is opened",
                            "    - HID: steam: Clean up locking",
                            "    - selinux: fix data race on AVC latest_notif",
                            "    - EDAC/amd64: Mask UMC chip select to the four implemented selects",
                            "    - mm/mremap: fix locked_vm leak by splitting VMA for MREMAP_DONTUNMAP",
                            "    - mm/mremap: fix locked_vm leak from MREMAP_DONTUNMAP self-merge",
                            "    - netfilter: nf_tables: fix bidirectional offload regression",
                            "    - net: team: Remove unused team_mode_op, port_enabled",
                            "    - net: team: Rename port_disabled team mode op to port_tx_disabled",
                            "    - Bluetooth: RFCOMM: connect the session socket without rfcomm_mutex",
                            "    - pmdomain: rockchip: fix clock leak on domain probe failure",
                            "    - pmdomain: rockchip: don't ignore clock lookup errors on attach",
                            "    - pmdomain: rockchip: propagate subdomain add errors",
                            "    - drm/amdgpu: copy debugfs register data outside the GRBM/SRBM locks",
                            "    - namespace: check the target before walking it in do_mount_setattr()",
                            "    - fcntl: refuse F_SET_RW_HINT on an immutable inode",
                            "    - netfilter: nf_tables: fix crash when nf_trace is enabled",
                            "    - tty: finish kernel-doc of tty_struct members",
                            "    - tty: add break_wait kernel-doc",
                            "    - xfrm: prevent policy_hthresh.work from racing with netns teardown",
                            "    - xfs: log items should have a xlog pointer, not a mount",
                            "    - xfs: aborting inodes on shutdown may need buffer lock",
                            "    - xfs: fix super block buf log item UAF during force shutdown",
                            "    - xfs: buffer pins need to hold a buffer reference",
                            "    - xfs: xfs_ifree_cluster vs xfs_iflush_shutdown_abort deadlock",
                            "    - xfs: catch stale AGF/AGF metadata",
                            "    - xfs: rearrange code in xfs_buf_item.c",
                            "    - xfs: factor out stale buffer item completion",
                            "    - xfs: fix unmount hang with unflushable inodes stuck in the AIL",
                            "    - power: supply: ds2780: Fix ds2780_get_capacity() returning raw value",
                            "    - ASoC: stm32: spdifrx: fix synchronization state check",
                            "    - ASoC: cs42l56: Put the Limiter Cushion control on the limiter register",
                            "    - ASoC: cs42l52: Fix the NG Type Switch bit",
                            "    - ASoC: pcm3168a: Fix the DAC zero flag polarity bit",
                            "    - ASoC: max98371: Fix the Speaker DHT Min Volume bits",
                            "    - ASoC: wm8978: Fix the 128x oversampling switch bits",
                            "    - ASoC: nau8822: Fix the 128x oversampling switch bits",
                            "    - netlink: remove netlink_broadcast_filtered",
                            "    - netlink: Reverse the patch which removed filtering",
                            "    - nios2: fix __wsum type degradation in csum_fold()",
                            "    - scsi: st: Save the visited block for the partition the drive is in",
                            "    - samples: pidfd: fix userprogs typo",
                            "    - clone: add CLONE_AUTOREAP",
                            "    - exit: fix lost-update race on the child_subreaper bitfields",
                            "    - tools: gpio: fix building from the top level with O=",
                            "    - i2c: qcom-cci: Fix HALT_ACK reset request being dropped",
                            "    - drm/amdgpu/sdma3: Work around POLL_REGMEM / FENCE hang",
                            "    - tracing: Fix the shift out of bounds in the log2 histogram modifier",
                            "    - cgroup: fix spurious SIGKILL of CLONE_INTO_CGROUP children",
                            "    - dm cache: fix demotion stats in passthrough mode",
                            "    - dm cache: fix issue with background work locking",
                            "    - dm-ebs: fix incorrect device offset check in ebs_ctr()",
                            "    - tipc: protect node reset trace dump with node lock",
                            "    - drm/amdgpu: Fix VCE 3 ring align_mask",
                            "    - KVM: x86/mmu: Preserve nested TDP shadow page tables if they are used as",
                            "      roots",
                            "    - tracing/histograms: Reject non-stacktrace fields for synthetic",
                            "      stacktrace fields",
                            "    - dm-integrity: require stable writes for internal hash modes",
                            "    - cifs: add revalidation on FSCTL failure in smb2_duplicate_extents()",
                            "    - SAUCE: Revert \"md: move initialization and destruction of 'io_acct_set'",
                            "      to md.c\"",
                            "    - md: move initialization and destruction of 'io_acct_set' to md.c",
                            "    - net_sched: codel: fix stale state for empty flows in fq_codel",
                            "    - Bluetooth: L2CAP: access chan->conn safely in get/setsockopt",
                            "    - Bluetooth: L2CAP: refuse __l2cap_chan_add if chan already has conn",
                            "    - tracing: Reject incomplete event filter expressions",
                            "    - tracing: Save the event file instead of the compatible histogram",
                            "    - tracing: Unregister field variable histograms when the command fails",
                            "    - tracing: Fix 64-bit and signed histogram fields on 32-bit kernels",
                            "    - keys: Avoid the owner account dereference in named keyring lookup",
                            "    - keys: Check the authorization payload in process keyring searches",
                            "    - keys: Protect the type name while describing a key",
                            "    - keys: make keyring indexes independent of kernel addresses",
                            "    - keys: Protect the read method check against type removal",
                            "    - KEYS: Fix key_reject_and_link() race with keyring restriction",
                            "    - KEYS: trusted: Fix blob allocation size in tpm2_key_decode()",
                            "    - keys/trusted_keys: return immediately after TPM unseal failure",
                            "    - io-wq: order the exit bit against worker creation task work",
                            "    - signal: don't retarget shared signals in a dying thread group",
                            "    - Linux 5.15.224",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99115",
                            "    - ksmbd: fill in FileSysIdentifier in FS_POSIX_INFORMATION",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99113",
                            "    - ksmbd: zero the FS_OBJECT_ID_INFORMATION buffer before filling it in",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99114",
                            "    - ksmbd: initialize FileSystemControlFlags in FS_CONTROL_INFORMATION",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99132",
                            "    - xfs: don't hold buffer locks across sync transaction commit in",
                            "      xfs_sync_sb_buf",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99135",
                            "    - dm-integrity: fix infinite loop on discard with large tag size",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99118",
                            "    - drm/i915/dmc: Harden DMC firmware payload parsing",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99169",
                            "    - futex: Fix mm reuse handling for FUT_OFF_MMSHARED",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99161",
                            "    - i2c: viai2c-wmt: Fix clock leak in wmt_i2c_probe()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99077",
                            "    - ipv4: udp: Create exceptions before socket matching",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99123",
                            "    - vsock/virtio: validate packet source for connected sockets",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-89987",
                            "    - mm/huge_memory: transfer the pmd dirty bit to the folio on zap",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-80572",
                            "    - Input: byd - synchronize timer deletion before freeing private data",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99180",
                            "    - unicode: free the map after a grace period",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99179",
                            "    - watch_queue: Fix note pool publication race in watch_queue_set_size()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-89912",
                            "    - KVM: arm64: vgic-its: Don't dereference a NULL collection on ITT save",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99156",
                            "    - scsi: st: Fix use-after-free race between st_remove() and st_open()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99112",
                            "    - net/sched: cls_flower: validate mask pointer after nla_next()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99117",
                            "    - net: bridge: mcast: don't truncate the port group walk on teardown",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-74405",
                            "    - OPP: Fix race between OPP addition and lookup",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-74739",
                            "    - net/sched: cls_u32: skip hash tables in u32_bind_class()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-64015",
                            "    - security/keys: fix missed RCU read section on lookup",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-74672",
                            "    - mm/vmalloc: acquire init_mm lock on huge vmap to avoid ptdump UAF",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99121",
                            "    - ipv4: avoid divide by zero in fib_rebalance",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99124",
                            "    - s390/pci: Fix leak of uninitialized kernel data in SCLP report",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99126",
                            "    - s390/ctcm: Prevent XID null dereference",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99127",
                            "    - page_pool: keep frag_offset aligned for odd-sized requests",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99128",
                            "    - sctp: validate chunk length in the inqueue parser",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99133",
                            "    - net/iucv: fix the recvmsg window update",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99136",
                            "    - dm-crypt: fix a tiny race condition in crypt_dec_pending",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99138",
                            "    - tcp: fix use-after-free in do_tcp_getsockopt(TCP_CC_INFO)",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99100",
                            "    - wifi: p54: validate firmware record lengths",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99140",
                            "    - tracing: Fix hist trigger timestamps for buffered events",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99150",
                            "    - drm/amdgpu: don't drop the runtime PM reference twice in amdgpu_gpr",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99152",
                            "    - scsi: libiscsi: Validate the task named by a management response",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99153",
                            "    - scsi: libiscsi: Validate the ITT reflected in a Reject PDU",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99154",
                            "    - scsi: libiscsi: Reject a negative task index from parse_pdu_itt",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99165",
                            "    - sctp: revalidate output stream after association connect wait",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99166",
                            "    - net: rds: fix uninitialized trans dereference in CM event handler",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99167",
                            "    - net/sched: fix use-after-free in __tcf_action_put()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99175",
                            "    - fsnotify: prevent mark additions during connector teardown",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99176",
                            "    - KVM: nVMX: Reset MMU back to the root MMU if loading L2 state fails for",
                            "      !VM-Entry",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99181",
                            "    - autofs: ignore notification errors from a replaced pipe",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99201",
                            "    - netlink: avoid hashing the network namespace pointer",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99203",
                            "    - pipe: preserve existing fasync readers on writer setup failure",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99204",
                            "    - ocfs2/dlm: Protect the recovery list during debugfs reads",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99206",
                            "    - scsi: target: iscsi: Fix race in discovery auth updates",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99211",
                            "    - netlink: reset skb headers before unicast and multicast filtering",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99212",
                            "    - net/rds: don't let the rdma_cm destroy an id RDS still owns on route",
                            "      failure",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99213",
                            "    - vsock: treat TCP_CLOSING as once-established",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99216",
                            "    - Drivers: hv: Don't reset VMBus connection state on error/exit paths",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2022-50167",
                            "    - bpf: fix potential 32-bit overflow when accessing ARRAY map element",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99082",
                            "    - KVM: x86: Use active memslots for the per-vCPU MMIO cache",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99083",
                            "    - ksmbd: fix heap out-of-bounds write in krb5_authenticate()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98977",
                            "    - namespace: handle mount locking for automounts correctly",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98992",
                            "    - namespace: don't copy an unmounted mount tree",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98981",
                            "    - namespace: unhash a dentry before detaching the mounts on it",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99005",
                            "    - drm/i915/gt: Unmask interrupts only when ACTIVE is true",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99007",
                            "    - drm/fb-helper: defer setup when fbdev_probe() fails, not just on -EAGAIN",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99019",
                            "    - scsi: ch: Do not keep references to data transfer element devices",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99024",
                            "    - optee: register TEE devices only once fully initialized",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99036",
                            "    - dm: fix reading free memory in do_resume",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98985",
                            "    - namespace: check the mounts before reading their parents in pivot_root()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98993",
                            "    - namespace: don't inherit MNT_UMOUNT in clone_mnt()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99002",
                            "    - drm/vmwgfx: validate pitch coming from userspace",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99027",
                            "    - net: team: stop reusing skb after queue override",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-64190",
                            "    - net: team: fix NULL pointer dereference in team_xmit during mode change",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99041",
                            "    - ip6_gre: remove obsolete ERSPAN PMTU update",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-97935",
                            "    - tracing: Set the trace clock before registering the histogram trigger",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98944",
                            "    - HID: steam: Refactor registration",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98945",
                            "    - HID: steam: Rearrange teardown sequence",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2025-40135",
                            "    - ipv6: use RCU in ip6_xmit()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2025-38728",
                            "    - smb3: fix for slab out of bounds on mount to ksmbd",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-31678",
                            "    - openvswitch: defer tunnel netdev_put to RCU release",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99088",
                            "    - net: openvswitch: validate transport header presence in set_ipv6_addr",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98950",
                            "    - flow_dissector: avoid u16 truncation of hlen in bpf_flow_dissect()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98955",
                            "    - flow_dissector: avoid u16 truncation of skb->len when computing thoff",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99089",
                            "    - ASoC: samsung: i2s: enable op_clk in probe to balance runtime PM",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98956",
                            "    - ASoC: adau1372: allow sleepy powerdown GPIOs",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98964",
                            "    - nvmet: use the local P2P device on metadata allocation failure",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98967",
                            "    - cxgb4/ch_ktls: disable softirqs around tid_list erases",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98969",
                            "    - net/sched: em_text: reject unterminated algo before autoload",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98970",
                            "    - drm/vc4: Free the BO cache size list on teardown",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98971",
                            "    - gpio: exar: initialize the ID before registering its cleanup",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98979",
                            "    - namespace: refuse an automount below a mount that is in no namespace",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98984",
                            "    - dcache: don't put a mountpoint on a dentry that's being removed",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98990",
                            "    - namespace: check a submount for references right before unmounting it",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99095",
                            "    - drm/vc4: drain the hangcheck timer and works on V3D unbind",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99006",
                            "    - drm/i915/gem: Prevent overstepping exec array boundary",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99008",
                            "    - Bluetooth: RFCOMM: Fix NULL tty_dev dereference in rfcomm_dev_shutdown",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99010",
                            "    - Bluetooth: RFCOMM: free the skb when the DLC has no owner",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99015",
                            "    - Bluetooth: hci_sock: Serialize dead-device detachment",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99022",
                            "    - regulator: ltc3676: don't read the write-only HRST and CLIRQ registers",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99025",
                            "    - openvswitch: fix soft lockup in the netlink flow dump",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99031",
                            "    - net: bridge: avoid recursive multicast port cleanup",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99032",
                            "    - net/smc: protect clcsock lifetime in smc_getname",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99033",
                            "    - net/packet: guard the ll header push in packet_rcv_spkt()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99034",
                            "    - mmc: sdhci-sprd: disable runtime PM on remove",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99035",
                            "    - mmc: mtk-sd: Cancel request timeout work on remove",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99037",
                            "    - dm-crypt: reject the lmk IV mode with AEAD ciphers",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99038",
                            "    - memstick: rtsx_usb_ms: complete requests after eject instead of dropping",
                            "      them",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99039",
                            "    - memstick: core: wait for request completion before freeing card",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99040",
                            "    - KEYS: Fix add_key() race with keyring restriction",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99045",
                            "    - ibmveth: h_free logical LAN on open-fail after register",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99049",
                            "    - gpio: xilinx: fix runtime PM leak on request error path",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99052",
                            "    - selinux: preserve NATIVE_LABELS on already-initialized sb in",
                            "      set_mnt_opts",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99053",
                            "    - tipc: hold a reference to nodes found by link name",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99054",
                            "    - tipc: destroy topsrv workqueues before closing connections",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99056",
                            "    - strparser: make sure __strp_recv isn't running before tearing down the",
                            "      parser",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99057",
                            "    - xen/netfront: don't leak the skb when xennet_fill_frags() fails",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99058",
                            "    - workqueue: Fix NULL current_pwq deref in chained work check",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99059",
                            "    - wireguard: noise: reject response consumption after intermediate",
                            "      initiation",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99061",
                            "    - wifi: brcmfmac: fix P2P device removal race in brcmf_detach()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99063",
                            "    - dm ioctl: don't let data_start run past the buffer",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99067",
                            "    - btrfs: scrub: fix local_root reference leak in",
                            "      scrub_print_warning_inode()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99070",
                            "    - ipv6: do not warn on route notification size race",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99071",
                            "    - ipv4: do not warn on route notification size race",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99072",
                            "    - ipv4: stop route notification sizing when nexthop group shrinks",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98686",
                            "    - smb: client: discard post-EOF pagecache when extending a file via zero",
                            "      range",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98700",
                            "    - wifi: mac80211: set info->band for 802.3 encap offload frames",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98716",
                            "    - KVM: SVM: Use the active VMCB's MSR bitmap when checking if MSR is",
                            "      intercepted",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99080",
                            "    - fs: Free any excess xarray nodes in clear_inode()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98709",
                            "    - wifi: mac80211: count only matching reservations in reserved switch",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98708",
                            "    - wifi: mac80211: keep paired old chanctx alive",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98752",
                            "    - tty: port: fix tty_port_tty_vhangup() race",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99081",
                            "    - bnxt_en: fix DMA mapping length for padded small packets",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98696",
                            "    - USB: serial: fix driver deregistration order",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98705",
                            "    - wifi: mac80211: account proxy paths against the mesh path limit",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98722",
                            "    - mtd: block2mtd: Fix divide error when erase_size is zero",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98695",
                            "    - USB: serial: fix ioctl hangup race",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98694",
                            "    - thunderbolt: Fix KASAN reported use-after-free when request is canceled",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98704",
                            "    - wifi: mac80211: keep fallback association elements alive",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98707",
                            "    - wifi: mac80211: shut down RX BA session timer on teardown",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98749",
                            "    - tty: serial: max3100: shut down timer before freeing port",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98751",
                            "    - tty: abort break signalling on hangup",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98753",
                            "    - tty: tty_port: restore TTY_IO_ERROR on activation failure",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98762",
                            "    - USB: dwc2: shut down wakeup timer before freeing HCD state",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98784",
                            "    - drm/amdgpu/gfx6: fix firmware leak on teardown",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98779",
                            "    - drm/amdgpu: fix ACP MFD device leak on init failure",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98742",
                            "    - ALSA: seq: Serialize compat port-info ioctls",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98655",
                            "    - perf: Require kernel access for text poke events",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98750",
                            "    - tty: fix saved termios reset race",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-89638",
                            "    - smb: client: clear setuid/setgid bit on write with",
                            "      cifsacl/modefromsid/posix extensions",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98375",
                            "    - xen/netfront: drop RX packets with a short Ethernet header",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-89738",
                            "    - usb: gadget: at91_udc: drain polled-VBUS timer/work before udc is freed",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-89740",
                            "    - serial: imx: serialize imx_uart_ports[] lifetime",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-74341",
                            "    - wifi: wcn36xx: fix heap overflow from oversized firmware HAL response",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-74406",
                            "    - vxlan: Fix potential null-ptr-deref in vxlan_gro_prepare_receive().",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-46265",
                            "    - RDMA/hns: Fix WQ_MEM_RECLAIM warning",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98681",
                            "    - smb: client: split cifsFileInfo bitfields to avoid shared-byte RMW races",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-89539",
                            "    - SUNRPC: reject duplicate CREDS_VALUE options",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-93179",
                            "    - drm/amd/powerplay: fix VoltageObjectInfo zero-stride loop and OOB read",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2023-52561",
                            "    - arm64: dts: qcom: sdm845-db845c: Mark cont splash memory region as",
                            "      reserved",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2023-53651",
                            "    - Input: exc3000 - properly stop timer on shutdown",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2023-53733",
                            "    - net: sched: cls_u32: Undo tcf_bind_filter if u32_replace_hw_knode",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98657",
                            "    - iio: proximity: pulsedlight: fix iio_device left registered on PM setup",
                            "      failure",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98662",
                            "    - iio: light: gp2ap020a00f: drain irq_work after free_irq",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98663",
                            "    - iio: imu: adis16480: fix unprotected debugfs reads",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98664",
                            "    - iio: imu: adis16400: fix unprotected debugfs reads",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98666",
                            "    - iio: gyro: adis16136: fix unprotected debugfs reads",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98671",
                            "    - iio: adc: sun4i-gpadc-iio: clean up on thermal zone registration failure",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98679",
                            "    - iio: accel: kxcjk-1013: reject duplicate event disable",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98687",
                            "    - thunderbolt: Reject oversized XDomain properties responses",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98697",
                            "    - USB: serial: fix dynamic id driver deregistration race",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98698",
                            "    - wifi: mac80211: handle empty FILS association request payload",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98701",
                            "    - wifi: mac80211: release mesh path quota on failed additions",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98703",
                            "    - wifi: mac80211: minstrel_ht: validate fixed rate index",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98706",
                            "    - wifi: mac80211: drain PS delivery work during station teardown",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98710",
                            "    - wifi: iwlegacy: 3945: free EEPROM data on remove",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98711",
                            "    - wifi: cw1200: fix TX padding OOB read leaking heap data to device",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98721",
                            "    - mtd: rawnand: cadence: Initialize IRQ state before requesting IRQ",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98726",
                            "    - nvme-multipath: fix underflow in ANA log bounds checks",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98856",
                            "    - kprobes: Skip disarmed probes when checking optkprobe overlap",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98857",
                            "    - ipvs: bound LBLCR and LBLC cache growth",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98732",
                            "    - Bluetooth: btintel: fix buffer over-read in btintel_hw_error()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98735",
                            "    - Bluetooth: hci_core: Serialize ACL scheduling with channel deletion",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98739",
                            "    - Bluetooth: RFCOMM: Fix initial port reference race",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98741",
                            "    - ALSA: ua101: reject mismatched capture/playback packet sizes",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98940",
                            "    - ASoC: qcom: lpass-cpu: use DAI table index for playback constraints",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98748",
                            "    - serial: 8250_bcm7271: fix use-after-free in brcmuart_remove()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98754",
                            "    - tty: vcc: hold port lock when clearing tty pointer in vcc_cleanup",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98755",
                            "    - tty: vcc: zero-initialize control packet in vcc_send_ctl()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98756",
                            "    - usb: cdns3: Fix NULL pointer dereference in cdns3_pci_probe",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98757",
                            "    - usb: cdns3: fix use-after-free in cdns3_gadget_exit()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98760",
                            "    - usb: typec: tipd: fix uninitialized typec_partner_desc in",
                            "      tps6598x_connect()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98761",
                            "    - usb: typec: tcpm: recover after failure to start the frs ams",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98763",
                            "    - usb: core: clear both ep_in and ep_out for non-ep0 control endpoints",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98764",
                            "    - usb: gadget: f_fs: Fix NULL pointer dereference in",
                            "      FUNCTIONFS_ENDPOINT_DESC",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98765",
                            "    - USB: gadget: dummy-hcd: Fix wait for outstanding request completions",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98766",
                            "    - usb: gadget: aspeed-vhub: cancel wake work on device removal",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98769",
                            "    - usb: gadget: f_uac1_legacy: validate bRequest index in",
                            "      generic_{set,get}_cmd",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98771",
                            "    - usb: storage: sierra_ms: reject short SWoC info transfers",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98772",
                            "    - USB: serial: fix port tear down use-after-free",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98775",
                            "    - nitro_enclaves: fix use-after-free on SLOT_ALLOC failure",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98790",
                            "    - perf: Fix race between perf_event_exit_task() and perf_pending_task()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98934",
                            "    - ipv6: sr: use skb_get_hash_net() in seg6_make_flowlabel()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2022-49622",
                            "    - netfilter: nf_tables: avoid skb access on nf_stolen",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98794",
                            "    - ipvs: filter some flags received in the backup server",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98805",
                            "    - tipc: prevent GCM nonce reuse on peer key changes",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98811",
                            "    - net/sched: cls_api: reclaim an empty proto on the error path",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98812",
                            "    - net/mctp: publish the mctp_dev only after it is initialised",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98819",
                            "    - Bluetooth: btintel: validate DDC record lengths",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98823",
                            "    - wifi: cfg80211: preserve hidden-group beacon IE ownership",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98936",
                            "    - wifi: ath11k: reset ar->num_stations on hardware start",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98831",
                            "    - of/overlay: don't leak fragment references when changeset init fails",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98833",
                            "    - mtd: core: call _get_device() with the master MTD",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-89860",
                            "    - scsi: qla2xxx: Initialize NVMe abort_work once at submission",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-53353",
                            "    - hsr: Remove WARN_ONCE() in hsr_addr_is_self().",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98836",
                            "    - ALSA: line6: reject oversized playback packets",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98838",
                            "    - vt: skip screen update for DEC alignment test on backgroup consoles",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98568",
                            "    - vxlan: use one headroom snapshot for neighbour replies",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2024-49901",
                            "    - drm/msm/adreno: Assign msm_gpu->pdev earlier to avoid nullptrs",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98846",
                            "    - sctp: check RCV_SHUTDOWN after the sendmsg connect wait",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98847",
                            "    - rtc: spear: initialize IRQ state before requesting alarm IRQ",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98850",
                            "    - net/packet: prevent TX_RING byte count overflow",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98851",
                            "    - netfilter: nft_flow_offload: drop flowtable reference on init error path",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98854",
                            "    - of/overlay: only treat a positive changeset id as registered",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98855",
                            "    - of/overlay: put property on deadprops only after changeset add succeeds",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98862",
                            "    - audit: fix exe mark UAF in kill_rules()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98450",
                            "    - smb: client: close completed creates on compound wait errors",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98502",
                            "    - HID: alps: unregister DualPoint Stick input device on remove",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98456",
                            "    - Bluetooth: mgmt: fix race in read_unconf_index_list()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98451",
                            "    - smb: client: use finish_no_open() for non-regular inodes",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98484",
                            "    - netfilter: nf_tables: skip expired catchall elements on insert and",
                            "      delete",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98486",
                            "    - net: ena: fix MMIO read buffer leak on probe failure",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98493",
                            "    - net: ipconfig: bound DHCP option construction",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98454",
                            "    - smb: client: fix create context out-of-bounds reads",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98490",
                            "    - net: openvswitch: conntrack: fix helper UAF due to extensions realloc",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98507",
                            "    - mm/rmap: fix missing barrier between anon_vma init and vma->anon_vma",
                            "      publish",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98519",
                            "    - drm/amdgpu: Fix runtime PM leak in amdgpu_debugfs_test_ib_show()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98549",
                            "    - tcp: prevent collapsing skbs across boundary in rtx queue",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98544",
                            "    - bna: prevent IOC timer rearm during teardown",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98172",
                            "    - smb: client: fix smbd_connection leak on cifs_get_tcp_session() error",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98192",
                            "    - wifi: wcn36xx: Fix potential use-after-free in TX ack timer teardown",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98198",
                            "    - hwmon: (pwm-fan) Stop RPM timer before freeing tach data",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98409",
                            "    - watchdog: rtd119x: Avoid division by zero",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98245",
                            "    - btrfs: take commit root semaphore when iterating in",
                            "      mark_block_group_to_copy()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98264",
                            "    - ALSA: virtio: reset device before deleting virtqueues",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-97558",
                            "    - smb: client: fix cifsFileInfo reference leak in deferred close",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-97616",
                            "    - net/sched: act_api: release all action references on NEWACTION failure",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-97939",
                            "    - ipmr: account multicast table and route memory",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-89837",
                            "    - f2fs: fix dentry folio leak in find_in_level",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-89838",
                            "    - f2fs: limit recovery filename logging to stored length",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-97530",
                            "    - scsi: qla2xxx: Fix soft lockup polling continuation IOCB signature",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98386",
                            "    - scsi: qla2xxx: Use memset_io() to clear QLAFX00 request ring slot",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-89848",
                            "    - scsi: qla2xxx: Quiesce response IRQ before freeing request queue",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-97532",
                            "    - scsi: qla2xxx: Null out freed pointers in qla2x00_mem_alloc() error path",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-89877",
                            "    - media: saa7164: fix cleanup on resource allocation failure",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-93239",
                            "    - arm64: mm: Fix the lockless page-table walk in show_pte()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-90023",
                            "    - usb: gadget: f_mass_storage: fix null pointer dereference in",
                            "      fsg_common_set_num_buffers()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-93200",
                            "    - i3c: master: Fix use-after-free of master->this",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-93199",
                            "    - i3c: master: Do not treat master device as a duplicate target",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-89441",
                            "    - mmc: via-sdmmc: cancel card-detect work on remove",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-89465",
                            "    - power: supply: rt9455: quiesce delayed work before teardown",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-93231",
                            "    - lockd: fix swapped arguments in nlmsvc_match_ip()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-89552",
                            "    - params: fix charp corruption on allocation failure",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-89640",
                            "    - cifs: fix loff_t underflow in cifs_remap_file_range() when len == 0",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-89672",
                            "    - nfsd: gate nfs2 setacl by argp->mask",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-89685",
                            "    - nfsd: fix clock domain mismatch in clients_still_reclaiming()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-89707",
                            "    - nfsd: release path refs on follow_down() error",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-89719",
                            "    - zram: fix out-of-bounds access in read_block_state()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-89763",
                            "    - KEYS: trusted: Fix TPM teardown ordering",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-80851",
                            "    - gtp: serialize PDP context updates",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-80861",
                            "    - usb: xhci: bail out of setup if the controller is inaccessible",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98377",
                            "    - vlan: require the MAC header to be present in __vlan_insert_inner_tag()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98170",
                            "    - smb: client: fix OOB struct field reads in move_smb2_ea_to_cifs()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98171",
                            "    - smb: client: fix next_buffer UAF and NextCommand bounds in compound PDUs",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98169",
                            "    - smb: client: fix potential OOB read in smb3_enum_snapshots()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98193",
                            "    - wifi: libipw: reject TKIP frames without a full MIC",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-97555",
                            "    - smb: client: fix heap overflow in DACL owner/group rewrite",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-97557",
                            "    - smb: client: avoid leaking refcount in cifs_queue_oplock_break()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-97564",
                            "    - smb: client: reject userspace cifs.idmap descriptions",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-97615",
                            "    - net: bridge: use option bits for CFM/MRP frame handlers",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-97901",
                            "    - genetlink: pin family module during policy dump",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-97908",
                            "    - Bluetooth: btqcomsmd: destroy RPMsg endpoints before freeing hci_dev",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-97925",
                            "    - tick/broadcast: Plug clockevents replacement race",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-93285",
                            "    - f2fs: embed f2fs_gc_kthread in f2fs_sb_info",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-97529",
                            "    - scsi: qla2xxx: Validate BSG request_len before reading vendor_cmd[]",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-97536",
                            "    - scsi: qla2xxx: Fix use-after-free of qpair work on queue teardown",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-97537",
                            "    - scsi: qla2xxx: Fix queue teardown NULL dma_free and bitmap locking",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-89859",
                            "    - scsi: qla2xxx: Zero dport diagnostics buffer to avoid info leak",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-89921",
                            "    - KVM: s390: Zero initialize data structures for inject_pfault_token",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-89972",
                            "    - nvme: add missing SRCU grace period in error path",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-89988",
                            "    - kprobes: Protect kprobe_blacklist with RCU",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-90002",
                            "    - ftrace: Take trace_array reference before accessing its ftrace_ops",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-90016",
                            "    - staging: rtl8723bs: fix OOB read in rtw_restruct_wmm_ie()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-90029",
                            "    - usb: storage: realtek_cr: fix use-after-free on disconnect",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-80947",
                            "    - wifi: rtl8xxxu: fix use-after-free from rx_urb_wq on stop",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-89481",
                            "    - nvme-tcp: fix host memory disclosure on R2T for a read command",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-89492",
                            "    - ocfs2: validate directory-index entry counts when reading metadata",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-89553",
                            "    - nouveau/gem: reserve the bo in the info ioctl around the vma lookup",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-89625",
                            "    - HID: sony: fix UAF of ghl_poke_timer / ghl_urb at driver unbind",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-89633",
                            "    - smb: client: fix OOB read/write from unvalidated DataOffset in",
                            "      coalesce_t2()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-89652",
                            "    - ceph: bound copied dentry name length in NFS export get_name",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-89680",
                            "    - nfsd: fix nfsd_file leak on inter-server COPY setup failure",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-89761",
                            "    - apparmor: fix out-of-bounds write when null terminating a label vec",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-80852",
                            "    - tls: device: fix out-of-bounds write in tls_append_frag()",
                            ""
                        ],
                        "package": "linux-kvm",
                        "version": "5.15.0-1113.118",
                        "urgency": "medium",
                        "distributions": "jammy",
                        "launchpad_bugs_fixed": [
                            2173211,
                            2173225,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857
                        ],
                        "author": "Ubuntu Kernel Preparation Bot <ubuntu-kernel-bot@canonical.com>",
                        "date": "Mon, 09 Nov 2026 16:21:29 +0000"
                    }
                ],
                "notes": "linux-kvm-headers-5.15.0-1113 version '5.15.0-1113.118' (source package linux-kvm version '5.15.0-1113.118') was added. linux-kvm-headers-5.15.0-1113 version '5.15.0-1113.118' has the same source package name, linux-kvm, as removed package linux-headers-5.15.0-1112-kvm. As such we can use the source package version of the removed package, '5.15.0-1112.117', as the starting point in our changelog diff. Kernel packages are an example of where the binary package name changes for the same source package. Using the removed package source package version as our starting point means we can still get meaningful changelog diffs even for what appears to be a new package.",
                "is_version_downgrade": false
            },
            {
                "name": "linux-modules-5.15.0-1113-kvm",
                "from_version": {
                    "source_package_name": "linux-kvm",
                    "source_package_version": "5.15.0-1112.117",
                    "version": null
                },
                "to_version": {
                    "source_package_name": "linux-kvm",
                    "source_package_version": "5.15.0-1113.118",
                    "version": "5.15.0-1113.118"
                },
                "cves": [
                    {
                        "cve": "CVE-2026-99115",
                        "url": "https://ubuntu.com/security/CVE-2026-99115",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ksmbd: fill in FileSysIdentifier in FS_POSIX_INFORMATION  smb2_get_info_filesystem() reports 56 bytes for FS_POSIX_INFORMATION, that is the whole of FILE_SYSTEM_POSIX_INFO, but never assigns FileSysIdentifier.  Those eight bytes go to the client as they are found in the response buffer.  The buffer is zeroed on allocation, so a standalone request leaks nothing.  A compound request can leak: the offset of the next response is advanced by the length pinned for the previous one, so a reply that was written into the buffer and then dropped in favour of the short error response of smb2_set_err_rsp() stays there, and the next reply is laid over it with only the header cleared.  Report the file system id statfs() returned, which is what the field is for.  FileSysIdentifier is __le64 and f_fsid is a pair of ints, so assemble the value first, val[0] as the low half, and convert it on the way out.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99113",
                        "url": "https://ubuntu.com/security/CVE-2026-99113",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ksmbd: zero the FS_OBJECT_ID_INFORMATION buffer before filling it in  smb2_get_info_filesystem() reports 64 bytes for FS_OBJECT_ID_INFORMATION, that is the whole of struct object_id_info, but writes only 46 of them:   - objid[] is 16 bytes, and when the volume UUID is not available only    sizeof(stfs.f_fsid) (8) bytes are copied into it;  - extended_info.version_string[] is STRING_LENGTH (28) bytes, and only    strlen(\"1.1.0\") (5) bytes are copied into it.  The response buffer is zeroed on allocation (kvzalloc() in smb2_allocate_rsp_buf()), so for a standalone request the remaining 31 bytes are zero.  In a compound request they need not be.  The offset of the next response is advanced by the length pinned for the previous one, so if a preceding command wrote its reply into the buffer and then failed, smb2_set_err_rsp() pins only the short error response and the next reply lands inside the area that has already been written.  Only the header is cleared there:  \tmemset((char *)rsp_hdr, 0, sizeof(struct smb2_hdr) + 2);  The client then receives up to 31 bytes of a response it was not meant to see, including one that failed with an access denied error.  Clear the structure before filling it in.  As a side effect version_string is now NUL terminated.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99114",
                        "url": "https://ubuntu.com/security/CVE-2026-99114",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ksmbd: initialize FileSystemControlFlags in FS_CONTROL_INFORMATION  smb2_get_info_filesystem() reports 48 bytes for FS_CONTROL_INFORMATION, that is the whole of struct smb2_fs_control_info, but never assigns FileSystemControlFlags.  Those four bytes go to the client as they are found in the response buffer.  The buffer is zeroed on allocation, so a standalone request leaks nothing.  A compound request can leak: the offset of the next response is advanced by the length pinned for the previous one, so a reply that was written into the buffer and then dropped in favour of the short error response of smb2_set_err_rsp() stays there, and the next reply is laid over it with only the header cleared.  ksmbd does not implement quota tracking, so report no control flags.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99132",
                        "url": "https://ubuntu.com/security/CVE-2026-99132",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  xfs: don't hold buffer locks across sync transaction commit in xfs_sync_sb_buf  xfs_sync_sb_buf() holds sb/rtsb buffer locks across a synchronous xfs_trans_commit(), which flushes the CIL push workqueue internally. If shutdown occurs during the CIL push, xfs_buf_item_unpin() needs to lock these buffers to fail them, causing a deadlock:    setlabel:          holds buf lock -> flush_workqueue(xfs-cil)   CIL push worker:   xfs_buf_item_unpin -> xfs_buf_lock(same buf)  Remove the xfs_trans_bhold() calls so that commit releases the buffer locks normally.  After the sync commit, re-acquire the buffers via mp->m_sb_bp / mp->m_rtsb_bp for the on-disk writeback.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99135",
                        "url": "https://ubuntu.com/security/CVE-2026-99135",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  dm-integrity: fix infinite loop on discard with large tag size  When integrity_metadata handles a discard, it fills a buffer with DISCARD_FILLER and writes it over the tags, max_blocks blocks at a time. If the kmalloc fails, the buffer is the on-stack array checksums_onstack and max_size is set to HASH_MAX_DIGESTSIZE. So if the tag size is larger than HASH_MAX_DIGESTSIZE, max_blocks is zero, bi_size is never decremented and the loop never terminates.  Fix this by using sizeof(checksums_onstack) as max_size. The array has MAX_TAG_SIZE bytes since commit b93b6643e9b5 (\"dm integrity: fix a crash with unusually large tag size\"), so max_blocks is at least 1.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99118",
                        "url": "https://ubuntu.com/security/CVE-2026-99118",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  drm/i915/dmc: Harden DMC firmware payload parsing  Validate the conversion of the DMC firmware size from dwords to bytes using check_mul_overflow() before calculating the firmware payload size.  Reject zero-length payloads and zero MMIO counts in the DMC firmware header so malformed firmware is caught early. Also set dmc_fw_size only after the payload allocation succeeds.  (cherry picked from commit efde6601a1f1daedfe3dcc2816c934ddb44e3eef)",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99169",
                        "url": "https://ubuntu.com/security/CVE-2026-99169",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  futex: Fix mm reuse handling for FUT_OFF_MMSHARED  A FUT_OFF_MMSHARED futex is a shared futex that refers to an MM. It is possible for a process to wait on a shared futex with a different MM because a FUT_OFF_INODE waiter can be requeued onto a FUT_OFF_MMSHARED futex by another process. This can cause FUT_OFF_MMSHARED waiters on a freed MM to consume wakeups intended for a newly allocated MM at the same address.  Fix it by keying FUT_OFF_MMSHARED using a unique 64-bit per-MM ID. Leave private futexes as before to avoid influencing the performance of the hotpath.  (Multi-threaded processes typically implicitly use FUT_OFF_MMSHARED by setting clear_child_tid such that it points into anonymous memory, which causes mm_release() in a multi-threaded mm to perform FUTEX_WAKE.)",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99161",
                        "url": "https://ubuntu.com/security/CVE-2026-99161",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  i2c: viai2c-wmt: Fix clock leak in wmt_i2c_probe()  In wmt_i2c_probe(), i2c->clk is acquired using of_clk_get(). If any subsequent operation fails or when the module is unloaded, the clock reference count is never decremented via clk_put(), leading to a resource leak.  Switch to devm_clk_get() so that the clock is automatically managed and released.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99077",
                        "url": "https://ubuntu.com/security/CVE-2026-99077",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ipv4: udp: Create exceptions before socket matching  Currently, when ICMP Fragmentation Needed and Redirect Message packets are locally delivered and quote a UDP packet, a FIB nexthop exception (FNHE) is only created if the kernel can match the UDP packet to an existing socket.  This behavior allows off-path attackers to conduct a side-channel attack on the FNHE cache in order to discover the ephemeral port used by a connected UDP socket.  Commit 6457378fe796 (\"ipv4: use siphash instead of Jenkins in fnhe_hashfun()\") and commit 67d6d681e15b (\"ipv4: make exception cache less predictible\") tried to mitigate such attacks by making it harder for attackers to discover hash collisions in the FNHE cache and by randomizing the number of exceptions a hash bucket can hold, respectively. Unfortunately, both of the mitigations can be bypassed.  Instead, mitigate such attacks by always creating a FNHE, even before trying to find a matching socket. Do that by calling ipv4_update_pmtu() and ipv4_redirect(), the helpers used when the quoted packet did not originate from a socket.  This means that guesses (right or wrong) from an off-path attacker will always result in a FNHE being created or updated in the cache that the attacker can observe.  Pass an oif of 0, in a similar fashion to icmp_err(). This is also the oif used by the socket path for sockets that are not bound to a device.  Note that this does not allow attackers to create FNHEs that they could not create before, as both helpers can already be reached with little to no validation. For example, by sending an ICMP error that quotes an ICMP Echo Reply or one that quotes a UDP source port that matches a wildcard socket.  Also note that in the good case (matched socket) the above scheme comes at the cost of an extra route lookup, as the no socket helpers perform their own lookup before the one performed by ipv4_sk_update_pmtu() / ipv4_sk_redirect(). When the two resolve to different nexthops, it also results in two exceptions being created for the same destination IP. One in the FNHE cache of the nexthop resolved by the no socket helpers and another in the FNHE cache of the nexthop used by the socket.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99123",
                        "url": "https://ubuntu.com/security/CVE-2026-99123",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  vsock/virtio: validate packet source for connected sockets  virtio_transport_recv_pkt() looks up sockets first by the full source and destination tuple, then by destination only in the bound table. The fallback is needed for listening and connecting sockets, but sockets remain in the bound table after connect(), so it can also return a non-listening socket.  The fallback does not validate the source address. In TCP_SYN_SENT, a RESPONSE from an unrelated source can transition the victim socket to TCP_ESTABLISHED while its stored remote address remains unchanged. Subsequent RW packets from that source are delivered through the same destination-only fallback.  This was reproduced with capability-empty processes under different UIDs. The attacker discovered the target tuple through unprivileged AF_VSOCK sock_diag and caused the victim socket to read 16 attacker-chosen bytes; the intended peer-side socket read 0 of those 16 bytes.  Add vsock_check_source() to validate the transport, source port and source CID against the peer stored in a non-listening socket. The local transport is the CID exception because its packets are generated internally with VMADDR_CID_LOCAL as their source, including connections using CID aliases.  Use the helper after lock_sock() in the virtio receive path.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-89987",
                        "url": "https://ubuntu.com/security/CVE-2026-89987",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  mm/huge_memory: transfer the pmd dirty bit to the folio on zap  zap_huge_pmd_folio() propagates the pmd young bit to the folio for the file case, but not the dirty bit.  The pte path does propagate it, in zap_present_folio_ptes() and so does the pmd split path, in __split_huge_pmd_locked().  For most file mappings the omission is harmless, because writing to a shared file mapping goes through page_mkwrite(), which dirties the folio. tmpfs is different: it has no page_mkwrite(), and vma_wants_writenotify() is false for it, so a *read* fault on a MAP_SHARED tmpfs mapping installs a writable pmd via do_read_fault().  do_read_fault() does not call fault_dirty_shared_page(), so subsequent stores through that mapping set only the hardware dirty bit in the pmd and never call folio_mark_dirty(). A shmem folio allocated by a fault is marked uptodate but not dirty (see the clear: block in shmem_get_folio_gfp()), so PG_dirty is never set at all.  Unmapping such a folio - munmap(), or exit_mmap() when the process dies - then loses the only record that it was written, because zap_huge_pmd() drops the pmd without transferring the dirty bit.  Reclaim afterwards sees a clean shmem folio: the whole swap-out block in shrink_folio_list() is inside \"if (folio_test_dirty(folio))\", so pageout() is skipped and the folio falls into __remove_mapping().  There, folio_is_file_lru() is false for a swapbacked folio, so no shadow entry is created and __filemap_remove_folio(folio, NULL) simply empties the i_pages slot.  The data is freed without ever being written to swap, and the next fault on that index returns a freshly zeroed folio.  This is silent data loss for any process that keeps state in a MAP_SHARED tmpfs segment across an unmap - for example a cache handed from one process generation to the next through /dev/shm.  It requires the folio to be PMD-mapped, so it only shows up once shmem THP is enabled (which is what we did in Meta fleet and started noticing crashes); with THP off the pte path transfers the dirty bit correctly.  It also only becomes visible when swap is enabled, because with no swap device shmem folios (which are on the anon LRU) are not scanned by reclaim at all, so the clean folio is never dropped.  Reproduced on x86_64 with a tmpfs mounted huge=within_size: read-fault a 2MB-backed region, write a known pattern through the resulting mapping, munmap, force reclaim of the cgroup, then re-map and read back.  Without this patch the region reads back as zeros and vmstat shows zswpout 0 - the data was discarded rather than swapped.  With this patch the region reads back correctly and the pages are swapped out as expected.  With huge=never, or when the first touch is a write, the test passes either way.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-09-16 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-80572",
                        "url": "https://ubuntu.com/security/CVE-2026-80572",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  Input: byd - synchronize timer deletion before freeing private data  byd_disconnect() uses timer_delete() before freeing the driver's private data.  This does not wait for a running byd_clear_touch() callback, which dereferences the private data and its psmouse pointer.  A callback racing with disconnect can therefore access the private data after it has been freed.  The timer can also still be re-armed by byd_process_byte() while the disconnect is in progress.  Use timer_shutdown_sync() before freeing the private data: it waits for a running callback and turns any later re-arm attempt into a no-op.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-08-26 15:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99180",
                        "url": "https://ubuntu.com/security/CVE-2026-99180",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  unicode: free the map after a grace period  generic_ci_d_hash() and generic_ci_d_compare() read sb->s_encoding and dereference the unicode map while a pathwalk in rcu mode holds nothing but rcu_read_lock(). The filesystems that use them, ext4, f2fs and tmpfs, drop the map with utf8_unload() from ->put_super(), which runs when the last reference to the mount goes away. A lookup that is still inside such a filesystem at that point reads a freed map.  With a pathwalk held up in utf8_casefold_hash() while the last reference to a casefolded tmpfs goes away:    BUG: KASAN: slab-use-after-free in utf8nlookup+0x74c/0x950   Read of size 8 at addr ff110001030fe658 by task walker/98   Call Trace:    <TASK>    utf8nlookup+0x74c/0x950    utf8byte+0x160/0x1560    utf8_casefold_hash+0x167/0x230    generic_ci_d_hash+0xdd/0x1c0    link_path_walk+0x11ad/0x1d30    path_lookupat+0x63/0xb00    filename_lookup+0x1f1/0x5b0    vfs_statx+0xd7/0x3b0   [...]   Allocated by task 94:    __kmalloc_cache_noprof+0x249/0x560    utf8_load+0x4e/0x570    shmem_parse_opt_casefold.isra.0+0x92/0x270   [...]   Freed by task 97:    kfree+0x1db/0x5b0    shmem_put_super+0x72/0x170    generic_shutdown_super+0x14c/0x530    kill_anon_super+0x3a/0x60    deactivate_locked_super+0x9c/0xf0    cleanup_mnt+0x9f/0x130  So far that has been hard to hit. umount(2) waits for a grace period in namespace_unlock() before it drops the mount, so only a mount whose last reference goes away elsewhere, like the close of a file or a chdir out of a lazily unmounted directory, can race a walker. So it is reachable.  Delay the free until a grace period has passed. The map and the data table it holds a reference to then outlive any pathwalk that found the superblock before the mount went away. The reference on the data table module is dropped from the rcu callback as well. utf8-core is built in whenever CONFIG_UNICODE is set, so there is no module exit that would have to wait for the callbacks.  Overlayfs points the s_encoding of an overlay at the map of its first layer without taking a reference of its own. That stays correct. The layer is held by the overlay, so its map is dropped only after the overlay is gone.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99179",
                        "url": "https://ubuntu.com/security/CVE-2026-99179",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  watch_queue: Fix note pool publication race in watch_queue_set_size()  There is a race between watch_queue_set_size() and post_one_notification(). watch_queue_set_size() publishes wqueue->notes, notes_bitmap, nr_pages and nr_notes with plain stores, and post_one_notification() reads them with plain loads under a different lock, so nothing orders the four stores against the poster's loads: depending on the build, notes can be stored last (gcc 14 on x86-64 does this).  Since keyctl_watch_key() lets a watch attach to a queue before it is sized, post_one_notification() can already be running on another CPU at that moment: it reads nr_notes > 0, passes its bounds check, and then reads notes while it is still NULL, dereferencing notes[0].  An unprivileged user triggers this reliably by watching one of its own keys through a notification pipe and racing ioctl(IOC_WATCH_QUEUE_SET_SIZE) on that pipe against keyctl(KEYCTL_SETPERM) on the key from another CPU, triggering:    BUG: kernel NULL pointer dereference, address: 0000000000000000   RIP: 0010:post_one_notification.isra.0+0xa2/0x1e0   Call Trace:    __post_watch_notification+0x148/0x180    keyctl_setperm_key+0x119/0x130    do_syscall_64+0x108/0x4c0    entry_SYSCALL_64_after_hwframe+0x77/0x7f   Kernel panic - not syncing: Fatal exception in interrupt  Fix this by publishing nr_notes last with smp_store_release(), and by reading it once with smp_load_acquire() in post_one_notification() before the bitmap and the page array are touched.  A poster that observes a non-zero nr_notes then also observes the pool behind it; one that observes zero drops the notification as before.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-89912",
                        "url": "https://ubuntu.com/security/CVE-2026-89912",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  KVM: arm64: vgic-its: Don't dereference a NULL collection on ITT save  MAPC with V=0 drops ite->collection but leaves the ITE on the device's ITT list, and vgic_its_save_ite() dereferences it unconditionally. A guest that issues MAPD, MAPTI and then MAPC(V=0) therefore oopses the host when the VMM issues KVM_DEV_ARM_ITS_SAVE_TABLES to migrate it. That sequence is UNPREDICTABLE per the architecture, but KVM already handles the resulting state in the translate, MOVI and DISCARD paths.  Save a zeroed entry, which vgic_its_restore_ite() reads back as invalid. Skipping the ITE instead would leave the ITT slot holding whatever is in guest memory, and restore rejects an entry naming a collection the restored collection table does not have.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-09-16 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99156",
                        "url": "https://ubuntu.com/security/CVE-2026-99156",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  scsi: st: Fix use-after-free race between st_remove() and st_open()  st_remove() drops the probe reference on the scsi_tape with kref_put() and only afterwards removes its index from st_index_idr. If that was the last reference, scsi_tape_release() frees the structure while it is still published in the idr.  scsi_tape_get(), called from st_open(), looks up the tape in st_index_idr and takes a reference under st_ref_mutex and st_index_lock. remove_cdevs() does not wait for opens that are already past chrdev_open(), so an open that is blocked on st_ref_mutex while st_remove() holds it can take the mutex as soon as st_remove() drops it, find the freed tpnt in the idr and call kref_get() on it:    BUG: KASAN: slab-use-after-free in st_open   Write of size 4 ...    st_open (drivers/scsi/st.c:254 drivers/scsi/st.c:1291)    chrdev_open   ...   Freed by task ...:    kfree    st_remove (drivers/scsi/st.c:4512)  Remove the index from the idr before dropping the reference, all under st_ref_mutex. A concurrent scsi_tape_get() now either runs first and holds a valid reference that keeps the tape alive, or runs afterwards and finds nothing, so st_open() fails with -ENXIO.  This restores the ordering st_remove() had before the conversion to st_index_idr, where the tape was unpublished from scsi_tapes[] before the final kref_put().",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99112",
                        "url": "https://ubuntu.com/security/CVE-2026-99112",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net/sched: cls_flower: validate mask pointer after nla_next()  fl_set_enc_opt() iterates the key's nested tunnel-option attributes with nla_for_each_attr() while advancing a single mask pointer via nla_next() at the bottom of each loop, so the mask cursor is driven by the number of key attributes rather than by the mask's own attributes.  The nla_ok() added by commit c96adff956191 (\"cls_flower: call nla_ok() before nla_next()\") only validates the mask pointer that was just consumed; the pointer produced by nla_next() is used by the next iteration (fl_set_geneve_opt() and siblings) without any validation.  The mask's nested attributes are validated with NL_VALIDATE_LIBERAL, which merely warns on trailing bytes that do not form a complete attribute.  A mask carrying one valid attribute plus 1-3 residue bytes (or a non-aligned attribute length making msk_depth negative) therefore reaches the next iteration with msk_depth != 0, so neither the !msk_depth check in fl_set_enc_opt() nor the !depth check in the per-type helpers fires.  nla_type() then reads past the mask payload and nla_parse_nested_deprecated() iterates with an nla_len taken from those bytes, reading well beyond the mask attribute (KASAN: slab-out-of-bounds read in __nla_validate_parse from fl_change()).  Validate the advanced mask pointer as well: when the mask is not legitimately exhausted (msk_depth != 0) and the new pointer fails nla_ok(), reject the filter with -EINVAL.  An exactly exhausted mask still skips the check, preserving exact-match behaviour for the remaining key attributes.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99117",
                        "url": "https://ubuntu.com/security/CVE-2026-99117",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net: bridge: mcast: don't truncate the port group walk on teardown  __br_multicast_disable_port_ctx() and br_multicast_del_port() walk port->mglist with hlist_for_each_entry_safe(). However, br_multicast_find_del_pg() can also delete other entries from the same list through br_multicast_fwd_src_remove() or __fwd_del_star_excl().  If such an entry is the iterator's saved next node, hlist_del_init() clears its ->next and terminates the walk early. The reproducer triggers this in both teardown walks, leaving port groups in the bridge mdb with a dangling ->key.port after del_nbp() frees the port:    BUG: KASAN: slab-use-after-free in __mdb_fill_info+0x1191/0x1320    __mdb_fill_info+0x1191/0x1320    br_mdb_dump+0x594/0xe40    rtnl_mdb_dump+0x1cf/0x5d0  Use hlist_del_init_rcu() to unlink the group while preserving ->next. br_multicast_del_pg() and the teardown walks run under br->multicast_lock. The GC worker must acquire the same lock before detaching the group for destruction, so the node remains alive while the walk uses the preserved pointer.  Preserving ->next means a walk can now reach a group that an earlier iteration already deleted as a side effect. That group is off mp->ports, so br_multicast_find_del_pg() would fall through its port scan and hit the trailing WARN_ON(1). Skip such groups at the top of that helper: a port group is put on port->mglist when it is created and only unlinked when it is deleted, so hlist_unhashed() identifies exactly this case.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-74405",
                        "url": "https://ubuntu.com/security/CVE-2026-74405",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  OPP: Fix race between OPP addition and lookup  A race exists between dev_pm_opp_add_dynamic() and dev_pm_opp_find_freq_exact():    CPU0 (add)                          CPU1 (lookup)   -------------------------------     ------------------------------   _opp_add()     mutex_lock()     list_add(&new_opp->node, head)     mutex_unlock()                    _opp_table_find_key()                                         mutex_lock()                                         dev_pm_opp_get(opp)                                           kref_get()                                         mutex_unlock()     kref_init(&new_opp->kref)                                       dev_pm_opp_put()                                         kref_put_mutex()  The newly added OPP is inserted into the list before its kref is initialized. A concurrent lookup can find this OPP and increment its reference count while it is still uninitialized, leading to refcount corruption and a potential premature free.  Fix this by initializing ->kref and ->opp_table before making the OPP visible via list_add(). This ensures any concurrent lookup observes a fully initialized object.  [ Viresh: Updated commit log ]",
                        "cve_priority": "low",
                        "cve_public_date": "2026-08-15 06:22:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-74739",
                        "url": "https://ubuntu.com/security/CVE-2026-74739",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net/sched: cls_u32: skip hash tables in u32_bind_class()  u32_walk() enumerates both struct tc_u_hnode and struct tc_u_knode through the walker callback. u32_bind_class() unconditionally casts the passed fh to tc_u_knode and accesses &n->res, so when fh is actually a tc_u_hnode, which has no tcf_result member, this results in a slab-out-of-bounds read of res->classid in tc_cls_bind_class().  The issue can be reproduced with the following commands:      tc qdisc add dev lo root handle 1: hfsc     tc class add dev lo parent 1: classid 1:1 hfsc sc rate 1000kbit     tc filter add dev lo parent 1:1 protocol ip prio 1 u32 match u32 0 0 flowid 1:1     tc class add dev lo parent 1: classid 1:2 hfsc sc rate 2000kbit  Fix this by skipping hash tables via the TC_U32_KEY(handle) check.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-08-26 15:16:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-64015",
                        "url": "https://ubuntu.com/security/CVE-2026-64015",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  security/keys: fix missed RCU read section on lookup  Nicholas Carlini reports that the keyring code calls assoc_array_find() in find_key_to_update() without holding the RCU read lock, while the assoc_array_gc() code really is designed around removing the node from the tree and then freeing it after an RCU grace-period.  The regular key handling doesn't see this because holding the keyring semaphore hides any lifetime issues, but the persistent key handling uses a different model.  Instead of extending the keyring locking, just do the simple RCU locking that the assoc_array was designed for.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-07-19 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-74672",
                        "url": "https://ubuntu.com/security/CVE-2026-74672",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  mm/vmalloc: acquire init_mm lock on huge vmap to avoid ptdump UAF  Patch series \"mm: fix UAF caused by race between ptdump and vmap pgtable freeing\", v6.  Kernel page table walkers fall into two broad categories - those ranges where no exclusion is required via walk_kernel_page_table_range_lockless() and those where exclusion is required via walk_kernel_page_table_range() or walk_page_range_debug().  The former category is used only by arm64 arch code operating on ranges it both wholly owns and does not concurrently write.  The latter category consists of kernel page table walkers operating on ranges that are wholly owned (but which need exclusion against concurrent writers).  The lock used for exclusion is the mmap lock, and for kernel ranges this is the mmap lock on init_mm.  ptdump is a special case being both the only user of walk_page_range_debug(), and the only case in which it walks ranges it does not own.  This presents a problem, as page tables may be freed under ptdump.  And indeed there is a use-after-free bug in the kernel as a result, which this series addresses.  vmap promotes page tables to huge leaf entries where possible, freeing the lower page table when it does.  It does this with no meaningful locks held against concurrent ptdump walks.  As a result, use-after-free can currently occur.  This series addresses the issue by having the vmap huge promotion logic acquire the mmap read lock while both setting the huge page table entry and freeing the prior leaf page table.  The ptdump code already acquires the mmap write lock, so by doing so we ensure that the ptdump walker only ever observes either the huge page table entry or the existing page table entry, and nothing is freed underneath it.  A mitigation for this issue was already applied for arm64 in commit fa93b45fd397 (\"arm64: Enable vmalloc-huge with ptdump\"), which this series has to deal with carefully.  This mitigation resolves the issue by acquiring the mmap read lock on init_mm on vmap page table free if a ptdump is in progress.  However the fix in this series would cause a deadlock if we were to simply apply it for arm64 without also reverting the change.  This is because vmap may acquire the read lock before ptdump attempts to acquire the write lock, which then gets queued, and rwsem starvation rules mean that the (unacknowledged) nested mmap read lock in the arm64 code would also block, meaning the original read lock is never released and thus deadlock.  This series works around this by #ifndef CONFIG_ARM64'ing the mmap read lock in vmap logic, then partially reverting commit fa93b45fd397 (\"arm64: Enable vmalloc-huge with ptdump\"), keeping the enablement of huge vmap support, and removing the ifdeffery with the partial revert patch.  There are related issues that are also addressed in this series:  * x86 page attribute logic, specifically Change Page Attributes (CPA),   implements a feature whereby huge ranges can be collapsed into huge leaf   entries. This can similarly cause a UAF when done in parallel with a   ptdump walk, so similarly acquire the init_mm mmap lock to avoid this.  * The CPA logic allows concurrent page table manipulation and CPA   collapse, meaning the former risks accessing a page table the latter   frees. Fix this by acquiring mmap write lock on init_mm across the   whole CPA collapse operation and read lock on the page table   manipulation.  * x86 and arm64 permit walks of non-kernel mm's (both allowing efi mm   walks, and in x86's case arbitrary mm's), so we ensure kernel mappings   remain stable by locking the init_mm as well as the mm being walked.  The ordering of patches is established for both strict dependencies (the arm64 partial revert in particular has to be done after the vmap changes) and logical ones (the non-kernel mm fix only makes sense once the vmap/CPA fixes are in place).   This patch (of 3):  Currently there is a nasty ra ---truncated---",
                        "cve_priority": "low",
                        "cve_public_date": "2026-08-22 16:16:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99121",
                        "url": "https://ubuntu.com/security/CVE-2026-99121",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ipv4: avoid divide by zero in fib_rebalance  fib_rebalance() computes the total eligible nexthop weight in one pass and programs upper bounds in a second pass. A concurrent change to ignore_routes_with_linkdown can make the first pass return zero while the second pass sees an eligible nexthop, resulting in division by zero.  If the first pass reports a zero total, set each nexthop upper bound to -1 and skip the division. This matches the IPv6 fix in commit d2c26c2911dd (\"ipv6: avoid divide by zero in rt6_multipath_rebalance\") and preserves the lock-free rebalance path.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99124",
                        "url": "https://ubuntu.com/security/CVE-2026-99124",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  s390/pci: Fix leak of uninitialized kernel data in SCLP report  While report_error_write() checks that the provided buffer is at least as large as the header struct, but not that it is large enough to contain the report with the length claimed by report->length. If user-space provides a short buffer, meaning a larger report->length than the actually written payload, up to around 4K of kernel data from past the kmalloc(len + 1) sized buffer allocated in kernfs_fop_write_iter() will leak into the SCLP report.  However, as the entity processing the SCLP is privileged and able to access at least the page including the report, this does not leak data that entity could not access but it is still an out of bounds read and a malformed error report that should be rejected.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99126",
                        "url": "https://ubuntu.com/security/CVE-2026-99126",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  s390/ctcm: Prevent XID null dereference  The mpc_validate_xid() function sets grp->saved_xid2->xid2_flag2 to 0x40 to signal XID validation error. If peer XID is NULL or r/w channel pairing mismatch happens, grp->saved_xid2 is never initialized. An attempt to set the flag in such case leads to NULL dereference.  Fix this by using the always available priv->xid->xid2_flag2 instead of grp->saved_xid2->xid2_flag2 for validation errors.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99127",
                        "url": "https://ubuntu.com/security/CVE-2026-99127",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  page_pool: keep frag_offset aligned for odd-sized requests  page_pool_alloc_frag_netmem() rounds the requested fragment size with  \tsize = ALIGN(size, dma_get_cache_alignment());  dma_get_cache_alignment() returns 1 unless the architecture defines ARCH_DMA_MINALIGN, which DMA-coherent architectures such as x86 do not. There the ALIGN() is a no-op and pool->frag_offset advances by the raw, unrounded size.  A single caller asking for an odd size then leaves frag_offset misaligned for every fragment carved out of that page afterwards.  The pool is shared, so the damage is not confined to the caller that caused it.  The per-cpu system_page_pool used by generic XDP hits this. skb_pp_cow_data() allocates its fragments with the raw packet length:  \tsize = min_t(u32, len, PAGE_SIZE); \ttruesize = size; \tpage = page_pool_dev_alloc(pool, &page_off, &truesize);  leaving frag_offset odd for whatever is carved out of that page next.  Its own head allocation is already aligned -- SKB_HEAD_ALIGN(size) plus the XDP_PACKET_HEADROOM its callers pass -- so it is a later user of the shared pool that pays: page_pool_dev_alloc_va() returns a misaligned buffer, napi_build_skb() installs it as skb->head, and skb_shinfo(skb) == skb->head + skb->end is misaligned with it.  skb_shinfo()->dataref is a 4-byte atomic_t at offset 0x20, so the atomic_inc() in __skb_clone() straddles a cache line.  On x86 with split lock detection -- fatal for kernel split locks by default -- this panics the machine:    Oops: Split lock detected   RIP: 0010:skb_clone+0x154/0x1e0   Call Trace:    <IRQ>    raw_local_deliver+0x1ed/0x2c0    ip_protocol_deliver_rcu+0x54/0x1c0    ip_local_deliver_finish+0x85/0x100    ip_local_deliver+0x67/0x100    __netif_receive_skb_one_core+0x85/0xa0    process_backlog+0x87/0x130  Reproduced by attaching any generic-mode XDP program to loopback and opening a RAW IPPROTO_UDP socket, which makes raw_local_deliver() clone every locally delivered UDP packet; ordinary DNS traffic then triggers it, roughly once per 2500 clones.  Observed on 6.12.101 and 7.1.8.  Tracing page_pool_alloc_frag_netmem() over one such run shows the amplification -- two odd-sized requests, nine misaligned offsets:    requested size & 7:   0: 17035    5: 1    7: 1   frag_offset & 7:      0: 17028    3: 1    4: 1    5: 1    6: 1    7: 5  and skb_pp_cow_data() returning heads that were aligned on entry:    head 0xffff8f4c86aeac00 -> 0xffff8f4c53a9a9c4 (&7=4)   head 0xffff8f4d6a8a42c0 -> 0xffff8f4c4f7b7a45 (&7=5)  Round the fragment size up to at least the alignment struct skb_shared_info requires, so fragments are always suitably aligned for the objects callers build on them.  Architectures needing a larger DMA alignment keep it.  This also makes the remainder computed in page_pool_alloc_netmem(),  \t*size = max_size - *offset;  aligned, since max_size is a power of two -- which fixes the matching misalignment of skb->end.  Verified with a controlled A/B under QEMU/KVM: same tree, same config, same compiler, same rootfs and identical traffic, differing only by this patch.  A SEC(\"xdp.frags\") XDP_PASS program on lo plus UDP datagrams larger than max_head_size drives skb_pp_cow_data()'s fragment loop, which passes raw packet lengths to the pool.  Measured at the return of skb_pp_cow_data():                            unpatched   patched   skb_pp_cow_data calls       40800     40800   misaligned skb->head         1120         0   dataref at line offset >60     80         0  The last row counts the accesses that actually fault: skb_shinfo()->dataref sits at head+end+0x20 and is a 4-byte atomic, so `lock incl` splits a 64-byte cache line only when that address lands at offset 61..63.  All 80 occurrences were at offset 61; the panic reported above was at offset 62.  Eliminating the misalignment removes every one of them.  Same class of bug as commit 3bed3cc4156e (\"net: Do not allocate page fragments t ---truncated---",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99128",
                        "url": "https://ubuntu.com/security/CVE-2026-99128",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  sctp: validate chunk length in the inqueue parser  SCTP chunks always include a four-byte generic header, but sctp_inq_pop() currently accepts shorter declared lengths. A zero-length chunk leaves chunk_end at the current header.  When ASCONF is covered by the association's SCTP-AUTH policy, sctp_assoc_bh_rcv() can continue before the state machine performs its normal chunk-length check. sctp_inq_pop() then returns the same malformed chunk repeatedly and the receive softirq can lock up.  A remote SCTP peer can trigger this after establishing an association on a kernel built with CONFIG_IP_SCTP and configured with net.sctp.addip_enable=1 and net.sctp.auth_enable=1. The reproducer did not require application credentials, a shared SCTP AUTH key, or net.sctp.addip_noauth_enable=1.  On commit f967455fb2a5 (\"seg6: reset IP6CB after IPv6 decapsulation\"), one zero-length ASCONF caused repeated watchdog soft-lockup reports in a two-vCPU KVM guest. All 3 pre-trigger health probes succeeded, while 36 of 37 post-trigger probes failed. With this change, all 37 post-trigger probes succeeded and no equivalent soft-lockup signature appeared.  Reject chunks shorter than the generic SCTP header at the shared inqueue parser boundary. Mark the packet for discard before either caller can continue processing it, while preserving the four-byte generic minimum. Declared-length 1 through 4 controls and kernel-generated ASCONF traffic remained healthy. The patched sctp_hello selftest passed for IPv4 and IPv6.  The complete private reproducer and validation evidence are available directly to maintainers on request.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99133",
                        "url": "https://ubuntu.com/security/CVE-2026-99133",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net/iucv: fix the recvmsg window update  iucv_sock_recvmsg() sends the HiperSockets-only AF_IUCV_FLAG_WIN without testing the transport, so on a classic z/VM socket iucv_send_ctrl() sizes the skb through a NULL iucv->hs_dev. SO_MSGLIMIT accepts 1, so msglimit / 2 is zero and one recvmsg() on its own socket is enough for an unprivileged process to take a spurious disconnect.  It also calls iucv_send_ctrl() under spin_lock_bh(&message_q.lock), which allocates GFP_KERNEL inside a section the code treats as atomic. Sending outside that lock lets two recvmsg() reach afiucv_hs_send() at once, where msg_recv is sampled for the advertised window and subtracted after dev_queue_xmit() -- and sendmsg reaches that counter under lock_sock() while recvmsg holds no socket lock, so both can subtract the same value, the counter goes negative and the credit reaches the peer twice.  Test the transport, claim the credit with atomic_xchg() after the last error exit and hand it back if the transmit fails, and send once the lock is dropped.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99136",
                        "url": "https://ubuntu.com/security/CVE-2026-99136",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  dm-crypt: fix a tiny race condition in crypt_dec_pending  crypt_dec_pending reads io->error before calling atomic_dec_and_test. Another context, for example crypt_endio called from an interrupt, may set io->error and drop its reference between the read and the decrement. crypt_dec_pending then drops the last reference and completes the bio with the stale status - so a read that failed and was never decrypted, or a write that failed, is reported as successful.  The read was placed before the decrement by commit b35f8caa0890 (\"dm crypt: wait for endio to complete before destruction\"), because that commit freed dm_crypt_io before calling bio_endio. This is no longer the case, dm_crypt_io lives in the per-bio data now.  Read io->error after atomic_dec_and_test instead. atomic_dec_and_test is fully ordered, so no additional barrier is needed.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99138",
                        "url": "https://ubuntu.com/security/CVE-2026-99138",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  tcp: fix use-after-free in do_tcp_getsockopt(TCP_CC_INFO)  do_tcp_getsockopt() reads icsk->icsk_ca_ops and dereferences the get_info function pointer without rcu_read_lock(). With BPF struct_ops congestion control, ca_ops can point to dynamically allocated memory that is freed concurrently, resulting in a use-after-free when the kernel dereferences or calls through the stale pointer.    BUG: KASAN: slab-use-after-free in do_tcp_getsockopt+0x2037/0x23e0   Read of size 8 at addr ffff888013701258 by task exploit/149    do_tcp_getsockopt+0x2037/0x23e0 (net/ipv4/tcp.c:4564)    tcp_getsockopt+0x91/0xf0    __sys_getsockopt+0xf7/0x170  Fix this by wrapping the ca_ops load and get_info call within rcu_read_lock()/rcu_read_unlock(), and using READ_ONCE() to load the icsk_ca_ops pointer.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99100",
                        "url": "https://ubuntu.com/security/CVE-2026-99100",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: p54: validate firmware record lengths  The p54 firmware parser accesses component ID and component version records without checking that their lengths cover the fields being read. A malformed record can therefore make the parser read past the record.  Validate the component ID and component version record lengths before accessing their data. The descriptor record is also checked against the shortest descriptor length found in the supported firmware images.  Reject descriptor values that underflow the RX offset or produce an empty RX range before updating the driver state.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-28 04:18:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99140",
                        "url": "https://ubuntu.com/security/CVE-2026-99140",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  tracing: Fix hist trigger timestamps for buffered events  Syzkaller triggered a WARN_ON_ONCE(!nest) warning:    WARNING: kernel/trace/ring_buffer.c:821 at ring_buffer_event_time_stamp   Call trace:     ring_buffer_event_time_stamp     hist_field_timestamp     hist_fn_call     event_hist_trigger     event_triggers_call     __event_trigger_test_discard     trace_event_buffer_commit     do_trace_event_raw_event_sched_switch     trace_event_raw_event_sched_switch  The warning is probabilistically reproducible and is related to syzkaller executing the following commands:    echo 'prev_pid == 999999' > events/sched/sched_switch/filter   echo 'hist:keys=common_timestamp' > events/sched/sched_switch/trigger  The specific triggering process is as follows:  CPU 0                                           CPU 1 (context switching)                             (echo 'hist:keys=common_timestamp' > \\                                                        events/sched/sched_switch/trigger) do_trace_event_raw_event_##call   trace_event_buffer_lock_reserve     if (!tr->no_filter_buffering_ref &&         trace_file->flags & EVENT_FILE_FL_FILTERED)         return entry;  // return directly                                                 event_hist_trigger_parse                                                   hist_register_trigger                                                    tracing_set_filter_buffering(file->tr, true);                                                      tr->no_filter_buffering_ref++;     __trace_buffer_lock_reserve       rb_start_commit         local_inc(&cpu_buffer->committing);  // skipped and not executed   trace_event_buffer_commit     __event_trigger_test_discard       event_triggers_call         event_hist_trigger           hist_fn_call             hist_field_timestamp               ring_buffer_event_time_stamp                 nest = local_read(&cpu_buffer->committing);                 WARN_ON_ONCE(!nest)  // trigger warning  The root cause is that when an event file has a filter attached and the hist trigger has not yet been attached, trace_event_buffer_lock_reserve() writes the event into the per-CPU trace_buffered_event temp buffer instead of reserving it in the ring buffer, so cpu_buffer->committing is not incremented. When the event is later processed at commit time by a hist trigger, hist_field_timestamp() -> ring_buffer_event_time_stamp() sees a zero committing count, triggering WARN_ON_ONCE(!nest).  tracing_event_time_stamp() was added by commit d8279bfc5e959 (\"tracing: Add tracing_event_time_stamp() API\") for exactly this case: if the event is the per-CPU trace_buffered_event, it returns the current ring buffer timestamp. But it never gained a caller. Use it in hist_field_timestamp(), so that a hist trigger that races onto a buffered event records the current time, which is only marginally later than when the event was recorded, instead of warning and recording a bogus timestamp.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99150",
                        "url": "https://ubuntu.com/security/CVE-2026-99150",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  drm/amdgpu: don't drop the runtime PM reference twice in amdgpu_gpr  amdgpu_debugfs_gpr_read() drops its runtime PM reference right after reading the wave registers. When copying them to userspace fails, it jumps to the err label, which drops the reference a second time. A read into a bad buffer on Navi31 either steals a reference somebody else holds (power/runtime_usage goes from 1 to 0) or underflows the count:    amdgpu 0000:03:00.0: Runtime PM usage count underflow!  The registers are already in the kernel buffer at that point, so finish the hardware access first and copy the buffer with a single copy_to_user() instead of the put_user() loop with its own error path.  (cherry picked from commit 31035bbd74f7c3e10c163db875b8e67f8b50ee6a)",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99152",
                        "url": "https://ubuntu.com/security/CVE-2026-99152",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  scsi: libiscsi: Validate the task named by a management response  __iscsi_complete_pdu() fetches the task for five response types from one place and checks only that the index resolved:        case ISCSI_OP_LOGOUT_RSP:       case ISCSI_OP_LOGIN_RSP:       case ISCSI_OP_TEXT_RSP:       case ISCSI_OP_SCSI_TMFUNC_RSP:       case ISCSI_OP_NOOP_IN:               task = iscsi_itt_to_task(conn, hdr->itt);               if (!task)                       return ISCSI_ERR_BAD_ITT;  iscsi_itt_to_task() bounds the index against cmds_max and looks at nothing else, so a target can name any slot in the pool, including one that has never been used. task->conn is then NULL, and both iscsi_nop_out_rsp() and iscsi_complete_task() dereference it. One unsolicited NOP-In is enough; a Text Response carrying the same ITT crashes in iscsi_complete_task() instead.  Require the task to be in flight and not a SCSI command, the way iscsi_itt_to_ctask() does for the command opcodes.  [    6.298634] Oops: general protection fault, probably for non-canonical address 0xdffffc000000000c: 0000 [#1] SMP KASAN NOPTI [    6.298642] KASAN: null-ptr-deref in range [0x0000000000000060-0x0000000000000067] [    6.298652] CPU: 1 UID: 0 PID: 111 Comm: iscsistart Not tainted 7.2.0-rc5-ISCSI1-gf5098b6bae76 #1 PREEMPT(lazy) [    6.298654] Hardware name: QEMU Ubuntu 24.04 PC v2 (i440FX + PIIX, arch_caps fix, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 [    6.298656] RIP: 0010:iscsi_nop_out_rsp.constprop.0+0x46/0x160 [    6.298691] Code: c1 ea 03 48 83 ec 08 80 3c 02 00 0f 85 f5 00 00 00 48 b8 00 00 00 00 00 fc ff df 48 8b 6b 58 48 8d 7d 60 48 89 fa 48 c1 ea 03 <80> 3c 02 00 0f 85 c0 00 00 00 48 8b 45 60 48 39 c3 74 50 48 b8 00 [    6.298698] RSP: 0018:ffff88806c907be8 EFLAGS: 00010206 [    6.298701] RAX: dffffc0000000000 RBX: ffff888006116800 RCX: 0000000000000020 [    6.298702] RDX: 000000000000000c RSI: ffff88800525d578 RDI: 0000000000000060 [    6.298703] RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000 [    6.298706] R10: 0000000000000020 R11: 0000000000000000 R12: 0000000000000000 [    6.298706] R13: 000000000000002e R14: ffff8880056eb440 R15: ffff888006116800 [    6.298707] FS:  00007fc02d1c2740(0000) GS:ffff8880b29bc000(0000) knlGS:0000000000000000 [    6.298710] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [    6.298711] CR2: 000055fe3b56ddf8 CR3: 00000000053b9004 CR4: 0000000000770ef0 [    6.298712] PKRU: 55555554 [    6.298713] Call Trace: [    6.298714]  <IRQ> [    6.298714]  __iscsi_complete_pdu+0x13a8/0x22a0 [    6.298758]  iscsi_complete_pdu+0x54/0xa0 [    6.298759]  iscsi_tcp_hdr_recv_done+0x870/0x2c80 [    6.298778]  iscsi_tcp_recv_skb+0x31e/0xec0 [    6.298800]  iscsi_sw_tcp_recv+0x12f/0x390 [    6.298804]  __tcp_read_sock+0x1ab/0x810 [    6.298812]  iscsi_sw_tcp_data_ready+0x18b/0x510 [    6.298814]  tcp_rcv_established+0x1f56/0x3a00 [    6.298842]  tcp_v4_do_rcv+0x449/0x960 [    6.298847]  tcp_v4_rcv+0x2245/0x3bc0",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99153",
                        "url": "https://ubuntu.com/security/CVE-2026-99153",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  scsi: libiscsi: Validate the ITT reflected in a Reject PDU  A Reject PDU carries a copy of the header it rejects, and iscsi_handle_reject() takes the ITT out of that copy to find the task to clean up:        memcpy(&rejected_pdu, data, sizeof(struct iscsi_hdr));       ...       task = iscsi_itt_to_task(conn, rejected_pdu.itt);  That value is whatever the target put there. iscsi_itt_to_task() bounds the index against cmds_max and checks nothing else, so any task in the pool can be named, and iscsi_nop_out_rsp() then completes it.  An index that has never been used gives a NULL task->conn: the pool is zeroed at session setup and conn is assigned only when a task is allocated. If the task was used and returned, iscsi_complete_task() hits its WARN_ON_ONCE(task->state == ISCSI_TASK_FREE) and the refcount underflows. An in-flight SCSI command is completed as successful - a 1 MiB read returned 1048576 with none of its buffer written and no warning.  Validate the reflected ITT the way iscsi_itt_to_ctask() validates a command ITT, and require the task to be in flight and not a SCSI command.  [    6.248477] Oops: general protection fault, probably for non-canonical address 0xdffffc000000000c: 0000 [#1] SMP KASAN NOPTI [    6.249357] KASAN: null-ptr-deref in range [0x0000000000000060-0x0000000000000067] [    6.249951] CPU: 1 UID: 0 PID: 0 Comm: swapper/1 Not tainted 7.2.0-rc5-ISCSI1-gf5098b6bae76 #1 PREEMPT(lazy) [    6.250718] Hardware name: QEMU Ubuntu 24.04 PC v2 (i440FX + PIIX, arch_caps fix, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 [    6.251616] RIP: 0010:iscsi_nop_out_rsp.constprop.0+0x46/0x160 [    6.252043] Code: c1 ea 03 48 83 ec 08 80 3c 02 00 0f 85 f5 00 00 00 48 b8 00 00 00 00 00 fc ff df 48 8b 6b 58 48 8d 7d 60 48 89 fa 48 c1 ea 03 <80> 3c 02 00 0f 85 c0 00 00 00 48 8b 45 60 48 39 c3 74 50 48 b8 00 [    6.252813] RSP: 0018:ffff88806c907b80 EFLAGS: 00010206 [    6.253042] RAX: dffffc0000000000 RBX: ffff88800607e000 RCX: ffffffff8d571a25 [    6.253345] RDX: 000000000000000c RSI: ffff88806c907c38 RDI: 0000000000000060 [    6.253642] RBP: 0000000000000000 R08: 0000000000000000 R09: fffffbfff235a504 [    6.253947] R10: 0000000000000003 R11: 7463656e6e6f6320 R12: 0000000000000000 [    6.254251] R13: 0000000000000000 R14: ffff88806c907c38 R15: 0000000000000000 [    6.254549] FS:  0000000000000000(0000) GS:ffff8880d95bc000(0000) knlGS:0000000000000000 [    6.254887] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [    6.255140] CR2: 00007fc393e8ffc0 CR3: 0000000005252006 CR4: 0000000000770ef0 [    6.255439] PKRU: 55555554 [    6.255564] Call Trace: [    6.255674]  <IRQ> [    6.255768]  __iscsi_complete_pdu+0x18bf/0x22a0 [    6.256733]  iscsi_complete_pdu+0x54/0xa0 [    6.256905]  iscsi_tcp_data_recv_done+0xf4/0x250 [    6.257103]  iscsi_tcp_recv_skb+0x31e/0xec0 [    6.257680]  iscsi_sw_tcp_recv+0x12f/0x390 [    6.258061]  __tcp_read_sock+0x1ab/0x810 [    6.258853]  iscsi_sw_tcp_data_ready+0x18b/0x510 [    6.259808]  tcp_data_queue+0x1f13/0x4cd0 [    6.260567]  tcp_rcv_established+0x8a5/0x3a00 [    6.261931]  tcp_v4_do_rcv+0x449/0x960 [    6.262269]  tcp_v4_rcv+0x2245/0x3bc0",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99154",
                        "url": "https://ubuntu.com/security/CVE-2026-99154",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  scsi: libiscsi: Reject a negative task index from parse_pdu_itt  A transport that implements parse_pdu_itt hands libiscsi an index taken from the PDU, and both lookups bound it from above only:        if (i >= session->cmds_max)  i and cmds_max are both int, so a negative index passes and session->cmds[i] is read from before the array.  be2iscsi produces one. beiscsi_parse_pdu() assigns the raw tag,        *index = (int)itt;  and beiscsi_complete_pdu() forwards an unsolicited NOP-In from the hardware async ring without replacing its ITT, so the value is the target's. It also reports the session's own age rather than the one in the tag, which leaves the age comparison in iscsi_verify_itt() with nothing to reject.  Bound the index from below in both lookups.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99165",
                        "url": "https://ubuntu.com/security/CVE-2026-99165",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  sctp: revalidate output stream after association connect wait  When message interleaving is enabled, the first send waits for association establishment before building its data chunks.  The wait drops the socket lock, and handshake processing can reduce the output stream count to the peer-advertised inbound stream count.  sctp_stream_init() then frees the extension of every removed stream.  The sender resumes with the stream that it checked before the wait.  If the peer removed that stream, sctp_outq_tail() later dereferences its NULL extension.  Fatal-oops policies then panic the host.  KASAN: null-ptr-deref in range [0x38-0x3f] RIP: sctp_outq_tail+0x49e/0xaa0 Call Trace:  sctp_primitive_SEND  sctp_sendmsg_to_asoc  sctp_sendmsg  A range check alone is insufficient.  Stream reconfiguration can grow the output count again while the lock is released without recreating extensions freed by the earlier shrink.  The stream can then be in range while its extension remains NULL.  The send-buffer wait has the same issue.  Factor the range and extension checks into a helper and repeat both after each send-path wait that drops the socket lock.  Once the lock is reacquired, the validation remains stable through data creation and queueing.  If validation fails after the connect wait, the auto-created association is already established.  Return ESRCH so the existing caller path keeps it under state-machine ownership instead of freeing it directly, which would leave protocol, counter and socket state inconsistent.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99166",
                        "url": "https://ubuntu.com/security/CVE-2026-99166",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net: rds: fix uninitialized trans dereference in CM event handler  rds_rdma_cm_event_handler_cmn() assigns trans only when the RDMA device is an InfiniBand CA (RDMA_NODE_IB_CA).  On any other device type, e.g. an iWARP RNIC such as siw, trans stays uninitialized, but the event switch dereferences it: unconditionally in the RDMA_CM_EVENT_CONNECT_REQUEST case via trans->cm_handle_connect(), and (with a connection context) in the ROUTE_RESOLVED and ESTABLISHED cases.  An RDS listener on an iWARP device therefore crashes the kernel as soon as a connect request arrives: with CONFIG_INIT_STACK_ALL_ZERO the wild load becomes a NULL dereference at offset 0xa0 (&trans->cm_handle_connect) in the iw_cm_wq workqueue.  GCC masks the bug in default builds by folding the uninitialized load into &rds_ib_transport; Clang-built kernels take the real uninitialized path and oops.  The active side can land on a non-IB device too: the id that rds_ib_conn_path_connect() creates is not restricted to a node type, so rdma_resolve_addr() binds it to whichever device serves the local address, and an iWARP RNIC on the same netdev qualifies.  The crash there is different: resolving a route on an iWARP id never fills in cm_id->route.path_rec, and the ROUTE_RESOLVED case writes path_rec[0].sl before it calls into the transport.  The iWARP transport was dropped long ago and IB is the only transport left, so make that explicit: initialize trans to &rds_ib_transport at declaration, drop the conditional assignment, reject a connect request that arrives on a non-IB device, and drop a connection whose address resolved to one instead of resolving a route on it.  The rejection is limited to RDMA_CM_EVENT_CONNECT_REQUEST on purpose: a non-zero return from the handler makes rdma_cm destroy the id the event was delivered on, which is right for the request's freshly created id but would free a connection id that RDS still owns for any other event.  On the active side the id stays ic->i_cm_id and the connection's shutdown destroys it, so that case returns 0.  [achender: reject only on RDMA_CM_EVENT_CONNECT_REQUEST instead of  bailing out for every event on a non-IB device, so that rdma_cm does  not destroy connection ids RDS still tracks; drop a connection whose  address resolved to a non-IB device before a route is resolved on it;  changelog adjusted]",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99167",
                        "url": "https://ubuntu.com/security/CVE-2026-99167",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net/sched: fix use-after-free in __tcf_action_put()  __tcf_action_put() decrements the reference count before decrementing the binding count. Another thread can free the action between these operations, causing the binding-count update to access freed memory. KASAN reports it as:    BUG: KASAN: slab-use-after-free in __tcf_action_put+0x327/0x340   Write of size 4 at addr ff11000000d46420 by task tc-put-pause/64  Hold the action IDR mutex across both counter updates and IDR removal, keeping cleanup outside the lock.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99175",
                        "url": "https://ubuntu.com/security/CVE-2026-99175",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  fsnotify: prevent mark additions during connector teardown  fsnotify_destroy_marks() keeps a reference to its current mark while it drops conn->lock to destroy the mark. This stabilizes the forward-walk cursor, but does not prevent a new mark from being inserted before it. For example, an inotify watch re-added after IN_IGNORED sorts before the old, detached mark for the same group. The walk can miss the replacement and then detach the entire connector from the object.  The replacement is still on its group's marks_list and, for inotify, in the watch IDR. The group mutex no longer protects the connector's object from disappearing. An unprivileged fdinfo read racing the final detach can consequently call igrab(NULL):    BUG: KASAN: null-ptr-deref in igrab+0x24/0x100   Write of size 4 at addr 0000000000000148   Call Trace:    igrab+0x24/0x100    inotify_show_fdinfo+0x1dc/0x5e0    seq_show+0x397/0x690  Set a DESTROYING flag under conn->lock before starting the walk, and reject new marks on that connector with -ENOENT. The existing add-mark error paths undo the temporary group-list entry and the backend's watch allocation. Do not wait for teardown while holding the group mutex, which the destroyer needs. Once the old connector is detached, an add can install a fresh connector as before.  This closes the insertion race for all object types using the common connector teardown, without changing the mark reference or SRCU lifetime rules.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99176",
                        "url": "https://ubuntu.com/security/CVE-2026-99176",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  KVM: nVMX: Reset MMU back to the root MMU if loading L2 state fails for !VM-Entry  Reset the vCPU's MMU pointer back to the root MMU if loading L2 state fails in the \"not from VM-Entry\" case, i.e. when emulating RSM or handling KVM_SET_NESTED_STATE.  Failure to unwind the MMU pointer results in KVM trying to run L1 with a nested MMU, and is especially problematic if the vCPU manages to free its nested state before the VM crashes.  Constructing the root for a nested EPT MMU goes through vmcs12, which is dynamically allocated/freed when nVMX is enabled/disabled.  And so if the nested state is freed with the MMU still pointing at the nested MMU, KVM will hit a NULL pointer deref when attempting to get L1=>L2 EPTP.    BUG: kernel NULL pointer dereference, address: 0000000000000078   #PF: supervisor read access in kernel mode   #PF: error_code(0x0000) - not-present page   PGD 114a2d067 P4D 111743067 PUD 11141f067 PMD 0   Oops: Oops: 0000 [#1] SMP   CPU: 20 UID: 1000 PID: 1272 Comm: nested_tdp_faul Not tainted 7.3.0-rc4-8c89f11d1a99b-sink-vm #1914 PREEMPTLAZY   Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015   RIP: 0010:nested_ept_get_eptp+0xb/0x10 [kvm_intel]   Call Trace:    <TASK>    kvm_mmu_load+0xcd/0x870 [kvm]    kvm_arch_vcpu_ioctl_run+0x18f5/0x1f80 [kvm]    kvm_vcpu_ioctl+0x2c7/0x970 [kvm]    __x64_sys_ioctl+0x90/0xd0    do_syscall_64+0x9c/0x4d0    entry_SYSCALL_64_after_hwframe+0x4b/0x53   RIP: 0033:0x47491b    </TASK>   Modules linked in: kvm_intel kvm irqbypass   CR2: 0000000000000078   ---[ end trace 0000000000000000 ]---   RIP: 0010:nested_ept_get_eptp+0xb/0x10 [kvm_intel]  [sean: write changelog]",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99181",
                        "url": "https://ubuntu.com/security/CVE-2026-99181",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  autofs: ignore notification errors from a replaced pipe  autofs_notify_daemon() takes a reference to the current notification pipe under wq_mutex, then drops the mutex before writing the request. The write can block while the daemon enters catatonic mode and installs a replacement pipe.  If the old pipe's reader is then closed, the delayed write returns -EPIPE and the generic error path enters catatonic mode again. That transition acts on the current superblock state, closes the replacement pipe, and releases the new daemon generation's wait queues.  Only enter catatonic mode when the pipe which failed is still the current pipe. Factor the already-locked transition so the identity check and state change are atomic with respect to another replacement.  This was reproduced on v7.3-rc5-337-gff47652a4b66c in a local QEMU guest. An unprivileged UID 65534 lookup filled the old packet pipe before a normal CATATONIC/SETPIPEFD restart. On the unmodified kernel, the new pipe received HUP and both a pending victim lookup and a later lookup failed with ENOENT in two out of two fresh-mount runs.  With this change, the new pipe remained active, received an intact 304-byte request, and both victim lookups completed in two out of two runs. Normal lookup and restart-without-a-blocked-writer controls passed. No KASAN, oops, refcount, or lock diagnostic was observed. A source reproducer and complete local logs are available privately on request.  The demonstrated impact is limited to denial of a shared autofs service during a legitimate daemon restart. No memory corruption, information leak, privilege escalation, or code execution primitive was observed.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99201",
                        "url": "https://ubuntu.com/security/CVE-2026-99201",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  netlink: avoid hashing the network namespace pointer  The netlink rhashtable key includes a raw struct net pointer and a user-controlled port ID. Both /proc/net/netlink and socket diagnostics expose the table's bucket order. By binding and rebinding chosen NETLINK_USERSOCK port IDs, an unprivileged reader can distinguish equal buckets and recover the low bits of the Jenkins hash. Its 32-bit seed and the limited set of kernel-image slides can then be searched offline to recover the address of init_net.  Use the namespace's unique, non-address net_cookie in the comparison key instead. It is assigned before the per-net initializers run and remains unchanged for the namespace's lifetime. The lookup key and object hash are still built by netlink_compare_arg_init(), keeping lookup, insertion, removal and rehashing consistent while preserving namespace separation. Neither public table walker needs to change.  Reading the socket's namespace cookie in netlink_compare() is safe under RCU, including during namespace teardown. netlink_release() removes the socket from the hash table and defers its final put with call_rcu(). cleanup_net() runs the per-net exit methods and waits for outstanding RCU callbacks with rcu_barrier() before freeing namespace storage.  Unlike ns.ns_id, net_cookie is also available and initialized during setup_net() in older stable kernels, making the change straightforward to backport to v5.15 and later.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99203",
                        "url": "https://ubuntu.com/security/CVE-2026-99203",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  pipe: preserve existing fasync readers on writer setup failure  F_SETFL and FIOASYNC decide whether to invoke ->fasync() before pipe_fasync() takes pipe->mutex. Two enables of one O_RDWR FIFO can therefore both enter the callback.  fasync_helper() allocates before checking for an existing entry. If the first enable installs both entries, a second enable can update the reader entry and then fail the allocation for the writer entry. The error path removes the pre-existing reader entry, clearing FASYNC while the writer entry remains registered. __fput() then skips ->fasync(), so a later pipe notification can dereference the freed file or its f_owner. An unprivileged memory-pressure reproducer triggers a KASAN slab-use-after-free in send_sigio() through this path.  Keep the reader helper's result and undo the registration only if this call added it. The pipe mutex serializes changes to both lists, so a failed new registration still removes its reader, while a failed duplicate preserves the existing registrations and FASYNC. Successful duplicate enables continue to update fa_fd as before.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99204",
                        "url": "https://ubuntu.com/security/CVE-2026-99204",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ocfs2/dlm: Protect the recovery list during debugfs reads  Recovery participant records must remain alive while debug_state_print() walks reco.node_data and formats their fields. The formatter holds dlm->spinlock, but the recovery participant list is protected by dlm_reco_state_lock. In particular, dlm_destroy_recovery_area() detaches the list under dlm_reco_state_lock and frees the detached records after releasing it. A concurrent debugfs open can therefore read freed memory.  Protect the participant traversal and field reads in debug_state_print() with dlm_reco_state_lock, matching the existing list writers. This also serializes the traversal against list_add_tail() during recovery-area initialization. Make the existing lock available to the debug code through dlmcommon.h; the lock remains internal to the OCFS2 DLM module.  Release dlm->spinlock after formatting the other domain state and before acquiring dlm_reco_state_lock, so the debug reader does not nest the two locks. Leave recovery list insertion, detachment and freeing unchanged.  KASAN report as below:      BUG: KASAN: slab-use-after-free in debug_state_open+0x1169/0x12d0     Read of size 4 at addr ffff88810662ef80 by task dlm-state-stres/896      CPU: 1 UID: 0 PID: 896 Comm: dlm-state-stres Not tainted 7.3.0-rc4-next-20260921-pmb-ocfs2-functional-v1+ #1 PREEMPT(lazy)     Hardware name: QEMU Ubuntu 24.04 PC v2 (i440FX + PIIX, arch_caps fix, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014     Call Trace:      <TASK>      dump_stack_lvl+0x93/0xd0      print_report+0xce/0x630      ? debug_state_open+0x1169/0x12d0      ? srso_alias_return_thunk+0x5/0xfbef5      ? __virt_addr_valid+0x20e/0x420      ? debug_state_open+0x1169/0x12d0      kasan_report+0xe0/0x110      ? debug_state_open+0x1169/0x12d0      debug_state_open+0x1169/0x12d0      ? __pfx_debug_state_open+0x10/0x10      full_proxy_open_regular+0x193/0x310      do_dentry_open+0x595/0x12d0      ? __pfx_full_proxy_open_regular+0x10/0x10      vfs_open_consume+0xd1/0x400      ? srso_alias_return_thunk+0x5/0xfbef5      path_openat+0x18d0/0x2020      ? __pfx_path_openat+0x10/0x10      do_file_open+0x21e/0x470      ? __pfx_do_file_open+0x10/0x10      ? _raw_spin_unlock+0x23/0x40      ? srso_alias_return_thunk+0x5/0xfbef5      ? alloc_fd+0x3a6/0x6b0      do_sys_openat2+0xf4/0x1b0      ? __pfx_do_sys_openat2+0x10/0x10      ? srso_alias_return_thunk+0x5/0xfbef5      ? __fput+0x5b5/0xa60      __x64_sys_openat+0x136/0x1e0      ? __pfx___x64_sys_openat+0x10/0x10      do_syscall_64+0x114/0x620      entry_SYSCALL_64_after_hwframe+0x77/0x7f     [Register dump omitted.]      </TASK>      Allocated by task 880:      kasan_save_stack+0x33/0x60      kasan_save_track+0x14/0x30      __kasan_kmalloc+0xaa/0xb0      __kmalloc_cache_noprof+0x28d/0x610      dlm_remaster_locks+0x147/0x1d90      dlm_do_recovery+0xde1/0x1580      dlm_recovery_thread+0x109/0x300      kthread+0x351/0x460      ret_from_fork+0x659/0x940      ret_from_fork_asm+0x1a/0x30      Freed by task 880:      kasan_save_stack+0x33/0x60      kasan_save_track+0x14/0x30      kasan_save_free_info+0x3b/0x60      __kasan_slab_free+0x5f/0x80      kfree+0x308/0x580      dlm_destroy_recovery_area+0x285/0x460      dlm_remaster_locks+0x17c4/0x1d90      dlm_do_recovery+0xde1/0x1580      dlm_recovery_thread+0x109/0x300      kthread+0x351/0x460      ret_from_fork+0x659/0x940      ret_from_fork_asm+0x1a/0x30      The buggy address belongs to the object at ffff88810662ef80      which belongs to the cache kmalloc-32 of size 32     The buggy address is located 0 bytes inside of      freed 32-byte region [ffff88810662ef80, ffff88810662efa0)      [Page and memory-state dumps omitted.]",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99206",
                        "url": "https://ubuntu.com/security/CVE-2026-99206",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  scsi: target: iscsi: Fix race in discovery auth updates  Separate configfs opens can concurrently update the discovery AuthMethod parameter. Both callers may free the same value in iscsi_update_param_value(), causing a double-free.  Protect the lookup and replacement with the discovery TPG access lock, as used by the other TPG configfs parameter updates.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99211",
                        "url": "https://ubuntu.com/security/CVE-2026-99211",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  netlink: reset skb headers before unicast and multicast filtering  Socket filters can use SKF_NET_OFF and SKF_LL_OFF to read relative to an skb's network and MAC headers. Netlink producers may reserve headroom without resetting those headers, allowing a receiving socket's filter to read data before the initialized message.  For example, IWPM HELLO replies are allocated with dev_alloc_skb(), which reserves NET_SKB_PAD bytes. An unprivileged NETLINK_RDMA user can attach a classic socket filter and disclose this headroom through the length of the delivered reply. The resets in netlink_dump() do not help because IWPM sends a separately allocated skb through netlink_unicast().  Reset both headers before running the receiver's filter in unicast and broadcast delivery, as is already done for dump skbs. This also covers other netlink producers that reserve headroom without changing their allocation or message-building code.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99212",
                        "url": "https://ubuntu.com/security/CVE-2026-99212",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net/rds: don't let the rdma_cm destroy an id RDS still owns on route failure  rds_rdma_cm_event_handler_cmn() hands the return value of rdma_resolve_route() straight back to the rdma_cm on RDMA_CM_EVENT_ADDR_RESOLVED.  A synchronous failure there - -ENOMEM from the route work allocation, an SA query that cannot be set up, a RoCE route with no usable device - makes addr_handler() destroy the id the event was delivered on.  That id is ic->i_cm_id, and nothing clears the pointer: the connection sits in RDS_CONN_CONNECTING with a freed id until its shutdown calls rdma_disconnect() and rdma_destroy_id() on it.  The ROUTE_RESOLVED case already avoids this: rds_ib_cm_initiate_connect() forces a zero return while ic->i_cm_id == cm_id, as the comment there explains.  Do the same here - drop the connection and return 0 - so the id stays RDS's to destroy from the shutdown, and the reconnect gets a fresh one.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99213",
                        "url": "https://ubuntu.com/security/CVE-2026-99213",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  vsock: treat TCP_CLOSING as once-established  Handle the TCP_ESTABLISHED -> TCP_CLOSING transition on OP_RST, which can race with the connect loop. Immediately break and return 0 on ESTABLISHED/CLOSING. The return value of connect() should reflect what happened up to the point the connection was established or failed. Events that occur afterwards must not affect it. E.g. even if OP_RW has already set sk_err, connect() should still return 0, not ENOBUFS because of it. Adapt the inaccurate comment above signal_pending().  Resetting a socket that is still present in connected_table can lead to memory corruption. The reporter noted lost transports for in-flight skbs, and I have reproduced crashes caused by re-insertion into connected_table.    list_add double add: new=, prev=, next=.   kernel BUG at lib/list_debug.c:35!   Oops: invalid opcode: 0000 [#1] SMP KASAN NOPTI   Workqueue: vsock-loopback vsock_loopback_work   RIP: 0010:__list_add_valid_or_report+0x11f/0x130   Call Trace:    vsock_insert_connected.cold+0xe/0x13    virtio_transport_recv_pkt+0x10e9/0x1460    vsock_loopback_work+0x305/0x480    process_one_work+0xe4c/0x1560    worker_thread+0x4f1/0xd60    kthread+0x36e/0x470    ret_from_fork+0x47b/0x6b0    ret_from_fork_asm+0x1a/0x30  This fix is supplementary to commit 002541ef650b (\"vsock: Ignore signal/timeout on connect() if already established\"). Details under Link.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99216",
                        "url": "https://ubuntu.com/security/CVE-2026-99216",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  Drivers: hv: Don't reset VMBus connection state on error/exit paths  In two places, current code forces vmbus_connection.conn_state to DISCONNECTED prior to calling vmbus_disconnect(). But vmbus_disconnect() calls vmbus_initiate_unload(), which unloads the VMBus connection only if the conn_state is CONNECTED. Consequently, the connection remains and the Hyper-V host might continue to send messages or post VMBus interrupts.  The problem was introduced in commit 74347a99e73ae (\"x86/Hyper-V: Unload vmbus channel in hv panic callback\"), in that vmbus_initiate_unload() started checking the current connection state before doing the unload. This commit removed some occurrences where conn_state was forced to DISCONNECTED, but these two remained, apparently due to an oversight at the time.  Fix this by not forcing conn_state to DISCONNECTED during VMBus exit, or if a failure occurs when establishing the connection in the first place. Whatever value conn_state has at the time is then read by vmbus_initiate_unload() to determine if there is a connection to be unloaded.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-28 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2022-50167",
                        "url": "https://ubuntu.com/security/CVE-2022-50167",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  bpf: fix potential 32-bit overflow when accessing ARRAY map element  If BPF array map is bigger than 4GB, element pointer calculation can overflow because both index and elem_size are u32. Fix this everywhere by forcing 64-bit multiplication. Extract this formula into separate small helper and use it consistently in various places.  Speculative-preventing formula utilizing index_mask trick is left as is, but explicit u64 casts are added in both places.",
                        "cve_priority": "high",
                        "cve_public_date": "2025-06-18 11:15:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99082",
                        "url": "https://ubuntu.com/security/CVE-2026-99082",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  KVM: x86: Use active memslots for the per-vCPU MMIO cache  KVM tags the per-vCPU MMIO cache with a memslot generation so that a memslot update invalidates cached MMIO information.  Both the fill and validation paths use kvm_memslots(), which unconditionally selects address space 0, even when the vCPU is running in SMM and using address space 1.  Commit 56f17dd3fbc4 (\"kvm: x86: fix stale mmio cache bug\") added the memslot generation to the cache key so that a memslot update could not leave a stale entry valid.  When commit 699023e23965 (\"KVM: x86: add SMM to the MMU role, support SMRAM address space\") added the SMM address space, these helpers were not converted to use the active memslots.  Consequently, an update to the SMM memslots can leave an entry from the old SMM address space apparently valid after the vCPU returns to the normal address space.  A guest can then cause an access to valid RAM at the same GFN to be returned to userspace as KVM_EXIT_MMIO.  Completing that exit through the VMM's RAM address space writes the backing page without going through KVM's write-tracking path.  If the page backs a nested EPT table, KVM can continue using shadow translations derived from the old contents.  The WARN_ON_ONCE() in kvm_mmu_write_protect_fault() catches this invalid cache and memslot combination.  Use the vCPU's active memslots when caching and validating the entry. Memslot generations are unique across address spaces, so the generation also distinguishes the normal and SMM views.  This matches the MMIO SPTE cache, which already uses kvm_vcpu_memslots().  On an unpatched current-mainline kernel, a regression test that fills the cache in SMM and updates only the SMM memslots fails the intended RAM write and triggers the kvm_mmu_write_protect_fault() warning.  With this change, the same test completes the RAM write without a warning.  The x86/smm_test, set_memory_region_test, and memslot_modification_stress_test selftests also pass.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99083",
                        "url": "https://ubuntu.com/security/CVE-2026-99083",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ksmbd: fix heap out-of-bounds write in krb5_authenticate()  In krb5_authenticate(), out_len is calculated to determine available headroom in response_buf for the incoming Kerberos AP-REP token. However, when SMB2_SESSION_SETUP is processed as a non-first element of a compounded SMB2 request, the calculation omits work->next_smb2_rsp_hdr_off.  This causes out_len to overstate remaining buffer headroom by the cumulative size of prior responses in the compound chain. Consequently, the length check in ksmbd_krb5_authenticate() (*out_len <= resp->spnego_blob_len) passes erroneously, allowing memcpy() to write the AP-REP blob past the end of response_buf into adjacent kernel heap memory.  Fix this by subtracting work->next_smb2_rsp_hdr_off when computing out_len, ensuring it accurately reflects physical remaining buffer space.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98977",
                        "url": "https://ubuntu.com/security/CVE-2026-98977",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  namespace: handle mount locking for automounts correctly  If mounts are propagated across user namespaces, attach_recursive_mnt() locks every copy of the source mount to protect overmounts from vanishing and revealing the underlying files or directories.  The user namespace is taken from the caller's mount namespaces since this is where the mounts end up. Except, that's not always true. Automounts may legitimately get popped in by tasks located in a different mount and user namespace during path lookup.  Then check doesn't make sense at that point. The copy in the namespace of the parent - which may be the host's - is now locked and the host cannot change the flags of its own mounts anymore.  Here's the reproducer:  - host has debugfs mounted nosuid,nodev,noexec and shared - tracefs automount below it is not yet active - hand a child process a directory descriptor on that mount - child process enters auser and mount namespace - child process' namespace now holds a locked copy of the host's debugfs   mount that receives propagation from it - child process stats \"tracing/.\" through the descriptor - lookup runs on the host's mount so the automount lands below the host's mount - propagation puts a copy below the child's copy - both try to clear the flags on the mount they got, with a bind remount:      host, on its own automount:            MS_REMOUNT|MS_BIND = EPERM     child, on the copy in its namespace:   MS_REMOUNT|MS_BIND = 0  So the lock landed on the host's mount instead of the child's copy. Congrats. So we need to compare with the owner of the namespace the mount actually gets mounted on. For all regular cases that is the caller's mount namespace and so nothing changes.  Detached trees in anonymous mount namespaces by be handed over via SCM_RIGHTS or inherited in other ways on purpose so the attaching task's mount namespace is authoritative, not the creator of the detached tree.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98992",
                        "url": "https://ubuntu.com/security/CVE-2026-98992",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  namespace: don't copy an unmounted mount tree  may_copy_tree() accepts a mount whose root is an nsfs or pidfs file before it checks whether that mount is mounted. This exception exists for nsfs and pidfs mounts. They are part of no mount namespace so neither check_mnt() nor is_mounted() would let them through and bind-mounting a nsfsfd or a pidfd wouldn't work.  Problem is that exception also admits a bind mount of such a file when it was lazily unmounted and is only kept alive by a file descriptor:    mount --bind /proc/self/ns/net /tmp/x   exec 3< /tmp/x   umount -l /tmp/x   mount --rbind /proc/self/fd/3 /tmp/y  With MS_REC or AT_RECURSIVE copy_tree() doesn't stop at the unmounted mount. It copies every mount that stayed attached to it as well. So if you have a bunch of overmounts over the nsfsfd or the pidfd the whole unmounted stack is copied. That's a bug.  So refuse to walk an unmounted tree. Copying its root alone stays possible. So a bind mount of a namespace that is gone can still be recreated from a file descriptor on the old one. The file descriptor pins that mount and its root and __has_locked_children() only reads the direct children which don't leave the parent's list without namespace_sem. The internal mounts carry MNT_NS_INTERNAL instead of NULL and are still walked. Copying an unmounted tree recursively fails with EINVAL.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98981",
                        "url": "https://ubuntu.com/security/CVE-2026-98981",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  namespace: unhash a dentry before detaching the mounts on it  unlink(), rmdir() and rename() remove the entry from the filesystem, call detach_mounts() on the entry with the inode locked and then call d_delete() once the inode is unlocked.  The thing is that between detach_mounts() and d_delete() the dentry is still hashed and positive. But after detach_mounts() nothing covers the dentry anymore. A lookup that finds this dentry in the dcache can uncover what the mounts hid.  That's a problem when unlinking files or directories that are mountpoints in other mount namespaces. Everybody who had the underlying entry covered can race the detach_mount() call until d_delete() has run.  The race window isn't all that small. It encompasses namespace_unlock() with a full synchronize_rcu_expedited() grace period and the inode_unlock() of the entry.  In my experiments three walkers that kept trying read an overmounted file in 11938 of the 16140 unlinks that removed its mountpoint from a bind mount of the filesystem within a minute.  Fun fact, d_invalidate() has the same ordering problem but gets it right. It unhashes the dentry first and detaches the mounts afterwards. Let's do the same in __detach_mounts():  - A lookup that hasn't found the dentry yet misses it in the dcache and   waits for the directory lock that the caller holds until the name is   gone for good.  - A lockless lookup that found it already fails the mount_lock check   while the dentry still counts as a mountpoint and the d_seq check once   it doesn't, and retries.  This fixes the lockless path. We still need to fix the reference count lookup in a follow-up patch.  So d_drop() the dentry. The dentry stays positive and held but can't be found anymore. Then proceed with the detach and unlink.  Reproducer:  The reads were counted with the program below, three walkers for 60 s in a VM with 4 CPUs. The race window is stretched with the debug patch pasted here. fs.detach_race_walk_us sleeps in lookup_fast() once it found a mountpoint dentry and before its mounts are crossed. fs.detach_race_unlink_us sleeps in vfs_unlink() between detach_mounts() and d_delete().    // SPDX-License-Identifier: GPL-2.0   /*    * unlink_covered: unlink a file that is a mountpoint in a detached copy of    * its mount, against lookups that open it through that copy.    *    * A is a tmpfs with the file f1 (content SECRET_F) and the plain file    * MARK_A. A' is an open_tree(OPEN_TREE_CLONE) copy of A with MARK_A bound    * on A'/f1, held through an O_PATH fd on its root once the tree fd is    * closed. Walkers open f1 through that fd while the driver unlinks A/f1,    * where nothing is mounted on it. A walker may read MARK_A or get ENOENT.    * A read of SECRET_F is a hit: the name was found after its mount was    * gone. The lockless walks use openat2(RESOLVE_CACHED).    *    * usage: unlink_covered [-t seconds] [-w walkers]    */   #ifndef _GNU_SOURCE   #define _GNU_SOURCE   #endif   #include <errno.h>   #include <fcntl.h>   #include <pthread.h>   #include <stdatomic.h>   #include <stdio.h>   #include <stdlib.h>   #include <string.h>   #include <unistd.h>   #include <sys/mount.h>   #include <sys/stat.h>   #include <sys/syscall.h>   #include <linux/openat2.h>    #ifndef __NR_open_tree   #define __NR_open_tree 428   #endif   #ifndef __NR_move_mount   #define __NR_move_mount 429   #endif   #ifndef __NR_openat2   #define __NR_openat2 437   #endif   #ifndef OPEN_TREE_CLONE   #define OPEN_TREE_CLONE 1   #endif   #ifndef OPEN_TREE_CLOEXEC   #define OPEN_TREE_CLOEXEC O_CLOEXEC   #endif   #ifndef MOVE_MOUNT_F_EMPTY_PATH   #define MOVE_MOUNT_F_EMPTY_PATH 0x00000004   #endif    #define WORK \"/tmp/uc\"   #define ADIR WORK \"/A\"    static int duration = 60, nwalkers = 3;   static atomic_int stop, writer_waiting;   static pthread_rwlock_t cur_lock = PTHREAD_RWLOCK_INITIALIZER;   static int cur_fd = -1;\t\t/* the root of A', -1 wh ---truncated---",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99005",
                        "url": "https://ubuntu.com/security/CVE-2026-99005",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  drm/i915/gt: Unmask interrupts only when ACTIVE is true  There is a small race window between intel_rps_boost() reading a stale ACTIVE state and queuing rps->work, where ACTIVE may be changed via asynchronous calls triggered by wakeref drop. This means that rps_work() could be triggered after the GT has been parked, so unmasking RPS PM interrupts would happen without holding PM wakelock. This sequence of events may be observed during live_rc6_ctx_wa() selftest:  1) live_rc6_ctx_wa()    -> intel_engine_pm_put()       -> wakeref_put()  ASYNC1) wakeref_put() callback           -> __engine_park()              -> intel_gt_pm_put_async()                 -> intel_gt_pm_put_async_untracked()                    -> intel_wakeref_put_async()  ASYNC2) wakeref_put_async() callback           -> __gt_park()              -> intel_rps_park()                 -> intel_rps_clear_active() [clear ACTIVE]                 WITH INTERRUPTS:                 -> rps_disable_interrupts()                    -> cancel_work_sync(rps->work)                    -> rps_reset_interrupts() [rps->pm_iir = 0]                 WITHOUT INTERRUPTS (TIMER mode):                 -> rps_stop_timer()                    -> cancel_work_sync(rps->work)  2) live_rc6_ctx_wa()    -> intel_gt_wait_for_idle()       -> intel_gt_retire_requests_timeout()          -> dma_fence_wait_timeout()             -> ops->wait() [i915_fence_wait()]                -> i915_request_wait_timeout()                   -> intel_rps_boost()                      -> intel_rps_is_active() [check ACTIVE]                         [OPEN RACE WINDOW]                      -> queue_work(rps->work)          -> retire_requests()             -> i915_request_retire()                -> intel_rps_dec_waiters() [from 1 to 0]  If ASYNC1 and ASYNC2 would execute during [OPEN RACE WINDOW], then:  3) rps_work() executes from the workqueue and may satisfy    \"(!pm_iir && !client_boost)\" test (in TIMER mode rps->pm_iir    is zeroed by an earlier rps_work() call or never gets a new    value after previous intel_rps_unpark() event), so it jumps    to \"out\" label, bypassing intel_rps_is_active() guard and    executes gen6_gt_pm_unmask_irq();  4) GT is parked and runtime PM wakelock is dropped, so only    a raw reference in __gt_park() ->    intel_display_power_put_async() remains for 100ms, then the    MMIO write in gen6_gt_pm_unmask_irq() detects missing    wakelock via assert_rpm_wakelock_held() and emits    \"RPM wakelock ref not held during HW access\" tainting kernel.  Commit 3e7abf814193 (\"drm/i915: Extract GT render power state management\") dropped the \"if (rps->interrupts_enabled)\" guard that gen6_pm_rps_work() had around this unmask in i915_irq.c. INTEL_RPS_ACTIVE brackets the same window, since it is set in intel_rps_unpark() before rps_enable_interrupts() and rps_start_timer() and cleared in intel_rps_park() before rps_stop_timer() and rps_disable_interrupts().  Skip unmasking when RPS is no longer active (reaching unmask operation is independent of INTERRUPT mode). This does not prevent RPS operation from resuming on the next unpark. In interrupt mode, intel_rps_unpark() calls rps_enable_interrupts(), which enables and unmasks the PM interrupts. In timer mode, it calls rps_start_timer(), restarting periodic engine-busyness evaluation. The timer generates software RPS events and queues rps_work() directly, independently of PM interrupt delivery. Neither mode requires the late worker to unmask interrupts while the GT is parked  (cherry picked from commit ca4a6deadad15b91ee083afe445fa6bdbfb68206)",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99007",
                        "url": "https://ubuntu.com/security/CVE-2026-99007",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  drm/fb-helper: defer setup when fbdev_probe() fails, not just on -EAGAIN  __drm_fb_helper_initial_config_and_unlock() calls drm_client_modeset_probe() first, which already fills in each mode_set->mode/num_connectors for every connected output, and only afterwards calls drm_fb_helper_single_fb_probe() to create fb_helper->fb and wire it into those mode_sets via drm_setup_crtcs_fb().  If drm_fb_helper_single_fb_probe() fails with anything other than -EAGAIN (e.g. dev->driver->fbdev_probe() itself fails), the function bails out before drm_setup_crtcs_fb() runs and before setting fb_helper->deferred_setup. The client is left with mode_sets that have a mode and connectors but mode_set->fb == NULL, and nothing marks this fb_helper as needing a retry.  __drm_fb_helper_restore_fbdev_mode_unlocked() only skips committing when fb_helper->deferred_setup is set, so a later .restore() call (drm_lastclose() on process exit, in this report) commits the stale mode_set through drm_client_modeset_commit() -> drm_client_modeset_commit_atomic() -> __drm_atomic_helper_set_config(), which hits WARN_ON(!set->fb).  Mark fb_helper->deferred_setup on any drm_fb_helper_single_fb_probe() failure, not just -EAGAIN, so restore keeps skipping the commit until a later hotplug event successfully re-probes and re-populates mode_set->fb. The real error code is still returned to the caller unchanged.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99019",
                        "url": "https://ubuntu.com/security/CVE-2026-99019",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  scsi: ch: Do not keep references to data transfer element devices  ch_readconfig() looks up the scsi_device of every data transfer element whose SCSI id the changer reports in READ ELEMENT STATUS, and stores it in ch->dt[]. scsi_device_lookup() takes a reference, and nothing ever drops it: ch_destroy() frees the array with kfree(). ch->dt[] is read nowhere else - it only supplies the vendor, model and revision printed in the same loop.  Once such a drive is removed, its scsi_device can never be released. It stays on the host's device list at its address, so a new device there is refused by anything that walks the list - target_core_pscsi reports \"scsi_device_get() failed for H:C:T:L\" - and the low-level driver's module can no longer be unloaded. Only a reboot recovers.  It shows with any changer that reports its drives' ids; with the mhvtl virtual library (IBM 3573-TL personality), each create and remove of a library with four drives leaves four references behind, counted by the module's use count in lsmod. With ch not bound the count is unchanged, and with this patch applied it is unchanged too.  Drop the reference as soon as the name has been printed, and remove the now unused dt[] array. That also removes the array leaked when ch_probe() fails after ch_readconfig().  The same leak was reported with an RFC patch in 2022, which was not merged.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99024",
                        "url": "https://ubuntu.com/security/CVE-2026-99024",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  optee: register TEE devices only once fully initialized  optee_probe() called tee_device_register() on both the client and the supplicant device before the rest of struct optee had been initialized.  tee_device_register() calls cdev_device_add(), which does two things at once: it creates /dev/tee0 and /dev/teepriv0, and it links the device into the tee class so that class_find_device() can find it. From that moment on the device is reachable both from user space via tee_open() and from kernel space via tee_client_open_context(). The only gate in teedev_open() is tee_device_get(), which merely checks that teedev->desc is non-NULL, which was already set by tee_device_alloc(). Therefore, there is effectively no gate at all.  A context opened in that window can run against a struct optee where    - optee->call_queue.mutex is not initialized by optee_cq_init()   - optee->supp mutex and completions is not initialized by     optee_supp_init()   - optee->rpmb_dev_mutex is not initialized yet,   - the message argument cache is not initialized by     optee_shm_arg_cache_init()   - optee->ctx is still NULL  Any open session or invoke during this window takes uninitialized mutexes and dereferences a NULL pointer.  Fix it by moving both tee_device_register() calls down to the point where all of struct optee is set up.  [JW: adding fixes and cc]",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99036",
                        "url": "https://ubuntu.com/security/CVE-2026-99036",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  dm: fix reading free memory in do_resume  When do_resume calls dm_table_get_mode(new_map), the call is done without holding any locks (it only holds a reference to the md). It may be possible that another concurrent ioctl on the same device will swap table after dm_swap_table and before dm_table_get_mode. In this case, dm_table_get_mode(new_map) reads freed memory.  This race condition was triggered by syzbot.  This commit fixes the race by reading mode of the new table before dm_swap_table. Note that new_map is also passed to dm_ima_need_measure, but this function doesn't attempt to dereference it, so this call should be safe.  Note that this is not a security bug because only root can trigger it and the commonly used tools such as lvm or cryptsetup do not call the ioctls concurrently, so that they can't trigger it acceidentally.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98985",
                        "url": "https://ubuntu.com/security/CVE-2026-98985",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  namespace: check the mounts before reading their parents in pivot_root()  path_pivot_root() reads the parents of new_root and of the caller's root and checks whether they are shared before it checks that either mount is in the caller's mount namespace. Only namespace_sem is held. That's fine for a mount that is in the caller's mount namespace.  But new_root can be a file descriptor to a mount that has been unmounted and that only the file descriptor keeps alive. If that mount stayed attached to its parent when it was unmounted nothing pins the parent for it. The final mntput() of the parent unhooks the children under mount_lock alone and frees the parent afterwards:    pivot_root()                     close(fd), last ref on the parent   ------------                     ---------------------------------   ex_parent = new_mnt->mnt_parent                                    mntput_no_expire_slowpath()                                      __umount_mnt(new_mnt)                                    cleanup_mnt()                                      call_rcu()   IS_MNT_SHARED(ex_parent)    BUG: KASAN: slab-use-after-free in path_pivot_root+0xf1a/0x1840   Read of size 4 at addr ffff8881047382f8 by task pivot_widen/157    path_pivot_root+0xf1a/0x1840    __x64_sys_pivot_root+0x165/0x190  The same goes for the caller's root via chroot(). Both outcomes of the check end in EINVAL so nothing but the read itself goes wrong. It's the same thing commit bb4609405752 (\"statmount: read the parent of an unmounted mount under mount_lock\") fixed for statmount().  Check that both mounts are in the caller's namespace before their parents are read. Every path returns EINVAL either way.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98993",
                        "url": "https://ubuntu.com/security/CVE-2026-98993",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  namespace: don't inherit MNT_UMOUNT in clone_mnt()  MNT_UMOUNT gets raised on a mount that umount_tree() or umount_one() has taken out of its namespace. It's never cleared. __detach_mounts() unhooks a mount that carries it instead of unmounting it.  disconnect_mount() lets an unmounted child stay attached only if its parent carries it. propagate_umount() takes it as the sign that a mount is going to be unmounted when it decides what else can be unmounted, where a chain of locked mounts ends and where a for reparenting an overmount.  clone_mnt() copies the flags of the source and only masks MNT_INTERNAL_FLAGS which doesn't include MNT_UMOUNT. A mount that was lazily unmounted but is kept alive by a file descriptor can still be copied when its root is an nsfs or pidfs file because may_copy_tree() accepts those before checking whether the source is mounted at all:    mount --bind /proc/self/ns/net /tmp/x   exec 3< /tmp/x   umount -l /tmp/x   mount --bind /proc/self/fd/3 /tmp/y  The mount on /tmp/y is attached to the caller's namespace with MNT_UMOUNT already set and every copy of it inherits the flag again.  That causes a number of bugs:  - Unlink its mountpoint from a mount namespace where it isn't one.   __detach_mounts() takes it for a mount that was unmounted earlier,   unhooks it from its parent and drops the reference the namespace   holds on it. It stays in the namespace with one reference too few   and as its own parent, so it can't be unmounted through the file   descriptor anymore and the namespace never finds it again. When the   namespace goes away it's leaked and points to a freed struct   mnt_namespace that may_change_propagation() and anon_ns_root() read   on the next propagation change or mount_setattr() through the file   descriptor.  - Make it shared and unmount a peer. trace_transfers() follows the   flag from the peer into it and strips it from its peer group.  - Let a propagated umount reach it. gather_candidates() marks it with   T_UMOUNT_CANDIDATE but never puts it on the candidate list, so the   mark is never cleared and every later propagated umount skips it. If   it's the parent of a locked mount handle_locked() takes it as the   cutoff and commits the locked child that should have stayed and   disconnect_mount() leaves that child attached to it, unmounted under   a mounted parent, which is what disconnect_mount() exists to   prevent. When the namespace goes away umount_tree() visits the child   a second time. And once __detach_mounts() has made it its own parent   reparent() never finds the end of the chain of unmounted parents.  A clone is a new mount that has never been unmounted. Add MNT_UMOUNT to MNT_INTERNAL_FLAGS so clone_mnt() never copies it. And warn when umount_tree() reaches a mount that already has it set.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99002",
                        "url": "https://ubuntu.com/security/CVE-2026-99002",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  drm/vmwgfx: validate pitch coming from userspace  Validate the pitch, alongside the box dimensions before trying to copy data from the underlying surface. Fixes possible out of bounds reads with cursor snooping.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99027",
                        "url": "https://ubuntu.com/security/CVE-2026-99027",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net: team: stop reusing skb after queue override  A nonzero dev_queue_xmit() result does not return ownership of the skb. When an override port's qdisc drops it, the queue override helper used to try another port or the mode transmit op with the freed skb.  Return the handoff decision separately from transmit success. Select only the first override port under RCU and stop after handing it the skb, regardless of the lower transmit result. Keep the existing success and drop accounting.    BUG: KASAN: slab-use-after-free in sk_skb_reason_drop   Write of size 4 by task poc/5040   sk_skb_reason_drop (net/core/skbuff.c:1240)   dev_kfree_skb_any_reason (net/core/dev.c:3470)   ab_transmit (drivers/net/team/team_mode_activebackup.c:49)   team_xmit (drivers/net/team/team_core.c:1849)   __dev_direct_xmit (net/core/dev.c:4934)   Freed by task 5040:   __tcf_kfree_skb_list (net/sched/sch_generic.c:43)   __dev_queue_xmit (net/core/dev.c:4831)   team_xmit (drivers/net/team/team_core.c:1846)   Kernel panic - not syncing: KASAN: panic_on_warn set ...",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-64190",
                        "url": "https://ubuntu.com/security/CVE-2026-64190",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net: team: fix NULL pointer dereference in team_xmit during mode change  __team_change_mode() clears team->ops with memset() before restoring safe dummy handlers via team_adjust_ops(). A concurrent team_xmit() running under RCU on another CPU can read team->ops.transmit during this window and call a NULL function pointer, crashing the kernel.  The race requires a mode change (CAP_NET_ADMIN) concurrent with transmit on the team device.   BUG: kernel NULL pointer dereference, address: 0000000000000000  Oops: 0010 [#1] SMP KASAN NOPTI  RIP: 0010:0x0  Call Trace:   team_xmit (drivers/net/team/team_core.c:1853)   dev_hard_start_xmit (net/core/dev.c:3904)   __dev_queue_xmit (net/core/dev.c:4871)   packet_sendmsg (net/packet/af_packet.c:3109)   __sys_sendto (net/socket.c:2265)  The original code assumed that no ports means no traffic, so mode changes could freely memset()/memcpy() the ops.  AF_PACKET with forced carrier breaks that assumption.  Prevent the race instead of making it safe: replace memset()/memcpy() with per-field updates that never touch transmit or receive.  Those two handlers are managed solely by team_adjust_ops(), which already installs dummies when tx_en_port_count == 0 (always true during mode change since no ports are present).  WRITE_ONCE/READ_ONCE prevent store/load tearing on the handler pointers.  synchronize_net() before exit_op() drains in-flight readers that may still reference old mode state from before port removal switched the handlers to dummies.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-07-20 17:18:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99041",
                        "url": "https://ubuntu.com/security/CVE-2026-99041",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ip6_gre: remove obsolete ERSPAN PMTU update  A tc tunnel_key action can attach a METADATA_IP_TUNNEL dst to an skb, and mirred can redirect it to a native ip6erspan device. The legacy PMTU update in ip6erspan_tunnel_xmit() treats that metadata dst as a route. Since it has no output device, dst_dev(dst)->mtu dereferences NULL.  On v7.2 with KASAN, an initial UID/GID 65534 process with CapEff 0 used self-created user and network namespaces to trigger:    KASAN: null-ptr-deref   RIP: ip6erspan_tunnel_xmit+0x10fc/0x2cc0   Kernel panic - not syncing: Fatal exception in interrupt  The update is obsolete. Commit fe1a4ca0a2b7 (\"ip6_gre: process toobig in a better way\") changed IPv6 GRE Too Big handling to update the underlay route and removed the equivalent block from __gre6_xmit(). ip6_tnl_xmit() then propagates the underlay PMTU to the overlay route.  Remove the stale ERSPAN copy and its now-unused dst variable. This eliminates the metadata-dst dereference and keeps ERSPAN aligned with IPv6 GRE PMTU handling.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-97935",
                        "url": "https://ubuntu.com/security/CVE-2026-97935",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  tracing: Set the trace clock before registering the histogram trigger  hist_register_trigger() puts the trigger on the global named_triggers list in cmd_ops->init(), and only then sets the trace clock:  \tif (data->cmd_ops->init) { \t\tret = data->cmd_ops->init(data); \t\tif (ret < 0) \t\t\tgoto out; \t}  \tif (hist_data->enable_timestamps) { \t\tret = tracing_set_clock(file->tr, hist_data->attrs->clock); \t\tif (ret) { \t\t\thist_err(tr, HIST_ERR_SET_CLOCK_FAIL, errpos(clock)); \t\t\tgoto out; \t\t}  The clock string is not checked anywhere before that call, so a named trigger using common_timestamp with an unknown clock fails after it has already become findable. event_hist_trigger_parse() then frees it without taking it off the list, and the next lookup by name reads the freed object:   ~# cd /sys/kernel/tracing/events/sched/sched_switch  ~# echo 'hist:name=foo:keys=common_pid:ts=common_timestamp:clock=bogus' > trigger  bash: echo: write error: Invalid argument  ~# echo 'hist:name=foo:keys=common_pid' > trigger    BUG: KASAN: slab-use-after-free in find_named_trigger+0xac/0xc0   Read of size 8 at addr ffff88800915d760 by task init/1    find_named_trigger+0xac/0xc0    hist_register_trigger+0xc1/0x900    event_hist_trigger_parse+0x3146/0x6af0    event_trigger_write+0xce/0x160   Freed by task 63:    kfree+0x154/0x420    trigger_kthread_fn+0xfd/0x160  Set the clock before the trigger is registered, so that nothing which can fail runs after it is published, the way commit 6f86bdeab633 (\"tracing: Fix bad hist from corrupting named_triggers list\") moved the registration below the rest of the setup.  tracing_set_filter_buffering() is reference counted, so the init failure path has to drop the reference that the clock block now takes first.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-09-25 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98944",
                        "url": "https://ubuntu.com/security/CVE-2026-98944",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  HID: steam: Refactor registration  This refactors and simplifies the registration/unregistration flow. Since we now only perform registration when the client isn't opened anymore, the logic for handling that can be removed, and the rest of the function streamlined.  We also remove the previous assumption that we have a serial number to show we're registered, replacing it with a single purpose boolean.  In a previous refactor the code for unregistering a battery if later registration steps failed was accidentally left out. As a result, a lingering power_supply object could get left over after the steam object was torn down. This is also fixed here.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98945",
                        "url": "https://ubuntu.com/security/CVE-2026-98945",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  HID: steam: Rearrange teardown sequence  This fixes a narrow window during the teardown sequence where callbacks could still be scheduled during cleanup that would then have a dangling pointer to the now-freed steam struct.  This also puts work canceling for rumble and mode switch in steam_unregister, as that shouldn't persist while the client hdev is open.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2025-40135",
                        "url": "https://ubuntu.com/security/CVE-2025-40135",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ipv6: use RCU in ip6_xmit()  Use RCU in ip6_xmit() in order to use dst_dev_rcu() to prevent possible UAF.",
                        "cve_priority": "high",
                        "cve_public_date": "2025-11-12 11:15:00 UTC"
                    },
                    {
                        "cve": "CVE-2025-38728",
                        "url": "https://ubuntu.com/security/CVE-2025-38728",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  smb3: fix for slab out of bounds on mount to ksmbd  With KASAN enabled, it is possible to get a slab out of bounds during mount to ksmbd due to missing check in parse_server_interfaces() (see below):   BUG: KASAN: slab-out-of-bounds in  parse_server_interfaces+0x14ee/0x1880 [cifs]  Read of size 4 at addr ffff8881433dba98 by task mount/9827   CPU: 5 UID: 0 PID: 9827 Comm: mount Tainted: G  OE       6.16.0-rc2-kasan #2 PREEMPT(voluntary)  Tainted: [O]=OOT_MODULE, [E]=UNSIGNED_MODULE  Hardware name: Dell Inc. Precision Tower 3620/0MWYPT,  BIOS 2.13.1 06/14/2019  Call Trace:   <TASK>  dump_stack_lvl+0x9f/0xf0  print_report+0xd1/0x670  __virt_addr_valid+0x22c/0x430  ? parse_server_interfaces+0x14ee/0x1880 [cifs]  ? kasan_complete_mode_report_info+0x2a/0x1f0  ? parse_server_interfaces+0x14ee/0x1880 [cifs]    kasan_report+0xd6/0x110    parse_server_interfaces+0x14ee/0x1880 [cifs]    __asan_report_load_n_noabort+0x13/0x20    parse_server_interfaces+0x14ee/0x1880 [cifs]  ? __pfx_parse_server_interfaces+0x10/0x10 [cifs]  ? trace_hardirqs_on+0x51/0x60  SMB3_request_interfaces+0x1ad/0x3f0 [cifs]  ? __pfx_SMB3_request_interfaces+0x10/0x10 [cifs]  ? SMB2_tcon+0x23c/0x15d0 [cifs]  smb3_qfs_tcon+0x173/0x2b0 [cifs]  ? __pfx_smb3_qfs_tcon+0x10/0x10 [cifs]  ? cifs_get_tcon+0x105d/0x2120 [cifs]  ? do_raw_spin_unlock+0x5d/0x200  ? cifs_get_tcon+0x105d/0x2120 [cifs]  ? __pfx_smb3_qfs_tcon+0x10/0x10 [cifs]  cifs_mount_get_tcon+0x369/0xb90 [cifs]  ? dfs_cache_find+0xe7/0x150 [cifs]  dfs_mount_share+0x985/0x2970 [cifs]  ? check_path.constprop.0+0x28/0x50  ? save_trace+0x54/0x370  ? __pfx_dfs_mount_share+0x10/0x10 [cifs]  ? __lock_acquire+0xb82/0x2ba0  ? __kasan_check_write+0x18/0x20  cifs_mount+0xbc/0x9e0 [cifs]  ? __pfx_cifs_mount+0x10/0x10 [cifs]  ? do_raw_spin_unlock+0x5d/0x200  ? cifs_setup_cifs_sb+0x29d/0x810 [cifs]  cifs_smb3_do_mount+0x263/0x1990 [cifs]",
                        "cve_priority": "high",
                        "cve_public_date": "2025-09-04 16:15:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-31678",
                        "url": "https://ubuntu.com/security/CVE-2026-31678",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  openvswitch: defer tunnel netdev_put to RCU release  ovs_netdev_tunnel_destroy() may run after NETDEV_UNREGISTER already detached the device. Dropping the netdev reference in destroy can race with concurrent readers that still observe vport->dev.  Do not release vport->dev in ovs_netdev_tunnel_destroy(). Instead, let vport_netdev_free() drop the reference from the RCU callback, matching the non-tunnel destroy path and avoiding additional synchronization under RTNL.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-04-25 09:16:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99088",
                        "url": "https://ubuntu.com/security/CVE-2026-99088",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net: openvswitch: validate transport header presence in set_ipv6_addr  When executing IPv6 address rewrite actions on IPv6 fragments, set_ipv6_addr() calls update_ipv6_checksum(). If parse_ipv6hdr() processes a non-first IPv6 fragment, it sets key->ip.proto to NEXTHDR_FRAGMENT and returns early without calling skb_set_transport_header().  update_ipv6_checksum() unconditionally evaluates skb_transport_offset() on entry before checking l4_proto.  Because skb->transport_header is uninitialized, this triggers a warning under CONFIG_DEBUG_NET=y although it is completely harmless.  Fix this by returning early in update_ipv6_checksum() if l4_proto is NEXTHDR_FRAGMENT. This avoids reading the uninitialized transport offset for fragments while preserving the debug warning for any other protocol where the transport header is unexpectedly missing.  See the syzbot trace:  !skb_transport_header_was_set(skb) WARNING: ./include/linux/skbuff.h:3075 at skb_transport_header include/linux/skbuff.h:3075 [inline], CPU#1: syz-executor463/5635 WARNING: ./include/linux/skbuff.h:3075 at skb_transport_offset include/linux/skbuff.h:3250 [inline], CPU#1: syz-executor463/5635 WARNING: ./include/linux/skbuff.h:3075 at update_ipv6_checksum net/openvswitch/actions.c:361 [inline], CPU#1: syz-executor463/5635 WARNING: ./include/linux/skbuff.h:3075 at set_ipv6_addr+0x462/0x660 net/openvswitch/actions.c:399, CPU#1: syz-executor463/5635 [...] RIP: 0010:skb_transport_header include/linux/skbuff.h:3075 [inline] RIP: 0010:skb_transport_offset include/linux/skbuff.h:3250 [inline] RIP: 0010:update_ipv6_checksum net/openvswitch/actions.c:361 [inline] RIP: 0010:set_ipv6_addr+0x462/0x660 net/openvswitch/actions.c:399 [...] Call Trace:  <TASK>  set_ipv6 net/openvswitch/actions.c:531 [inline]  do_execute_actions+0x557e/0x8600 net/openvswitch/actions.c:1366  ovs_execute_actions+0xde/0x520 net/openvswitch/actions.c:1592  ovs_packet_cmd_execute+0xb4f/0xf10 net/openvswitch/datapath.c:705  genl_family_rcv_msg_doit+0x233/0x340 net/netlink/genetlink.c:1114  genl_rcv_msg+0x614/0x7a0 net/netlink/genetlink.c:1209  netlink_rcv_skb+0x226/0x4a0 net/netlink/af_netlink.c:2572  genl_rcv+0x28/0x40 net/netlink/genetlink.c:1218  netlink_unicast+0x7bd/0x940 net/netlink/af_netlink.c:1361  netlink_sendmsg+0x813/0xb40 net/netlink/af_netlink.c:1916  sock_sendmsg_nosec+0x14e/0x190 net/socket.c:800",
                        "cve_priority": "negligible",
                        "cve_public_date": "2026-10-26 15:16:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98950",
                        "url": "https://ubuntu.com/security/CVE-2026-98950",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  flow_dissector: avoid u16 truncation of hlen in bpf_flow_dissect()  bpf_flow_dissect() sanitizes the offsets returned by the BPF program with clamp_t(u16, ..., hlen).  If hlen is bigger than 65535, the upper bound is truncated before the comparison. For instance, with hlen == 65536, both nhoff and thoff are forced to zero, even if the program returned sane values.  This is the same class of bug as the one fixed in commit 99bda1ecbd56 (\"flow_dissector: avoid u16 truncation of skb->len when computing thoff\"). That fix does not cover the BPF path, because __skb_flow_dissect() returns early when a BPF flow dissector handles the packet.  struct bpf_flow_keys stores nhoff and thoff as u16, so cap hlen to U16_MAX before clamping.  Found by sashiko while reviewing the commit above.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98955",
                        "url": "https://ubuntu.com/security/CVE-2026-98955",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  flow_dissector: avoid u16 truncation of skb->len when computing thoff  __skb_flow_dissect() computes key_control->thoff using:    key_control->thoff = min_t(u16, nhoff, skb ? skb->len : hlen);  min_t(u16, ...) casts both arguments to u16 before comparing them. Whenever skb->len (or hlen) modulo 65536 is smaller than nhoff, the truncated length wins and thoff is set to a bogus small value, even when the dissection succeeded. For example, an IPv4/TCP frame with skb->len == 65540 and nhoff == 34 gets thoff == 4, so callers such as skb_probe_transport_header() point the transport header inside the Ethernet header.  Such skbs are not exotic: - At the time of commit d0c081b49137 (\"flow_dissector: properly cap   thoff field\"), AF_PACKET with PACKET_VNET_HDR could already build GSO   skbs larger than 64KB (MTU checks are skipped for GSO, and   alloc_skb_with_frags() accepted up to MAX_SKB_FRAGS (17) order-0   pages on top of the linear part). - BIG TCP now makes skbs larger than 64KB common. - The following patch makes tun_get_user() dissect IFF_TAP frames   before eth_type_trans() pulls the Ethernet header, so a GSO frame   carrying a 65522..65535 byte L3 packet will be dissected with   skb->len in [65536, 65549].  Compare as u32 instead. If the resulting offset cannot be represented in the u16 key_control->thoff, cap it to U16_MAX and report the dissection as failed rather than silently returning a wrong transport offset. thoff is still set on failure, as some callers (such as eth_get_headlen()) use it regardless of the return value.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99089",
                        "url": "https://ubuntu.com/security/CVE-2026-99089",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ASoC: samsung: i2s: enable op_clk in probe to balance runtime PM  The probe function puts the device into the runtime PM active state with only the \"iis\" bus clock enabled, but it also sets priv->op_clk to the parent of the RCLK_SRC mux without enabling it. The runtime PM suspend callback disables both clocks, so the first runtime suspend after probe disables op_clk once more than it was enabled.  On Exynos5250 Arndale both clocks resolve to the same EXYNOS_I2S_BUS gate, so this triggers the following warning during boot:   WARNING: drivers/clk/clk.c:1270 at clk_core_disable+0xe4/0x23c, CPU#0: kworker/u8:3/45  i2s_bus already disabled  ...  Workqueue: pm pm_runtime_work  Call trace:   ...   clk_core_disable from clk_disable+0x28/0x34   clk_disable from i2s_runtime_suspend+0x58/0x68 [snd_soc_i2s]   i2s_runtime_suspend [snd_soc_i2s] from genpd_runtime_suspend+0xc4/0x298   genpd_runtime_suspend from __rpm_callback+0x48/0x18c   __rpm_callback from rpm_callback+0x4c/0x50   rpm_callback from rpm_suspend+0xf4/0x718   rpm_suspend from pm_runtime_work+0x9c/0xa0   ...  Fix this by enabling op_clk in probe right after getting it, so the clock state matches the runtime PM active state, and by disabling it in remove.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-26 15:16:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98956",
                        "url": "https://ubuntu.com/security/CVE-2026-98956",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ASoC: adau1372: allow sleepy powerdown GPIOs  gpiod_set_value() emits a WARN when the GPIO provider indicates that it can sleep, as is typical for I2C controlled GPIO expanders. Since the powerdown GPIO is only manipulated in process context, use the _cansleep variant instead. This lets the driver use sleepy GPIOs to power off the chip.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98964",
                        "url": "https://ubuntu.com/security/CVE-2026-98964",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  nvmet: use the local P2P device on metadata allocation failure  nvmet_req_alloc_p2pmem_sgls() assigns req->p2p_dev only after the data and metadata SGL allocations succeed. If the data allocation succeeds but the metadata allocation fails, out_free_sg passes req->p2p_dev to pci_p2pmem_free_sgl() before that assignment has taken place.  Pass the local p2p_dev argument instead, so cleanup uses the same PCI device as the successful data allocation.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98967",
                        "url": "https://ubuntu.com/security/CVE-2026-98967",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  cxgb4/ch_ktls: disable softirqs around tid_list erases  chcr_ktls_cpl_act_open_rpl() inserts into tid_list from the receive path using xa_insert_bh().  The array is shared by the adapter's connections and initialized with XA_FLAGS_LOCK_BH.  However, chcr_ktls_dev_del() and the chcr_ktls_dev_add() error path use xa_erase(), which takes the XArray lock without disabling softirqs.  When cleanup runs with softirqs enabled, a receive softirq for another connection on the same CPU can interrupt the erase and spin on the lock held by the interrupted task.  Use xa_erase_bh() at both sites to match the insertion path.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98969",
                        "url": "https://ubuntu.com/security/CVE-2026-98969",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net/sched: em_text: reject unterminated algo before autoload  This is a follow-up to commit 9c572a83037a (\"net/sched: fix potential stack infoleak in em_text_dump()\"), which zero-initialised the dump-side struct. Sashiko pointed at a pre-existing bug that exposed the change-side input-validation gap open.  em_text_change() casts the raw netlink attribute payload to struct tcf_em_text and passes conf->algo, a 16-byte array with no enforced NUL terminator, to textsearch_prepare().  On the TS_AUTOLOAD retry textsearch_prepare() calls request_module(\"ts_%s\", algo); vsnprintf() walks %s until it finds a NUL, so an algo[] with no NUL reads past the array into the adjacent struct fields and payload and feeds those bytes to the usermode helper command line.  This is an out-of-bounds read and a kernel memory disclosure.  Reject the attribute when no NUL exists within TC_EM_TEXT_ALGOSIZ bytes, matching the check xt_string has had since 3ab720881b6e.  Conditions to recreate the bug: - CAP_NET_ADMIN on the target netns (namespace-local via unshare -Urn   is enough) - install clsact on an interface, then add a basic filter with one text   ematch whose algo[] is 16 bytes with no NUL (e.g. \"A\"*16) and   pattern_len at least 1 - the add fails with -ENOENT and the kernel invokes modprobe with a   module name made of \"ts_\" plus the 16 bytes and the adjacent payload",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98970",
                        "url": "https://ubuntu.com/security/CVE-2026-98970",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  drm/vc4: Free the BO cache size list on teardown  vc4_bo_cache_destroy() purges the cached BOs but never frees the size list, leaking it on every unbind.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98971",
                        "url": "https://ubuntu.com/security/CVE-2026-98971",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  gpio: exar: initialize the ID before registering its cleanup  devm_add_action_or_reset() invokes the cleanup action immediately when registering the action fails.  gpio_exar_probe() currently stores the allocated ID in exar_gpio only after registering the action, so that failure makes exar_devm_ida_free() release ID 0.  If the allocated ID is nonzero, this leaks that ID and can free ID 0 belonging to another device.  Store the ID before registering the cleanup action so both the immediate failure path and normal device teardown release the correct allocation.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98979",
                        "url": "https://ubuntu.com/security/CVE-2026-98979",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  namespace: refuse an automount below a mount that is in no namespace  It's possible to add autmounts even when the parent mount isn't in the mount namespace of the caller. The only requirement we have is that the parent mount namespace must not be NULL, i.e., unmounted.  Problem is that clone_private_mount() has MNT_NS_INTERNAL which makes that trivially true. So that passes the test and attach_recursive_mnt() accepts that as a mount point and funny enough, count_mounts() dereferences MNT_NS_INTERNAL. The problem is it is an error pointer...  So we can reach this in userspace via fanotify. A filesystem mark on the lower filesystem of an overlay reports paths on the layer clone and reading the event hands out a descriptor on it. For example with debugfs as the lower layer it goes kaboom:    openat(evfd, \"tracing\", O_DIRECTORY)    Oops: general protection fault   KASAN: null-ptr-deref in range [0x1d0-0x1d7]   RIP: 0010:count_mounts+0x35/0x200    attach_recursive_mnt    finish_automount  And since that sleeping beauty happens under namespace_sem held for writing every mount operation on the system blocks from then on. Congrats.  Use is_mounted() instead which rejects unmounted and internal mounts alike. The open fails with EINVAL just as it did before clone_private_mount() used MNT_NS_INTERNAL.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98984",
                        "url": "https://ubuntu.com/security/CVE-2026-98984",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  dcache: don't put a mountpoint on a dentry that's being removed  rmdir(), unlink() and rename() call dont_mount() on the victim and then detach_mounts() with the victim's inode locked. do_lock_mount() takes the inode lock of the mountpoint and checks cant_mount() so a mount can't show up after detach_mounts().  But attach_recursive_mnt() makes a second mountpoint for the root of the source mount so that the mounts already located at the destination can be put on top of it. No inode is locked for that one and d_set_mounted() only refuses a dentry that is unlinked. Between detach_mounts() and d_delete() the victim is still hashed:    rmrace: b passed dont_mount() and detach_mounts(), sleeping   T2: move_mount(S, /tmp/plcant/x, BENEATH) = 0 errno 0 ()   T1: rmdir(/tmp/plcant/d/b) = 0 errno 0       109 107 0:61 /d/b//deleted /tmp/plcant/x rw,relatime - tmpfs tmpfs rw       108 109 0:63 / /tmp/plcant/x rw,relatime - tmpfs T rw  A bind mount of the directory that's being removed is moved beneath an existing mount while the rmdir() is located between the two calls. The mount ends up on the removed directory and nothing will ever detach it.  Check cant_mount() in d_set_mounted() as well. dont_mount() raises the flag under d_lock before detach_mounts() runs so either the mountpoint is set first and detach_mounts() finds the mount or the flag is seen and the mount is refused.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98990",
                        "url": "https://ubuntu.com/security/CVE-2026-98990",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  namespace: check a submount for references right before unmounting it  shrink_submounts() and mark_mounts_for_expiry() first collect all the mounts they are allowed to unmount and then unmount them.  Whether a mount is busy is decided by propagate_mount_busy() on the tree. But unmounting the first mount changes the tree that the second one propagates into. propagate_umount() moves a surviving overmount off a copy it unmounts and mounts it where the copy was mounted. If that's where the propagated copy of the second victim is looked up the overmount becomes a candidate of the second umount_tree(). It's childless and so trim_one() commits it without looking at its reference count.  So a synchronous umount pulls out a busy mount that is in use somewhere else and marks it MNT_SYNC_UMOUNT while it has users:    umount2(/tmp/plshrink/p1, 0) = 0 errno 0   cwd is (unreachable)  The same two umounts requested one after the other fail with EBUSY. This needs a mount with MNT_SHRINKABLE, i.e., automounted submounts of NFS, AFS and CIFS or the tracefs mount below debugfs. Bind mounts inherit the flag.  Check each mount right before it is unmounted under the same hold of namespace_sem and mount_lock as the umount itself. Make sure that the algorithm stays linear.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99095",
                        "url": "https://ubuntu.com/security/CVE-2026-99095",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  drm/vc4: drain the hangcheck timer and works on V3D unbind  Nothing stops the hangcheck timer that submitted jobs arm, or the job_done_work that the render-done interrupt queues, at teardown: vc4_irq_disable() cancels only overflow_mem_work, and vc4_gem_destroy() runs from the drm-managed release, after vc4_v3d_unbind() has already uninstalled the V3D interrupt and cleared vc4->v3d. A timer still armed by then reads V3D registers through the NULL vc4->v3d pointer, and the late callbacks run on the vc4_dev embedding them after it has been freed.  Drain them in vc4_v3d_unbind(): shut the timer down and cancel reset_work before the interrupt is taken down, because its vc4_irq_reset() re-enables it, then flush job_done_work so that completions queued at teardown still release their jobs.  This issue was found by an in-house static analysis tool.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-26 15:16:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99006",
                        "url": "https://ubuntu.com/security/CVE-2026-99006",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  drm/i915/gem: Prevent overstepping exec array boundary  It is possible for eb_relocate_parse_slow() to call kvfree() on entries outside the original exec array during following scenario inside eb_relocate_parse_slow():  1) eb_copy_relocations() allocates as many as eb->buffer_count    copies for exec entries; 2) eb_parse() appends up to two VMAs, right after incrementing    eb->buffer_count; 3) cleanup under \"out\" label uses this incremented buffer_count    to release relocation pointers from exec array via kvfree(),    not from VMA array.  To amend this problem, ensure that relocation cleanup uses the original exec object count, excluding the VMAs appended by the command parser.  (cherry picked from commit 2a0158925fb943c7ba8f3216e2734952128defc9)",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99008",
                        "url": "https://ubuntu.com/security/CVE-2026-99008",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  Bluetooth: RFCOMM: Fix NULL tty_dev dereference in rfcomm_dev_shutdown  syzbot hit a NULL pointer dereference in rfcomm_dev_shutdown() when an RFCOMM tty is closed.  rfcomm_dev_add() puts the new device on rfcomm_dev_list first and only then registers the tty device and saves it in dev->tty_dev. If that registration fails, dev->tty_dev is never set at all. The device can be looked up in the meantime, so an open() of /dev/rfcommN gets through rfcomm_tty_install() and attaches to it. When that tty is closed again, rfcomm_dev_shutdown() uses dev->tty_dev without checking it:    Oops: general protection fault, probably for non-canonical address   KASAN: null-ptr-deref in range [0x0000000000000040-0x0000000000000047]   RIP: 0010:rfcomm_dev_shutdown+0x48/0xb0 net/bluetooth/rfcomm/tty.c:131   Call Trace:    tty_port_shutdown+0x1bf/0x220 drivers/tty/tty_port.c:372    tty_port_close+0x4e/0x150 drivers/tty/tty_port.c:705    tty_release+0x359/0x1670 drivers/tty/tty_io.c:1718    __fput+0x418/0xa50 fs/file_table.c:512  rfcomm_dev_destruct() already copes with a NULL dev->tty_dev. Add the same check to rfcomm_dev_shutdown(), so the tty device is only moved when it was actually registered.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99010",
                        "url": "https://ubuntu.com/security/CVE-2026-99010",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  Bluetooth: RFCOMM: free the skb when the DLC has no owner  rfcomm_recv_data() hands the skb to d->data_ready() and returns 0 without freeing it, so the callback owns the skb from that point on. The tty implementation frees it when the DLC has been detached from its device:    static void rfcomm_dev_data_ready(struct rfcomm_dlc *dlc,                                     struct sk_buff *skb)   {           struct rfcomm_dev *dev = dlc->owner;            if (!dev) {                   kfree_skb(skb);                   return;           }  The socket implementation returns without freeing it, and the skb is leaked.  A connected DLC can have no owner: rfcomm_sock_destruct() clears d->owner, while the DLC itself stays on the session until it is closed. Data frames that arrive in that window still find d->state == BT_CONNECTED in rfcomm_recv_data() and are handed to the callback, one leaked skb each.  The leak does not stop on its own either.  The remote runs out of credits only once RFCOMM_RX_THROTTLED is set, and for a socket the only place that sets it is rfcomm_sk_data_ready() itself, below the return. rfcomm_process_dlcs() keeps granting credits, so the remote keeps sending and the leak keeps growing.  Free the skb, as the tty side does.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99015",
                        "url": "https://ubuntu.com/security/CVE-2026-99015",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  Bluetooth: hci_sock: Serialize dead-device detachment  Rebinding an HCI socket after its controller is unregistered can race monitor control replay and crash the kernel. hci_sock_bind() clears hci_pi(sk)->hdev and drops the device reference under only the socket lock, whereas send_monitor_control_replay() holds hci_sk_list.lock for reading.  Replay can observe a non-NULL hdev, then bind can clear it and drop the last reference before create_monitor_ctrl_open() reads hdev->id. This can cause a NULL pointer dereference if the pointer is reloaded, or a use-after-free if the old pointer is retained.  The kernel reported:    KASAN: null-ptr-deref in range [0x0000000000000068-0x000000000000006f]   RIP: 0010:create_monitor_ctrl_open+0x579/0x800   Call Trace:    hci_sock_bind+0xd96/0x1190    __sys_bind+0x166/0x200    __x64_sys_bind+0x6d/0xb0    do_syscall_64+0xdd/0x4a0    entry_SYSCALL_64_after_hwframe+0x77/0x7f  The same missing serialization lets hci_send_to_sock() select a socket for the old device and queue its frame after bind has detached the socket or installed a new binding.  Take hci_sk_list.lock for writing when clearing the device pointer and resetting the socket state. This waits for existing replay and delivery readers to finish before detachment and prevents later readers from using the old binding. Keep hci_dev_put() outside the critical section because the final device release can sleep.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99022",
                        "url": "https://ubuntu.com/security/CVE-2026-99022",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  regulator: ltc3676: don't read the write-only HRST and CLIRQ registers  HRST (0x1e) and CLIRQ (0x1f) are write-only command strobes. Writing HRST triggers a hard reset of the chip and writing CLIRQ clears the interrupt; reading them returns nothing useful, and the read itself fires the command.  The result is that a plain register dump resets the board:    cat /sys/kernel/debug/regmap/2-003c/registers  walks every readable register, hits HRST, and the board reboots.  Split the callback back in two so HRST and CLIRQ stay writable but are no longer readable. The readable range is left unchanged (LTC3676_BUCK1 ... LTC3676_IRQSTAT).",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99025",
                        "url": "https://ubuntu.com/security/CVE-2026-99025",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  openvswitch: fix soft lockup in the netlink flow dump  A production compute node carrying a few thousand datapath flows hit a soft lockup inside a single netlink flow dump and panicked.  ovs_flow_cmd_dump() calls ovs_flow_stats_get() for every flow it emits, and that releases stats->lock with spin_unlock_bh() once per CPU that has touched the flow. Every release is a local_bh_enable(), and each one runs the pending softirq backlog in the dumping thread's own context.  The skb bounds the flows one callback emits, but not the softirq work it absorbs. On a CPU that carries the box's packet load the backlog refills as fast as it drains, so the dumping thread becomes that CPU's softirq engine. It never sleeps and it has no reschedule point, so under voluntary preemption nothing can take the CPU away from it: neither the ksoftirqd the kernel woke to take the work over, nor the stopper thread the softlockup detector dispatches to refresh its timestamp.  Hold BH off across the whole callback instead, the way ctnetlink_dump_table() does, so the nested spin_unlock_bh() stop draining softirqs. The loop already runs under rcu_read_lock() and cannot sleep. What it gives up is preemption under CONFIG_PREEMPT, since a BH-off region is not preemptible outside PREEMPT_RT. The region stays short: the skb caps the flows one callback emits, and empty buckets cost no skb space but are each visited once per dump, as the cursor only moves forward. The table grows on insert and shrinks only on flush, so the walk is bounded by the largest flow count the datapath has held. The softirq backlog the callback used to absorb has no bound at all.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99031",
                        "url": "https://ubuntu.com/security/CVE-2026-99031",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net: bridge: avoid recursive multicast port cleanup  br_multicast_sg_del_exclude_ports() removes automatically added STAR_EXCL port groups by calling br_multicast_del_pg(). For S,G entries, that deletion calls back into br_multicast_sg_del_exclude_ports(), so a large number of STAR_EXCL ports consumes one kernel stack frame per port and can hit the stack guard page.  Keep the complete port-group deletion path for cleanup, but suppress the S,G exclude-port cleanup while that helper is already walking the same entry. Normal deletion callers retain the existing behavior.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99032",
                        "url": "https://ubuntu.com/security/CVE-2026-99032",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net/smc: protect clcsock lifetime in smc_getname  smc_getname() dereferences smc->clcsock without holding clcsock_release_lock. Link-group termination can release the CLC socket through smc_close_active_abort() while the SMC socket is still open, for example after shutdown(SHUT_WR).  A getsockname() caller can load smc->clcsock, then the termination worker can clear the pointer and call sock_release() before the caller accesses clcsock->ops or invokes getname(). This causes a use-after-free; if the worker clears the pointer before the load, it causes a NULL dereference. The syscall's file reference keeps the SMC socket alive but does not prevent asynchronous release of its CLC socket.  KASAN reported the following with test-only timing instrumentation:    BUG: KASAN: slab-use-after-free in smc_getname+0x19e/0x1b0   Read of size 8 at addr ffff888109abb4e0 by task poc/103   Call Trace:    smc_getname+0x19e/0x1b0    do_getsockname+0xe5/0x170    __sys_getsockname+0x8c/0x100    Allocated by task 95:    sock_alloc_inode+0x1e/0x280    sock_alloc+0x3d/0x240    __sock_create+0x7e/0x430    smc_create+0x121/0x240    Freed by task 0:    kmem_cache_free+0xcc/0x340    rcu_core+0x50a/0x1850    Last potentially related work creation:    evict+0x446/0x6c0    smc_clcsock_release+0xa8/0xd0    smc_close_active_abort+0x26a/0x3a0    __smc_lgr_terminate.part.0+0x137/0x2e0  Hold clcsock_release_lock across the pointer check and the getname() callback to serialize with smc_clcsock_release(). Return -EBADF if the CLC socket has already been released, preserving the existing peer state check and the callback's return value otherwise.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99033",
                        "url": "https://ubuntu.com/security/CVE-2026-99033",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net/packet: guard the ll header push in packet_rcv_spkt()  packet_rcv_spkt() restores the link layer header with  \tskb_push(skb, skb->data - skb_mac_header(skb));  That subtraction is only meaningful when the device actually has a link layer header.  packet_rcv() and tpacket_rcv() both wrap it in dev_has_header(), which is also the predicate the block comment at the top of the file states the restore in terms of; packet_rcv_spkt() does not.  commit d549699048b4 (\"net/packet: fix packet receive on L3 devices without visible hard header\") introduced the helper and changed the two call sites, and this one stayed behind.  A device without a visible ll header can leave skb->mac_header at the 0xFFFF sentinel that __alloc_skb() initialises it to.  A CAN skb does: init_can_skb() sets pkt_type and ip_summed but does not reset the headers, and commit 9f10374bb024 (\"can: remove private CAN skb headroom infrastructure\") dropped the skb_reset_*_header() calls that used to be there.  skb_mac_header() is then 0xFFFF, the length becomes a large negative number and skb_push() reports it through skb_under_panic() -- from softirq context, so it is a full system panic even with panic_on_oops=0:    skbuff: skb_under_panic: text:ffffffff8bd21bc1 len:-65455 put:-65471 head:... data:... tail:0x50 end:0x180 dev:can0   kernel BUG at net/core/skbuff.c:214!   RIP: 0010:skb_panic+0x50/0x60   Call Trace:    <IRQ>    skb_push+0x38/0x40    packet_rcv_spkt+0xe1/0x170    __netif_receive_skb_core.constprop.0+0x7e8/0xd30    ...   Kernel panic - not syncing: Fatal exception in interrupt  The socket type is reachable: packet_create() accepts SOCK_PACKET alongside SOCK_RAW and SOCK_DGRAM behind the same CAP_NET_RAW check, and neither the socket length nor a capability check keeps it away from a CAN interface.  The missing skb_reset_*_header() calls in init_can_skb() are a regression in their own right and are being fixed separately, but a packet socket should not turn a link layer that did not initialise its mac header into a kernel panic.  Guard the push the way the other two receive paths do.  Tested on v7.3-rc5 under QEMU with a slcan device on a pty, which is the driver RX path: vcan does not reproduce it, because can_send() resets the headers on the way out.  One SOCK_PACKET socket bound to can0 and one frame written into the line discipline panics an unpatched kernel with the trace above; the same image with this patch prints no panic and powers off normally.  Both kernels are this tree, defconfig plus CONFIG_CAN_SLCAN=y, differing only in this hunk.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99034",
                        "url": "https://ubuntu.com/security/CVE-2026-99034",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  mmc: sdhci-sprd: disable runtime PM on remove  sdhci_sprd_probe() enables runtime PM, while sdhci_sprd_remove() does not perform the corresponding runtime PM cleanup.  The probe failure path disables runtime PM before disabling the clocks, but the normal remove path directly disables clocks that are also managed by the runtime PM callbacks. If the device is runtime suspended, those clocks may already be disabled.  Resume the device before removal, disable runtime PM and drop the temporary runtime PM reference before disabling the clocks.  This issue was found by manual code inspection.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99035",
                        "url": "https://ubuntu.com/security/CVE-2026-99035",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  mmc: mtk-sd: Cancel request timeout work on remove  The driver queues req_timeout while a request is active. msdc_request_done() uses cancel_delayed_work(), which does not wait for a timeout callback that has already started.  The timeout callback calls mmc_request_done(), which wakes the request waiter, and then continues to use host->dev_comp and check the SDIO IRQ. During unbind, msdc_drv_remove() can return and the managed mmc_host can be freed before the callback finishes.  KASAN reported use-after-free accesses in msdc_request_done() and msdc_recheck_sdio_irq() in each of three unbind tests.  The same tests completed without a kernel diagnostic after this change.  Call cancel_delayed_work_sync() after mmc_remove_host() has stopped new requests and before the driver releases the host resources.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99037",
                        "url": "https://ubuntu.com/security/CVE-2026-99037",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  dm-crypt: reject the lmk IV mode with AEAD ciphers  A \"capi:\" table line that pairs an AEAD cipher with the lmk IV mode, for example \"capi:gcm(aes)-lmk\" with the integrity:28:aead option, causes an oops when it is loaded. lmk sets tfms_count to 64, but crypt_alloc_tfms_aead only allocates one transform, so crypt_setkey reads past the end of the tfms_aead array and calls crypto_aead_setkey on the values it finds there.  lmk exists for compatibility with Loop-AES, which uses CBC, so refuse it with an AEAD cipher rather than allocate 64 AEAD transforms. The check cannot go in crypt_iv_lmk_ctr with the other lmk checks, because the IV constructor runs after crypt_set_key.  Note that this is not a security bug because the memory corruption can only be triggered by root.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99038",
                        "url": "https://ubuntu.com/security/CVE-2026-99038",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  memstick: rtsx_usb_ms: complete requests after eject instead of dropping them  memstick_check() can pass its host->removing check just before rtsx_usb_ms_drv_remove() sets eject/removing. Its next request is then silently dropped: rtsx_usb_ms_request() skips schedule_work() once eject is set, and drv_remove's cancel_work_sync() can also cancel a queued handle_req before it picks the request up. Nobody completes card->mrq_complete.  Once memstick core waits for requests without a timeout (\"memstick: core: wait for request completion before freeing card\"), this hangs removal: memstick_check() never returns and memstick_remove_host() blocks in flush_workqueue():    INFO: task kworker/u10:3:65 blocked for more than 20 seconds.   Workqueue: kmemstick memstick_check    __wait_for_common    memstick_check    INFO: task kworker/1:1:33 blocked for more than 20 seconds.   Workqueue: usb_hub_wq hub_event    __flush_workqueue    memstick_remove_host    rtsx_usb_ms_drv_remove  Never drop a request. rtsx_usb_ms_request() always schedules handle_req, and handle_req fails requests with -ENOMEDIUM once eject is set, without touching the device. drv_remove flushes handle_req instead of cancelling it, and cancels it only after memstick_remove_host(), when no new request can arrive, so it cannot run on a freed host.  The host_mutex drain in drv_remove is removed: handle_req always leaves host->req NULL when it finishes, so the drain never had anything to do, and it would now race with handle_req.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99039",
                        "url": "https://ubuntu.com/security/CVE-2026-99039",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  memstick: core: wait for request completion before freeing card  In memstick_alloc_card() and memstick_set_rw_addr(), wait_for_completion_timeout() is used to wait for device identification and address configuration requests to complete.  The memstick subsystem does not provide an abort or cancellation callback in struct memstick_host for in-flight requests. If wait_for_completion_timeout() expires (for instance, when a USB transfer or command retry is delayed), memstick_alloc_card() returns an error and frees the memstick_dev structure via kfree(card).  However, the host controller driver (such as rtsx_usb_ms) is still running the request asynchronously in worker context. When the transfer eventually finishes, the driver writes into host->req->data, which points to memory inside the already freed card structure. This leads to a KASAN slab-use-after-free write:    BUG: KASAN: slab-use-after-free in ms_read_bytes+0x8fe/0x990   Write of size 1 at addr ffff88813c188079 by task kworker/1:5/5239   Workqueue: events rtsx_usb_ms_handle_req   Call Trace:    ms_read_bytes+0x8fe/0x990 drivers/memstick/host/rtsx_usb_ms.c:450    rtsx_usb_ms_issue_cmd drivers/memstick/host/rtsx_usb_ms.c:477 [inline]    rtsx_usb_ms_handle_req+0x557/0x1a00 drivers/memstick/host/rtsx_usb_ms.c:531    process_one_work+0xac7/0x1b10 kernel/workqueue.c:3396    worker_thread+0x5ef/0xe50 kernel/workqueue.c:3560    kthread+0x373/0x450 kernel/kthread.c:436    Allocated by task 1662:    memstick_alloc_card drivers/memstick/core/memstick.c:383 [inline]    memstick_check+0x2c1/0x10d0 drivers/memstick/core/memstick.c:452    process_one_work+0xac7/0x1b10 kernel/workqueue.c:3396    Freed by task 1662:    kfree+0x20c/0x650 mm/slub.c:6792    memstick_alloc_card drivers/memstick/core/memstick.c:420 [inline]    memstick_check+0x72b/0x10d0 drivers/memstick/core/memstick.c:452    process_one_work+0xac7/0x1b10 kernel/workqueue.c:3396  Host controller drivers (rtsx_usb_ms, jmb38x_ms, tifm_ms, r592) already implement their own hardware and bus timeouts, and callers in mspro_block and ms_block already rely on wait_for_completion() unconditionally.  Replace wait_for_completion_timeout() with wait_for_completion() in memstick_set_rw_addr() and memstick_alloc_card() so that the card structure is never freed while an asynchronous request is in flight.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99040",
                        "url": "https://ubuntu.com/security/CVE-2026-99040",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  KEYS: Fix add_key() race with keyring restriction  __key_create_or_update() snapshots keyring->restrict_link before taking the destination keyring's semaphore.  keyring_restrict() installs a restriction while holding that semaphore.  This allows a writer to observe no restriction, wait for the keyring owner to install a reject-all restriction and return successfully, and then link a key using the stale NULL snapshot.  The writer only needs write permission on the destination keyring.  Move the restrict_link read after __key_link_lock() and __key_link_begin().  The read and the subsequent restriction check are then serialized with restriction installation by keyring->sem.  The race was reproduced on v7.2.8 in 19 executions where restriction installation returned before the link completed.  All 19 linked the key despite the reject-all restriction.  With this change, 312 executions reached the same ordering and every add_key() call failed with -EPERM.  The issue was found by manual concurrency analysis assisted by AI-based analysis and independently verified with a QEMU reproducer and kernel instrumentation.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99045",
                        "url": "https://ubuntu.com/security/CVE-2026-99045",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ibmveth: h_free logical LAN on open-fail after register  ibmveth_open() registers the logical LAN, then allocates the RX buffer pools. A pool failure jumps to out_free_buffer_pools without h_free_logical_lan(), so PHYP still owns the buffer-list page when it is unmapped. request_irq() failure already issued the hypercall before taking the same label.  Move that h_free to the shared post-register unwind so both paths deregister before the buffer list is unmapped.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99049",
                        "url": "https://ubuntu.com/security/CVE-2026-99049",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  gpio: xilinx: fix runtime PM leak on request error path  pm_runtime_get_sync() leaves the usage counter incremented even when it fails, and xgpio_request() returns the error without dropping it.  gpiolib does not call ->free() when ->request() fails, so xgpio_free(), which holds the only matching pm_runtime_put(), never runs. The reference is leaked and the controller can no longer runtime-suspend, so its clock stays enabled.  Switch to pm_runtime_resume_and_get(), which only increments the usage counter on success.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99052",
                        "url": "https://ubuntu.com/security/CVE-2026-99052",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  selinux: preserve NATIVE_LABELS on already-initialized sb in set_mnt_opts  When an NFSv4 filesystem exported with security_label is mounted a second time, sget_fc() returns the existing superblock and nfs_get_root() calls security_sb_set_mnt_opts() again on it. Since the superblock is already SB_INITIALIZED, selinux_set_mnt_opts() takes an early exit without setting SECURITY_LSM_NATIVE_LABELS in *set_kern_flags. nfs_get_root() then sees kflags without SECURITY_LSM_NATIVE_LABELS set and clears NFS_CAP_SECURITY_LABEL on the shared nfs_server, silently disabling per-file labeling for both the new and the original mount.  Commit 3815a245b501 (\"security/selinux: fix SECURITY_LSM_NATIVE_LABELS on reused superblock\") fixed the same problem in selinux_sb_clone_mnt_opts().  The reused-superblock path for a plain second mount now goes through sb_set_mnt_opts rather than sb_clone_mnt_opts, so it needs the same treatment: on both SE_SBINITIALIZED early exits, set SECURITY_LSM_NATIVE_LABELS in *set_kern_flags when the superblock was already using SECURITY_FS_USE_NATVE.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99053",
                        "url": "https://ubuntu.com/security/CVE-2026-99053",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  tipc: hold a reference to nodes found by link name  tipc_node_find_by_name() returns a node after dropping its RCU read lock without taking a reference.  The LINK_SET, LINK_GET and LINK_RESET_STATS handlers then lock and access the node, racing with timer-driven cleanup of a down peer.  Generic netlink serialization does not exclude the node timer.  The following interleaving can leave a handler using a freed node:    CPU 0: find the node under RCU and release the node read lock   CPU 1: tipc_node_timeout() clears the links and unlinks the down node   CPU 1: drop the list and timer references, queuing tipc_node_free()   CPU 0: leave the RCU read-side critical section   CPU 1: complete the grace period and free the node   CPU 0: acquire the node lock through the stale pointer  LINK_SET also uses the node's media address after releasing the node lock, when passing queued packets to tipc_bearer_xmit().  KASAN on v7.3-rc5 reported:    BUG: KASAN: slab-use-after-free in _raw_read_lock_bh   Write of size 4 at addr ffff88807e06f008 by task poc/92   Call Trace:    _raw_read_lock_bh                 kernel/locking/spinlock.c:287    tipc_nl_node_set_link             net/tipc/node.c:2475    genl_family_rcv_msg_doit          net/netlink/genetlink.c:1114    genl_rcv_msg                      net/netlink/genetlink.c:1209    netlink_rcv_skb                   net/netlink/af_netlink.c:2575    Allocated by task 0:    tipc_node_create                  net/tipc/node.c:539    tipc_node_check_dest              net/tipc/node.c:1196    tipc_disc_rcv                     net/tipc/discover.c:252    Freed by task 92:    kfree                             mm/slub.c:6801    rcu_core                          kernel/rcu/tree.c:2919    Last potentially related work creation:    __call_rcu_common.constprop.0     kernel/rcu/tree.c:3181    tipc_node_timeout                 net/tipc/node.c:814  Acquire a reference to the selected node with kref_get_unless_zero() before leaving RCU, returning NULL if the node has already been released.  Release that reference on every caller exit after the last node access, including transmission in LINK_SET.  Keep the existing link lookup order and locking so concurrent link removal still takes the existing error paths.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99054",
                        "url": "https://ubuntu.com/security/CVE-2026-99054",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  tipc: destroy topsrv workqueues before closing connections  tipc_topsrv_stop() closed subscriber connections while the topology server's send and receive workqueues were still running. Socket callbacks and subscription events could then queue more work, and in-flight send/recv work could drop the last connection reference during the conn_idr walk.  That race produced several teardown failures: refcount_t addition on 0 from conn_get() on a connection whose release was blocked on idr_lock, a subsequent use-after-free in tipc_conn_close(), queue_work() on an already destroyed workqueue from the listener data-ready callback, and an RCU stall in tipc_topsrv_exit_net() while the walk spun under idr_lock.  Clear srv->listener under idr_lock so it acts as a shutdown flag, skip queue_work() once it is NULL, destroy the workqueues to flush in-flight work, and only then close the remaining connections. Refuse tipc_conn_lookup() after that flag is cleared, and drop idr_lock when the teardown walk finds no connection, so an in-flight subscription event cannot pin idr_in_use while the walk holds the lock.  v3 supersedes the narrower in-thread diff Tung Quang Nguyen posted on 2026-09-23. It keeps his teardown order and adds the lookup refusal and the empty-idr unlock.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99056",
                        "url": "https://ubuntu.com/security/CVE-2026-99056",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  strparser: make sure __strp_recv isn't running before tearing down the parser  The comment above strp_done() claims that if strp is stopped, strp_recv will no longer be called. That's only true if the caller has a mechanism (eg locking) to guarantee that strp_recv() calls that started before strp_stop() have completed by the time we call strp_done().  This adds a dummy lock_sock/release_sock pair to guarantee that any in-flight strp_recv() (which runs under either bh_lock_sock or lock_sock, depending if it's called from ->sk_data_ready or strp_work) has completed.  Only espintcp can be affected by this race condition, but this patch makes sure no future user of strp can have the bug.  This could crash on strp->sk (\"general mode\" of strp), but this mode has been here for 9 years and has never been used. It'll be gone soon, no point worrying about it.  Switch the stopped/paused/etc bits to u8's to avoid races between strp_stop() and strp_pause/unpause().  A reproducer has been published and turns the possible UAF into an exploit [1].",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99057",
                        "url": "https://ubuntu.com/security/CVE-2026-99057",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  xen/netfront: don't leak the skb when xennet_fill_frags() fails  When a response chain has more slots than fit in the skb's frags, xennet_fill_frags() returns an error and xennet_poll() jumps to its error path.  That path moves what's left on tmpq to errq to be freed, but the skb being filled was already dequeued from tmpq, so it's never freed.  Each chain that overflows leaks the skb and the pages attached to it as frags, and the backend decides how many slots it sends.  Put the skb back on tmpq before taking the error path, like the xennet_set_skb_gso() failure just above it does.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99058",
                        "url": "https://ubuntu.com/security/CVE-2026-99058",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  workqueue: Fix NULL current_pwq deref in chained work check  current_wq_worker() only tells us that %current is a kworker. It does not guarantee that the worker is currently executing a work item, as worker->current_pwq is populated only while process_one_work() is running the work function.  is_chained_work() can be reached while queueing on a draining or destroying workqueue. If a kworker outside work-item execution reaches that path, current_wq_worker() returns a worker but worker->current_pwq is NULL, and the chained-work test can fault before it emits the intended warning.  Guard the chained-work test with worker->current_pwq. A kworker without current_pwq is not executing work on the target workqueue, so the helper should return false and let the draining/destroying warning fire.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99059",
                        "url": "https://ubuntu.com/security/CVE-2026-99059",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wireguard: noise: reject response consumption after intermediate initiation  Two threads begin processing the identical response message, received twice. The first thread, A, runs. While it's running, the second one, B, gets partway through, and during that slow calculation, or even while blocking on down_write(), A completes and then also a handshake initiation that's already been queued up runs in thread C, which itself takes that same down_write(). The handshake initiation creation succeeds, and sets the state back to waiting-for-response, and calls up_write(), at which point thread B resumes, because either its finished its calculations or was finally allowed to acquire down_write(). Thread B then copies the state back to the peer, and begins a new session, using that state, which is the same session as the one made in thread A.  Thread A\t\t\tThread B\t\t\tThread C  down_read()  sA = handshake->state  memcpy(cA, handshake->crypto) up_read() if (sA != 1)  goto fail slow_crypto(cA) \t\t\t\tdown_read() \t\t\t\t sB = handshake->state \t\t\t\t memcpy(cB, handshake->crypto) \t\t\t\tup_read() \t\t\t\tif (sB != 1) \t\t\t\t goto fail \t\t\t\tslow_crypto(cB) down_write()  if (sA != handshake->state)   goto fail  memcpy(handshake->crypto, cA)  handshake->state = 2 up_write() down_write()  if (handshake->state != 2)   goto fail  derive_session(handshake->crypto) up_write() \t\t\t\t\t\t\t\tdown_write() \t\t\t\t\t\t\t\t slow_crypto(handshake->crypto) \t\t\t\t\t\t\t\t handshake->state = 1 \t\t\t\t\t\t\t\tup_write() \t\t\t\tdown_write() \t\t\t\t if (sB != handshake->state) \t\t\t\t   goto fail \t\t\t\t memcpy(handshake->crypto, cB) \t\t\t\t handshake->state = 2 \t\t\t\tup_write() \t\t\t\tdown_write() \t\t\t\t if (handshake->state != 2) \t\t\t\t  goto fail \t\t\t\t derive_session(handshake->crypto) \t\t\t\tup_write()  This seems basically impossible to hit in a meaningful way in practice, but ensure that it absolutely cannot happen by comparing the ephemeral private key that's on the stack with the latest one that the peer's handshake state has.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99061",
                        "url": "https://ubuntu.com/security/CVE-2026-99061",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: brcmfmac: fix P2P device removal race in brcmf_detach()  When the driver is removed while the user space process that created the P2P device (e.g. wpa_supplicant) is still exiting, the P2P device interface is removed twice and the kernel crashes.  The two paths are:   - wpa_supplicant, on exit, sends NL80211_CMD_DEL_INTERFACE for the P2P    device. nl80211_del_interface() holds RTNL and the wiphy mutex and    calls brcmf_p2p_del_vif(), which disables discovery and waits up to    1.5 s for BRCMF_E_IF_DEL. Then it calls brcmf_remove_interface(),    which unregisters the wdev and frees the vif and the ifp.   - brcmf_detach() sets the bus down, so BRCMF_E_IF_DEL never arrives,    and calls brcmf_remove_interface(ifp, false) for the same ifp.    brcmf_p2p_ifp_removed() reads ifp->vif and then blocks on    rtnl_lock(). When brcmf_p2p_del_vif() releases RTNL, it calls    cfg80211_unregister_wdev() on the wdev that was already unregistered    and freed.  The second list_del_rcu() of wdev->list faults on LIST_POISON2:    brcmfmac: brcmf_p2p_del_vif delete P2P vif   brcmfmac: brcmf_p2p_deinit_discovery enter   brcmfmac: brcmf_p2p_del_vif P2P: GO_NEG_PHASE status cleared   brcmfmac: brcmf_detach Enter   brcmfmac: brcmf_bus_change_state 1 -> 0   brcmfmac: brcmf_remove_interface Enter, bsscfgidx=1, ifidx=0   brcmfmac: brcmf_del_if Enter, bsscfgidx=1, ifidx=0   brcmfmac: brcmf_p2p_ifp_removed P2P: device interface removed   [1.5 s later, brcmf_p2p_del_vif() timed out]   brcmfmac: brcmf_remove_interface Enter, bsscfgidx=1, ifidx=0   brcmfmac: brcmf_del_if Enter, bsscfgidx=1, ifidx=0   brcmfmac: brcmf_p2p_ifp_removed P2P: device interface removed   Unable to handle kernel paging request at virtual address dead000000000122   Internal error: Oops: 96000044 [#1] PREEMPT_RT SMP   pc : _cfg80211_unregister_wdev+0x6c/0x264 [cfg80211]   Call trace:    _cfg80211_unregister_wdev+0x6c/0x264 [cfg80211]    cfg80211_unregister_wdev+0x10/0x1c [cfg80211]    brcmf_p2p_ifp_removed+0x84/0xb0 [brcmfmac]    brcmf_remove_interface+0x1f4/0x254 [brcmfmac]    brcmf_detach+0x88/0x180 [brcmfmac]    brcmf_sdio_remove+0x90/0x7b0 [brcmfmac]    brcmf_sdiod_remove+0x20/0xa0 [brcmfmac]    brcmf_ops_sdio_remove+0xbc/0x12c [brcmfmac]    sdio_bus_remove+0x38/0x144    device_release_driver_internal+0x1e8/0x2c0    device_release_driver+0x14/0x20    brcmf_sdio_bus_remove+0x2c/0x40 [brcmfmac]    brcmf_fwvid_unregister_vendor+0xd8/0x170 [brcmfmac]    __exit_compat+0x18/0x418 [brcmfmac_cyw]    __arm64_sys_delete_module+0x1ac/0x244  The log was taken with debug=0x406 on an i.MX 8M Plus board with a CYW55513 (Sona IF513) on SDIO. The driver is the Ezurio backport of brcmfmac from v6.18.22 on a 5.4-rt kernel. The code involved is the same in mainline.  To reproduce:    1. Start wpa_supplicant on wlan0 and let it associate. It creates the      P2P device (iw dev shows \"type P2P-device\").   2. Stop wpa_supplicant and remove the driver without waiting for      wpa_supplicant to exit:         kill $(pidof wpa_supplicant)        rmmod brcmfmac_cyw brcmfmac  The crash is reproducible on that board.  For the interface without a netdev (the P2P device), take RTNL and the wiphy mutex in brcmf_detach() before reading iflist, and remove it with locked=true. If brcmf_p2p_del_vif() runs first, brcmf_detach() finds the slot empty. If brcmf_detach() runs first, nl80211 does not find the wdev any more. The interfaces with a netdev are removed as before, because brcmf_del_if() takes RTNL on its own for the primary interface.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99063",
                        "url": "https://ubuntu.com/security/CVE-2026-99063",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  dm ioctl: don't let data_start run past the buffer  struct dm_ioctl has seven bytes of trailing padding, so the smallest buffer userspace is allowed to ask for, offsetof(struct dm_ioctl, data), is seven bytes shorter than sizeof(struct dm_ioctl).  get_result_buffer() sets data_start to sizeof(struct dm_ioctl) without looking at how big the buffer actually is. Ask for the minimum and data_start ends up seven bytes past the end. Callers add it to data_size, and ctl_ioctl() copies that much back to userspace:    BUG: KASAN: slab-out-of-bounds in _copy_to_user+0xad/0xd0   Read of size 312 at addr ffff8880169e4c00 by task repro-dm/140    ctl_ioctl+0x5e3/0xcb0    dm_ctl_ioctl+0x25/0x40   allocated 305-byte region [ffff8880169e4c00, ffff8880169e4d31)  A DM_LIST_DEVICES with data_size set to 305 is enough to hit it, and the seven bytes that leak are whatever sat next to the allocation.  Clamp data_start to the buffer size.  Note that this is not a security bug because the out-of-bounds read can only be triggered by root.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99067",
                        "url": "https://ubuntu.com/security/CVE-2026-99067",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  btrfs: scrub: fix local_root reference leak in scrub_print_warning_inode()  When paths_from_inode() fails, scrub_print_warning_inode() jumps to err without dropping the reference taken by btrfs_get_fs_root(), leaking a reference to the root every time path resolution fails while printing scrub warnings.  Every other error and success path of the function drops the reference.  Drop the reference on the paths_from_inode() failure path too.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99070",
                        "url": "https://ubuntu.com/security/CVE-2026-99070",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ipv6: do not warn on route notification size race  fib6_info_hw_flags_set() sizes the skb with rt6_nlmsg_size() and later fills it with rt6_fill_node().  With nexthop compatibility mode enabled, a concurrent replacement can grow the group between these independent snapshots.  rt6_fill_node() can then legitimately return -EMSGSIZE, so the warning does not prove a sizing bug.  Remove the warning.  The existing error path still frees the skb and reports the error to listeners.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99071",
                        "url": "https://ubuntu.com/security/CVE-2026-99071",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ipv4: do not warn on route notification size race  Commit 680aea08e78c (\"net: ipv4: Emit notification when fib hardware flags are changed\") added asynchronous route notifications for hardware flag changes.  fib_alias_hw_flags_set() sizes the skb with fib_nlmsg_size() and later fills it with fib_dump_info() while holding only RCU.  With nexthop compatibility mode enabled, a concurrent replacement can grow the group between these independent snapshots.  fib_dump_info() can then legitimately return -EMSGSIZE, so the warning does not prove a sizing bug.  Remove the warning.  The existing error path still frees the skb and reports the error to listeners.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99072",
                        "url": "https://ubuntu.com/security/CVE-2026-99072",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ipv4: stop route notification sizing when nexthop group shrinks  Commit 680aea08e78c (\"net: ipv4: Emit notification when fib hardware flags are changed\") added an RCU-only fib_nlmsg_size() call for asynchronous hardware flag notifications.  fib_nlmsg_size() checks fib_info_num_path() before each iteration, then fib_info_nhc() independently reloads nh->nh_grp. If RTM_NEWNEXTHOP replaces a group with fewer paths between those loads, fib_info_nhc() returns NULL and fib_nexthop_nlmsg_size() dereferences it.  Stop sizing when the indexed path is absent. Nexthop groups are dense, so the current snapshot has no later path.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98686",
                        "url": "https://ubuntu.com/security/CVE-2026-98686",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  smb: client: discard post-EOF pagecache when extending a file via zero range  smb3_zero_range() removed the pagecache only for the range being zeroed, so when it extends the file the folio straddling the old EOF - which may hold data dirtied past EOF through an mmap - was never dropped and became visible as file content once the file was extended.  Lower the discard boundary to the smaller of the zero-range offset and the old EOF.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98700",
                        "url": "https://ubuntu.com/security/CVE-2026-98700",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: mac80211: set info->band for 802.3 encap offload frames  Unlike the 802.11 TX paths, ieee80211_8023_xmit() does not set info->band from the channel context on non-MLD interfaces. It stays at 0, so ieee80211_get_tx_rates() uses the wrong band for these frames.  Set it the same way as ieee80211_build_hdr(): drop the frame if there is no channel context, and leave the band at 0 on MLD interfaces.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98716",
                        "url": "https://ubuntu.com/security/CVE-2026-98716",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  KVM: SVM: Use the active VMCB's MSR bitmap when checking if MSR is intercepted  Use the MSR permission bitmap of the active VMCB instead of assuming that KVM is always using vmcb02's bitmap when L2 is active, as KVM uses msrpm02 if and only if L1 wants to intercept MSR accesses, i.e. if and only if KVM needs to merge msprm01 with msrpm12.  Don't bother tracking the virtual address of the bitmap that's being used, as __va() is cheap on x86, and caching the virtual address would introduce yet another source of potentially stale information.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99080",
                        "url": "https://ubuntu.com/security/CVE-2026-99080",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  fs: Free any excess xarray nodes in clear_inode()  For many years we've had a hard to hit leak of xarray nodes.  Hugh documented it well in commit 786b31121a2c.  Recently people and syzbot have found ways to force it to happen with madvise.  Rather than fix the leaks where they happen, just call xa_destroy() which has the side-effect of cycling the i_pages lock.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98709",
                        "url": "https://ubuntu.com/security/CVE-2026-98709",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: mac80211: count only matching reservations in reserved switch  ieee80211_vif_use_reserved_switch() validates a replacement by counting assigned links on ctx->replace_ctx and treating reservations too broadly. A link can still be assigned to the old channel context while holding a reservation that belongs to a different replacement operation.  That can make the current replacement appear complete too early. If another link finalizes first, the function can free the WILL_BE_REPLACED chanctx while the unmatched link and driver still use it, leading to a use-after-free in later beacon generation.  Require an in-place reservation to point at the current replacement context, and require the reserved and assigned contexts to be the matching replacement pair, before counting or moving the link.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98708",
                        "url": "https://ubuntu.com/security/CVE-2026-98708",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: mac80211: keep paired old chanctx alive  An in-place replacement keeps reciprocal replace_ctx pointers between the old WILL_BE_REPLACED chanctx and the new REPLACES_OTHER chanctx. However, the early free paths only consider assigned and reserved link users when deciding whether to free the old chanctx.  That lets the old chanctx be freed too early while the replacement partner still points back to it, either when the last assigned link is released or when that link successfully reassigns to another existing context. Later unreserve and switch-finalization paths can then follow a stale replace_ctx pointer.  Keep a paired old chanctx alive until the replacement pair has been torn down. Apply the same check to both __ieee80211_link_release_channel() and ieee80211_link_use_reserved_reassign(). If the replacement is later abandoned, ieee80211_link_unreserve_chanctx() already tears down the pairing before freeing the old chanctx once no users remain.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98752",
                        "url": "https://ubuntu.com/security/CVE-2026-98752",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  tty: port: fix tty_port_tty_vhangup() race  Drivers rely on tty_port_tty_vhangup() to synchronously hang up their ports before tearing down resources as part of deregistration (e.g. on physical disconnect).  If tty_port_tty_vhangup() races with another hangup it may however return before the port has been shut down. This is in turn can lead to use-after-free and NULL-pointer dereferences in racing ioctls (including a synchronous hangup) and in processing of racing asynchronous hangups (carrier loss).  Add the missing serialisation to tty_port_tty_vhangup() and tty_port_hangup() so that the former does not return until the port has been shut down also when there is a racing hangup.  Note that serial core does not use tty_port_hangup(), but it already holds the port mutex when clearing port->tty and shutting down the port in uart_hangup().",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-99081",
                        "url": "https://ubuntu.com/security/CVE-2026-99081",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  bnxt_en: fix DMA mapping length for padded small packets  Stefan Fleischmann reported Intel IOMMU DMA Read faults on BCM57412 NetXtreme-E NICs when transmitting packets on VLAN/macvlan interfaces:    DMAR: [DMA Read NO_PASID] Request device [18:00.0] fault addr 0xfc499000         [fault reason 0x06] PTE Read access is not set   bnxt_en 0000:18:00.0 eno1np0: Abandoning msg {0xb4 0x41a} len: 0 due to firmware status: 0x2000001   ...   NETDEV WATCHDOG: eno1np0 (bnxt_en): transmit queue 0 timed out  The fault address (0xfc499000) is on an exact 4KB page boundary, pointing to a DMA read buffer overrun.  In bnxt_start_xmit(), packets smaller than BNXT_MIN_PKT_SIZE (52 bytes), such as 42-byte untagged ARP frames, are padded:      if (length < BNXT_MIN_PKT_SIZE) {         pad = BNXT_MIN_PKT_SIZE - length;         if (skb_pad(skb, pad))             goto tx_kick_pending;         length = BNXT_MIN_PKT_SIZE;     }      mapping = dma_map_single(&pdev->dev, skb->data, len, DMA_TO_DEVICE);     ...     dma_unmap_len_set(tx_buf, len, len);  However, 'len' was initialized earlier to skb_headlen(skb) (e.g. 42 bytes) and is left unadjusted after padding. Consequently, dma_map_single() and dma_unmap_len_set() map and track only 42 bytes.  Later, the hardware TX buffer descriptor is programmed with the padded length:      txbd->tx_bd_len_flags_type =         cpu_to_le32(((len + pad) << TX_BD_LEN_SHIFT) | flags |                     TX_BD_FLAGS_PACKET_END);  The NIC DMA engine is thus instructed to read 52 bytes from a region where only 42 bytes were DMA-mapped. If skb->data ends near the boundary of a 4KB page (within 'pad' bytes of the next page), the hardware DMA read overruns into the unmapped adjacent page, triggering an IOMMU fault.  This issue was exposed after commit 447cbe95ebb9 (\"vlan: fix skb_under_panic and races when toggling HW VLAN offload\") because reserving extra VLAN headroom rounded LL_RESERVED_SPACE from 48 up to 64 bytes, shifting skb->data offsets and potentially causing small frames to land right against page boundaries.  Fix this by using skb_put_padto(skb, BNXT_MIN_PKT_SIZE) in bnxt_start_xmit(), before skb_shinfo(skb)->nr_frags is sampled, because padding might linearize the skb. This ensures skb->len and skb_headlen(skb) reflect the padded size so that dma_map_single() maps the full buffer and the descriptor length is consistent. This also removes the temporary 'pad' variable and masking logic.  The padding is done after the SW USO branch, otherwise bnxt_sw_udp_gso_xmit() would account the padding as UDP payload and send it in extra segments.  Note that SW USO segments are still not padded: with IPv4, a segment carrying less than 10 bytes of UDP payload (small gso_size, or a short last segment) is sent as a frame shorter than BNXT_MIN_PKT_SIZE. This is a separate issue, left for a followup patch.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98696",
                        "url": "https://ubuntu.com/security/CVE-2026-98696",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  USB: serial: fix driver deregistration order  USB serial driver modules register one driver for the USB bus and one or more drivers for the ports on the USB serial bus.  When unloading a driver module, the USB driver must be deregistered before the USB serial bus drivers so that I/O is stopped before unbinding the ports to avoid use-after-free in completion handlers accessing port data.  Note that the \"new_id\" attributes must first be removed to prevent new ids from being added and triggering a probe of the USB driver after it has been deregistered.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98705",
                        "url": "https://ubuntu.com/security/CVE-2026-98705",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: mac80211: account proxy paths against the mesh path limit  Proxy-path churn can drive the interface path counter negative and let later mesh path additions exceed MESH_MAX_MPATHS.  mesh_path_free_rcu() decrements the interface mpaths counter for entries from both the mesh and proxy path tables, but mpp_path_add() never reserves a slot in that counter. Removing or expiring a proxy path therefore returns a slot that was never charged.  mesh_path_add() uses the same counter to enforce MESH_MAX_MPATHS, so once it falls below the number of installed paths the limit no longer holds.  Reserve the shared quota before allocating a proxy path and release it on every unsuccessful addition. Mesh and proxy paths now share one 1024-entry budget, so mpp_path_add() can return -ENOSPC at that limit.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98722",
                        "url": "https://ubuntu.com/security/CVE-2026-98722",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  mtd: block2mtd: Fix divide error when erase_size is zero  The erase size is parsed from the \"block2mtd\" module parameter and can be set to zero. add_device() then evaluates          if (size % erase_size)  with a zero divisor, which triggers a divide error:  divide error: 0000 [#1] PREEMPT SMP PTI RIP: 0010:add_device drivers/mtd/devices/block2mtd.c:296 [inline] RIP: 0010:block2mtd_setup2+0x592/0xda0 drivers/mtd/devices/block2mtd.c:459 Call Trace: block2mtd_setup+0x27/0xe0 drivers/mtd/devices/block2mtd.c:476 param_attr_store+0x214/0x310 kernel/params.c:589 module_attr_store+0x65/0x90 kernel/params.c:904 kernfs_fop_write_iter+0x3a4/0x540 fs/kernfs/file.c:345 ...  Reject a zero erase size before performing the modulo operation so the existing \"erasesize must be a divisor of device size\" error path reports the invalid argument and frees the device.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98695",
                        "url": "https://ubuntu.com/security/CVE-2026-98695",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  USB: serial: fix ioctl hangup race  The tty ioctls can race with hangup and end up calling into a tty driver for a device that is already gone or powered down.  Serialise the callbacks using the tty port mutex and add the missing checks to make sure the port has not been hung up before accessing port driver data or hardware.  This specifically avoids dereferencing a NULL-pointer if a device is disconnected during lengthy break signalling.  Note that TIOCGICOUNT and TIOCMIWAIT do not access port driver data or hardware and are therefore not affected by the race.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98694",
                        "url": "https://ubuntu.com/security/CVE-2026-98694",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  thunderbolt: Fix KASAN reported use-after-free when request is canceled  Alan reported that when doing stress testing sometimes KASAN notices use-after-free during control channel operation (stripped down keeping the relevant parts):   BUG: KASAN: slab-use-after-free in tb_cfg_request_sync+0x240/0x250 [thunderbolt]  Read of size 24 at addr ffff88811067f290 by task kworker/u40:2/1760   <TASK>   tb_cfg_request_sync+0x240/0x250 [thunderbolt]   tb_cfg_read_raw+0x367/0x510 [thunderbolt]   tb_cfg_read+0xec/0x240 [thunderbolt]   tb_port_get_link_generation+0x258/0x420 [thunderbolt]   tb_usb3_consumed_bandwidth+0x1c1/0x2c0 [thunderbolt]   tb_tunnel_consumed_bandwidth+0xfd/0x910 [thunderbolt]   tb_available_bandwidth+0x5f2/0xeb0 [thunderbolt]   tb_recalc_estimated_bandwidth+0x2a0/0x1bc0 [thunderbolt]   tb_handle_dp_bandwidth_request+0x1897/0x5e20 [thunderbolt]   process_one_work+0x675/0x1230   worker_thread+0x5e6/0xf70   kthread+0x365/0x470   ret_from_fork+0x54d/0x710   ret_from_fork_asm+0x1a/0x30   </TASK>   Allocated by task 1760:   __kmalloc_cache_noprof+0x1ee/0x550   tb_cfg_read_raw+0x1d3/0x510 [thunderbolt]   tb_cfg_read+0xec/0x240 [thunderbolt]   tb_port_get_link_generation+0x258/0x420 [thunderbolt]   tb_usb3_consumed_bandwidth+0x1c1/0x2c0 [thunderbolt]   tb_tunnel_consumed_bandwidth+0xfd/0x910 [thunderbolt]   tb_available_bandwidth+0x5f2/0xeb0 [thunderbolt]   tb_recalc_estimated_bandwidth+0x2a0/0x1bc0 [thunderbolt]   tb_handle_dp_bandwidth_request+0x1897/0x5e20 [thunderbolt]   process_one_work+0x675/0x1230   worker_thread+0x5e6/0xf70   kthread+0x365/0x470   ret_from_fork+0x54d/0x710   ret_from_fork_asm+0x1a/0x30   Freed by task 926:   kfree+0x18f/0x4a0   tb_cfg_request_put+0xb7/0xe0 [thunderbolt]   tb_cfg_request_work+0x82/0x120 [thunderbolt]   process_one_work+0x675/0x1230   worker_thread+0x5e6/0xf70   kthread+0x365/0x470   ret_from_fork+0x54d/0x710   ret_from_fork_asm+0x1a/0x30   Second to last potentially related work creation:   __queue_work+0x575/0xd00   queue_work_on+0x77/0x80   tb_cfg_request_cancel+0xc7/0x260 [thunderbolt]   tb_cfg_request_sync+0x1f6/0x250 [thunderbolt]   tb_cfg_read_raw+0x367/0x510 [thunderbolt]   tb_cfg_read+0xec/0x240 [thunderbolt]   tb_port_get_link_generation+0x258/0x420 [thunderbolt]   tb_usb3_consumed_bandwidth+0x1c1/0x2c0 [thunderbolt]   tb_tunnel_consumed_bandwidth+0xfd/0x910 [thunderbolt]   tb_available_bandwidth+0x5f2/0xeb0 [thunderbolt]   tb_recalc_estimated_bandwidth+0x2a0/0x1bc0 [thunderbolt]   tb_handle_dp_bandwidth_request+0x1897/0x5e20 [thunderbolt]   process_one_work+0x675/0x1230   worker_thread+0x5e6/0xf70   kthread+0x365/0x470   ret_from_fork+0x54d/0x710   ret_from_fork_asm+0x1a/0x30  The last stack trace is helpful because it shows that we are cancelling a request and looking at tb_cfg_request_cancel() what might happen is that tb_cfg_request_work() completes right before tb_cfg_request_cancel() starts and because of this it will call schedule_work() queueing the same work to run again. However, it is already removed from the request_queue and reference count is dropped so when tb_cfg_request_work() triggers again it will access memory that is already released.  Fix this so that we first make sure a cancelled request is not handed away from tb_cfg_request_find() or scheduled to run. Then instead of relying on the worker to clean up the request we will do it in tb_cfg_request_cancel() after the work is canceled from running. Make tb_cfg_request_dequeue() release the request only if it was actually removed from the queue.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98704",
                        "url": "https://ubuntu.com/security/CVE-2026-98704",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: mac80211: keep fallback association elements alive  Associating to a non-transmitted MBSSID profile reads freed memory while determining the operating channel and applying HT capabilities.  When an association response omits WMM, HT, or VHT information, ieee80211_assoc_config_link() parses the cached BSS IEs and copies the missing element pointers out of that fallback parse. For a non-transmitted MBSSID profile those pointers refer to merged-profile storage owned by the parse object, and the fallback block frees that object at its end. The copied pointers are used afterwards to determine the operating channel, configure bandwidth, and apply HT capabilities.  Keep the fallback parse result alive until association setup finishes.  [reorder variable declaration]",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98707",
                        "url": "https://ubuntu.com/security/CVE-2026-98707",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: mac80211: shut down RX BA session timer on teardown  Tearing down an RX BA session can leave the session timer queued on a freed tid_rx. Later timer-wheel processing and the timer callback itself then run against freed memory.  An RX BAR handler can dereference tid_rx under RCU before teardown unpublishes it and stay in its read-side critical section while teardown deletes the session timer. The stale handler can then rearm the timer after timer_delete_sync() returns and before the RCU callback frees tid_rx.  Use timer_shutdown_sync() so rearm attempts become ineffective once teardown starts. Keep reorder_timer unchanged: teardown marks the session removed under reorder_lock and its release path checks that state before rearming. session_timer has no equivalent guard because ieee80211_rx_h_ctrl() rearms it before taking reorder_lock.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98749",
                        "url": "https://ubuntu.com/security/CVE-2026-98749",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  tty: serial: max3100: shut down timer before freeing port  max3100_shutdown() stops the polling timer but returns early during system suspend. If the SPI device is unbound before resume, the serial core does not call max3100_shutdown() again, so max3100_remove() frees the port while the timer remains armed. max3100_timeout() may then access the freed port and re-arm the timer.  Add final timer teardown to max3100_remove() and use timer_shutdown_sync() to prevent a racing callback from re-arming it. Also free the IRQ and destroy the workqueue there before freeing the port. Keep timer_delete_sync() in max3100_shutdown() so that a subsequent open() can re-arm the timer.  The workqueue is created before request_irq() and destroyed on both request_irq() failure and normal shutdown. Its presence at remove thus identifies the IRQ left registered when suspend bypasses shutdown.  Free the IRQ before destroying the workqueue, in both max3100_shutdown() and max3100_remove(), and cancel the pending work in between. free_irq() waits for a running interrupt handler to finish and no new handler can start afterwards, so a racing handler cannot queue work on a workqueue that is being destroyed; the force_end_work check in max3100_dowork() only narrows that window, as a handler delayed between the check and queue_work() could still run after the teardown has cleared the workqueue pointer. Cancelling the work also keeps destroy_workqueue() from waiting on a queued work item in case remove() ever runs while the freezable workqueue is still frozen, e.g. device removal during the resume window, before workqueues are thawed.  This issue was found by an in-house static analysis tool.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98751",
                        "url": "https://ubuntu.com/security/CVE-2026-98751",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  tty: abort break signalling on hangup  The break ioctls can race with hangup and end up calling into a tty driver for a device that is already gone or powered down.  Drivers must handle this race, but TCSBRK and TCSBRKP should still be aborted to avoid calling back into the driver after a user-controlled timeout (possibly even after the tty has been reopened).  Note that drivers should disable any break state on shutdown so just return on hangup (calling break_ctl() again is racy and will most likely fail for drivers handling the race).",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98753",
                        "url": "https://ubuntu.com/security/CVE-2026-98753",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  tty: tty_port: restore TTY_IO_ERROR on activation failure  Make sure to restore the TTY_IO_ERROR flag if activation fails to prevent I/O attempts on a port that is gone or powered down.  This specifically avoids issues like kernel panic due to unclocked accesses or NULL-pointer dereferences when accessing powered down or deregistered ports when a TTY ioctl races with hangup and open.  Note that the flag is set again in tty_port_close() but not restoring it on activation failure leaves a window where drivers fail to handle the ioctl-hangup race.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98762",
                        "url": "https://ubuntu.com/security/CVE-2026-98762",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  USB: dwc2: shut down wakeup timer before freeing HCD state  dwc2_wakeup_detected() accesses the DWC2 host state and can rearm the wakeup timer.  dwc2_hcd_free() currently deletes the timer only after freeing host-owned state, and timer_delete() does not synchronize a callback or prevent it from being queued again.  Stop and shut down the timer in dwc2_hcd_release(), before the HCD resources are freed.  This covers both the HCD initialization error path and normal HCD removal.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98784",
                        "url": "https://ubuntu.com/security/CVE-2026-98784",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  drm/amdgpu/gfx6: fix firmware leak on teardown  The firmware requested in gfx_v6_0_init_microcode() is not released when the GFX block is torn down, leaking the firmware resources.  Add gfx_v6_0_free_microcode() and call it from gfx_v6_0_sw_fini() to release the PFP, ME, CE and RLC firmware.  (cherry picked from commit 386e81346f95ab0be5a82c5535de932e7a456924)",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98779",
                        "url": "https://ubuntu.com/security/CVE-2026-98779",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  drm/amdgpu: fix ACP MFD device leak on init failure  acp_hw_init() registers ACP child devices with mfd_add_devices() before attaching them to the ACP power domain and initializing the hardware.  If attaching a child to the power domain fails, or if the ACP reset or clock enable operation times out, the failure path frees only the source cell, resource, and platform-data allocations. The child platform devices already registered by mfd_add_devices() remain registered and are never released.  Remove the children from the power domain and unregister the MFD devices on failures that occur after mfd_add_devices() succeeds. Keep mfd_add_devices() failures on the existing cleanup path since the MFD core already rolls back partially registered children itself.  The issue was identified by a static analysis tool I developed and confirmed by manual review.  (cherry picked from commit 63da68d6a2279ec945581c990c5a59a5ae8b5560)",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98742",
                        "url": "https://ubuntu.com/security/CVE-2026-98742",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ALSA: seq: Serialize compat port-info ioctls  The native sequencer ioctl path serializes handler calls with client->ioctl_mutex, but the translated port-info compat path invokes the same handlers through snd_seq_kernel_client_ctl() without taking that mutex.  This lets concurrent compat CREATE_PORT requests pass the port-count check before any request reaches the serialized insertion. The computed integer port index can then exceed the address field range and wrap to an existing index. Subsequent subscriber teardown can resolve the duplicate address to the wrong port and access a freed subscriber.  Take ioctl_mutex while dispatching converted port-info requests, matching the native ioctl path. All translated port-info commands share this helper, so their accesses to the client port state are serialized as well.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98655",
                        "url": "https://ubuntu.com/security/CVE-2026-98655",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  perf: Require kernel access for text poke events  Perf events with exclude_kernel=1 can be opened without kernel perf access. However, exclude_kernel does not suppress text-poke sideband records. Every PERF_RECORD_TEXT_POKE is marked PERF_RECORD_MISC_KERNEL and contains a raw kernel instruction address.  An unprivileged task can therefore open and mmap a task-local software event with text_poke=1. Both opening a count-only tracepoint event and configuring UDP GRO for ESP-in-UDP cause updates to inline static calls; the observer receives the relocated addresses of the modified instructions. For a known kernel image, any such address reveals the runtime kernel text base despite KASLR.  Call perf_allow_kernel() whenever attr.text_poke is set, regardless of exclude_kernel. Events that neither monitor kernel execution nor request text-poke records retain their existing permissions.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98750",
                        "url": "https://ubuntu.com/security/CVE-2026-98750",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  tty: fix saved termios reset race  Resetting saved termios state on device registration is needed where a minor number can be reused for an entirely different device and where the old settings may prevent the port from even being opened (e.g. when CLOCAL is not set).  Not all TTY drivers guarantee that the minor number is no longer in use when registering devices however, something which can lead to a use-after-free when closing a TTY (and saving its termios) races with re-registration.  Add a new TTY_DRIVER_RESET_SAVED_TERMIOS flag to request that any saved termios state is reset on registration and only set it for drivers that make sure that the minor number is no longer in use.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-89638",
                        "url": "https://ubuntu.com/security/CVE-2026-89638",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  smb: client: clear setuid/setgid bit on write with cifsacl/modefromsid/posix extensions  When a file has the setuid or setgid bit set and is written to, the VFS strips those bits and issues a setattr with ATTR_KILL_SUID/ATTR_KILL_SGID together with an ATTR_MODE carrying the already-cleared mode.  Both cifs_setattr_unix() and cifs_setattr_nounix() unconditionally dropped ATTR_MODE in that case:  \t/* skip mode change if it's just for clearing setuid/setgid */ \tif (attrs->ia_valid & (ATTR_KILL_SUID|ATTR_KILL_SGID)) \t\tattrs->ia_valid &= ~ATTR_MODE;  This is fine for the default mount, where the mode is only emulated via the DOS read-only attribute and cannot represent the setuid/setgid bits anyway.  However, with the \"cifsacl\" or \"modefromsid\" mount options the mode is stored on the server through an ACL (id_mode_to_cifs_acl()), with the SMB3.1.1 POSIX extensions the mode is sent to the server directly, and with the SMB1 Unix extensions (cifs_setattr_unix) the mode is sent via CIFSSMBUnixSetPathInfo().  In all those cases dropping ATTR_MODE means the cleared mode is never pushed to the server, so the setuid/setgid bit survives the write.  This is a security issue: on local filesystems the setuid bit is stripped when a file is written, but over these cifs.ko mounts the bit persists on the server, potentially allowing an unexpected privilege escalation on subsequent execution.  Fix this in two places:    1. cifs_setattr_nounix(): only take the \"skip mode change\" shortcut      when the mode is emulated via the DOS read-only attribute (i.e.      neither cifsacl/modefromsid nor the SMB3.1.1 POSIX extensions are      in effect), so that the cleared mode is propagated to the server      in the ACL / POSIX cases.    2. cifs_setattr_unix(): this function is only called when Unix      extensions are in effect, so the mode is always stored on the      server.  Remove the shortcut entirely so that the cleared mode is      always pushed.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-09-11 20:19:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98375",
                        "url": "https://ubuntu.com/security/CVE-2026-98375",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  xen/netfront: drop RX packets with a short Ethernet header  handle_incoming_queue() pulls pull_to bytes into the head before calling eth_type_trans().  pull_to is the length of the first RX slot, capped at RX_COPY_THRESHOLD, and that length comes from the backend. Nothing checks it against ETH_HLEN.  If the first slot is shorter than ETH_HLEN and more slots follow, the head ends up shorter than an Ethernet header while skb->len is longer, and eth_type_trans() BUG()s in __skb_pull().  If the whole packet is shorter than ETH_HLEN, eth_type_trans() reads the header past the end of the data instead.  Pull at least ETH_HLEN, and drop the packet if that fails, which also drops packets too short to hold an Ethernet header.  This also checks the return value of the pull, which was ignored.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-09 08:16:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-89738",
                        "url": "https://ubuntu.com/security/CVE-2026-89738",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  usb: gadget: at91_udc: drain polled-VBUS timer/work before udc is freed  In polled-VBUS mode (board.vbus_pin && board.vbus_polled), probe arms a self-restarting cycle: at91_vbus_timer() schedules vbus_timer_work, and at91_vbus_timer_work() calls at91_vbus_update() and re-arms the timer via mod_timer(). Both recover the same udc through container_of and dereference it on every iteration.  Neither teardown path cancels this cycle. udc is devm-allocated, so it is freed after at91udc_remove() returns, and is likewise freed when probe fails and devres runs. A timer callback or work item that is pending or running at either point dereferences the freed udc.  Add at91_udc_shutdown_vbus_timer() and call it from at91udc_remove() and from the usb_add_gadget_udc() failure path in probe; the remaining probe error paths fail before the timer is armed. timer_shutdown_sync() waits for a running callback and clears timer->function, which makes the work handler's mod_timer() a permanent no-op; cancel_work_sync() then drains any pending or running work whose re-arm attempt now does nothing. The timer must be shut down first, since cancelling the work alone would let the timer re-queue it. The guard mirrors probe: in IRQ mode the timer and work_struct are never initialized.  This does not require a fault; a normal driver unbind can interleave with an already queued work item.  This issue was found by an in-house static analysis tool.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-09-11 20:20:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-89740",
                        "url": "https://ubuntu.com/security/CVE-2026-89740",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  serial: imx: serialize imx_uart_ports[] lifetime  imx_uart_probe() publishes its devm-allocated port in imx_uart_ports[] before uart_add_one_port() because console setup uses the table. The entry is not cleared when adding the port fails or after removal, leaving a dangling pointer.  A sibling probe can register the shared console through that stale entry. This was reproduced under KASAN on QEMU mcimx6ul-evk by unbinding a sibling UART, unbinding the console UART and rebinding the sibling.  Keep the entry valid through uart_remove_one_port(), then clear it. Protect port addition and removal together with their table updates so sibling operations cannot interleave. Reject an occupied slot rather than clobbering an active port during a duplicate-line probe.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-09-11 20:20:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-74341",
                        "url": "https://ubuntu.com/security/CVE-2026-74341",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: wcn36xx: fix heap overflow from oversized firmware HAL response  The firmware response dispatcher copies all synchronous HAL responses into the 4096-byte hal_buf without validating the response length. A response exceeding WCN36XX_HAL_BUF_SIZE causes a heap buffer overflow with firmware-controlled content.  Add a bounds check on the response length.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-08-15 06:22:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-74406",
                        "url": "https://ubuntu.com/security/CVE-2026-74406",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  vxlan: Fix potential null-ptr-deref in vxlan_gro_prepare_receive().  udp_tunnel_sock_release() could set sk->sk_user_data to NULL while vxlan_gro_prepare_receive() is running.  Let's check if rcu_dereference_sk_user_data() is NULL after skb_gro_remcsum_init().",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-08-15 06:22:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-46265",
                        "url": "https://ubuntu.com/security/CVE-2026-46265",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  RDMA/hns: Fix WQ_MEM_RECLAIM warning  When sunrpc is used, if a reset triggered, our wq may lead the following trace:  workqueue: WQ_MEM_RECLAIM xprtiod:xprt_rdma_connect_worker [rpcrdma] is flushing !WQ_MEM_RECLAIM hns_roce_irq_workq:flush_work_handle [hns_roce_hw_v2] WARNING: CPU: 0 PID: 8250 at kernel/workqueue.c:2644 check_flush_dependency+0xe0/0x144 Call trace:   check_flush_dependency+0xe0/0x144   start_flush_work.constprop.0+0x1d0/0x2f0   __flush_work.isra.0+0x40/0xb0   flush_work+0x14/0x30   hns_roce_v2_destroy_qp+0xac/0x1e0 [hns_roce_hw_v2]   ib_destroy_qp_user+0x9c/0x2b4   rdma_destroy_qp+0x34/0xb0   rpcrdma_ep_destroy+0x28/0xcc [rpcrdma]   rpcrdma_ep_put+0x74/0xb4 [rpcrdma]   rpcrdma_xprt_disconnect+0x1d8/0x260 [rpcrdma]   xprt_rdma_connect_worker+0xc0/0x120 [rpcrdma]   process_one_work+0x1cc/0x4d0   worker_thread+0x154/0x414   kthread+0x104/0x144   ret_from_fork+0x10/0x18  Since QP destruction frees memory, this wq should have the WQ_MEM_RECLAIM.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-06-03 18:16:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98681",
                        "url": "https://ubuntu.com/security/CVE-2026-98681",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  smb: client: split cifsFileInfo bitfields to avoid shared-byte RMW races  The invalidHandle, swapfile, oplock_break_cancelled, offload, and status_file_deleted fields are stored in the same bitfield byte in struct cifsFileInfo, but are updated in different code paths that may run simultaneously, and are protected by different locks.  Since bitfield assignments generate byte-level read-modify-write operations, a modification to one flag can overwrite a concurrent modification to another flag.  To avoid these races, convert these flags from a bitfield to separate bool fields.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-89539",
                        "url": "https://ubuntu.com/security/CVE-2026-89539",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  SUNRPC: reject duplicate CREDS_VALUE options  gssx_dec_option_array() walks the wire-supplied option array and, for every entry whose name matches CREDS_VALUE, calls gssx_dec_linux_creds() on the same struct svc_cred. That helper unconditionally installs a fresh groups_alloc() result into creds->cr_group_info without releasing whatever pointer was already there:      for (i = 0; i < count; i++) {         ... decode name ...         if (length == sizeof(CREDS_VALUE) &&             memcmp(p, CREDS_VALUE, sizeof(CREDS_VALUE)) == 0) {             err = gssx_dec_linux_creds(xdr, creds);             ...         }     }  A reply that carries two CREDS_VALUE entries therefore overwrites cr_group_info on the second iteration and orphans the group_info allocated by the first call. The earlier free_creds path only releases the last cr_group_info via free_svc_cred(), so the first allocation's refcount stays at one and its kvmalloc-backed storage is leaked. No in-tree caller of gssp_accept_sec_context_upcall() expects more than one CREDS_VALUE per reply.  Fix by tracking whether a CREDS_VALUE option has already been decoded and returning -EINVAL on any subsequent match, so the free_creds path releases the single group_info that was installed.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-09-11 20:19:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-93179",
                        "url": "https://ubuntu.com/security/CVE-2026-93179",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  drm/amd/powerplay: fix VoltageObjectInfo zero-stride loop and OOB read  Reject voltage objects whose usSize is smaller than the header or would advance the cursor past the table end, preventing an infinite loop or heap OOB read when the VBIOS supplies a malformed VoltageObjectInfo table.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-09-17 17:18:00 UTC"
                    },
                    {
                        "cve": "CVE-2023-52561",
                        "url": "https://ubuntu.com/security/CVE-2023-52561",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  arm64: dts: qcom: sdm845-db845c: Mark cont splash memory region as reserved  Adding a reserved memory region for the framebuffer memory (the splash memory region set up by the bootloader).  It fixes a kernel panic (arm-smmu: Unhandled context fault at this particular memory region) reported on DB845c running v5.10.y.",
                        "cve_priority": "low",
                        "cve_public_date": "2024-03-02 22:15:00 UTC"
                    },
                    {
                        "cve": "CVE-2023-53651",
                        "url": "https://ubuntu.com/security/CVE-2023-53651",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  Input: exc3000 - properly stop timer on shutdown  We need to stop the timer on driver unbind or probe failures, otherwise we get UAF/Oops.",
                        "cve_priority": "low",
                        "cve_public_date": "2025-10-07 16:15:00 UTC"
                    },
                    {
                        "cve": "CVE-2023-53733",
                        "url": "https://ubuntu.com/security/CVE-2023-53733",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net: sched: cls_u32: Undo tcf_bind_filter if u32_replace_hw_knode  When u32_replace_hw_knode fails, we need to undo the tcf_bind_filter operation done at u32_set_parms.",
                        "cve_priority": "medium",
                        "cve_public_date": "2025-10-24 12:15:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98657",
                        "url": "https://ubuntu.com/security/CVE-2026-98657",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  iio: proximity: pulsedlight: fix iio_device left registered on PM setup failure  pm_runtime_set_active() failing in probe() jumps to error_unreg_buffer, which only calls iio_triggered_buffer_cleanup() -- it does not undo the iio_device_register() that already succeeded a few lines above. probe() then returns the error, the devm-managed indio_dev is freed, but the iio core still has it registered: the sysfs/chardev nodes stay live and point at freed memory.  Add an error_unreg_dev label that unregisters the iio device before falling through to the existing buffer cleanup, mirroring the teardown order already used in lidar_remove().",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98662",
                        "url": "https://ubuntu.com/security/CVE-2026-98662",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  iio: light: gp2ap020a00f: drain irq_work after free_irq  The threaded IRQ handler queues data->work through irq_work_queue() so the trigger is polled from a per-CPU context.  free_irq() does not flush an irq_work the handler already queued, so after gp2ap020a00f_remove() returns that work may still run and call iio_trigger_poll() on data->trig, which the devm cleanup has already freed, causing a use-after-free.  Add irq_work_sync(&data->work) after free_irq() in remove() and in the probe error path, mirroring commit 78601726d4a5 (\"iio: trigger: sysfs: fix use-after-free on remove\").  Found by an in-house static analysis tool, confirmed by manual review.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98663",
                        "url": "https://ubuntu.com/security/CVE-2026-98663",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  iio: imu: adis16480: fix unprotected debugfs reads  The firmware_revision and firmware_date file operations are open coded and never call debugfs_file_get(), which debugfs_create_file_unsafe() requires. debugfs_remove_recursive() therefore does not wait for a read in progress, and unbind frees the iio_dev underneath it.  Use debugfs_create_file() instead.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98664",
                        "url": "https://ubuntu.com/security/CVE-2026-98664",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  iio: imu: adis16400: fix unprotected debugfs reads  adis16400_serial_number_fops is open coded and never calls debugfs_file_get(), so debugfs_remove_recursive() does not wait for a read in progress and unbind frees the iio_dev underneath it.  Commit ae1d37a9bb4b (\"iio: imu: adis16400: use DEFINE_DEBUGFS_ATTRIBUTE instead of DEFINE_SIMPLE_ATTRIBUTE\") converted product_id and flash_count to DEFINE_DEBUGFS_ATTRIBUTE, which protects itself, but moved all three files to debugfs_create_file_unsafe().  serial_number prints three registers as \"%.4x-%.4x-%.4x\" and DEFINE_DEBUGFS_ATTRIBUTE() formats a single u64, so it cannot be converted without changing what the file returns. adis16475 and adis16550 already use debugfs_create_file() for their open coded files. Use it here too.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98666",
                        "url": "https://ubuntu.com/security/CVE-2026-98666",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  iio: gyro: adis16136: fix unprotected debugfs reads  The serial_number file operations are open coded and never call debugfs_file_get(), which debugfs_create_file_unsafe() requires. debugfs_remove_recursive() therefore does not wait for a read in progress, and unbind frees the iio_dev underneath it.  Use debugfs_create_file() instead.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98671",
                        "url": "https://ubuntu.com/security/CVE-2026-98671",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  iio: adc: sun4i-gpadc-iio: clean up on thermal zone registration failure  If devm_thermal_of_zone_register() fails, probe returns without unregistering the IIO map array or disabling runtime PM.  Jump to err_map to release them.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98679",
                        "url": "https://ubuntu.com/security/CVE-2026-98679",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  iio: accel: kxcjk-1013: reject duplicate event disable  The IIO core does not filter duplicate writes to the event enable attribute. kxcjk1013_write_event_config() already ignores repeated enable requests, but a repeated disable request still calls kxcjk1013_set_power_state(data, false), dropping a runtime PM reference that was not acquired for this request. This can underflow the runtime PM usage count and trigger a \"Runtime PM usage count underflow\" warning.  Return early when the requested state already matches ev_enable_state.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98687",
                        "url": "https://ubuntu.com/security/CVE-2026-98687",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  thunderbolt: Reject oversized XDomain properties responses  tb_xdp_properties_request() allocates room for 45 data dwords in its 252-byte response buffer.  The XDomain length field is six bits wide, however, and a malicious peer can set it to 63.  After the fixed response fields are subtracted, the driver treats this as 48 data dwords.  Commit 322e93448d90 (\"thunderbolt: Clamp XDomain response data copy to allocation size\") only bounds the copy against data_len.  If data_len is at least 48, memcpy() reads 192 bytes from the 180-byte res->data array, causing a 12-byte heap out-of-bounds read.  Commit 4db2bd2ed478 (\"thunderbolt: Limit XDomain response copy to actual frame size\") limits the earlier copy but does not constrain this header-derived length.  Reject response data lengths that exceed the allocated source buffer before copying them into the assembled property block.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98697",
                        "url": "https://ubuntu.com/security/CVE-2026-98697",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  USB: serial: fix dynamic id driver deregistration race  Only free the dynamic ids after having deregistered the driver and removed the \"new_id\" attribute to avoid leaking any id added by a racing write to the attribute.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98698",
                        "url": "https://ubuntu.com/security/CVE-2026-98698",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: mac80211: handle empty FILS association request payload  fils_encrypt_assoc_req() accepts a (Re)Association Request frame whose last element is the FILS Session element.  crypt_len is then zero and aes_siv_encrypt() is called with an empty plaintext.  kmemdup() returns ZERO_SIZE_PTR for a zero-length allocation, so the unconditional sg_init_one() puts an invalid page into the scatterlist. With CONFIG_DEBUG_SG this triggers a kernel BUG in sg_set_buf(); without the debug check the bogus page is handed to the crypto backend.  AES-SIV is defined for empty plaintext and the S2V result is then the complete output, so handle this case before the CTR step, which has nothing to encrypt.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98701",
                        "url": "https://ubuntu.com/security/CVE-2026-98701",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: mac80211: release mesh path quota on failed additions  Repeated failed or duplicate mesh path additions can exhaust MESH_MAX_MPATHS while the path table holds fewer paths, which stops new paths to reachable destinations from being created.  mesh_path_add() reserves a slot before allocating and inserting a path. If allocation fails, the function returns without releasing the slot. If the rhashtable insertion reports an error or an existing destination, the function discards its candidate but retains the reservation. No new path is installed in any of these cases.  Release the reservation whenever the candidate is not installed.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98703",
                        "url": "https://ubuntu.com/security/CVE-2026-98703",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: mac80211: minstrel_ht: validate fixed rate index  The fixed_rate_idx debugfs file is a plain u32 attribute, so any value can be written to it.  minstrel_ht_update_stats() then copies the value into mi->max_tp_rate[] and mi->max_prob_rate, and minstrel_ht_set_rate() uses MI_RATE_GROUP()/MI_RATE_IDX() to index minstrel_mcs_groups[] (42 entries) and mi->groups[].rates[] (10 entries) with it.  Writing e.g. 65535 selects group 4095 and rate index 15, far outside both arrays.  The out-of-bounds entries are dereferenced and updated as struct minstrel_rate_stats (retry counts, etc.), so the invalid index corrupts adjacent kernel memory.  With CONFIG_UBSAN_BOUNDS the access is reported as an array-index-out-of-bounds in minstrel_ht_set_rate().  Only a valid group/rate pair, or U32_MAX to disable fixed rate processing, can be used safely, so reject any other value when the debugfs file is written.  The file is only reachable through a root-only debugfs mount, so this is not a privilege boundary.  The out-of-bounds access is still a bug that must not be reachable through a writable debugfs attribute.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98706",
                        "url": "https://ubuntu.com/security/CVE-2026-98706",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: mac80211: drain PS delivery work during station teardown  Removing an AP or mesh station can notify the driver and wake TXQs after the station has already been removed from the driver, and can update num_sta_ps and the power-save queues after station cleanup has purged them.  sta_deliver_ps_frames() tests sta->dead only before it starts delivery. A worker that passes that test can be delayed while teardown sets sta->dead and removes the station from the driver; when it resumes it still runs the full delivery.  The existing cancel_work_sync() sits near the end of __cleanup_single_sta(), after the final driver state transition and after PS accounting and queue purging, so it drains the worker only once the state it has to protect has already changed. Before commit d34ba2168a3c (\"mac80211: don't delay station destruction\") cleanup was deferred through the same ordered workqueue as the delivery work, which kept the two ordered.  Cancel the work after setting sta->dead and before moving the driver state, and move the existing cancellation to the start of __cleanup_single_sta(). The first drain closes the driver-lifetime window; driver callbacks during the remaining state transitions can still queue drv_deliver_wk through ieee80211_sta_block_awake(), so retain the second drain at the start of __cleanup_single_sta(). That drain also covers insertion failures, which reach cleanup without setting sta->dead.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98710",
                        "url": "https://ubuntu.com/security/CVE-2026-98710",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: iwlegacy: 3945: free EEPROM data on remove  il3945_pci_probe() calls il_eeprom_init(), which allocates memory for the EEPROM data. The probe failure paths release this allocation with il_eeprom_free(), but the remove path does not free it after a successful probe.  As a result, the EEPROM data is leaked when the PCI device is removed.  Free the EEPROM data in il3945_pci_remove() before releasing the mac80211 hardware structure.  This issue was found by manual code inspection.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98711",
                        "url": "https://ubuntu.com/security/CVE-2026-98711",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: cw1200: fix TX padding OOB read leaking heap data to device  The TX path rounds the transfer size up to the bus alignment (align_size(), up to 511 bytes for SDIO, 1 byte for SPI) but sends the padded length straight from the frame buffer, which has no room reserved for the padding.  cw1200_data_write() therefore reads past the end of the frame and the bus transfer carries those bytes to the device.  A bogus device can collect up to 511 bytes of kernel heap data per TX frame.  The RX path does not have this problem: it allocates the skb with the aligned length (alloc_len) before reading.  Compute the exact padding with the bus align_size() callback, make sure queued TX frames have tailroom for it, and zero the padding bytes before the transfer so nothing past the frame is exposed.  This is not expected to change driver behavior on most cases: frame contents and transfer sizes are unchanged, only the content of the padding bytes (previously undefined stale memory, now zero), which the device never reads since the WSM header carries the real frame length.  The skb expansion can only fail under memory exhaustion, in which case the frame is dropped like on the existing error paths of cw1200_tx().  Discovered by Atuin - Automated Vulnerability Discovery Engine.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98721",
                        "url": "https://ubuntu.com/security/CVE-2026-98721",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  mtd: rawnand: cadence: Initialize IRQ state before requesting IRQ  The Cadence NAND interrupt handler uses both the IRQ lock and completion object. Registering the IRQ before initializing them leaves a window in which a pending interrupt can access uninitialized synchronization state.  Initialize them before registering the handler.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98726",
                        "url": "https://ubuntu.com/security/CVE-2026-98726",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  nvme-multipath: fix underflow in ANA log bounds checks  The number of ANA groups advertised through Identify Controller sizes the ANA log buffer. The ANA log header and group descriptors independently supply the number of groups and namespace IDs to parse.  Both bounds checks subtract an untrusted object size from ana_log_size before comparing the current offset. If the object is larger than the buffer, the size_t subtraction underflows and lets the parser read beyond ana_log_buf.  Check the current offset before the first subtraction and compare each object size with the remaining buffer instead. This rejects inconsistent ANA data before dereferencing a truncated group descriptor or walking an oversized namespace ID array.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98856",
                        "url": "https://ubuntu.com/security/CVE-2026-98856",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  kprobes: Skip disarmed probes when checking optkprobe overlap  On x86, an optkprobe at A replaces five bytes with a jump. If a disabled probe B is at A+2, get_optimized_kprobe() stops at B when arming a new probe C at A+4. It leaves A optimized:                A    A+1  A+2  A+3  A+4   A's jump  | e9 | d0 | d1 | d2 | d3 |   after C   | e9 | d0 | d1 | d2 | cc |  The INT3 for C overwrites the last byte of A's jump displacement, so execution can jump to the wrong address. B can have prepared optinsns while disarmed, but has no jump to unoptimize.  Continue past disarmed and unprepared probes to find the active optimized probe before arming a probe in its jump.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98857",
                        "url": "https://ubuntu.com/security/CVE-2026-98857",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ipvs: bound LBLCR and LBLC cache growth  ip_vs_lblcr_new() and ip_vs_lblc_new() create cache entries for every previously unseen destination address. The table max_size only tells the periodic collector to reclaim entries after the cache has already exceeded the limit. It does not reclaim entries that the attacker continues to use.  Reject new cache entries once either table reaches max_size * 3 / 2. The extra headroom lets the periodic collector catch up while the existing scheduler fallback continues to use the selected destination when cache creation fails. New traffic therefore stays serviceable without growing the tables further.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98732",
                        "url": "https://ubuntu.com/security/CVE-2026-98732",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  Bluetooth: btintel: fix buffer over-read in btintel_hw_error()  The \"Exception info %s\" print uses skb->data + 1, but the 12-byte payload is not guaranteed to be NUL-terminated and can be read past its end.  Bound the print with \"%.*s\" and skb->len - 1.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98735",
                        "url": "https://ubuntu.com/security/CVE-2026-98735",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  Bluetooth: hci_core: Serialize ACL scheduling with channel deletion  hci_chan_sent() selects a channel under RCU but drops the read lock before accessing chan->conn and returning the channel. The ACL and LE schedulers then use its packet queue and update its transmit counters without any protection against channel deletion.  After TX selects a channel and releases RCU, a disconnect command timeout on the separate request workqueue can run hci_conn_failed() and l2cap_conn_del(). hci_chan_del() can then unlink the channel, complete synchronize_rcu(), purge its queue and free it before TX resumes. This causes use-after-free both in hci_chan_sent() and in its callers.  KASAN reported:    BUG: KASAN: slab-use-after-free in hci_chan_sent+0x892/0x9b0   Workqueue: hci0 hci_tx_work   Call Trace:    hci_chan_sent+0x892/0x9b0    hci_tx_work+0x5e6/0xb70   Allocated by task 91:    hci_chan_create+0xe3/0x350    l2cap_conn_add.part.0+0x12/0xa30    l2cap_chan_connect+0x110d/0x1b60    l2cap_sock_connect+0x310/0x530   Freed by task 99:    hci_chan_del+0x11f/0x170    l2cap_conn_del+0x4f1/0x800    l2cap_connect_cfm+0x88c/0xd30    hci_conn_failed+0x150/0x250    hci_abort_conn_sync+0x3e3/0x800    hci_cmd_sync_run+0x7e/0xc0    hci_abort_conn+0x105/0x1f0    disconnect_sync+0x157/0x290    hci_cmd_sync_work+0x13c/0x290  Hold the existing device mutex across channel selection and transmission in both schedulers to serialize them with channel teardown. Keep timeout handling outside the critical sections because hci_link_tx_to() acquires the same mutex. This also permits the transmit path to sleep, unlike extending the RCU read-side critical section across packet submission.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98739",
                        "url": "https://ubuntu.com/security/CVE-2026-98739",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  Bluetooth: RFCOMM: Fix initial port reference race  For RFCOMM_RELEASE_ONHUP devices, rfcomm_tty_install() and __rfcomm_release_dev() both use RFCOMM_TTY_OWNED to decide who drops the initial tty_port reference. The release path tests the bit separately from the install path setting it, so both can drop that reference.  The synchronous hangup does not prevent this race: port->tty is not assigned until tty_port_open(), after installation. The following interleaving is possible:    1. Install and release each obtain a reference with rfcomm_dev_get().   2. Release observes RFCOMM_TTY_OWNED clear.   3. Install sets RFCOMM_TTY_OWNED and drops the initial reference.   4. Release drops the same initial reference again.   5. TTY cleanup drops its reference and frees the device.   6. Release performs its final tty_port_put() on the freed port.  KASAN reported:    BUG: KASAN: slab-use-after-free in tty_port_put+0x22/0x190   Write of size 4 at addr ffff8881001d3d5c by task poc/92    Call Trace:    tty_port_put+0x22/0x190    rfcomm_dev_ioctl+0x1d4/0x1930    sock_do_ioctl+0x110/0x260    sock_ioctl+0x380/0x590    __x64_sys_ioctl+0x134/0x1c0    Allocated by task 88:    rfcomm_dev_ioctl+0x8f6/0x1930    sock_do_ioctl+0x110/0x260    sock_ioctl+0x380/0x590    __x64_sys_ioctl+0x134/0x1c0    Freed by task 65:    kfree+0x131/0x3c0    rfcomm_dev_destruct+0x23b/0x2f0    release_one_tty+0xc1/0x370    process_one_work+0x661/0x1090  Use test_and_set_bit() in both paths so that only the caller that changes RFCOMM_TTY_OWNED from clear to set drops the initial reference. Each path keeps its own lookup reference until release or TTY cleanup, preserving the existing callback ordering and error handling.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98741",
                        "url": "https://ubuntu.com/security/CVE-2026-98741",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ALSA: ua101: reject mismatched capture/playback packet sizes  detect_usb_format() cross-checks bSubframeSize, bBitResolution and tSamFreq between the capture and playback interfaces, but never relates the two endpoints' wMaxPacketSize and bNrChannels.  Each playback URB gets a buffer of ua->playback.max_packet_bytes, while the number of bytes written into it is derived from the capture stream: capture_urb_complete() computes frames from the received capture packet and capture.frame_bytes, and start_usb_playback() and playback_work() multiply that by playback.frame_bytes.  A device declaring a large capture wMaxPacketSize with few capture channels and a small playback wMaxPacketSize with many playback channels therefore memset()s and memcpy()s past the end of the playback buffer, in open() of the PCM node the driver registers during probe. usb_submit_urb() rejects the over-long iso_frame_desc[0].length with -EMSGSIZE, but only after the write.  Reject such descriptors at probe time.  Genuine UA-101/UA-1000 hardware declares proportional packet sizes and is unaffected.    BUG: KASAN: slab-out-of-bounds in start_usb_playback (sound/usb/misc/ua101.c:586)   Write of size 2048 at addr ffff8881098f3c00 by task exploit/5021   Call Trace:    __asan_memset (mm/kasan/shadow.c:84)    start_usb_playback (sound/usb/misc/ua101.c:586)    playback_pcm_open (sound/usb/misc/ua101.c:679)    snd_pcm_open_substream (sound/core/pcm_native.c:2829)    snd_pcm_open (sound/core/pcm_native.c:2865 sound/core/pcm_native.c:2932)    snd_pcm_playback_open (sound/core/pcm_native.c:2891)    snd_open (sound/core/sound.c:166)    chrdev_open (fs/char_dev.c:411)    do_dentry_open (fs/open.c:996)    vfs_open (fs/open.c:1101)    path_openat (fs/namei.c:4837 fs/namei.c:5000)    do_file_open (fs/namei.c:5029)    do_sys_openat2 (fs/open.c:1417)    __x64_sys_openat (fs/open.c:1423 fs/open.c:1439 fs/open.c:1434)    do_syscall_64 (arch/x86/entry/syscall_64.c:61 arch/x86/entry/syscall_64.c:84)    entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:121)    The buggy address belongs to the object at ffff8881098f3c00    which belongs to the cache kmalloc-192 of size 192   The buggy address is located 0 bytes inside of    allocated 168-byte region [ffff8881098f3c00, ffff8881098f3ca8)",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98940",
                        "url": "https://ubuntu.com/security/CVE-2026-98940",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ASoC: qcom: lpass-cpu: use DAI table index for playback constraints  The DAI ID is a hardware port ID and is not necessarily the index of the corresponding entry in variant->dai_driver.  When configuring a DAI with LPAIF_I2SCTL_MODE_QUAD01, the probe code currently uses dai_id to index variant->dai_driver. This is incorrect for platforms where DAI IDs are sparse. For example, the IPQ806x MI2S DAI has ID 4 while it is the only entry in the DAI driver table. If that DAI is configured for QUAD01 and probe reaches this branch, the code writes beyond that single entry via dai_driver[4] instead of updating the DAI being processed.  Use the loop index i when updating the current DAI's playback channel constraints, while retaining dai_id for indexing the hardware-port specific playback SD-line mode array.  This fixes the incorrect DAI table access for platforms where the DAI ID does not match its position in the driver table.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98748",
                        "url": "https://ubuntu.com/security/CVE-2026-98748",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  serial: 8250_bcm7271: fix use-after-free in brcmuart_remove()  brcmuart_handle_irq() starts priv->hrt to work around a receive-timeout quirk of the 8250 core when hardware flow control is enabled; the timer callback brcmuart_hrtimer_func() dereferences priv.  brcmuart_remove() cancels the hrtimer before it unregisters the port, so a receive-timeout interrupt that arrives in between re-arms the timer. After devm frees priv, the callback runs on freed memory.  Unregister the port before cancelling the hrtimer. serial8250_unregister_port() shuts the port down and frees its IRQ, so brcmuart_handle_irq() can no longer restart the timer, and the final hrtimer_cancel() drains any timer that was armed before or during the unregister.  This issue was found by an in-house static analysis tool.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98754",
                        "url": "https://ubuntu.com/security/CVE-2026-98754",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  tty: vcc: hold port lock when clearing tty pointer in vcc_cleanup  vcc_cleanup() sets port->tty to NULL without holding port->lock, racing with vcc_event() LDC callbacks that read port->tty under port->lock and then use tty->port. This can cause a use-after-free when the callback dereferences tty->port after cleanup has already destroyed and freed it.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98755",
                        "url": "https://ubuntu.com/security/CVE-2026-98755",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  tty: vcc: zero-initialize control packet in vcc_send_ctl()  The stack-allocated struct vio_vcc pkt was partially initialized, leaving the tag.stype_env field uninitialized before being sent via ldc_write(), potentially leaking kernel stack data to the LDC peer.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98756",
                        "url": "https://ubuntu.com/security/CVE-2026-98756",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  usb: cdns3: Fix NULL pointer dereference in cdns3_pci_probe  The Cadence USBSS controller is a two-function PCI device. The first probed function allocates the driver data and stores it with pci_set_drvdata(), while the second function reuses it via pci_get_drvdata() when pci_is_enabled() reports that the first function has already been probed.  When the second function is probed while the first one has been enabled but has not yet set its driver data, pci_get_drvdata() returns NULL, and the subsequent wrap->devfn assignment dereferences a NULL pointer and crashes the kernel. logs: Call trace:   cdns3_pci_probe+0xa4/0x300   local_pci_probe+0x44/0xa8   pci_call_probe+0x54/0x158   pci_device_probe+0x84/0x100   really_probe+0x184/0x3d0   __driver_probe_device+0x80/0x178   driver_probe_device+0x44/0xe8   __driver_attach+0xec/0x1f8   bus_for_each_dev+0x7c/0xe0   driver_attach+0x28/0x38   bus_add_driver+0x110/0x238   driver_register+0x64/0x128   __pci_register_driver+0x50/0x60   cdns3_pci_driver_init+0x28/0x38   do_one_initcall+0x5c/0x280   do_initcalls+0x104/0x1d8   kernel_init_freeable+0x140/0x218   kernel_init+0x28/0x1f8   ret_from_fork+0x10/0x20  Return -EPROBE_DEFER in this case so that probing is retried after the first function has completed its probe.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98757",
                        "url": "https://ubuntu.com/security/CVE-2026-98757",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  usb: cdns3: fix use-after-free in cdns3_gadget_exit()  cdns3_gadget_start() arms two works on system_freezable_wq: pending_status_wq for the deferred ep0 status stage and aligned_buf_wq for realigned request buffers. Both handlers use the cdns3_device the works are embedded in, and cdns3_pending_setup_status_handler() also calls the ep0 request completion.  cdns3_gadget_exit() does not wait for these works. It frees all endpoints and aligned buffers and drops the last reference to the gadget device, which frees priv_dev, so a work queued before the exit can run after the free.  Fix this by waiting for both works after the gadget driver is unbound and the IRQ is freed, when no new work can be queued, and before the endpoints and buffers are released.  This issue was found by an in-house static analysis tool.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98760",
                        "url": "https://ubuntu.com/security/CVE-2026-98760",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  usb: typec: tipd: fix uninitialized typec_partner_desc in tps6598x_connect()  tps6598x_connect() passes a stack-allocated typec_partner_desc to typec_register_partner() after initializing only usb_pd, accessory and identity.  typec_register_partner() copies attach and deattach from the descriptor into the partner. With those fields left unset, garbage function pointers may be stored and later invoked from typec_partner_link_device() when a USB device is linked to the port. Uninitialized pd_revision and usb_capability similarly leak stack data through partner sysfs.  Zero-initialize the descriptor so optional callbacks remain NULL and the remaining fields are zero.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98761",
                        "url": "https://ubuntu.com/security/CVE-2026-98761",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  usb: typec: tcpm: recover after failure to start the frs ams  Reset the port if the tcpm fails to start the FAST_ROLE_SWAP AMS by initiating error recovery on it.  This helps in cases where some cables (incorrectly) signal an FRS to an FRS capable port during disconnection. The TCPC autonomously starts sourcing VBUS on detecting the FRS signal. However, the VBUS sourcing is left on when the FAST_ROLE_SWAP AMS fails to start (as tcpm_sink_tx_ok is 0 as CC is open due to the cable disconnect). This is because the code sets the state to INVALID_STATE without resetting the port state.  Log snippet before changes: [  101.401960] AMS FAST_ROLE_SWAP start [  101.401971] Sink TX No Go [  101.401982] sourcing vbus [  101.401987] VBUS on [  101.402159] VBUS on [  109.257809] CC1: 0 -> 0, CC2: 5 -> 0 [state SNK_READY, polarity 1, disconnected] [  111.267442] VBUS on  After changes: [   70.541211] AMS FAST_ROLE_SWAP start [   70.541220] Sink TX No Go [   70.541228] state change SNK_READY -> ERROR_RECOVERY [rev3 NONE_AMS] [   70.541362] VBUS on [   70.541365] sourcing vbus [   70.541367] VBUS on [   70.541374] state change ERROR_RECOVERY -> PORT_RESET [rev3 NONE_AMS] [   70.541410] disable vbus discharge ret:0 [   70.543028] Setting usb_comm capable false [   70.544009] Setting voltage/current limit 0 mV 0 mA [   70.544034] polarity 0 [   70.544239] Requesting mux state 0, usb-role 0, orientation 0 [   70.555550] cc:=0 [   70.555595] pending state change PORT_RESET -> PORT_RESET_WAIT_OFF @ 100 ms [rev3 NONE_AMS] [   70.555697] VBUS off [   70.555702] VBUS VSAFE0V [   70.555762] CC1: 5 -> 0, CC2: 0 -> 0 [state PORT_RESET, polarity 0, disconnected] [   70.587794] VBUS off [   70.587799] VBUS VSAFE0V [   70.655672] state change PORT_RESET -> PORT_RESET_WAIT_OFF [delayed 100 ms] [   70.655682] state change PORT_RESET_WAIT_OFF -> SNK_UNATTACHED [rev3 NONE_AMS] [   70.655686] Start toggling [   70.656274] CC1: 0 -> 0, CC2: 0 -> 0 [state TOGGLING, polarity 0, disconnected]",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98763",
                        "url": "https://ubuntu.com/security/CVE-2026-98763",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  usb: core: clear both ep_in and ep_out for non-ep0 control endpoints  In usb_enable_endpoint(), non-zero control endpoints (where usb_endpoint_xfer_control(&ep->desc) is true) populate both dev->ep_in[epnum] and dev->ep_out[epnum] with the same struct usb_host_endpoint pointer.  However, usb_disable_endpoint() only clears either dev->ep_out[epnum] or dev->ep_in[epnum] depending on the direction bit of epaddr when reset_hardware is set, leaving the opposite direction's array slot pointing to the disabled/freed endpoint.  Clear both dev->ep_out[epnum] and dev->ep_in[epnum] when disabling a non-ep0 control endpoint with reset_hardware set, and update the function kerneldoc accordingly.  Tested in QEMU against Linux 7.3.0-rc3 using dummy_hcd and raw-gadget to enumerate a USB device with a non-zero control endpoint (bEndpointAddress 0x01, bmAttributes USB_ENDPOINT_XFER_CONTROL), verifying that both dev->ep_in[1] and dev->ep_out[1] are cleared when the interface is disabled.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98764",
                        "url": "https://ubuntu.com/security/CVE-2026-98764",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  usb: gadget: f_fs: Fix NULL pointer dereference in FUNCTIONFS_ENDPOINT_DESC  When user space sets up FunctionFS with only full-speed descriptors (e.g., flags = FUNCTIONFS_HAS_FS_DESC) and the gadget operates at a higher speed (such as USB_SPEED_HIGH or USB_SPEED_SUPER), config_ep_by_speed() detects that the function lacks descriptors for the current speed, logs a warning, and falls back to full-speed descriptors. The endpoint is then successfully enabled via usb_ep_enable(), and epfile->ep becomes valid.  However, when user space subsequently issues the FUNCTIONFS_ENDPOINT_DESC ioctl to query the endpoint descriptor, ffs_epfile_ioctl() selects the descriptor index solely based on gadget->speed:  \tswitch (epfile->ffs->gadget->speed) { \tcase USB_SPEED_SUPER: \tcase USB_SPEED_SUPER_PLUS: \t\tdesc_idx = 2; \t\tbreak; \tcase USB_SPEED_HIGH: \t\tdesc_idx = 1; \t\tbreak; \tdefault: \t\tdesc_idx = 0; \t} \tdesc = epfile->ep->descs[desc_idx]; \tmemcpy(&desc1, desc, desc->bLength);  Because user space only supplied full-speed descriptors, epfile->ep->descs[1] is NULL. Dereferencing desc->bLength triggers an immediate kernel NULL pointer dereference panic.  Fix this by falling back through lower speed descriptors if the current speed descriptor was not supplied, matching the fallback logic in config_ep_by_speed() and historical f_fs behavior. If still missing, fall back to epfile->ep->ep->desc (the active descriptor), and return -EINVAL safely if no valid descriptor is found. In addition, mark desc as const to match struct usb_ep::desc and avoid discarding qualifiers.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98765",
                        "url": "https://ubuntu.com/security/CVE-2026-98765",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  USB: gadget: dummy-hcd: Fix wait for outstanding request completions  The dummy-hcd driver emulates synchronize_irq() by waiting until its private callback_usage counter drops to 0 (with the private lock not held).  This counter is incremented whenever a gadget driver callback occurs (which requires the private lock to be dropped), but not when a request completion handler is called.  This is an oversight.  Request completion is triggered by timer interrupts (emulating device IRQs in a real UDC), and the interrupt handlers are supposed to have completed when the synchronize_irq() emulation routine returns -- they aren't supposed to be in the middle of a completion callback.  If this happens it can lead to a gadget driver's unbind routine running before all outstanding request completions have finished, maybe even allowing the gadget driver's module to be unloaded while a completion handler is still running.  Fix the oversight by incrementing the callback_usage value across request completion callbacks.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98766",
                        "url": "https://ubuntu.com/security/CVE-2026-98766",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  usb: gadget: aspeed-vhub: cancel wake work on device removal  wake_work is armed from the gadget .wakeup callback to resume suspended downstream ports, and it is never cancelled in ast_vhub_remove(), so a work item queued before or during removal can run after devm has freed vhub and its ports, a use-after-free.  Cancelling the work alone is not sufficient: usb_gadget_wakeup() takes no lock and the unbind path never clears wakeup_en, so a remote-wakeup request in flight on another CPU can re-arm the work after the cancel and before vhub is freed.  ast_vhub_del_dev() already clears d->registered under vhub->lock before unregistering the gadget. Refuse the wakeup in ast_vhub_udc_wakeup() once d->registered is clear: the check and the schedule_work() are then atomic against the unbind, so a wakeup that passed before the flag was cleared is drained by the cancel_work_sync() after the del_dev loop, and one that arrives later returns without arming. Also move INIT_WORK() to the top of ast_vhub_probe(), since the probe error path reuses ast_vhub_remove() and would otherwise cancel a never-initialized work item.  This issue was found by an in-house static analysis tool.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98769",
                        "url": "https://ubuntu.com/security/CVE-2026-98769",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  usb: gadget: f_uac1_legacy: validate bRequest index in generic_{set,get}_cmd  generic_set_cmd() and generic_get_cmd() use the low nibble of ctrl->bRequest as an index into con->data[]:      u8 cmd = (ctrl->bRequest & 0x0F);  /* 0 .. 15 */     ...     con->data[cmd] = value;            /* OOB when cmd >= 5 */  struct usb_audio_control (include/linux/usb/audio.h) declares data as a 5-element array, so indices 5 through 15 write (or read) up to 44 bytes past the end of the array on the heap.  A malicious USB host can craft a class-specific SET_CUR / GET_CUR request with an arbitrary bRequest value, triggering the out-of-bounds access from an IRQ completion handler with no further preconditions.  Add an ARRAY_SIZE() guard to both functions.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98771",
                        "url": "https://ubuntu.com/security/CVE-2026-98771",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  usb: storage: sierra_ms: reject short SWoC info transfers  sierra_get_swoc_info() requests sizeof(struct swoc_info) (60) bytes from the device via usb_control_msg(), but its callers only treat a negative return value as failure. A device that answers the vendor-specific GetSwocInfo request with a short IN transfer is therefore accepted, leaving the tail of the freshly allocated (kmalloc(), non-zeroing) swoc_info buffer uninitialized.  truinst_show() subsequently prints swocInfo->rev, swocInfo->LinuxSKU and swocInfo->LinuxVer from that buffer into the world-readable (0444) \"truinst\" sysfs attribute. An emulated/malicious USB device (VID 0x1199, PID 0x0fff) can exploit this to disclose up to 5 bytes of stale kernel heap memory (kmalloc-64) to unprivileged userspace, once per sysfs read, indefinitely. On kernels built without init_on_alloc this leaks recently freed heap contents.  Only accept the transfer when the full structure was received. sierra_ms_init() already retries failed queries, so well-behaved devices are unaffected.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98772",
                        "url": "https://ubuntu.com/security/CVE-2026-98772",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  USB: serial: fix port tear down use-after-free  Some drivers for multiport devices access port driver data from completion handlers of shared URBs submitted at attach() or first open() and stopped at disconnect() or last close(), respectively.  A simple NULL check before accessing the driver data makes sure that a port state container has at least been allocated, but a completion handler can still race with port tear down.  Reorder the disconnect handling so that ports are not deregistered (and their driver data freed) until after all ports have been hung up and the driver disconnect() callback has run so that all I/O has been stopped.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98775",
                        "url": "https://ubuntu.com/security/CVE-2026-98775",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  nitro_enclaves: fix use-after-free on SLOT_ALLOC failure  When ne_create_vm_ioctl() fails the SLOT_ALLOC request after anon_inode_getfile() has succeeded, the error path calls fput(enclave_file) and then frees ne_enclave.  In normal userspace context, fput() defers the final __fput() via task_work. ne_enclave_release() therefore runs after ne_enclave has already been freed and dereferences ne_enclave->slot_uid, causing a use-after-free: KASAN: slab-use-after-free in ne_enclave_release.  The enclave has no slot allocated and is not yet linked into the enclaves list on this error path, so ne_enclave_release() is expected to return early when slot_uid is zero. However, reading slot_uid already accesses the freed object.  Clear enclave_file->private_data before fput() on the error path. ne_enclave_release() then returns immediately when private_data is NULL, leaving the ioctl error path as the sole owner of ne_enclave. This is safe because the file has not been fd_install()'d yet.  Tested on an AWS EC2 m5.2xlarge with CONFIG_KASAN=y. Without the patch, the reproducer triggers a KASAN slab-use-after-free on every SLOT_ALLOC failure. With the patch, no KASAN report is produced and the SLOT_ALLOC error is still returned. Normal enclave creation and teardown are unaffected.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98790",
                        "url": "https://ubuntu.com/security/CVE-2026-98790",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  perf: Fix race between perf_event_exit_task() and perf_pending_task()  A race condition exists between perf_event_exit_task() and perf_pending_task() during begin_new_exec().  During begin_new_exec(), perf_event_exit_task() may be called, and the PF_EXITING flag is not set on task. So perf_sigtrap() continues to execute and triggers WARN_ON_ONCE(event->ctx->task != current).  Since both task exit and exec paths can call perf_event_exit_task() which sets ctx->task to TASK_TOMBSTONE, fix this by explicitly checking if event->ctx->task equals TASK_TOMBSTONE and dropping the redundant PF_EXITING check.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98934",
                        "url": "https://ubuntu.com/security/CVE-2026-98934",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ipv6: sr: use skb_get_hash_net() in seg6_make_flowlabel()  Since commit d58e468b1112 (\"flow_dissector: implements flow dissector BPF hook\") __skb_flow_dissect() needs a net pointer, either from skb->dev, skb->sk, or since commit 3cbf4ffba5ee (\"net: plumb network namespace into __skb_flow_dissect\") a caller provided pointer.  syzbot was able to reach seg6_make_flowlabel() with an skb having neither skb->dev nor skb->sk set: a TIPC UDP bearer sends a discovery message through an IPv4 route using seg6 encap, while net.ipv6.seg6_flowlabel is set to 1.  seg6_make_flowlabel() already has a net pointer, use skb_get_hash_net().  WARNING: net/core/flow_dissector.c:1131 at __skb_flow_dissect+0x910/0x5368 net/core/flow_dissector.c:1126, CPU#0: syz.0.17/4930 Call trace:   __skb_flow_dissect+0x910/0x5368 net/core/flow_dissector.c:1126 (P)   __skb_get_hash_net+0xe0/0x29c net/core/flow_dissector.c:1903   skb_get_hash include/linux/skbuff.h:1663 [inline]   seg6_make_flowlabel+0xcc/0x1ec net/ipv6/seg6_iptunnel.c:132   __seg6_do_srh_encap+0x320/0xbf4 net/ipv6/seg6_iptunnel.c:161   seg6_do_srh+0x4b4/0xa44 net/ipv6/seg6_iptunnel.c:431   seg6_output_core+0x164/0x688 net/ipv6/seg6_iptunnel.c:681   seg6_output+0x44/0x1ac net/ipv6/seg6_iptunnel.c:744   lwtunnel_output+0x3d0/0x664 net/core/lwtunnel.c:356   dst_output include/net/dst.h:470 [inline]   ip_local_out+0x110/0x148 net/ipv4/ip_output.c:131   iptunnel_xmit+0x50c/0xd38 net/ipv4/ip_tunnel_core.c:97   udp_tunnel_xmit_skb+0x220/0x348 net/ipv4/udp_tunnel_core.c:187   tipc_udp_xmit+0x75c/0x9c0 net/tipc/udp_media.c:202   tipc_udp_send_msg+0x214/0x374 net/tipc/udp_media.c:274   tipc_bearer_xmit_skb+0x260/0x3b0 net/tipc/bearer.c:576   tipc_enable_bearer net/tipc/bearer.c:366 [inline]   __tipc_nl_bearer_enable+0xc90/0xfb0 net/tipc/bearer.c:1048   tipc_nl_bearer_enable+0x2c/0x48 net/tipc/bearer.c:1057   genl_family_rcv_msg_doit+0x1e4/0x2d4 net/netlink/genetlink.c:1114",
                        "cve_priority": "negligible",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2022-49622",
                        "url": "https://ubuntu.com/security/CVE-2022-49622",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  netfilter: nf_tables: avoid skb access on nf_stolen  When verdict is NF_STOLEN, the skb might have been freed.  When tracing is enabled, this can result in a use-after-free: 1. access to skb->nf_trace 2. access to skb->mark 3. computation of trace id 4. dump of packet payload  To avoid 1, keep a cached copy of skb->nf_trace in the trace state struct. Refresh this copy whenever verdict is != STOLEN.  Avoid 2 by skipping skb->mark access if verdict is STOLEN.  3 is avoided by precomputing the trace id.  Only dump the packet when verdict is not \"STOLEN\".",
                        "cve_priority": "medium",
                        "cve_public_date": "2025-02-26 07:01:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98794",
                        "url": "https://ubuntu.com/security/CVE-2026-98794",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ipvs: filter some flags received in the backup server  While the IPVS SYNC protocol is not secure by design we can still protect the backup server from messages that can wreak havoc.  This commit addresses problems from received connection flags or their combinations. We now drop messages as follows:  1. the NO_CPORT+TEMPLATE combination allows lookups for normal connections to hit template which can break in many ways. While the master does not sync connections with NO_CPORT flag, i.e. before they are established, we still accept NO_CPORT without TEMPLATE.  2. ONE_PACKET: it is not sent by master, so we do not expect it in backup. Before now it was ignored by IP_VS_CONN_F_BACKUP_MASK for protocol v1 while protocol v0 created connections that are not hashed and dropped immediately. Better to apply the IP_VS_CONN_F_BACKUP_MASK also to the flags from v0 messages for consistency with v1.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98805",
                        "url": "https://ubuntu.com/security/CVE-2026-98805",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  tipc: prevent GCM nonce reuse on peer key changes  TIPC can encrypt traffic between nodes using a different transmit key for each node. In this mode, the AES-GCM nonce for a packet sent to a known peer consists of a 32-bit prefix (a per-key salt XOR the peer's address) followed by a 64-bit counter. That counter is stored in the peer's RX crypto object. When the peer reports a change in which key it uses to receive packets, TIPC resets this counter. The sender can still be using the same TX key and salt, so subsequent packets reuse earlier nonces. This nonce reuse breaks confidentiality and exposes GCM's authentication key. This makes forgeries trivial: an attacker can exploit CTR malleability to alter captured ciphertexts and use the recovered authentication key to compute a valid tag for the modified ciphertext, under the same key and nonce.  Use the TX key's existing aead->seqno counter instead. All encryptions using that key object share the same atomic counter, so concurrent encryptions get distinct nonce counter values. The counter survives key activation and peer reconnection, and peer key-status reports cannot reset it. This prevents those transitions from causing nonce reuse while the same TX key remains installed.  The nonce format is unchanged, and receivers do not require consecutive counter values, so sharing the counter across peers remains compatible with existing receivers. A pre-existing check still invokes key revocation in the unlikely event that the counter wraps to zero.",
                        "cve_priority": "critical",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98811",
                        "url": "https://ubuntu.com/security/CVE-2026-98811",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net/sched: cls_api: reclaim an empty proto on the error path  Two racing tc filter add requests on the same chain/prio of an unlocked classifier both run change() on the shared proto and both can fail: the winner's tcf_chain_tp_delete_empty() attempt gives up because the loser's handle is still in the idr, and the loser's error path drops only its own reference without a second reclamation attempt. The empty proto stays linked in the chain, holding the chain reference, a block reference and the classifier module reference until the chain or block is torn down.  Reclaim the proto on the error path of any failed request that holds a proto reference. The reclamation is emptiness-gated: tcf_chain_tp_delete_empty() unlinks the proto only when delete_empty() admits it is empty, so a live shared proto is never unlinked. A proto the request created is reclaimed unconditionally - it is the only owner, so marking it for deletion is safe even without a delete_empty callback. Classifiers without one (the check marks the proto unconditionally) are rtnl-serialized, so the raced window this guard closes cannot arise for them.  This is a follow-up to commit d4e359b3608a (\"net/sched: cls_api: fix teardown of an adopted proto on insert-race loss\"), which stopped the loser of the insert race from unlinking the winner's live proto but left the empty-proto residual in place.  Conditions to recreate: - CONFIG_NET_CLS_FLOWER=y; veth pair - tc qdisc add dev veth0 ingress - two concurrent `tc filter add dev veth0 ingress protocol ip pref 1   flower skip_sw ... action drop` (both fail in fl_hw_replace_filter   after publishing their handle in the idr); repeat in a loop - an empty flower tp stays linked after both requests fail; visible   as a bare `filter protocol ip pref 1 flower chain 0` header in   `tc filter show` with no filter entries - CAP_NET_ADMIN (namespace-local via unshare -Urn suffices)",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98812",
                        "url": "https://ubuntu.com/security/CVE-2026-98812",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net/mctp: publish the mctp_dev only after it is initialised  mctp_add_dev() links the new mctp_dev into dev->mctp_ptr before mdev->dev is assigned, so a reader that picks the device up in that window dereferences a net_device pointer that is still NULL:  KASAN: null-ptr-deref in range [0x00000000000000b0-0x00000000000000b7] Call Trace:  <TASK>  ? __pfx_mctp_sendmsg (./include/linux/sockptr.h:49)  ? __pfx_mctp_dst_output (net/mctp/route.c:41)  ? selinux_socket_sendmsg (security/selinux/hooks.c:5278)  ____sys_sendmsg (net/socket.c:775 (discriminator 1) net/socket.c:790  (discriminator 1) net/socket.c:2684 (discriminator 1))  ? __pfx_____sys_sendmsg (net/socket.c:1131)  ? __pfx_copy_msghdr_from_user (net/socket.c:2590)  ? update_cfs_rq_load_avg (kernel/sched/fair.c:5478)  ___sys_sendmsg (net/socket.c:2738)  ? __pfx____sys_sendmsg (net/socket.c:2625)  ? perf_event_task_tick (./include/linux/rcupdate.h:838)  ? sched_tick (kernel/sched/core.c:5818)  ? clockevents_program_event (kernel/time/clockevents.c:372)  ? fdget (./include/linux/rcupdate.h:873 fs/file.c:1100)  __sys_sendmsg (net/socket.c:2770)  ? __pfx___sys_sendmsg (net/socket.c:2751)  do_syscall_64 (arch/x86/entry/syscall_64.c:63)  entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:121)  </TASK>  Fix by publishing only once the object is fully initialised: __mctp_dev_get() runs under rcu_read_lock() only and hands this object to readers as soon as mctp_ptr is assigned, so they must never observe mdev->dev == NULL.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98819",
                        "url": "https://ubuntu.com/security/CVE-2026-98819",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  Bluetooth: btintel: validate DDC record lengths  Parse DDC record lengths in unsigned storage so 0xFF does not wrap. Reject records smaller than the mandatory three-byte header, records exceeding U8_MAX, and records exceeding remaining firmware bytes before issuing Intel_Write_DDC.  This issue was reported by Claude Mythos.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98823",
                        "url": "https://ubuntu.com/security/CVE-2026-98823",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: cfg80211: preserve hidden-group beacon IE ownership  A hidden-group probe-response entry borrows its beacon IEs from the group's beacon entry. cfg80211_update_assoc_bss_entry() can pass such an entry to cfg80211_update_known_bss() when merging scan entries after a channel switch.  Copying the borrowed beacon_ies into the associated entry gives the same allocation two owners. Releasing the group's beacon entry can then leave the associated entry pointing to freed IEs, which are freed again when that entry is released.  Skip beacon IE replacement when the source entry belongs to a hidden group. Preserve probe-response processing, the subsequent metadata updates, and the existing rejection path for conflicting hidden beacon updates.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98936",
                        "url": "https://ubuntu.com/security/CVE-2026-98936",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: ath11k: reset ar->num_stations on hardware start  When (multiple) hw restart occurs, we end up in a situation where we cannot accept new stations / mesh peers. This seems to be the 'num_stations' in 'struct ath11k' that did not get reset properly in this case. In ath11k_mac_op_start(), it was indeed the only accounting var that did not get reset so let's clear it too.  This avoids problems like those:  \t[1248828.088023] WARNING: CPU: 0 PID: 12281 at net/mac80211/util.c:1682 ieee80211_reconfig_stations+0x98/0xc0 \t[1248828.088115] Call trace: \t[1248828.088116]  ieee80211_reconfig_stations+0x98/0xc0 (P) \t[1248828.088119]  ieee80211_reconfig+0x774/0x1438 \t[1248828.088123]  ieee80211_restart_work+0x10c/0x178 \t[1248828.088127]  process_one_work+0x178/0x3c0 \t[1248828.088130]  worker_thread+0x280/0x440 \t[1248828.088133]  kthread+0xe0/0xf8 \t[1248828.088137]  ret_from_fork+0x10/0x20 \t[1248828.088141] ---[ end trace 0000000000000000 ]--- \t[1248836.686604] ath11k_pci 0000:04:00.0: refusing to associate station: too many connected already (128) \t[1248836.686609] ath11k_pci 0000:04:00.0: Failed to add station: xx:xx:xx:xx:xx:xx for VDEV: 1  Tested-on: QCN9074 hw1.0 PCI WLAN.HK.2.9.0.1-01977-QCAHKSWPL_SILICONZ-1",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-23 13:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98831",
                        "url": "https://ubuntu.com/security/CVE-2026-98831",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  of/overlay: don't leak fragment references when changeset init fails  init_overlay_changeset() stores the number of initialized fragments in ovcs->count only on full success. When find_target() or the __symbols__ lookup fails partway through, the target and overlay references taken for the fragments initialized so far are never dropped: free_overlay_changeset() bounds its cleanup loop by ovcs->count, which is still 0.  Store the running count on the error path so free_overlay_changeset() puts whatever was set up. The store is guarded by ovcs->fragments because on the allocation-failure path cnt still holds the counting pass total while there is no fragments array; everywhere else cnt only counts fully-initialized fragments.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98833",
                        "url": "https://ubuntu.com/security/CVE-2026-98833",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  mtd: core: call _get_device() with the master MTD  __get_mtd_device() calls the master's _get_device() callback with mtd, which may be a partition. __put_mtd_device() passes the master.  This breaks gluebi partitions because gluebi_get_device() uses container_of() and therefore requires the master MTD. Pass the master to _get_device(), matching _put_device().",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-89860",
                        "url": "https://ubuntu.com/security/CVE-2026-89860",
                        "cve_description": "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 second INIT_WORK() reinitializes a work item that is already queued, which can corrupt the workqueue list and lead to crashes or a looping worker.  Initialize priv->abort_work once at command submission, next to the existing per-command spin_lock_init(&priv->cmd_lock), and leave only schedule_work() in the abort paths. schedule_work() already does nothing when the work item is still pending, so a repeated abort no longer disturbs an in-flight work item. The command is not returned to the transport until the final kref_put()/release callback runs after abort_work has completed, so the work item is idle before priv is reused and the single submission-time INIT_WORK() is safe.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-09-16 11:16:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-53353",
                        "url": "https://ubuntu.com/security/CVE-2026-53353",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  hsr: Remove WARN_ONCE() in hsr_addr_is_self().  syzbot reported the warning [0] in hsr_addr_is_self(), whose assumption is simply wrong.  hsr->self_node is cleared in hsr_del_self_node(), which is called from hsr_dellink().  Since dev->rtnl_link_ops->dellink() is called before unregister_netdevice_many(), there is a window when user can find the device but without hsr->self_node.  Let's remove WARN_ONCE() in hsr_addr_is_self().  [0]: HSR: No self node WARNING: net/hsr/hsr_framereg.c:39 at hsr_addr_is_self+0x211/0x3f0 net/hsr/hsr_framereg.c:39, CPU#0: syz.4.16848/17220 Modules linked in: CPU: 0 UID: 0 PID: 17220 Comm: syz.4.16848 Tainted: G             L     syzkaller #0 PREEMPT_{RT,(full)} Tainted: [L]=SOFTLOCKUP Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/18/2026 RIP: 0010:hsr_addr_is_self+0x211/0x3f0 net/hsr/hsr_framereg.c:39 Code: 33 2f 41 0f b7 dd 89 ee 09 de 31 ff e8 c8 b4 c6 f6 09 dd 74 54 e8 0f b0 c6 f6 31 ed eb 53 e8 06 b0 c6 f6 48 8d 3d 2f 50 9c 04 <67> 48 0f b9 3a 31 ed eb 42 e8 c1 13 1f 00 89 c5 31 ff 89 c6 e8 96 RSP: 0018:ffffc900041c70e0 EFLAGS: 00010283 RAX: ffffffff8afdc6ca RBX: ffffffff8afdc4e6 RCX: 0000000000080000 RDX: ffffc90010493000 RSI: 0000000000000948 RDI: ffffffff8f9a1700 RBP: 0000000000000001 R08: 0000000000000000 R09: 0000000000000000 R10: ffffc900041c71e8 R11: fffff52000838e3f R12: dffffc0000000000 R13: ffff888041f9e3c0 R14: ffff888086ee3802 R15: 0000000000000000 FS:  00007f6fe985d6c0(0000) GS:ffff888126176000(0000) knlGS:0000000000000000 CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f80bd437dac CR3: 0000000025096000 CR4: 00000000003526f0 DR0: ffffffffffffffff DR1: 00000000000001f8 DR2: 0000000000000002 DR3: ffffffffefffff15 DR6: 00000000ffff0ff0 DR7: 0000000000000400 Call Trace:  <TASK>  check_local_dest net/hsr/hsr_forward.c:592 [inline]  fill_frame_info net/hsr/hsr_forward.c:728 [inline]  hsr_forward_skb+0xa11/0x2a80 net/hsr/hsr_forward.c:739  hsr_dev_xmit+0x253/0x370 net/hsr/hsr_device.c:236  __netdev_start_xmit include/linux/netdevice.h:5368 [inline]  netdev_start_xmit include/linux/netdevice.h:5377 [inline]  xmit_one net/core/dev.c:3888 [inline]  dev_hard_start_xmit+0x2df/0x860 net/core/dev.c:3904  __dev_queue_xmit+0x1428/0x3900 net/core/dev.c:4870  neigh_output include/net/neighbour.h:556 [inline]  ip_finish_output2+0xcec/0x10b0 net/ipv4/ip_output.c:237  ip_send_skb net/ipv4/ip_output.c:1510 [inline]  ip_push_pending_frames+0x8b/0x110 net/ipv4/ip_output.c:1530  raw_sendmsg+0x1547/0x1a50 net/ipv4/raw.c:659  sock_sendmsg_nosec net/socket.c:787 [inline]  __sock_sendmsg net/socket.c:802 [inline]  ____sys_sendmsg+0x7da/0x9c0 net/socket.c:2698  ___sys_sendmsg+0x2a5/0x360 net/socket.c:2752  __sys_sendmsg net/socket.c:2784 [inline]  __do_sys_sendmsg net/socket.c:2789 [inline]  __se_sys_sendmsg net/socket.c:2787 [inline]  __x64_sys_sendmsg+0x1c3/0x2a0 net/socket.c:2787  do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]  do_syscall_64+0x15f/0xf80 arch/x86/entry/syscall_64.c:94  entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f6feb62ce59 Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 e8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f6fe985d028 EFLAGS: 00000246 ORIG_RAX: 000000000000002e RAX: ffffffffffffffda RBX: 00007f6feb8a6090 RCX: 00007f6feb62ce59 RDX: 0000000000000000 RSI: 0000200000000000 RDI: 0000000000000004 RBP: 00007f6feb6c2d6f R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007f6feb8a6128 R14: 00007f6feb8a6090 R15: 00007ffcf01cc488  </TASK>",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-07-01 14:16:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98836",
                        "url": "https://ubuntu.com/security/CVE-2026-98836",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ALSA: line6: reject oversized playback packets  Each playback URB is handed a slice of out.buffer that is exactly LINE6_ISO_PACKETS * max_packet_size_out bytes, sized from the OUT endpoint, but the number of bytes written into that slice is never compared against it.  submit_audio_out_urb() takes the frame count from prev_fsize, which audio_in_callback() derived from the *IN* endpoint's received packet length, and rescales it with the playback frame size; when prev_fsize is still zero it synthesizes a length from the sample rate instead.  On a device declaring a large IN wMaxPacketSize and a small OUT wMaxPacketSize, the resulting memcpy(), or the memset() when the playback stream is idle, runs past its slice and, as the reproducer below shows, beyond the allocation.  usb_submit_urb() is not a backstop.  max_packet_size_out comes from usb_maxpacket(), which returns only the low 11 bits of wMaxPacketSize, while USB core validates a high-speed isochronous length against that base scaled by usb_endpoint_maxp_mult().  A length of up to three times the allocated slice is therefore accepted, and even a rejected URB is only rejected after the write.  Reject a packet that does not fit the slice the driver allocated for it. Clamping it instead would silently shorten the capture-derived rate feedback and desynchronize the two streams.    BUG: KASAN: slab-out-of-bounds in submit_audio_out_urb (sound/usb/line6/playback.c:229)   Write of size 1024 at addr ffff888100bbd400 by task kworker/1:2/5002   Workqueue: events line6_startup_work   Call Trace:    __asan_memcpy (mm/kasan/shadow.c:106)    submit_audio_out_urb (sound/usb/line6/playback.c:229)    line6_submit_audio_out_all_urbs (sound/usb/line6/playback.c:291)    line6_stream_start (sound/usb/line6/pcm.c:194)    line6_pcm_acquire (sound/usb/line6/pcm.c:337)    line6_startup_work (sound/usb/line6/driver.c:728)    process_one_work (kernel/workqueue.c:3396)    worker_thread (kernel/workqueue.c:3479 kernel/workqueue.c:3560)    kthread (kernel/kthread.c:436)    ret_from_fork (arch/x86/kernel/process.c:158)    ret_from_fork_asm (arch/x86/entry/entry_64.S:245)    The buggy address belongs to the object at ffff888100bbd400    which belongs to the cache kmalloc-256 of size 256   The buggy address is located 0 bytes inside of    allocated 256-byte region [ffff888100bbd400, ffff888100bbd500)",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98838",
                        "url": "https://ubuntu.com/security/CVE-2026-98838",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  vt: skip screen update for DEC alignment test on backgroup consoles  [BUG] Recently, we encountered a KASAN warning as follows:  BUG: KASAN: slab-out-of-bounds in fb_pad_aligned_buffer+0x11f/0x140 Read of size 1 at addr ff1100015fd9f6a4 by task tty_fbcon_oob/1239 CPU: 7 UID: 0 PID: 1239 Comm: tty_fbcon_oob Not tainted 7.3.0-rc1 #100 PREEMPT(full) Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.17.0-4.fc41 04/01/2014 Call Trace:  <TASK>  ...  kasan_report+0xf0/0x120  fb_pad_aligned_buffer+0x11f/0x140  ccw_putcs+0x86c/0xa80  fbcon_putcs+0x338/0x410  do_update_region+0x21d/0x450  do_con_write+0x1e0e/0x4880  con_write+0x13/0x80  n_tty_write+0x374/0x1010  file_tty_write.isra.0+0x404/0x7a0  ...  reproduce: 1) open /dev/tty0, set a KDFONTOP ioctl with op.op = KD_FONT_OP_SET, op.width = 8 and op.height = 16 (visible VC1) 2) open /dev/tty1, set a KDFONTOP ioctl with op.op = KD_FONT_OP_SET, op.width = 28 and op.height = 24 (invisible VC2) 3) echo 3 > /sys/devices/virtual/graphics/fbcon/rotate_all 4) write EShash8(esc hash8) to tty1  [CAUSE] All VCs render to the framebuffer. setfont only modifies the target VC's font without resizing the framebuffer backing buffer (par->rotated.buf); the buffer is only resized for the visible VC (fbcon_do_set_font -> ... -> vc_do_resize -> update_screen). This relies on the con_should_update() check performed before every update_region().  However, the ESC # 8 path (do_con_trol -> do_update_region) omits the con_should_update() check. After changing the font size of an invisible VC, do_update_region() fills using the new font size against a buffer that was never resized, causing an out-of-bounds access.  [FIX] Only push the update when the console is visible and not blanked, add the con_should_update() check in the do_con_trol() like every other call site of do_update_region() (update_region(), invert_screen(), ...).",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98568",
                        "url": "https://ubuntu.com/security/CVE-2026-98568",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  vxlan: use one headroom snapshot for neighbour replies  vxlan_na_create() samples LL_RESERVED_SPACE() to size the reply skb and then samples it again to reserve headroom. A concurrent vxlan_changelink() can update needed_headroom between the two reads, creating a TOCTOU race. The second value can exceed the allocation and make the Ethernet header write out of bounds.  The race is reproducible on the unpatched kernel. It occurred when vxlan_na_create() generated a neighbour reply while vxlan_changelink() changed the link headroom. KASAN caught a four-byte write two bytes beyond a 704-byte skbuff_small_head allocation.  Snapshot the headroom once and use that value for both allocation and reservation.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2024-49901",
                        "url": "https://ubuntu.com/security/CVE-2024-49901",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  drm/msm/adreno: Assign msm_gpu->pdev earlier to avoid nullptrs  There are some cases, such as the one uncovered by Commit 46d4efcccc68 (\"drm/msm/a6xx: Avoid a nullptr dereference when speedbin setting fails\") where  msm_gpu_cleanup() : platform_set_drvdata(gpu->pdev, NULL);  is called on gpu->pdev == NULL, as the GPU device has not been fully initialized yet.  Turns out that there's more than just the aforementioned path that causes this to happen (e.g. the case when there's speedbin data in the catalog, but opp-supported-hw is missing in DT).  Assigning msm_gpu->pdev earlier seems like the least painful solution to this, therefore do so.  Patchwork: https://patchwork.freedesktop.org/patch/602742/",
                        "cve_priority": "low",
                        "cve_public_date": "2024-10-21 18:15:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98846",
                        "url": "https://ubuntu.com/security/CVE-2026-98846",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  sctp: check RCV_SHUTDOWN after the sendmsg connect wait  sctp_wait_for_connect() drops the socket lock while it sleeps. An out-of-the-blue ABORT can then be processed from the socket backlog and unlink the association. If a concurrent shutdown(fd, SHUT_RD) sets RCV_SHUTDOWN, the waiter breaks with err == 0 before checking asoc->base.dead. Its final sctp_association_put() can then free the association, leaving sctp_sendmsg_to_asoc() to continue with a dangling pointer.  Check RCV_SHUTDOWN along with the wait error in sctp_sendmsg_to_asoc() before using the association again. The check only accesses the socket, so it needs no additional association reference. Return the existing -ESRCH so that sctp_sendmsg() skips freeing a new association that may already have been destroyed.  Keep sctp_wait_for_connect() unchanged to preserve its behavior for the connect() caller.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98847",
                        "url": "https://ubuntu.com/security/CVE-2026-98847",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  rtc: spear: initialize IRQ state before requesting alarm IRQ  devm_request_irq() enables the interrupt before it returns, so the handler may run while probe is still initializing the device. Initialize the MMIO address and spinlock before requesting the alarm IRQ.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98850",
                        "url": "https://ubuntu.com/security/CVE-2026-98850",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net/packet: prevent TX_RING byte count overflow  tpacket_snd() drains every SEND_REQUEST frame in a TX ring and adds each valid packet length to the signed int len_sum. Userspace can recycle completed frames concurrently, so a single blocking send call is not bounded by the ring size.  After enough successful transmissions len_sum wraps into the negative range. In particular, 65536 65535-byte frames followed by a 65007-byte frame produce 0xfffffdef, or -EIOCBQUEUED. sock_sendmsg_nosec() treats that as an impossible return and triggers a BUG. On systems configured to panic on oops, a CAP_NET_RAW holder can panic the host kernel.  Stop before the next frame would make the byte count exceed INT_MAX. The positive short count leaves that frame pending for a later send call.  A two-thread TPACKET_V2 reproducer triggered the BUG on an arm64 build of Linux 7.3-rc4. With this change, the same reproducer returned the expected positive short count without an oops.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98851",
                        "url": "https://ubuntu.com/security/CVE-2026-98851",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  netfilter: nft_flow_offload: drop flowtable reference on init error path  nft_flow_offload_init() bumps the flowtable use count with nft_use_inc() before calling nf_ct_netns_get().  When the latter fails, the error is returned as-is and the reference is leaked.  The upper layers do not balance it either: nf_tables_newexpr() clears expr->ops when the expression init callback fails, so the nft_expr_more() iteration in nft_rule_expr_deactivate() and nf_tables_rule_destroy() stops right before the failed expression and its ->destroy callback, which would drop the reference, never runs.  Each failed rule addition therefore leaks one flowtable reference and the flowtable can no longer be removed: NFT_MSG_DELFLOWTABLE keeps reporting -EBUSY even though no rule references it.  Save the nf_ct_netns_get() return value and undo the nft_use_inc() when it fails, restoring the inc/dec pairing within nft_flow_offload_init() itself.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98854",
                        "url": "https://ubuntu.com/security/CVE-2026-98854",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  of/overlay: only treat a positive changeset id as registered  of_overlay_fdt_apply() stores the idr_alloc() return value in ovcs->id before checking it. On failure the stored id is negative, free_overlay_changeset()'s \"if (ovcs->id)\" check passes, idr_remove() is called with a negative id and list_del() runs on ovcs->ovcs_list, which is not initialized until after the id allocation. An allocation failure at that point dereferences NULL.  Make free_overlay_changeset() treat only a strict-positive id as registered. The rest of the function already copes with a partially-initialized ovcs, so the error path stays a plain goto err_free_ovcs.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98855",
                        "url": "https://ubuntu.com/security/CVE-2026-98855",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  of/overlay: put property on deadprops only after changeset add succeeds  add_changeset_property() links a new property of a not-yet-live target node into the node's deadprops list before handing it to of_changeset_add_property(). If that fails, the error path frees the property but leaves the freed pointer linked in deadprops, and of_node_release() frees it a second time when the aborted overlay's node is released.  Record the changeset entry first and link the property into deadprops only on success. of_changeset_add_property() never looks at the node's property lists, so the order of the two steps is otherwise immaterial, and the error path frees a property that nothing references.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98862",
                        "url": "https://ubuntu.com/security/CVE-2026-98862",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  audit: fix exe mark UAF in kill_rules()  kill_rules() removes mixed AUDIT_DIR and AUDIT_EXE rules when an audit tree is pruned. It drops entry->rule.exe before removing the rule from the RCU-visible filter lists.  After a rule has been installed with AUDIT_ADD_RULE, which requires CAP_AUDIT_CONTROL, removing the watched directory can race with another task that is still evaluating the rule. In that case, fsnotify can free the executable mark before the reader reaches audit_mark_compare(), causing a use-after-free.  KASAN reports:      BUG: KASAN: slab-use-after-free in audit_mark_compare+0x8d/0xa0  Unlink the published rules from the RCU-visible lists and retain them on tree->rules for cleanup. If any rule has an executable mark, wait for a single RCU grace period before removing the marks and scheduling the entries for freeing. Otherwise, call_rcu() already provides the required deferred freeing without a synchronous wait.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98450",
                        "url": "https://ubuntu.com/security/CVE-2026-98450",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  smb: client: close completed creates on compound wait errors  compound_send_recv() waits for responses in order. If a later wait is interrupted, or if a later MID fails during response synchronization, an earlier CREATE may already have opened a remote handle. The earlier mid is then released without invoking handle_cancelled_mid(), leaving the remote handle open because no FID was copied to the caller.  Mark completed earlier mids as cancelled when a compound wait or MID synchronization aborts. Keep their response buffers attached while the MIDs are synchronized, and transfer them only after synchronization of the processed responses, so the release path can inspect successful CREATE responses and queue SMB2_close() after a later failure. Account for a remote open only after the close work is allocated and before it is queued, since the caller has not yet updated num_remote_opens. Mark the create+close compound used by smb2_unlink() so it is not closed again. Non-CREATE responses and compounds that already include a close keep their existing behavior.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:16:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98502",
                        "url": "https://ubuntu.com/security/CVE-2026-98502",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  HID: alps: unregister DualPoint Stick input device on remove  alps_input_configured() allocates a second input device (\"DualPoint Stick\") with input_allocate_device() and registers it, but the alps_driver struct has no .remove handler and input2 is not tracked in hdev->inputs.  The default remove path (hid_hw_stop -> hidinput_disconnect) only iterates hdev->inputs, so input2 is never unregistered and leaks on every device removal.  Add a .remove handler that stops the device first (preventing URB callbacks from touching input2 during teardown) and then unregisters input2.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98456",
                        "url": "https://ubuntu.com/security/CVE-2026-98456",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  Bluetooth: mgmt: fix race in read_unconf_index_list()  read_unconf_index_list() counts unconfigured controllers before allocating its response, then checks the device flags again while filling it.  hci_dev_list_lock stabilizes list membership, but it does not serialize the per-device flags. During asynchronous controller setup, the worker can set HCI_UNCONFIGURED and clear HCI_SETUP between the two passes. A controller omitted from the allocation count can then become eligible for the fill pass, causing an out-of-bounds write to rp->index[].  Allocate space for every device on hci_dev_list. Since list membership cannot change while hci_dev_list_lock is held, the response remains large enough regardless of flag transitions. The reported count and response length still include only eligible unconfigured controllers.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-18 16:16:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98451",
                        "url": "https://ubuntu.com/security/CVE-2026-98451",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  smb: client: use finish_no_open() for non-regular inodes  An O_CREAT open can find an existing symlink or another non-regular inode. cifs_atomic_open() calls finish_open() on it and attaches a cifsFileInfo. Symlink inodes have no CIFS release operation, so the dentry reference held by cifsFileInfo is leaked. FMODE_OPENED also prevents the VFS from following the symlink.  Track whether cifs_do_create() returned an open server handle. For non-regular inodes, close the handle if present, remove the pending open, and call finish_no_open() so the VFS can continue the lookup. Do not set FMODE_CREATED unless a regular file was opened. For O_NOFOLLOW with __O_REGULAR, return -ELOOP before the VFS's -EFTYPE check.  Defer closing a legacy POSIX handle on a non-regular inode until after inode lookup. This avoids closing it again if lookup fails.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-18 16:16:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98484",
                        "url": "https://ubuntu.com/security/CVE-2026-98484",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  netfilter: nf_tables: skip expired catchall elements on insert and delete  nft_setelem_catchall_insert() looks up duplicates with nft_set_elem_active() only, while nft_set_catchall_lookup() and the dump path additionally skip expired elements.  Once a catchall element with a timeout expires, this predicate drift makes it invisible to userspace dumps, yet it still blocks re-insertion: with NLM_F_EXCL the request fails with -EEXIST, and without it the request reports success but silently inserts nothing. The stale entry only goes away when the (user-tunable) gc interval elapses, so the catchall rule may silently stop matching for an arbitrarily long time after its first expiration.  The delete path shows the same drift: nft_setelem_catchall_deactivate() picks the first active-next entry in the catchall list, so with an expired entry still pending GC it retires the stale entry instead of the fresh one, and it deactivates an element that userspace no longer sees instead of failing with -ENOENT.  Align both walks with the lookup and dump predicates: only an element that is active and not expired counts as a duplicate or delete candidate, using the per-netns timestamp taken at transaction start, in line with the set backend .insert/.deactivate and catchall GC sync paths.",
                        "cve_priority": "negligible",
                        "cve_public_date": "2026-10-18 16:16:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98486",
                        "url": "https://ubuntu.com/security/CVE-2026-98486",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net: ena: fix MMIO read buffer leak on probe failure  ena_device_init() initializes the MMIO read mechanism with ena_com_mmio_reg_read_request_init(), which allocates a coherent DMA buffer for MMIO read responses.  The normal removal path releases this buffer through ena_com_mmio_reg_read_request_destroy(). However, if ena_probe() fails after ena_device_init() succeeds, the error path destroys the admin resources and eventually frees ena_dev without destroying the MMIO read request, leaving the coherent DMA buffer allocated.  Call ena_com_mmio_reg_read_request_destroy() in the probe error path before releasing the remaining device resources.  This issue was found by manual code inspection.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:16:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98493",
                        "url": "https://ubuntu.com/security/CVE-2026-98493",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net: ipconfig: bound DHCP option construction  ic_dhcp_init_options() appends the hostname (option 12), vendor-class (option 60) and client-ID (option 61) options into the fixed 312-byte bootp_pkt.exten[] buffer.  Only the client-ID branch checked the remaining space; the hostname and vendor-class writes were unbounded.  A 64-byte hostname together with the maximum 252-byte dhcpclass= identifier needs 18 + (2 + 64) + (2 + 252) = 338 of the 312 available bytes even before the terminating END marker, so the vendor-class memcpy runs past the end of exten[].  With CONFIG_FORTIFY_SOURCE this is reported as a field-spanning write and, when the kernel is booted with panic_on_warn=1, aborts boot with a panic.  Route the optional options through a common helper that makes sure the option, its 2-byte header and the END marker all fit and drops an option that would not.  Configurations with short options keep sending exactly the same bytes as before.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98454",
                        "url": "https://ubuntu.com/security/CVE-2026-98454",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  smb: client: fix create context out-of-bounds reads  smb2_parse_contexts() validates the complete create-context area but does not limit each record to its Next field before dispatching it.  A malformed chain can therefore expose bytes beyond the current context to a handler.  The QFid handler also used a full response-structure cast although it only reads DiskFileId.  The SMB2/SMB3 lease parsers made the same layout assumption: they read LeaseState and LeaseFlags at canonical offsets rather than at DataOffset.  A valid non-canonical DataOffset could therefore yield unrelated in-bounds data, while a short DataLength was still accepted.  Limit each context to its Next value, reject offsets before the context header, and reject malformed chains.  Bound the name range by the current context and do not dispatch a known handler when DataLength is zero.  Read the QFid DiskFileId only when the context data covers that field.  Parse the lease context from DataOffset and require DataLength to match the v1 or v2 lease_context size used by ksmbd.  A size mismatch skips lease parsing without failing the open.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-18 16:16:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98490",
                        "url": "https://ubuntu.com/security/CVE-2026-98490",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net: openvswitch: conntrack: fix helper UAF due to extensions realloc  While calling the helpers, a raw pointer to the extensions area is wired into expectations list:    -> nf_ct_helper()    -> helper->help()     -> nf_ct_expect_related_report()      -> nf_ct_expect_insert()       -> hlist_add_head_rcu(&exp->lnode, &master_help->expectations)  In case the connection is not confirmed yet, more extensions can be added afterwards with *_ext_add() calls reallocating the extension space and leaving the now invalid pointer in the expectations list that is later accessed while removing the expectation.  Make sure that helpers are called at the end after all the other extensions are already added.  Note that the helper rejection now leaves the mark and labels set, but that's not different from how the NAT was handled before or how the mark and the labels were handled on confirmation failure.  And there are no atomicity guarantees provided by the API anyway.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-18 16:16:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98507",
                        "url": "https://ubuntu.com/security/CVE-2026-98507",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  mm/rmap: fix missing barrier between anon_vma init and vma->anon_vma publish  On arm64 server, we find that a task trying to grab the anon_vma lock triggers hungtask.  INFO: task main:2354726 blocked for more than 120 seconds.       Tainted: G            E     5.10.0-0021.aarch64 #1 \"echo 0 > /proc/sys/kernel/hung_task_timeout_secs\" disables this message. task:main            state:D stack:    0 pid:2354726 ppid:2350673 flags:0x00000a01 Call trace:  __switch_to+0x7c/0xbc  __schedule+0x3b4/0x8a0  schedule+0x50/0xe0  rwsem_down_write_slowpath+0x3cc/0x6cc  down_write+0x60/0x260  __anon_vma_prepare+0x6c/0x210  do_anonymous_page+0x258/0x660  handle_pte_fault+0x188/0x214  __handle_mm_fault+0x1b0/0x380  handle_mm_fault+0xf4/0x284  do_page_fault+0x19c/0x494  do_translation_fault+0xcc/0xf8  do_mem_abort+0x48/0xac  el0_da+0x44/0x80  el0_sync_handler+0x88/0xb4  el0_sync+0x160/0x180  After analyzing the vmcore, we found the anon_vma->root->rwsem.count is -1.  There is another anon_vma whose anon_vma->root->rwsem.count is 1, the anon_vma->root->rwsem.owner shows the lock is held, but the stack of the task shows the task doesn't hold the anon_vma lock.  After adding more debugging info, we found __anon_vma_prepare() reuses anon_vma and triggers the UAF of anon_vma->root due to missing memory barrier, leading to locking and unlocking two different anon_vma->root, thus leading to an anon_vma will never be unlocked, and another anon_vma couldn't be locked anymore.  This race requires two adjacent VMAs that are not merged but are anon_vma-compatible (e.g., they differ in VMA_ACCESS_FLAGS that can be changed by mprotect()).  Two threads fault on each VMA concurrently, both calling __anon_vma_prepare() with only mmap_lock held for reading.      THREAD A                             THREAD B __anon_vma_prepare                __anon_vma_prepare  find_mergeable_anon_vma() -> NULL  anon_vma = anon_vma_alloc();    anon_vma->root = anon_vma;  // the two stores may be reordered  vma->anon_vma = anon_vma;                                    // finds A's anon_vma                                    anon_vma = find_mergeable_anon_vma(vma);                                    anon_vma_lock_write(anon_vma);                                      // may still see the old root                                      down_write(&anon_vma->root->rwsem);                                    anon_vma_unlock_write(anon_vma);                                      // see the new root, never unlock old                                      up_write(&anon_vma->root->rwsem);  thread A triggers page fault and calls __anon_vma_prepare() to prepare anon_vma for the faulting vma.  __anon_vma_prepare() allocates and initializes a new anon_vma, and then publishes it to the vma with a plain store.  anon_vma_prepare() only requires the mmap_lock to be held for reading, so two threads can fault on adjacent VMAs at the same time. While thread A publishes a new anon_vma, thread B could find the anon_vma via find_mergeable_anon_vma() and then locks anon_vma->root->rwsem.  The store to anon_vma->root in anon_vma_alloc() and the store to vma->anon_vma can be reordered.  The anon_vma_lock_write() and spin_lock() only provide acquire semantics, which do not prevent prior stores from being reordered after them.  The release semantics of the corresponding spin_unlock() and anon_vma_unlock_write() come too late, the store to vma->anon_vma is already published before they take effect.  As a result, thread B can observe the following order:      vma->anon_vma = anon_vma;     anon_vma->root = anon_vma;  The anon_vma slab is SLAB_TYPESAFE_BY_RCU, so a newly allocated anon_vma may reuse memory from a previously freed one.  The constructor (anon_vma_ctor) does not reset anon_vma->root, and __put_anon_vma() doesn't clear it either, so the old root value persists until anon_vma_alloc() overwrites it.  If that store isn't v ---truncated---",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98519",
                        "url": "https://ubuntu.com/security/CVE-2026-98519",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  drm/amdgpu: Fix runtime PM leak in amdgpu_debugfs_test_ib_show()  amdgpu_debugfs_test_ib_show() resumes the device with pm_runtime_get_sync() before taking the reset domain semaphore with down_write_killable().  If the write lock acquisition is interrupted, the function returns without calling pm_runtime_put_autosuspend(), leaking the runtime PM reference acquired for the device and keeping the GPU awake.  Drop the runtime PM reference on the interrupted down_write_killable() error path before returning.  (cherry picked from commit ec30a576c2d4c0364549e6c04218f50704ef56c8)",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98549",
                        "url": "https://ubuntu.com/security/CVE-2026-98549",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  tcp: prevent collapsing skbs across boundary in rtx queue  tcp_write_collapse_fence() sets TCP_SKB_CB(skb)->eor = 1 on tcp_write_queue_tail(sk) to prevent skbs queued after a switch to device encryption from being collapsed into earlier skbs.  The fence is a no-op if all earlier data has already been transmitted when the switch happens: sk->sk_write_queue is empty. The not yet acknowledged earlier skbs wait in sk->tcp_rtx_queue with eor 0.  On a subsequent retransmit or SACK shift, tcp_retrans_try_collapse() or tcp_shift_skb_data() can then merge an skb queued after the switch into one queued before it.  Both users of the fence are affected:  - psp: devices only encrypt skbs with skb->decrypted set. The merged skb   keeps decrypted = 0 from the earlier skb, so merged data sent after   psp_sock_assoc_set_tx() is retransmitted in cleartext.  - tls device offload: the merged skb straddles the start marker set in   tls_set_device_offload(). The software fallback (fill_sg_in() returns   -EINVAL) and the mlx5, nfp and funeth drivers cannot handle such an   skb and drop it. Every retransmit rebuilds the same skb, so the   connection stalls.  Fix this in two places, for defense in depth:  1. Fall back to tcp_rtx_queue_tail(sk) in tcp_write_collapse_fence()    when tcp_write_queue_tail(sk) is NULL.  2. Check !skb_cmp_decrypted(to, from) in tcp_skb_can_collapse(), as    tcp_skb_can_collapse_rx() does on receive. skb_shift(), which both    collapse paths call, already has a DEBUG_NET_WARN_ON_ONCE() for this    condition.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98544",
                        "url": "https://ubuntu.com/security/CVE-2026-98544",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  bna: prevent IOC timer rearm during teardown  bna: prevent IOC timer rearm during teardown  bnad_pci_remove() and the probe disable_ioceth path call timer_delete_sync() for ioc_timer, sem_timer and hb_timer, but not for iocpf_timer.  bnad_iocpf_timeout() then takes bnad->bna_lock after free_netdev() has freed the struct bnad.  Deleting iocpf_timer last does not fix this.  sem_timer and iocpf_timer rearm each other: bnad_iocpf_sem_timeout() can arm iocpf_timer, and bnad_iocpf_timeout() arms sem_timer from bfa_ioc_hw_sem_get() when the semaphore is busy. timer_delete_sync() only waits out its own callback. bnad_ioceth_disable() can time out and leave that callback live.  Shut all four IOC timers down with timer_shutdown_sync() on both paths, so a later mod_timer() is ignored.  This issue was identified during our ongoing static-analysis research while reviewing kernel code.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-18 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98172",
                        "url": "https://ubuntu.com/security/CVE-2026-98172",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  smb: client: fix smbd_connection leak on cifs_get_tcp_session() error  When an RDMA connection is successfully established via smbd_get_connection() but cifs_get_tcp_session() later fails (e.g. kthread_create() returns an error), the error path frees tcp_ses without first destroying the smbd_connection.  Fix this by calling smbd_destroy() in the out_err cleanup path before kfree(tcp_ses).  smbd_destroy() safely handles the case where smbd_conn is NULL, so it can be called unconditionally.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-06 09:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98192",
                        "url": "https://ubuntu.com/security/CVE-2026-98192",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: wcn36xx: Fix potential use-after-free in TX ack timer teardown  wcn36xx_dxe_deinit() tears down the TX ack timer with timer_delete(), which only dequeues the timer and does not wait for a callback that is already executing; the preceding free_irq() calls synchronize the interrupt handlers only. The callback, wcn36xx_dxe_tx_timer(), can therefore be running past the teardown and use the wcn freed along with the ieee80211_hw in wcn36xx_remove(): it takes wcn->dxe_lock, reads wcn->tx_ack_skb and passes wcn->hw to ieee80211_tx_status_irqsafe().  Fix this by using timer_shutdown_sync(), which waits for a running callback and also prevents the timer from being rearmed again. The timer is set up again by wcn36xx_dxe_init() on the next start, so the start/stop cycle is unaffected.  This issue was found by an in-house static analysis tool.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-06 09:18:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98198",
                        "url": "https://ubuntu.com/security/CVE-2026-98198",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  hwmon: (pwm-fan) Stop RPM timer before freeing tach data  sample_timer() rearms the RPM timer and accesses the devm-managed ctx->tachs and ctx->pulses_per_revolution arrays. The cleanup action which stops the timer is registered before those arrays are allocated.  Since devres releases entries in reverse order, driver detach can free the arrays before pwm_fan_cleanup() shuts down the timer. A timer expiry in that window accesses the freed tach data.  With a KASAN kernel, a test-only kprobe delayed entry to pwm_fan_cleanup() while normal sysfs unbind ran. Each of three runs reported three four-byte reads and two four-byte writes in sample_timer() after its backing devm allocations had been freed. The helper did not invoke the timer callback, cleanup actions or free functions.  With the fix, three matching unbind runs completed without KASAN, BUG, WARNING, Oops or panic. Instrumentation confirmed that timer retirement completed before the first timer backing allocation was released.  Split timer retirement from the power cleanup and register its devres action after the timer backing data and IRQ actions are installed. This preserves the early power rollback action while ensuring the timer is retired before its backing data is released. Use timer_shutdown_sync() because the callback can rearm itself.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-06 09:18:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98409",
                        "url": "https://ubuntu.com/security/CVE-2026-98409",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  watchdog: rtd119x: Avoid division by zero  clk_get_rate() could return 0.  Avoid a division by zero panic.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-14 14:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98245",
                        "url": "https://ubuntu.com/security/CVE-2026-98245",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  btrfs: take commit root semaphore when iterating in mark_block_group_to_copy()  mark_block_group_to_copy() iterates over the commit root with skip_locking=true. A concurrent transaction commit can swap and free the commit root during iteration, causing use-after-free when accessing extent buffers.  Fix it by using path->need_commit_sem to protect the commit root search.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-06 09:18:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98264",
                        "url": "https://ubuntu.com/security/CVE-2026-98264",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ALSA: virtio: reset device before deleting virtqueues  virtsnd_remove() and virtsnd_freeze() delete the virtqueues before resetting the device. del_vqs() frees the vring backing, but does not provide a generic device quiesce operation. In particular, modern virtio-pci keeps enabled queues active until the device is reset.  Reset the device before deleting the virtqueues so it can no longer access the vring memory when that memory is released. This also covers probe failures after DRIVER_OK, which unwind through virtsnd_remove().",
                        "cve_priority": "low",
                        "cve_public_date": "2026-10-06 09:18:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-97558",
                        "url": "https://ubuntu.com/security/CVE-2026-97558",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  smb: client: fix cifsFileInfo reference leak in deferred close  When cifs_close() defers a close, it hands the cifsFileInfo reference of the closing struct file to the queued work. Each execution of smb2_deferred_work_close() drops one such reference.  deferred_close_scheduled can be false while the work is pending: the workqueue clears PENDING when the callback starts to run, before the callback clears the flag under deferred_lock. A close in that interval requeues the running work, and the callback then clears the flag, leaving the requeued work pending with the flag down. A later cifs_open() can reuse the handle and its cifs_close() reaches the same branch: queue_delayed_work() fails because the work is still pending, but cifs_close() returns without dropping the closing file's reference. The cifsFileInfo count stays pinned and its tlink, dentry and server handle are leaked.  Check the return value and hand off the reference only when work was actually queued. Otherwise, use the shared _cifsFileInfo_put(), like the mod_delayed_work() branch above: the pending execution already owns its reference.  This issue was found by an in-house static analysis tool.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-09-25 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-97616",
                        "url": "https://ubuntu.com/security/CVE-2026-97616",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net/sched: act_api: release all action references on NEWACTION failure  When a batched RTM_NEWACTION request replaces an existing action, tcf_idr_check_alloc() takes a temporary reference on it. If a later action fails to initialize, tcf_action_destroy() uses strict release semantics to clean up the actions initialized so far. For an action bound to a filter, the strict check returns -EPERM without dropping the temporary reference.  This error also makes tcf_action_destroy() return before releasing subsequent entries. Any new action initialized between the bound action and the failing entry is leaked together with its reserved IDR slot, preventing reuse of its index.  Use tcf_idr_release() to drop each reference held by the batch without rejecting bound actions. This allows cleanup to continue through all initialized entries and preserves the module reference release when an action is destroyed. Explicit action deletion and flushing retain their separate bind-count checks.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-09-25 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-97939",
                        "url": "https://ubuntu.com/security/CVE-2026-97939",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ipmr: account multicast table and route memory  A netadmin in a user+net namespace can create many IPv4 and IPv6 multicast routing tables with MRT_TABLE and MRT6_TABLE. Each unseen id allocates an mr_table via the shared mr_table_alloc(), links it into the per-net list, and leaves it until netns teardown. Those objects were not charged to memcg, so the host unreclaimable slab grows with the table count.  Account mr_table allocations with GFP_KERNEL_ACCOUNT and mark the IPv4/IPv6 MFC caches SLAB_ACCOUNT. This matches the established handling of IP addresses, routes and alternate interface names.  Unresolved MFC entries are still allocated from softIRQ with GFP_ATOMIC and are not charged. They expire after 10 seconds and are bounded by the socket receive queue; see commit 0079ad8e8dc3 (\"ipmr: remove hard code cache_resolve_queue_len limit\").",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-09-25 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-89837",
                        "url": "https://ubuntu.com/security/CVE-2026-89837",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  f2fs: fix dentry folio leak in find_in_level  find_in_level() gets a dentry folio with f2fs_find_data_folio() before calling find_in_block().  If find_in_block() returns an error, the function stores the error in res_folio and breaks out of the loop without dropping the dentry folio.  This leaks the folio reference on the find_in_block() error path.  Drop the dentry folio before returning the error to the caller.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-09-16 11:16:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-89838",
                        "url": "https://ubuntu.com/security/CVE-2026-89838",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  f2fs: limit recovery filename logging to stored length  F2FS stores recovery filenames as a length plus a fixed-size i_name buffer.  The buffer is not NUL-terminated, but recover_inode() and recover_dentry() print it with %s.  For a 255-byte filename, recovery logging can read past i_name into the following raw inode fields.  Print the name with a precision bounded by i_namelen and F2FS_NAME_LEN.",
                        "cve_priority": "negligible",
                        "cve_public_date": "2026-09-16 11:16:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-97530",
                        "url": "https://ubuntu.com/security/CVE-2026-97530",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  scsi: qla2xxx: Fix soft lockup polling continuation IOCB signature  qla27xx_copy_multiple_pkt() and qla27xx_copy_fpin_pkt() poll rsp_q->ring_ptr->signature for RESPONSE_PROCESSED (0xDEADDEAD) to decide whether the next continuation IOCB has arrived, spinning on cpu_relax() without advancing the ring or decrementing the entry count while it has not. response_t::signature lives at byte offset 60, but a continuation IOCB (sts_cont_entry_t / struct sts_cont_entry_ext) carries raw FC frame payload at that offset (data[56..59]). A received frame whose payload bytes happen to equal 0xDEADDEAD is therefore misread as \"not yet arrived\", and the loop spins forever in interrupt/DPC context, causing a CPU soft lockup.  The poll is also unnecessary: callers of qla27xx_copy_multiple_pkt() (PT_LS4_UNSOL and the NVMe purls path) already gate on qla_chk_cont_iocb_avail(), which guarantees all entry_count IOCBs are present before copying begins. The sibling helper __qla_copy_purex_to_buffer() already drops the signature poll and relies on the entry_type == STATUS_CONT_TYPE guard instead.  Remove the signature busy-wait from both helpers, keeping the entry_type guard, and gate the FPIN path with qla_chk_cont_iocb_avail() so it defers and re-processes on the next interrupt once all continuation IOCBs have arrived, mirroring the ELS_AUTH_ELS and PT_LS4_UNSOL arms. With this the signature field is never read on a continuation IOCB, eliminating the payload-aliasing lockup.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-09-25 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98386",
                        "url": "https://ubuntu.com/security/CVE-2026-98386",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  scsi: qla2xxx: Use memset_io() to clear QLAFX00 request ring slot  For QLAFX00 the request ring is ioremapped device I/O memory (ha->iobase + req_que_off), not DMA-coherent RAM, which is why the rest of the FX00 path accesses it through memcpy_toio() and the wrt_reg_* helpers. __qla2x00_alloc_iocbs() however zeroed the producer slot with a plain memset(). On architectures such as ARM64 a regular memset() may emit unaligned or block-zeroing instructions (e.g. DC ZVA) that are invalid on Device memory, leading to a synchronous external abort.  Use memset_io() to clear the slot for QLAFX00, matching the I/O accessors used elsewhere on this ring. Other adapters keep the plain memset() on their DMA-coherent rings. The zero-fill is retained for FX00 because its IOCB builders (e.g. qlafx00_fxdisc_iocb()) copy only part of the entry and rely on the unused tail being pre-zeroed.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-14 14:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-89848",
                        "url": "https://ubuntu.com/security/CVE-2026-89848",
                        "cve_description": "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_work, and qla_do_work() -> qla24xx_process_response_queue() dereferences the now-freed rsp->req (LOGINOUT/CT/ELS entries and the status path), a use-after-free.  The cancel_work_sync() added for the qpair teardown lives in the response free path, which runs after the request queue is already freed, so it does not protect rsp->req.  Release the response-queue interrupt and flush qpair->q_work before deleting the request queue, so no late completion can reach the freed request queue. Clearing have_irq makes the subsequent qla25xx_free_rsp_que() skip its free_irq(), and the firmware queue-delete order (request then response) is preserved; the request-delete mailbox completes on the default vector and is unaffected by dropping the qpair response interrupt early.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-09-16 11:16:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-97532",
                        "url": "https://ubuntu.com/security/CVE-2026-97532",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  scsi: qla2xxx: Null out freed pointers in qla2x00_mem_alloc() error path  When qla2x00_mem_alloc() fails, qla2x00_probe_one() jumps to probe_hw_failed and calls qla2x00_mem_free(). Several error labels in qla2x00_mem_alloc() freed adapter members (elsrej.c, purex_dma_pool, flt, sfp_data, loop_id_map, async_pd, sf_init_cb, ex_init_cb, npiv_info) but left the pointers dangling. qla2x00_mem_free() then freed them a second time. Worse, for the dma_pool members it issued dma_pool_free(ha->s_dma_pool, ...) after s_dma_pool had already been destroyed and set to NULL at fail_s_dma_pool, dereferencing a NULL pool.  Clear each freed pointer (and its DMA handle) in the error labels so the subsequent qla2x00_mem_free() skips them.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-09-25 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-89877",
                        "url": "https://ubuntu.com/security/CVE-2026-89877",
                        "cve_description": "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 existing MMIO mapping error path to remove the device from saa7164_devlist and decrement the device count before returning.  Also release BAR0 if it was successfully requested but the BAR2 request fails.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-09-16 11:16:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-93239",
                        "url": "https://ubuntu.com/security/CVE-2026-93239",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  arm64: mm: Fix the lockless page-table walk in show_pte()  show_pte() walks page tables locklessly and can run with interrupts enabled. A concurrent teardown can free a table page while it is being walked. It can also clear a parent entry after show_pte() checked it; the regular pXd_offset() helpers then reread the cleared entry and can derive a bogus lower-level pointer and fault again.  Use the lockless offset helpers with the saved parent entries, as gup_fast() does, and pass the saved PMD to pte_offset_map().  For task page tables, arm64 selects MMU_GATHER_RCU_TABLE_FREE. Disable local interrupts around the walk to hold off RCU-deferred table frees and block the tlb_remove_table_sync_one() IPI until the walk is finished.  Place the IRQ guard after the header print. This does not make the output a consistent snapshot, but prevents the task page-table walk from dereferencing a released table page or deriving a pointer from a different parent value.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-09-24 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-90023",
                        "url": "https://ubuntu.com/security/CVE-2026-90023",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  usb: gadget: f_mass_storage: fix null pointer dereference in fsg_common_set_num_buffers()  Previously fsg_num_buffers_validate() was removed as it was not necessary due to Kconfig setting the limits for n from 2 to 256 with default as 2. However, setting the page content in such a way that kstrtou8() reflects n value as either 0 or 1 bypasses these restrictions leading to a null pointer dereference if n is 0. Fix this by adding a check for n < 2 and returning -EINVAL if n is either 0 or 1 consistent with Kconfig logic.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-09-16 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-93200",
                        "url": "https://ubuntu.com/security/CVE-2026-93200",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  i3c: master: Fix use-after-free of master->this  sysfs attribute callbacks for the master controller device dereference master->this.  However, master->this is freed in i3c_master_detach_free_devs() before the master device itself is released.  As a result, sysfs accesses can dereference a freed master->this pointer, leading to a use-after-free.  Keep master->this alive until i3c_masterdev_release(), which is called after the master device and its sysfs state are being torn down. Do not free master->this as part of the normal device detach path.  On the error path in i3c_master_set_info(), reset master->this and bus.cur_master to NULL before freeing the allocated device.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-09-17 17:18:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-93199",
                        "url": "https://ubuntu.com/security/CVE-2026-93199",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  i3c: master: Do not treat master device as a duplicate target  i3c_master_search_i3c_dev_duplicate() searches the bus for another I3C device with the same PID as the reference device.  The search can match master->this, causing the controller itself to be returned as a duplicate.  Since the controller is not a target device, it cannot be a duplicate of one.  Exclude master->this from matching so that the function only returns real duplicate target devices.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-09-17 17:18:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-89441",
                        "url": "https://ubuntu.com/security/CVE-2026-89441",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  mmc: via-sdmmc: cancel card-detect work on remove  Disabling the device interrupt and freeing the IRQ prevents new card-detect work from being queued, but carddet_work already queued by the handler can still run after via_sd_remove() returns. via_sdc_card_detect() recovers the host through container_of() and dereferences its MMIO base; once remove() returns the host can be freed, so that work would touch freed memory.  Cancel carddet_work after freeing the IRQ and before cancelling finish_bh_work, which the card-detect handler can also queue. carddet_work can re-enable the interrupt through via_reset_pcictrl(); mask it again afterwards.  This issue was found by an in-house static analysis tool and confirmed by manual code review.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-09-11 20:19:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-89465",
                        "url": "https://ubuntu.com/security/CVE-2026-89465",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  power: supply: rt9455: quiesce delayed work before teardown  The threaded IRQ handler can queue pwr_rdy_work, max_charging_time_work and batt_presence_work.  pwr_rdy_work and batt_presence_work can also queue max_charging_time_work, while batt_presence_work can requeue itself.  rt9455_remove() cancels max_charging_time_work before batt_presence_work.  The latter can therefore queue max_charging_time_work after it has already been cancelled:    rt9455_remove()                   workqueue     cancel pwr_rdy_work     cancel max_charging_time_work                                       batt_presence_work queues                                         max_charging_time_work     cancel batt_presence_work     return     devres frees rt9455_info                                       max_charging_time_work dereferences                                         rt9455_info  The IRQ also remains registered until devres cleanup and can queue more work after any of the cancellation calls.  If rt9455_hw_init() fails after the IRQ has been requested, probe returns without cancelling work that may already have been queued.  A pending callback can then access rt9455_info after it has been freed.  Register rt9455_cancel_all_delayed_works() through devm_add_action_or_reset() right after devm_power_supply_register(). devres invokes the action in reverse registration order, after the managed IRQ has been freed and before rt9455_info is released, so the delayed works are drained in both rt9455_remove() and the probe error path.  Cancel pwr_rdy_work and batt_presence_work before max_charging_time_work because both can queue the latter.  This issue was found by an in-house static analysis tool.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-09-11 20:19:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-93231",
                        "url": "https://ubuntu.com/security/CVE-2026-93231",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  lockd: fix swapped arguments in nlmsvc_match_ip()  When releasing locks by server IP address via /proc/fs/nfsd/unlock_ip, nlmsvc_unlock_all_by_ip() calls nlm_traverse_files() with the server sockaddr as the opaque @data argument:  \tnlm_traverse_files(server_addr, nlmsvc_match_ip, NULL);  The match callback is later invoked from nlm_traverse_locks() as:  \tmatch(lockhost, host);  where the first argument is the nlm_host that owns the lock, and the second argument is the @data that was originally passed down (here the server sockaddr).  This is the convention every other match callback relies on (nlmsvc_mark_host(), nlmsvc_same_host(), nlmsvc_is_client()): arg1 is the real nlm_host, arg2 is the caller-supplied reference value.  nlmsvc_match_ip() has had these two arguments reversed ever since the unlock-by-IP feature was introduced in commit 4373ea84c84d (\"lockd: unlock lockd locks associated with a given server ip\"):  \treturn rpc_cmp_addr(nlm_srcaddr(host), datap);  Here @host is actually the server sockaddr, so nlm_srcaddr(host) dereferences a struct sockaddr as a struct nlm_host and reads garbage at the offset of h_srcaddr; meanwhile @datap is actually the lock owner's nlm_host but is compared as a sockaddr.  As a result the comparison practically never matches and locks are not released for the requested IP.  Swap the arguments so the lock owner's source address is compared against the requested server address:  \treturn rpc_cmp_addr(nlm_srcaddr(datap), (struct sockaddr *)host);  [ cel: fix the misleading typedef parameter names too ]",
                        "cve_priority": "low",
                        "cve_public_date": "2026-09-24 16:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-89552",
                        "url": "https://ubuntu.com/security/CVE-2026-89552",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  params: fix charp corruption on allocation failure  param_set_charp() stores charp parameters in allocated memory after slab is available, and releases the previous value when the parameter is updated.  The previous value is released before the replacement allocation succeeds. If kmalloc_parameter() fails, the setter returns -ENOMEM with the parameter left as NULL.  Failing zswap's compressor update before zswap is initialized can later trigger:    BUG: kernel NULL pointer dereference, address: 0000000000000000   RIP: 0010:strcmp+0x10/0x30   Call Trace:     zswap_setup+0x3b1/0x490     zswap_enabled_param_set+0x5b/0xa0     param_attr_store+0x93/0xe0     module_attr_store+0x1c/0x30     kernfs_fop_write_iter+0x116/0x1f0  Allocate and copy the replacement first, then replace the parameter value only after allocation succeeds.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-09-11 20:19:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-89640",
                        "url": "https://ubuntu.com/security/CVE-2026-89640",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  cifs: fix loff_t underflow in cifs_remap_file_range() when len == 0  With len == 0 (clone to EOF), the effective length is computed as:      len = src_inode->i_size - off;  If off > i_size, this is a negative loff_t, corrupting the ByteCount in the FSCTL_DUPLICATE_EXTENTS_TO_FILE request and inverting the range in filemap_write_and_wait_range().  The existing off >= i_size check fires only after the ioctl has already been sent.  Snapshot i_size_read() once for both the bounds check and the length calculation, eliminating the TOCTOU and 32-bit torn-read risk.  Reject off > src_size with -EINVAL.  Treat off == src_size as a no-op, consistent with __generic_remap_file_range_prep().",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-09-11 20:19:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-89672",
                        "url": "https://ubuntu.com/security/CVE-2026-89672",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  nfsd: gate nfs2 setacl by argp->mask  The NFSACL v2 SETACL path shares the decoder convention used by its v3 sibling: nfsaclsvc_decode_setaclargs() fills in argp->acl_access only when NFS_ACL is set in the request mask and argp->acl_default only when NFS_DFACL is set, leaving the other pointer NULL because the argument buffer is zeroed up to pc_argzero before decode.  nfsacld_proc_setacl() then hands both pointers to set_posix_acl() unconditionally. set_posix_acl(idmap, dentry, type, NULL) is the VFS \"remove this ACL type\" operation, so an omitted arm is indistinguishable from an explicit request to delete that ACL. A SETACL carrying only NFS_ACL silently strips the directory's default ACL; mask=0 strips both.  This is the same defect just fixed in nfsd3_proc_setacl(); apply the same remedy. Gate each set_posix_acl() call on its mask bit and initialize error to 0 so that a request with neither bit set leaves the on-disk ACLs untouched and returns success. The out_drop_lock path and the unconditional posix_acl_release() in nfsaclsvc_release_setacl() already tolerate the skipped arms.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-09-11 20:19:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-89685",
                        "url": "https://ubuntu.com/security/CVE-2026-89685",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  nfsd: fix clock domain mismatch in clients_still_reclaiming()  clients_still_reclaiming() computes a deadline from nn->boot_time (CLOCK_REALTIME, ~1.7 billion) but compares it against ktime_get_boottime_seconds() (CLOCK_BOOTTIME, seconds since boot). The comparison is always false — it would take ~54 years of uptime for BOOTTIME to exceed the REALTIME-derived deadline.  This means any client can hold the server in grace indefinitely by sending CLAIM_PREVIOUS OPEN requests, blocking all non-reclaim operations for all other clients.  Add boot_time_bt (CLOCK_BOOTTIME) alongside the existing boot_time and use it for the deadline computation. boot_time (CLOCK_REALTIME) is preserved for its cl_boot clientid-nonce role.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-09-11 20:19:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-89707",
                        "url": "https://ubuntu.com/security/CVE-2026-89707",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  nfsd: release path refs on follow_down() error  nfsd_cross_mnt() initializes a local struct path with mntget() and dget() before calling follow_down(). On a negative return the error arm jumps to out without releasing those references:      err = follow_down(&path, follow_flags);     if (err < 0)             goto out;  follow_down() never drops the caller's entry-time refs on any error sub-case; for example a pre-cross d_manage() failure leaves path untouched, so the mntget()/dget() taken on entry survive the call.  Every other early-exit arm in nfsd_cross_mnt() (other-namespace return, IS_ERR(exp2), and the success tail after the swap) already calls path_put(&path); the err < 0 arm is the lone omission. The leak inflates mnt_count and d_count on each failed cross-mount, blocking umount and pinning dentries against the shrinker, and is reachable by any authenticated NFS client through nfsd_lookup_dentry or the NFSv4 READDIR encode path.  Fix by calling path_put(&path) before the goto out in the err < 0 arm so the entry-time refs are released on all follow_down() error returns.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-09-11 20:19:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-89719",
                        "url": "https://ubuntu.com/security/CVE-2026-89719",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  zram: fix out-of-bounds access in read_block_state()  read_block_state() calculates nr_pages before taking dev_lock.  If the device is reset and reinitialized with a smaller disksize before lock acquisition, nr_pages still describes the old table.  The subsequent loop can then call slot_lock() past the end of the newly allocated table.  Read disksize after acquiring dev_lock and checking that the device is initialized.  The read lock then keeps the table and its bound stable for the duration of the scan.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-09-11 20:20:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-89763",
                        "url": "https://ubuntu.com/security/CVE-2026-89763",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  KEYS: trusted: Fix TPM teardown ordering  trusted_tpm_exit() drops the TPM chip reference and frees the digest array before unregistering the trusted key type. key_type_lookup() holds key_types_sem for reading until the key operation finishes, while unregister_key_type() takes it for writing. It therefore provides the synchronization point that must precede backend teardown.  The current order permits this interleaving:    CPU 0                              CPU 1   trusted_tpm_exit()                 key_type_lookup(\"trusted\")     put_device(&chip->dev)             trusted_tpm_seal()     kfree(digests)                       pcrlock()     unregister_key_type()                  tpm_pcr_extend(..., digests)  CPU 1 can consequently dereference the freed digest array. The chip can also be released before callbacks stop using it.  KASAN reported:    BUG: KASAN: slab-use-after-free in tpm_pcr_extend+0x1f0/0x200   Read of size 2 at addr ffff88810872d000 by task poc/89   Call Trace:     tpm_pcr_extend+0x1f0/0x200     pcrlock+0x42/0x70 [trusted]     trusted_tpm_seal+0x1b6/0x570 [trusted]     trusted_instantiate+0x293/0x340 [trusted]     __key_instantiate_and_link+0xb2/0x2b0     __key_create_or_update+0x61e/0xb50     __do_sys_add_key+0x1b8/0x310   Allocated by task 88:     __kmalloc_noprof+0x1a7/0x490     do_one_initcall+0xa1/0x390     do_init_module+0x2df/0x840   Freed by task 90:     kfree+0x131/0x3c0     trusted_tpm_exit+0x59/0xa0 [trusted]     __do_sys_delete_module+0x346/0x510  Move unregister_key_type() before releasing either resource. This stops new lookups and waits for in-flight key operations to finish before the backend state is destroyed.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-09-11 20:20:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-80851",
                        "url": "https://ubuntu.com/security/CVE-2026-80851",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  gtp: serialize PDP context updates  PDP contexts can be deleted through GTP_CMD_DELPDP or while the GTP network device is being unregistered. The latter is serialized by RTNL, but the generic-netlink delete path only holds RCU.  Running both paths concurrently can therefore make both paths delete the same PDP context. The issue was found through static analysis and reproduced on a KASAN-enabled kernel by a simple two-thread program racing GTP_CMD_DELPDP against RTM_DELLINK:    Oops: general protection fault, probably for non-canonical address   KASAN: maybe wild-memory-access in range          [0xdead000000000120-0xdead000000000127]   RIP: gtp_genl_del_pdp+0x1c1/0x420 [gtp]   RBP: dead000000000122  The second deletion dereferenced the poisoned hlist pprev pointer.  Serialize gtp_pdp_add(), gtp_genl_del_pdp(), and gtp_dellink() with a shared mutex. Keep the mutex held until the final use of a PDP context in the NEWPDP path, and keep the RCU read-side section around the complete PDP context use in the DELPDP path.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-09-04 16:18:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-80861",
                        "url": "https://ubuntu.com/security/CVE-2026-80861",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  usb: xhci: bail out of setup if the controller is inaccessible  xhci_gen_setup() locates the operational registers using the capability length read from the very first register:  \txhci->op_regs = hcd->regs + \t\tHC_LENGTH(readl(&xhci->cap_regs->hc_capbase));  If the controller is dead or has dropped off the bus, that read returns ~0, HC_LENGTH() truncates it to 0xff, and op_regs ends up 0xff bytes past the page-aligned MMIO base, i.e. unaligned. The first access through it, xhci_halt() -> xhci_handshake() reading op_regs->status, is then an unaligned readl() on device memory. arm64 faults on unaligned device accesses, so instead of xhci_handshake() catching the all-ones value and returning -ENODEV, setup oopses:    xhci-pci-renesas 0005:08:00.0: Unable to change power state from D3cold to D0, device inaccessible   xhci-pci-renesas 0005:08:00.0: xHCI Host Controller   xhci-pci-renesas 0005:08:00.0: new USB bus registered, assigned bus number 1   Unable to handle kernel paging request at virtual address ffff80030a770103     ESR = 0x0000000096000021     FSC = 0x21: alignment fault   Internal error: Oops: 0000000096000021 [#1]  SMP   pc : xhci_halt [xhci_hcd]   Call trace:    xhci_halt    xhci_gen_setup    xhci_pci_setup    usb_add_hcd    usb_hcd_pci_probe    xhci_pci_common_probe    xhci_pci_renesas_probe  This was hit with a Renesas uPD720201 that failed to power up (\"Unable to change power state from D3cold to D0, device inaccessible\") yet still reached the HCD probe path.  Read the capability register once, and if it reads back the all-ones value (as xhci_handshake() and xhci_reset() already test for), abort setup with -ENODEV before op_regs is derived from it. Reading it once also avoids re-reading a register that may change under a concurrent hot-removal.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-09-04 16:18:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98377",
                        "url": "https://ubuntu.com/security/CVE-2026-98377",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  vlan: require the MAC header to be present in __vlan_insert_inner_tag()  __vlan_insert_inner_tag() only guarantees head room via skb_cow_head(), never that mac_len bytes of MAC header are present.  Its ETH_HLEN wrappers - __vlan_insert_tag() under skb_vlan_push(), and vlan_insert_tag() under validate_xmit_vlan() on the generic transmit path - therefore rewrite the first 16 bytes at skb->data: a 12-byte memmove plus two 2-byte stores at +12 and +14.  No caller supplies the bound, while the pop helpers use skb_ensure_writable()/pskb_may_pull().  An IFF_TUN device has hard_header_len == 0, so packet_snd() accepts a one-byte AF_PACKET/SOCK_RAW frame.  The first vlan push only sets a hwaccel tag; the next - clsact \"action vlan push\" or bpf_skb_vlan_push() - enters the helper with skb->len still 1.  The head comes from skbuff_small_head without __GFP_ZERO, so each push drags bytes from beyond skb->tail into the frame.  After three the one-byte send leaves as 13 bytes carrying 11 bytes of uninitialised slab:    0000: 5a b3 62 12 80 88 ff ff 00 b3 62 12 81            `------------------------------'   only 0x5a was sent; the rest is slab, here the top 56 bits of a   linear-map address  Require the MAC header the helper rewrites to be present, so such a frame is dropped rather than transmitted.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-09 08:16:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98170",
                        "url": "https://ubuntu.com/security/CVE-2026-98170",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  smb: client: fix OOB struct field reads in move_smb2_ea_to_cifs()  In move_smb2_ea_to_cifs(), the while (src_size > 0) loop condition is insufficient. It allows iteration to continue even if the remaining src_size is too small to contain a complete smb2_ea_info structure. Consequently, reads of ea_name_length and ea_value_length can occur out-of-bounds.  Fix this by ensuring src_size >= sizeof(*src) before attempting to read any structure fields. Additionally, reject any next_entry_offset that is smaller than sizeof(*src) or that would advance the pointer beyond the available buffer.  Note that for calls where the server returns a malformed EA list, the error returned to userspace changes from -ENODATA (getxattr) or -ERANGE (listxattr) to -EIO. This correctly signals a server protocol error rather than misleadingly indicating \"attribute not present\" or \"output buffer too small\".",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-06 09:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98171",
                        "url": "https://ubuntu.com/security/CVE-2026-98171",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  smb: client: fix next_buffer UAF and NextCommand bounds in compound PDUs  Fix several related bounds checking and pointer lifecycle issues in receive_encrypted_standard()'s handling of compound encrypted frames:  - Clear next_buffer after assigning it to server->bigbuf. A stale   next_buffer pointer can lead to a use-after-free on subsequent   error paths. - Update pdu_length to the decrypted plaintext size (buf_size). Using   the pre-decryption length allows NextCommand to point into stale   ciphertext residue. - Reject next_cmd values smaller than MID_HEADER_SIZE(server). - Fix an integer overflow in the upper bound check by verifying   pdu_length - next_cmd < MID_HEADER_SIZE(server), ensuring the   trailing slice is large enough for a header.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-10-06 09:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98169",
                        "url": "https://ubuntu.com/security/CVE-2026-98169",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  smb: client: fix potential OOB read in smb3_enum_snapshots()  If snapshot_array_size is smaller than GMT_TOKEN_SIZE, smb3_enum_snapshots() sets ret_data_len to sizeof(struct smb_snapshot_array) without verifying the actual length of the server's reply.  Because SMB2_ioctl() places no lower bound on the server-supplied OutputCount and allocates retbuf to exactly that length, a short reply results in ret_data_len exceeding the size of retbuf. The subsequent copy_to_user() then reads past the end of retbuf, leaking adjacent slab memory to userspace.  The subsequent clamp check is ineffective as it only reduces ret_data_len.  Fix this by rejecting replies shorter than sizeof(struct smb_snapshot_array) with -EIO. Note that the bound is set to the 12-byte struct size rather than the 16-byte MIN_SNAPSHOT_ARRAY_SIZE defined in MS-SMB2 3.3.5.15.1, because 12 bytes is exactly what copy_to_user() attempts to read.",
                        "cve_priority": "negligible",
                        "cve_public_date": "2026-10-06 09:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-98193",
                        "url": "https://ubuntu.com/security/CVE-2026-98193",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: libipw: reject TKIP frames without a full MIC  libipw_michael_mic_verify() assumes that an skb contains an eight-byte Michael MIC. A short TKIP frame makes the unsigned payload length wrap, causing michael_mic() to read past the skb.  Check that the MIC is present before verifying it, and use the existing MICHAEL_MIC_LEN constant for all MIC lengths in the verifier.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-10-06 09:18:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-97555",
                        "url": "https://ubuntu.com/security/CVE-2026-97555",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  smb: client: fix heap overflow in DACL owner/group rewrite  When id_mode_to_cifs_acl rewrites an existing DACL, it allocates a buffer sized according to the on-disk DACL length reported by dacl_ptr->size. However, replace_sids_and_copy_aces may rewrite each ACE with a new owner/group SID obtained from the cifs.idmap upcall. Those SIDs can have up to SID_MAX_SUB_AUTHORITIES (15) sub-authorities, making each ACE up to 76 bytes (sizeof(struct smb_ace)).  If the original DACL contains short SIDs (e.g., 1 sub-authority) while the replacement SIDs are long, the rewritten ACEs overflow the allocation.  Fix this by always budgeting for worst-case SID expansion: allocate sizeof(struct smb_acl) plus num_aces * sizeof(struct smb_ace), which covers the smb_acl header and room for every ACE at maximum SID size. This replaces the previous split logic that used dacl_ptr->size for cifsacl mounts but num_aces * sizeof(struct smb_ace) for mode_from_sid mounts: both paths can trigger the same rewrite and need the same headroom.  KASAN reports this as:   BUG: KASAN: slab-out-of-bounds in build_sec_desc+0x1e8a/0x2680 [cifs]   Write of size 4 at addr ffff8881a5e25374 by task chown/5298   ...   The buggy address is located 0 bytes to the right of    allocated 884-byte region [ffff8881a5e25000, ffff8881a5e25374)",
                        "cve_priority": "high",
                        "cve_public_date": "2026-09-25 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-97557",
                        "url": "https://ubuntu.com/security/CVE-2026-97557",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  smb: client: avoid leaking refcount in cifs_queue_oplock_break()  cifs_queue_oplock_break() unconditionally takes a reference on the target file before queueing cifs_oplock_break(). Only that work item decreases the reference counter again.  If another oplock break arrives while that work is still queued, queue_work() will return false and not queue this second work item. As a result, we will never reach the point to drop the file reference again and are leaking this reference. This can be triggered when interacting with a slow-responding server.  As a result, later unmount operations for this file system will fail with    BUG: Dentry ... still in use (1) [unmount of cifs cifs]   VFS: Busy inodes after unmount of cifs (cifs)   kernel BUG at fs/super.c:777!  Fix this by only incrementing the reference count if the work has been queued successfully. Taking it after queue_work() is safe because all three callers hold tcon->open_file_lock across the call and _cifsFileInfo_put() decrements under that same lock, so a worker that starts the handler in the window cannot drop the reference before it has been taken.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-09-25 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-97564",
                        "url": "https://ubuntu.com/security/CVE-2026-97564",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  smb: client: reject userspace cifs.idmap descriptions  cifs.idmap key descriptions carry authority-bearing fields (owner and group SIDs and uid/gid values in \"os:\"/\"gs:\"/\"oi:\"/\"gi:\" form) that the cifs.idmap upcall helper treats as kernel-originating inputs.  Unlike its sibling cifs.spnego, the cifs.idmap key type has no vet_description hook, so userspace can create keys of this type through request_key(2)/add_key(2) and supply those fields without CIFS origin. A request_key(2) call with a non-NULL callout then drives a root usermodehelper upcall (/sbin/request-key -> cifs.idmap) that consumes the unvetted description in root context.  Only accept cifs.idmap descriptions while CIFS is using its private root_cred to request the key.  id_to_sid()/sid_to_id() already run under override_creds(root_cred), so the kernel-originated path is unaffected.  This mirrors commit 3da1fdf4efbc (\"smb: client: reject userspace cifs.spnego descriptions\"), which applied the same restriction to cifs.spnego.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-09-25 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-97615",
                        "url": "https://ubuntu.com/security/CVE-2026-97615",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net: bridge: use option bits for CFM/MRP frame handlers  CFM and MRP register a global br_frame_type whose hlist_node is linked into the per-bridge frame_type_list when the first MEP/MRP instance is created. Enabling the protocol on multiple bridges therefore inserts the same node into multiple lists. Unregistering it on one bridge then corrupts list state belonging to another.  These handlers can only be installed once per bridge, and they are uncommon. Track their per-bridge enable state with net_bridge option bits, which already live on the Rx hot cache line, and dispatch the matching handler directly from the receive path. Check both bits together first as an unlikely case.  Remove the generic frame_type_list and br_frame_type helpers, which have had no other users since CFM and MRP were added. That shrinks struct net_bridge by 8 bytes and drops the list walk from the fast path. When neither protocol is compiled in, BR_CFM_MRP_OPTS is 0 and the compiler prunes the branch.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-09-25 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-97901",
                        "url": "https://ubuntu.com/security/CVE-2026-97901",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  genetlink: pin family module during policy dump  The generic netlink controller's policy dump keeps pointers to the target family's operation and policy tables in its callback state.  A dump may be split across multiple skbs and remain pending after the initial request.  Netlink pins the module which owns the dump callback, but in this case that is the controller's owner rather than the target family's owner.  The target family can consequently be unregistered and its module unloaded while a policy dump is pending.  Advancing the dump then dereferences policy memory from the unloaded module.  Take a reference to the target family's module when the dump starts. Drop it from the error and done paths.  This matches the lifetime for which the dump context retains the family and policy pointers.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-09-25 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-97908",
                        "url": "https://ubuntu.com/security/CVE-2026-97908",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  Bluetooth: btqcomsmd: destroy RPMsg endpoints before freeing hci_dev  The command and ACL RPMsg endpoints store struct btqcomsmd as their callback private data. The receive callbacks dereference btq->hdev without taking an hci_dev reference.  The current teardown order frees the hci_dev before destroying the RPMsg endpoints in both the hci_register_dev() error path and the driver remove path. If WCNSS delivers data in that window, the endpoint callback can run with an already freed hci_dev and pass it to the Bluetooth core.  For qcom_smd endpoints, rpmsg_destroy_ept() closes the channel and clears the callback under the channel recv_lock. The receive path holds the same lock while invoking the callback, so destroying the endpoints first both prevents new callbacks and serializes with any callback already running.  Destroy the command and ACL endpoints before hci_free_dev(). Keep hci_unregister_dev() first during remove so the HCI core stops issuing operations before the transport endpoints are shut down. In the full registration-error cleanup path, return directly after freeing the hci_dev to avoid falling through to the partial-construction labels and destroying the endpoints twice.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-09-25 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-97925",
                        "url": "https://ubuntu.com/security/CVE-2026-97925",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  tick/broadcast: Plug clockevents replacement race  朱恺乾 reported and decoded the following race condition when a broadcast device is replaced:  CPUA\t\t\t\t\tCPUB  __tick_broadcast_oneshot_control()    bc = tick_broadcast_device.evtdev; \t\t\t\t\ttick_install_broadcast_device(dev)         \t\t\t\tclockevents_exchange_device(cur, dev) \t\t\t\t\t   shutdown(cur); \t\t\t\t\t   detach(cur); \t\t\t\t\t   cur->handler = noop; \t\t\t\t\t   tick_broadcast_device.evtdev = dev;    tick_broadcast_set_event(bc, next_event); <- FAIL: arms a detached device.  If the original broadcast device has a restricted interrupt affinity mask and the last CPU in that mask goes offline then the BUG() in tick_cleanup_dead_cpu() triggers because the clockevent device is not in detached state.  The reason for this is that tick_install_broadcast_device() is not serialized vs. tick broadcast operations.  The obvious cure is to serialize tick_install_broadcast_device() with tick_broadcast_lock against a concurrent tick broadcast operation.  That requires to split clockevents_exchange_device() into two parts, one which does the exchange, shutdown and detach operation and the other which drops the module reference count. This is required because the module reference cannot be dropped while holding tick_broadcast_lock.  Let clockevents_exchange_device() do both operations as before, but let the broadcast device code take the two step approach and do the device exchange under tick_broadcast_lock and drop the module reference count after releasing it.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-09-25 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-93285",
                        "url": "https://ubuntu.com/security/CVE-2026-93285",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  f2fs: embed f2fs_gc_kthread in f2fs_sb_info  Instead of allocating f2fs_gc_kthread dynamically, embed it in f2fs_sb_info. This simplifies lifetime management and prepares for fixing race conditions during teardown.  - __sbi_store\t\t\t- remount|shutdown \t\t\t\t - f2fs_stop_gc_thread  - access sbi->gc_thread \t\t\t\t  - sbi->gc_thread = NULL  - access sbi->gc_thread->f2fs_gc_task",
                        "cve_priority": "low",
                        "cve_public_date": "2026-09-24 17:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-97529",
                        "url": "https://ubuntu.com/security/CVE-2026-97529",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  scsi: qla2xxx: Validate BSG request_len before reading vendor_cmd[]  The FC BSG transport allocates job->request via memdup_user() using the exact user-supplied request_len. For FC_BSG_HST_VENDOR, fc_bsg_host_dispatch() only guarantees request_len covers msgcode and vendor_id; it does not account for the vendor_cmd[] flexible array.  qla2xxx then reads the command selector vendor_cmd[0] and, in several sub-handlers, vendor_cmd[1]/[2] or structures overlaid on the vendor command area without verifying request_len. A caller holding CAP_SYS_RAWIO can submit a short request whose vendor_id matches the host, triggering out-of-bounds heap reads (KASAN-detectable, and able to mis-select a command or panic).  Add a central guard in qla2x00_process_vendor_specific() so the selector is always in bounds, restrict the early vendor_cmd[0] read in qla24xx_bsg_request() to sufficiently long vendor messages, and add request_len checks to the sub-handlers that read further: qla24xx_proc_fcp_prio_cfg_cmd(), qla2x00_process_loopback(), qla84xx_reset(), qla84xx_updatefw(), qla2x00_read_optrom(), qla2x00_update_optrom(), qlafx00_mgmt_cmd() and qla28xx_validate_flash_image().",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-09-25 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-97536",
                        "url": "https://ubuntu.com/security/CVE-2026-97536",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  scsi: qla2xxx: Fix use-after-free of qpair work on queue teardown  The response queue MSI-X handler qla2xxx_msix_rsp_q() schedules qla_do_work() via queue_work(ha->wq, &qpair->q_work). qla_do_work() dereferences the qpair (vha, rsp) and takes qpair->qp_lock.  During teardown, qla2xxx_delete_qpair() deletes the response queue, which calls free_irq() in qla25xx_free_rsp_que(), and then frees the queue and the qpair. free_irq() waits for running hardirq handlers but does not cancel work already placed on ha->wq. A still-pending q_work then runs qla_do_work() against the freed qpair and response queue, causing a use-after-free. This is especially likely during full adapter teardown, where destroy_workqueue(ha->wq) forces pending work to run after the queue pairs have been freed.  Flush the work item with cancel_work_sync() in qla25xx_free_rsp_que() after free_irq() has released the interrupt (so no new work can be queued) and before the response queue and qpair memory are freed (so the flushed handler still sees valid memory). Guard on rsp->qpair and ha->wq to match the INIT_WORK() condition and avoid operating on an uninitialized work_struct.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-09-25 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-97537",
                        "url": "https://ubuntu.com/security/CVE-2026-97537",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  scsi: qla2xxx: Fix queue teardown NULL dma_free and bitmap locking  qla25xx_free_req_que() and qla25xx_free_rsp_que() have two pre-existing bugs exposed on the error path of qla25xx_create_{req,rsp}_que():   1. When dma_alloc_coherent() fails during queue creation, the error     path calls the free function with req->ring / rsp->ring still NULL     (from kzalloc).  The unconditional dma_free_coherent() with a NULL     cpu_addr is undefined behavior and can panic.   2. The free functions clear req_qid_map / rsp_qid_map under vport_lock,     but the create functions protect the same bitmaps with mq_lock.     This provides no mutual exclusion.  Additionally, the create error     path clears the bit and releases mq_lock before calling the free     function, creating a window where another thread can allocate the     same que_id and have its ha->req_q_map entry clobbered by the     subsequent lockless NULL assignment in the free function.  Fix by:   - Guarding dma_free_coherent() with a NULL check on the ring pointer.   - Using mq_lock (the lock held by all creators) in the free functions    to atomically NULL the map entry and clear the bitmap bit.   - Removing the now-redundant clear_bit blocks from the create error    paths since the free functions handle it atomically.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-09-25 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-89859",
                        "url": "https://ubuntu.com/security/CVE-2026-89859",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  scsi: qla2xxx: Zero dport diagnostics buffer to avoid info leak  qla2x00_do_dport_diagnostics() allocates the qla_dport_diag response buffer with kmalloc_obj() (non-zeroing) and, on success, copies the full sizeof(*dd) back to user space via sg_copy_from_buffer(). The inbound sg_copy_to_buffer() only fills as many bytes as the user request payload provides, and qla26xx_dport_diagnostics() zeroes only dd->buf. The options and unused[] fields are therefore copied out uninitialized, leaking kernel heap contents to user space.  Allocate with kzalloc_obj(), matching qla2x00_do_dport_diagnostics_v2().",
                        "cve_priority": "low",
                        "cve_public_date": "2026-09-16 11:16:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-89921",
                        "url": "https://ubuntu.com/security/CVE-2026-89921",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  KVM: s390: Zero initialize data structures for inject_pfault_token  __kvm_inject_pfault_token() only sets .type and .u.ext.ext_params2 of the on-stack struct kvm_s390_irq but the full ext substructure is copied into the cpu local variable on inject. ext_params and pad contain stale stack values.  Interrupt delivery only uses ext_params2, so nothing leaks to the guest, but a host user can use the migration ioctls to get to the data.  Fix by zero-initializing the irq struct. Do the same for the inti data structure.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-09-16 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-89972",
                        "url": "https://ubuntu.com/security/CVE-2026-89972",
                        "cve_description": "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 reference to ns when kfree(ns) runs.  The normal removal path in nvme_ns_remove() correctly calls synchronize_srcu(&ns->head->srcu) after list_del_rcu() to wait for in-progress readers. Add the same grace period in the error path.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-09-16 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-89988",
                        "url": "https://ubuntu.com/security/CVE-2026-89988",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  kprobes: Protect kprobe_blacklist with RCU  __within_kprobe_blacklist() traverses kprobe_blacklist without holding kprobe_mutex. When a module is unloaded, kprobe_remove_area_blacklist() removes blacklist entries and immediately frees them with kfree(). A concurrent call to within_kprobe_blacklist() can therefore dereference freed memory.  Furthermore, within_kprobe_blacklist() can be called in atomic or non-preemptible contexts where the sleeping kprobe_mutex cannot be taken.  Protect kprobe_blacklist with RCU. Use guard(rcu)() and list_for_each_entry_rcu() for traversal, list_add_tail_rcu() for insertions, list_del_rcu() for deletions, and kfree_rcu() to reclaim entries safely after a grace period.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-09-16 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-90002",
                        "url": "https://ubuntu.com/security/CVE-2026-90002",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ftrace: Take trace_array reference before accessing its ftrace_ops  The trace instance files set_ftrace_filter and set_ftrace_notrace was updated to work with specific trace instances (trace_arrays). The issue is that when these files are opened, there is a small race window where it will use the ftrace_ops from the inode->private pointer to get a reference to the trace_array and then take its reference. The problem is that the ftrace_ops itself could be freed. If the rmdir on the instance happens at the same time the set_ftrace_filter file is opened, the rmdir could have also freed the ftrace_ops and referencing it will cause a use-after-free bug and crash the kernel.  Instead, pass in the trace_array as the file private data (NULL for the top level instance), and then pass both the trace_array and the ftrace_ops to the ftrace_regex_open() function. If the trace_array is NULL, then it just uses the ftrace_ops without the need to take its reference (like normal). If the ftrace_ops is NULL, that is only the case for the top level instance and the global_ops can be used.  This allows the trace_array to have its reference incremented before touching the ftrace_ops that could also be freed when the instance is.",
                        "cve_priority": "low",
                        "cve_public_date": "2026-09-16 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-90016",
                        "url": "https://ubuntu.com/security/CVE-2026-90016",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  staging: rtl8723bs: fix OOB read in rtw_restruct_wmm_ie()  rtw_restruct_wmm_ie() scans in_ie for a WMM IE with:  \twhile (i < in_len) { \t\t... \t\tif (i + 5 < in_len && in_ie[i] == 0xDD && ...) { \t\t\t... \t\t\tbreak; \t\t} \t\ti += (in_ie[i + 1] + 2); /* to the next IE element */ \t}  When the \"i + 5 < in_len\" match check fails simply because i is within 5 bytes of the end of the buffer (i.e. no WMM IE was found near the tail of in_ie), execution falls through to \"i += (in_ie[i + 1] + 2)\", which reads in_ie[i + 1]. If i == in_len - 1 at that point, this is a 1-byte out-of-bounds read of an attacker-influenced IE buffer built from association/scan data.  Commit a75281626fc8f (\"staging: rtl8723bs: fix potential out-of-bounds read in rtw_restruct_wmm_ie\") added the \"i + 5 < in_len\" guard to the match condition itself, but did not add an equivalent guard before the fallthrough advance, so the same class of OOB read remained reachable through the non-matching path.  Add an explicit bounds check before advancing to the next IE.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-09-16 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-90029",
                        "url": "https://ubuntu.com/security/CVE-2026-90029",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  usb: storage: realtek_cr: fix use-after-free on disconnect  realtek_cr_destructor() calls timer_delete() before the chip containing the timer is freed. The timer callback may still be running and can rearm itself, resulting in a use-after-free.  Use timer_shutdown_sync() to wait for the callback and prevent further rearming. Do this unconditionally because ss_en may be changed after the timer is armed.  Move timer_setup() into init_realtek_cr() so the timer is initialized before any failure path can invoke the destructor.  Found by static analysis.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-09-16 11:17:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-80947",
                        "url": "https://ubuntu.com/security/CVE-2026-80947",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: rtl8xxxu: fix use-after-free from rx_urb_wq on stop  rtl8xxxu arms rx_urb_wq from the RX completion path: rtl8xxxu_rx_complete() hands the URB to rtl8xxxu_queue_rx_urb(), which queues it on rx_urb_pending_list and, once the list grows past RTL8XXXU_RX_URB_PENDING_WATER, schedules rx_urb_wq.  The worker rtl8xxxu_rx_urb_work() drains rx_urb_pending_list, recovers priv through container_of, and resubmits each URB through rtl8xxxu_submit_rx_urb(), which anchors it on rx_anchor and dereferences priv->udev.  rtl8xxxu_stop() cancels the sibling work items (c2hcmd_work, ra_watchdog, update_beacon_work) but never cancels rx_urb_wq, so a worker armed during the last burst of RX traffic can run rtl8xxxu_rx_urb_work() after rtl8xxxu_disconnect() has called ieee80211_free_hw(), which frees priv, producing a use-after-free.  The window opens under active RX traffic (pending count above the watermark) followed by a disconnect.  There are two teardown races to close:    * rtl8xxxu_queue_rx_urb() decided whether to enqueue under rx_urb_lock     but called schedule_work() after dropping the lock.  A completion     that observed shutdown == false and released the lock could then call     schedule_work() after rtl8xxxu_stop() had set shutdown and     cancel_work_sync() had already returned, arming the worker to run     after the teardown.  Move schedule_work() under the same !shutdown     branch so the arming decision is atomic with the shutdown check.    * rtl8xxxu_rx_urb_work() anchors every URB it drained back onto     rx_anchor through rtl8xxxu_submit_rx_urb().  A worker still running     when usb_kill_anchored_urbs(&priv->rx_anchor) returned would submit a     URB that escaped the kill.  In rtl8xxxu_stop(), call     cancel_work_sync(&priv->rx_urb_wq) before the kill so the worker is     drained first.  After priv->shutdown is set under rx_urb_lock, completions can no longer queue rx_urb_wq. cancel_work_sync() then drains the last queued or running worker, and the following usb_kill_anchored_urbs() kills the URBs it may have submitted.  rtl8xxxu_disconnect() is covered because ieee80211_unregister_hw() guarantees .stop() runs for a live interface before ieee80211_free_hw() frees priv.  The probe error path needs no cancel: rx_urb_wq is INIT_WORK()'d there but cannot have been scheduled, since no URB is submitted before ieee80211_register_hw() succeeds.  This bug was found by static analysis.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-09-11 20:19:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-89481",
                        "url": "https://ubuntu.com/security/CVE-2026-89481",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  nvme-tcp: fix host memory disclosure on R2T for a read command  nvme_tcp_handle_r2t() does not check the direction of the request the R2T refers to. A malicious controller can send an R2T for a READ and the host will answer it: nvme_tcp_setup_h2c_data_pdu() builds the H2CData header and nvme_tcp_try_send_data() sends the request's data buffer. That buffer is the READ destination, so its contents go to the controller.  The command then completes normally and nothing is logged.  Against a test controller that answers every READ with an R2T, a 4096 byte buffered read returned all 4096 bytes, split over two R2Ts. The pages contained stale kernel data, including an array of struct page pointers.  Reject an R2T for a request that is not a write.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-09-11 20:19:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-89492",
                        "url": "https://ubuntu.com/security/CVE-2026-89492",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ocfs2: validate directory-index entry counts when reading metadata  ocfs2_validate_dx_leaf() and ocfs2_validate_dx_root() check the ECC and signature of an indexed-directory block before it reaches higher-level callers, but neither validator bounds the ocfs2_dx_entry_list counts against the capacity of the block that holds them.  ocfs2_dx_dir_search() then walks  \tfor (i = 0; i < le16_to_cpu(entry_list->de_num_used); i++) \t\tdx_entry = &entry_list->de_entries[i];  over de_num_used entries with no bounds check.  entry_list is either dx_leaf->dl_list (from ocfs2_read_dx_leaf) or, for an inline root, dx_root->dr_entries.  A crafted on-disk image can set de_num_used (and de_count, which is the __counted_by_le() bound of de_entries) to 0xffff and make the walk read far past the end of the 4KB metadata block, giving a slab out-of-bounds read reachable from any path lookup, stat() or open() on an indexed directory once the image is mounted.  Commit 775c17386a6f (\"ocfs2: validate dx_root extent list fields during block read\") already bounds dr_list for the non-inline dx_root, but left the inline dr_entries path and the dx_leaf dl_list unchecked.  Add the same read-time validation for both entry lists: de_count must equal the capacity of the block (ocfs2_dx_entries_per_leaf()/per_root()) and de_num_used must not exceed de_count, rejecting corrupted metadata with -EFSCORRUPTED before ocfs2_dx_dir_search() can walk an out-of-range entry array.  de_count is always written as exactly the block capacity when a leaf or inline root is formatted, so the equality check does not reject any valid image.  Found by 0sec automated security-research tooling (https://0sec.ai).",
                        "cve_priority": "high",
                        "cve_public_date": "2026-09-11 20:19:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-89553",
                        "url": "https://ubuntu.com/security/CVE-2026-89553",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  nouveau/gem: reserve the bo in the info ioctl around the vma lookup  In the non-uvmm path, there could be a race between the info lookup finding the vma, and the gem close path closing the vma leading to a use-after-free.  Spotted with the help of Opus 4.6.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-09-11 20:19:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-89625",
                        "url": "https://ubuntu.com/security/CVE-2026-89625",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  HID: sony: fix UAF of ghl_poke_timer / ghl_urb at driver unbind  For GHL (Guitar Hero Live) dongles, sony_probe() arms a periodic timer: ghl_magic_poke() (the timer callback) submits sc->ghl_urb, and the URB completion ghl_magic_poke_cb() re-arms the timer with mod_timer().  sony_remove() drained the timer with timer_delete_sync() and then freed the URB with usb_free_urb():  \ttimer_delete_sync(&sc->ghl_poke_timer); \tusb_free_urb(sc->ghl_urb);  timer_delete_sync() does not block re-arming, and while the URB is in flight the timer is not pending, so the sync delete is a no-op. A URB completion that runs after the delete re-arms the timer, and usb_free_urb() only drops a reference -- it does not kill an in-flight URB. sc is allocated with devm_kzalloc() and freed once sony_remove() returns, so the re-armed ghl_poke_timer (embedded in sc) then fires on freed memory, a use-after-free from timer softirq. This is a disconnect/rmmod race.  Poison the URB first, then shut the timer down, before freeing the URB. usb_poison_urb() kills any in-flight URB and permanently rejects further submissions, so a poke timer that is still pending cannot re-submit the URB from ghl_magic_poke() in the window before timer_shutdown_sync() runs. usb_kill_urb() would not suffice: it only cancels the in-flight URB and leaves it submittable once it returns, so the pending timer could re-submit it and put a fresh URB in flight over the freed sc. timer_shutdown_sync() then drains any last callback and blocks re-arming. The probe error path is unaffected: it is only reached before the timer is armed.  Reproduced under KASAN on next-20260710 via dummy_hcd + raw-gadget emulation of the GHL PS4 dongle (VID 0x1430 / PID 0x07bb): hid-sony binds and arms the poke timer, the poke URB is held in flight, the driver is unbound (freeing sc), then the URB is released. The completion re-arms the timer on the freed sc, and the re-armed timer fires ~8 s later:    BUG: KASAN: slab-use-after-free in ghl_magic_poke+0x98/0xb0   Read of size 8 at addr ffff88810b02fd50 by task swapper/0/0    ghl_magic_poke+0x98/0xb0    call_timer_fn+0x35/0x2b0    __run_timers+0x69c/0x9a0    run_timer_softirq+0x173/0x2a0   Allocated by task 169:  sony_probe   Freed by task 338:      devres_release_group <- hid_device_remove (sony_remove)  Found by 0sec (https://0sec.ai) using automated source analysis.",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-09-11 20:19:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-89633",
                        "url": "https://ubuntu.com/security/CVE-2026-89633",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  smb: client: fix OOB read/write from unvalidated DataOffset in coalesce_t2()  coalesce_t2() computes data pointers directly from server-supplied DataOffset fields with no validation against buffer bounds:    data_area_of_tgt = (char *)&pSMBt->hdr.Protocol +                      get_unaligned_le16(&pSMBt->t2_rsp.DataOffset);   data_area_of_src = (char *)&pSMBs->hdr.Protocol +                      get_unaligned_le16(&pSMBs->t2_rsp.DataOffset);   data_area_of_tgt += total_in_tgt;   ...   memcpy(data_area_of_tgt, data_area_of_src, total_in_src);  A small DataOffset can push a pointer below the actual byte area, overwriting header fields; a large one can push it past the buffer end, causing out-of-bounds heap reads (source) or writes (target). The BCC overflow guard does not prevent this: BCC reflects how much data is present, while DataOffset controls where in the buffer it starts.  The \"validate target area\" comment present since the function was first written in 2005 was a placeholder that was never implemented.  Add lower- and upper-bound checks for both data pointers before the memcpy, and before any target header fields are modified.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-09-11 20:19:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-89652",
                        "url": "https://ubuntu.com/security/CVE-2026-89652",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ceph: bound copied dentry name length in NFS export get_name  ceph_get_name() copies the MDS-supplied name into the caller's NAME_MAX-sized buffer with memcpy(name, rinfo->dname, rinfo->dname_len) and then writes name[rinfo->dname_len] = 0, without checking dname_len against NAME_MAX. A malicious or buggy MDS that returns a LOOKUPNAME reply with dname_len > NAME_MAX overflows the buffer. __get_snap_name() copies rde->name / rde->name_len the same unchecked way.  Impact: a malicious or compromised Ceph MDS overflows the NAME_MAX name buffer in a client's NFS-export get_name path, a slab out-of-bounds write reported by KASAN. Reachable when a CephFS mount is re-exported over NFS.  Add ceph_export_copy_name(), which rejects lengths above NAME_MAX with -ENAMETOOLONG before the copy, and use it in both ceph_get_name() and __get_snap_name().",
                        "cve_priority": "critical",
                        "cve_public_date": "2026-09-11 20:19:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-89680",
                        "url": "https://ubuntu.com/security/CVE-2026-89680",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  nfsd: fix nfsd_file leak on inter-server COPY setup failure  When nfsd4_setup_inter_ssc() fails, nfsd4_copy() returns nfserr_offload_denied directly, bypassing the out: label where release_copy_files() would drop the nf_dst reference taken by nfs4_preprocess_stateid_op(). Each failed inter-server COPY leaks one nfsd_file, pinning file/inode/dentry/vfsmount.  Fix by setting status and jumping to out: instead of returning directly.",
                        "cve_priority": "high",
                        "cve_public_date": "2026-09-11 20:19:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-89761",
                        "url": "https://ubuntu.com/security/CVE-2026-89761",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  apparmor: fix out-of-bounds write when null terminating a label vec  aa_vec_unique() null terminates at vec[n - dups] when VEC_FLAG_TERMINATE is passed. If the components are all distinct no duplicates are dropped, dups is 0 and the terminator goes to vec[n], so the caller has to provide room for n + 1 entries.  aa_label_strn_parse() sets up its vector with vec_setup(profile, vec, len, gfp) and then calls aa_vec_unique(vec, len, VEC_FLAG_TERMINATE), but vec_setup() does not reserve the terminator entry. Up to LOCAL_VEC_ENTRIES it uses the local array of LOCAL_VEC_ENTRIES pointers, above that it allocates exactly len pointers. The terminator therefore lands one entry past the end of the local array when len is LOCAL_VEC_ENTRIES, and one entry past the end of the allocation when len is larger.  len comes from the number of \"//&\" separated components in the label name and label_count_strn_entries() does not bound it. An unprivileged task reaches the parse by writing to /proc/self/attr/apparmor/current or through lsm_set_self_attr(2), both of which go through do_setattr(), and the name is parsed before the change_profile permission is checked. The query_label() path behind the securityfs .access file, which is mode 0666, performs no permission check at all. Every component has to resolve to a loaded profile, so a system with policy loaded is required.  The other two VEC_FLAG_TERMINATE users work on a label vec that aa_label_alloc() has already sized with \"+ 1 for null terminator entry on vec\". Reserve the same entry in vec_setup() and DEFINE_VEC(). Passing len + 1 from the caller instead would move len == LOCAL_VEC_ENTRIES out of the local array and into kzalloc().",
                        "cve_priority": "medium",
                        "cve_public_date": "2026-09-11 20:20:00 UTC"
                    },
                    {
                        "cve": "CVE-2026-80852",
                        "url": "https://ubuntu.com/security/CVE-2026-80852",
                        "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  tls: device: fix out-of-bounds write in tls_append_frag()  Found with syzkaller and a local syzbot instance running on top of a netdevsim TLS offload emulation; tls_device.c is otherwise only reachable on a machine with a NIC that implements the offload.  tls_push_data() only checks whether the open record still has room for another frag at the bottom of its loop, and the MSG_MORE early break skips that check.  The record survives to the next syscall with the frag count it already had, and tls_append_frag() does not check either, so with TLS_TX_ZEROCOPY_RO every splice(SPLICE_F_MORE) of a byte or two adds a non-coalescing pipe page and num_frags walks off the end of tls_record_info.frags[MAX_SKB_FRAGS].  Once the record is pushed, tls_push_record() runs the same index over sg_tx_data[MAX_SKB_FRAGS] and the sg_set_page() writes land on the destruct_work that follows it, which the workqueue then calls.  The byte limit is fine because copy drops to 0 and the loop falls through to the same check; the frag count has no such feedback.  Push the record rather than keep a full one open, which is what a plain TCP socket does - tcp_sendmsg_locked() uses tcp_mark_push() and new_segment in both the copy and the MSG_SPLICE_PAGES paths, and tls_sw already sets full_record when the sk_msg ring fills up, MSG_MORE or not.    BUG: KASAN: slab-out-of-bounds in tls_append_frag ( net/tls/tls_device.c:269)   Write of size 8 at addr ffff8881104d1530 by task tls_oob/450    CPU: 2 UID: 0 PID: 450 Comm: tls_oob Not tainted 7.2.0-rc7+ #329 PREEMPT   Call Trace:    <TASK>    dump_stack_lvl (lib/dump_stack.c:94 lib/dump_stack.c:120)    print_report (mm/kasan/report.c:378 mm/kasan/report.c:482)    kasan_report (mm/kasan/report.c:595)    tls_append_frag (net/tls/tls_device.c:269)    tls_push_data (net/tls/tls_device.c:518)    tls_device_sendmsg (net/tls/tls_device.c:583)    inet_sendmsg (net/ipv4/af_inet.c:865)    sock_sendmsg (net/socket.c:775 net/socket.c:790 net/socket.c:813)    splice_to_socket (fs/splice.c:884)    do_splice (fs/splice.c:936 fs/splice.c:1349)    __do_splice (fs/splice.c:1431)    __x64_sys_splice (fs/splice.c:1634 fs/splice.c:1616)    do_syscall_64 (arch/x86/entry/syscall_64.c:63 arch/x86/entry/syscall_64.c:94)    entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:121)    </TASK>  and, once the record is pushed:    UBSAN: array-index-out-of-bounds in net/tls/tls_device.c:300:24   index 18 is out of range for type 'skb_frag_t [17]'   UBSAN: array-index-out-of-bounds in net/tls/tls_device.c:301:41   index 18 is out of range for type 'scatterlist [17]'   UBSAN: array-index-out-of-bounds in net/tls/tls_device.c:302:39   index 18 is out of range for type 'scatterlist [17]'   UBSAN: array-index-out-of-bounds in net/tls/tls_device.c:307:38   index 26 is out of range for type 'scatterlist [17]'    kernel tried to execute NX-protected page - exploit attempt? (uid: 0)   BUG: unable to handle page fault for address: ffffea000411a680   #PF: supervisor instruction fetch in kernel mode   #PF: error_code(0x0011) - permissions violation   Oops: Oops: 0011 [#1] SMP KASAN PTI   Workqueue: ktls_device_destruct 0xffffea000411a680   RIP: 0010:0xffffea000411a680   Call Trace:    <TASK>    worker_thread (kernel/workqueue.c:3405 kernel/workqueue.c:3486)    kthread (kernel/kthread.c:436)    ret_from_fork (arch/x86/kernel/process.c:158)    ret_from_fork_asm (arch/x86/entry/entry_64.S:245)    </TASK>",
                        "cve_priority": "high",
                        "cve_public_date": "2026-09-04 16:18:00 UTC"
                    }
                ],
                "launchpad_bugs_fixed": [
                    2173211,
                    2173225,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857,
                    2172857
                ],
                "changes": [
                    {
                        "cves": [
                            {
                                "cve": "CVE-2026-99115",
                                "url": "https://ubuntu.com/security/CVE-2026-99115",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ksmbd: fill in FileSysIdentifier in FS_POSIX_INFORMATION  smb2_get_info_filesystem() reports 56 bytes for FS_POSIX_INFORMATION, that is the whole of FILE_SYSTEM_POSIX_INFO, but never assigns FileSysIdentifier.  Those eight bytes go to the client as they are found in the response buffer.  The buffer is zeroed on allocation, so a standalone request leaks nothing.  A compound request can leak: the offset of the next response is advanced by the length pinned for the previous one, so a reply that was written into the buffer and then dropped in favour of the short error response of smb2_set_err_rsp() stays there, and the next reply is laid over it with only the header cleared.  Report the file system id statfs() returned, which is what the field is for.  FileSysIdentifier is __le64 and f_fsid is a pair of ints, so assemble the value first, val[0] as the low half, and convert it on the way out.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99113",
                                "url": "https://ubuntu.com/security/CVE-2026-99113",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ksmbd: zero the FS_OBJECT_ID_INFORMATION buffer before filling it in  smb2_get_info_filesystem() reports 64 bytes for FS_OBJECT_ID_INFORMATION, that is the whole of struct object_id_info, but writes only 46 of them:   - objid[] is 16 bytes, and when the volume UUID is not available only    sizeof(stfs.f_fsid) (8) bytes are copied into it;  - extended_info.version_string[] is STRING_LENGTH (28) bytes, and only    strlen(\"1.1.0\") (5) bytes are copied into it.  The response buffer is zeroed on allocation (kvzalloc() in smb2_allocate_rsp_buf()), so for a standalone request the remaining 31 bytes are zero.  In a compound request they need not be.  The offset of the next response is advanced by the length pinned for the previous one, so if a preceding command wrote its reply into the buffer and then failed, smb2_set_err_rsp() pins only the short error response and the next reply lands inside the area that has already been written.  Only the header is cleared there:  \tmemset((char *)rsp_hdr, 0, sizeof(struct smb2_hdr) + 2);  The client then receives up to 31 bytes of a response it was not meant to see, including one that failed with an access denied error.  Clear the structure before filling it in.  As a side effect version_string is now NUL terminated.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99114",
                                "url": "https://ubuntu.com/security/CVE-2026-99114",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ksmbd: initialize FileSystemControlFlags in FS_CONTROL_INFORMATION  smb2_get_info_filesystem() reports 48 bytes for FS_CONTROL_INFORMATION, that is the whole of struct smb2_fs_control_info, but never assigns FileSystemControlFlags.  Those four bytes go to the client as they are found in the response buffer.  The buffer is zeroed on allocation, so a standalone request leaks nothing.  A compound request can leak: the offset of the next response is advanced by the length pinned for the previous one, so a reply that was written into the buffer and then dropped in favour of the short error response of smb2_set_err_rsp() stays there, and the next reply is laid over it with only the header cleared.  ksmbd does not implement quota tracking, so report no control flags.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99132",
                                "url": "https://ubuntu.com/security/CVE-2026-99132",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  xfs: don't hold buffer locks across sync transaction commit in xfs_sync_sb_buf  xfs_sync_sb_buf() holds sb/rtsb buffer locks across a synchronous xfs_trans_commit(), which flushes the CIL push workqueue internally. If shutdown occurs during the CIL push, xfs_buf_item_unpin() needs to lock these buffers to fail them, causing a deadlock:    setlabel:          holds buf lock -> flush_workqueue(xfs-cil)   CIL push worker:   xfs_buf_item_unpin -> xfs_buf_lock(same buf)  Remove the xfs_trans_bhold() calls so that commit releases the buffer locks normally.  After the sync commit, re-acquire the buffers via mp->m_sb_bp / mp->m_rtsb_bp for the on-disk writeback.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99135",
                                "url": "https://ubuntu.com/security/CVE-2026-99135",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  dm-integrity: fix infinite loop on discard with large tag size  When integrity_metadata handles a discard, it fills a buffer with DISCARD_FILLER and writes it over the tags, max_blocks blocks at a time. If the kmalloc fails, the buffer is the on-stack array checksums_onstack and max_size is set to HASH_MAX_DIGESTSIZE. So if the tag size is larger than HASH_MAX_DIGESTSIZE, max_blocks is zero, bi_size is never decremented and the loop never terminates.  Fix this by using sizeof(checksums_onstack) as max_size. The array has MAX_TAG_SIZE bytes since commit b93b6643e9b5 (\"dm integrity: fix a crash with unusually large tag size\"), so max_blocks is at least 1.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99118",
                                "url": "https://ubuntu.com/security/CVE-2026-99118",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  drm/i915/dmc: Harden DMC firmware payload parsing  Validate the conversion of the DMC firmware size from dwords to bytes using check_mul_overflow() before calculating the firmware payload size.  Reject zero-length payloads and zero MMIO counts in the DMC firmware header so malformed firmware is caught early. Also set dmc_fw_size only after the payload allocation succeeds.  (cherry picked from commit efde6601a1f1daedfe3dcc2816c934ddb44e3eef)",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99169",
                                "url": "https://ubuntu.com/security/CVE-2026-99169",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  futex: Fix mm reuse handling for FUT_OFF_MMSHARED  A FUT_OFF_MMSHARED futex is a shared futex that refers to an MM. It is possible for a process to wait on a shared futex with a different MM because a FUT_OFF_INODE waiter can be requeued onto a FUT_OFF_MMSHARED futex by another process. This can cause FUT_OFF_MMSHARED waiters on a freed MM to consume wakeups intended for a newly allocated MM at the same address.  Fix it by keying FUT_OFF_MMSHARED using a unique 64-bit per-MM ID. Leave private futexes as before to avoid influencing the performance of the hotpath.  (Multi-threaded processes typically implicitly use FUT_OFF_MMSHARED by setting clear_child_tid such that it points into anonymous memory, which causes mm_release() in a multi-threaded mm to perform FUTEX_WAKE.)",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99161",
                                "url": "https://ubuntu.com/security/CVE-2026-99161",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  i2c: viai2c-wmt: Fix clock leak in wmt_i2c_probe()  In wmt_i2c_probe(), i2c->clk is acquired using of_clk_get(). If any subsequent operation fails or when the module is unloaded, the clock reference count is never decremented via clk_put(), leading to a resource leak.  Switch to devm_clk_get() so that the clock is automatically managed and released.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99077",
                                "url": "https://ubuntu.com/security/CVE-2026-99077",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ipv4: udp: Create exceptions before socket matching  Currently, when ICMP Fragmentation Needed and Redirect Message packets are locally delivered and quote a UDP packet, a FIB nexthop exception (FNHE) is only created if the kernel can match the UDP packet to an existing socket.  This behavior allows off-path attackers to conduct a side-channel attack on the FNHE cache in order to discover the ephemeral port used by a connected UDP socket.  Commit 6457378fe796 (\"ipv4: use siphash instead of Jenkins in fnhe_hashfun()\") and commit 67d6d681e15b (\"ipv4: make exception cache less predictible\") tried to mitigate such attacks by making it harder for attackers to discover hash collisions in the FNHE cache and by randomizing the number of exceptions a hash bucket can hold, respectively. Unfortunately, both of the mitigations can be bypassed.  Instead, mitigate such attacks by always creating a FNHE, even before trying to find a matching socket. Do that by calling ipv4_update_pmtu() and ipv4_redirect(), the helpers used when the quoted packet did not originate from a socket.  This means that guesses (right or wrong) from an off-path attacker will always result in a FNHE being created or updated in the cache that the attacker can observe.  Pass an oif of 0, in a similar fashion to icmp_err(). This is also the oif used by the socket path for sockets that are not bound to a device.  Note that this does not allow attackers to create FNHEs that they could not create before, as both helpers can already be reached with little to no validation. For example, by sending an ICMP error that quotes an ICMP Echo Reply or one that quotes a UDP source port that matches a wildcard socket.  Also note that in the good case (matched socket) the above scheme comes at the cost of an extra route lookup, as the no socket helpers perform their own lookup before the one performed by ipv4_sk_update_pmtu() / ipv4_sk_redirect(). When the two resolve to different nexthops, it also results in two exceptions being created for the same destination IP. One in the FNHE cache of the nexthop resolved by the no socket helpers and another in the FNHE cache of the nexthop used by the socket.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99123",
                                "url": "https://ubuntu.com/security/CVE-2026-99123",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  vsock/virtio: validate packet source for connected sockets  virtio_transport_recv_pkt() looks up sockets first by the full source and destination tuple, then by destination only in the bound table. The fallback is needed for listening and connecting sockets, but sockets remain in the bound table after connect(), so it can also return a non-listening socket.  The fallback does not validate the source address. In TCP_SYN_SENT, a RESPONSE from an unrelated source can transition the victim socket to TCP_ESTABLISHED while its stored remote address remains unchanged. Subsequent RW packets from that source are delivered through the same destination-only fallback.  This was reproduced with capability-empty processes under different UIDs. The attacker discovered the target tuple through unprivileged AF_VSOCK sock_diag and caused the victim socket to read 16 attacker-chosen bytes; the intended peer-side socket read 0 of those 16 bytes.  Add vsock_check_source() to validate the transport, source port and source CID against the peer stored in a non-listening socket. The local transport is the CID exception because its packets are generated internally with VMADDR_CID_LOCAL as their source, including connections using CID aliases.  Use the helper after lock_sock() in the virtio receive path.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-89987",
                                "url": "https://ubuntu.com/security/CVE-2026-89987",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  mm/huge_memory: transfer the pmd dirty bit to the folio on zap  zap_huge_pmd_folio() propagates the pmd young bit to the folio for the file case, but not the dirty bit.  The pte path does propagate it, in zap_present_folio_ptes() and so does the pmd split path, in __split_huge_pmd_locked().  For most file mappings the omission is harmless, because writing to a shared file mapping goes through page_mkwrite(), which dirties the folio. tmpfs is different: it has no page_mkwrite(), and vma_wants_writenotify() is false for it, so a *read* fault on a MAP_SHARED tmpfs mapping installs a writable pmd via do_read_fault().  do_read_fault() does not call fault_dirty_shared_page(), so subsequent stores through that mapping set only the hardware dirty bit in the pmd and never call folio_mark_dirty(). A shmem folio allocated by a fault is marked uptodate but not dirty (see the clear: block in shmem_get_folio_gfp()), so PG_dirty is never set at all.  Unmapping such a folio - munmap(), or exit_mmap() when the process dies - then loses the only record that it was written, because zap_huge_pmd() drops the pmd without transferring the dirty bit.  Reclaim afterwards sees a clean shmem folio: the whole swap-out block in shrink_folio_list() is inside \"if (folio_test_dirty(folio))\", so pageout() is skipped and the folio falls into __remove_mapping().  There, folio_is_file_lru() is false for a swapbacked folio, so no shadow entry is created and __filemap_remove_folio(folio, NULL) simply empties the i_pages slot.  The data is freed without ever being written to swap, and the next fault on that index returns a freshly zeroed folio.  This is silent data loss for any process that keeps state in a MAP_SHARED tmpfs segment across an unmap - for example a cache handed from one process generation to the next through /dev/shm.  It requires the folio to be PMD-mapped, so it only shows up once shmem THP is enabled (which is what we did in Meta fleet and started noticing crashes); with THP off the pte path transfers the dirty bit correctly.  It also only becomes visible when swap is enabled, because with no swap device shmem folios (which are on the anon LRU) are not scanned by reclaim at all, so the clean folio is never dropped.  Reproduced on x86_64 with a tmpfs mounted huge=within_size: read-fault a 2MB-backed region, write a known pattern through the resulting mapping, munmap, force reclaim of the cgroup, then re-map and read back.  Without this patch the region reads back as zeros and vmstat shows zswpout 0 - the data was discarded rather than swapped.  With this patch the region reads back correctly and the pages are swapped out as expected.  With huge=never, or when the first touch is a write, the test passes either way.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-09-16 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-80572",
                                "url": "https://ubuntu.com/security/CVE-2026-80572",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  Input: byd - synchronize timer deletion before freeing private data  byd_disconnect() uses timer_delete() before freeing the driver's private data.  This does not wait for a running byd_clear_touch() callback, which dereferences the private data and its psmouse pointer.  A callback racing with disconnect can therefore access the private data after it has been freed.  The timer can also still be re-armed by byd_process_byte() while the disconnect is in progress.  Use timer_shutdown_sync() before freeing the private data: it waits for a running callback and turns any later re-arm attempt into a no-op.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-08-26 15:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99180",
                                "url": "https://ubuntu.com/security/CVE-2026-99180",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  unicode: free the map after a grace period  generic_ci_d_hash() and generic_ci_d_compare() read sb->s_encoding and dereference the unicode map while a pathwalk in rcu mode holds nothing but rcu_read_lock(). The filesystems that use them, ext4, f2fs and tmpfs, drop the map with utf8_unload() from ->put_super(), which runs when the last reference to the mount goes away. A lookup that is still inside such a filesystem at that point reads a freed map.  With a pathwalk held up in utf8_casefold_hash() while the last reference to a casefolded tmpfs goes away:    BUG: KASAN: slab-use-after-free in utf8nlookup+0x74c/0x950   Read of size 8 at addr ff110001030fe658 by task walker/98   Call Trace:    <TASK>    utf8nlookup+0x74c/0x950    utf8byte+0x160/0x1560    utf8_casefold_hash+0x167/0x230    generic_ci_d_hash+0xdd/0x1c0    link_path_walk+0x11ad/0x1d30    path_lookupat+0x63/0xb00    filename_lookup+0x1f1/0x5b0    vfs_statx+0xd7/0x3b0   [...]   Allocated by task 94:    __kmalloc_cache_noprof+0x249/0x560    utf8_load+0x4e/0x570    shmem_parse_opt_casefold.isra.0+0x92/0x270   [...]   Freed by task 97:    kfree+0x1db/0x5b0    shmem_put_super+0x72/0x170    generic_shutdown_super+0x14c/0x530    kill_anon_super+0x3a/0x60    deactivate_locked_super+0x9c/0xf0    cleanup_mnt+0x9f/0x130  So far that has been hard to hit. umount(2) waits for a grace period in namespace_unlock() before it drops the mount, so only a mount whose last reference goes away elsewhere, like the close of a file or a chdir out of a lazily unmounted directory, can race a walker. So it is reachable.  Delay the free until a grace period has passed. The map and the data table it holds a reference to then outlive any pathwalk that found the superblock before the mount went away. The reference on the data table module is dropped from the rcu callback as well. utf8-core is built in whenever CONFIG_UNICODE is set, so there is no module exit that would have to wait for the callbacks.  Overlayfs points the s_encoding of an overlay at the map of its first layer without taking a reference of its own. That stays correct. The layer is held by the overlay, so its map is dropped only after the overlay is gone.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99179",
                                "url": "https://ubuntu.com/security/CVE-2026-99179",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  watch_queue: Fix note pool publication race in watch_queue_set_size()  There is a race between watch_queue_set_size() and post_one_notification(). watch_queue_set_size() publishes wqueue->notes, notes_bitmap, nr_pages and nr_notes with plain stores, and post_one_notification() reads them with plain loads under a different lock, so nothing orders the four stores against the poster's loads: depending on the build, notes can be stored last (gcc 14 on x86-64 does this).  Since keyctl_watch_key() lets a watch attach to a queue before it is sized, post_one_notification() can already be running on another CPU at that moment: it reads nr_notes > 0, passes its bounds check, and then reads notes while it is still NULL, dereferencing notes[0].  An unprivileged user triggers this reliably by watching one of its own keys through a notification pipe and racing ioctl(IOC_WATCH_QUEUE_SET_SIZE) on that pipe against keyctl(KEYCTL_SETPERM) on the key from another CPU, triggering:    BUG: kernel NULL pointer dereference, address: 0000000000000000   RIP: 0010:post_one_notification.isra.0+0xa2/0x1e0   Call Trace:    __post_watch_notification+0x148/0x180    keyctl_setperm_key+0x119/0x130    do_syscall_64+0x108/0x4c0    entry_SYSCALL_64_after_hwframe+0x77/0x7f   Kernel panic - not syncing: Fatal exception in interrupt  Fix this by publishing nr_notes last with smp_store_release(), and by reading it once with smp_load_acquire() in post_one_notification() before the bitmap and the page array are touched.  A poster that observes a non-zero nr_notes then also observes the pool behind it; one that observes zero drops the notification as before.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-89912",
                                "url": "https://ubuntu.com/security/CVE-2026-89912",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  KVM: arm64: vgic-its: Don't dereference a NULL collection on ITT save  MAPC with V=0 drops ite->collection but leaves the ITE on the device's ITT list, and vgic_its_save_ite() dereferences it unconditionally. A guest that issues MAPD, MAPTI and then MAPC(V=0) therefore oopses the host when the VMM issues KVM_DEV_ARM_ITS_SAVE_TABLES to migrate it. That sequence is UNPREDICTABLE per the architecture, but KVM already handles the resulting state in the translate, MOVI and DISCARD paths.  Save a zeroed entry, which vgic_its_restore_ite() reads back as invalid. Skipping the ITE instead would leave the ITT slot holding whatever is in guest memory, and restore rejects an entry naming a collection the restored collection table does not have.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-09-16 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99156",
                                "url": "https://ubuntu.com/security/CVE-2026-99156",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  scsi: st: Fix use-after-free race between st_remove() and st_open()  st_remove() drops the probe reference on the scsi_tape with kref_put() and only afterwards removes its index from st_index_idr. If that was the last reference, scsi_tape_release() frees the structure while it is still published in the idr.  scsi_tape_get(), called from st_open(), looks up the tape in st_index_idr and takes a reference under st_ref_mutex and st_index_lock. remove_cdevs() does not wait for opens that are already past chrdev_open(), so an open that is blocked on st_ref_mutex while st_remove() holds it can take the mutex as soon as st_remove() drops it, find the freed tpnt in the idr and call kref_get() on it:    BUG: KASAN: slab-use-after-free in st_open   Write of size 4 ...    st_open (drivers/scsi/st.c:254 drivers/scsi/st.c:1291)    chrdev_open   ...   Freed by task ...:    kfree    st_remove (drivers/scsi/st.c:4512)  Remove the index from the idr before dropping the reference, all under st_ref_mutex. A concurrent scsi_tape_get() now either runs first and holds a valid reference that keeps the tape alive, or runs afterwards and finds nothing, so st_open() fails with -ENXIO.  This restores the ordering st_remove() had before the conversion to st_index_idr, where the tape was unpublished from scsi_tapes[] before the final kref_put().",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99112",
                                "url": "https://ubuntu.com/security/CVE-2026-99112",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net/sched: cls_flower: validate mask pointer after nla_next()  fl_set_enc_opt() iterates the key's nested tunnel-option attributes with nla_for_each_attr() while advancing a single mask pointer via nla_next() at the bottom of each loop, so the mask cursor is driven by the number of key attributes rather than by the mask's own attributes.  The nla_ok() added by commit c96adff956191 (\"cls_flower: call nla_ok() before nla_next()\") only validates the mask pointer that was just consumed; the pointer produced by nla_next() is used by the next iteration (fl_set_geneve_opt() and siblings) without any validation.  The mask's nested attributes are validated with NL_VALIDATE_LIBERAL, which merely warns on trailing bytes that do not form a complete attribute.  A mask carrying one valid attribute plus 1-3 residue bytes (or a non-aligned attribute length making msk_depth negative) therefore reaches the next iteration with msk_depth != 0, so neither the !msk_depth check in fl_set_enc_opt() nor the !depth check in the per-type helpers fires.  nla_type() then reads past the mask payload and nla_parse_nested_deprecated() iterates with an nla_len taken from those bytes, reading well beyond the mask attribute (KASAN: slab-out-of-bounds read in __nla_validate_parse from fl_change()).  Validate the advanced mask pointer as well: when the mask is not legitimately exhausted (msk_depth != 0) and the new pointer fails nla_ok(), reject the filter with -EINVAL.  An exactly exhausted mask still skips the check, preserving exact-match behaviour for the remaining key attributes.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99117",
                                "url": "https://ubuntu.com/security/CVE-2026-99117",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net: bridge: mcast: don't truncate the port group walk on teardown  __br_multicast_disable_port_ctx() and br_multicast_del_port() walk port->mglist with hlist_for_each_entry_safe(). However, br_multicast_find_del_pg() can also delete other entries from the same list through br_multicast_fwd_src_remove() or __fwd_del_star_excl().  If such an entry is the iterator's saved next node, hlist_del_init() clears its ->next and terminates the walk early. The reproducer triggers this in both teardown walks, leaving port groups in the bridge mdb with a dangling ->key.port after del_nbp() frees the port:    BUG: KASAN: slab-use-after-free in __mdb_fill_info+0x1191/0x1320    __mdb_fill_info+0x1191/0x1320    br_mdb_dump+0x594/0xe40    rtnl_mdb_dump+0x1cf/0x5d0  Use hlist_del_init_rcu() to unlink the group while preserving ->next. br_multicast_del_pg() and the teardown walks run under br->multicast_lock. The GC worker must acquire the same lock before detaching the group for destruction, so the node remains alive while the walk uses the preserved pointer.  Preserving ->next means a walk can now reach a group that an earlier iteration already deleted as a side effect. That group is off mp->ports, so br_multicast_find_del_pg() would fall through its port scan and hit the trailing WARN_ON(1). Skip such groups at the top of that helper: a port group is put on port->mglist when it is created and only unlinked when it is deleted, so hlist_unhashed() identifies exactly this case.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-74405",
                                "url": "https://ubuntu.com/security/CVE-2026-74405",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  OPP: Fix race between OPP addition and lookup  A race exists between dev_pm_opp_add_dynamic() and dev_pm_opp_find_freq_exact():    CPU0 (add)                          CPU1 (lookup)   -------------------------------     ------------------------------   _opp_add()     mutex_lock()     list_add(&new_opp->node, head)     mutex_unlock()                    _opp_table_find_key()                                         mutex_lock()                                         dev_pm_opp_get(opp)                                           kref_get()                                         mutex_unlock()     kref_init(&new_opp->kref)                                       dev_pm_opp_put()                                         kref_put_mutex()  The newly added OPP is inserted into the list before its kref is initialized. A concurrent lookup can find this OPP and increment its reference count while it is still uninitialized, leading to refcount corruption and a potential premature free.  Fix this by initializing ->kref and ->opp_table before making the OPP visible via list_add(). This ensures any concurrent lookup observes a fully initialized object.  [ Viresh: Updated commit log ]",
                                "cve_priority": "low",
                                "cve_public_date": "2026-08-15 06:22:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-74739",
                                "url": "https://ubuntu.com/security/CVE-2026-74739",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net/sched: cls_u32: skip hash tables in u32_bind_class()  u32_walk() enumerates both struct tc_u_hnode and struct tc_u_knode through the walker callback. u32_bind_class() unconditionally casts the passed fh to tc_u_knode and accesses &n->res, so when fh is actually a tc_u_hnode, which has no tcf_result member, this results in a slab-out-of-bounds read of res->classid in tc_cls_bind_class().  The issue can be reproduced with the following commands:      tc qdisc add dev lo root handle 1: hfsc     tc class add dev lo parent 1: classid 1:1 hfsc sc rate 1000kbit     tc filter add dev lo parent 1:1 protocol ip prio 1 u32 match u32 0 0 flowid 1:1     tc class add dev lo parent 1: classid 1:2 hfsc sc rate 2000kbit  Fix this by skipping hash tables via the TC_U32_KEY(handle) check.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-08-26 15:16:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-64015",
                                "url": "https://ubuntu.com/security/CVE-2026-64015",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  security/keys: fix missed RCU read section on lookup  Nicholas Carlini reports that the keyring code calls assoc_array_find() in find_key_to_update() without holding the RCU read lock, while the assoc_array_gc() code really is designed around removing the node from the tree and then freeing it after an RCU grace-period.  The regular key handling doesn't see this because holding the keyring semaphore hides any lifetime issues, but the persistent key handling uses a different model.  Instead of extending the keyring locking, just do the simple RCU locking that the assoc_array was designed for.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-07-19 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-74672",
                                "url": "https://ubuntu.com/security/CVE-2026-74672",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  mm/vmalloc: acquire init_mm lock on huge vmap to avoid ptdump UAF  Patch series \"mm: fix UAF caused by race between ptdump and vmap pgtable freeing\", v6.  Kernel page table walkers fall into two broad categories - those ranges where no exclusion is required via walk_kernel_page_table_range_lockless() and those where exclusion is required via walk_kernel_page_table_range() or walk_page_range_debug().  The former category is used only by arm64 arch code operating on ranges it both wholly owns and does not concurrently write.  The latter category consists of kernel page table walkers operating on ranges that are wholly owned (but which need exclusion against concurrent writers).  The lock used for exclusion is the mmap lock, and for kernel ranges this is the mmap lock on init_mm.  ptdump is a special case being both the only user of walk_page_range_debug(), and the only case in which it walks ranges it does not own.  This presents a problem, as page tables may be freed under ptdump.  And indeed there is a use-after-free bug in the kernel as a result, which this series addresses.  vmap promotes page tables to huge leaf entries where possible, freeing the lower page table when it does.  It does this with no meaningful locks held against concurrent ptdump walks.  As a result, use-after-free can currently occur.  This series addresses the issue by having the vmap huge promotion logic acquire the mmap read lock while both setting the huge page table entry and freeing the prior leaf page table.  The ptdump code already acquires the mmap write lock, so by doing so we ensure that the ptdump walker only ever observes either the huge page table entry or the existing page table entry, and nothing is freed underneath it.  A mitigation for this issue was already applied for arm64 in commit fa93b45fd397 (\"arm64: Enable vmalloc-huge with ptdump\"), which this series has to deal with carefully.  This mitigation resolves the issue by acquiring the mmap read lock on init_mm on vmap page table free if a ptdump is in progress.  However the fix in this series would cause a deadlock if we were to simply apply it for arm64 without also reverting the change.  This is because vmap may acquire the read lock before ptdump attempts to acquire the write lock, which then gets queued, and rwsem starvation rules mean that the (unacknowledged) nested mmap read lock in the arm64 code would also block, meaning the original read lock is never released and thus deadlock.  This series works around this by #ifndef CONFIG_ARM64'ing the mmap read lock in vmap logic, then partially reverting commit fa93b45fd397 (\"arm64: Enable vmalloc-huge with ptdump\"), keeping the enablement of huge vmap support, and removing the ifdeffery with the partial revert patch.  There are related issues that are also addressed in this series:  * x86 page attribute logic, specifically Change Page Attributes (CPA),   implements a feature whereby huge ranges can be collapsed into huge leaf   entries. This can similarly cause a UAF when done in parallel with a   ptdump walk, so similarly acquire the init_mm mmap lock to avoid this.  * The CPA logic allows concurrent page table manipulation and CPA   collapse, meaning the former risks accessing a page table the latter   frees. Fix this by acquiring mmap write lock on init_mm across the   whole CPA collapse operation and read lock on the page table   manipulation.  * x86 and arm64 permit walks of non-kernel mm's (both allowing efi mm   walks, and in x86's case arbitrary mm's), so we ensure kernel mappings   remain stable by locking the init_mm as well as the mm being walked.  The ordering of patches is established for both strict dependencies (the arm64 partial revert in particular has to be done after the vmap changes) and logical ones (the non-kernel mm fix only makes sense once the vmap/CPA fixes are in place).   This patch (of 3):  Currently there is a nasty ra ---truncated---",
                                "cve_priority": "low",
                                "cve_public_date": "2026-08-22 16:16:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99121",
                                "url": "https://ubuntu.com/security/CVE-2026-99121",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ipv4: avoid divide by zero in fib_rebalance  fib_rebalance() computes the total eligible nexthop weight in one pass and programs upper bounds in a second pass. A concurrent change to ignore_routes_with_linkdown can make the first pass return zero while the second pass sees an eligible nexthop, resulting in division by zero.  If the first pass reports a zero total, set each nexthop upper bound to -1 and skip the division. This matches the IPv6 fix in commit d2c26c2911dd (\"ipv6: avoid divide by zero in rt6_multipath_rebalance\") and preserves the lock-free rebalance path.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99124",
                                "url": "https://ubuntu.com/security/CVE-2026-99124",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  s390/pci: Fix leak of uninitialized kernel data in SCLP report  While report_error_write() checks that the provided buffer is at least as large as the header struct, but not that it is large enough to contain the report with the length claimed by report->length. If user-space provides a short buffer, meaning a larger report->length than the actually written payload, up to around 4K of kernel data from past the kmalloc(len + 1) sized buffer allocated in kernfs_fop_write_iter() will leak into the SCLP report.  However, as the entity processing the SCLP is privileged and able to access at least the page including the report, this does not leak data that entity could not access but it is still an out of bounds read and a malformed error report that should be rejected.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99126",
                                "url": "https://ubuntu.com/security/CVE-2026-99126",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  s390/ctcm: Prevent XID null dereference  The mpc_validate_xid() function sets grp->saved_xid2->xid2_flag2 to 0x40 to signal XID validation error. If peer XID is NULL or r/w channel pairing mismatch happens, grp->saved_xid2 is never initialized. An attempt to set the flag in such case leads to NULL dereference.  Fix this by using the always available priv->xid->xid2_flag2 instead of grp->saved_xid2->xid2_flag2 for validation errors.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99127",
                                "url": "https://ubuntu.com/security/CVE-2026-99127",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  page_pool: keep frag_offset aligned for odd-sized requests  page_pool_alloc_frag_netmem() rounds the requested fragment size with  \tsize = ALIGN(size, dma_get_cache_alignment());  dma_get_cache_alignment() returns 1 unless the architecture defines ARCH_DMA_MINALIGN, which DMA-coherent architectures such as x86 do not. There the ALIGN() is a no-op and pool->frag_offset advances by the raw, unrounded size.  A single caller asking for an odd size then leaves frag_offset misaligned for every fragment carved out of that page afterwards.  The pool is shared, so the damage is not confined to the caller that caused it.  The per-cpu system_page_pool used by generic XDP hits this. skb_pp_cow_data() allocates its fragments with the raw packet length:  \tsize = min_t(u32, len, PAGE_SIZE); \ttruesize = size; \tpage = page_pool_dev_alloc(pool, &page_off, &truesize);  leaving frag_offset odd for whatever is carved out of that page next.  Its own head allocation is already aligned -- SKB_HEAD_ALIGN(size) plus the XDP_PACKET_HEADROOM its callers pass -- so it is a later user of the shared pool that pays: page_pool_dev_alloc_va() returns a misaligned buffer, napi_build_skb() installs it as skb->head, and skb_shinfo(skb) == skb->head + skb->end is misaligned with it.  skb_shinfo()->dataref is a 4-byte atomic_t at offset 0x20, so the atomic_inc() in __skb_clone() straddles a cache line.  On x86 with split lock detection -- fatal for kernel split locks by default -- this panics the machine:    Oops: Split lock detected   RIP: 0010:skb_clone+0x154/0x1e0   Call Trace:    <IRQ>    raw_local_deliver+0x1ed/0x2c0    ip_protocol_deliver_rcu+0x54/0x1c0    ip_local_deliver_finish+0x85/0x100    ip_local_deliver+0x67/0x100    __netif_receive_skb_one_core+0x85/0xa0    process_backlog+0x87/0x130  Reproduced by attaching any generic-mode XDP program to loopback and opening a RAW IPPROTO_UDP socket, which makes raw_local_deliver() clone every locally delivered UDP packet; ordinary DNS traffic then triggers it, roughly once per 2500 clones.  Observed on 6.12.101 and 7.1.8.  Tracing page_pool_alloc_frag_netmem() over one such run shows the amplification -- two odd-sized requests, nine misaligned offsets:    requested size & 7:   0: 17035    5: 1    7: 1   frag_offset & 7:      0: 17028    3: 1    4: 1    5: 1    6: 1    7: 5  and skb_pp_cow_data() returning heads that were aligned on entry:    head 0xffff8f4c86aeac00 -> 0xffff8f4c53a9a9c4 (&7=4)   head 0xffff8f4d6a8a42c0 -> 0xffff8f4c4f7b7a45 (&7=5)  Round the fragment size up to at least the alignment struct skb_shared_info requires, so fragments are always suitably aligned for the objects callers build on them.  Architectures needing a larger DMA alignment keep it.  This also makes the remainder computed in page_pool_alloc_netmem(),  \t*size = max_size - *offset;  aligned, since max_size is a power of two -- which fixes the matching misalignment of skb->end.  Verified with a controlled A/B under QEMU/KVM: same tree, same config, same compiler, same rootfs and identical traffic, differing only by this patch.  A SEC(\"xdp.frags\") XDP_PASS program on lo plus UDP datagrams larger than max_head_size drives skb_pp_cow_data()'s fragment loop, which passes raw packet lengths to the pool.  Measured at the return of skb_pp_cow_data():                            unpatched   patched   skb_pp_cow_data calls       40800     40800   misaligned skb->head         1120         0   dataref at line offset >60     80         0  The last row counts the accesses that actually fault: skb_shinfo()->dataref sits at head+end+0x20 and is a 4-byte atomic, so `lock incl` splits a 64-byte cache line only when that address lands at offset 61..63.  All 80 occurrences were at offset 61; the panic reported above was at offset 62.  Eliminating the misalignment removes every one of them.  Same class of bug as commit 3bed3cc4156e (\"net: Do not allocate page fragments t ---truncated---",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99128",
                                "url": "https://ubuntu.com/security/CVE-2026-99128",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  sctp: validate chunk length in the inqueue parser  SCTP chunks always include a four-byte generic header, but sctp_inq_pop() currently accepts shorter declared lengths. A zero-length chunk leaves chunk_end at the current header.  When ASCONF is covered by the association's SCTP-AUTH policy, sctp_assoc_bh_rcv() can continue before the state machine performs its normal chunk-length check. sctp_inq_pop() then returns the same malformed chunk repeatedly and the receive softirq can lock up.  A remote SCTP peer can trigger this after establishing an association on a kernel built with CONFIG_IP_SCTP and configured with net.sctp.addip_enable=1 and net.sctp.auth_enable=1. The reproducer did not require application credentials, a shared SCTP AUTH key, or net.sctp.addip_noauth_enable=1.  On commit f967455fb2a5 (\"seg6: reset IP6CB after IPv6 decapsulation\"), one zero-length ASCONF caused repeated watchdog soft-lockup reports in a two-vCPU KVM guest. All 3 pre-trigger health probes succeeded, while 36 of 37 post-trigger probes failed. With this change, all 37 post-trigger probes succeeded and no equivalent soft-lockup signature appeared.  Reject chunks shorter than the generic SCTP header at the shared inqueue parser boundary. Mark the packet for discard before either caller can continue processing it, while preserving the four-byte generic minimum. Declared-length 1 through 4 controls and kernel-generated ASCONF traffic remained healthy. The patched sctp_hello selftest passed for IPv4 and IPv6.  The complete private reproducer and validation evidence are available directly to maintainers on request.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99133",
                                "url": "https://ubuntu.com/security/CVE-2026-99133",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net/iucv: fix the recvmsg window update  iucv_sock_recvmsg() sends the HiperSockets-only AF_IUCV_FLAG_WIN without testing the transport, so on a classic z/VM socket iucv_send_ctrl() sizes the skb through a NULL iucv->hs_dev. SO_MSGLIMIT accepts 1, so msglimit / 2 is zero and one recvmsg() on its own socket is enough for an unprivileged process to take a spurious disconnect.  It also calls iucv_send_ctrl() under spin_lock_bh(&message_q.lock), which allocates GFP_KERNEL inside a section the code treats as atomic. Sending outside that lock lets two recvmsg() reach afiucv_hs_send() at once, where msg_recv is sampled for the advertised window and subtracted after dev_queue_xmit() -- and sendmsg reaches that counter under lock_sock() while recvmsg holds no socket lock, so both can subtract the same value, the counter goes negative and the credit reaches the peer twice.  Test the transport, claim the credit with atomic_xchg() after the last error exit and hand it back if the transmit fails, and send once the lock is dropped.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99136",
                                "url": "https://ubuntu.com/security/CVE-2026-99136",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  dm-crypt: fix a tiny race condition in crypt_dec_pending  crypt_dec_pending reads io->error before calling atomic_dec_and_test. Another context, for example crypt_endio called from an interrupt, may set io->error and drop its reference between the read and the decrement. crypt_dec_pending then drops the last reference and completes the bio with the stale status - so a read that failed and was never decrypted, or a write that failed, is reported as successful.  The read was placed before the decrement by commit b35f8caa0890 (\"dm crypt: wait for endio to complete before destruction\"), because that commit freed dm_crypt_io before calling bio_endio. This is no longer the case, dm_crypt_io lives in the per-bio data now.  Read io->error after atomic_dec_and_test instead. atomic_dec_and_test is fully ordered, so no additional barrier is needed.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99138",
                                "url": "https://ubuntu.com/security/CVE-2026-99138",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  tcp: fix use-after-free in do_tcp_getsockopt(TCP_CC_INFO)  do_tcp_getsockopt() reads icsk->icsk_ca_ops and dereferences the get_info function pointer without rcu_read_lock(). With BPF struct_ops congestion control, ca_ops can point to dynamically allocated memory that is freed concurrently, resulting in a use-after-free when the kernel dereferences or calls through the stale pointer.    BUG: KASAN: slab-use-after-free in do_tcp_getsockopt+0x2037/0x23e0   Read of size 8 at addr ffff888013701258 by task exploit/149    do_tcp_getsockopt+0x2037/0x23e0 (net/ipv4/tcp.c:4564)    tcp_getsockopt+0x91/0xf0    __sys_getsockopt+0xf7/0x170  Fix this by wrapping the ca_ops load and get_info call within rcu_read_lock()/rcu_read_unlock(), and using READ_ONCE() to load the icsk_ca_ops pointer.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99100",
                                "url": "https://ubuntu.com/security/CVE-2026-99100",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: p54: validate firmware record lengths  The p54 firmware parser accesses component ID and component version records without checking that their lengths cover the fields being read. A malformed record can therefore make the parser read past the record.  Validate the component ID and component version record lengths before accessing their data. The descriptor record is also checked against the shortest descriptor length found in the supported firmware images.  Reject descriptor values that underflow the RX offset or produce an empty RX range before updating the driver state.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-28 04:18:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99140",
                                "url": "https://ubuntu.com/security/CVE-2026-99140",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  tracing: Fix hist trigger timestamps for buffered events  Syzkaller triggered a WARN_ON_ONCE(!nest) warning:    WARNING: kernel/trace/ring_buffer.c:821 at ring_buffer_event_time_stamp   Call trace:     ring_buffer_event_time_stamp     hist_field_timestamp     hist_fn_call     event_hist_trigger     event_triggers_call     __event_trigger_test_discard     trace_event_buffer_commit     do_trace_event_raw_event_sched_switch     trace_event_raw_event_sched_switch  The warning is probabilistically reproducible and is related to syzkaller executing the following commands:    echo 'prev_pid == 999999' > events/sched/sched_switch/filter   echo 'hist:keys=common_timestamp' > events/sched/sched_switch/trigger  The specific triggering process is as follows:  CPU 0                                           CPU 1 (context switching)                             (echo 'hist:keys=common_timestamp' > \\                                                        events/sched/sched_switch/trigger) do_trace_event_raw_event_##call   trace_event_buffer_lock_reserve     if (!tr->no_filter_buffering_ref &&         trace_file->flags & EVENT_FILE_FL_FILTERED)         return entry;  // return directly                                                 event_hist_trigger_parse                                                   hist_register_trigger                                                    tracing_set_filter_buffering(file->tr, true);                                                      tr->no_filter_buffering_ref++;     __trace_buffer_lock_reserve       rb_start_commit         local_inc(&cpu_buffer->committing);  // skipped and not executed   trace_event_buffer_commit     __event_trigger_test_discard       event_triggers_call         event_hist_trigger           hist_fn_call             hist_field_timestamp               ring_buffer_event_time_stamp                 nest = local_read(&cpu_buffer->committing);                 WARN_ON_ONCE(!nest)  // trigger warning  The root cause is that when an event file has a filter attached and the hist trigger has not yet been attached, trace_event_buffer_lock_reserve() writes the event into the per-CPU trace_buffered_event temp buffer instead of reserving it in the ring buffer, so cpu_buffer->committing is not incremented. When the event is later processed at commit time by a hist trigger, hist_field_timestamp() -> ring_buffer_event_time_stamp() sees a zero committing count, triggering WARN_ON_ONCE(!nest).  tracing_event_time_stamp() was added by commit d8279bfc5e959 (\"tracing: Add tracing_event_time_stamp() API\") for exactly this case: if the event is the per-CPU trace_buffered_event, it returns the current ring buffer timestamp. But it never gained a caller. Use it in hist_field_timestamp(), so that a hist trigger that races onto a buffered event records the current time, which is only marginally later than when the event was recorded, instead of warning and recording a bogus timestamp.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99150",
                                "url": "https://ubuntu.com/security/CVE-2026-99150",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  drm/amdgpu: don't drop the runtime PM reference twice in amdgpu_gpr  amdgpu_debugfs_gpr_read() drops its runtime PM reference right after reading the wave registers. When copying them to userspace fails, it jumps to the err label, which drops the reference a second time. A read into a bad buffer on Navi31 either steals a reference somebody else holds (power/runtime_usage goes from 1 to 0) or underflows the count:    amdgpu 0000:03:00.0: Runtime PM usage count underflow!  The registers are already in the kernel buffer at that point, so finish the hardware access first and copy the buffer with a single copy_to_user() instead of the put_user() loop with its own error path.  (cherry picked from commit 31035bbd74f7c3e10c163db875b8e67f8b50ee6a)",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99152",
                                "url": "https://ubuntu.com/security/CVE-2026-99152",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  scsi: libiscsi: Validate the task named by a management response  __iscsi_complete_pdu() fetches the task for five response types from one place and checks only that the index resolved:        case ISCSI_OP_LOGOUT_RSP:       case ISCSI_OP_LOGIN_RSP:       case ISCSI_OP_TEXT_RSP:       case ISCSI_OP_SCSI_TMFUNC_RSP:       case ISCSI_OP_NOOP_IN:               task = iscsi_itt_to_task(conn, hdr->itt);               if (!task)                       return ISCSI_ERR_BAD_ITT;  iscsi_itt_to_task() bounds the index against cmds_max and looks at nothing else, so a target can name any slot in the pool, including one that has never been used. task->conn is then NULL, and both iscsi_nop_out_rsp() and iscsi_complete_task() dereference it. One unsolicited NOP-In is enough; a Text Response carrying the same ITT crashes in iscsi_complete_task() instead.  Require the task to be in flight and not a SCSI command, the way iscsi_itt_to_ctask() does for the command opcodes.  [    6.298634] Oops: general protection fault, probably for non-canonical address 0xdffffc000000000c: 0000 [#1] SMP KASAN NOPTI [    6.298642] KASAN: null-ptr-deref in range [0x0000000000000060-0x0000000000000067] [    6.298652] CPU: 1 UID: 0 PID: 111 Comm: iscsistart Not tainted 7.2.0-rc5-ISCSI1-gf5098b6bae76 #1 PREEMPT(lazy) [    6.298654] Hardware name: QEMU Ubuntu 24.04 PC v2 (i440FX + PIIX, arch_caps fix, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 [    6.298656] RIP: 0010:iscsi_nop_out_rsp.constprop.0+0x46/0x160 [    6.298691] Code: c1 ea 03 48 83 ec 08 80 3c 02 00 0f 85 f5 00 00 00 48 b8 00 00 00 00 00 fc ff df 48 8b 6b 58 48 8d 7d 60 48 89 fa 48 c1 ea 03 <80> 3c 02 00 0f 85 c0 00 00 00 48 8b 45 60 48 39 c3 74 50 48 b8 00 [    6.298698] RSP: 0018:ffff88806c907be8 EFLAGS: 00010206 [    6.298701] RAX: dffffc0000000000 RBX: ffff888006116800 RCX: 0000000000000020 [    6.298702] RDX: 000000000000000c RSI: ffff88800525d578 RDI: 0000000000000060 [    6.298703] RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000 [    6.298706] R10: 0000000000000020 R11: 0000000000000000 R12: 0000000000000000 [    6.298706] R13: 000000000000002e R14: ffff8880056eb440 R15: ffff888006116800 [    6.298707] FS:  00007fc02d1c2740(0000) GS:ffff8880b29bc000(0000) knlGS:0000000000000000 [    6.298710] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [    6.298711] CR2: 000055fe3b56ddf8 CR3: 00000000053b9004 CR4: 0000000000770ef0 [    6.298712] PKRU: 55555554 [    6.298713] Call Trace: [    6.298714]  <IRQ> [    6.298714]  __iscsi_complete_pdu+0x13a8/0x22a0 [    6.298758]  iscsi_complete_pdu+0x54/0xa0 [    6.298759]  iscsi_tcp_hdr_recv_done+0x870/0x2c80 [    6.298778]  iscsi_tcp_recv_skb+0x31e/0xec0 [    6.298800]  iscsi_sw_tcp_recv+0x12f/0x390 [    6.298804]  __tcp_read_sock+0x1ab/0x810 [    6.298812]  iscsi_sw_tcp_data_ready+0x18b/0x510 [    6.298814]  tcp_rcv_established+0x1f56/0x3a00 [    6.298842]  tcp_v4_do_rcv+0x449/0x960 [    6.298847]  tcp_v4_rcv+0x2245/0x3bc0",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99153",
                                "url": "https://ubuntu.com/security/CVE-2026-99153",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  scsi: libiscsi: Validate the ITT reflected in a Reject PDU  A Reject PDU carries a copy of the header it rejects, and iscsi_handle_reject() takes the ITT out of that copy to find the task to clean up:        memcpy(&rejected_pdu, data, sizeof(struct iscsi_hdr));       ...       task = iscsi_itt_to_task(conn, rejected_pdu.itt);  That value is whatever the target put there. iscsi_itt_to_task() bounds the index against cmds_max and checks nothing else, so any task in the pool can be named, and iscsi_nop_out_rsp() then completes it.  An index that has never been used gives a NULL task->conn: the pool is zeroed at session setup and conn is assigned only when a task is allocated. If the task was used and returned, iscsi_complete_task() hits its WARN_ON_ONCE(task->state == ISCSI_TASK_FREE) and the refcount underflows. An in-flight SCSI command is completed as successful - a 1 MiB read returned 1048576 with none of its buffer written and no warning.  Validate the reflected ITT the way iscsi_itt_to_ctask() validates a command ITT, and require the task to be in flight and not a SCSI command.  [    6.248477] Oops: general protection fault, probably for non-canonical address 0xdffffc000000000c: 0000 [#1] SMP KASAN NOPTI [    6.249357] KASAN: null-ptr-deref in range [0x0000000000000060-0x0000000000000067] [    6.249951] CPU: 1 UID: 0 PID: 0 Comm: swapper/1 Not tainted 7.2.0-rc5-ISCSI1-gf5098b6bae76 #1 PREEMPT(lazy) [    6.250718] Hardware name: QEMU Ubuntu 24.04 PC v2 (i440FX + PIIX, arch_caps fix, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 [    6.251616] RIP: 0010:iscsi_nop_out_rsp.constprop.0+0x46/0x160 [    6.252043] Code: c1 ea 03 48 83 ec 08 80 3c 02 00 0f 85 f5 00 00 00 48 b8 00 00 00 00 00 fc ff df 48 8b 6b 58 48 8d 7d 60 48 89 fa 48 c1 ea 03 <80> 3c 02 00 0f 85 c0 00 00 00 48 8b 45 60 48 39 c3 74 50 48 b8 00 [    6.252813] RSP: 0018:ffff88806c907b80 EFLAGS: 00010206 [    6.253042] RAX: dffffc0000000000 RBX: ffff88800607e000 RCX: ffffffff8d571a25 [    6.253345] RDX: 000000000000000c RSI: ffff88806c907c38 RDI: 0000000000000060 [    6.253642] RBP: 0000000000000000 R08: 0000000000000000 R09: fffffbfff235a504 [    6.253947] R10: 0000000000000003 R11: 7463656e6e6f6320 R12: 0000000000000000 [    6.254251] R13: 0000000000000000 R14: ffff88806c907c38 R15: 0000000000000000 [    6.254549] FS:  0000000000000000(0000) GS:ffff8880d95bc000(0000) knlGS:0000000000000000 [    6.254887] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [    6.255140] CR2: 00007fc393e8ffc0 CR3: 0000000005252006 CR4: 0000000000770ef0 [    6.255439] PKRU: 55555554 [    6.255564] Call Trace: [    6.255674]  <IRQ> [    6.255768]  __iscsi_complete_pdu+0x18bf/0x22a0 [    6.256733]  iscsi_complete_pdu+0x54/0xa0 [    6.256905]  iscsi_tcp_data_recv_done+0xf4/0x250 [    6.257103]  iscsi_tcp_recv_skb+0x31e/0xec0 [    6.257680]  iscsi_sw_tcp_recv+0x12f/0x390 [    6.258061]  __tcp_read_sock+0x1ab/0x810 [    6.258853]  iscsi_sw_tcp_data_ready+0x18b/0x510 [    6.259808]  tcp_data_queue+0x1f13/0x4cd0 [    6.260567]  tcp_rcv_established+0x8a5/0x3a00 [    6.261931]  tcp_v4_do_rcv+0x449/0x960 [    6.262269]  tcp_v4_rcv+0x2245/0x3bc0",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99154",
                                "url": "https://ubuntu.com/security/CVE-2026-99154",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  scsi: libiscsi: Reject a negative task index from parse_pdu_itt  A transport that implements parse_pdu_itt hands libiscsi an index taken from the PDU, and both lookups bound it from above only:        if (i >= session->cmds_max)  i and cmds_max are both int, so a negative index passes and session->cmds[i] is read from before the array.  be2iscsi produces one. beiscsi_parse_pdu() assigns the raw tag,        *index = (int)itt;  and beiscsi_complete_pdu() forwards an unsolicited NOP-In from the hardware async ring without replacing its ITT, so the value is the target's. It also reports the session's own age rather than the one in the tag, which leaves the age comparison in iscsi_verify_itt() with nothing to reject.  Bound the index from below in both lookups.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99165",
                                "url": "https://ubuntu.com/security/CVE-2026-99165",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  sctp: revalidate output stream after association connect wait  When message interleaving is enabled, the first send waits for association establishment before building its data chunks.  The wait drops the socket lock, and handshake processing can reduce the output stream count to the peer-advertised inbound stream count.  sctp_stream_init() then frees the extension of every removed stream.  The sender resumes with the stream that it checked before the wait.  If the peer removed that stream, sctp_outq_tail() later dereferences its NULL extension.  Fatal-oops policies then panic the host.  KASAN: null-ptr-deref in range [0x38-0x3f] RIP: sctp_outq_tail+0x49e/0xaa0 Call Trace:  sctp_primitive_SEND  sctp_sendmsg_to_asoc  sctp_sendmsg  A range check alone is insufficient.  Stream reconfiguration can grow the output count again while the lock is released without recreating extensions freed by the earlier shrink.  The stream can then be in range while its extension remains NULL.  The send-buffer wait has the same issue.  Factor the range and extension checks into a helper and repeat both after each send-path wait that drops the socket lock.  Once the lock is reacquired, the validation remains stable through data creation and queueing.  If validation fails after the connect wait, the auto-created association is already established.  Return ESRCH so the existing caller path keeps it under state-machine ownership instead of freeing it directly, which would leave protocol, counter and socket state inconsistent.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99166",
                                "url": "https://ubuntu.com/security/CVE-2026-99166",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net: rds: fix uninitialized trans dereference in CM event handler  rds_rdma_cm_event_handler_cmn() assigns trans only when the RDMA device is an InfiniBand CA (RDMA_NODE_IB_CA).  On any other device type, e.g. an iWARP RNIC such as siw, trans stays uninitialized, but the event switch dereferences it: unconditionally in the RDMA_CM_EVENT_CONNECT_REQUEST case via trans->cm_handle_connect(), and (with a connection context) in the ROUTE_RESOLVED and ESTABLISHED cases.  An RDS listener on an iWARP device therefore crashes the kernel as soon as a connect request arrives: with CONFIG_INIT_STACK_ALL_ZERO the wild load becomes a NULL dereference at offset 0xa0 (&trans->cm_handle_connect) in the iw_cm_wq workqueue.  GCC masks the bug in default builds by folding the uninitialized load into &rds_ib_transport; Clang-built kernels take the real uninitialized path and oops.  The active side can land on a non-IB device too: the id that rds_ib_conn_path_connect() creates is not restricted to a node type, so rdma_resolve_addr() binds it to whichever device serves the local address, and an iWARP RNIC on the same netdev qualifies.  The crash there is different: resolving a route on an iWARP id never fills in cm_id->route.path_rec, and the ROUTE_RESOLVED case writes path_rec[0].sl before it calls into the transport.  The iWARP transport was dropped long ago and IB is the only transport left, so make that explicit: initialize trans to &rds_ib_transport at declaration, drop the conditional assignment, reject a connect request that arrives on a non-IB device, and drop a connection whose address resolved to one instead of resolving a route on it.  The rejection is limited to RDMA_CM_EVENT_CONNECT_REQUEST on purpose: a non-zero return from the handler makes rdma_cm destroy the id the event was delivered on, which is right for the request's freshly created id but would free a connection id that RDS still owns for any other event.  On the active side the id stays ic->i_cm_id and the connection's shutdown destroys it, so that case returns 0.  [achender: reject only on RDMA_CM_EVENT_CONNECT_REQUEST instead of  bailing out for every event on a non-IB device, so that rdma_cm does  not destroy connection ids RDS still tracks; drop a connection whose  address resolved to a non-IB device before a route is resolved on it;  changelog adjusted]",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99167",
                                "url": "https://ubuntu.com/security/CVE-2026-99167",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net/sched: fix use-after-free in __tcf_action_put()  __tcf_action_put() decrements the reference count before decrementing the binding count. Another thread can free the action between these operations, causing the binding-count update to access freed memory. KASAN reports it as:    BUG: KASAN: slab-use-after-free in __tcf_action_put+0x327/0x340   Write of size 4 at addr ff11000000d46420 by task tc-put-pause/64  Hold the action IDR mutex across both counter updates and IDR removal, keeping cleanup outside the lock.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99175",
                                "url": "https://ubuntu.com/security/CVE-2026-99175",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  fsnotify: prevent mark additions during connector teardown  fsnotify_destroy_marks() keeps a reference to its current mark while it drops conn->lock to destroy the mark. This stabilizes the forward-walk cursor, but does not prevent a new mark from being inserted before it. For example, an inotify watch re-added after IN_IGNORED sorts before the old, detached mark for the same group. The walk can miss the replacement and then detach the entire connector from the object.  The replacement is still on its group's marks_list and, for inotify, in the watch IDR. The group mutex no longer protects the connector's object from disappearing. An unprivileged fdinfo read racing the final detach can consequently call igrab(NULL):    BUG: KASAN: null-ptr-deref in igrab+0x24/0x100   Write of size 4 at addr 0000000000000148   Call Trace:    igrab+0x24/0x100    inotify_show_fdinfo+0x1dc/0x5e0    seq_show+0x397/0x690  Set a DESTROYING flag under conn->lock before starting the walk, and reject new marks on that connector with -ENOENT. The existing add-mark error paths undo the temporary group-list entry and the backend's watch allocation. Do not wait for teardown while holding the group mutex, which the destroyer needs. Once the old connector is detached, an add can install a fresh connector as before.  This closes the insertion race for all object types using the common connector teardown, without changing the mark reference or SRCU lifetime rules.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99176",
                                "url": "https://ubuntu.com/security/CVE-2026-99176",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  KVM: nVMX: Reset MMU back to the root MMU if loading L2 state fails for !VM-Entry  Reset the vCPU's MMU pointer back to the root MMU if loading L2 state fails in the \"not from VM-Entry\" case, i.e. when emulating RSM or handling KVM_SET_NESTED_STATE.  Failure to unwind the MMU pointer results in KVM trying to run L1 with a nested MMU, and is especially problematic if the vCPU manages to free its nested state before the VM crashes.  Constructing the root for a nested EPT MMU goes through vmcs12, which is dynamically allocated/freed when nVMX is enabled/disabled.  And so if the nested state is freed with the MMU still pointing at the nested MMU, KVM will hit a NULL pointer deref when attempting to get L1=>L2 EPTP.    BUG: kernel NULL pointer dereference, address: 0000000000000078   #PF: supervisor read access in kernel mode   #PF: error_code(0x0000) - not-present page   PGD 114a2d067 P4D 111743067 PUD 11141f067 PMD 0   Oops: Oops: 0000 [#1] SMP   CPU: 20 UID: 1000 PID: 1272 Comm: nested_tdp_faul Not tainted 7.3.0-rc4-8c89f11d1a99b-sink-vm #1914 PREEMPTLAZY   Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015   RIP: 0010:nested_ept_get_eptp+0xb/0x10 [kvm_intel]   Call Trace:    <TASK>    kvm_mmu_load+0xcd/0x870 [kvm]    kvm_arch_vcpu_ioctl_run+0x18f5/0x1f80 [kvm]    kvm_vcpu_ioctl+0x2c7/0x970 [kvm]    __x64_sys_ioctl+0x90/0xd0    do_syscall_64+0x9c/0x4d0    entry_SYSCALL_64_after_hwframe+0x4b/0x53   RIP: 0033:0x47491b    </TASK>   Modules linked in: kvm_intel kvm irqbypass   CR2: 0000000000000078   ---[ end trace 0000000000000000 ]---   RIP: 0010:nested_ept_get_eptp+0xb/0x10 [kvm_intel]  [sean: write changelog]",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99181",
                                "url": "https://ubuntu.com/security/CVE-2026-99181",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  autofs: ignore notification errors from a replaced pipe  autofs_notify_daemon() takes a reference to the current notification pipe under wq_mutex, then drops the mutex before writing the request. The write can block while the daemon enters catatonic mode and installs a replacement pipe.  If the old pipe's reader is then closed, the delayed write returns -EPIPE and the generic error path enters catatonic mode again. That transition acts on the current superblock state, closes the replacement pipe, and releases the new daemon generation's wait queues.  Only enter catatonic mode when the pipe which failed is still the current pipe. Factor the already-locked transition so the identity check and state change are atomic with respect to another replacement.  This was reproduced on v7.3-rc5-337-gff47652a4b66c in a local QEMU guest. An unprivileged UID 65534 lookup filled the old packet pipe before a normal CATATONIC/SETPIPEFD restart. On the unmodified kernel, the new pipe received HUP and both a pending victim lookup and a later lookup failed with ENOENT in two out of two fresh-mount runs.  With this change, the new pipe remained active, received an intact 304-byte request, and both victim lookups completed in two out of two runs. Normal lookup and restart-without-a-blocked-writer controls passed. No KASAN, oops, refcount, or lock diagnostic was observed. A source reproducer and complete local logs are available privately on request.  The demonstrated impact is limited to denial of a shared autofs service during a legitimate daemon restart. No memory corruption, information leak, privilege escalation, or code execution primitive was observed.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99201",
                                "url": "https://ubuntu.com/security/CVE-2026-99201",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  netlink: avoid hashing the network namespace pointer  The netlink rhashtable key includes a raw struct net pointer and a user-controlled port ID. Both /proc/net/netlink and socket diagnostics expose the table's bucket order. By binding and rebinding chosen NETLINK_USERSOCK port IDs, an unprivileged reader can distinguish equal buckets and recover the low bits of the Jenkins hash. Its 32-bit seed and the limited set of kernel-image slides can then be searched offline to recover the address of init_net.  Use the namespace's unique, non-address net_cookie in the comparison key instead. It is assigned before the per-net initializers run and remains unchanged for the namespace's lifetime. The lookup key and object hash are still built by netlink_compare_arg_init(), keeping lookup, insertion, removal and rehashing consistent while preserving namespace separation. Neither public table walker needs to change.  Reading the socket's namespace cookie in netlink_compare() is safe under RCU, including during namespace teardown. netlink_release() removes the socket from the hash table and defers its final put with call_rcu(). cleanup_net() runs the per-net exit methods and waits for outstanding RCU callbacks with rcu_barrier() before freeing namespace storage.  Unlike ns.ns_id, net_cookie is also available and initialized during setup_net() in older stable kernels, making the change straightforward to backport to v5.15 and later.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99203",
                                "url": "https://ubuntu.com/security/CVE-2026-99203",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  pipe: preserve existing fasync readers on writer setup failure  F_SETFL and FIOASYNC decide whether to invoke ->fasync() before pipe_fasync() takes pipe->mutex. Two enables of one O_RDWR FIFO can therefore both enter the callback.  fasync_helper() allocates before checking for an existing entry. If the first enable installs both entries, a second enable can update the reader entry and then fail the allocation for the writer entry. The error path removes the pre-existing reader entry, clearing FASYNC while the writer entry remains registered. __fput() then skips ->fasync(), so a later pipe notification can dereference the freed file or its f_owner. An unprivileged memory-pressure reproducer triggers a KASAN slab-use-after-free in send_sigio() through this path.  Keep the reader helper's result and undo the registration only if this call added it. The pipe mutex serializes changes to both lists, so a failed new registration still removes its reader, while a failed duplicate preserves the existing registrations and FASYNC. Successful duplicate enables continue to update fa_fd as before.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99204",
                                "url": "https://ubuntu.com/security/CVE-2026-99204",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ocfs2/dlm: Protect the recovery list during debugfs reads  Recovery participant records must remain alive while debug_state_print() walks reco.node_data and formats their fields. The formatter holds dlm->spinlock, but the recovery participant list is protected by dlm_reco_state_lock. In particular, dlm_destroy_recovery_area() detaches the list under dlm_reco_state_lock and frees the detached records after releasing it. A concurrent debugfs open can therefore read freed memory.  Protect the participant traversal and field reads in debug_state_print() with dlm_reco_state_lock, matching the existing list writers. This also serializes the traversal against list_add_tail() during recovery-area initialization. Make the existing lock available to the debug code through dlmcommon.h; the lock remains internal to the OCFS2 DLM module.  Release dlm->spinlock after formatting the other domain state and before acquiring dlm_reco_state_lock, so the debug reader does not nest the two locks. Leave recovery list insertion, detachment and freeing unchanged.  KASAN report as below:      BUG: KASAN: slab-use-after-free in debug_state_open+0x1169/0x12d0     Read of size 4 at addr ffff88810662ef80 by task dlm-state-stres/896      CPU: 1 UID: 0 PID: 896 Comm: dlm-state-stres Not tainted 7.3.0-rc4-next-20260921-pmb-ocfs2-functional-v1+ #1 PREEMPT(lazy)     Hardware name: QEMU Ubuntu 24.04 PC v2 (i440FX + PIIX, arch_caps fix, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014     Call Trace:      <TASK>      dump_stack_lvl+0x93/0xd0      print_report+0xce/0x630      ? debug_state_open+0x1169/0x12d0      ? srso_alias_return_thunk+0x5/0xfbef5      ? __virt_addr_valid+0x20e/0x420      ? debug_state_open+0x1169/0x12d0      kasan_report+0xe0/0x110      ? debug_state_open+0x1169/0x12d0      debug_state_open+0x1169/0x12d0      ? __pfx_debug_state_open+0x10/0x10      full_proxy_open_regular+0x193/0x310      do_dentry_open+0x595/0x12d0      ? __pfx_full_proxy_open_regular+0x10/0x10      vfs_open_consume+0xd1/0x400      ? srso_alias_return_thunk+0x5/0xfbef5      path_openat+0x18d0/0x2020      ? __pfx_path_openat+0x10/0x10      do_file_open+0x21e/0x470      ? __pfx_do_file_open+0x10/0x10      ? _raw_spin_unlock+0x23/0x40      ? srso_alias_return_thunk+0x5/0xfbef5      ? alloc_fd+0x3a6/0x6b0      do_sys_openat2+0xf4/0x1b0      ? __pfx_do_sys_openat2+0x10/0x10      ? srso_alias_return_thunk+0x5/0xfbef5      ? __fput+0x5b5/0xa60      __x64_sys_openat+0x136/0x1e0      ? __pfx___x64_sys_openat+0x10/0x10      do_syscall_64+0x114/0x620      entry_SYSCALL_64_after_hwframe+0x77/0x7f     [Register dump omitted.]      </TASK>      Allocated by task 880:      kasan_save_stack+0x33/0x60      kasan_save_track+0x14/0x30      __kasan_kmalloc+0xaa/0xb0      __kmalloc_cache_noprof+0x28d/0x610      dlm_remaster_locks+0x147/0x1d90      dlm_do_recovery+0xde1/0x1580      dlm_recovery_thread+0x109/0x300      kthread+0x351/0x460      ret_from_fork+0x659/0x940      ret_from_fork_asm+0x1a/0x30      Freed by task 880:      kasan_save_stack+0x33/0x60      kasan_save_track+0x14/0x30      kasan_save_free_info+0x3b/0x60      __kasan_slab_free+0x5f/0x80      kfree+0x308/0x580      dlm_destroy_recovery_area+0x285/0x460      dlm_remaster_locks+0x17c4/0x1d90      dlm_do_recovery+0xde1/0x1580      dlm_recovery_thread+0x109/0x300      kthread+0x351/0x460      ret_from_fork+0x659/0x940      ret_from_fork_asm+0x1a/0x30      The buggy address belongs to the object at ffff88810662ef80      which belongs to the cache kmalloc-32 of size 32     The buggy address is located 0 bytes inside of      freed 32-byte region [ffff88810662ef80, ffff88810662efa0)      [Page and memory-state dumps omitted.]",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99206",
                                "url": "https://ubuntu.com/security/CVE-2026-99206",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  scsi: target: iscsi: Fix race in discovery auth updates  Separate configfs opens can concurrently update the discovery AuthMethod parameter. Both callers may free the same value in iscsi_update_param_value(), causing a double-free.  Protect the lookup and replacement with the discovery TPG access lock, as used by the other TPG configfs parameter updates.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99211",
                                "url": "https://ubuntu.com/security/CVE-2026-99211",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  netlink: reset skb headers before unicast and multicast filtering  Socket filters can use SKF_NET_OFF and SKF_LL_OFF to read relative to an skb's network and MAC headers. Netlink producers may reserve headroom without resetting those headers, allowing a receiving socket's filter to read data before the initialized message.  For example, IWPM HELLO replies are allocated with dev_alloc_skb(), which reserves NET_SKB_PAD bytes. An unprivileged NETLINK_RDMA user can attach a classic socket filter and disclose this headroom through the length of the delivered reply. The resets in netlink_dump() do not help because IWPM sends a separately allocated skb through netlink_unicast().  Reset both headers before running the receiver's filter in unicast and broadcast delivery, as is already done for dump skbs. This also covers other netlink producers that reserve headroom without changing their allocation or message-building code.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99212",
                                "url": "https://ubuntu.com/security/CVE-2026-99212",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net/rds: don't let the rdma_cm destroy an id RDS still owns on route failure  rds_rdma_cm_event_handler_cmn() hands the return value of rdma_resolve_route() straight back to the rdma_cm on RDMA_CM_EVENT_ADDR_RESOLVED.  A synchronous failure there - -ENOMEM from the route work allocation, an SA query that cannot be set up, a RoCE route with no usable device - makes addr_handler() destroy the id the event was delivered on.  That id is ic->i_cm_id, and nothing clears the pointer: the connection sits in RDS_CONN_CONNECTING with a freed id until its shutdown calls rdma_disconnect() and rdma_destroy_id() on it.  The ROUTE_RESOLVED case already avoids this: rds_ib_cm_initiate_connect() forces a zero return while ic->i_cm_id == cm_id, as the comment there explains.  Do the same here - drop the connection and return 0 - so the id stays RDS's to destroy from the shutdown, and the reconnect gets a fresh one.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99213",
                                "url": "https://ubuntu.com/security/CVE-2026-99213",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  vsock: treat TCP_CLOSING as once-established  Handle the TCP_ESTABLISHED -> TCP_CLOSING transition on OP_RST, which can race with the connect loop. Immediately break and return 0 on ESTABLISHED/CLOSING. The return value of connect() should reflect what happened up to the point the connection was established or failed. Events that occur afterwards must not affect it. E.g. even if OP_RW has already set sk_err, connect() should still return 0, not ENOBUFS because of it. Adapt the inaccurate comment above signal_pending().  Resetting a socket that is still present in connected_table can lead to memory corruption. The reporter noted lost transports for in-flight skbs, and I have reproduced crashes caused by re-insertion into connected_table.    list_add double add: new=, prev=, next=.   kernel BUG at lib/list_debug.c:35!   Oops: invalid opcode: 0000 [#1] SMP KASAN NOPTI   Workqueue: vsock-loopback vsock_loopback_work   RIP: 0010:__list_add_valid_or_report+0x11f/0x130   Call Trace:    vsock_insert_connected.cold+0xe/0x13    virtio_transport_recv_pkt+0x10e9/0x1460    vsock_loopback_work+0x305/0x480    process_one_work+0xe4c/0x1560    worker_thread+0x4f1/0xd60    kthread+0x36e/0x470    ret_from_fork+0x47b/0x6b0    ret_from_fork_asm+0x1a/0x30  This fix is supplementary to commit 002541ef650b (\"vsock: Ignore signal/timeout on connect() if already established\"). Details under Link.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99216",
                                "url": "https://ubuntu.com/security/CVE-2026-99216",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  Drivers: hv: Don't reset VMBus connection state on error/exit paths  In two places, current code forces vmbus_connection.conn_state to DISCONNECTED prior to calling vmbus_disconnect(). But vmbus_disconnect() calls vmbus_initiate_unload(), which unloads the VMBus connection only if the conn_state is CONNECTED. Consequently, the connection remains and the Hyper-V host might continue to send messages or post VMBus interrupts.  The problem was introduced in commit 74347a99e73ae (\"x86/Hyper-V: Unload vmbus channel in hv panic callback\"), in that vmbus_initiate_unload() started checking the current connection state before doing the unload. This commit removed some occurrences where conn_state was forced to DISCONNECTED, but these two remained, apparently due to an oversight at the time.  Fix this by not forcing conn_state to DISCONNECTED during VMBus exit, or if a failure occurs when establishing the connection in the first place. Whatever value conn_state has at the time is then read by vmbus_initiate_unload() to determine if there is a connection to be unloaded.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-28 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2022-50167",
                                "url": "https://ubuntu.com/security/CVE-2022-50167",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  bpf: fix potential 32-bit overflow when accessing ARRAY map element  If BPF array map is bigger than 4GB, element pointer calculation can overflow because both index and elem_size are u32. Fix this everywhere by forcing 64-bit multiplication. Extract this formula into separate small helper and use it consistently in various places.  Speculative-preventing formula utilizing index_mask trick is left as is, but explicit u64 casts are added in both places.",
                                "cve_priority": "high",
                                "cve_public_date": "2025-06-18 11:15:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99082",
                                "url": "https://ubuntu.com/security/CVE-2026-99082",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  KVM: x86: Use active memslots for the per-vCPU MMIO cache  KVM tags the per-vCPU MMIO cache with a memslot generation so that a memslot update invalidates cached MMIO information.  Both the fill and validation paths use kvm_memslots(), which unconditionally selects address space 0, even when the vCPU is running in SMM and using address space 1.  Commit 56f17dd3fbc4 (\"kvm: x86: fix stale mmio cache bug\") added the memslot generation to the cache key so that a memslot update could not leave a stale entry valid.  When commit 699023e23965 (\"KVM: x86: add SMM to the MMU role, support SMRAM address space\") added the SMM address space, these helpers were not converted to use the active memslots.  Consequently, an update to the SMM memslots can leave an entry from the old SMM address space apparently valid after the vCPU returns to the normal address space.  A guest can then cause an access to valid RAM at the same GFN to be returned to userspace as KVM_EXIT_MMIO.  Completing that exit through the VMM's RAM address space writes the backing page without going through KVM's write-tracking path.  If the page backs a nested EPT table, KVM can continue using shadow translations derived from the old contents.  The WARN_ON_ONCE() in kvm_mmu_write_protect_fault() catches this invalid cache and memslot combination.  Use the vCPU's active memslots when caching and validating the entry. Memslot generations are unique across address spaces, so the generation also distinguishes the normal and SMM views.  This matches the MMIO SPTE cache, which already uses kvm_vcpu_memslots().  On an unpatched current-mainline kernel, a regression test that fills the cache in SMM and updates only the SMM memslots fails the intended RAM write and triggers the kvm_mmu_write_protect_fault() warning.  With this change, the same test completes the RAM write without a warning.  The x86/smm_test, set_memory_region_test, and memslot_modification_stress_test selftests also pass.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99083",
                                "url": "https://ubuntu.com/security/CVE-2026-99083",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ksmbd: fix heap out-of-bounds write in krb5_authenticate()  In krb5_authenticate(), out_len is calculated to determine available headroom in response_buf for the incoming Kerberos AP-REP token. However, when SMB2_SESSION_SETUP is processed as a non-first element of a compounded SMB2 request, the calculation omits work->next_smb2_rsp_hdr_off.  This causes out_len to overstate remaining buffer headroom by the cumulative size of prior responses in the compound chain. Consequently, the length check in ksmbd_krb5_authenticate() (*out_len <= resp->spnego_blob_len) passes erroneously, allowing memcpy() to write the AP-REP blob past the end of response_buf into adjacent kernel heap memory.  Fix this by subtracting work->next_smb2_rsp_hdr_off when computing out_len, ensuring it accurately reflects physical remaining buffer space.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98977",
                                "url": "https://ubuntu.com/security/CVE-2026-98977",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  namespace: handle mount locking for automounts correctly  If mounts are propagated across user namespaces, attach_recursive_mnt() locks every copy of the source mount to protect overmounts from vanishing and revealing the underlying files or directories.  The user namespace is taken from the caller's mount namespaces since this is where the mounts end up. Except, that's not always true. Automounts may legitimately get popped in by tasks located in a different mount and user namespace during path lookup.  Then check doesn't make sense at that point. The copy in the namespace of the parent - which may be the host's - is now locked and the host cannot change the flags of its own mounts anymore.  Here's the reproducer:  - host has debugfs mounted nosuid,nodev,noexec and shared - tracefs automount below it is not yet active - hand a child process a directory descriptor on that mount - child process enters auser and mount namespace - child process' namespace now holds a locked copy of the host's debugfs   mount that receives propagation from it - child process stats \"tracing/.\" through the descriptor - lookup runs on the host's mount so the automount lands below the host's mount - propagation puts a copy below the child's copy - both try to clear the flags on the mount they got, with a bind remount:      host, on its own automount:            MS_REMOUNT|MS_BIND = EPERM     child, on the copy in its namespace:   MS_REMOUNT|MS_BIND = 0  So the lock landed on the host's mount instead of the child's copy. Congrats. So we need to compare with the owner of the namespace the mount actually gets mounted on. For all regular cases that is the caller's mount namespace and so nothing changes.  Detached trees in anonymous mount namespaces by be handed over via SCM_RIGHTS or inherited in other ways on purpose so the attaching task's mount namespace is authoritative, not the creator of the detached tree.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98992",
                                "url": "https://ubuntu.com/security/CVE-2026-98992",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  namespace: don't copy an unmounted mount tree  may_copy_tree() accepts a mount whose root is an nsfs or pidfs file before it checks whether that mount is mounted. This exception exists for nsfs and pidfs mounts. They are part of no mount namespace so neither check_mnt() nor is_mounted() would let them through and bind-mounting a nsfsfd or a pidfd wouldn't work.  Problem is that exception also admits a bind mount of such a file when it was lazily unmounted and is only kept alive by a file descriptor:    mount --bind /proc/self/ns/net /tmp/x   exec 3< /tmp/x   umount -l /tmp/x   mount --rbind /proc/self/fd/3 /tmp/y  With MS_REC or AT_RECURSIVE copy_tree() doesn't stop at the unmounted mount. It copies every mount that stayed attached to it as well. So if you have a bunch of overmounts over the nsfsfd or the pidfd the whole unmounted stack is copied. That's a bug.  So refuse to walk an unmounted tree. Copying its root alone stays possible. So a bind mount of a namespace that is gone can still be recreated from a file descriptor on the old one. The file descriptor pins that mount and its root and __has_locked_children() only reads the direct children which don't leave the parent's list without namespace_sem. The internal mounts carry MNT_NS_INTERNAL instead of NULL and are still walked. Copying an unmounted tree recursively fails with EINVAL.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98981",
                                "url": "https://ubuntu.com/security/CVE-2026-98981",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  namespace: unhash a dentry before detaching the mounts on it  unlink(), rmdir() and rename() remove the entry from the filesystem, call detach_mounts() on the entry with the inode locked and then call d_delete() once the inode is unlocked.  The thing is that between detach_mounts() and d_delete() the dentry is still hashed and positive. But after detach_mounts() nothing covers the dentry anymore. A lookup that finds this dentry in the dcache can uncover what the mounts hid.  That's a problem when unlinking files or directories that are mountpoints in other mount namespaces. Everybody who had the underlying entry covered can race the detach_mount() call until d_delete() has run.  The race window isn't all that small. It encompasses namespace_unlock() with a full synchronize_rcu_expedited() grace period and the inode_unlock() of the entry.  In my experiments three walkers that kept trying read an overmounted file in 11938 of the 16140 unlinks that removed its mountpoint from a bind mount of the filesystem within a minute.  Fun fact, d_invalidate() has the same ordering problem but gets it right. It unhashes the dentry first and detaches the mounts afterwards. Let's do the same in __detach_mounts():  - A lookup that hasn't found the dentry yet misses it in the dcache and   waits for the directory lock that the caller holds until the name is   gone for good.  - A lockless lookup that found it already fails the mount_lock check   while the dentry still counts as a mountpoint and the d_seq check once   it doesn't, and retries.  This fixes the lockless path. We still need to fix the reference count lookup in a follow-up patch.  So d_drop() the dentry. The dentry stays positive and held but can't be found anymore. Then proceed with the detach and unlink.  Reproducer:  The reads were counted with the program below, three walkers for 60 s in a VM with 4 CPUs. The race window is stretched with the debug patch pasted here. fs.detach_race_walk_us sleeps in lookup_fast() once it found a mountpoint dentry and before its mounts are crossed. fs.detach_race_unlink_us sleeps in vfs_unlink() between detach_mounts() and d_delete().    // SPDX-License-Identifier: GPL-2.0   /*    * unlink_covered: unlink a file that is a mountpoint in a detached copy of    * its mount, against lookups that open it through that copy.    *    * A is a tmpfs with the file f1 (content SECRET_F) and the plain file    * MARK_A. A' is an open_tree(OPEN_TREE_CLONE) copy of A with MARK_A bound    * on A'/f1, held through an O_PATH fd on its root once the tree fd is    * closed. Walkers open f1 through that fd while the driver unlinks A/f1,    * where nothing is mounted on it. A walker may read MARK_A or get ENOENT.    * A read of SECRET_F is a hit: the name was found after its mount was    * gone. The lockless walks use openat2(RESOLVE_CACHED).    *    * usage: unlink_covered [-t seconds] [-w walkers]    */   #ifndef _GNU_SOURCE   #define _GNU_SOURCE   #endif   #include <errno.h>   #include <fcntl.h>   #include <pthread.h>   #include <stdatomic.h>   #include <stdio.h>   #include <stdlib.h>   #include <string.h>   #include <unistd.h>   #include <sys/mount.h>   #include <sys/stat.h>   #include <sys/syscall.h>   #include <linux/openat2.h>    #ifndef __NR_open_tree   #define __NR_open_tree 428   #endif   #ifndef __NR_move_mount   #define __NR_move_mount 429   #endif   #ifndef __NR_openat2   #define __NR_openat2 437   #endif   #ifndef OPEN_TREE_CLONE   #define OPEN_TREE_CLONE 1   #endif   #ifndef OPEN_TREE_CLOEXEC   #define OPEN_TREE_CLOEXEC O_CLOEXEC   #endif   #ifndef MOVE_MOUNT_F_EMPTY_PATH   #define MOVE_MOUNT_F_EMPTY_PATH 0x00000004   #endif    #define WORK \"/tmp/uc\"   #define ADIR WORK \"/A\"    static int duration = 60, nwalkers = 3;   static atomic_int stop, writer_waiting;   static pthread_rwlock_t cur_lock = PTHREAD_RWLOCK_INITIALIZER;   static int cur_fd = -1;\t\t/* the root of A', -1 wh ---truncated---",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99005",
                                "url": "https://ubuntu.com/security/CVE-2026-99005",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  drm/i915/gt: Unmask interrupts only when ACTIVE is true  There is a small race window between intel_rps_boost() reading a stale ACTIVE state and queuing rps->work, where ACTIVE may be changed via asynchronous calls triggered by wakeref drop. This means that rps_work() could be triggered after the GT has been parked, so unmasking RPS PM interrupts would happen without holding PM wakelock. This sequence of events may be observed during live_rc6_ctx_wa() selftest:  1) live_rc6_ctx_wa()    -> intel_engine_pm_put()       -> wakeref_put()  ASYNC1) wakeref_put() callback           -> __engine_park()              -> intel_gt_pm_put_async()                 -> intel_gt_pm_put_async_untracked()                    -> intel_wakeref_put_async()  ASYNC2) wakeref_put_async() callback           -> __gt_park()              -> intel_rps_park()                 -> intel_rps_clear_active() [clear ACTIVE]                 WITH INTERRUPTS:                 -> rps_disable_interrupts()                    -> cancel_work_sync(rps->work)                    -> rps_reset_interrupts() [rps->pm_iir = 0]                 WITHOUT INTERRUPTS (TIMER mode):                 -> rps_stop_timer()                    -> cancel_work_sync(rps->work)  2) live_rc6_ctx_wa()    -> intel_gt_wait_for_idle()       -> intel_gt_retire_requests_timeout()          -> dma_fence_wait_timeout()             -> ops->wait() [i915_fence_wait()]                -> i915_request_wait_timeout()                   -> intel_rps_boost()                      -> intel_rps_is_active() [check ACTIVE]                         [OPEN RACE WINDOW]                      -> queue_work(rps->work)          -> retire_requests()             -> i915_request_retire()                -> intel_rps_dec_waiters() [from 1 to 0]  If ASYNC1 and ASYNC2 would execute during [OPEN RACE WINDOW], then:  3) rps_work() executes from the workqueue and may satisfy    \"(!pm_iir && !client_boost)\" test (in TIMER mode rps->pm_iir    is zeroed by an earlier rps_work() call or never gets a new    value after previous intel_rps_unpark() event), so it jumps    to \"out\" label, bypassing intel_rps_is_active() guard and    executes gen6_gt_pm_unmask_irq();  4) GT is parked and runtime PM wakelock is dropped, so only    a raw reference in __gt_park() ->    intel_display_power_put_async() remains for 100ms, then the    MMIO write in gen6_gt_pm_unmask_irq() detects missing    wakelock via assert_rpm_wakelock_held() and emits    \"RPM wakelock ref not held during HW access\" tainting kernel.  Commit 3e7abf814193 (\"drm/i915: Extract GT render power state management\") dropped the \"if (rps->interrupts_enabled)\" guard that gen6_pm_rps_work() had around this unmask in i915_irq.c. INTEL_RPS_ACTIVE brackets the same window, since it is set in intel_rps_unpark() before rps_enable_interrupts() and rps_start_timer() and cleared in intel_rps_park() before rps_stop_timer() and rps_disable_interrupts().  Skip unmasking when RPS is no longer active (reaching unmask operation is independent of INTERRUPT mode). This does not prevent RPS operation from resuming on the next unpark. In interrupt mode, intel_rps_unpark() calls rps_enable_interrupts(), which enables and unmasks the PM interrupts. In timer mode, it calls rps_start_timer(), restarting periodic engine-busyness evaluation. The timer generates software RPS events and queues rps_work() directly, independently of PM interrupt delivery. Neither mode requires the late worker to unmask interrupts while the GT is parked  (cherry picked from commit ca4a6deadad15b91ee083afe445fa6bdbfb68206)",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99007",
                                "url": "https://ubuntu.com/security/CVE-2026-99007",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  drm/fb-helper: defer setup when fbdev_probe() fails, not just on -EAGAIN  __drm_fb_helper_initial_config_and_unlock() calls drm_client_modeset_probe() first, which already fills in each mode_set->mode/num_connectors for every connected output, and only afterwards calls drm_fb_helper_single_fb_probe() to create fb_helper->fb and wire it into those mode_sets via drm_setup_crtcs_fb().  If drm_fb_helper_single_fb_probe() fails with anything other than -EAGAIN (e.g. dev->driver->fbdev_probe() itself fails), the function bails out before drm_setup_crtcs_fb() runs and before setting fb_helper->deferred_setup. The client is left with mode_sets that have a mode and connectors but mode_set->fb == NULL, and nothing marks this fb_helper as needing a retry.  __drm_fb_helper_restore_fbdev_mode_unlocked() only skips committing when fb_helper->deferred_setup is set, so a later .restore() call (drm_lastclose() on process exit, in this report) commits the stale mode_set through drm_client_modeset_commit() -> drm_client_modeset_commit_atomic() -> __drm_atomic_helper_set_config(), which hits WARN_ON(!set->fb).  Mark fb_helper->deferred_setup on any drm_fb_helper_single_fb_probe() failure, not just -EAGAIN, so restore keeps skipping the commit until a later hotplug event successfully re-probes and re-populates mode_set->fb. The real error code is still returned to the caller unchanged.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99019",
                                "url": "https://ubuntu.com/security/CVE-2026-99019",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  scsi: ch: Do not keep references to data transfer element devices  ch_readconfig() looks up the scsi_device of every data transfer element whose SCSI id the changer reports in READ ELEMENT STATUS, and stores it in ch->dt[]. scsi_device_lookup() takes a reference, and nothing ever drops it: ch_destroy() frees the array with kfree(). ch->dt[] is read nowhere else - it only supplies the vendor, model and revision printed in the same loop.  Once such a drive is removed, its scsi_device can never be released. It stays on the host's device list at its address, so a new device there is refused by anything that walks the list - target_core_pscsi reports \"scsi_device_get() failed for H:C:T:L\" - and the low-level driver's module can no longer be unloaded. Only a reboot recovers.  It shows with any changer that reports its drives' ids; with the mhvtl virtual library (IBM 3573-TL personality), each create and remove of a library with four drives leaves four references behind, counted by the module's use count in lsmod. With ch not bound the count is unchanged, and with this patch applied it is unchanged too.  Drop the reference as soon as the name has been printed, and remove the now unused dt[] array. That also removes the array leaked when ch_probe() fails after ch_readconfig().  The same leak was reported with an RFC patch in 2022, which was not merged.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99024",
                                "url": "https://ubuntu.com/security/CVE-2026-99024",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  optee: register TEE devices only once fully initialized  optee_probe() called tee_device_register() on both the client and the supplicant device before the rest of struct optee had been initialized.  tee_device_register() calls cdev_device_add(), which does two things at once: it creates /dev/tee0 and /dev/teepriv0, and it links the device into the tee class so that class_find_device() can find it. From that moment on the device is reachable both from user space via tee_open() and from kernel space via tee_client_open_context(). The only gate in teedev_open() is tee_device_get(), which merely checks that teedev->desc is non-NULL, which was already set by tee_device_alloc(). Therefore, there is effectively no gate at all.  A context opened in that window can run against a struct optee where    - optee->call_queue.mutex is not initialized by optee_cq_init()   - optee->supp mutex and completions is not initialized by     optee_supp_init()   - optee->rpmb_dev_mutex is not initialized yet,   - the message argument cache is not initialized by     optee_shm_arg_cache_init()   - optee->ctx is still NULL  Any open session or invoke during this window takes uninitialized mutexes and dereferences a NULL pointer.  Fix it by moving both tee_device_register() calls down to the point where all of struct optee is set up.  [JW: adding fixes and cc]",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99036",
                                "url": "https://ubuntu.com/security/CVE-2026-99036",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  dm: fix reading free memory in do_resume  When do_resume calls dm_table_get_mode(new_map), the call is done without holding any locks (it only holds a reference to the md). It may be possible that another concurrent ioctl on the same device will swap table after dm_swap_table and before dm_table_get_mode. In this case, dm_table_get_mode(new_map) reads freed memory.  This race condition was triggered by syzbot.  This commit fixes the race by reading mode of the new table before dm_swap_table. Note that new_map is also passed to dm_ima_need_measure, but this function doesn't attempt to dereference it, so this call should be safe.  Note that this is not a security bug because only root can trigger it and the commonly used tools such as lvm or cryptsetup do not call the ioctls concurrently, so that they can't trigger it acceidentally.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98985",
                                "url": "https://ubuntu.com/security/CVE-2026-98985",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  namespace: check the mounts before reading their parents in pivot_root()  path_pivot_root() reads the parents of new_root and of the caller's root and checks whether they are shared before it checks that either mount is in the caller's mount namespace. Only namespace_sem is held. That's fine for a mount that is in the caller's mount namespace.  But new_root can be a file descriptor to a mount that has been unmounted and that only the file descriptor keeps alive. If that mount stayed attached to its parent when it was unmounted nothing pins the parent for it. The final mntput() of the parent unhooks the children under mount_lock alone and frees the parent afterwards:    pivot_root()                     close(fd), last ref on the parent   ------------                     ---------------------------------   ex_parent = new_mnt->mnt_parent                                    mntput_no_expire_slowpath()                                      __umount_mnt(new_mnt)                                    cleanup_mnt()                                      call_rcu()   IS_MNT_SHARED(ex_parent)    BUG: KASAN: slab-use-after-free in path_pivot_root+0xf1a/0x1840   Read of size 4 at addr ffff8881047382f8 by task pivot_widen/157    path_pivot_root+0xf1a/0x1840    __x64_sys_pivot_root+0x165/0x190  The same goes for the caller's root via chroot(). Both outcomes of the check end in EINVAL so nothing but the read itself goes wrong. It's the same thing commit bb4609405752 (\"statmount: read the parent of an unmounted mount under mount_lock\") fixed for statmount().  Check that both mounts are in the caller's namespace before their parents are read. Every path returns EINVAL either way.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98993",
                                "url": "https://ubuntu.com/security/CVE-2026-98993",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  namespace: don't inherit MNT_UMOUNT in clone_mnt()  MNT_UMOUNT gets raised on a mount that umount_tree() or umount_one() has taken out of its namespace. It's never cleared. __detach_mounts() unhooks a mount that carries it instead of unmounting it.  disconnect_mount() lets an unmounted child stay attached only if its parent carries it. propagate_umount() takes it as the sign that a mount is going to be unmounted when it decides what else can be unmounted, where a chain of locked mounts ends and where a for reparenting an overmount.  clone_mnt() copies the flags of the source and only masks MNT_INTERNAL_FLAGS which doesn't include MNT_UMOUNT. A mount that was lazily unmounted but is kept alive by a file descriptor can still be copied when its root is an nsfs or pidfs file because may_copy_tree() accepts those before checking whether the source is mounted at all:    mount --bind /proc/self/ns/net /tmp/x   exec 3< /tmp/x   umount -l /tmp/x   mount --bind /proc/self/fd/3 /tmp/y  The mount on /tmp/y is attached to the caller's namespace with MNT_UMOUNT already set and every copy of it inherits the flag again.  That causes a number of bugs:  - Unlink its mountpoint from a mount namespace where it isn't one.   __detach_mounts() takes it for a mount that was unmounted earlier,   unhooks it from its parent and drops the reference the namespace   holds on it. It stays in the namespace with one reference too few   and as its own parent, so it can't be unmounted through the file   descriptor anymore and the namespace never finds it again. When the   namespace goes away it's leaked and points to a freed struct   mnt_namespace that may_change_propagation() and anon_ns_root() read   on the next propagation change or mount_setattr() through the file   descriptor.  - Make it shared and unmount a peer. trace_transfers() follows the   flag from the peer into it and strips it from its peer group.  - Let a propagated umount reach it. gather_candidates() marks it with   T_UMOUNT_CANDIDATE but never puts it on the candidate list, so the   mark is never cleared and every later propagated umount skips it. If   it's the parent of a locked mount handle_locked() takes it as the   cutoff and commits the locked child that should have stayed and   disconnect_mount() leaves that child attached to it, unmounted under   a mounted parent, which is what disconnect_mount() exists to   prevent. When the namespace goes away umount_tree() visits the child   a second time. And once __detach_mounts() has made it its own parent   reparent() never finds the end of the chain of unmounted parents.  A clone is a new mount that has never been unmounted. Add MNT_UMOUNT to MNT_INTERNAL_FLAGS so clone_mnt() never copies it. And warn when umount_tree() reaches a mount that already has it set.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99002",
                                "url": "https://ubuntu.com/security/CVE-2026-99002",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  drm/vmwgfx: validate pitch coming from userspace  Validate the pitch, alongside the box dimensions before trying to copy data from the underlying surface. Fixes possible out of bounds reads with cursor snooping.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99027",
                                "url": "https://ubuntu.com/security/CVE-2026-99027",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net: team: stop reusing skb after queue override  A nonzero dev_queue_xmit() result does not return ownership of the skb. When an override port's qdisc drops it, the queue override helper used to try another port or the mode transmit op with the freed skb.  Return the handoff decision separately from transmit success. Select only the first override port under RCU and stop after handing it the skb, regardless of the lower transmit result. Keep the existing success and drop accounting.    BUG: KASAN: slab-use-after-free in sk_skb_reason_drop   Write of size 4 by task poc/5040   sk_skb_reason_drop (net/core/skbuff.c:1240)   dev_kfree_skb_any_reason (net/core/dev.c:3470)   ab_transmit (drivers/net/team/team_mode_activebackup.c:49)   team_xmit (drivers/net/team/team_core.c:1849)   __dev_direct_xmit (net/core/dev.c:4934)   Freed by task 5040:   __tcf_kfree_skb_list (net/sched/sch_generic.c:43)   __dev_queue_xmit (net/core/dev.c:4831)   team_xmit (drivers/net/team/team_core.c:1846)   Kernel panic - not syncing: KASAN: panic_on_warn set ...",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-64190",
                                "url": "https://ubuntu.com/security/CVE-2026-64190",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net: team: fix NULL pointer dereference in team_xmit during mode change  __team_change_mode() clears team->ops with memset() before restoring safe dummy handlers via team_adjust_ops(). A concurrent team_xmit() running under RCU on another CPU can read team->ops.transmit during this window and call a NULL function pointer, crashing the kernel.  The race requires a mode change (CAP_NET_ADMIN) concurrent with transmit on the team device.   BUG: kernel NULL pointer dereference, address: 0000000000000000  Oops: 0010 [#1] SMP KASAN NOPTI  RIP: 0010:0x0  Call Trace:   team_xmit (drivers/net/team/team_core.c:1853)   dev_hard_start_xmit (net/core/dev.c:3904)   __dev_queue_xmit (net/core/dev.c:4871)   packet_sendmsg (net/packet/af_packet.c:3109)   __sys_sendto (net/socket.c:2265)  The original code assumed that no ports means no traffic, so mode changes could freely memset()/memcpy() the ops.  AF_PACKET with forced carrier breaks that assumption.  Prevent the race instead of making it safe: replace memset()/memcpy() with per-field updates that never touch transmit or receive.  Those two handlers are managed solely by team_adjust_ops(), which already installs dummies when tx_en_port_count == 0 (always true during mode change since no ports are present).  WRITE_ONCE/READ_ONCE prevent store/load tearing on the handler pointers.  synchronize_net() before exit_op() drains in-flight readers that may still reference old mode state from before port removal switched the handlers to dummies.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-07-20 17:18:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99041",
                                "url": "https://ubuntu.com/security/CVE-2026-99041",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ip6_gre: remove obsolete ERSPAN PMTU update  A tc tunnel_key action can attach a METADATA_IP_TUNNEL dst to an skb, and mirred can redirect it to a native ip6erspan device. The legacy PMTU update in ip6erspan_tunnel_xmit() treats that metadata dst as a route. Since it has no output device, dst_dev(dst)->mtu dereferences NULL.  On v7.2 with KASAN, an initial UID/GID 65534 process with CapEff 0 used self-created user and network namespaces to trigger:    KASAN: null-ptr-deref   RIP: ip6erspan_tunnel_xmit+0x10fc/0x2cc0   Kernel panic - not syncing: Fatal exception in interrupt  The update is obsolete. Commit fe1a4ca0a2b7 (\"ip6_gre: process toobig in a better way\") changed IPv6 GRE Too Big handling to update the underlay route and removed the equivalent block from __gre6_xmit(). ip6_tnl_xmit() then propagates the underlay PMTU to the overlay route.  Remove the stale ERSPAN copy and its now-unused dst variable. This eliminates the metadata-dst dereference and keeps ERSPAN aligned with IPv6 GRE PMTU handling.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-97935",
                                "url": "https://ubuntu.com/security/CVE-2026-97935",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  tracing: Set the trace clock before registering the histogram trigger  hist_register_trigger() puts the trigger on the global named_triggers list in cmd_ops->init(), and only then sets the trace clock:  \tif (data->cmd_ops->init) { \t\tret = data->cmd_ops->init(data); \t\tif (ret < 0) \t\t\tgoto out; \t}  \tif (hist_data->enable_timestamps) { \t\tret = tracing_set_clock(file->tr, hist_data->attrs->clock); \t\tif (ret) { \t\t\thist_err(tr, HIST_ERR_SET_CLOCK_FAIL, errpos(clock)); \t\t\tgoto out; \t\t}  The clock string is not checked anywhere before that call, so a named trigger using common_timestamp with an unknown clock fails after it has already become findable. event_hist_trigger_parse() then frees it without taking it off the list, and the next lookup by name reads the freed object:   ~# cd /sys/kernel/tracing/events/sched/sched_switch  ~# echo 'hist:name=foo:keys=common_pid:ts=common_timestamp:clock=bogus' > trigger  bash: echo: write error: Invalid argument  ~# echo 'hist:name=foo:keys=common_pid' > trigger    BUG: KASAN: slab-use-after-free in find_named_trigger+0xac/0xc0   Read of size 8 at addr ffff88800915d760 by task init/1    find_named_trigger+0xac/0xc0    hist_register_trigger+0xc1/0x900    event_hist_trigger_parse+0x3146/0x6af0    event_trigger_write+0xce/0x160   Freed by task 63:    kfree+0x154/0x420    trigger_kthread_fn+0xfd/0x160  Set the clock before the trigger is registered, so that nothing which can fail runs after it is published, the way commit 6f86bdeab633 (\"tracing: Fix bad hist from corrupting named_triggers list\") moved the registration below the rest of the setup.  tracing_set_filter_buffering() is reference counted, so the init failure path has to drop the reference that the clock block now takes first.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-09-25 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98944",
                                "url": "https://ubuntu.com/security/CVE-2026-98944",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  HID: steam: Refactor registration  This refactors and simplifies the registration/unregistration flow. Since we now only perform registration when the client isn't opened anymore, the logic for handling that can be removed, and the rest of the function streamlined.  We also remove the previous assumption that we have a serial number to show we're registered, replacing it with a single purpose boolean.  In a previous refactor the code for unregistering a battery if later registration steps failed was accidentally left out. As a result, a lingering power_supply object could get left over after the steam object was torn down. This is also fixed here.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98945",
                                "url": "https://ubuntu.com/security/CVE-2026-98945",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  HID: steam: Rearrange teardown sequence  This fixes a narrow window during the teardown sequence where callbacks could still be scheduled during cleanup that would then have a dangling pointer to the now-freed steam struct.  This also puts work canceling for rumble and mode switch in steam_unregister, as that shouldn't persist while the client hdev is open.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2025-40135",
                                "url": "https://ubuntu.com/security/CVE-2025-40135",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ipv6: use RCU in ip6_xmit()  Use RCU in ip6_xmit() in order to use dst_dev_rcu() to prevent possible UAF.",
                                "cve_priority": "high",
                                "cve_public_date": "2025-11-12 11:15:00 UTC"
                            },
                            {
                                "cve": "CVE-2025-38728",
                                "url": "https://ubuntu.com/security/CVE-2025-38728",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  smb3: fix for slab out of bounds on mount to ksmbd  With KASAN enabled, it is possible to get a slab out of bounds during mount to ksmbd due to missing check in parse_server_interfaces() (see below):   BUG: KASAN: slab-out-of-bounds in  parse_server_interfaces+0x14ee/0x1880 [cifs]  Read of size 4 at addr ffff8881433dba98 by task mount/9827   CPU: 5 UID: 0 PID: 9827 Comm: mount Tainted: G  OE       6.16.0-rc2-kasan #2 PREEMPT(voluntary)  Tainted: [O]=OOT_MODULE, [E]=UNSIGNED_MODULE  Hardware name: Dell Inc. Precision Tower 3620/0MWYPT,  BIOS 2.13.1 06/14/2019  Call Trace:   <TASK>  dump_stack_lvl+0x9f/0xf0  print_report+0xd1/0x670  __virt_addr_valid+0x22c/0x430  ? parse_server_interfaces+0x14ee/0x1880 [cifs]  ? kasan_complete_mode_report_info+0x2a/0x1f0  ? parse_server_interfaces+0x14ee/0x1880 [cifs]    kasan_report+0xd6/0x110    parse_server_interfaces+0x14ee/0x1880 [cifs]    __asan_report_load_n_noabort+0x13/0x20    parse_server_interfaces+0x14ee/0x1880 [cifs]  ? __pfx_parse_server_interfaces+0x10/0x10 [cifs]  ? trace_hardirqs_on+0x51/0x60  SMB3_request_interfaces+0x1ad/0x3f0 [cifs]  ? __pfx_SMB3_request_interfaces+0x10/0x10 [cifs]  ? SMB2_tcon+0x23c/0x15d0 [cifs]  smb3_qfs_tcon+0x173/0x2b0 [cifs]  ? __pfx_smb3_qfs_tcon+0x10/0x10 [cifs]  ? cifs_get_tcon+0x105d/0x2120 [cifs]  ? do_raw_spin_unlock+0x5d/0x200  ? cifs_get_tcon+0x105d/0x2120 [cifs]  ? __pfx_smb3_qfs_tcon+0x10/0x10 [cifs]  cifs_mount_get_tcon+0x369/0xb90 [cifs]  ? dfs_cache_find+0xe7/0x150 [cifs]  dfs_mount_share+0x985/0x2970 [cifs]  ? check_path.constprop.0+0x28/0x50  ? save_trace+0x54/0x370  ? __pfx_dfs_mount_share+0x10/0x10 [cifs]  ? __lock_acquire+0xb82/0x2ba0  ? __kasan_check_write+0x18/0x20  cifs_mount+0xbc/0x9e0 [cifs]  ? __pfx_cifs_mount+0x10/0x10 [cifs]  ? do_raw_spin_unlock+0x5d/0x200  ? cifs_setup_cifs_sb+0x29d/0x810 [cifs]  cifs_smb3_do_mount+0x263/0x1990 [cifs]",
                                "cve_priority": "high",
                                "cve_public_date": "2025-09-04 16:15:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-31678",
                                "url": "https://ubuntu.com/security/CVE-2026-31678",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  openvswitch: defer tunnel netdev_put to RCU release  ovs_netdev_tunnel_destroy() may run after NETDEV_UNREGISTER already detached the device. Dropping the netdev reference in destroy can race with concurrent readers that still observe vport->dev.  Do not release vport->dev in ovs_netdev_tunnel_destroy(). Instead, let vport_netdev_free() drop the reference from the RCU callback, matching the non-tunnel destroy path and avoiding additional synchronization under RTNL.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-04-25 09:16:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99088",
                                "url": "https://ubuntu.com/security/CVE-2026-99088",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net: openvswitch: validate transport header presence in set_ipv6_addr  When executing IPv6 address rewrite actions on IPv6 fragments, set_ipv6_addr() calls update_ipv6_checksum(). If parse_ipv6hdr() processes a non-first IPv6 fragment, it sets key->ip.proto to NEXTHDR_FRAGMENT and returns early without calling skb_set_transport_header().  update_ipv6_checksum() unconditionally evaluates skb_transport_offset() on entry before checking l4_proto.  Because skb->transport_header is uninitialized, this triggers a warning under CONFIG_DEBUG_NET=y although it is completely harmless.  Fix this by returning early in update_ipv6_checksum() if l4_proto is NEXTHDR_FRAGMENT. This avoids reading the uninitialized transport offset for fragments while preserving the debug warning for any other protocol where the transport header is unexpectedly missing.  See the syzbot trace:  !skb_transport_header_was_set(skb) WARNING: ./include/linux/skbuff.h:3075 at skb_transport_header include/linux/skbuff.h:3075 [inline], CPU#1: syz-executor463/5635 WARNING: ./include/linux/skbuff.h:3075 at skb_transport_offset include/linux/skbuff.h:3250 [inline], CPU#1: syz-executor463/5635 WARNING: ./include/linux/skbuff.h:3075 at update_ipv6_checksum net/openvswitch/actions.c:361 [inline], CPU#1: syz-executor463/5635 WARNING: ./include/linux/skbuff.h:3075 at set_ipv6_addr+0x462/0x660 net/openvswitch/actions.c:399, CPU#1: syz-executor463/5635 [...] RIP: 0010:skb_transport_header include/linux/skbuff.h:3075 [inline] RIP: 0010:skb_transport_offset include/linux/skbuff.h:3250 [inline] RIP: 0010:update_ipv6_checksum net/openvswitch/actions.c:361 [inline] RIP: 0010:set_ipv6_addr+0x462/0x660 net/openvswitch/actions.c:399 [...] Call Trace:  <TASK>  set_ipv6 net/openvswitch/actions.c:531 [inline]  do_execute_actions+0x557e/0x8600 net/openvswitch/actions.c:1366  ovs_execute_actions+0xde/0x520 net/openvswitch/actions.c:1592  ovs_packet_cmd_execute+0xb4f/0xf10 net/openvswitch/datapath.c:705  genl_family_rcv_msg_doit+0x233/0x340 net/netlink/genetlink.c:1114  genl_rcv_msg+0x614/0x7a0 net/netlink/genetlink.c:1209  netlink_rcv_skb+0x226/0x4a0 net/netlink/af_netlink.c:2572  genl_rcv+0x28/0x40 net/netlink/genetlink.c:1218  netlink_unicast+0x7bd/0x940 net/netlink/af_netlink.c:1361  netlink_sendmsg+0x813/0xb40 net/netlink/af_netlink.c:1916  sock_sendmsg_nosec+0x14e/0x190 net/socket.c:800",
                                "cve_priority": "negligible",
                                "cve_public_date": "2026-10-26 15:16:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98950",
                                "url": "https://ubuntu.com/security/CVE-2026-98950",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  flow_dissector: avoid u16 truncation of hlen in bpf_flow_dissect()  bpf_flow_dissect() sanitizes the offsets returned by the BPF program with clamp_t(u16, ..., hlen).  If hlen is bigger than 65535, the upper bound is truncated before the comparison. For instance, with hlen == 65536, both nhoff and thoff are forced to zero, even if the program returned sane values.  This is the same class of bug as the one fixed in commit 99bda1ecbd56 (\"flow_dissector: avoid u16 truncation of skb->len when computing thoff\"). That fix does not cover the BPF path, because __skb_flow_dissect() returns early when a BPF flow dissector handles the packet.  struct bpf_flow_keys stores nhoff and thoff as u16, so cap hlen to U16_MAX before clamping.  Found by sashiko while reviewing the commit above.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98955",
                                "url": "https://ubuntu.com/security/CVE-2026-98955",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  flow_dissector: avoid u16 truncation of skb->len when computing thoff  __skb_flow_dissect() computes key_control->thoff using:    key_control->thoff = min_t(u16, nhoff, skb ? skb->len : hlen);  min_t(u16, ...) casts both arguments to u16 before comparing them. Whenever skb->len (or hlen) modulo 65536 is smaller than nhoff, the truncated length wins and thoff is set to a bogus small value, even when the dissection succeeded. For example, an IPv4/TCP frame with skb->len == 65540 and nhoff == 34 gets thoff == 4, so callers such as skb_probe_transport_header() point the transport header inside the Ethernet header.  Such skbs are not exotic: - At the time of commit d0c081b49137 (\"flow_dissector: properly cap   thoff field\"), AF_PACKET with PACKET_VNET_HDR could already build GSO   skbs larger than 64KB (MTU checks are skipped for GSO, and   alloc_skb_with_frags() accepted up to MAX_SKB_FRAGS (17) order-0   pages on top of the linear part). - BIG TCP now makes skbs larger than 64KB common. - The following patch makes tun_get_user() dissect IFF_TAP frames   before eth_type_trans() pulls the Ethernet header, so a GSO frame   carrying a 65522..65535 byte L3 packet will be dissected with   skb->len in [65536, 65549].  Compare as u32 instead. If the resulting offset cannot be represented in the u16 key_control->thoff, cap it to U16_MAX and report the dissection as failed rather than silently returning a wrong transport offset. thoff is still set on failure, as some callers (such as eth_get_headlen()) use it regardless of the return value.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99089",
                                "url": "https://ubuntu.com/security/CVE-2026-99089",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ASoC: samsung: i2s: enable op_clk in probe to balance runtime PM  The probe function puts the device into the runtime PM active state with only the \"iis\" bus clock enabled, but it also sets priv->op_clk to the parent of the RCLK_SRC mux without enabling it. The runtime PM suspend callback disables both clocks, so the first runtime suspend after probe disables op_clk once more than it was enabled.  On Exynos5250 Arndale both clocks resolve to the same EXYNOS_I2S_BUS gate, so this triggers the following warning during boot:   WARNING: drivers/clk/clk.c:1270 at clk_core_disable+0xe4/0x23c, CPU#0: kworker/u8:3/45  i2s_bus already disabled  ...  Workqueue: pm pm_runtime_work  Call trace:   ...   clk_core_disable from clk_disable+0x28/0x34   clk_disable from i2s_runtime_suspend+0x58/0x68 [snd_soc_i2s]   i2s_runtime_suspend [snd_soc_i2s] from genpd_runtime_suspend+0xc4/0x298   genpd_runtime_suspend from __rpm_callback+0x48/0x18c   __rpm_callback from rpm_callback+0x4c/0x50   rpm_callback from rpm_suspend+0xf4/0x718   rpm_suspend from pm_runtime_work+0x9c/0xa0   ...  Fix this by enabling op_clk in probe right after getting it, so the clock state matches the runtime PM active state, and by disabling it in remove.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-26 15:16:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98956",
                                "url": "https://ubuntu.com/security/CVE-2026-98956",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ASoC: adau1372: allow sleepy powerdown GPIOs  gpiod_set_value() emits a WARN when the GPIO provider indicates that it can sleep, as is typical for I2C controlled GPIO expanders. Since the powerdown GPIO is only manipulated in process context, use the _cansleep variant instead. This lets the driver use sleepy GPIOs to power off the chip.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98964",
                                "url": "https://ubuntu.com/security/CVE-2026-98964",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  nvmet: use the local P2P device on metadata allocation failure  nvmet_req_alloc_p2pmem_sgls() assigns req->p2p_dev only after the data and metadata SGL allocations succeed. If the data allocation succeeds but the metadata allocation fails, out_free_sg passes req->p2p_dev to pci_p2pmem_free_sgl() before that assignment has taken place.  Pass the local p2p_dev argument instead, so cleanup uses the same PCI device as the successful data allocation.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98967",
                                "url": "https://ubuntu.com/security/CVE-2026-98967",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  cxgb4/ch_ktls: disable softirqs around tid_list erases  chcr_ktls_cpl_act_open_rpl() inserts into tid_list from the receive path using xa_insert_bh().  The array is shared by the adapter's connections and initialized with XA_FLAGS_LOCK_BH.  However, chcr_ktls_dev_del() and the chcr_ktls_dev_add() error path use xa_erase(), which takes the XArray lock without disabling softirqs.  When cleanup runs with softirqs enabled, a receive softirq for another connection on the same CPU can interrupt the erase and spin on the lock held by the interrupted task.  Use xa_erase_bh() at both sites to match the insertion path.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98969",
                                "url": "https://ubuntu.com/security/CVE-2026-98969",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net/sched: em_text: reject unterminated algo before autoload  This is a follow-up to commit 9c572a83037a (\"net/sched: fix potential stack infoleak in em_text_dump()\"), which zero-initialised the dump-side struct. Sashiko pointed at a pre-existing bug that exposed the change-side input-validation gap open.  em_text_change() casts the raw netlink attribute payload to struct tcf_em_text and passes conf->algo, a 16-byte array with no enforced NUL terminator, to textsearch_prepare().  On the TS_AUTOLOAD retry textsearch_prepare() calls request_module(\"ts_%s\", algo); vsnprintf() walks %s until it finds a NUL, so an algo[] with no NUL reads past the array into the adjacent struct fields and payload and feeds those bytes to the usermode helper command line.  This is an out-of-bounds read and a kernel memory disclosure.  Reject the attribute when no NUL exists within TC_EM_TEXT_ALGOSIZ bytes, matching the check xt_string has had since 3ab720881b6e.  Conditions to recreate the bug: - CAP_NET_ADMIN on the target netns (namespace-local via unshare -Urn   is enough) - install clsact on an interface, then add a basic filter with one text   ematch whose algo[] is 16 bytes with no NUL (e.g. \"A\"*16) and   pattern_len at least 1 - the add fails with -ENOENT and the kernel invokes modprobe with a   module name made of \"ts_\" plus the 16 bytes and the adjacent payload",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98970",
                                "url": "https://ubuntu.com/security/CVE-2026-98970",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  drm/vc4: Free the BO cache size list on teardown  vc4_bo_cache_destroy() purges the cached BOs but never frees the size list, leaking it on every unbind.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98971",
                                "url": "https://ubuntu.com/security/CVE-2026-98971",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  gpio: exar: initialize the ID before registering its cleanup  devm_add_action_or_reset() invokes the cleanup action immediately when registering the action fails.  gpio_exar_probe() currently stores the allocated ID in exar_gpio only after registering the action, so that failure makes exar_devm_ida_free() release ID 0.  If the allocated ID is nonzero, this leaks that ID and can free ID 0 belonging to another device.  Store the ID before registering the cleanup action so both the immediate failure path and normal device teardown release the correct allocation.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98979",
                                "url": "https://ubuntu.com/security/CVE-2026-98979",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  namespace: refuse an automount below a mount that is in no namespace  It's possible to add autmounts even when the parent mount isn't in the mount namespace of the caller. The only requirement we have is that the parent mount namespace must not be NULL, i.e., unmounted.  Problem is that clone_private_mount() has MNT_NS_INTERNAL which makes that trivially true. So that passes the test and attach_recursive_mnt() accepts that as a mount point and funny enough, count_mounts() dereferences MNT_NS_INTERNAL. The problem is it is an error pointer...  So we can reach this in userspace via fanotify. A filesystem mark on the lower filesystem of an overlay reports paths on the layer clone and reading the event hands out a descriptor on it. For example with debugfs as the lower layer it goes kaboom:    openat(evfd, \"tracing\", O_DIRECTORY)    Oops: general protection fault   KASAN: null-ptr-deref in range [0x1d0-0x1d7]   RIP: 0010:count_mounts+0x35/0x200    attach_recursive_mnt    finish_automount  And since that sleeping beauty happens under namespace_sem held for writing every mount operation on the system blocks from then on. Congrats.  Use is_mounted() instead which rejects unmounted and internal mounts alike. The open fails with EINVAL just as it did before clone_private_mount() used MNT_NS_INTERNAL.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98984",
                                "url": "https://ubuntu.com/security/CVE-2026-98984",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  dcache: don't put a mountpoint on a dentry that's being removed  rmdir(), unlink() and rename() call dont_mount() on the victim and then detach_mounts() with the victim's inode locked. do_lock_mount() takes the inode lock of the mountpoint and checks cant_mount() so a mount can't show up after detach_mounts().  But attach_recursive_mnt() makes a second mountpoint for the root of the source mount so that the mounts already located at the destination can be put on top of it. No inode is locked for that one and d_set_mounted() only refuses a dentry that is unlinked. Between detach_mounts() and d_delete() the victim is still hashed:    rmrace: b passed dont_mount() and detach_mounts(), sleeping   T2: move_mount(S, /tmp/plcant/x, BENEATH) = 0 errno 0 ()   T1: rmdir(/tmp/plcant/d/b) = 0 errno 0       109 107 0:61 /d/b//deleted /tmp/plcant/x rw,relatime - tmpfs tmpfs rw       108 109 0:63 / /tmp/plcant/x rw,relatime - tmpfs T rw  A bind mount of the directory that's being removed is moved beneath an existing mount while the rmdir() is located between the two calls. The mount ends up on the removed directory and nothing will ever detach it.  Check cant_mount() in d_set_mounted() as well. dont_mount() raises the flag under d_lock before detach_mounts() runs so either the mountpoint is set first and detach_mounts() finds the mount or the flag is seen and the mount is refused.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98990",
                                "url": "https://ubuntu.com/security/CVE-2026-98990",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  namespace: check a submount for references right before unmounting it  shrink_submounts() and mark_mounts_for_expiry() first collect all the mounts they are allowed to unmount and then unmount them.  Whether a mount is busy is decided by propagate_mount_busy() on the tree. But unmounting the first mount changes the tree that the second one propagates into. propagate_umount() moves a surviving overmount off a copy it unmounts and mounts it where the copy was mounted. If that's where the propagated copy of the second victim is looked up the overmount becomes a candidate of the second umount_tree(). It's childless and so trim_one() commits it without looking at its reference count.  So a synchronous umount pulls out a busy mount that is in use somewhere else and marks it MNT_SYNC_UMOUNT while it has users:    umount2(/tmp/plshrink/p1, 0) = 0 errno 0   cwd is (unreachable)  The same two umounts requested one after the other fail with EBUSY. This needs a mount with MNT_SHRINKABLE, i.e., automounted submounts of NFS, AFS and CIFS or the tracefs mount below debugfs. Bind mounts inherit the flag.  Check each mount right before it is unmounted under the same hold of namespace_sem and mount_lock as the umount itself. Make sure that the algorithm stays linear.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99095",
                                "url": "https://ubuntu.com/security/CVE-2026-99095",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  drm/vc4: drain the hangcheck timer and works on V3D unbind  Nothing stops the hangcheck timer that submitted jobs arm, or the job_done_work that the render-done interrupt queues, at teardown: vc4_irq_disable() cancels only overflow_mem_work, and vc4_gem_destroy() runs from the drm-managed release, after vc4_v3d_unbind() has already uninstalled the V3D interrupt and cleared vc4->v3d. A timer still armed by then reads V3D registers through the NULL vc4->v3d pointer, and the late callbacks run on the vc4_dev embedding them after it has been freed.  Drain them in vc4_v3d_unbind(): shut the timer down and cancel reset_work before the interrupt is taken down, because its vc4_irq_reset() re-enables it, then flush job_done_work so that completions queued at teardown still release their jobs.  This issue was found by an in-house static analysis tool.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-26 15:16:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99006",
                                "url": "https://ubuntu.com/security/CVE-2026-99006",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  drm/i915/gem: Prevent overstepping exec array boundary  It is possible for eb_relocate_parse_slow() to call kvfree() on entries outside the original exec array during following scenario inside eb_relocate_parse_slow():  1) eb_copy_relocations() allocates as many as eb->buffer_count    copies for exec entries; 2) eb_parse() appends up to two VMAs, right after incrementing    eb->buffer_count; 3) cleanup under \"out\" label uses this incremented buffer_count    to release relocation pointers from exec array via kvfree(),    not from VMA array.  To amend this problem, ensure that relocation cleanup uses the original exec object count, excluding the VMAs appended by the command parser.  (cherry picked from commit 2a0158925fb943c7ba8f3216e2734952128defc9)",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99008",
                                "url": "https://ubuntu.com/security/CVE-2026-99008",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  Bluetooth: RFCOMM: Fix NULL tty_dev dereference in rfcomm_dev_shutdown  syzbot hit a NULL pointer dereference in rfcomm_dev_shutdown() when an RFCOMM tty is closed.  rfcomm_dev_add() puts the new device on rfcomm_dev_list first and only then registers the tty device and saves it in dev->tty_dev. If that registration fails, dev->tty_dev is never set at all. The device can be looked up in the meantime, so an open() of /dev/rfcommN gets through rfcomm_tty_install() and attaches to it. When that tty is closed again, rfcomm_dev_shutdown() uses dev->tty_dev without checking it:    Oops: general protection fault, probably for non-canonical address   KASAN: null-ptr-deref in range [0x0000000000000040-0x0000000000000047]   RIP: 0010:rfcomm_dev_shutdown+0x48/0xb0 net/bluetooth/rfcomm/tty.c:131   Call Trace:    tty_port_shutdown+0x1bf/0x220 drivers/tty/tty_port.c:372    tty_port_close+0x4e/0x150 drivers/tty/tty_port.c:705    tty_release+0x359/0x1670 drivers/tty/tty_io.c:1718    __fput+0x418/0xa50 fs/file_table.c:512  rfcomm_dev_destruct() already copes with a NULL dev->tty_dev. Add the same check to rfcomm_dev_shutdown(), so the tty device is only moved when it was actually registered.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99010",
                                "url": "https://ubuntu.com/security/CVE-2026-99010",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  Bluetooth: RFCOMM: free the skb when the DLC has no owner  rfcomm_recv_data() hands the skb to d->data_ready() and returns 0 without freeing it, so the callback owns the skb from that point on. The tty implementation frees it when the DLC has been detached from its device:    static void rfcomm_dev_data_ready(struct rfcomm_dlc *dlc,                                     struct sk_buff *skb)   {           struct rfcomm_dev *dev = dlc->owner;            if (!dev) {                   kfree_skb(skb);                   return;           }  The socket implementation returns without freeing it, and the skb is leaked.  A connected DLC can have no owner: rfcomm_sock_destruct() clears d->owner, while the DLC itself stays on the session until it is closed. Data frames that arrive in that window still find d->state == BT_CONNECTED in rfcomm_recv_data() and are handed to the callback, one leaked skb each.  The leak does not stop on its own either.  The remote runs out of credits only once RFCOMM_RX_THROTTLED is set, and for a socket the only place that sets it is rfcomm_sk_data_ready() itself, below the return. rfcomm_process_dlcs() keeps granting credits, so the remote keeps sending and the leak keeps growing.  Free the skb, as the tty side does.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99015",
                                "url": "https://ubuntu.com/security/CVE-2026-99015",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  Bluetooth: hci_sock: Serialize dead-device detachment  Rebinding an HCI socket after its controller is unregistered can race monitor control replay and crash the kernel. hci_sock_bind() clears hci_pi(sk)->hdev and drops the device reference under only the socket lock, whereas send_monitor_control_replay() holds hci_sk_list.lock for reading.  Replay can observe a non-NULL hdev, then bind can clear it and drop the last reference before create_monitor_ctrl_open() reads hdev->id. This can cause a NULL pointer dereference if the pointer is reloaded, or a use-after-free if the old pointer is retained.  The kernel reported:    KASAN: null-ptr-deref in range [0x0000000000000068-0x000000000000006f]   RIP: 0010:create_monitor_ctrl_open+0x579/0x800   Call Trace:    hci_sock_bind+0xd96/0x1190    __sys_bind+0x166/0x200    __x64_sys_bind+0x6d/0xb0    do_syscall_64+0xdd/0x4a0    entry_SYSCALL_64_after_hwframe+0x77/0x7f  The same missing serialization lets hci_send_to_sock() select a socket for the old device and queue its frame after bind has detached the socket or installed a new binding.  Take hci_sk_list.lock for writing when clearing the device pointer and resetting the socket state. This waits for existing replay and delivery readers to finish before detachment and prevents later readers from using the old binding. Keep hci_dev_put() outside the critical section because the final device release can sleep.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99022",
                                "url": "https://ubuntu.com/security/CVE-2026-99022",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  regulator: ltc3676: don't read the write-only HRST and CLIRQ registers  HRST (0x1e) and CLIRQ (0x1f) are write-only command strobes. Writing HRST triggers a hard reset of the chip and writing CLIRQ clears the interrupt; reading them returns nothing useful, and the read itself fires the command.  The result is that a plain register dump resets the board:    cat /sys/kernel/debug/regmap/2-003c/registers  walks every readable register, hits HRST, and the board reboots.  Split the callback back in two so HRST and CLIRQ stay writable but are no longer readable. The readable range is left unchanged (LTC3676_BUCK1 ... LTC3676_IRQSTAT).",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99025",
                                "url": "https://ubuntu.com/security/CVE-2026-99025",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  openvswitch: fix soft lockup in the netlink flow dump  A production compute node carrying a few thousand datapath flows hit a soft lockup inside a single netlink flow dump and panicked.  ovs_flow_cmd_dump() calls ovs_flow_stats_get() for every flow it emits, and that releases stats->lock with spin_unlock_bh() once per CPU that has touched the flow. Every release is a local_bh_enable(), and each one runs the pending softirq backlog in the dumping thread's own context.  The skb bounds the flows one callback emits, but not the softirq work it absorbs. On a CPU that carries the box's packet load the backlog refills as fast as it drains, so the dumping thread becomes that CPU's softirq engine. It never sleeps and it has no reschedule point, so under voluntary preemption nothing can take the CPU away from it: neither the ksoftirqd the kernel woke to take the work over, nor the stopper thread the softlockup detector dispatches to refresh its timestamp.  Hold BH off across the whole callback instead, the way ctnetlink_dump_table() does, so the nested spin_unlock_bh() stop draining softirqs. The loop already runs under rcu_read_lock() and cannot sleep. What it gives up is preemption under CONFIG_PREEMPT, since a BH-off region is not preemptible outside PREEMPT_RT. The region stays short: the skb caps the flows one callback emits, and empty buckets cost no skb space but are each visited once per dump, as the cursor only moves forward. The table grows on insert and shrinks only on flush, so the walk is bounded by the largest flow count the datapath has held. The softirq backlog the callback used to absorb has no bound at all.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99031",
                                "url": "https://ubuntu.com/security/CVE-2026-99031",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net: bridge: avoid recursive multicast port cleanup  br_multicast_sg_del_exclude_ports() removes automatically added STAR_EXCL port groups by calling br_multicast_del_pg(). For S,G entries, that deletion calls back into br_multicast_sg_del_exclude_ports(), so a large number of STAR_EXCL ports consumes one kernel stack frame per port and can hit the stack guard page.  Keep the complete port-group deletion path for cleanup, but suppress the S,G exclude-port cleanup while that helper is already walking the same entry. Normal deletion callers retain the existing behavior.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99032",
                                "url": "https://ubuntu.com/security/CVE-2026-99032",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net/smc: protect clcsock lifetime in smc_getname  smc_getname() dereferences smc->clcsock without holding clcsock_release_lock. Link-group termination can release the CLC socket through smc_close_active_abort() while the SMC socket is still open, for example after shutdown(SHUT_WR).  A getsockname() caller can load smc->clcsock, then the termination worker can clear the pointer and call sock_release() before the caller accesses clcsock->ops or invokes getname(). This causes a use-after-free; if the worker clears the pointer before the load, it causes a NULL dereference. The syscall's file reference keeps the SMC socket alive but does not prevent asynchronous release of its CLC socket.  KASAN reported the following with test-only timing instrumentation:    BUG: KASAN: slab-use-after-free in smc_getname+0x19e/0x1b0   Read of size 8 at addr ffff888109abb4e0 by task poc/103   Call Trace:    smc_getname+0x19e/0x1b0    do_getsockname+0xe5/0x170    __sys_getsockname+0x8c/0x100    Allocated by task 95:    sock_alloc_inode+0x1e/0x280    sock_alloc+0x3d/0x240    __sock_create+0x7e/0x430    smc_create+0x121/0x240    Freed by task 0:    kmem_cache_free+0xcc/0x340    rcu_core+0x50a/0x1850    Last potentially related work creation:    evict+0x446/0x6c0    smc_clcsock_release+0xa8/0xd0    smc_close_active_abort+0x26a/0x3a0    __smc_lgr_terminate.part.0+0x137/0x2e0  Hold clcsock_release_lock across the pointer check and the getname() callback to serialize with smc_clcsock_release(). Return -EBADF if the CLC socket has already been released, preserving the existing peer state check and the callback's return value otherwise.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99033",
                                "url": "https://ubuntu.com/security/CVE-2026-99033",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net/packet: guard the ll header push in packet_rcv_spkt()  packet_rcv_spkt() restores the link layer header with  \tskb_push(skb, skb->data - skb_mac_header(skb));  That subtraction is only meaningful when the device actually has a link layer header.  packet_rcv() and tpacket_rcv() both wrap it in dev_has_header(), which is also the predicate the block comment at the top of the file states the restore in terms of; packet_rcv_spkt() does not.  commit d549699048b4 (\"net/packet: fix packet receive on L3 devices without visible hard header\") introduced the helper and changed the two call sites, and this one stayed behind.  A device without a visible ll header can leave skb->mac_header at the 0xFFFF sentinel that __alloc_skb() initialises it to.  A CAN skb does: init_can_skb() sets pkt_type and ip_summed but does not reset the headers, and commit 9f10374bb024 (\"can: remove private CAN skb headroom infrastructure\") dropped the skb_reset_*_header() calls that used to be there.  skb_mac_header() is then 0xFFFF, the length becomes a large negative number and skb_push() reports it through skb_under_panic() -- from softirq context, so it is a full system panic even with panic_on_oops=0:    skbuff: skb_under_panic: text:ffffffff8bd21bc1 len:-65455 put:-65471 head:... data:... tail:0x50 end:0x180 dev:can0   kernel BUG at net/core/skbuff.c:214!   RIP: 0010:skb_panic+0x50/0x60   Call Trace:    <IRQ>    skb_push+0x38/0x40    packet_rcv_spkt+0xe1/0x170    __netif_receive_skb_core.constprop.0+0x7e8/0xd30    ...   Kernel panic - not syncing: Fatal exception in interrupt  The socket type is reachable: packet_create() accepts SOCK_PACKET alongside SOCK_RAW and SOCK_DGRAM behind the same CAP_NET_RAW check, and neither the socket length nor a capability check keeps it away from a CAN interface.  The missing skb_reset_*_header() calls in init_can_skb() are a regression in their own right and are being fixed separately, but a packet socket should not turn a link layer that did not initialise its mac header into a kernel panic.  Guard the push the way the other two receive paths do.  Tested on v7.3-rc5 under QEMU with a slcan device on a pty, which is the driver RX path: vcan does not reproduce it, because can_send() resets the headers on the way out.  One SOCK_PACKET socket bound to can0 and one frame written into the line discipline panics an unpatched kernel with the trace above; the same image with this patch prints no panic and powers off normally.  Both kernels are this tree, defconfig plus CONFIG_CAN_SLCAN=y, differing only in this hunk.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99034",
                                "url": "https://ubuntu.com/security/CVE-2026-99034",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  mmc: sdhci-sprd: disable runtime PM on remove  sdhci_sprd_probe() enables runtime PM, while sdhci_sprd_remove() does not perform the corresponding runtime PM cleanup.  The probe failure path disables runtime PM before disabling the clocks, but the normal remove path directly disables clocks that are also managed by the runtime PM callbacks. If the device is runtime suspended, those clocks may already be disabled.  Resume the device before removal, disable runtime PM and drop the temporary runtime PM reference before disabling the clocks.  This issue was found by manual code inspection.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99035",
                                "url": "https://ubuntu.com/security/CVE-2026-99035",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  mmc: mtk-sd: Cancel request timeout work on remove  The driver queues req_timeout while a request is active. msdc_request_done() uses cancel_delayed_work(), which does not wait for a timeout callback that has already started.  The timeout callback calls mmc_request_done(), which wakes the request waiter, and then continues to use host->dev_comp and check the SDIO IRQ. During unbind, msdc_drv_remove() can return and the managed mmc_host can be freed before the callback finishes.  KASAN reported use-after-free accesses in msdc_request_done() and msdc_recheck_sdio_irq() in each of three unbind tests.  The same tests completed without a kernel diagnostic after this change.  Call cancel_delayed_work_sync() after mmc_remove_host() has stopped new requests and before the driver releases the host resources.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99037",
                                "url": "https://ubuntu.com/security/CVE-2026-99037",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  dm-crypt: reject the lmk IV mode with AEAD ciphers  A \"capi:\" table line that pairs an AEAD cipher with the lmk IV mode, for example \"capi:gcm(aes)-lmk\" with the integrity:28:aead option, causes an oops when it is loaded. lmk sets tfms_count to 64, but crypt_alloc_tfms_aead only allocates one transform, so crypt_setkey reads past the end of the tfms_aead array and calls crypto_aead_setkey on the values it finds there.  lmk exists for compatibility with Loop-AES, which uses CBC, so refuse it with an AEAD cipher rather than allocate 64 AEAD transforms. The check cannot go in crypt_iv_lmk_ctr with the other lmk checks, because the IV constructor runs after crypt_set_key.  Note that this is not a security bug because the memory corruption can only be triggered by root.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99038",
                                "url": "https://ubuntu.com/security/CVE-2026-99038",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  memstick: rtsx_usb_ms: complete requests after eject instead of dropping them  memstick_check() can pass its host->removing check just before rtsx_usb_ms_drv_remove() sets eject/removing. Its next request is then silently dropped: rtsx_usb_ms_request() skips schedule_work() once eject is set, and drv_remove's cancel_work_sync() can also cancel a queued handle_req before it picks the request up. Nobody completes card->mrq_complete.  Once memstick core waits for requests without a timeout (\"memstick: core: wait for request completion before freeing card\"), this hangs removal: memstick_check() never returns and memstick_remove_host() blocks in flush_workqueue():    INFO: task kworker/u10:3:65 blocked for more than 20 seconds.   Workqueue: kmemstick memstick_check    __wait_for_common    memstick_check    INFO: task kworker/1:1:33 blocked for more than 20 seconds.   Workqueue: usb_hub_wq hub_event    __flush_workqueue    memstick_remove_host    rtsx_usb_ms_drv_remove  Never drop a request. rtsx_usb_ms_request() always schedules handle_req, and handle_req fails requests with -ENOMEDIUM once eject is set, without touching the device. drv_remove flushes handle_req instead of cancelling it, and cancels it only after memstick_remove_host(), when no new request can arrive, so it cannot run on a freed host.  The host_mutex drain in drv_remove is removed: handle_req always leaves host->req NULL when it finishes, so the drain never had anything to do, and it would now race with handle_req.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99039",
                                "url": "https://ubuntu.com/security/CVE-2026-99039",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  memstick: core: wait for request completion before freeing card  In memstick_alloc_card() and memstick_set_rw_addr(), wait_for_completion_timeout() is used to wait for device identification and address configuration requests to complete.  The memstick subsystem does not provide an abort or cancellation callback in struct memstick_host for in-flight requests. If wait_for_completion_timeout() expires (for instance, when a USB transfer or command retry is delayed), memstick_alloc_card() returns an error and frees the memstick_dev structure via kfree(card).  However, the host controller driver (such as rtsx_usb_ms) is still running the request asynchronously in worker context. When the transfer eventually finishes, the driver writes into host->req->data, which points to memory inside the already freed card structure. This leads to a KASAN slab-use-after-free write:    BUG: KASAN: slab-use-after-free in ms_read_bytes+0x8fe/0x990   Write of size 1 at addr ffff88813c188079 by task kworker/1:5/5239   Workqueue: events rtsx_usb_ms_handle_req   Call Trace:    ms_read_bytes+0x8fe/0x990 drivers/memstick/host/rtsx_usb_ms.c:450    rtsx_usb_ms_issue_cmd drivers/memstick/host/rtsx_usb_ms.c:477 [inline]    rtsx_usb_ms_handle_req+0x557/0x1a00 drivers/memstick/host/rtsx_usb_ms.c:531    process_one_work+0xac7/0x1b10 kernel/workqueue.c:3396    worker_thread+0x5ef/0xe50 kernel/workqueue.c:3560    kthread+0x373/0x450 kernel/kthread.c:436    Allocated by task 1662:    memstick_alloc_card drivers/memstick/core/memstick.c:383 [inline]    memstick_check+0x2c1/0x10d0 drivers/memstick/core/memstick.c:452    process_one_work+0xac7/0x1b10 kernel/workqueue.c:3396    Freed by task 1662:    kfree+0x20c/0x650 mm/slub.c:6792    memstick_alloc_card drivers/memstick/core/memstick.c:420 [inline]    memstick_check+0x72b/0x10d0 drivers/memstick/core/memstick.c:452    process_one_work+0xac7/0x1b10 kernel/workqueue.c:3396  Host controller drivers (rtsx_usb_ms, jmb38x_ms, tifm_ms, r592) already implement their own hardware and bus timeouts, and callers in mspro_block and ms_block already rely on wait_for_completion() unconditionally.  Replace wait_for_completion_timeout() with wait_for_completion() in memstick_set_rw_addr() and memstick_alloc_card() so that the card structure is never freed while an asynchronous request is in flight.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99040",
                                "url": "https://ubuntu.com/security/CVE-2026-99040",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  KEYS: Fix add_key() race with keyring restriction  __key_create_or_update() snapshots keyring->restrict_link before taking the destination keyring's semaphore.  keyring_restrict() installs a restriction while holding that semaphore.  This allows a writer to observe no restriction, wait for the keyring owner to install a reject-all restriction and return successfully, and then link a key using the stale NULL snapshot.  The writer only needs write permission on the destination keyring.  Move the restrict_link read after __key_link_lock() and __key_link_begin().  The read and the subsequent restriction check are then serialized with restriction installation by keyring->sem.  The race was reproduced on v7.2.8 in 19 executions where restriction installation returned before the link completed.  All 19 linked the key despite the reject-all restriction.  With this change, 312 executions reached the same ordering and every add_key() call failed with -EPERM.  The issue was found by manual concurrency analysis assisted by AI-based analysis and independently verified with a QEMU reproducer and kernel instrumentation.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99045",
                                "url": "https://ubuntu.com/security/CVE-2026-99045",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ibmveth: h_free logical LAN on open-fail after register  ibmveth_open() registers the logical LAN, then allocates the RX buffer pools. A pool failure jumps to out_free_buffer_pools without h_free_logical_lan(), so PHYP still owns the buffer-list page when it is unmapped. request_irq() failure already issued the hypercall before taking the same label.  Move that h_free to the shared post-register unwind so both paths deregister before the buffer list is unmapped.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99049",
                                "url": "https://ubuntu.com/security/CVE-2026-99049",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  gpio: xilinx: fix runtime PM leak on request error path  pm_runtime_get_sync() leaves the usage counter incremented even when it fails, and xgpio_request() returns the error without dropping it.  gpiolib does not call ->free() when ->request() fails, so xgpio_free(), which holds the only matching pm_runtime_put(), never runs. The reference is leaked and the controller can no longer runtime-suspend, so its clock stays enabled.  Switch to pm_runtime_resume_and_get(), which only increments the usage counter on success.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99052",
                                "url": "https://ubuntu.com/security/CVE-2026-99052",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  selinux: preserve NATIVE_LABELS on already-initialized sb in set_mnt_opts  When an NFSv4 filesystem exported with security_label is mounted a second time, sget_fc() returns the existing superblock and nfs_get_root() calls security_sb_set_mnt_opts() again on it. Since the superblock is already SB_INITIALIZED, selinux_set_mnt_opts() takes an early exit without setting SECURITY_LSM_NATIVE_LABELS in *set_kern_flags. nfs_get_root() then sees kflags without SECURITY_LSM_NATIVE_LABELS set and clears NFS_CAP_SECURITY_LABEL on the shared nfs_server, silently disabling per-file labeling for both the new and the original mount.  Commit 3815a245b501 (\"security/selinux: fix SECURITY_LSM_NATIVE_LABELS on reused superblock\") fixed the same problem in selinux_sb_clone_mnt_opts().  The reused-superblock path for a plain second mount now goes through sb_set_mnt_opts rather than sb_clone_mnt_opts, so it needs the same treatment: on both SE_SBINITIALIZED early exits, set SECURITY_LSM_NATIVE_LABELS in *set_kern_flags when the superblock was already using SECURITY_FS_USE_NATVE.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99053",
                                "url": "https://ubuntu.com/security/CVE-2026-99053",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  tipc: hold a reference to nodes found by link name  tipc_node_find_by_name() returns a node after dropping its RCU read lock without taking a reference.  The LINK_SET, LINK_GET and LINK_RESET_STATS handlers then lock and access the node, racing with timer-driven cleanup of a down peer.  Generic netlink serialization does not exclude the node timer.  The following interleaving can leave a handler using a freed node:    CPU 0: find the node under RCU and release the node read lock   CPU 1: tipc_node_timeout() clears the links and unlinks the down node   CPU 1: drop the list and timer references, queuing tipc_node_free()   CPU 0: leave the RCU read-side critical section   CPU 1: complete the grace period and free the node   CPU 0: acquire the node lock through the stale pointer  LINK_SET also uses the node's media address after releasing the node lock, when passing queued packets to tipc_bearer_xmit().  KASAN on v7.3-rc5 reported:    BUG: KASAN: slab-use-after-free in _raw_read_lock_bh   Write of size 4 at addr ffff88807e06f008 by task poc/92   Call Trace:    _raw_read_lock_bh                 kernel/locking/spinlock.c:287    tipc_nl_node_set_link             net/tipc/node.c:2475    genl_family_rcv_msg_doit          net/netlink/genetlink.c:1114    genl_rcv_msg                      net/netlink/genetlink.c:1209    netlink_rcv_skb                   net/netlink/af_netlink.c:2575    Allocated by task 0:    tipc_node_create                  net/tipc/node.c:539    tipc_node_check_dest              net/tipc/node.c:1196    tipc_disc_rcv                     net/tipc/discover.c:252    Freed by task 92:    kfree                             mm/slub.c:6801    rcu_core                          kernel/rcu/tree.c:2919    Last potentially related work creation:    __call_rcu_common.constprop.0     kernel/rcu/tree.c:3181    tipc_node_timeout                 net/tipc/node.c:814  Acquire a reference to the selected node with kref_get_unless_zero() before leaving RCU, returning NULL if the node has already been released.  Release that reference on every caller exit after the last node access, including transmission in LINK_SET.  Keep the existing link lookup order and locking so concurrent link removal still takes the existing error paths.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99054",
                                "url": "https://ubuntu.com/security/CVE-2026-99054",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  tipc: destroy topsrv workqueues before closing connections  tipc_topsrv_stop() closed subscriber connections while the topology server's send and receive workqueues were still running. Socket callbacks and subscription events could then queue more work, and in-flight send/recv work could drop the last connection reference during the conn_idr walk.  That race produced several teardown failures: refcount_t addition on 0 from conn_get() on a connection whose release was blocked on idr_lock, a subsequent use-after-free in tipc_conn_close(), queue_work() on an already destroyed workqueue from the listener data-ready callback, and an RCU stall in tipc_topsrv_exit_net() while the walk spun under idr_lock.  Clear srv->listener under idr_lock so it acts as a shutdown flag, skip queue_work() once it is NULL, destroy the workqueues to flush in-flight work, and only then close the remaining connections. Refuse tipc_conn_lookup() after that flag is cleared, and drop idr_lock when the teardown walk finds no connection, so an in-flight subscription event cannot pin idr_in_use while the walk holds the lock.  v3 supersedes the narrower in-thread diff Tung Quang Nguyen posted on 2026-09-23. It keeps his teardown order and adds the lookup refusal and the empty-idr unlock.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99056",
                                "url": "https://ubuntu.com/security/CVE-2026-99056",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  strparser: make sure __strp_recv isn't running before tearing down the parser  The comment above strp_done() claims that if strp is stopped, strp_recv will no longer be called. That's only true if the caller has a mechanism (eg locking) to guarantee that strp_recv() calls that started before strp_stop() have completed by the time we call strp_done().  This adds a dummy lock_sock/release_sock pair to guarantee that any in-flight strp_recv() (which runs under either bh_lock_sock or lock_sock, depending if it's called from ->sk_data_ready or strp_work) has completed.  Only espintcp can be affected by this race condition, but this patch makes sure no future user of strp can have the bug.  This could crash on strp->sk (\"general mode\" of strp), but this mode has been here for 9 years and has never been used. It'll be gone soon, no point worrying about it.  Switch the stopped/paused/etc bits to u8's to avoid races between strp_stop() and strp_pause/unpause().  A reproducer has been published and turns the possible UAF into an exploit [1].",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99057",
                                "url": "https://ubuntu.com/security/CVE-2026-99057",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  xen/netfront: don't leak the skb when xennet_fill_frags() fails  When a response chain has more slots than fit in the skb's frags, xennet_fill_frags() returns an error and xennet_poll() jumps to its error path.  That path moves what's left on tmpq to errq to be freed, but the skb being filled was already dequeued from tmpq, so it's never freed.  Each chain that overflows leaks the skb and the pages attached to it as frags, and the backend decides how many slots it sends.  Put the skb back on tmpq before taking the error path, like the xennet_set_skb_gso() failure just above it does.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99058",
                                "url": "https://ubuntu.com/security/CVE-2026-99058",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  workqueue: Fix NULL current_pwq deref in chained work check  current_wq_worker() only tells us that %current is a kworker. It does not guarantee that the worker is currently executing a work item, as worker->current_pwq is populated only while process_one_work() is running the work function.  is_chained_work() can be reached while queueing on a draining or destroying workqueue. If a kworker outside work-item execution reaches that path, current_wq_worker() returns a worker but worker->current_pwq is NULL, and the chained-work test can fault before it emits the intended warning.  Guard the chained-work test with worker->current_pwq. A kworker without current_pwq is not executing work on the target workqueue, so the helper should return false and let the draining/destroying warning fire.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99059",
                                "url": "https://ubuntu.com/security/CVE-2026-99059",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wireguard: noise: reject response consumption after intermediate initiation  Two threads begin processing the identical response message, received twice. The first thread, A, runs. While it's running, the second one, B, gets partway through, and during that slow calculation, or even while blocking on down_write(), A completes and then also a handshake initiation that's already been queued up runs in thread C, which itself takes that same down_write(). The handshake initiation creation succeeds, and sets the state back to waiting-for-response, and calls up_write(), at which point thread B resumes, because either its finished its calculations or was finally allowed to acquire down_write(). Thread B then copies the state back to the peer, and begins a new session, using that state, which is the same session as the one made in thread A.  Thread A\t\t\tThread B\t\t\tThread C  down_read()  sA = handshake->state  memcpy(cA, handshake->crypto) up_read() if (sA != 1)  goto fail slow_crypto(cA) \t\t\t\tdown_read() \t\t\t\t sB = handshake->state \t\t\t\t memcpy(cB, handshake->crypto) \t\t\t\tup_read() \t\t\t\tif (sB != 1) \t\t\t\t goto fail \t\t\t\tslow_crypto(cB) down_write()  if (sA != handshake->state)   goto fail  memcpy(handshake->crypto, cA)  handshake->state = 2 up_write() down_write()  if (handshake->state != 2)   goto fail  derive_session(handshake->crypto) up_write() \t\t\t\t\t\t\t\tdown_write() \t\t\t\t\t\t\t\t slow_crypto(handshake->crypto) \t\t\t\t\t\t\t\t handshake->state = 1 \t\t\t\t\t\t\t\tup_write() \t\t\t\tdown_write() \t\t\t\t if (sB != handshake->state) \t\t\t\t   goto fail \t\t\t\t memcpy(handshake->crypto, cB) \t\t\t\t handshake->state = 2 \t\t\t\tup_write() \t\t\t\tdown_write() \t\t\t\t if (handshake->state != 2) \t\t\t\t  goto fail \t\t\t\t derive_session(handshake->crypto) \t\t\t\tup_write()  This seems basically impossible to hit in a meaningful way in practice, but ensure that it absolutely cannot happen by comparing the ephemeral private key that's on the stack with the latest one that the peer's handshake state has.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99061",
                                "url": "https://ubuntu.com/security/CVE-2026-99061",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: brcmfmac: fix P2P device removal race in brcmf_detach()  When the driver is removed while the user space process that created the P2P device (e.g. wpa_supplicant) is still exiting, the P2P device interface is removed twice and the kernel crashes.  The two paths are:   - wpa_supplicant, on exit, sends NL80211_CMD_DEL_INTERFACE for the P2P    device. nl80211_del_interface() holds RTNL and the wiphy mutex and    calls brcmf_p2p_del_vif(), which disables discovery and waits up to    1.5 s for BRCMF_E_IF_DEL. Then it calls brcmf_remove_interface(),    which unregisters the wdev and frees the vif and the ifp.   - brcmf_detach() sets the bus down, so BRCMF_E_IF_DEL never arrives,    and calls brcmf_remove_interface(ifp, false) for the same ifp.    brcmf_p2p_ifp_removed() reads ifp->vif and then blocks on    rtnl_lock(). When brcmf_p2p_del_vif() releases RTNL, it calls    cfg80211_unregister_wdev() on the wdev that was already unregistered    and freed.  The second list_del_rcu() of wdev->list faults on LIST_POISON2:    brcmfmac: brcmf_p2p_del_vif delete P2P vif   brcmfmac: brcmf_p2p_deinit_discovery enter   brcmfmac: brcmf_p2p_del_vif P2P: GO_NEG_PHASE status cleared   brcmfmac: brcmf_detach Enter   brcmfmac: brcmf_bus_change_state 1 -> 0   brcmfmac: brcmf_remove_interface Enter, bsscfgidx=1, ifidx=0   brcmfmac: brcmf_del_if Enter, bsscfgidx=1, ifidx=0   brcmfmac: brcmf_p2p_ifp_removed P2P: device interface removed   [1.5 s later, brcmf_p2p_del_vif() timed out]   brcmfmac: brcmf_remove_interface Enter, bsscfgidx=1, ifidx=0   brcmfmac: brcmf_del_if Enter, bsscfgidx=1, ifidx=0   brcmfmac: brcmf_p2p_ifp_removed P2P: device interface removed   Unable to handle kernel paging request at virtual address dead000000000122   Internal error: Oops: 96000044 [#1] PREEMPT_RT SMP   pc : _cfg80211_unregister_wdev+0x6c/0x264 [cfg80211]   Call trace:    _cfg80211_unregister_wdev+0x6c/0x264 [cfg80211]    cfg80211_unregister_wdev+0x10/0x1c [cfg80211]    brcmf_p2p_ifp_removed+0x84/0xb0 [brcmfmac]    brcmf_remove_interface+0x1f4/0x254 [brcmfmac]    brcmf_detach+0x88/0x180 [brcmfmac]    brcmf_sdio_remove+0x90/0x7b0 [brcmfmac]    brcmf_sdiod_remove+0x20/0xa0 [brcmfmac]    brcmf_ops_sdio_remove+0xbc/0x12c [brcmfmac]    sdio_bus_remove+0x38/0x144    device_release_driver_internal+0x1e8/0x2c0    device_release_driver+0x14/0x20    brcmf_sdio_bus_remove+0x2c/0x40 [brcmfmac]    brcmf_fwvid_unregister_vendor+0xd8/0x170 [brcmfmac]    __exit_compat+0x18/0x418 [brcmfmac_cyw]    __arm64_sys_delete_module+0x1ac/0x244  The log was taken with debug=0x406 on an i.MX 8M Plus board with a CYW55513 (Sona IF513) on SDIO. The driver is the Ezurio backport of brcmfmac from v6.18.22 on a 5.4-rt kernel. The code involved is the same in mainline.  To reproduce:    1. Start wpa_supplicant on wlan0 and let it associate. It creates the      P2P device (iw dev shows \"type P2P-device\").   2. Stop wpa_supplicant and remove the driver without waiting for      wpa_supplicant to exit:         kill $(pidof wpa_supplicant)        rmmod brcmfmac_cyw brcmfmac  The crash is reproducible on that board.  For the interface without a netdev (the P2P device), take RTNL and the wiphy mutex in brcmf_detach() before reading iflist, and remove it with locked=true. If brcmf_p2p_del_vif() runs first, brcmf_detach() finds the slot empty. If brcmf_detach() runs first, nl80211 does not find the wdev any more. The interfaces with a netdev are removed as before, because brcmf_del_if() takes RTNL on its own for the primary interface.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99063",
                                "url": "https://ubuntu.com/security/CVE-2026-99063",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  dm ioctl: don't let data_start run past the buffer  struct dm_ioctl has seven bytes of trailing padding, so the smallest buffer userspace is allowed to ask for, offsetof(struct dm_ioctl, data), is seven bytes shorter than sizeof(struct dm_ioctl).  get_result_buffer() sets data_start to sizeof(struct dm_ioctl) without looking at how big the buffer actually is. Ask for the minimum and data_start ends up seven bytes past the end. Callers add it to data_size, and ctl_ioctl() copies that much back to userspace:    BUG: KASAN: slab-out-of-bounds in _copy_to_user+0xad/0xd0   Read of size 312 at addr ffff8880169e4c00 by task repro-dm/140    ctl_ioctl+0x5e3/0xcb0    dm_ctl_ioctl+0x25/0x40   allocated 305-byte region [ffff8880169e4c00, ffff8880169e4d31)  A DM_LIST_DEVICES with data_size set to 305 is enough to hit it, and the seven bytes that leak are whatever sat next to the allocation.  Clamp data_start to the buffer size.  Note that this is not a security bug because the out-of-bounds read can only be triggered by root.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99067",
                                "url": "https://ubuntu.com/security/CVE-2026-99067",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  btrfs: scrub: fix local_root reference leak in scrub_print_warning_inode()  When paths_from_inode() fails, scrub_print_warning_inode() jumps to err without dropping the reference taken by btrfs_get_fs_root(), leaking a reference to the root every time path resolution fails while printing scrub warnings.  Every other error and success path of the function drops the reference.  Drop the reference on the paths_from_inode() failure path too.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99070",
                                "url": "https://ubuntu.com/security/CVE-2026-99070",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ipv6: do not warn on route notification size race  fib6_info_hw_flags_set() sizes the skb with rt6_nlmsg_size() and later fills it with rt6_fill_node().  With nexthop compatibility mode enabled, a concurrent replacement can grow the group between these independent snapshots.  rt6_fill_node() can then legitimately return -EMSGSIZE, so the warning does not prove a sizing bug.  Remove the warning.  The existing error path still frees the skb and reports the error to listeners.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99071",
                                "url": "https://ubuntu.com/security/CVE-2026-99071",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ipv4: do not warn on route notification size race  Commit 680aea08e78c (\"net: ipv4: Emit notification when fib hardware flags are changed\") added asynchronous route notifications for hardware flag changes.  fib_alias_hw_flags_set() sizes the skb with fib_nlmsg_size() and later fills it with fib_dump_info() while holding only RCU.  With nexthop compatibility mode enabled, a concurrent replacement can grow the group between these independent snapshots.  fib_dump_info() can then legitimately return -EMSGSIZE, so the warning does not prove a sizing bug.  Remove the warning.  The existing error path still frees the skb and reports the error to listeners.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99072",
                                "url": "https://ubuntu.com/security/CVE-2026-99072",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ipv4: stop route notification sizing when nexthop group shrinks  Commit 680aea08e78c (\"net: ipv4: Emit notification when fib hardware flags are changed\") added an RCU-only fib_nlmsg_size() call for asynchronous hardware flag notifications.  fib_nlmsg_size() checks fib_info_num_path() before each iteration, then fib_info_nhc() independently reloads nh->nh_grp. If RTM_NEWNEXTHOP replaces a group with fewer paths between those loads, fib_info_nhc() returns NULL and fib_nexthop_nlmsg_size() dereferences it.  Stop sizing when the indexed path is absent. Nexthop groups are dense, so the current snapshot has no later path.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98686",
                                "url": "https://ubuntu.com/security/CVE-2026-98686",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  smb: client: discard post-EOF pagecache when extending a file via zero range  smb3_zero_range() removed the pagecache only for the range being zeroed, so when it extends the file the folio straddling the old EOF - which may hold data dirtied past EOF through an mmap - was never dropped and became visible as file content once the file was extended.  Lower the discard boundary to the smaller of the zero-range offset and the old EOF.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98700",
                                "url": "https://ubuntu.com/security/CVE-2026-98700",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: mac80211: set info->band for 802.3 encap offload frames  Unlike the 802.11 TX paths, ieee80211_8023_xmit() does not set info->band from the channel context on non-MLD interfaces. It stays at 0, so ieee80211_get_tx_rates() uses the wrong band for these frames.  Set it the same way as ieee80211_build_hdr(): drop the frame if there is no channel context, and leave the band at 0 on MLD interfaces.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98716",
                                "url": "https://ubuntu.com/security/CVE-2026-98716",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  KVM: SVM: Use the active VMCB's MSR bitmap when checking if MSR is intercepted  Use the MSR permission bitmap of the active VMCB instead of assuming that KVM is always using vmcb02's bitmap when L2 is active, as KVM uses msrpm02 if and only if L1 wants to intercept MSR accesses, i.e. if and only if KVM needs to merge msprm01 with msrpm12.  Don't bother tracking the virtual address of the bitmap that's being used, as __va() is cheap on x86, and caching the virtual address would introduce yet another source of potentially stale information.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99080",
                                "url": "https://ubuntu.com/security/CVE-2026-99080",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  fs: Free any excess xarray nodes in clear_inode()  For many years we've had a hard to hit leak of xarray nodes.  Hugh documented it well in commit 786b31121a2c.  Recently people and syzbot have found ways to force it to happen with madvise.  Rather than fix the leaks where they happen, just call xa_destroy() which has the side-effect of cycling the i_pages lock.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98709",
                                "url": "https://ubuntu.com/security/CVE-2026-98709",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: mac80211: count only matching reservations in reserved switch  ieee80211_vif_use_reserved_switch() validates a replacement by counting assigned links on ctx->replace_ctx and treating reservations too broadly. A link can still be assigned to the old channel context while holding a reservation that belongs to a different replacement operation.  That can make the current replacement appear complete too early. If another link finalizes first, the function can free the WILL_BE_REPLACED chanctx while the unmatched link and driver still use it, leading to a use-after-free in later beacon generation.  Require an in-place reservation to point at the current replacement context, and require the reserved and assigned contexts to be the matching replacement pair, before counting or moving the link.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98708",
                                "url": "https://ubuntu.com/security/CVE-2026-98708",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: mac80211: keep paired old chanctx alive  An in-place replacement keeps reciprocal replace_ctx pointers between the old WILL_BE_REPLACED chanctx and the new REPLACES_OTHER chanctx. However, the early free paths only consider assigned and reserved link users when deciding whether to free the old chanctx.  That lets the old chanctx be freed too early while the replacement partner still points back to it, either when the last assigned link is released or when that link successfully reassigns to another existing context. Later unreserve and switch-finalization paths can then follow a stale replace_ctx pointer.  Keep a paired old chanctx alive until the replacement pair has been torn down. Apply the same check to both __ieee80211_link_release_channel() and ieee80211_link_use_reserved_reassign(). If the replacement is later abandoned, ieee80211_link_unreserve_chanctx() already tears down the pairing before freeing the old chanctx once no users remain.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98752",
                                "url": "https://ubuntu.com/security/CVE-2026-98752",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  tty: port: fix tty_port_tty_vhangup() race  Drivers rely on tty_port_tty_vhangup() to synchronously hang up their ports before tearing down resources as part of deregistration (e.g. on physical disconnect).  If tty_port_tty_vhangup() races with another hangup it may however return before the port has been shut down. This is in turn can lead to use-after-free and NULL-pointer dereferences in racing ioctls (including a synchronous hangup) and in processing of racing asynchronous hangups (carrier loss).  Add the missing serialisation to tty_port_tty_vhangup() and tty_port_hangup() so that the former does not return until the port has been shut down also when there is a racing hangup.  Note that serial core does not use tty_port_hangup(), but it already holds the port mutex when clearing port->tty and shutting down the port in uart_hangup().",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-99081",
                                "url": "https://ubuntu.com/security/CVE-2026-99081",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  bnxt_en: fix DMA mapping length for padded small packets  Stefan Fleischmann reported Intel IOMMU DMA Read faults on BCM57412 NetXtreme-E NICs when transmitting packets on VLAN/macvlan interfaces:    DMAR: [DMA Read NO_PASID] Request device [18:00.0] fault addr 0xfc499000         [fault reason 0x06] PTE Read access is not set   bnxt_en 0000:18:00.0 eno1np0: Abandoning msg {0xb4 0x41a} len: 0 due to firmware status: 0x2000001   ...   NETDEV WATCHDOG: eno1np0 (bnxt_en): transmit queue 0 timed out  The fault address (0xfc499000) is on an exact 4KB page boundary, pointing to a DMA read buffer overrun.  In bnxt_start_xmit(), packets smaller than BNXT_MIN_PKT_SIZE (52 bytes), such as 42-byte untagged ARP frames, are padded:      if (length < BNXT_MIN_PKT_SIZE) {         pad = BNXT_MIN_PKT_SIZE - length;         if (skb_pad(skb, pad))             goto tx_kick_pending;         length = BNXT_MIN_PKT_SIZE;     }      mapping = dma_map_single(&pdev->dev, skb->data, len, DMA_TO_DEVICE);     ...     dma_unmap_len_set(tx_buf, len, len);  However, 'len' was initialized earlier to skb_headlen(skb) (e.g. 42 bytes) and is left unadjusted after padding. Consequently, dma_map_single() and dma_unmap_len_set() map and track only 42 bytes.  Later, the hardware TX buffer descriptor is programmed with the padded length:      txbd->tx_bd_len_flags_type =         cpu_to_le32(((len + pad) << TX_BD_LEN_SHIFT) | flags |                     TX_BD_FLAGS_PACKET_END);  The NIC DMA engine is thus instructed to read 52 bytes from a region where only 42 bytes were DMA-mapped. If skb->data ends near the boundary of a 4KB page (within 'pad' bytes of the next page), the hardware DMA read overruns into the unmapped adjacent page, triggering an IOMMU fault.  This issue was exposed after commit 447cbe95ebb9 (\"vlan: fix skb_under_panic and races when toggling HW VLAN offload\") because reserving extra VLAN headroom rounded LL_RESERVED_SPACE from 48 up to 64 bytes, shifting skb->data offsets and potentially causing small frames to land right against page boundaries.  Fix this by using skb_put_padto(skb, BNXT_MIN_PKT_SIZE) in bnxt_start_xmit(), before skb_shinfo(skb)->nr_frags is sampled, because padding might linearize the skb. This ensures skb->len and skb_headlen(skb) reflect the padded size so that dma_map_single() maps the full buffer and the descriptor length is consistent. This also removes the temporary 'pad' variable and masking logic.  The padding is done after the SW USO branch, otherwise bnxt_sw_udp_gso_xmit() would account the padding as UDP payload and send it in extra segments.  Note that SW USO segments are still not padded: with IPv4, a segment carrying less than 10 bytes of UDP payload (small gso_size, or a short last segment) is sent as a frame shorter than BNXT_MIN_PKT_SIZE. This is a separate issue, left for a followup patch.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98696",
                                "url": "https://ubuntu.com/security/CVE-2026-98696",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  USB: serial: fix driver deregistration order  USB serial driver modules register one driver for the USB bus and one or more drivers for the ports on the USB serial bus.  When unloading a driver module, the USB driver must be deregistered before the USB serial bus drivers so that I/O is stopped before unbinding the ports to avoid use-after-free in completion handlers accessing port data.  Note that the \"new_id\" attributes must first be removed to prevent new ids from being added and triggering a probe of the USB driver after it has been deregistered.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98705",
                                "url": "https://ubuntu.com/security/CVE-2026-98705",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: mac80211: account proxy paths against the mesh path limit  Proxy-path churn can drive the interface path counter negative and let later mesh path additions exceed MESH_MAX_MPATHS.  mesh_path_free_rcu() decrements the interface mpaths counter for entries from both the mesh and proxy path tables, but mpp_path_add() never reserves a slot in that counter. Removing or expiring a proxy path therefore returns a slot that was never charged.  mesh_path_add() uses the same counter to enforce MESH_MAX_MPATHS, so once it falls below the number of installed paths the limit no longer holds.  Reserve the shared quota before allocating a proxy path and release it on every unsuccessful addition. Mesh and proxy paths now share one 1024-entry budget, so mpp_path_add() can return -ENOSPC at that limit.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98722",
                                "url": "https://ubuntu.com/security/CVE-2026-98722",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  mtd: block2mtd: Fix divide error when erase_size is zero  The erase size is parsed from the \"block2mtd\" module parameter and can be set to zero. add_device() then evaluates          if (size % erase_size)  with a zero divisor, which triggers a divide error:  divide error: 0000 [#1] PREEMPT SMP PTI RIP: 0010:add_device drivers/mtd/devices/block2mtd.c:296 [inline] RIP: 0010:block2mtd_setup2+0x592/0xda0 drivers/mtd/devices/block2mtd.c:459 Call Trace: block2mtd_setup+0x27/0xe0 drivers/mtd/devices/block2mtd.c:476 param_attr_store+0x214/0x310 kernel/params.c:589 module_attr_store+0x65/0x90 kernel/params.c:904 kernfs_fop_write_iter+0x3a4/0x540 fs/kernfs/file.c:345 ...  Reject a zero erase size before performing the modulo operation so the existing \"erasesize must be a divisor of device size\" error path reports the invalid argument and frees the device.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98695",
                                "url": "https://ubuntu.com/security/CVE-2026-98695",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  USB: serial: fix ioctl hangup race  The tty ioctls can race with hangup and end up calling into a tty driver for a device that is already gone or powered down.  Serialise the callbacks using the tty port mutex and add the missing checks to make sure the port has not been hung up before accessing port driver data or hardware.  This specifically avoids dereferencing a NULL-pointer if a device is disconnected during lengthy break signalling.  Note that TIOCGICOUNT and TIOCMIWAIT do not access port driver data or hardware and are therefore not affected by the race.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98694",
                                "url": "https://ubuntu.com/security/CVE-2026-98694",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  thunderbolt: Fix KASAN reported use-after-free when request is canceled  Alan reported that when doing stress testing sometimes KASAN notices use-after-free during control channel operation (stripped down keeping the relevant parts):   BUG: KASAN: slab-use-after-free in tb_cfg_request_sync+0x240/0x250 [thunderbolt]  Read of size 24 at addr ffff88811067f290 by task kworker/u40:2/1760   <TASK>   tb_cfg_request_sync+0x240/0x250 [thunderbolt]   tb_cfg_read_raw+0x367/0x510 [thunderbolt]   tb_cfg_read+0xec/0x240 [thunderbolt]   tb_port_get_link_generation+0x258/0x420 [thunderbolt]   tb_usb3_consumed_bandwidth+0x1c1/0x2c0 [thunderbolt]   tb_tunnel_consumed_bandwidth+0xfd/0x910 [thunderbolt]   tb_available_bandwidth+0x5f2/0xeb0 [thunderbolt]   tb_recalc_estimated_bandwidth+0x2a0/0x1bc0 [thunderbolt]   tb_handle_dp_bandwidth_request+0x1897/0x5e20 [thunderbolt]   process_one_work+0x675/0x1230   worker_thread+0x5e6/0xf70   kthread+0x365/0x470   ret_from_fork+0x54d/0x710   ret_from_fork_asm+0x1a/0x30   </TASK>   Allocated by task 1760:   __kmalloc_cache_noprof+0x1ee/0x550   tb_cfg_read_raw+0x1d3/0x510 [thunderbolt]   tb_cfg_read+0xec/0x240 [thunderbolt]   tb_port_get_link_generation+0x258/0x420 [thunderbolt]   tb_usb3_consumed_bandwidth+0x1c1/0x2c0 [thunderbolt]   tb_tunnel_consumed_bandwidth+0xfd/0x910 [thunderbolt]   tb_available_bandwidth+0x5f2/0xeb0 [thunderbolt]   tb_recalc_estimated_bandwidth+0x2a0/0x1bc0 [thunderbolt]   tb_handle_dp_bandwidth_request+0x1897/0x5e20 [thunderbolt]   process_one_work+0x675/0x1230   worker_thread+0x5e6/0xf70   kthread+0x365/0x470   ret_from_fork+0x54d/0x710   ret_from_fork_asm+0x1a/0x30   Freed by task 926:   kfree+0x18f/0x4a0   tb_cfg_request_put+0xb7/0xe0 [thunderbolt]   tb_cfg_request_work+0x82/0x120 [thunderbolt]   process_one_work+0x675/0x1230   worker_thread+0x5e6/0xf70   kthread+0x365/0x470   ret_from_fork+0x54d/0x710   ret_from_fork_asm+0x1a/0x30   Second to last potentially related work creation:   __queue_work+0x575/0xd00   queue_work_on+0x77/0x80   tb_cfg_request_cancel+0xc7/0x260 [thunderbolt]   tb_cfg_request_sync+0x1f6/0x250 [thunderbolt]   tb_cfg_read_raw+0x367/0x510 [thunderbolt]   tb_cfg_read+0xec/0x240 [thunderbolt]   tb_port_get_link_generation+0x258/0x420 [thunderbolt]   tb_usb3_consumed_bandwidth+0x1c1/0x2c0 [thunderbolt]   tb_tunnel_consumed_bandwidth+0xfd/0x910 [thunderbolt]   tb_available_bandwidth+0x5f2/0xeb0 [thunderbolt]   tb_recalc_estimated_bandwidth+0x2a0/0x1bc0 [thunderbolt]   tb_handle_dp_bandwidth_request+0x1897/0x5e20 [thunderbolt]   process_one_work+0x675/0x1230   worker_thread+0x5e6/0xf70   kthread+0x365/0x470   ret_from_fork+0x54d/0x710   ret_from_fork_asm+0x1a/0x30  The last stack trace is helpful because it shows that we are cancelling a request and looking at tb_cfg_request_cancel() what might happen is that tb_cfg_request_work() completes right before tb_cfg_request_cancel() starts and because of this it will call schedule_work() queueing the same work to run again. However, it is already removed from the request_queue and reference count is dropped so when tb_cfg_request_work() triggers again it will access memory that is already released.  Fix this so that we first make sure a cancelled request is not handed away from tb_cfg_request_find() or scheduled to run. Then instead of relying on the worker to clean up the request we will do it in tb_cfg_request_cancel() after the work is canceled from running. Make tb_cfg_request_dequeue() release the request only if it was actually removed from the queue.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98704",
                                "url": "https://ubuntu.com/security/CVE-2026-98704",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: mac80211: keep fallback association elements alive  Associating to a non-transmitted MBSSID profile reads freed memory while determining the operating channel and applying HT capabilities.  When an association response omits WMM, HT, or VHT information, ieee80211_assoc_config_link() parses the cached BSS IEs and copies the missing element pointers out of that fallback parse. For a non-transmitted MBSSID profile those pointers refer to merged-profile storage owned by the parse object, and the fallback block frees that object at its end. The copied pointers are used afterwards to determine the operating channel, configure bandwidth, and apply HT capabilities.  Keep the fallback parse result alive until association setup finishes.  [reorder variable declaration]",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98707",
                                "url": "https://ubuntu.com/security/CVE-2026-98707",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: mac80211: shut down RX BA session timer on teardown  Tearing down an RX BA session can leave the session timer queued on a freed tid_rx. Later timer-wheel processing and the timer callback itself then run against freed memory.  An RX BAR handler can dereference tid_rx under RCU before teardown unpublishes it and stay in its read-side critical section while teardown deletes the session timer. The stale handler can then rearm the timer after timer_delete_sync() returns and before the RCU callback frees tid_rx.  Use timer_shutdown_sync() so rearm attempts become ineffective once teardown starts. Keep reorder_timer unchanged: teardown marks the session removed under reorder_lock and its release path checks that state before rearming. session_timer has no equivalent guard because ieee80211_rx_h_ctrl() rearms it before taking reorder_lock.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98749",
                                "url": "https://ubuntu.com/security/CVE-2026-98749",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  tty: serial: max3100: shut down timer before freeing port  max3100_shutdown() stops the polling timer but returns early during system suspend. If the SPI device is unbound before resume, the serial core does not call max3100_shutdown() again, so max3100_remove() frees the port while the timer remains armed. max3100_timeout() may then access the freed port and re-arm the timer.  Add final timer teardown to max3100_remove() and use timer_shutdown_sync() to prevent a racing callback from re-arming it. Also free the IRQ and destroy the workqueue there before freeing the port. Keep timer_delete_sync() in max3100_shutdown() so that a subsequent open() can re-arm the timer.  The workqueue is created before request_irq() and destroyed on both request_irq() failure and normal shutdown. Its presence at remove thus identifies the IRQ left registered when suspend bypasses shutdown.  Free the IRQ before destroying the workqueue, in both max3100_shutdown() and max3100_remove(), and cancel the pending work in between. free_irq() waits for a running interrupt handler to finish and no new handler can start afterwards, so a racing handler cannot queue work on a workqueue that is being destroyed; the force_end_work check in max3100_dowork() only narrows that window, as a handler delayed between the check and queue_work() could still run after the teardown has cleared the workqueue pointer. Cancelling the work also keeps destroy_workqueue() from waiting on a queued work item in case remove() ever runs while the freezable workqueue is still frozen, e.g. device removal during the resume window, before workqueues are thawed.  This issue was found by an in-house static analysis tool.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98751",
                                "url": "https://ubuntu.com/security/CVE-2026-98751",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  tty: abort break signalling on hangup  The break ioctls can race with hangup and end up calling into a tty driver for a device that is already gone or powered down.  Drivers must handle this race, but TCSBRK and TCSBRKP should still be aborted to avoid calling back into the driver after a user-controlled timeout (possibly even after the tty has been reopened).  Note that drivers should disable any break state on shutdown so just return on hangup (calling break_ctl() again is racy and will most likely fail for drivers handling the race).",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98753",
                                "url": "https://ubuntu.com/security/CVE-2026-98753",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  tty: tty_port: restore TTY_IO_ERROR on activation failure  Make sure to restore the TTY_IO_ERROR flag if activation fails to prevent I/O attempts on a port that is gone or powered down.  This specifically avoids issues like kernel panic due to unclocked accesses or NULL-pointer dereferences when accessing powered down or deregistered ports when a TTY ioctl races with hangup and open.  Note that the flag is set again in tty_port_close() but not restoring it on activation failure leaves a window where drivers fail to handle the ioctl-hangup race.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98762",
                                "url": "https://ubuntu.com/security/CVE-2026-98762",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  USB: dwc2: shut down wakeup timer before freeing HCD state  dwc2_wakeup_detected() accesses the DWC2 host state and can rearm the wakeup timer.  dwc2_hcd_free() currently deletes the timer only after freeing host-owned state, and timer_delete() does not synchronize a callback or prevent it from being queued again.  Stop and shut down the timer in dwc2_hcd_release(), before the HCD resources are freed.  This covers both the HCD initialization error path and normal HCD removal.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98784",
                                "url": "https://ubuntu.com/security/CVE-2026-98784",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  drm/amdgpu/gfx6: fix firmware leak on teardown  The firmware requested in gfx_v6_0_init_microcode() is not released when the GFX block is torn down, leaking the firmware resources.  Add gfx_v6_0_free_microcode() and call it from gfx_v6_0_sw_fini() to release the PFP, ME, CE and RLC firmware.  (cherry picked from commit 386e81346f95ab0be5a82c5535de932e7a456924)",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98779",
                                "url": "https://ubuntu.com/security/CVE-2026-98779",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  drm/amdgpu: fix ACP MFD device leak on init failure  acp_hw_init() registers ACP child devices with mfd_add_devices() before attaching them to the ACP power domain and initializing the hardware.  If attaching a child to the power domain fails, or if the ACP reset or clock enable operation times out, the failure path frees only the source cell, resource, and platform-data allocations. The child platform devices already registered by mfd_add_devices() remain registered and are never released.  Remove the children from the power domain and unregister the MFD devices on failures that occur after mfd_add_devices() succeeds. Keep mfd_add_devices() failures on the existing cleanup path since the MFD core already rolls back partially registered children itself.  The issue was identified by a static analysis tool I developed and confirmed by manual review.  (cherry picked from commit 63da68d6a2279ec945581c990c5a59a5ae8b5560)",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98742",
                                "url": "https://ubuntu.com/security/CVE-2026-98742",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ALSA: seq: Serialize compat port-info ioctls  The native sequencer ioctl path serializes handler calls with client->ioctl_mutex, but the translated port-info compat path invokes the same handlers through snd_seq_kernel_client_ctl() without taking that mutex.  This lets concurrent compat CREATE_PORT requests pass the port-count check before any request reaches the serialized insertion. The computed integer port index can then exceed the address field range and wrap to an existing index. Subsequent subscriber teardown can resolve the duplicate address to the wrong port and access a freed subscriber.  Take ioctl_mutex while dispatching converted port-info requests, matching the native ioctl path. All translated port-info commands share this helper, so their accesses to the client port state are serialized as well.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98655",
                                "url": "https://ubuntu.com/security/CVE-2026-98655",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  perf: Require kernel access for text poke events  Perf events with exclude_kernel=1 can be opened without kernel perf access. However, exclude_kernel does not suppress text-poke sideband records. Every PERF_RECORD_TEXT_POKE is marked PERF_RECORD_MISC_KERNEL and contains a raw kernel instruction address.  An unprivileged task can therefore open and mmap a task-local software event with text_poke=1. Both opening a count-only tracepoint event and configuring UDP GRO for ESP-in-UDP cause updates to inline static calls; the observer receives the relocated addresses of the modified instructions. For a known kernel image, any such address reveals the runtime kernel text base despite KASLR.  Call perf_allow_kernel() whenever attr.text_poke is set, regardless of exclude_kernel. Events that neither monitor kernel execution nor request text-poke records retain their existing permissions.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98750",
                                "url": "https://ubuntu.com/security/CVE-2026-98750",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  tty: fix saved termios reset race  Resetting saved termios state on device registration is needed where a minor number can be reused for an entirely different device and where the old settings may prevent the port from even being opened (e.g. when CLOCAL is not set).  Not all TTY drivers guarantee that the minor number is no longer in use when registering devices however, something which can lead to a use-after-free when closing a TTY (and saving its termios) races with re-registration.  Add a new TTY_DRIVER_RESET_SAVED_TERMIOS flag to request that any saved termios state is reset on registration and only set it for drivers that make sure that the minor number is no longer in use.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-89638",
                                "url": "https://ubuntu.com/security/CVE-2026-89638",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  smb: client: clear setuid/setgid bit on write with cifsacl/modefromsid/posix extensions  When a file has the setuid or setgid bit set and is written to, the VFS strips those bits and issues a setattr with ATTR_KILL_SUID/ATTR_KILL_SGID together with an ATTR_MODE carrying the already-cleared mode.  Both cifs_setattr_unix() and cifs_setattr_nounix() unconditionally dropped ATTR_MODE in that case:  \t/* skip mode change if it's just for clearing setuid/setgid */ \tif (attrs->ia_valid & (ATTR_KILL_SUID|ATTR_KILL_SGID)) \t\tattrs->ia_valid &= ~ATTR_MODE;  This is fine for the default mount, where the mode is only emulated via the DOS read-only attribute and cannot represent the setuid/setgid bits anyway.  However, with the \"cifsacl\" or \"modefromsid\" mount options the mode is stored on the server through an ACL (id_mode_to_cifs_acl()), with the SMB3.1.1 POSIX extensions the mode is sent to the server directly, and with the SMB1 Unix extensions (cifs_setattr_unix) the mode is sent via CIFSSMBUnixSetPathInfo().  In all those cases dropping ATTR_MODE means the cleared mode is never pushed to the server, so the setuid/setgid bit survives the write.  This is a security issue: on local filesystems the setuid bit is stripped when a file is written, but over these cifs.ko mounts the bit persists on the server, potentially allowing an unexpected privilege escalation on subsequent execution.  Fix this in two places:    1. cifs_setattr_nounix(): only take the \"skip mode change\" shortcut      when the mode is emulated via the DOS read-only attribute (i.e.      neither cifsacl/modefromsid nor the SMB3.1.1 POSIX extensions are      in effect), so that the cleared mode is propagated to the server      in the ACL / POSIX cases.    2. cifs_setattr_unix(): this function is only called when Unix      extensions are in effect, so the mode is always stored on the      server.  Remove the shortcut entirely so that the cleared mode is      always pushed.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-09-11 20:19:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98375",
                                "url": "https://ubuntu.com/security/CVE-2026-98375",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  xen/netfront: drop RX packets with a short Ethernet header  handle_incoming_queue() pulls pull_to bytes into the head before calling eth_type_trans().  pull_to is the length of the first RX slot, capped at RX_COPY_THRESHOLD, and that length comes from the backend. Nothing checks it against ETH_HLEN.  If the first slot is shorter than ETH_HLEN and more slots follow, the head ends up shorter than an Ethernet header while skb->len is longer, and eth_type_trans() BUG()s in __skb_pull().  If the whole packet is shorter than ETH_HLEN, eth_type_trans() reads the header past the end of the data instead.  Pull at least ETH_HLEN, and drop the packet if that fails, which also drops packets too short to hold an Ethernet header.  This also checks the return value of the pull, which was ignored.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-09 08:16:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-89738",
                                "url": "https://ubuntu.com/security/CVE-2026-89738",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  usb: gadget: at91_udc: drain polled-VBUS timer/work before udc is freed  In polled-VBUS mode (board.vbus_pin && board.vbus_polled), probe arms a self-restarting cycle: at91_vbus_timer() schedules vbus_timer_work, and at91_vbus_timer_work() calls at91_vbus_update() and re-arms the timer via mod_timer(). Both recover the same udc through container_of and dereference it on every iteration.  Neither teardown path cancels this cycle. udc is devm-allocated, so it is freed after at91udc_remove() returns, and is likewise freed when probe fails and devres runs. A timer callback or work item that is pending or running at either point dereferences the freed udc.  Add at91_udc_shutdown_vbus_timer() and call it from at91udc_remove() and from the usb_add_gadget_udc() failure path in probe; the remaining probe error paths fail before the timer is armed. timer_shutdown_sync() waits for a running callback and clears timer->function, which makes the work handler's mod_timer() a permanent no-op; cancel_work_sync() then drains any pending or running work whose re-arm attempt now does nothing. The timer must be shut down first, since cancelling the work alone would let the timer re-queue it. The guard mirrors probe: in IRQ mode the timer and work_struct are never initialized.  This does not require a fault; a normal driver unbind can interleave with an already queued work item.  This issue was found by an in-house static analysis tool.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-09-11 20:20:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-89740",
                                "url": "https://ubuntu.com/security/CVE-2026-89740",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  serial: imx: serialize imx_uart_ports[] lifetime  imx_uart_probe() publishes its devm-allocated port in imx_uart_ports[] before uart_add_one_port() because console setup uses the table. The entry is not cleared when adding the port fails or after removal, leaving a dangling pointer.  A sibling probe can register the shared console through that stale entry. This was reproduced under KASAN on QEMU mcimx6ul-evk by unbinding a sibling UART, unbinding the console UART and rebinding the sibling.  Keep the entry valid through uart_remove_one_port(), then clear it. Protect port addition and removal together with their table updates so sibling operations cannot interleave. Reject an occupied slot rather than clobbering an active port during a duplicate-line probe.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-09-11 20:20:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-74341",
                                "url": "https://ubuntu.com/security/CVE-2026-74341",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: wcn36xx: fix heap overflow from oversized firmware HAL response  The firmware response dispatcher copies all synchronous HAL responses into the 4096-byte hal_buf without validating the response length. A response exceeding WCN36XX_HAL_BUF_SIZE causes a heap buffer overflow with firmware-controlled content.  Add a bounds check on the response length.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-08-15 06:22:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-74406",
                                "url": "https://ubuntu.com/security/CVE-2026-74406",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  vxlan: Fix potential null-ptr-deref in vxlan_gro_prepare_receive().  udp_tunnel_sock_release() could set sk->sk_user_data to NULL while vxlan_gro_prepare_receive() is running.  Let's check if rcu_dereference_sk_user_data() is NULL after skb_gro_remcsum_init().",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-08-15 06:22:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-46265",
                                "url": "https://ubuntu.com/security/CVE-2026-46265",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  RDMA/hns: Fix WQ_MEM_RECLAIM warning  When sunrpc is used, if a reset triggered, our wq may lead the following trace:  workqueue: WQ_MEM_RECLAIM xprtiod:xprt_rdma_connect_worker [rpcrdma] is flushing !WQ_MEM_RECLAIM hns_roce_irq_workq:flush_work_handle [hns_roce_hw_v2] WARNING: CPU: 0 PID: 8250 at kernel/workqueue.c:2644 check_flush_dependency+0xe0/0x144 Call trace:   check_flush_dependency+0xe0/0x144   start_flush_work.constprop.0+0x1d0/0x2f0   __flush_work.isra.0+0x40/0xb0   flush_work+0x14/0x30   hns_roce_v2_destroy_qp+0xac/0x1e0 [hns_roce_hw_v2]   ib_destroy_qp_user+0x9c/0x2b4   rdma_destroy_qp+0x34/0xb0   rpcrdma_ep_destroy+0x28/0xcc [rpcrdma]   rpcrdma_ep_put+0x74/0xb4 [rpcrdma]   rpcrdma_xprt_disconnect+0x1d8/0x260 [rpcrdma]   xprt_rdma_connect_worker+0xc0/0x120 [rpcrdma]   process_one_work+0x1cc/0x4d0   worker_thread+0x154/0x414   kthread+0x104/0x144   ret_from_fork+0x10/0x18  Since QP destruction frees memory, this wq should have the WQ_MEM_RECLAIM.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-06-03 18:16:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98681",
                                "url": "https://ubuntu.com/security/CVE-2026-98681",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  smb: client: split cifsFileInfo bitfields to avoid shared-byte RMW races  The invalidHandle, swapfile, oplock_break_cancelled, offload, and status_file_deleted fields are stored in the same bitfield byte in struct cifsFileInfo, but are updated in different code paths that may run simultaneously, and are protected by different locks.  Since bitfield assignments generate byte-level read-modify-write operations, a modification to one flag can overwrite a concurrent modification to another flag.  To avoid these races, convert these flags from a bitfield to separate bool fields.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-89539",
                                "url": "https://ubuntu.com/security/CVE-2026-89539",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  SUNRPC: reject duplicate CREDS_VALUE options  gssx_dec_option_array() walks the wire-supplied option array and, for every entry whose name matches CREDS_VALUE, calls gssx_dec_linux_creds() on the same struct svc_cred. That helper unconditionally installs a fresh groups_alloc() result into creds->cr_group_info without releasing whatever pointer was already there:      for (i = 0; i < count; i++) {         ... decode name ...         if (length == sizeof(CREDS_VALUE) &&             memcmp(p, CREDS_VALUE, sizeof(CREDS_VALUE)) == 0) {             err = gssx_dec_linux_creds(xdr, creds);             ...         }     }  A reply that carries two CREDS_VALUE entries therefore overwrites cr_group_info on the second iteration and orphans the group_info allocated by the first call. The earlier free_creds path only releases the last cr_group_info via free_svc_cred(), so the first allocation's refcount stays at one and its kvmalloc-backed storage is leaked. No in-tree caller of gssp_accept_sec_context_upcall() expects more than one CREDS_VALUE per reply.  Fix by tracking whether a CREDS_VALUE option has already been decoded and returning -EINVAL on any subsequent match, so the free_creds path releases the single group_info that was installed.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-09-11 20:19:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-93179",
                                "url": "https://ubuntu.com/security/CVE-2026-93179",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  drm/amd/powerplay: fix VoltageObjectInfo zero-stride loop and OOB read  Reject voltage objects whose usSize is smaller than the header or would advance the cursor past the table end, preventing an infinite loop or heap OOB read when the VBIOS supplies a malformed VoltageObjectInfo table.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-09-17 17:18:00 UTC"
                            },
                            {
                                "cve": "CVE-2023-52561",
                                "url": "https://ubuntu.com/security/CVE-2023-52561",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  arm64: dts: qcom: sdm845-db845c: Mark cont splash memory region as reserved  Adding a reserved memory region for the framebuffer memory (the splash memory region set up by the bootloader).  It fixes a kernel panic (arm-smmu: Unhandled context fault at this particular memory region) reported on DB845c running v5.10.y.",
                                "cve_priority": "low",
                                "cve_public_date": "2024-03-02 22:15:00 UTC"
                            },
                            {
                                "cve": "CVE-2023-53651",
                                "url": "https://ubuntu.com/security/CVE-2023-53651",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  Input: exc3000 - properly stop timer on shutdown  We need to stop the timer on driver unbind or probe failures, otherwise we get UAF/Oops.",
                                "cve_priority": "low",
                                "cve_public_date": "2025-10-07 16:15:00 UTC"
                            },
                            {
                                "cve": "CVE-2023-53733",
                                "url": "https://ubuntu.com/security/CVE-2023-53733",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net: sched: cls_u32: Undo tcf_bind_filter if u32_replace_hw_knode  When u32_replace_hw_knode fails, we need to undo the tcf_bind_filter operation done at u32_set_parms.",
                                "cve_priority": "medium",
                                "cve_public_date": "2025-10-24 12:15:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98657",
                                "url": "https://ubuntu.com/security/CVE-2026-98657",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  iio: proximity: pulsedlight: fix iio_device left registered on PM setup failure  pm_runtime_set_active() failing in probe() jumps to error_unreg_buffer, which only calls iio_triggered_buffer_cleanup() -- it does not undo the iio_device_register() that already succeeded a few lines above. probe() then returns the error, the devm-managed indio_dev is freed, but the iio core still has it registered: the sysfs/chardev nodes stay live and point at freed memory.  Add an error_unreg_dev label that unregisters the iio device before falling through to the existing buffer cleanup, mirroring the teardown order already used in lidar_remove().",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98662",
                                "url": "https://ubuntu.com/security/CVE-2026-98662",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  iio: light: gp2ap020a00f: drain irq_work after free_irq  The threaded IRQ handler queues data->work through irq_work_queue() so the trigger is polled from a per-CPU context.  free_irq() does not flush an irq_work the handler already queued, so after gp2ap020a00f_remove() returns that work may still run and call iio_trigger_poll() on data->trig, which the devm cleanup has already freed, causing a use-after-free.  Add irq_work_sync(&data->work) after free_irq() in remove() and in the probe error path, mirroring commit 78601726d4a5 (\"iio: trigger: sysfs: fix use-after-free on remove\").  Found by an in-house static analysis tool, confirmed by manual review.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98663",
                                "url": "https://ubuntu.com/security/CVE-2026-98663",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  iio: imu: adis16480: fix unprotected debugfs reads  The firmware_revision and firmware_date file operations are open coded and never call debugfs_file_get(), which debugfs_create_file_unsafe() requires. debugfs_remove_recursive() therefore does not wait for a read in progress, and unbind frees the iio_dev underneath it.  Use debugfs_create_file() instead.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98664",
                                "url": "https://ubuntu.com/security/CVE-2026-98664",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  iio: imu: adis16400: fix unprotected debugfs reads  adis16400_serial_number_fops is open coded and never calls debugfs_file_get(), so debugfs_remove_recursive() does not wait for a read in progress and unbind frees the iio_dev underneath it.  Commit ae1d37a9bb4b (\"iio: imu: adis16400: use DEFINE_DEBUGFS_ATTRIBUTE instead of DEFINE_SIMPLE_ATTRIBUTE\") converted product_id and flash_count to DEFINE_DEBUGFS_ATTRIBUTE, which protects itself, but moved all three files to debugfs_create_file_unsafe().  serial_number prints three registers as \"%.4x-%.4x-%.4x\" and DEFINE_DEBUGFS_ATTRIBUTE() formats a single u64, so it cannot be converted without changing what the file returns. adis16475 and adis16550 already use debugfs_create_file() for their open coded files. Use it here too.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98666",
                                "url": "https://ubuntu.com/security/CVE-2026-98666",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  iio: gyro: adis16136: fix unprotected debugfs reads  The serial_number file operations are open coded and never call debugfs_file_get(), which debugfs_create_file_unsafe() requires. debugfs_remove_recursive() therefore does not wait for a read in progress, and unbind frees the iio_dev underneath it.  Use debugfs_create_file() instead.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98671",
                                "url": "https://ubuntu.com/security/CVE-2026-98671",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  iio: adc: sun4i-gpadc-iio: clean up on thermal zone registration failure  If devm_thermal_of_zone_register() fails, probe returns without unregistering the IIO map array or disabling runtime PM.  Jump to err_map to release them.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98679",
                                "url": "https://ubuntu.com/security/CVE-2026-98679",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  iio: accel: kxcjk-1013: reject duplicate event disable  The IIO core does not filter duplicate writes to the event enable attribute. kxcjk1013_write_event_config() already ignores repeated enable requests, but a repeated disable request still calls kxcjk1013_set_power_state(data, false), dropping a runtime PM reference that was not acquired for this request. This can underflow the runtime PM usage count and trigger a \"Runtime PM usage count underflow\" warning.  Return early when the requested state already matches ev_enable_state.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98687",
                                "url": "https://ubuntu.com/security/CVE-2026-98687",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  thunderbolt: Reject oversized XDomain properties responses  tb_xdp_properties_request() allocates room for 45 data dwords in its 252-byte response buffer.  The XDomain length field is six bits wide, however, and a malicious peer can set it to 63.  After the fixed response fields are subtracted, the driver treats this as 48 data dwords.  Commit 322e93448d90 (\"thunderbolt: Clamp XDomain response data copy to allocation size\") only bounds the copy against data_len.  If data_len is at least 48, memcpy() reads 192 bytes from the 180-byte res->data array, causing a 12-byte heap out-of-bounds read.  Commit 4db2bd2ed478 (\"thunderbolt: Limit XDomain response copy to actual frame size\") limits the earlier copy but does not constrain this header-derived length.  Reject response data lengths that exceed the allocated source buffer before copying them into the assembled property block.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98697",
                                "url": "https://ubuntu.com/security/CVE-2026-98697",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  USB: serial: fix dynamic id driver deregistration race  Only free the dynamic ids after having deregistered the driver and removed the \"new_id\" attribute to avoid leaking any id added by a racing write to the attribute.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98698",
                                "url": "https://ubuntu.com/security/CVE-2026-98698",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: mac80211: handle empty FILS association request payload  fils_encrypt_assoc_req() accepts a (Re)Association Request frame whose last element is the FILS Session element.  crypt_len is then zero and aes_siv_encrypt() is called with an empty plaintext.  kmemdup() returns ZERO_SIZE_PTR for a zero-length allocation, so the unconditional sg_init_one() puts an invalid page into the scatterlist. With CONFIG_DEBUG_SG this triggers a kernel BUG in sg_set_buf(); without the debug check the bogus page is handed to the crypto backend.  AES-SIV is defined for empty plaintext and the S2V result is then the complete output, so handle this case before the CTR step, which has nothing to encrypt.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98701",
                                "url": "https://ubuntu.com/security/CVE-2026-98701",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: mac80211: release mesh path quota on failed additions  Repeated failed or duplicate mesh path additions can exhaust MESH_MAX_MPATHS while the path table holds fewer paths, which stops new paths to reachable destinations from being created.  mesh_path_add() reserves a slot before allocating and inserting a path. If allocation fails, the function returns without releasing the slot. If the rhashtable insertion reports an error or an existing destination, the function discards its candidate but retains the reservation. No new path is installed in any of these cases.  Release the reservation whenever the candidate is not installed.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98703",
                                "url": "https://ubuntu.com/security/CVE-2026-98703",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: mac80211: minstrel_ht: validate fixed rate index  The fixed_rate_idx debugfs file is a plain u32 attribute, so any value can be written to it.  minstrel_ht_update_stats() then copies the value into mi->max_tp_rate[] and mi->max_prob_rate, and minstrel_ht_set_rate() uses MI_RATE_GROUP()/MI_RATE_IDX() to index minstrel_mcs_groups[] (42 entries) and mi->groups[].rates[] (10 entries) with it.  Writing e.g. 65535 selects group 4095 and rate index 15, far outside both arrays.  The out-of-bounds entries are dereferenced and updated as struct minstrel_rate_stats (retry counts, etc.), so the invalid index corrupts adjacent kernel memory.  With CONFIG_UBSAN_BOUNDS the access is reported as an array-index-out-of-bounds in minstrel_ht_set_rate().  Only a valid group/rate pair, or U32_MAX to disable fixed rate processing, can be used safely, so reject any other value when the debugfs file is written.  The file is only reachable through a root-only debugfs mount, so this is not a privilege boundary.  The out-of-bounds access is still a bug that must not be reachable through a writable debugfs attribute.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98706",
                                "url": "https://ubuntu.com/security/CVE-2026-98706",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: mac80211: drain PS delivery work during station teardown  Removing an AP or mesh station can notify the driver and wake TXQs after the station has already been removed from the driver, and can update num_sta_ps and the power-save queues after station cleanup has purged them.  sta_deliver_ps_frames() tests sta->dead only before it starts delivery. A worker that passes that test can be delayed while teardown sets sta->dead and removes the station from the driver; when it resumes it still runs the full delivery.  The existing cancel_work_sync() sits near the end of __cleanup_single_sta(), after the final driver state transition and after PS accounting and queue purging, so it drains the worker only once the state it has to protect has already changed. Before commit d34ba2168a3c (\"mac80211: don't delay station destruction\") cleanup was deferred through the same ordered workqueue as the delivery work, which kept the two ordered.  Cancel the work after setting sta->dead and before moving the driver state, and move the existing cancellation to the start of __cleanup_single_sta(). The first drain closes the driver-lifetime window; driver callbacks during the remaining state transitions can still queue drv_deliver_wk through ieee80211_sta_block_awake(), so retain the second drain at the start of __cleanup_single_sta(). That drain also covers insertion failures, which reach cleanup without setting sta->dead.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98710",
                                "url": "https://ubuntu.com/security/CVE-2026-98710",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: iwlegacy: 3945: free EEPROM data on remove  il3945_pci_probe() calls il_eeprom_init(), which allocates memory for the EEPROM data. The probe failure paths release this allocation with il_eeprom_free(), but the remove path does not free it after a successful probe.  As a result, the EEPROM data is leaked when the PCI device is removed.  Free the EEPROM data in il3945_pci_remove() before releasing the mac80211 hardware structure.  This issue was found by manual code inspection.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98711",
                                "url": "https://ubuntu.com/security/CVE-2026-98711",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: cw1200: fix TX padding OOB read leaking heap data to device  The TX path rounds the transfer size up to the bus alignment (align_size(), up to 511 bytes for SDIO, 1 byte for SPI) but sends the padded length straight from the frame buffer, which has no room reserved for the padding.  cw1200_data_write() therefore reads past the end of the frame and the bus transfer carries those bytes to the device.  A bogus device can collect up to 511 bytes of kernel heap data per TX frame.  The RX path does not have this problem: it allocates the skb with the aligned length (alloc_len) before reading.  Compute the exact padding with the bus align_size() callback, make sure queued TX frames have tailroom for it, and zero the padding bytes before the transfer so nothing past the frame is exposed.  This is not expected to change driver behavior on most cases: frame contents and transfer sizes are unchanged, only the content of the padding bytes (previously undefined stale memory, now zero), which the device never reads since the WSM header carries the real frame length.  The skb expansion can only fail under memory exhaustion, in which case the frame is dropped like on the existing error paths of cw1200_tx().  Discovered by Atuin - Automated Vulnerability Discovery Engine.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98721",
                                "url": "https://ubuntu.com/security/CVE-2026-98721",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  mtd: rawnand: cadence: Initialize IRQ state before requesting IRQ  The Cadence NAND interrupt handler uses both the IRQ lock and completion object. Registering the IRQ before initializing them leaves a window in which a pending interrupt can access uninitialized synchronization state.  Initialize them before registering the handler.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98726",
                                "url": "https://ubuntu.com/security/CVE-2026-98726",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  nvme-multipath: fix underflow in ANA log bounds checks  The number of ANA groups advertised through Identify Controller sizes the ANA log buffer. The ANA log header and group descriptors independently supply the number of groups and namespace IDs to parse.  Both bounds checks subtract an untrusted object size from ana_log_size before comparing the current offset. If the object is larger than the buffer, the size_t subtraction underflows and lets the parser read beyond ana_log_buf.  Check the current offset before the first subtraction and compare each object size with the remaining buffer instead. This rejects inconsistent ANA data before dereferencing a truncated group descriptor or walking an oversized namespace ID array.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98856",
                                "url": "https://ubuntu.com/security/CVE-2026-98856",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  kprobes: Skip disarmed probes when checking optkprobe overlap  On x86, an optkprobe at A replaces five bytes with a jump. If a disabled probe B is at A+2, get_optimized_kprobe() stops at B when arming a new probe C at A+4. It leaves A optimized:                A    A+1  A+2  A+3  A+4   A's jump  | e9 | d0 | d1 | d2 | d3 |   after C   | e9 | d0 | d1 | d2 | cc |  The INT3 for C overwrites the last byte of A's jump displacement, so execution can jump to the wrong address. B can have prepared optinsns while disarmed, but has no jump to unoptimize.  Continue past disarmed and unprepared probes to find the active optimized probe before arming a probe in its jump.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98857",
                                "url": "https://ubuntu.com/security/CVE-2026-98857",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ipvs: bound LBLCR and LBLC cache growth  ip_vs_lblcr_new() and ip_vs_lblc_new() create cache entries for every previously unseen destination address. The table max_size only tells the periodic collector to reclaim entries after the cache has already exceeded the limit. It does not reclaim entries that the attacker continues to use.  Reject new cache entries once either table reaches max_size * 3 / 2. The extra headroom lets the periodic collector catch up while the existing scheduler fallback continues to use the selected destination when cache creation fails. New traffic therefore stays serviceable without growing the tables further.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98732",
                                "url": "https://ubuntu.com/security/CVE-2026-98732",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  Bluetooth: btintel: fix buffer over-read in btintel_hw_error()  The \"Exception info %s\" print uses skb->data + 1, but the 12-byte payload is not guaranteed to be NUL-terminated and can be read past its end.  Bound the print with \"%.*s\" and skb->len - 1.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98735",
                                "url": "https://ubuntu.com/security/CVE-2026-98735",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  Bluetooth: hci_core: Serialize ACL scheduling with channel deletion  hci_chan_sent() selects a channel under RCU but drops the read lock before accessing chan->conn and returning the channel. The ACL and LE schedulers then use its packet queue and update its transmit counters without any protection against channel deletion.  After TX selects a channel and releases RCU, a disconnect command timeout on the separate request workqueue can run hci_conn_failed() and l2cap_conn_del(). hci_chan_del() can then unlink the channel, complete synchronize_rcu(), purge its queue and free it before TX resumes. This causes use-after-free both in hci_chan_sent() and in its callers.  KASAN reported:    BUG: KASAN: slab-use-after-free in hci_chan_sent+0x892/0x9b0   Workqueue: hci0 hci_tx_work   Call Trace:    hci_chan_sent+0x892/0x9b0    hci_tx_work+0x5e6/0xb70   Allocated by task 91:    hci_chan_create+0xe3/0x350    l2cap_conn_add.part.0+0x12/0xa30    l2cap_chan_connect+0x110d/0x1b60    l2cap_sock_connect+0x310/0x530   Freed by task 99:    hci_chan_del+0x11f/0x170    l2cap_conn_del+0x4f1/0x800    l2cap_connect_cfm+0x88c/0xd30    hci_conn_failed+0x150/0x250    hci_abort_conn_sync+0x3e3/0x800    hci_cmd_sync_run+0x7e/0xc0    hci_abort_conn+0x105/0x1f0    disconnect_sync+0x157/0x290    hci_cmd_sync_work+0x13c/0x290  Hold the existing device mutex across channel selection and transmission in both schedulers to serialize them with channel teardown. Keep timeout handling outside the critical sections because hci_link_tx_to() acquires the same mutex. This also permits the transmit path to sleep, unlike extending the RCU read-side critical section across packet submission.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98739",
                                "url": "https://ubuntu.com/security/CVE-2026-98739",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  Bluetooth: RFCOMM: Fix initial port reference race  For RFCOMM_RELEASE_ONHUP devices, rfcomm_tty_install() and __rfcomm_release_dev() both use RFCOMM_TTY_OWNED to decide who drops the initial tty_port reference. The release path tests the bit separately from the install path setting it, so both can drop that reference.  The synchronous hangup does not prevent this race: port->tty is not assigned until tty_port_open(), after installation. The following interleaving is possible:    1. Install and release each obtain a reference with rfcomm_dev_get().   2. Release observes RFCOMM_TTY_OWNED clear.   3. Install sets RFCOMM_TTY_OWNED and drops the initial reference.   4. Release drops the same initial reference again.   5. TTY cleanup drops its reference and frees the device.   6. Release performs its final tty_port_put() on the freed port.  KASAN reported:    BUG: KASAN: slab-use-after-free in tty_port_put+0x22/0x190   Write of size 4 at addr ffff8881001d3d5c by task poc/92    Call Trace:    tty_port_put+0x22/0x190    rfcomm_dev_ioctl+0x1d4/0x1930    sock_do_ioctl+0x110/0x260    sock_ioctl+0x380/0x590    __x64_sys_ioctl+0x134/0x1c0    Allocated by task 88:    rfcomm_dev_ioctl+0x8f6/0x1930    sock_do_ioctl+0x110/0x260    sock_ioctl+0x380/0x590    __x64_sys_ioctl+0x134/0x1c0    Freed by task 65:    kfree+0x131/0x3c0    rfcomm_dev_destruct+0x23b/0x2f0    release_one_tty+0xc1/0x370    process_one_work+0x661/0x1090  Use test_and_set_bit() in both paths so that only the caller that changes RFCOMM_TTY_OWNED from clear to set drops the initial reference. Each path keeps its own lookup reference until release or TTY cleanup, preserving the existing callback ordering and error handling.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98741",
                                "url": "https://ubuntu.com/security/CVE-2026-98741",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ALSA: ua101: reject mismatched capture/playback packet sizes  detect_usb_format() cross-checks bSubframeSize, bBitResolution and tSamFreq between the capture and playback interfaces, but never relates the two endpoints' wMaxPacketSize and bNrChannels.  Each playback URB gets a buffer of ua->playback.max_packet_bytes, while the number of bytes written into it is derived from the capture stream: capture_urb_complete() computes frames from the received capture packet and capture.frame_bytes, and start_usb_playback() and playback_work() multiply that by playback.frame_bytes.  A device declaring a large capture wMaxPacketSize with few capture channels and a small playback wMaxPacketSize with many playback channels therefore memset()s and memcpy()s past the end of the playback buffer, in open() of the PCM node the driver registers during probe. usb_submit_urb() rejects the over-long iso_frame_desc[0].length with -EMSGSIZE, but only after the write.  Reject such descriptors at probe time.  Genuine UA-101/UA-1000 hardware declares proportional packet sizes and is unaffected.    BUG: KASAN: slab-out-of-bounds in start_usb_playback (sound/usb/misc/ua101.c:586)   Write of size 2048 at addr ffff8881098f3c00 by task exploit/5021   Call Trace:    __asan_memset (mm/kasan/shadow.c:84)    start_usb_playback (sound/usb/misc/ua101.c:586)    playback_pcm_open (sound/usb/misc/ua101.c:679)    snd_pcm_open_substream (sound/core/pcm_native.c:2829)    snd_pcm_open (sound/core/pcm_native.c:2865 sound/core/pcm_native.c:2932)    snd_pcm_playback_open (sound/core/pcm_native.c:2891)    snd_open (sound/core/sound.c:166)    chrdev_open (fs/char_dev.c:411)    do_dentry_open (fs/open.c:996)    vfs_open (fs/open.c:1101)    path_openat (fs/namei.c:4837 fs/namei.c:5000)    do_file_open (fs/namei.c:5029)    do_sys_openat2 (fs/open.c:1417)    __x64_sys_openat (fs/open.c:1423 fs/open.c:1439 fs/open.c:1434)    do_syscall_64 (arch/x86/entry/syscall_64.c:61 arch/x86/entry/syscall_64.c:84)    entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:121)    The buggy address belongs to the object at ffff8881098f3c00    which belongs to the cache kmalloc-192 of size 192   The buggy address is located 0 bytes inside of    allocated 168-byte region [ffff8881098f3c00, ffff8881098f3ca8)",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98940",
                                "url": "https://ubuntu.com/security/CVE-2026-98940",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ASoC: qcom: lpass-cpu: use DAI table index for playback constraints  The DAI ID is a hardware port ID and is not necessarily the index of the corresponding entry in variant->dai_driver.  When configuring a DAI with LPAIF_I2SCTL_MODE_QUAD01, the probe code currently uses dai_id to index variant->dai_driver. This is incorrect for platforms where DAI IDs are sparse. For example, the IPQ806x MI2S DAI has ID 4 while it is the only entry in the DAI driver table. If that DAI is configured for QUAD01 and probe reaches this branch, the code writes beyond that single entry via dai_driver[4] instead of updating the DAI being processed.  Use the loop index i when updating the current DAI's playback channel constraints, while retaining dai_id for indexing the hardware-port specific playback SD-line mode array.  This fixes the incorrect DAI table access for platforms where the DAI ID does not match its position in the driver table.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98748",
                                "url": "https://ubuntu.com/security/CVE-2026-98748",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  serial: 8250_bcm7271: fix use-after-free in brcmuart_remove()  brcmuart_handle_irq() starts priv->hrt to work around a receive-timeout quirk of the 8250 core when hardware flow control is enabled; the timer callback brcmuart_hrtimer_func() dereferences priv.  brcmuart_remove() cancels the hrtimer before it unregisters the port, so a receive-timeout interrupt that arrives in between re-arms the timer. After devm frees priv, the callback runs on freed memory.  Unregister the port before cancelling the hrtimer. serial8250_unregister_port() shuts the port down and frees its IRQ, so brcmuart_handle_irq() can no longer restart the timer, and the final hrtimer_cancel() drains any timer that was armed before or during the unregister.  This issue was found by an in-house static analysis tool.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98754",
                                "url": "https://ubuntu.com/security/CVE-2026-98754",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  tty: vcc: hold port lock when clearing tty pointer in vcc_cleanup  vcc_cleanup() sets port->tty to NULL without holding port->lock, racing with vcc_event() LDC callbacks that read port->tty under port->lock and then use tty->port. This can cause a use-after-free when the callback dereferences tty->port after cleanup has already destroyed and freed it.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98755",
                                "url": "https://ubuntu.com/security/CVE-2026-98755",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  tty: vcc: zero-initialize control packet in vcc_send_ctl()  The stack-allocated struct vio_vcc pkt was partially initialized, leaving the tag.stype_env field uninitialized before being sent via ldc_write(), potentially leaking kernel stack data to the LDC peer.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98756",
                                "url": "https://ubuntu.com/security/CVE-2026-98756",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  usb: cdns3: Fix NULL pointer dereference in cdns3_pci_probe  The Cadence USBSS controller is a two-function PCI device. The first probed function allocates the driver data and stores it with pci_set_drvdata(), while the second function reuses it via pci_get_drvdata() when pci_is_enabled() reports that the first function has already been probed.  When the second function is probed while the first one has been enabled but has not yet set its driver data, pci_get_drvdata() returns NULL, and the subsequent wrap->devfn assignment dereferences a NULL pointer and crashes the kernel. logs: Call trace:   cdns3_pci_probe+0xa4/0x300   local_pci_probe+0x44/0xa8   pci_call_probe+0x54/0x158   pci_device_probe+0x84/0x100   really_probe+0x184/0x3d0   __driver_probe_device+0x80/0x178   driver_probe_device+0x44/0xe8   __driver_attach+0xec/0x1f8   bus_for_each_dev+0x7c/0xe0   driver_attach+0x28/0x38   bus_add_driver+0x110/0x238   driver_register+0x64/0x128   __pci_register_driver+0x50/0x60   cdns3_pci_driver_init+0x28/0x38   do_one_initcall+0x5c/0x280   do_initcalls+0x104/0x1d8   kernel_init_freeable+0x140/0x218   kernel_init+0x28/0x1f8   ret_from_fork+0x10/0x20  Return -EPROBE_DEFER in this case so that probing is retried after the first function has completed its probe.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98757",
                                "url": "https://ubuntu.com/security/CVE-2026-98757",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  usb: cdns3: fix use-after-free in cdns3_gadget_exit()  cdns3_gadget_start() arms two works on system_freezable_wq: pending_status_wq for the deferred ep0 status stage and aligned_buf_wq for realigned request buffers. Both handlers use the cdns3_device the works are embedded in, and cdns3_pending_setup_status_handler() also calls the ep0 request completion.  cdns3_gadget_exit() does not wait for these works. It frees all endpoints and aligned buffers and drops the last reference to the gadget device, which frees priv_dev, so a work queued before the exit can run after the free.  Fix this by waiting for both works after the gadget driver is unbound and the IRQ is freed, when no new work can be queued, and before the endpoints and buffers are released.  This issue was found by an in-house static analysis tool.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98760",
                                "url": "https://ubuntu.com/security/CVE-2026-98760",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  usb: typec: tipd: fix uninitialized typec_partner_desc in tps6598x_connect()  tps6598x_connect() passes a stack-allocated typec_partner_desc to typec_register_partner() after initializing only usb_pd, accessory and identity.  typec_register_partner() copies attach and deattach from the descriptor into the partner. With those fields left unset, garbage function pointers may be stored and later invoked from typec_partner_link_device() when a USB device is linked to the port. Uninitialized pd_revision and usb_capability similarly leak stack data through partner sysfs.  Zero-initialize the descriptor so optional callbacks remain NULL and the remaining fields are zero.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98761",
                                "url": "https://ubuntu.com/security/CVE-2026-98761",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  usb: typec: tcpm: recover after failure to start the frs ams  Reset the port if the tcpm fails to start the FAST_ROLE_SWAP AMS by initiating error recovery on it.  This helps in cases where some cables (incorrectly) signal an FRS to an FRS capable port during disconnection. The TCPC autonomously starts sourcing VBUS on detecting the FRS signal. However, the VBUS sourcing is left on when the FAST_ROLE_SWAP AMS fails to start (as tcpm_sink_tx_ok is 0 as CC is open due to the cable disconnect). This is because the code sets the state to INVALID_STATE without resetting the port state.  Log snippet before changes: [  101.401960] AMS FAST_ROLE_SWAP start [  101.401971] Sink TX No Go [  101.401982] sourcing vbus [  101.401987] VBUS on [  101.402159] VBUS on [  109.257809] CC1: 0 -> 0, CC2: 5 -> 0 [state SNK_READY, polarity 1, disconnected] [  111.267442] VBUS on  After changes: [   70.541211] AMS FAST_ROLE_SWAP start [   70.541220] Sink TX No Go [   70.541228] state change SNK_READY -> ERROR_RECOVERY [rev3 NONE_AMS] [   70.541362] VBUS on [   70.541365] sourcing vbus [   70.541367] VBUS on [   70.541374] state change ERROR_RECOVERY -> PORT_RESET [rev3 NONE_AMS] [   70.541410] disable vbus discharge ret:0 [   70.543028] Setting usb_comm capable false [   70.544009] Setting voltage/current limit 0 mV 0 mA [   70.544034] polarity 0 [   70.544239] Requesting mux state 0, usb-role 0, orientation 0 [   70.555550] cc:=0 [   70.555595] pending state change PORT_RESET -> PORT_RESET_WAIT_OFF @ 100 ms [rev3 NONE_AMS] [   70.555697] VBUS off [   70.555702] VBUS VSAFE0V [   70.555762] CC1: 5 -> 0, CC2: 0 -> 0 [state PORT_RESET, polarity 0, disconnected] [   70.587794] VBUS off [   70.587799] VBUS VSAFE0V [   70.655672] state change PORT_RESET -> PORT_RESET_WAIT_OFF [delayed 100 ms] [   70.655682] state change PORT_RESET_WAIT_OFF -> SNK_UNATTACHED [rev3 NONE_AMS] [   70.655686] Start toggling [   70.656274] CC1: 0 -> 0, CC2: 0 -> 0 [state TOGGLING, polarity 0, disconnected]",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98763",
                                "url": "https://ubuntu.com/security/CVE-2026-98763",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  usb: core: clear both ep_in and ep_out for non-ep0 control endpoints  In usb_enable_endpoint(), non-zero control endpoints (where usb_endpoint_xfer_control(&ep->desc) is true) populate both dev->ep_in[epnum] and dev->ep_out[epnum] with the same struct usb_host_endpoint pointer.  However, usb_disable_endpoint() only clears either dev->ep_out[epnum] or dev->ep_in[epnum] depending on the direction bit of epaddr when reset_hardware is set, leaving the opposite direction's array slot pointing to the disabled/freed endpoint.  Clear both dev->ep_out[epnum] and dev->ep_in[epnum] when disabling a non-ep0 control endpoint with reset_hardware set, and update the function kerneldoc accordingly.  Tested in QEMU against Linux 7.3.0-rc3 using dummy_hcd and raw-gadget to enumerate a USB device with a non-zero control endpoint (bEndpointAddress 0x01, bmAttributes USB_ENDPOINT_XFER_CONTROL), verifying that both dev->ep_in[1] and dev->ep_out[1] are cleared when the interface is disabled.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98764",
                                "url": "https://ubuntu.com/security/CVE-2026-98764",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  usb: gadget: f_fs: Fix NULL pointer dereference in FUNCTIONFS_ENDPOINT_DESC  When user space sets up FunctionFS with only full-speed descriptors (e.g., flags = FUNCTIONFS_HAS_FS_DESC) and the gadget operates at a higher speed (such as USB_SPEED_HIGH or USB_SPEED_SUPER), config_ep_by_speed() detects that the function lacks descriptors for the current speed, logs a warning, and falls back to full-speed descriptors. The endpoint is then successfully enabled via usb_ep_enable(), and epfile->ep becomes valid.  However, when user space subsequently issues the FUNCTIONFS_ENDPOINT_DESC ioctl to query the endpoint descriptor, ffs_epfile_ioctl() selects the descriptor index solely based on gadget->speed:  \tswitch (epfile->ffs->gadget->speed) { \tcase USB_SPEED_SUPER: \tcase USB_SPEED_SUPER_PLUS: \t\tdesc_idx = 2; \t\tbreak; \tcase USB_SPEED_HIGH: \t\tdesc_idx = 1; \t\tbreak; \tdefault: \t\tdesc_idx = 0; \t} \tdesc = epfile->ep->descs[desc_idx]; \tmemcpy(&desc1, desc, desc->bLength);  Because user space only supplied full-speed descriptors, epfile->ep->descs[1] is NULL. Dereferencing desc->bLength triggers an immediate kernel NULL pointer dereference panic.  Fix this by falling back through lower speed descriptors if the current speed descriptor was not supplied, matching the fallback logic in config_ep_by_speed() and historical f_fs behavior. If still missing, fall back to epfile->ep->ep->desc (the active descriptor), and return -EINVAL safely if no valid descriptor is found. In addition, mark desc as const to match struct usb_ep::desc and avoid discarding qualifiers.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98765",
                                "url": "https://ubuntu.com/security/CVE-2026-98765",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  USB: gadget: dummy-hcd: Fix wait for outstanding request completions  The dummy-hcd driver emulates synchronize_irq() by waiting until its private callback_usage counter drops to 0 (with the private lock not held).  This counter is incremented whenever a gadget driver callback occurs (which requires the private lock to be dropped), but not when a request completion handler is called.  This is an oversight.  Request completion is triggered by timer interrupts (emulating device IRQs in a real UDC), and the interrupt handlers are supposed to have completed when the synchronize_irq() emulation routine returns -- they aren't supposed to be in the middle of a completion callback.  If this happens it can lead to a gadget driver's unbind routine running before all outstanding request completions have finished, maybe even allowing the gadget driver's module to be unloaded while a completion handler is still running.  Fix the oversight by incrementing the callback_usage value across request completion callbacks.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98766",
                                "url": "https://ubuntu.com/security/CVE-2026-98766",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  usb: gadget: aspeed-vhub: cancel wake work on device removal  wake_work is armed from the gadget .wakeup callback to resume suspended downstream ports, and it is never cancelled in ast_vhub_remove(), so a work item queued before or during removal can run after devm has freed vhub and its ports, a use-after-free.  Cancelling the work alone is not sufficient: usb_gadget_wakeup() takes no lock and the unbind path never clears wakeup_en, so a remote-wakeup request in flight on another CPU can re-arm the work after the cancel and before vhub is freed.  ast_vhub_del_dev() already clears d->registered under vhub->lock before unregistering the gadget. Refuse the wakeup in ast_vhub_udc_wakeup() once d->registered is clear: the check and the schedule_work() are then atomic against the unbind, so a wakeup that passed before the flag was cleared is drained by the cancel_work_sync() after the del_dev loop, and one that arrives later returns without arming. Also move INIT_WORK() to the top of ast_vhub_probe(), since the probe error path reuses ast_vhub_remove() and would otherwise cancel a never-initialized work item.  This issue was found by an in-house static analysis tool.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98769",
                                "url": "https://ubuntu.com/security/CVE-2026-98769",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  usb: gadget: f_uac1_legacy: validate bRequest index in generic_{set,get}_cmd  generic_set_cmd() and generic_get_cmd() use the low nibble of ctrl->bRequest as an index into con->data[]:      u8 cmd = (ctrl->bRequest & 0x0F);  /* 0 .. 15 */     ...     con->data[cmd] = value;            /* OOB when cmd >= 5 */  struct usb_audio_control (include/linux/usb/audio.h) declares data as a 5-element array, so indices 5 through 15 write (or read) up to 44 bytes past the end of the array on the heap.  A malicious USB host can craft a class-specific SET_CUR / GET_CUR request with an arbitrary bRequest value, triggering the out-of-bounds access from an IRQ completion handler with no further preconditions.  Add an ARRAY_SIZE() guard to both functions.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98771",
                                "url": "https://ubuntu.com/security/CVE-2026-98771",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  usb: storage: sierra_ms: reject short SWoC info transfers  sierra_get_swoc_info() requests sizeof(struct swoc_info) (60) bytes from the device via usb_control_msg(), but its callers only treat a negative return value as failure. A device that answers the vendor-specific GetSwocInfo request with a short IN transfer is therefore accepted, leaving the tail of the freshly allocated (kmalloc(), non-zeroing) swoc_info buffer uninitialized.  truinst_show() subsequently prints swocInfo->rev, swocInfo->LinuxSKU and swocInfo->LinuxVer from that buffer into the world-readable (0444) \"truinst\" sysfs attribute. An emulated/malicious USB device (VID 0x1199, PID 0x0fff) can exploit this to disclose up to 5 bytes of stale kernel heap memory (kmalloc-64) to unprivileged userspace, once per sysfs read, indefinitely. On kernels built without init_on_alloc this leaks recently freed heap contents.  Only accept the transfer when the full structure was received. sierra_ms_init() already retries failed queries, so well-behaved devices are unaffected.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98772",
                                "url": "https://ubuntu.com/security/CVE-2026-98772",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  USB: serial: fix port tear down use-after-free  Some drivers for multiport devices access port driver data from completion handlers of shared URBs submitted at attach() or first open() and stopped at disconnect() or last close(), respectively.  A simple NULL check before accessing the driver data makes sure that a port state container has at least been allocated, but a completion handler can still race with port tear down.  Reorder the disconnect handling so that ports are not deregistered (and their driver data freed) until after all ports have been hung up and the driver disconnect() callback has run so that all I/O has been stopped.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98775",
                                "url": "https://ubuntu.com/security/CVE-2026-98775",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  nitro_enclaves: fix use-after-free on SLOT_ALLOC failure  When ne_create_vm_ioctl() fails the SLOT_ALLOC request after anon_inode_getfile() has succeeded, the error path calls fput(enclave_file) and then frees ne_enclave.  In normal userspace context, fput() defers the final __fput() via task_work. ne_enclave_release() therefore runs after ne_enclave has already been freed and dereferences ne_enclave->slot_uid, causing a use-after-free: KASAN: slab-use-after-free in ne_enclave_release.  The enclave has no slot allocated and is not yet linked into the enclaves list on this error path, so ne_enclave_release() is expected to return early when slot_uid is zero. However, reading slot_uid already accesses the freed object.  Clear enclave_file->private_data before fput() on the error path. ne_enclave_release() then returns immediately when private_data is NULL, leaving the ioctl error path as the sole owner of ne_enclave. This is safe because the file has not been fd_install()'d yet.  Tested on an AWS EC2 m5.2xlarge with CONFIG_KASAN=y. Without the patch, the reproducer triggers a KASAN slab-use-after-free on every SLOT_ALLOC failure. With the patch, no KASAN report is produced and the SLOT_ALLOC error is still returned. Normal enclave creation and teardown are unaffected.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98790",
                                "url": "https://ubuntu.com/security/CVE-2026-98790",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  perf: Fix race between perf_event_exit_task() and perf_pending_task()  A race condition exists between perf_event_exit_task() and perf_pending_task() during begin_new_exec().  During begin_new_exec(), perf_event_exit_task() may be called, and the PF_EXITING flag is not set on task. So perf_sigtrap() continues to execute and triggers WARN_ON_ONCE(event->ctx->task != current).  Since both task exit and exec paths can call perf_event_exit_task() which sets ctx->task to TASK_TOMBSTONE, fix this by explicitly checking if event->ctx->task equals TASK_TOMBSTONE and dropping the redundant PF_EXITING check.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98934",
                                "url": "https://ubuntu.com/security/CVE-2026-98934",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ipv6: sr: use skb_get_hash_net() in seg6_make_flowlabel()  Since commit d58e468b1112 (\"flow_dissector: implements flow dissector BPF hook\") __skb_flow_dissect() needs a net pointer, either from skb->dev, skb->sk, or since commit 3cbf4ffba5ee (\"net: plumb network namespace into __skb_flow_dissect\") a caller provided pointer.  syzbot was able to reach seg6_make_flowlabel() with an skb having neither skb->dev nor skb->sk set: a TIPC UDP bearer sends a discovery message through an IPv4 route using seg6 encap, while net.ipv6.seg6_flowlabel is set to 1.  seg6_make_flowlabel() already has a net pointer, use skb_get_hash_net().  WARNING: net/core/flow_dissector.c:1131 at __skb_flow_dissect+0x910/0x5368 net/core/flow_dissector.c:1126, CPU#0: syz.0.17/4930 Call trace:   __skb_flow_dissect+0x910/0x5368 net/core/flow_dissector.c:1126 (P)   __skb_get_hash_net+0xe0/0x29c net/core/flow_dissector.c:1903   skb_get_hash include/linux/skbuff.h:1663 [inline]   seg6_make_flowlabel+0xcc/0x1ec net/ipv6/seg6_iptunnel.c:132   __seg6_do_srh_encap+0x320/0xbf4 net/ipv6/seg6_iptunnel.c:161   seg6_do_srh+0x4b4/0xa44 net/ipv6/seg6_iptunnel.c:431   seg6_output_core+0x164/0x688 net/ipv6/seg6_iptunnel.c:681   seg6_output+0x44/0x1ac net/ipv6/seg6_iptunnel.c:744   lwtunnel_output+0x3d0/0x664 net/core/lwtunnel.c:356   dst_output include/net/dst.h:470 [inline]   ip_local_out+0x110/0x148 net/ipv4/ip_output.c:131   iptunnel_xmit+0x50c/0xd38 net/ipv4/ip_tunnel_core.c:97   udp_tunnel_xmit_skb+0x220/0x348 net/ipv4/udp_tunnel_core.c:187   tipc_udp_xmit+0x75c/0x9c0 net/tipc/udp_media.c:202   tipc_udp_send_msg+0x214/0x374 net/tipc/udp_media.c:274   tipc_bearer_xmit_skb+0x260/0x3b0 net/tipc/bearer.c:576   tipc_enable_bearer net/tipc/bearer.c:366 [inline]   __tipc_nl_bearer_enable+0xc90/0xfb0 net/tipc/bearer.c:1048   tipc_nl_bearer_enable+0x2c/0x48 net/tipc/bearer.c:1057   genl_family_rcv_msg_doit+0x1e4/0x2d4 net/netlink/genetlink.c:1114",
                                "cve_priority": "negligible",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2022-49622",
                                "url": "https://ubuntu.com/security/CVE-2022-49622",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  netfilter: nf_tables: avoid skb access on nf_stolen  When verdict is NF_STOLEN, the skb might have been freed.  When tracing is enabled, this can result in a use-after-free: 1. access to skb->nf_trace 2. access to skb->mark 3. computation of trace id 4. dump of packet payload  To avoid 1, keep a cached copy of skb->nf_trace in the trace state struct. Refresh this copy whenever verdict is != STOLEN.  Avoid 2 by skipping skb->mark access if verdict is STOLEN.  3 is avoided by precomputing the trace id.  Only dump the packet when verdict is not \"STOLEN\".",
                                "cve_priority": "medium",
                                "cve_public_date": "2025-02-26 07:01:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98794",
                                "url": "https://ubuntu.com/security/CVE-2026-98794",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ipvs: filter some flags received in the backup server  While the IPVS SYNC protocol is not secure by design we can still protect the backup server from messages that can wreak havoc.  This commit addresses problems from received connection flags or their combinations. We now drop messages as follows:  1. the NO_CPORT+TEMPLATE combination allows lookups for normal connections to hit template which can break in many ways. While the master does not sync connections with NO_CPORT flag, i.e. before they are established, we still accept NO_CPORT without TEMPLATE.  2. ONE_PACKET: it is not sent by master, so we do not expect it in backup. Before now it was ignored by IP_VS_CONN_F_BACKUP_MASK for protocol v1 while protocol v0 created connections that are not hashed and dropped immediately. Better to apply the IP_VS_CONN_F_BACKUP_MASK also to the flags from v0 messages for consistency with v1.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98805",
                                "url": "https://ubuntu.com/security/CVE-2026-98805",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  tipc: prevent GCM nonce reuse on peer key changes  TIPC can encrypt traffic between nodes using a different transmit key for each node. In this mode, the AES-GCM nonce for a packet sent to a known peer consists of a 32-bit prefix (a per-key salt XOR the peer's address) followed by a 64-bit counter. That counter is stored in the peer's RX crypto object. When the peer reports a change in which key it uses to receive packets, TIPC resets this counter. The sender can still be using the same TX key and salt, so subsequent packets reuse earlier nonces. This nonce reuse breaks confidentiality and exposes GCM's authentication key. This makes forgeries trivial: an attacker can exploit CTR malleability to alter captured ciphertexts and use the recovered authentication key to compute a valid tag for the modified ciphertext, under the same key and nonce.  Use the TX key's existing aead->seqno counter instead. All encryptions using that key object share the same atomic counter, so concurrent encryptions get distinct nonce counter values. The counter survives key activation and peer reconnection, and peer key-status reports cannot reset it. This prevents those transitions from causing nonce reuse while the same TX key remains installed.  The nonce format is unchanged, and receivers do not require consecutive counter values, so sharing the counter across peers remains compatible with existing receivers. A pre-existing check still invokes key revocation in the unlikely event that the counter wraps to zero.",
                                "cve_priority": "critical",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98811",
                                "url": "https://ubuntu.com/security/CVE-2026-98811",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net/sched: cls_api: reclaim an empty proto on the error path  Two racing tc filter add requests on the same chain/prio of an unlocked classifier both run change() on the shared proto and both can fail: the winner's tcf_chain_tp_delete_empty() attempt gives up because the loser's handle is still in the idr, and the loser's error path drops only its own reference without a second reclamation attempt. The empty proto stays linked in the chain, holding the chain reference, a block reference and the classifier module reference until the chain or block is torn down.  Reclaim the proto on the error path of any failed request that holds a proto reference. The reclamation is emptiness-gated: tcf_chain_tp_delete_empty() unlinks the proto only when delete_empty() admits it is empty, so a live shared proto is never unlinked. A proto the request created is reclaimed unconditionally - it is the only owner, so marking it for deletion is safe even without a delete_empty callback. Classifiers without one (the check marks the proto unconditionally) are rtnl-serialized, so the raced window this guard closes cannot arise for them.  This is a follow-up to commit d4e359b3608a (\"net/sched: cls_api: fix teardown of an adopted proto on insert-race loss\"), which stopped the loser of the insert race from unlinking the winner's live proto but left the empty-proto residual in place.  Conditions to recreate: - CONFIG_NET_CLS_FLOWER=y; veth pair - tc qdisc add dev veth0 ingress - two concurrent `tc filter add dev veth0 ingress protocol ip pref 1   flower skip_sw ... action drop` (both fail in fl_hw_replace_filter   after publishing their handle in the idr); repeat in a loop - an empty flower tp stays linked after both requests fail; visible   as a bare `filter protocol ip pref 1 flower chain 0` header in   `tc filter show` with no filter entries - CAP_NET_ADMIN (namespace-local via unshare -Urn suffices)",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98812",
                                "url": "https://ubuntu.com/security/CVE-2026-98812",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net/mctp: publish the mctp_dev only after it is initialised  mctp_add_dev() links the new mctp_dev into dev->mctp_ptr before mdev->dev is assigned, so a reader that picks the device up in that window dereferences a net_device pointer that is still NULL:  KASAN: null-ptr-deref in range [0x00000000000000b0-0x00000000000000b7] Call Trace:  <TASK>  ? __pfx_mctp_sendmsg (./include/linux/sockptr.h:49)  ? __pfx_mctp_dst_output (net/mctp/route.c:41)  ? selinux_socket_sendmsg (security/selinux/hooks.c:5278)  ____sys_sendmsg (net/socket.c:775 (discriminator 1) net/socket.c:790  (discriminator 1) net/socket.c:2684 (discriminator 1))  ? __pfx_____sys_sendmsg (net/socket.c:1131)  ? __pfx_copy_msghdr_from_user (net/socket.c:2590)  ? update_cfs_rq_load_avg (kernel/sched/fair.c:5478)  ___sys_sendmsg (net/socket.c:2738)  ? __pfx____sys_sendmsg (net/socket.c:2625)  ? perf_event_task_tick (./include/linux/rcupdate.h:838)  ? sched_tick (kernel/sched/core.c:5818)  ? clockevents_program_event (kernel/time/clockevents.c:372)  ? fdget (./include/linux/rcupdate.h:873 fs/file.c:1100)  __sys_sendmsg (net/socket.c:2770)  ? __pfx___sys_sendmsg (net/socket.c:2751)  do_syscall_64 (arch/x86/entry/syscall_64.c:63)  entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:121)  </TASK>  Fix by publishing only once the object is fully initialised: __mctp_dev_get() runs under rcu_read_lock() only and hands this object to readers as soon as mctp_ptr is assigned, so they must never observe mdev->dev == NULL.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98819",
                                "url": "https://ubuntu.com/security/CVE-2026-98819",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  Bluetooth: btintel: validate DDC record lengths  Parse DDC record lengths in unsigned storage so 0xFF does not wrap. Reject records smaller than the mandatory three-byte header, records exceeding U8_MAX, and records exceeding remaining firmware bytes before issuing Intel_Write_DDC.  This issue was reported by Claude Mythos.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98823",
                                "url": "https://ubuntu.com/security/CVE-2026-98823",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: cfg80211: preserve hidden-group beacon IE ownership  A hidden-group probe-response entry borrows its beacon IEs from the group's beacon entry. cfg80211_update_assoc_bss_entry() can pass such an entry to cfg80211_update_known_bss() when merging scan entries after a channel switch.  Copying the borrowed beacon_ies into the associated entry gives the same allocation two owners. Releasing the group's beacon entry can then leave the associated entry pointing to freed IEs, which are freed again when that entry is released.  Skip beacon IE replacement when the source entry belongs to a hidden group. Preserve probe-response processing, the subsequent metadata updates, and the existing rejection path for conflicting hidden beacon updates.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98936",
                                "url": "https://ubuntu.com/security/CVE-2026-98936",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: ath11k: reset ar->num_stations on hardware start  When (multiple) hw restart occurs, we end up in a situation where we cannot accept new stations / mesh peers. This seems to be the 'num_stations' in 'struct ath11k' that did not get reset properly in this case. In ath11k_mac_op_start(), it was indeed the only accounting var that did not get reset so let's clear it too.  This avoids problems like those:  \t[1248828.088023] WARNING: CPU: 0 PID: 12281 at net/mac80211/util.c:1682 ieee80211_reconfig_stations+0x98/0xc0 \t[1248828.088115] Call trace: \t[1248828.088116]  ieee80211_reconfig_stations+0x98/0xc0 (P) \t[1248828.088119]  ieee80211_reconfig+0x774/0x1438 \t[1248828.088123]  ieee80211_restart_work+0x10c/0x178 \t[1248828.088127]  process_one_work+0x178/0x3c0 \t[1248828.088130]  worker_thread+0x280/0x440 \t[1248828.088133]  kthread+0xe0/0xf8 \t[1248828.088137]  ret_from_fork+0x10/0x20 \t[1248828.088141] ---[ end trace 0000000000000000 ]--- \t[1248836.686604] ath11k_pci 0000:04:00.0: refusing to associate station: too many connected already (128) \t[1248836.686609] ath11k_pci 0000:04:00.0: Failed to add station: xx:xx:xx:xx:xx:xx for VDEV: 1  Tested-on: QCN9074 hw1.0 PCI WLAN.HK.2.9.0.1-01977-QCAHKSWPL_SILICONZ-1",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-23 13:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98831",
                                "url": "https://ubuntu.com/security/CVE-2026-98831",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  of/overlay: don't leak fragment references when changeset init fails  init_overlay_changeset() stores the number of initialized fragments in ovcs->count only on full success. When find_target() or the __symbols__ lookup fails partway through, the target and overlay references taken for the fragments initialized so far are never dropped: free_overlay_changeset() bounds its cleanup loop by ovcs->count, which is still 0.  Store the running count on the error path so free_overlay_changeset() puts whatever was set up. The store is guarded by ovcs->fragments because on the allocation-failure path cnt still holds the counting pass total while there is no fragments array; everywhere else cnt only counts fully-initialized fragments.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98833",
                                "url": "https://ubuntu.com/security/CVE-2026-98833",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  mtd: core: call _get_device() with the master MTD  __get_mtd_device() calls the master's _get_device() callback with mtd, which may be a partition. __put_mtd_device() passes the master.  This breaks gluebi partitions because gluebi_get_device() uses container_of() and therefore requires the master MTD. Pass the master to _get_device(), matching _put_device().",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-89860",
                                "url": "https://ubuntu.com/security/CVE-2026-89860",
                                "cve_description": "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 second INIT_WORK() reinitializes a work item that is already queued, which can corrupt the workqueue list and lead to crashes or a looping worker.  Initialize priv->abort_work once at command submission, next to the existing per-command spin_lock_init(&priv->cmd_lock), and leave only schedule_work() in the abort paths. schedule_work() already does nothing when the work item is still pending, so a repeated abort no longer disturbs an in-flight work item. The command is not returned to the transport until the final kref_put()/release callback runs after abort_work has completed, so the work item is idle before priv is reused and the single submission-time INIT_WORK() is safe.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-09-16 11:16:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-53353",
                                "url": "https://ubuntu.com/security/CVE-2026-53353",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  hsr: Remove WARN_ONCE() in hsr_addr_is_self().  syzbot reported the warning [0] in hsr_addr_is_self(), whose assumption is simply wrong.  hsr->self_node is cleared in hsr_del_self_node(), which is called from hsr_dellink().  Since dev->rtnl_link_ops->dellink() is called before unregister_netdevice_many(), there is a window when user can find the device but without hsr->self_node.  Let's remove WARN_ONCE() in hsr_addr_is_self().  [0]: HSR: No self node WARNING: net/hsr/hsr_framereg.c:39 at hsr_addr_is_self+0x211/0x3f0 net/hsr/hsr_framereg.c:39, CPU#0: syz.4.16848/17220 Modules linked in: CPU: 0 UID: 0 PID: 17220 Comm: syz.4.16848 Tainted: G             L     syzkaller #0 PREEMPT_{RT,(full)} Tainted: [L]=SOFTLOCKUP Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/18/2026 RIP: 0010:hsr_addr_is_self+0x211/0x3f0 net/hsr/hsr_framereg.c:39 Code: 33 2f 41 0f b7 dd 89 ee 09 de 31 ff e8 c8 b4 c6 f6 09 dd 74 54 e8 0f b0 c6 f6 31 ed eb 53 e8 06 b0 c6 f6 48 8d 3d 2f 50 9c 04 <67> 48 0f b9 3a 31 ed eb 42 e8 c1 13 1f 00 89 c5 31 ff 89 c6 e8 96 RSP: 0018:ffffc900041c70e0 EFLAGS: 00010283 RAX: ffffffff8afdc6ca RBX: ffffffff8afdc4e6 RCX: 0000000000080000 RDX: ffffc90010493000 RSI: 0000000000000948 RDI: ffffffff8f9a1700 RBP: 0000000000000001 R08: 0000000000000000 R09: 0000000000000000 R10: ffffc900041c71e8 R11: fffff52000838e3f R12: dffffc0000000000 R13: ffff888041f9e3c0 R14: ffff888086ee3802 R15: 0000000000000000 FS:  00007f6fe985d6c0(0000) GS:ffff888126176000(0000) knlGS:0000000000000000 CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f80bd437dac CR3: 0000000025096000 CR4: 00000000003526f0 DR0: ffffffffffffffff DR1: 00000000000001f8 DR2: 0000000000000002 DR3: ffffffffefffff15 DR6: 00000000ffff0ff0 DR7: 0000000000000400 Call Trace:  <TASK>  check_local_dest net/hsr/hsr_forward.c:592 [inline]  fill_frame_info net/hsr/hsr_forward.c:728 [inline]  hsr_forward_skb+0xa11/0x2a80 net/hsr/hsr_forward.c:739  hsr_dev_xmit+0x253/0x370 net/hsr/hsr_device.c:236  __netdev_start_xmit include/linux/netdevice.h:5368 [inline]  netdev_start_xmit include/linux/netdevice.h:5377 [inline]  xmit_one net/core/dev.c:3888 [inline]  dev_hard_start_xmit+0x2df/0x860 net/core/dev.c:3904  __dev_queue_xmit+0x1428/0x3900 net/core/dev.c:4870  neigh_output include/net/neighbour.h:556 [inline]  ip_finish_output2+0xcec/0x10b0 net/ipv4/ip_output.c:237  ip_send_skb net/ipv4/ip_output.c:1510 [inline]  ip_push_pending_frames+0x8b/0x110 net/ipv4/ip_output.c:1530  raw_sendmsg+0x1547/0x1a50 net/ipv4/raw.c:659  sock_sendmsg_nosec net/socket.c:787 [inline]  __sock_sendmsg net/socket.c:802 [inline]  ____sys_sendmsg+0x7da/0x9c0 net/socket.c:2698  ___sys_sendmsg+0x2a5/0x360 net/socket.c:2752  __sys_sendmsg net/socket.c:2784 [inline]  __do_sys_sendmsg net/socket.c:2789 [inline]  __se_sys_sendmsg net/socket.c:2787 [inline]  __x64_sys_sendmsg+0x1c3/0x2a0 net/socket.c:2787  do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]  do_syscall_64+0x15f/0xf80 arch/x86/entry/syscall_64.c:94  entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f6feb62ce59 Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 e8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f6fe985d028 EFLAGS: 00000246 ORIG_RAX: 000000000000002e RAX: ffffffffffffffda RBX: 00007f6feb8a6090 RCX: 00007f6feb62ce59 RDX: 0000000000000000 RSI: 0000200000000000 RDI: 0000000000000004 RBP: 00007f6feb6c2d6f R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007f6feb8a6128 R14: 00007f6feb8a6090 R15: 00007ffcf01cc488  </TASK>",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-07-01 14:16:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98836",
                                "url": "https://ubuntu.com/security/CVE-2026-98836",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ALSA: line6: reject oversized playback packets  Each playback URB is handed a slice of out.buffer that is exactly LINE6_ISO_PACKETS * max_packet_size_out bytes, sized from the OUT endpoint, but the number of bytes written into that slice is never compared against it.  submit_audio_out_urb() takes the frame count from prev_fsize, which audio_in_callback() derived from the *IN* endpoint's received packet length, and rescales it with the playback frame size; when prev_fsize is still zero it synthesizes a length from the sample rate instead.  On a device declaring a large IN wMaxPacketSize and a small OUT wMaxPacketSize, the resulting memcpy(), or the memset() when the playback stream is idle, runs past its slice and, as the reproducer below shows, beyond the allocation.  usb_submit_urb() is not a backstop.  max_packet_size_out comes from usb_maxpacket(), which returns only the low 11 bits of wMaxPacketSize, while USB core validates a high-speed isochronous length against that base scaled by usb_endpoint_maxp_mult().  A length of up to three times the allocated slice is therefore accepted, and even a rejected URB is only rejected after the write.  Reject a packet that does not fit the slice the driver allocated for it. Clamping it instead would silently shorten the capture-derived rate feedback and desynchronize the two streams.    BUG: KASAN: slab-out-of-bounds in submit_audio_out_urb (sound/usb/line6/playback.c:229)   Write of size 1024 at addr ffff888100bbd400 by task kworker/1:2/5002   Workqueue: events line6_startup_work   Call Trace:    __asan_memcpy (mm/kasan/shadow.c:106)    submit_audio_out_urb (sound/usb/line6/playback.c:229)    line6_submit_audio_out_all_urbs (sound/usb/line6/playback.c:291)    line6_stream_start (sound/usb/line6/pcm.c:194)    line6_pcm_acquire (sound/usb/line6/pcm.c:337)    line6_startup_work (sound/usb/line6/driver.c:728)    process_one_work (kernel/workqueue.c:3396)    worker_thread (kernel/workqueue.c:3479 kernel/workqueue.c:3560)    kthread (kernel/kthread.c:436)    ret_from_fork (arch/x86/kernel/process.c:158)    ret_from_fork_asm (arch/x86/entry/entry_64.S:245)    The buggy address belongs to the object at ffff888100bbd400    which belongs to the cache kmalloc-256 of size 256   The buggy address is located 0 bytes inside of    allocated 256-byte region [ffff888100bbd400, ffff888100bbd500)",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98838",
                                "url": "https://ubuntu.com/security/CVE-2026-98838",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  vt: skip screen update for DEC alignment test on backgroup consoles  [BUG] Recently, we encountered a KASAN warning as follows:  BUG: KASAN: slab-out-of-bounds in fb_pad_aligned_buffer+0x11f/0x140 Read of size 1 at addr ff1100015fd9f6a4 by task tty_fbcon_oob/1239 CPU: 7 UID: 0 PID: 1239 Comm: tty_fbcon_oob Not tainted 7.3.0-rc1 #100 PREEMPT(full) Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.17.0-4.fc41 04/01/2014 Call Trace:  <TASK>  ...  kasan_report+0xf0/0x120  fb_pad_aligned_buffer+0x11f/0x140  ccw_putcs+0x86c/0xa80  fbcon_putcs+0x338/0x410  do_update_region+0x21d/0x450  do_con_write+0x1e0e/0x4880  con_write+0x13/0x80  n_tty_write+0x374/0x1010  file_tty_write.isra.0+0x404/0x7a0  ...  reproduce: 1) open /dev/tty0, set a KDFONTOP ioctl with op.op = KD_FONT_OP_SET, op.width = 8 and op.height = 16 (visible VC1) 2) open /dev/tty1, set a KDFONTOP ioctl with op.op = KD_FONT_OP_SET, op.width = 28 and op.height = 24 (invisible VC2) 3) echo 3 > /sys/devices/virtual/graphics/fbcon/rotate_all 4) write EShash8(esc hash8) to tty1  [CAUSE] All VCs render to the framebuffer. setfont only modifies the target VC's font without resizing the framebuffer backing buffer (par->rotated.buf); the buffer is only resized for the visible VC (fbcon_do_set_font -> ... -> vc_do_resize -> update_screen). This relies on the con_should_update() check performed before every update_region().  However, the ESC # 8 path (do_con_trol -> do_update_region) omits the con_should_update() check. After changing the font size of an invisible VC, do_update_region() fills using the new font size against a buffer that was never resized, causing an out-of-bounds access.  [FIX] Only push the update when the console is visible and not blanked, add the con_should_update() check in the do_con_trol() like every other call site of do_update_region() (update_region(), invert_screen(), ...).",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98568",
                                "url": "https://ubuntu.com/security/CVE-2026-98568",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  vxlan: use one headroom snapshot for neighbour replies  vxlan_na_create() samples LL_RESERVED_SPACE() to size the reply skb and then samples it again to reserve headroom. A concurrent vxlan_changelink() can update needed_headroom between the two reads, creating a TOCTOU race. The second value can exceed the allocation and make the Ethernet header write out of bounds.  The race is reproducible on the unpatched kernel. It occurred when vxlan_na_create() generated a neighbour reply while vxlan_changelink() changed the link headroom. KASAN caught a four-byte write two bytes beyond a 704-byte skbuff_small_head allocation.  Snapshot the headroom once and use that value for both allocation and reservation.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2024-49901",
                                "url": "https://ubuntu.com/security/CVE-2024-49901",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  drm/msm/adreno: Assign msm_gpu->pdev earlier to avoid nullptrs  There are some cases, such as the one uncovered by Commit 46d4efcccc68 (\"drm/msm/a6xx: Avoid a nullptr dereference when speedbin setting fails\") where  msm_gpu_cleanup() : platform_set_drvdata(gpu->pdev, NULL);  is called on gpu->pdev == NULL, as the GPU device has not been fully initialized yet.  Turns out that there's more than just the aforementioned path that causes this to happen (e.g. the case when there's speedbin data in the catalog, but opp-supported-hw is missing in DT).  Assigning msm_gpu->pdev earlier seems like the least painful solution to this, therefore do so.  Patchwork: https://patchwork.freedesktop.org/patch/602742/",
                                "cve_priority": "low",
                                "cve_public_date": "2024-10-21 18:15:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98846",
                                "url": "https://ubuntu.com/security/CVE-2026-98846",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  sctp: check RCV_SHUTDOWN after the sendmsg connect wait  sctp_wait_for_connect() drops the socket lock while it sleeps. An out-of-the-blue ABORT can then be processed from the socket backlog and unlink the association. If a concurrent shutdown(fd, SHUT_RD) sets RCV_SHUTDOWN, the waiter breaks with err == 0 before checking asoc->base.dead. Its final sctp_association_put() can then free the association, leaving sctp_sendmsg_to_asoc() to continue with a dangling pointer.  Check RCV_SHUTDOWN along with the wait error in sctp_sendmsg_to_asoc() before using the association again. The check only accesses the socket, so it needs no additional association reference. Return the existing -ESRCH so that sctp_sendmsg() skips freeing a new association that may already have been destroyed.  Keep sctp_wait_for_connect() unchanged to preserve its behavior for the connect() caller.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98847",
                                "url": "https://ubuntu.com/security/CVE-2026-98847",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  rtc: spear: initialize IRQ state before requesting alarm IRQ  devm_request_irq() enables the interrupt before it returns, so the handler may run while probe is still initializing the device. Initialize the MMIO address and spinlock before requesting the alarm IRQ.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98850",
                                "url": "https://ubuntu.com/security/CVE-2026-98850",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net/packet: prevent TX_RING byte count overflow  tpacket_snd() drains every SEND_REQUEST frame in a TX ring and adds each valid packet length to the signed int len_sum. Userspace can recycle completed frames concurrently, so a single blocking send call is not bounded by the ring size.  After enough successful transmissions len_sum wraps into the negative range. In particular, 65536 65535-byte frames followed by a 65007-byte frame produce 0xfffffdef, or -EIOCBQUEUED. sock_sendmsg_nosec() treats that as an impossible return and triggers a BUG. On systems configured to panic on oops, a CAP_NET_RAW holder can panic the host kernel.  Stop before the next frame would make the byte count exceed INT_MAX. The positive short count leaves that frame pending for a later send call.  A two-thread TPACKET_V2 reproducer triggered the BUG on an arm64 build of Linux 7.3-rc4. With this change, the same reproducer returned the expected positive short count without an oops.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98851",
                                "url": "https://ubuntu.com/security/CVE-2026-98851",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  netfilter: nft_flow_offload: drop flowtable reference on init error path  nft_flow_offload_init() bumps the flowtable use count with nft_use_inc() before calling nf_ct_netns_get().  When the latter fails, the error is returned as-is and the reference is leaked.  The upper layers do not balance it either: nf_tables_newexpr() clears expr->ops when the expression init callback fails, so the nft_expr_more() iteration in nft_rule_expr_deactivate() and nf_tables_rule_destroy() stops right before the failed expression and its ->destroy callback, which would drop the reference, never runs.  Each failed rule addition therefore leaks one flowtable reference and the flowtable can no longer be removed: NFT_MSG_DELFLOWTABLE keeps reporting -EBUSY even though no rule references it.  Save the nf_ct_netns_get() return value and undo the nft_use_inc() when it fails, restoring the inc/dec pairing within nft_flow_offload_init() itself.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98854",
                                "url": "https://ubuntu.com/security/CVE-2026-98854",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  of/overlay: only treat a positive changeset id as registered  of_overlay_fdt_apply() stores the idr_alloc() return value in ovcs->id before checking it. On failure the stored id is negative, free_overlay_changeset()'s \"if (ovcs->id)\" check passes, idr_remove() is called with a negative id and list_del() runs on ovcs->ovcs_list, which is not initialized until after the id allocation. An allocation failure at that point dereferences NULL.  Make free_overlay_changeset() treat only a strict-positive id as registered. The rest of the function already copes with a partially-initialized ovcs, so the error path stays a plain goto err_free_ovcs.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98855",
                                "url": "https://ubuntu.com/security/CVE-2026-98855",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  of/overlay: put property on deadprops only after changeset add succeeds  add_changeset_property() links a new property of a not-yet-live target node into the node's deadprops list before handing it to of_changeset_add_property(). If that fails, the error path frees the property but leaves the freed pointer linked in deadprops, and of_node_release() frees it a second time when the aborted overlay's node is released.  Record the changeset entry first and link the property into deadprops only on success. of_changeset_add_property() never looks at the node's property lists, so the order of the two steps is otherwise immaterial, and the error path frees a property that nothing references.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98862",
                                "url": "https://ubuntu.com/security/CVE-2026-98862",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  audit: fix exe mark UAF in kill_rules()  kill_rules() removes mixed AUDIT_DIR and AUDIT_EXE rules when an audit tree is pruned. It drops entry->rule.exe before removing the rule from the RCU-visible filter lists.  After a rule has been installed with AUDIT_ADD_RULE, which requires CAP_AUDIT_CONTROL, removing the watched directory can race with another task that is still evaluating the rule. In that case, fsnotify can free the executable mark before the reader reaches audit_mark_compare(), causing a use-after-free.  KASAN reports:      BUG: KASAN: slab-use-after-free in audit_mark_compare+0x8d/0xa0  Unlink the published rules from the RCU-visible lists and retain them on tree->rules for cleanup. If any rule has an executable mark, wait for a single RCU grace period before removing the marks and scheduling the entries for freeing. Otherwise, call_rcu() already provides the required deferred freeing without a synchronous wait.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98450",
                                "url": "https://ubuntu.com/security/CVE-2026-98450",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  smb: client: close completed creates on compound wait errors  compound_send_recv() waits for responses in order. If a later wait is interrupted, or if a later MID fails during response synchronization, an earlier CREATE may already have opened a remote handle. The earlier mid is then released without invoking handle_cancelled_mid(), leaving the remote handle open because no FID was copied to the caller.  Mark completed earlier mids as cancelled when a compound wait or MID synchronization aborts. Keep their response buffers attached while the MIDs are synchronized, and transfer them only after synchronization of the processed responses, so the release path can inspect successful CREATE responses and queue SMB2_close() after a later failure. Account for a remote open only after the close work is allocated and before it is queued, since the caller has not yet updated num_remote_opens. Mark the create+close compound used by smb2_unlink() so it is not closed again. Non-CREATE responses and compounds that already include a close keep their existing behavior.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:16:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98502",
                                "url": "https://ubuntu.com/security/CVE-2026-98502",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  HID: alps: unregister DualPoint Stick input device on remove  alps_input_configured() allocates a second input device (\"DualPoint Stick\") with input_allocate_device() and registers it, but the alps_driver struct has no .remove handler and input2 is not tracked in hdev->inputs.  The default remove path (hid_hw_stop -> hidinput_disconnect) only iterates hdev->inputs, so input2 is never unregistered and leaks on every device removal.  Add a .remove handler that stops the device first (preventing URB callbacks from touching input2 during teardown) and then unregisters input2.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98456",
                                "url": "https://ubuntu.com/security/CVE-2026-98456",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  Bluetooth: mgmt: fix race in read_unconf_index_list()  read_unconf_index_list() counts unconfigured controllers before allocating its response, then checks the device flags again while filling it.  hci_dev_list_lock stabilizes list membership, but it does not serialize the per-device flags. During asynchronous controller setup, the worker can set HCI_UNCONFIGURED and clear HCI_SETUP between the two passes. A controller omitted from the allocation count can then become eligible for the fill pass, causing an out-of-bounds write to rp->index[].  Allocate space for every device on hci_dev_list. Since list membership cannot change while hci_dev_list_lock is held, the response remains large enough regardless of flag transitions. The reported count and response length still include only eligible unconfigured controllers.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-18 16:16:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98451",
                                "url": "https://ubuntu.com/security/CVE-2026-98451",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  smb: client: use finish_no_open() for non-regular inodes  An O_CREAT open can find an existing symlink or another non-regular inode. cifs_atomic_open() calls finish_open() on it and attaches a cifsFileInfo. Symlink inodes have no CIFS release operation, so the dentry reference held by cifsFileInfo is leaked. FMODE_OPENED also prevents the VFS from following the symlink.  Track whether cifs_do_create() returned an open server handle. For non-regular inodes, close the handle if present, remove the pending open, and call finish_no_open() so the VFS can continue the lookup. Do not set FMODE_CREATED unless a regular file was opened. For O_NOFOLLOW with __O_REGULAR, return -ELOOP before the VFS's -EFTYPE check.  Defer closing a legacy POSIX handle on a non-regular inode until after inode lookup. This avoids closing it again if lookup fails.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-18 16:16:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98484",
                                "url": "https://ubuntu.com/security/CVE-2026-98484",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  netfilter: nf_tables: skip expired catchall elements on insert and delete  nft_setelem_catchall_insert() looks up duplicates with nft_set_elem_active() only, while nft_set_catchall_lookup() and the dump path additionally skip expired elements.  Once a catchall element with a timeout expires, this predicate drift makes it invisible to userspace dumps, yet it still blocks re-insertion: with NLM_F_EXCL the request fails with -EEXIST, and without it the request reports success but silently inserts nothing. The stale entry only goes away when the (user-tunable) gc interval elapses, so the catchall rule may silently stop matching for an arbitrarily long time after its first expiration.  The delete path shows the same drift: nft_setelem_catchall_deactivate() picks the first active-next entry in the catchall list, so with an expired entry still pending GC it retires the stale entry instead of the fresh one, and it deactivates an element that userspace no longer sees instead of failing with -ENOENT.  Align both walks with the lookup and dump predicates: only an element that is active and not expired counts as a duplicate or delete candidate, using the per-netns timestamp taken at transaction start, in line with the set backend .insert/.deactivate and catchall GC sync paths.",
                                "cve_priority": "negligible",
                                "cve_public_date": "2026-10-18 16:16:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98486",
                                "url": "https://ubuntu.com/security/CVE-2026-98486",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net: ena: fix MMIO read buffer leak on probe failure  ena_device_init() initializes the MMIO read mechanism with ena_com_mmio_reg_read_request_init(), which allocates a coherent DMA buffer for MMIO read responses.  The normal removal path releases this buffer through ena_com_mmio_reg_read_request_destroy(). However, if ena_probe() fails after ena_device_init() succeeds, the error path destroys the admin resources and eventually frees ena_dev without destroying the MMIO read request, leaving the coherent DMA buffer allocated.  Call ena_com_mmio_reg_read_request_destroy() in the probe error path before releasing the remaining device resources.  This issue was found by manual code inspection.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:16:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98493",
                                "url": "https://ubuntu.com/security/CVE-2026-98493",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net: ipconfig: bound DHCP option construction  ic_dhcp_init_options() appends the hostname (option 12), vendor-class (option 60) and client-ID (option 61) options into the fixed 312-byte bootp_pkt.exten[] buffer.  Only the client-ID branch checked the remaining space; the hostname and vendor-class writes were unbounded.  A 64-byte hostname together with the maximum 252-byte dhcpclass= identifier needs 18 + (2 + 64) + (2 + 252) = 338 of the 312 available bytes even before the terminating END marker, so the vendor-class memcpy runs past the end of exten[].  With CONFIG_FORTIFY_SOURCE this is reported as a field-spanning write and, when the kernel is booted with panic_on_warn=1, aborts boot with a panic.  Route the optional options through a common helper that makes sure the option, its 2-byte header and the END marker all fit and drops an option that would not.  Configurations with short options keep sending exactly the same bytes as before.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98454",
                                "url": "https://ubuntu.com/security/CVE-2026-98454",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  smb: client: fix create context out-of-bounds reads  smb2_parse_contexts() validates the complete create-context area but does not limit each record to its Next field before dispatching it.  A malformed chain can therefore expose bytes beyond the current context to a handler.  The QFid handler also used a full response-structure cast although it only reads DiskFileId.  The SMB2/SMB3 lease parsers made the same layout assumption: they read LeaseState and LeaseFlags at canonical offsets rather than at DataOffset.  A valid non-canonical DataOffset could therefore yield unrelated in-bounds data, while a short DataLength was still accepted.  Limit each context to its Next value, reject offsets before the context header, and reject malformed chains.  Bound the name range by the current context and do not dispatch a known handler when DataLength is zero.  Read the QFid DiskFileId only when the context data covers that field.  Parse the lease context from DataOffset and require DataLength to match the v1 or v2 lease_context size used by ksmbd.  A size mismatch skips lease parsing without failing the open.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-18 16:16:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98490",
                                "url": "https://ubuntu.com/security/CVE-2026-98490",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net: openvswitch: conntrack: fix helper UAF due to extensions realloc  While calling the helpers, a raw pointer to the extensions area is wired into expectations list:    -> nf_ct_helper()    -> helper->help()     -> nf_ct_expect_related_report()      -> nf_ct_expect_insert()       -> hlist_add_head_rcu(&exp->lnode, &master_help->expectations)  In case the connection is not confirmed yet, more extensions can be added afterwards with *_ext_add() calls reallocating the extension space and leaving the now invalid pointer in the expectations list that is later accessed while removing the expectation.  Make sure that helpers are called at the end after all the other extensions are already added.  Note that the helper rejection now leaves the mark and labels set, but that's not different from how the NAT was handled before or how the mark and the labels were handled on confirmation failure.  And there are no atomicity guarantees provided by the API anyway.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-18 16:16:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98507",
                                "url": "https://ubuntu.com/security/CVE-2026-98507",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  mm/rmap: fix missing barrier between anon_vma init and vma->anon_vma publish  On arm64 server, we find that a task trying to grab the anon_vma lock triggers hungtask.  INFO: task main:2354726 blocked for more than 120 seconds.       Tainted: G            E     5.10.0-0021.aarch64 #1 \"echo 0 > /proc/sys/kernel/hung_task_timeout_secs\" disables this message. task:main            state:D stack:    0 pid:2354726 ppid:2350673 flags:0x00000a01 Call trace:  __switch_to+0x7c/0xbc  __schedule+0x3b4/0x8a0  schedule+0x50/0xe0  rwsem_down_write_slowpath+0x3cc/0x6cc  down_write+0x60/0x260  __anon_vma_prepare+0x6c/0x210  do_anonymous_page+0x258/0x660  handle_pte_fault+0x188/0x214  __handle_mm_fault+0x1b0/0x380  handle_mm_fault+0xf4/0x284  do_page_fault+0x19c/0x494  do_translation_fault+0xcc/0xf8  do_mem_abort+0x48/0xac  el0_da+0x44/0x80  el0_sync_handler+0x88/0xb4  el0_sync+0x160/0x180  After analyzing the vmcore, we found the anon_vma->root->rwsem.count is -1.  There is another anon_vma whose anon_vma->root->rwsem.count is 1, the anon_vma->root->rwsem.owner shows the lock is held, but the stack of the task shows the task doesn't hold the anon_vma lock.  After adding more debugging info, we found __anon_vma_prepare() reuses anon_vma and triggers the UAF of anon_vma->root due to missing memory barrier, leading to locking and unlocking two different anon_vma->root, thus leading to an anon_vma will never be unlocked, and another anon_vma couldn't be locked anymore.  This race requires two adjacent VMAs that are not merged but are anon_vma-compatible (e.g., they differ in VMA_ACCESS_FLAGS that can be changed by mprotect()).  Two threads fault on each VMA concurrently, both calling __anon_vma_prepare() with only mmap_lock held for reading.      THREAD A                             THREAD B __anon_vma_prepare                __anon_vma_prepare  find_mergeable_anon_vma() -> NULL  anon_vma = anon_vma_alloc();    anon_vma->root = anon_vma;  // the two stores may be reordered  vma->anon_vma = anon_vma;                                    // finds A's anon_vma                                    anon_vma = find_mergeable_anon_vma(vma);                                    anon_vma_lock_write(anon_vma);                                      // may still see the old root                                      down_write(&anon_vma->root->rwsem);                                    anon_vma_unlock_write(anon_vma);                                      // see the new root, never unlock old                                      up_write(&anon_vma->root->rwsem);  thread A triggers page fault and calls __anon_vma_prepare() to prepare anon_vma for the faulting vma.  __anon_vma_prepare() allocates and initializes a new anon_vma, and then publishes it to the vma with a plain store.  anon_vma_prepare() only requires the mmap_lock to be held for reading, so two threads can fault on adjacent VMAs at the same time. While thread A publishes a new anon_vma, thread B could find the anon_vma via find_mergeable_anon_vma() and then locks anon_vma->root->rwsem.  The store to anon_vma->root in anon_vma_alloc() and the store to vma->anon_vma can be reordered.  The anon_vma_lock_write() and spin_lock() only provide acquire semantics, which do not prevent prior stores from being reordered after them.  The release semantics of the corresponding spin_unlock() and anon_vma_unlock_write() come too late, the store to vma->anon_vma is already published before they take effect.  As a result, thread B can observe the following order:      vma->anon_vma = anon_vma;     anon_vma->root = anon_vma;  The anon_vma slab is SLAB_TYPESAFE_BY_RCU, so a newly allocated anon_vma may reuse memory from a previously freed one.  The constructor (anon_vma_ctor) does not reset anon_vma->root, and __put_anon_vma() doesn't clear it either, so the old root value persists until anon_vma_alloc() overwrites it.  If that store isn't v ---truncated---",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98519",
                                "url": "https://ubuntu.com/security/CVE-2026-98519",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  drm/amdgpu: Fix runtime PM leak in amdgpu_debugfs_test_ib_show()  amdgpu_debugfs_test_ib_show() resumes the device with pm_runtime_get_sync() before taking the reset domain semaphore with down_write_killable().  If the write lock acquisition is interrupted, the function returns without calling pm_runtime_put_autosuspend(), leaking the runtime PM reference acquired for the device and keeping the GPU awake.  Drop the runtime PM reference on the interrupted down_write_killable() error path before returning.  (cherry picked from commit ec30a576c2d4c0364549e6c04218f50704ef56c8)",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98549",
                                "url": "https://ubuntu.com/security/CVE-2026-98549",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  tcp: prevent collapsing skbs across boundary in rtx queue  tcp_write_collapse_fence() sets TCP_SKB_CB(skb)->eor = 1 on tcp_write_queue_tail(sk) to prevent skbs queued after a switch to device encryption from being collapsed into earlier skbs.  The fence is a no-op if all earlier data has already been transmitted when the switch happens: sk->sk_write_queue is empty. The not yet acknowledged earlier skbs wait in sk->tcp_rtx_queue with eor 0.  On a subsequent retransmit or SACK shift, tcp_retrans_try_collapse() or tcp_shift_skb_data() can then merge an skb queued after the switch into one queued before it.  Both users of the fence are affected:  - psp: devices only encrypt skbs with skb->decrypted set. The merged skb   keeps decrypted = 0 from the earlier skb, so merged data sent after   psp_sock_assoc_set_tx() is retransmitted in cleartext.  - tls device offload: the merged skb straddles the start marker set in   tls_set_device_offload(). The software fallback (fill_sg_in() returns   -EINVAL) and the mlx5, nfp and funeth drivers cannot handle such an   skb and drop it. Every retransmit rebuilds the same skb, so the   connection stalls.  Fix this in two places, for defense in depth:  1. Fall back to tcp_rtx_queue_tail(sk) in tcp_write_collapse_fence()    when tcp_write_queue_tail(sk) is NULL.  2. Check !skb_cmp_decrypted(to, from) in tcp_skb_can_collapse(), as    tcp_skb_can_collapse_rx() does on receive. skb_shift(), which both    collapse paths call, already has a DEBUG_NET_WARN_ON_ONCE() for this    condition.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98544",
                                "url": "https://ubuntu.com/security/CVE-2026-98544",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  bna: prevent IOC timer rearm during teardown  bna: prevent IOC timer rearm during teardown  bnad_pci_remove() and the probe disable_ioceth path call timer_delete_sync() for ioc_timer, sem_timer and hb_timer, but not for iocpf_timer.  bnad_iocpf_timeout() then takes bnad->bna_lock after free_netdev() has freed the struct bnad.  Deleting iocpf_timer last does not fix this.  sem_timer and iocpf_timer rearm each other: bnad_iocpf_sem_timeout() can arm iocpf_timer, and bnad_iocpf_timeout() arms sem_timer from bfa_ioc_hw_sem_get() when the semaphore is busy. timer_delete_sync() only waits out its own callback. bnad_ioceth_disable() can time out and leave that callback live.  Shut all four IOC timers down with timer_shutdown_sync() on both paths, so a later mod_timer() is ignored.  This issue was identified during our ongoing static-analysis research while reviewing kernel code.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-18 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98172",
                                "url": "https://ubuntu.com/security/CVE-2026-98172",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  smb: client: fix smbd_connection leak on cifs_get_tcp_session() error  When an RDMA connection is successfully established via smbd_get_connection() but cifs_get_tcp_session() later fails (e.g. kthread_create() returns an error), the error path frees tcp_ses without first destroying the smbd_connection.  Fix this by calling smbd_destroy() in the out_err cleanup path before kfree(tcp_ses).  smbd_destroy() safely handles the case where smbd_conn is NULL, so it can be called unconditionally.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-06 09:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98192",
                                "url": "https://ubuntu.com/security/CVE-2026-98192",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: wcn36xx: Fix potential use-after-free in TX ack timer teardown  wcn36xx_dxe_deinit() tears down the TX ack timer with timer_delete(), which only dequeues the timer and does not wait for a callback that is already executing; the preceding free_irq() calls synchronize the interrupt handlers only. The callback, wcn36xx_dxe_tx_timer(), can therefore be running past the teardown and use the wcn freed along with the ieee80211_hw in wcn36xx_remove(): it takes wcn->dxe_lock, reads wcn->tx_ack_skb and passes wcn->hw to ieee80211_tx_status_irqsafe().  Fix this by using timer_shutdown_sync(), which waits for a running callback and also prevents the timer from being rearmed again. The timer is set up again by wcn36xx_dxe_init() on the next start, so the start/stop cycle is unaffected.  This issue was found by an in-house static analysis tool.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-06 09:18:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98198",
                                "url": "https://ubuntu.com/security/CVE-2026-98198",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  hwmon: (pwm-fan) Stop RPM timer before freeing tach data  sample_timer() rearms the RPM timer and accesses the devm-managed ctx->tachs and ctx->pulses_per_revolution arrays. The cleanup action which stops the timer is registered before those arrays are allocated.  Since devres releases entries in reverse order, driver detach can free the arrays before pwm_fan_cleanup() shuts down the timer. A timer expiry in that window accesses the freed tach data.  With a KASAN kernel, a test-only kprobe delayed entry to pwm_fan_cleanup() while normal sysfs unbind ran. Each of three runs reported three four-byte reads and two four-byte writes in sample_timer() after its backing devm allocations had been freed. The helper did not invoke the timer callback, cleanup actions or free functions.  With the fix, three matching unbind runs completed without KASAN, BUG, WARNING, Oops or panic. Instrumentation confirmed that timer retirement completed before the first timer backing allocation was released.  Split timer retirement from the power cleanup and register its devres action after the timer backing data and IRQ actions are installed. This preserves the early power rollback action while ensuring the timer is retired before its backing data is released. Use timer_shutdown_sync() because the callback can rearm itself.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-06 09:18:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98409",
                                "url": "https://ubuntu.com/security/CVE-2026-98409",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  watchdog: rtd119x: Avoid division by zero  clk_get_rate() could return 0.  Avoid a division by zero panic.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-14 14:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98245",
                                "url": "https://ubuntu.com/security/CVE-2026-98245",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  btrfs: take commit root semaphore when iterating in mark_block_group_to_copy()  mark_block_group_to_copy() iterates over the commit root with skip_locking=true. A concurrent transaction commit can swap and free the commit root during iteration, causing use-after-free when accessing extent buffers.  Fix it by using path->need_commit_sem to protect the commit root search.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-06 09:18:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98264",
                                "url": "https://ubuntu.com/security/CVE-2026-98264",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ALSA: virtio: reset device before deleting virtqueues  virtsnd_remove() and virtsnd_freeze() delete the virtqueues before resetting the device. del_vqs() frees the vring backing, but does not provide a generic device quiesce operation. In particular, modern virtio-pci keeps enabled queues active until the device is reset.  Reset the device before deleting the virtqueues so it can no longer access the vring memory when that memory is released. This also covers probe failures after DRIVER_OK, which unwind through virtsnd_remove().",
                                "cve_priority": "low",
                                "cve_public_date": "2026-10-06 09:18:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-97558",
                                "url": "https://ubuntu.com/security/CVE-2026-97558",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  smb: client: fix cifsFileInfo reference leak in deferred close  When cifs_close() defers a close, it hands the cifsFileInfo reference of the closing struct file to the queued work. Each execution of smb2_deferred_work_close() drops one such reference.  deferred_close_scheduled can be false while the work is pending: the workqueue clears PENDING when the callback starts to run, before the callback clears the flag under deferred_lock. A close in that interval requeues the running work, and the callback then clears the flag, leaving the requeued work pending with the flag down. A later cifs_open() can reuse the handle and its cifs_close() reaches the same branch: queue_delayed_work() fails because the work is still pending, but cifs_close() returns without dropping the closing file's reference. The cifsFileInfo count stays pinned and its tlink, dentry and server handle are leaked.  Check the return value and hand off the reference only when work was actually queued. Otherwise, use the shared _cifsFileInfo_put(), like the mod_delayed_work() branch above: the pending execution already owns its reference.  This issue was found by an in-house static analysis tool.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-09-25 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-97616",
                                "url": "https://ubuntu.com/security/CVE-2026-97616",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net/sched: act_api: release all action references on NEWACTION failure  When a batched RTM_NEWACTION request replaces an existing action, tcf_idr_check_alloc() takes a temporary reference on it. If a later action fails to initialize, tcf_action_destroy() uses strict release semantics to clean up the actions initialized so far. For an action bound to a filter, the strict check returns -EPERM without dropping the temporary reference.  This error also makes tcf_action_destroy() return before releasing subsequent entries. Any new action initialized between the bound action and the failing entry is leaked together with its reserved IDR slot, preventing reuse of its index.  Use tcf_idr_release() to drop each reference held by the batch without rejecting bound actions. This allows cleanup to continue through all initialized entries and preserves the module reference release when an action is destroyed. Explicit action deletion and flushing retain their separate bind-count checks.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-09-25 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-97939",
                                "url": "https://ubuntu.com/security/CVE-2026-97939",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ipmr: account multicast table and route memory  A netadmin in a user+net namespace can create many IPv4 and IPv6 multicast routing tables with MRT_TABLE and MRT6_TABLE. Each unseen id allocates an mr_table via the shared mr_table_alloc(), links it into the per-net list, and leaves it until netns teardown. Those objects were not charged to memcg, so the host unreclaimable slab grows with the table count.  Account mr_table allocations with GFP_KERNEL_ACCOUNT and mark the IPv4/IPv6 MFC caches SLAB_ACCOUNT. This matches the established handling of IP addresses, routes and alternate interface names.  Unresolved MFC entries are still allocated from softIRQ with GFP_ATOMIC and are not charged. They expire after 10 seconds and are bounded by the socket receive queue; see commit 0079ad8e8dc3 (\"ipmr: remove hard code cache_resolve_queue_len limit\").",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-09-25 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-89837",
                                "url": "https://ubuntu.com/security/CVE-2026-89837",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  f2fs: fix dentry folio leak in find_in_level  find_in_level() gets a dentry folio with f2fs_find_data_folio() before calling find_in_block().  If find_in_block() returns an error, the function stores the error in res_folio and breaks out of the loop without dropping the dentry folio.  This leaks the folio reference on the find_in_block() error path.  Drop the dentry folio before returning the error to the caller.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-09-16 11:16:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-89838",
                                "url": "https://ubuntu.com/security/CVE-2026-89838",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  f2fs: limit recovery filename logging to stored length  F2FS stores recovery filenames as a length plus a fixed-size i_name buffer.  The buffer is not NUL-terminated, but recover_inode() and recover_dentry() print it with %s.  For a 255-byte filename, recovery logging can read past i_name into the following raw inode fields.  Print the name with a precision bounded by i_namelen and F2FS_NAME_LEN.",
                                "cve_priority": "negligible",
                                "cve_public_date": "2026-09-16 11:16:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-97530",
                                "url": "https://ubuntu.com/security/CVE-2026-97530",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  scsi: qla2xxx: Fix soft lockup polling continuation IOCB signature  qla27xx_copy_multiple_pkt() and qla27xx_copy_fpin_pkt() poll rsp_q->ring_ptr->signature for RESPONSE_PROCESSED (0xDEADDEAD) to decide whether the next continuation IOCB has arrived, spinning on cpu_relax() without advancing the ring or decrementing the entry count while it has not. response_t::signature lives at byte offset 60, but a continuation IOCB (sts_cont_entry_t / struct sts_cont_entry_ext) carries raw FC frame payload at that offset (data[56..59]). A received frame whose payload bytes happen to equal 0xDEADDEAD is therefore misread as \"not yet arrived\", and the loop spins forever in interrupt/DPC context, causing a CPU soft lockup.  The poll is also unnecessary: callers of qla27xx_copy_multiple_pkt() (PT_LS4_UNSOL and the NVMe purls path) already gate on qla_chk_cont_iocb_avail(), which guarantees all entry_count IOCBs are present before copying begins. The sibling helper __qla_copy_purex_to_buffer() already drops the signature poll and relies on the entry_type == STATUS_CONT_TYPE guard instead.  Remove the signature busy-wait from both helpers, keeping the entry_type guard, and gate the FPIN path with qla_chk_cont_iocb_avail() so it defers and re-processes on the next interrupt once all continuation IOCBs have arrived, mirroring the ELS_AUTH_ELS and PT_LS4_UNSOL arms. With this the signature field is never read on a continuation IOCB, eliminating the payload-aliasing lockup.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-09-25 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98386",
                                "url": "https://ubuntu.com/security/CVE-2026-98386",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  scsi: qla2xxx: Use memset_io() to clear QLAFX00 request ring slot  For QLAFX00 the request ring is ioremapped device I/O memory (ha->iobase + req_que_off), not DMA-coherent RAM, which is why the rest of the FX00 path accesses it through memcpy_toio() and the wrt_reg_* helpers. __qla2x00_alloc_iocbs() however zeroed the producer slot with a plain memset(). On architectures such as ARM64 a regular memset() may emit unaligned or block-zeroing instructions (e.g. DC ZVA) that are invalid on Device memory, leading to a synchronous external abort.  Use memset_io() to clear the slot for QLAFX00, matching the I/O accessors used elsewhere on this ring. Other adapters keep the plain memset() on their DMA-coherent rings. The zero-fill is retained for FX00 because its IOCB builders (e.g. qlafx00_fxdisc_iocb()) copy only part of the entry and rely on the unused tail being pre-zeroed.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-14 14:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-89848",
                                "url": "https://ubuntu.com/security/CVE-2026-89848",
                                "cve_description": "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_work, and qla_do_work() -> qla24xx_process_response_queue() dereferences the now-freed rsp->req (LOGINOUT/CT/ELS entries and the status path), a use-after-free.  The cancel_work_sync() added for the qpair teardown lives in the response free path, which runs after the request queue is already freed, so it does not protect rsp->req.  Release the response-queue interrupt and flush qpair->q_work before deleting the request queue, so no late completion can reach the freed request queue. Clearing have_irq makes the subsequent qla25xx_free_rsp_que() skip its free_irq(), and the firmware queue-delete order (request then response) is preserved; the request-delete mailbox completes on the default vector and is unaffected by dropping the qpair response interrupt early.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-09-16 11:16:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-97532",
                                "url": "https://ubuntu.com/security/CVE-2026-97532",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  scsi: qla2xxx: Null out freed pointers in qla2x00_mem_alloc() error path  When qla2x00_mem_alloc() fails, qla2x00_probe_one() jumps to probe_hw_failed and calls qla2x00_mem_free(). Several error labels in qla2x00_mem_alloc() freed adapter members (elsrej.c, purex_dma_pool, flt, sfp_data, loop_id_map, async_pd, sf_init_cb, ex_init_cb, npiv_info) but left the pointers dangling. qla2x00_mem_free() then freed them a second time. Worse, for the dma_pool members it issued dma_pool_free(ha->s_dma_pool, ...) after s_dma_pool had already been destroyed and set to NULL at fail_s_dma_pool, dereferencing a NULL pool.  Clear each freed pointer (and its DMA handle) in the error labels so the subsequent qla2x00_mem_free() skips them.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-09-25 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-89877",
                                "url": "https://ubuntu.com/security/CVE-2026-89877",
                                "cve_description": "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 existing MMIO mapping error path to remove the device from saa7164_devlist and decrement the device count before returning.  Also release BAR0 if it was successfully requested but the BAR2 request fails.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-09-16 11:16:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-93239",
                                "url": "https://ubuntu.com/security/CVE-2026-93239",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  arm64: mm: Fix the lockless page-table walk in show_pte()  show_pte() walks page tables locklessly and can run with interrupts enabled. A concurrent teardown can free a table page while it is being walked. It can also clear a parent entry after show_pte() checked it; the regular pXd_offset() helpers then reread the cleared entry and can derive a bogus lower-level pointer and fault again.  Use the lockless offset helpers with the saved parent entries, as gup_fast() does, and pass the saved PMD to pte_offset_map().  For task page tables, arm64 selects MMU_GATHER_RCU_TABLE_FREE. Disable local interrupts around the walk to hold off RCU-deferred table frees and block the tlb_remove_table_sync_one() IPI until the walk is finished.  Place the IRQ guard after the header print. This does not make the output a consistent snapshot, but prevents the task page-table walk from dereferencing a released table page or deriving a pointer from a different parent value.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-09-24 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-90023",
                                "url": "https://ubuntu.com/security/CVE-2026-90023",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  usb: gadget: f_mass_storage: fix null pointer dereference in fsg_common_set_num_buffers()  Previously fsg_num_buffers_validate() was removed as it was not necessary due to Kconfig setting the limits for n from 2 to 256 with default as 2. However, setting the page content in such a way that kstrtou8() reflects n value as either 0 or 1 bypasses these restrictions leading to a null pointer dereference if n is 0. Fix this by adding a check for n < 2 and returning -EINVAL if n is either 0 or 1 consistent with Kconfig logic.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-09-16 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-93200",
                                "url": "https://ubuntu.com/security/CVE-2026-93200",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  i3c: master: Fix use-after-free of master->this  sysfs attribute callbacks for the master controller device dereference master->this.  However, master->this is freed in i3c_master_detach_free_devs() before the master device itself is released.  As a result, sysfs accesses can dereference a freed master->this pointer, leading to a use-after-free.  Keep master->this alive until i3c_masterdev_release(), which is called after the master device and its sysfs state are being torn down. Do not free master->this as part of the normal device detach path.  On the error path in i3c_master_set_info(), reset master->this and bus.cur_master to NULL before freeing the allocated device.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-09-17 17:18:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-93199",
                                "url": "https://ubuntu.com/security/CVE-2026-93199",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  i3c: master: Do not treat master device as a duplicate target  i3c_master_search_i3c_dev_duplicate() searches the bus for another I3C device with the same PID as the reference device.  The search can match master->this, causing the controller itself to be returned as a duplicate.  Since the controller is not a target device, it cannot be a duplicate of one.  Exclude master->this from matching so that the function only returns real duplicate target devices.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-09-17 17:18:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-89441",
                                "url": "https://ubuntu.com/security/CVE-2026-89441",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  mmc: via-sdmmc: cancel card-detect work on remove  Disabling the device interrupt and freeing the IRQ prevents new card-detect work from being queued, but carddet_work already queued by the handler can still run after via_sd_remove() returns. via_sdc_card_detect() recovers the host through container_of() and dereferences its MMIO base; once remove() returns the host can be freed, so that work would touch freed memory.  Cancel carddet_work after freeing the IRQ and before cancelling finish_bh_work, which the card-detect handler can also queue. carddet_work can re-enable the interrupt through via_reset_pcictrl(); mask it again afterwards.  This issue was found by an in-house static analysis tool and confirmed by manual code review.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-09-11 20:19:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-89465",
                                "url": "https://ubuntu.com/security/CVE-2026-89465",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  power: supply: rt9455: quiesce delayed work before teardown  The threaded IRQ handler can queue pwr_rdy_work, max_charging_time_work and batt_presence_work.  pwr_rdy_work and batt_presence_work can also queue max_charging_time_work, while batt_presence_work can requeue itself.  rt9455_remove() cancels max_charging_time_work before batt_presence_work.  The latter can therefore queue max_charging_time_work after it has already been cancelled:    rt9455_remove()                   workqueue     cancel pwr_rdy_work     cancel max_charging_time_work                                       batt_presence_work queues                                         max_charging_time_work     cancel batt_presence_work     return     devres frees rt9455_info                                       max_charging_time_work dereferences                                         rt9455_info  The IRQ also remains registered until devres cleanup and can queue more work after any of the cancellation calls.  If rt9455_hw_init() fails after the IRQ has been requested, probe returns without cancelling work that may already have been queued.  A pending callback can then access rt9455_info after it has been freed.  Register rt9455_cancel_all_delayed_works() through devm_add_action_or_reset() right after devm_power_supply_register(). devres invokes the action in reverse registration order, after the managed IRQ has been freed and before rt9455_info is released, so the delayed works are drained in both rt9455_remove() and the probe error path.  Cancel pwr_rdy_work and batt_presence_work before max_charging_time_work because both can queue the latter.  This issue was found by an in-house static analysis tool.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-09-11 20:19:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-93231",
                                "url": "https://ubuntu.com/security/CVE-2026-93231",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  lockd: fix swapped arguments in nlmsvc_match_ip()  When releasing locks by server IP address via /proc/fs/nfsd/unlock_ip, nlmsvc_unlock_all_by_ip() calls nlm_traverse_files() with the server sockaddr as the opaque @data argument:  \tnlm_traverse_files(server_addr, nlmsvc_match_ip, NULL);  The match callback is later invoked from nlm_traverse_locks() as:  \tmatch(lockhost, host);  where the first argument is the nlm_host that owns the lock, and the second argument is the @data that was originally passed down (here the server sockaddr).  This is the convention every other match callback relies on (nlmsvc_mark_host(), nlmsvc_same_host(), nlmsvc_is_client()): arg1 is the real nlm_host, arg2 is the caller-supplied reference value.  nlmsvc_match_ip() has had these two arguments reversed ever since the unlock-by-IP feature was introduced in commit 4373ea84c84d (\"lockd: unlock lockd locks associated with a given server ip\"):  \treturn rpc_cmp_addr(nlm_srcaddr(host), datap);  Here @host is actually the server sockaddr, so nlm_srcaddr(host) dereferences a struct sockaddr as a struct nlm_host and reads garbage at the offset of h_srcaddr; meanwhile @datap is actually the lock owner's nlm_host but is compared as a sockaddr.  As a result the comparison practically never matches and locks are not released for the requested IP.  Swap the arguments so the lock owner's source address is compared against the requested server address:  \treturn rpc_cmp_addr(nlm_srcaddr(datap), (struct sockaddr *)host);  [ cel: fix the misleading typedef parameter names too ]",
                                "cve_priority": "low",
                                "cve_public_date": "2026-09-24 16:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-89552",
                                "url": "https://ubuntu.com/security/CVE-2026-89552",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  params: fix charp corruption on allocation failure  param_set_charp() stores charp parameters in allocated memory after slab is available, and releases the previous value when the parameter is updated.  The previous value is released before the replacement allocation succeeds. If kmalloc_parameter() fails, the setter returns -ENOMEM with the parameter left as NULL.  Failing zswap's compressor update before zswap is initialized can later trigger:    BUG: kernel NULL pointer dereference, address: 0000000000000000   RIP: 0010:strcmp+0x10/0x30   Call Trace:     zswap_setup+0x3b1/0x490     zswap_enabled_param_set+0x5b/0xa0     param_attr_store+0x93/0xe0     module_attr_store+0x1c/0x30     kernfs_fop_write_iter+0x116/0x1f0  Allocate and copy the replacement first, then replace the parameter value only after allocation succeeds.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-09-11 20:19:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-89640",
                                "url": "https://ubuntu.com/security/CVE-2026-89640",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  cifs: fix loff_t underflow in cifs_remap_file_range() when len == 0  With len == 0 (clone to EOF), the effective length is computed as:      len = src_inode->i_size - off;  If off > i_size, this is a negative loff_t, corrupting the ByteCount in the FSCTL_DUPLICATE_EXTENTS_TO_FILE request and inverting the range in filemap_write_and_wait_range().  The existing off >= i_size check fires only after the ioctl has already been sent.  Snapshot i_size_read() once for both the bounds check and the length calculation, eliminating the TOCTOU and 32-bit torn-read risk.  Reject off > src_size with -EINVAL.  Treat off == src_size as a no-op, consistent with __generic_remap_file_range_prep().",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-09-11 20:19:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-89672",
                                "url": "https://ubuntu.com/security/CVE-2026-89672",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  nfsd: gate nfs2 setacl by argp->mask  The NFSACL v2 SETACL path shares the decoder convention used by its v3 sibling: nfsaclsvc_decode_setaclargs() fills in argp->acl_access only when NFS_ACL is set in the request mask and argp->acl_default only when NFS_DFACL is set, leaving the other pointer NULL because the argument buffer is zeroed up to pc_argzero before decode.  nfsacld_proc_setacl() then hands both pointers to set_posix_acl() unconditionally. set_posix_acl(idmap, dentry, type, NULL) is the VFS \"remove this ACL type\" operation, so an omitted arm is indistinguishable from an explicit request to delete that ACL. A SETACL carrying only NFS_ACL silently strips the directory's default ACL; mask=0 strips both.  This is the same defect just fixed in nfsd3_proc_setacl(); apply the same remedy. Gate each set_posix_acl() call on its mask bit and initialize error to 0 so that a request with neither bit set leaves the on-disk ACLs untouched and returns success. The out_drop_lock path and the unconditional posix_acl_release() in nfsaclsvc_release_setacl() already tolerate the skipped arms.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-09-11 20:19:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-89685",
                                "url": "https://ubuntu.com/security/CVE-2026-89685",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  nfsd: fix clock domain mismatch in clients_still_reclaiming()  clients_still_reclaiming() computes a deadline from nn->boot_time (CLOCK_REALTIME, ~1.7 billion) but compares it against ktime_get_boottime_seconds() (CLOCK_BOOTTIME, seconds since boot). The comparison is always false — it would take ~54 years of uptime for BOOTTIME to exceed the REALTIME-derived deadline.  This means any client can hold the server in grace indefinitely by sending CLAIM_PREVIOUS OPEN requests, blocking all non-reclaim operations for all other clients.  Add boot_time_bt (CLOCK_BOOTTIME) alongside the existing boot_time and use it for the deadline computation. boot_time (CLOCK_REALTIME) is preserved for its cl_boot clientid-nonce role.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-09-11 20:19:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-89707",
                                "url": "https://ubuntu.com/security/CVE-2026-89707",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  nfsd: release path refs on follow_down() error  nfsd_cross_mnt() initializes a local struct path with mntget() and dget() before calling follow_down(). On a negative return the error arm jumps to out without releasing those references:      err = follow_down(&path, follow_flags);     if (err < 0)             goto out;  follow_down() never drops the caller's entry-time refs on any error sub-case; for example a pre-cross d_manage() failure leaves path untouched, so the mntget()/dget() taken on entry survive the call.  Every other early-exit arm in nfsd_cross_mnt() (other-namespace return, IS_ERR(exp2), and the success tail after the swap) already calls path_put(&path); the err < 0 arm is the lone omission. The leak inflates mnt_count and d_count on each failed cross-mount, blocking umount and pinning dentries against the shrinker, and is reachable by any authenticated NFS client through nfsd_lookup_dentry or the NFSv4 READDIR encode path.  Fix by calling path_put(&path) before the goto out in the err < 0 arm so the entry-time refs are released on all follow_down() error returns.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-09-11 20:19:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-89719",
                                "url": "https://ubuntu.com/security/CVE-2026-89719",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  zram: fix out-of-bounds access in read_block_state()  read_block_state() calculates nr_pages before taking dev_lock.  If the device is reset and reinitialized with a smaller disksize before lock acquisition, nr_pages still describes the old table.  The subsequent loop can then call slot_lock() past the end of the newly allocated table.  Read disksize after acquiring dev_lock and checking that the device is initialized.  The read lock then keeps the table and its bound stable for the duration of the scan.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-09-11 20:20:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-89763",
                                "url": "https://ubuntu.com/security/CVE-2026-89763",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  KEYS: trusted: Fix TPM teardown ordering  trusted_tpm_exit() drops the TPM chip reference and frees the digest array before unregistering the trusted key type. key_type_lookup() holds key_types_sem for reading until the key operation finishes, while unregister_key_type() takes it for writing. It therefore provides the synchronization point that must precede backend teardown.  The current order permits this interleaving:    CPU 0                              CPU 1   trusted_tpm_exit()                 key_type_lookup(\"trusted\")     put_device(&chip->dev)             trusted_tpm_seal()     kfree(digests)                       pcrlock()     unregister_key_type()                  tpm_pcr_extend(..., digests)  CPU 1 can consequently dereference the freed digest array. The chip can also be released before callbacks stop using it.  KASAN reported:    BUG: KASAN: slab-use-after-free in tpm_pcr_extend+0x1f0/0x200   Read of size 2 at addr ffff88810872d000 by task poc/89   Call Trace:     tpm_pcr_extend+0x1f0/0x200     pcrlock+0x42/0x70 [trusted]     trusted_tpm_seal+0x1b6/0x570 [trusted]     trusted_instantiate+0x293/0x340 [trusted]     __key_instantiate_and_link+0xb2/0x2b0     __key_create_or_update+0x61e/0xb50     __do_sys_add_key+0x1b8/0x310   Allocated by task 88:     __kmalloc_noprof+0x1a7/0x490     do_one_initcall+0xa1/0x390     do_init_module+0x2df/0x840   Freed by task 90:     kfree+0x131/0x3c0     trusted_tpm_exit+0x59/0xa0 [trusted]     __do_sys_delete_module+0x346/0x510  Move unregister_key_type() before releasing either resource. This stops new lookups and waits for in-flight key operations to finish before the backend state is destroyed.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-09-11 20:20:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-80851",
                                "url": "https://ubuntu.com/security/CVE-2026-80851",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  gtp: serialize PDP context updates  PDP contexts can be deleted through GTP_CMD_DELPDP or while the GTP network device is being unregistered. The latter is serialized by RTNL, but the generic-netlink delete path only holds RCU.  Running both paths concurrently can therefore make both paths delete the same PDP context. The issue was found through static analysis and reproduced on a KASAN-enabled kernel by a simple two-thread program racing GTP_CMD_DELPDP against RTM_DELLINK:    Oops: general protection fault, probably for non-canonical address   KASAN: maybe wild-memory-access in range          [0xdead000000000120-0xdead000000000127]   RIP: gtp_genl_del_pdp+0x1c1/0x420 [gtp]   RBP: dead000000000122  The second deletion dereferenced the poisoned hlist pprev pointer.  Serialize gtp_pdp_add(), gtp_genl_del_pdp(), and gtp_dellink() with a shared mutex. Keep the mutex held until the final use of a PDP context in the NEWPDP path, and keep the RCU read-side section around the complete PDP context use in the DELPDP path.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-09-04 16:18:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-80861",
                                "url": "https://ubuntu.com/security/CVE-2026-80861",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  usb: xhci: bail out of setup if the controller is inaccessible  xhci_gen_setup() locates the operational registers using the capability length read from the very first register:  \txhci->op_regs = hcd->regs + \t\tHC_LENGTH(readl(&xhci->cap_regs->hc_capbase));  If the controller is dead or has dropped off the bus, that read returns ~0, HC_LENGTH() truncates it to 0xff, and op_regs ends up 0xff bytes past the page-aligned MMIO base, i.e. unaligned. The first access through it, xhci_halt() -> xhci_handshake() reading op_regs->status, is then an unaligned readl() on device memory. arm64 faults on unaligned device accesses, so instead of xhci_handshake() catching the all-ones value and returning -ENODEV, setup oopses:    xhci-pci-renesas 0005:08:00.0: Unable to change power state from D3cold to D0, device inaccessible   xhci-pci-renesas 0005:08:00.0: xHCI Host Controller   xhci-pci-renesas 0005:08:00.0: new USB bus registered, assigned bus number 1   Unable to handle kernel paging request at virtual address ffff80030a770103     ESR = 0x0000000096000021     FSC = 0x21: alignment fault   Internal error: Oops: 0000000096000021 [#1]  SMP   pc : xhci_halt [xhci_hcd]   Call trace:    xhci_halt    xhci_gen_setup    xhci_pci_setup    usb_add_hcd    usb_hcd_pci_probe    xhci_pci_common_probe    xhci_pci_renesas_probe  This was hit with a Renesas uPD720201 that failed to power up (\"Unable to change power state from D3cold to D0, device inaccessible\") yet still reached the HCD probe path.  Read the capability register once, and if it reads back the all-ones value (as xhci_handshake() and xhci_reset() already test for), abort setup with -ENODEV before op_regs is derived from it. Reading it once also avoids re-reading a register that may change under a concurrent hot-removal.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-09-04 16:18:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98377",
                                "url": "https://ubuntu.com/security/CVE-2026-98377",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  vlan: require the MAC header to be present in __vlan_insert_inner_tag()  __vlan_insert_inner_tag() only guarantees head room via skb_cow_head(), never that mac_len bytes of MAC header are present.  Its ETH_HLEN wrappers - __vlan_insert_tag() under skb_vlan_push(), and vlan_insert_tag() under validate_xmit_vlan() on the generic transmit path - therefore rewrite the first 16 bytes at skb->data: a 12-byte memmove plus two 2-byte stores at +12 and +14.  No caller supplies the bound, while the pop helpers use skb_ensure_writable()/pskb_may_pull().  An IFF_TUN device has hard_header_len == 0, so packet_snd() accepts a one-byte AF_PACKET/SOCK_RAW frame.  The first vlan push only sets a hwaccel tag; the next - clsact \"action vlan push\" or bpf_skb_vlan_push() - enters the helper with skb->len still 1.  The head comes from skbuff_small_head without __GFP_ZERO, so each push drags bytes from beyond skb->tail into the frame.  After three the one-byte send leaves as 13 bytes carrying 11 bytes of uninitialised slab:    0000: 5a b3 62 12 80 88 ff ff 00 b3 62 12 81            `------------------------------'   only 0x5a was sent; the rest is slab, here the top 56 bits of a   linear-map address  Require the MAC header the helper rewrites to be present, so such a frame is dropped rather than transmitted.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-09 08:16:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98170",
                                "url": "https://ubuntu.com/security/CVE-2026-98170",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  smb: client: fix OOB struct field reads in move_smb2_ea_to_cifs()  In move_smb2_ea_to_cifs(), the while (src_size > 0) loop condition is insufficient. It allows iteration to continue even if the remaining src_size is too small to contain a complete smb2_ea_info structure. Consequently, reads of ea_name_length and ea_value_length can occur out-of-bounds.  Fix this by ensuring src_size >= sizeof(*src) before attempting to read any structure fields. Additionally, reject any next_entry_offset that is smaller than sizeof(*src) or that would advance the pointer beyond the available buffer.  Note that for calls where the server returns a malformed EA list, the error returned to userspace changes from -ENODATA (getxattr) or -ERANGE (listxattr) to -EIO. This correctly signals a server protocol error rather than misleadingly indicating \"attribute not present\" or \"output buffer too small\".",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-06 09:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98171",
                                "url": "https://ubuntu.com/security/CVE-2026-98171",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  smb: client: fix next_buffer UAF and NextCommand bounds in compound PDUs  Fix several related bounds checking and pointer lifecycle issues in receive_encrypted_standard()'s handling of compound encrypted frames:  - Clear next_buffer after assigning it to server->bigbuf. A stale   next_buffer pointer can lead to a use-after-free on subsequent   error paths. - Update pdu_length to the decrypted plaintext size (buf_size). Using   the pre-decryption length allows NextCommand to point into stale   ciphertext residue. - Reject next_cmd values smaller than MID_HEADER_SIZE(server). - Fix an integer overflow in the upper bound check by verifying   pdu_length - next_cmd < MID_HEADER_SIZE(server), ensuring the   trailing slice is large enough for a header.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-10-06 09:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98169",
                                "url": "https://ubuntu.com/security/CVE-2026-98169",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  smb: client: fix potential OOB read in smb3_enum_snapshots()  If snapshot_array_size is smaller than GMT_TOKEN_SIZE, smb3_enum_snapshots() sets ret_data_len to sizeof(struct smb_snapshot_array) without verifying the actual length of the server's reply.  Because SMB2_ioctl() places no lower bound on the server-supplied OutputCount and allocates retbuf to exactly that length, a short reply results in ret_data_len exceeding the size of retbuf. The subsequent copy_to_user() then reads past the end of retbuf, leaking adjacent slab memory to userspace.  The subsequent clamp check is ineffective as it only reduces ret_data_len.  Fix this by rejecting replies shorter than sizeof(struct smb_snapshot_array) with -EIO. Note that the bound is set to the 12-byte struct size rather than the 16-byte MIN_SNAPSHOT_ARRAY_SIZE defined in MS-SMB2 3.3.5.15.1, because 12 bytes is exactly what copy_to_user() attempts to read.",
                                "cve_priority": "negligible",
                                "cve_public_date": "2026-10-06 09:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-98193",
                                "url": "https://ubuntu.com/security/CVE-2026-98193",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: libipw: reject TKIP frames without a full MIC  libipw_michael_mic_verify() assumes that an skb contains an eight-byte Michael MIC. A short TKIP frame makes the unsigned payload length wrap, causing michael_mic() to read past the skb.  Check that the MIC is present before verifying it, and use the existing MICHAEL_MIC_LEN constant for all MIC lengths in the verifier.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-10-06 09:18:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-97555",
                                "url": "https://ubuntu.com/security/CVE-2026-97555",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  smb: client: fix heap overflow in DACL owner/group rewrite  When id_mode_to_cifs_acl rewrites an existing DACL, it allocates a buffer sized according to the on-disk DACL length reported by dacl_ptr->size. However, replace_sids_and_copy_aces may rewrite each ACE with a new owner/group SID obtained from the cifs.idmap upcall. Those SIDs can have up to SID_MAX_SUB_AUTHORITIES (15) sub-authorities, making each ACE up to 76 bytes (sizeof(struct smb_ace)).  If the original DACL contains short SIDs (e.g., 1 sub-authority) while the replacement SIDs are long, the rewritten ACEs overflow the allocation.  Fix this by always budgeting for worst-case SID expansion: allocate sizeof(struct smb_acl) plus num_aces * sizeof(struct smb_ace), which covers the smb_acl header and room for every ACE at maximum SID size. This replaces the previous split logic that used dacl_ptr->size for cifsacl mounts but num_aces * sizeof(struct smb_ace) for mode_from_sid mounts: both paths can trigger the same rewrite and need the same headroom.  KASAN reports this as:   BUG: KASAN: slab-out-of-bounds in build_sec_desc+0x1e8a/0x2680 [cifs]   Write of size 4 at addr ffff8881a5e25374 by task chown/5298   ...   The buggy address is located 0 bytes to the right of    allocated 884-byte region [ffff8881a5e25000, ffff8881a5e25374)",
                                "cve_priority": "high",
                                "cve_public_date": "2026-09-25 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-97557",
                                "url": "https://ubuntu.com/security/CVE-2026-97557",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  smb: client: avoid leaking refcount in cifs_queue_oplock_break()  cifs_queue_oplock_break() unconditionally takes a reference on the target file before queueing cifs_oplock_break(). Only that work item decreases the reference counter again.  If another oplock break arrives while that work is still queued, queue_work() will return false and not queue this second work item. As a result, we will never reach the point to drop the file reference again and are leaking this reference. This can be triggered when interacting with a slow-responding server.  As a result, later unmount operations for this file system will fail with    BUG: Dentry ... still in use (1) [unmount of cifs cifs]   VFS: Busy inodes after unmount of cifs (cifs)   kernel BUG at fs/super.c:777!  Fix this by only incrementing the reference count if the work has been queued successfully. Taking it after queue_work() is safe because all three callers hold tcon->open_file_lock across the call and _cifsFileInfo_put() decrements under that same lock, so a worker that starts the handler in the window cannot drop the reference before it has been taken.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-09-25 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-97564",
                                "url": "https://ubuntu.com/security/CVE-2026-97564",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  smb: client: reject userspace cifs.idmap descriptions  cifs.idmap key descriptions carry authority-bearing fields (owner and group SIDs and uid/gid values in \"os:\"/\"gs:\"/\"oi:\"/\"gi:\" form) that the cifs.idmap upcall helper treats as kernel-originating inputs.  Unlike its sibling cifs.spnego, the cifs.idmap key type has no vet_description hook, so userspace can create keys of this type through request_key(2)/add_key(2) and supply those fields without CIFS origin. A request_key(2) call with a non-NULL callout then drives a root usermodehelper upcall (/sbin/request-key -> cifs.idmap) that consumes the unvetted description in root context.  Only accept cifs.idmap descriptions while CIFS is using its private root_cred to request the key.  id_to_sid()/sid_to_id() already run under override_creds(root_cred), so the kernel-originated path is unaffected.  This mirrors commit 3da1fdf4efbc (\"smb: client: reject userspace cifs.spnego descriptions\"), which applied the same restriction to cifs.spnego.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-09-25 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-97615",
                                "url": "https://ubuntu.com/security/CVE-2026-97615",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  net: bridge: use option bits for CFM/MRP frame handlers  CFM and MRP register a global br_frame_type whose hlist_node is linked into the per-bridge frame_type_list when the first MEP/MRP instance is created. Enabling the protocol on multiple bridges therefore inserts the same node into multiple lists. Unregistering it on one bridge then corrupts list state belonging to another.  These handlers can only be installed once per bridge, and they are uncommon. Track their per-bridge enable state with net_bridge option bits, which already live on the Rx hot cache line, and dispatch the matching handler directly from the receive path. Check both bits together first as an unlikely case.  Remove the generic frame_type_list and br_frame_type helpers, which have had no other users since CFM and MRP were added. That shrinks struct net_bridge by 8 bytes and drops the list walk from the fast path. When neither protocol is compiled in, BR_CFM_MRP_OPTS is 0 and the compiler prunes the branch.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-09-25 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-97901",
                                "url": "https://ubuntu.com/security/CVE-2026-97901",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  genetlink: pin family module during policy dump  The generic netlink controller's policy dump keeps pointers to the target family's operation and policy tables in its callback state.  A dump may be split across multiple skbs and remain pending after the initial request.  Netlink pins the module which owns the dump callback, but in this case that is the controller's owner rather than the target family's owner.  The target family can consequently be unregistered and its module unloaded while a policy dump is pending.  Advancing the dump then dereferences policy memory from the unloaded module.  Take a reference to the target family's module when the dump starts. Drop it from the error and done paths.  This matches the lifetime for which the dump context retains the family and policy pointers.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-09-25 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-97908",
                                "url": "https://ubuntu.com/security/CVE-2026-97908",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  Bluetooth: btqcomsmd: destroy RPMsg endpoints before freeing hci_dev  The command and ACL RPMsg endpoints store struct btqcomsmd as their callback private data. The receive callbacks dereference btq->hdev without taking an hci_dev reference.  The current teardown order frees the hci_dev before destroying the RPMsg endpoints in both the hci_register_dev() error path and the driver remove path. If WCNSS delivers data in that window, the endpoint callback can run with an already freed hci_dev and pass it to the Bluetooth core.  For qcom_smd endpoints, rpmsg_destroy_ept() closes the channel and clears the callback under the channel recv_lock. The receive path holds the same lock while invoking the callback, so destroying the endpoints first both prevents new callbacks and serializes with any callback already running.  Destroy the command and ACL endpoints before hci_free_dev(). Keep hci_unregister_dev() first during remove so the HCI core stops issuing operations before the transport endpoints are shut down. In the full registration-error cleanup path, return directly after freeing the hci_dev to avoid falling through to the partial-construction labels and destroying the endpoints twice.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-09-25 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-97925",
                                "url": "https://ubuntu.com/security/CVE-2026-97925",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  tick/broadcast: Plug clockevents replacement race  朱恺乾 reported and decoded the following race condition when a broadcast device is replaced:  CPUA\t\t\t\t\tCPUB  __tick_broadcast_oneshot_control()    bc = tick_broadcast_device.evtdev; \t\t\t\t\ttick_install_broadcast_device(dev)         \t\t\t\tclockevents_exchange_device(cur, dev) \t\t\t\t\t   shutdown(cur); \t\t\t\t\t   detach(cur); \t\t\t\t\t   cur->handler = noop; \t\t\t\t\t   tick_broadcast_device.evtdev = dev;    tick_broadcast_set_event(bc, next_event); <- FAIL: arms a detached device.  If the original broadcast device has a restricted interrupt affinity mask and the last CPU in that mask goes offline then the BUG() in tick_cleanup_dead_cpu() triggers because the clockevent device is not in detached state.  The reason for this is that tick_install_broadcast_device() is not serialized vs. tick broadcast operations.  The obvious cure is to serialize tick_install_broadcast_device() with tick_broadcast_lock against a concurrent tick broadcast operation.  That requires to split clockevents_exchange_device() into two parts, one which does the exchange, shutdown and detach operation and the other which drops the module reference count. This is required because the module reference cannot be dropped while holding tick_broadcast_lock.  Let clockevents_exchange_device() do both operations as before, but let the broadcast device code take the two step approach and do the device exchange under tick_broadcast_lock and drop the module reference count after releasing it.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-09-25 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-93285",
                                "url": "https://ubuntu.com/security/CVE-2026-93285",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  f2fs: embed f2fs_gc_kthread in f2fs_sb_info  Instead of allocating f2fs_gc_kthread dynamically, embed it in f2fs_sb_info. This simplifies lifetime management and prepares for fixing race conditions during teardown.  - __sbi_store\t\t\t- remount|shutdown \t\t\t\t - f2fs_stop_gc_thread  - access sbi->gc_thread \t\t\t\t  - sbi->gc_thread = NULL  - access sbi->gc_thread->f2fs_gc_task",
                                "cve_priority": "low",
                                "cve_public_date": "2026-09-24 17:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-97529",
                                "url": "https://ubuntu.com/security/CVE-2026-97529",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  scsi: qla2xxx: Validate BSG request_len before reading vendor_cmd[]  The FC BSG transport allocates job->request via memdup_user() using the exact user-supplied request_len. For FC_BSG_HST_VENDOR, fc_bsg_host_dispatch() only guarantees request_len covers msgcode and vendor_id; it does not account for the vendor_cmd[] flexible array.  qla2xxx then reads the command selector vendor_cmd[0] and, in several sub-handlers, vendor_cmd[1]/[2] or structures overlaid on the vendor command area without verifying request_len. A caller holding CAP_SYS_RAWIO can submit a short request whose vendor_id matches the host, triggering out-of-bounds heap reads (KASAN-detectable, and able to mis-select a command or panic).  Add a central guard in qla2x00_process_vendor_specific() so the selector is always in bounds, restrict the early vendor_cmd[0] read in qla24xx_bsg_request() to sufficiently long vendor messages, and add request_len checks to the sub-handlers that read further: qla24xx_proc_fcp_prio_cfg_cmd(), qla2x00_process_loopback(), qla84xx_reset(), qla84xx_updatefw(), qla2x00_read_optrom(), qla2x00_update_optrom(), qlafx00_mgmt_cmd() and qla28xx_validate_flash_image().",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-09-25 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-97536",
                                "url": "https://ubuntu.com/security/CVE-2026-97536",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  scsi: qla2xxx: Fix use-after-free of qpair work on queue teardown  The response queue MSI-X handler qla2xxx_msix_rsp_q() schedules qla_do_work() via queue_work(ha->wq, &qpair->q_work). qla_do_work() dereferences the qpair (vha, rsp) and takes qpair->qp_lock.  During teardown, qla2xxx_delete_qpair() deletes the response queue, which calls free_irq() in qla25xx_free_rsp_que(), and then frees the queue and the qpair. free_irq() waits for running hardirq handlers but does not cancel work already placed on ha->wq. A still-pending q_work then runs qla_do_work() against the freed qpair and response queue, causing a use-after-free. This is especially likely during full adapter teardown, where destroy_workqueue(ha->wq) forces pending work to run after the queue pairs have been freed.  Flush the work item with cancel_work_sync() in qla25xx_free_rsp_que() after free_irq() has released the interrupt (so no new work can be queued) and before the response queue and qpair memory are freed (so the flushed handler still sees valid memory). Guard on rsp->qpair and ha->wq to match the INIT_WORK() condition and avoid operating on an uninitialized work_struct.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-09-25 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-97537",
                                "url": "https://ubuntu.com/security/CVE-2026-97537",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  scsi: qla2xxx: Fix queue teardown NULL dma_free and bitmap locking  qla25xx_free_req_que() and qla25xx_free_rsp_que() have two pre-existing bugs exposed on the error path of qla25xx_create_{req,rsp}_que():   1. When dma_alloc_coherent() fails during queue creation, the error     path calls the free function with req->ring / rsp->ring still NULL     (from kzalloc).  The unconditional dma_free_coherent() with a NULL     cpu_addr is undefined behavior and can panic.   2. The free functions clear req_qid_map / rsp_qid_map under vport_lock,     but the create functions protect the same bitmaps with mq_lock.     This provides no mutual exclusion.  Additionally, the create error     path clears the bit and releases mq_lock before calling the free     function, creating a window where another thread can allocate the     same que_id and have its ha->req_q_map entry clobbered by the     subsequent lockless NULL assignment in the free function.  Fix by:   - Guarding dma_free_coherent() with a NULL check on the ring pointer.   - Using mq_lock (the lock held by all creators) in the free functions    to atomically NULL the map entry and clear the bitmap bit.   - Removing the now-redundant clear_bit blocks from the create error    paths since the free functions handle it atomically.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-09-25 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-89859",
                                "url": "https://ubuntu.com/security/CVE-2026-89859",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  scsi: qla2xxx: Zero dport diagnostics buffer to avoid info leak  qla2x00_do_dport_diagnostics() allocates the qla_dport_diag response buffer with kmalloc_obj() (non-zeroing) and, on success, copies the full sizeof(*dd) back to user space via sg_copy_from_buffer(). The inbound sg_copy_to_buffer() only fills as many bytes as the user request payload provides, and qla26xx_dport_diagnostics() zeroes only dd->buf. The options and unused[] fields are therefore copied out uninitialized, leaking kernel heap contents to user space.  Allocate with kzalloc_obj(), matching qla2x00_do_dport_diagnostics_v2().",
                                "cve_priority": "low",
                                "cve_public_date": "2026-09-16 11:16:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-89921",
                                "url": "https://ubuntu.com/security/CVE-2026-89921",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  KVM: s390: Zero initialize data structures for inject_pfault_token  __kvm_inject_pfault_token() only sets .type and .u.ext.ext_params2 of the on-stack struct kvm_s390_irq but the full ext substructure is copied into the cpu local variable on inject. ext_params and pad contain stale stack values.  Interrupt delivery only uses ext_params2, so nothing leaks to the guest, but a host user can use the migration ioctls to get to the data.  Fix by zero-initializing the irq struct. Do the same for the inti data structure.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-09-16 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-89972",
                                "url": "https://ubuntu.com/security/CVE-2026-89972",
                                "cve_description": "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 reference to ns when kfree(ns) runs.  The normal removal path in nvme_ns_remove() correctly calls synchronize_srcu(&ns->head->srcu) after list_del_rcu() to wait for in-progress readers. Add the same grace period in the error path.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-09-16 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-89988",
                                "url": "https://ubuntu.com/security/CVE-2026-89988",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  kprobes: Protect kprobe_blacklist with RCU  __within_kprobe_blacklist() traverses kprobe_blacklist without holding kprobe_mutex. When a module is unloaded, kprobe_remove_area_blacklist() removes blacklist entries and immediately frees them with kfree(). A concurrent call to within_kprobe_blacklist() can therefore dereference freed memory.  Furthermore, within_kprobe_blacklist() can be called in atomic or non-preemptible contexts where the sleeping kprobe_mutex cannot be taken.  Protect kprobe_blacklist with RCU. Use guard(rcu)() and list_for_each_entry_rcu() for traversal, list_add_tail_rcu() for insertions, list_del_rcu() for deletions, and kfree_rcu() to reclaim entries safely after a grace period.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-09-16 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-90002",
                                "url": "https://ubuntu.com/security/CVE-2026-90002",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ftrace: Take trace_array reference before accessing its ftrace_ops  The trace instance files set_ftrace_filter and set_ftrace_notrace was updated to work with specific trace instances (trace_arrays). The issue is that when these files are opened, there is a small race window where it will use the ftrace_ops from the inode->private pointer to get a reference to the trace_array and then take its reference. The problem is that the ftrace_ops itself could be freed. If the rmdir on the instance happens at the same time the set_ftrace_filter file is opened, the rmdir could have also freed the ftrace_ops and referencing it will cause a use-after-free bug and crash the kernel.  Instead, pass in the trace_array as the file private data (NULL for the top level instance), and then pass both the trace_array and the ftrace_ops to the ftrace_regex_open() function. If the trace_array is NULL, then it just uses the ftrace_ops without the need to take its reference (like normal). If the ftrace_ops is NULL, that is only the case for the top level instance and the global_ops can be used.  This allows the trace_array to have its reference incremented before touching the ftrace_ops that could also be freed when the instance is.",
                                "cve_priority": "low",
                                "cve_public_date": "2026-09-16 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-90016",
                                "url": "https://ubuntu.com/security/CVE-2026-90016",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  staging: rtl8723bs: fix OOB read in rtw_restruct_wmm_ie()  rtw_restruct_wmm_ie() scans in_ie for a WMM IE with:  \twhile (i < in_len) { \t\t... \t\tif (i + 5 < in_len && in_ie[i] == 0xDD && ...) { \t\t\t... \t\t\tbreak; \t\t} \t\ti += (in_ie[i + 1] + 2); /* to the next IE element */ \t}  When the \"i + 5 < in_len\" match check fails simply because i is within 5 bytes of the end of the buffer (i.e. no WMM IE was found near the tail of in_ie), execution falls through to \"i += (in_ie[i + 1] + 2)\", which reads in_ie[i + 1]. If i == in_len - 1 at that point, this is a 1-byte out-of-bounds read of an attacker-influenced IE buffer built from association/scan data.  Commit a75281626fc8f (\"staging: rtl8723bs: fix potential out-of-bounds read in rtw_restruct_wmm_ie\") added the \"i + 5 < in_len\" guard to the match condition itself, but did not add an equivalent guard before the fallthrough advance, so the same class of OOB read remained reachable through the non-matching path.  Add an explicit bounds check before advancing to the next IE.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-09-16 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-90029",
                                "url": "https://ubuntu.com/security/CVE-2026-90029",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  usb: storage: realtek_cr: fix use-after-free on disconnect  realtek_cr_destructor() calls timer_delete() before the chip containing the timer is freed. The timer callback may still be running and can rearm itself, resulting in a use-after-free.  Use timer_shutdown_sync() to wait for the callback and prevent further rearming. Do this unconditionally because ss_en may be changed after the timer is armed.  Move timer_setup() into init_realtek_cr() so the timer is initialized before any failure path can invoke the destructor.  Found by static analysis.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-09-16 11:17:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-80947",
                                "url": "https://ubuntu.com/security/CVE-2026-80947",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  wifi: rtl8xxxu: fix use-after-free from rx_urb_wq on stop  rtl8xxxu arms rx_urb_wq from the RX completion path: rtl8xxxu_rx_complete() hands the URB to rtl8xxxu_queue_rx_urb(), which queues it on rx_urb_pending_list and, once the list grows past RTL8XXXU_RX_URB_PENDING_WATER, schedules rx_urb_wq.  The worker rtl8xxxu_rx_urb_work() drains rx_urb_pending_list, recovers priv through container_of, and resubmits each URB through rtl8xxxu_submit_rx_urb(), which anchors it on rx_anchor and dereferences priv->udev.  rtl8xxxu_stop() cancels the sibling work items (c2hcmd_work, ra_watchdog, update_beacon_work) but never cancels rx_urb_wq, so a worker armed during the last burst of RX traffic can run rtl8xxxu_rx_urb_work() after rtl8xxxu_disconnect() has called ieee80211_free_hw(), which frees priv, producing a use-after-free.  The window opens under active RX traffic (pending count above the watermark) followed by a disconnect.  There are two teardown races to close:    * rtl8xxxu_queue_rx_urb() decided whether to enqueue under rx_urb_lock     but called schedule_work() after dropping the lock.  A completion     that observed shutdown == false and released the lock could then call     schedule_work() after rtl8xxxu_stop() had set shutdown and     cancel_work_sync() had already returned, arming the worker to run     after the teardown.  Move schedule_work() under the same !shutdown     branch so the arming decision is atomic with the shutdown check.    * rtl8xxxu_rx_urb_work() anchors every URB it drained back onto     rx_anchor through rtl8xxxu_submit_rx_urb().  A worker still running     when usb_kill_anchored_urbs(&priv->rx_anchor) returned would submit a     URB that escaped the kill.  In rtl8xxxu_stop(), call     cancel_work_sync(&priv->rx_urb_wq) before the kill so the worker is     drained first.  After priv->shutdown is set under rx_urb_lock, completions can no longer queue rx_urb_wq. cancel_work_sync() then drains the last queued or running worker, and the following usb_kill_anchored_urbs() kills the URBs it may have submitted.  rtl8xxxu_disconnect() is covered because ieee80211_unregister_hw() guarantees .stop() runs for a live interface before ieee80211_free_hw() frees priv.  The probe error path needs no cancel: rx_urb_wq is INIT_WORK()'d there but cannot have been scheduled, since no URB is submitted before ieee80211_register_hw() succeeds.  This bug was found by static analysis.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-09-11 20:19:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-89481",
                                "url": "https://ubuntu.com/security/CVE-2026-89481",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  nvme-tcp: fix host memory disclosure on R2T for a read command  nvme_tcp_handle_r2t() does not check the direction of the request the R2T refers to. A malicious controller can send an R2T for a READ and the host will answer it: nvme_tcp_setup_h2c_data_pdu() builds the H2CData header and nvme_tcp_try_send_data() sends the request's data buffer. That buffer is the READ destination, so its contents go to the controller.  The command then completes normally and nothing is logged.  Against a test controller that answers every READ with an R2T, a 4096 byte buffered read returned all 4096 bytes, split over two R2Ts. The pages contained stale kernel data, including an array of struct page pointers.  Reject an R2T for a request that is not a write.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-09-11 20:19:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-89492",
                                "url": "https://ubuntu.com/security/CVE-2026-89492",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ocfs2: validate directory-index entry counts when reading metadata  ocfs2_validate_dx_leaf() and ocfs2_validate_dx_root() check the ECC and signature of an indexed-directory block before it reaches higher-level callers, but neither validator bounds the ocfs2_dx_entry_list counts against the capacity of the block that holds them.  ocfs2_dx_dir_search() then walks  \tfor (i = 0; i < le16_to_cpu(entry_list->de_num_used); i++) \t\tdx_entry = &entry_list->de_entries[i];  over de_num_used entries with no bounds check.  entry_list is either dx_leaf->dl_list (from ocfs2_read_dx_leaf) or, for an inline root, dx_root->dr_entries.  A crafted on-disk image can set de_num_used (and de_count, which is the __counted_by_le() bound of de_entries) to 0xffff and make the walk read far past the end of the 4KB metadata block, giving a slab out-of-bounds read reachable from any path lookup, stat() or open() on an indexed directory once the image is mounted.  Commit 775c17386a6f (\"ocfs2: validate dx_root extent list fields during block read\") already bounds dr_list for the non-inline dx_root, but left the inline dr_entries path and the dx_leaf dl_list unchecked.  Add the same read-time validation for both entry lists: de_count must equal the capacity of the block (ocfs2_dx_entries_per_leaf()/per_root()) and de_num_used must not exceed de_count, rejecting corrupted metadata with -EFSCORRUPTED before ocfs2_dx_dir_search() can walk an out-of-range entry array.  de_count is always written as exactly the block capacity when a leaf or inline root is formatted, so the equality check does not reject any valid image.  Found by 0sec automated security-research tooling (https://0sec.ai).",
                                "cve_priority": "high",
                                "cve_public_date": "2026-09-11 20:19:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-89553",
                                "url": "https://ubuntu.com/security/CVE-2026-89553",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  nouveau/gem: reserve the bo in the info ioctl around the vma lookup  In the non-uvmm path, there could be a race between the info lookup finding the vma, and the gem close path closing the vma leading to a use-after-free.  Spotted with the help of Opus 4.6.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-09-11 20:19:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-89625",
                                "url": "https://ubuntu.com/security/CVE-2026-89625",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  HID: sony: fix UAF of ghl_poke_timer / ghl_urb at driver unbind  For GHL (Guitar Hero Live) dongles, sony_probe() arms a periodic timer: ghl_magic_poke() (the timer callback) submits sc->ghl_urb, and the URB completion ghl_magic_poke_cb() re-arms the timer with mod_timer().  sony_remove() drained the timer with timer_delete_sync() and then freed the URB with usb_free_urb():  \ttimer_delete_sync(&sc->ghl_poke_timer); \tusb_free_urb(sc->ghl_urb);  timer_delete_sync() does not block re-arming, and while the URB is in flight the timer is not pending, so the sync delete is a no-op. A URB completion that runs after the delete re-arms the timer, and usb_free_urb() only drops a reference -- it does not kill an in-flight URB. sc is allocated with devm_kzalloc() and freed once sony_remove() returns, so the re-armed ghl_poke_timer (embedded in sc) then fires on freed memory, a use-after-free from timer softirq. This is a disconnect/rmmod race.  Poison the URB first, then shut the timer down, before freeing the URB. usb_poison_urb() kills any in-flight URB and permanently rejects further submissions, so a poke timer that is still pending cannot re-submit the URB from ghl_magic_poke() in the window before timer_shutdown_sync() runs. usb_kill_urb() would not suffice: it only cancels the in-flight URB and leaves it submittable once it returns, so the pending timer could re-submit it and put a fresh URB in flight over the freed sc. timer_shutdown_sync() then drains any last callback and blocks re-arming. The probe error path is unaffected: it is only reached before the timer is armed.  Reproduced under KASAN on next-20260710 via dummy_hcd + raw-gadget emulation of the GHL PS4 dongle (VID 0x1430 / PID 0x07bb): hid-sony binds and arms the poke timer, the poke URB is held in flight, the driver is unbound (freeing sc), then the URB is released. The completion re-arms the timer on the freed sc, and the re-armed timer fires ~8 s later:    BUG: KASAN: slab-use-after-free in ghl_magic_poke+0x98/0xb0   Read of size 8 at addr ffff88810b02fd50 by task swapper/0/0    ghl_magic_poke+0x98/0xb0    call_timer_fn+0x35/0x2b0    __run_timers+0x69c/0x9a0    run_timer_softirq+0x173/0x2a0   Allocated by task 169:  sony_probe   Freed by task 338:      devres_release_group <- hid_device_remove (sony_remove)  Found by 0sec (https://0sec.ai) using automated source analysis.",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-09-11 20:19:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-89633",
                                "url": "https://ubuntu.com/security/CVE-2026-89633",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  smb: client: fix OOB read/write from unvalidated DataOffset in coalesce_t2()  coalesce_t2() computes data pointers directly from server-supplied DataOffset fields with no validation against buffer bounds:    data_area_of_tgt = (char *)&pSMBt->hdr.Protocol +                      get_unaligned_le16(&pSMBt->t2_rsp.DataOffset);   data_area_of_src = (char *)&pSMBs->hdr.Protocol +                      get_unaligned_le16(&pSMBs->t2_rsp.DataOffset);   data_area_of_tgt += total_in_tgt;   ...   memcpy(data_area_of_tgt, data_area_of_src, total_in_src);  A small DataOffset can push a pointer below the actual byte area, overwriting header fields; a large one can push it past the buffer end, causing out-of-bounds heap reads (source) or writes (target). The BCC overflow guard does not prevent this: BCC reflects how much data is present, while DataOffset controls where in the buffer it starts.  The \"validate target area\" comment present since the function was first written in 2005 was a placeholder that was never implemented.  Add lower- and upper-bound checks for both data pointers before the memcpy, and before any target header fields are modified.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-09-11 20:19:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-89652",
                                "url": "https://ubuntu.com/security/CVE-2026-89652",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  ceph: bound copied dentry name length in NFS export get_name  ceph_get_name() copies the MDS-supplied name into the caller's NAME_MAX-sized buffer with memcpy(name, rinfo->dname, rinfo->dname_len) and then writes name[rinfo->dname_len] = 0, without checking dname_len against NAME_MAX. A malicious or buggy MDS that returns a LOOKUPNAME reply with dname_len > NAME_MAX overflows the buffer. __get_snap_name() copies rde->name / rde->name_len the same unchecked way.  Impact: a malicious or compromised Ceph MDS overflows the NAME_MAX name buffer in a client's NFS-export get_name path, a slab out-of-bounds write reported by KASAN. Reachable when a CephFS mount is re-exported over NFS.  Add ceph_export_copy_name(), which rejects lengths above NAME_MAX with -ENAMETOOLONG before the copy, and use it in both ceph_get_name() and __get_snap_name().",
                                "cve_priority": "critical",
                                "cve_public_date": "2026-09-11 20:19:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-89680",
                                "url": "https://ubuntu.com/security/CVE-2026-89680",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  nfsd: fix nfsd_file leak on inter-server COPY setup failure  When nfsd4_setup_inter_ssc() fails, nfsd4_copy() returns nfserr_offload_denied directly, bypassing the out: label where release_copy_files() would drop the nf_dst reference taken by nfs4_preprocess_stateid_op(). Each failed inter-server COPY leaks one nfsd_file, pinning file/inode/dentry/vfsmount.  Fix by setting status and jumping to out: instead of returning directly.",
                                "cve_priority": "high",
                                "cve_public_date": "2026-09-11 20:19:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-89761",
                                "url": "https://ubuntu.com/security/CVE-2026-89761",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  apparmor: fix out-of-bounds write when null terminating a label vec  aa_vec_unique() null terminates at vec[n - dups] when VEC_FLAG_TERMINATE is passed. If the components are all distinct no duplicates are dropped, dups is 0 and the terminator goes to vec[n], so the caller has to provide room for n + 1 entries.  aa_label_strn_parse() sets up its vector with vec_setup(profile, vec, len, gfp) and then calls aa_vec_unique(vec, len, VEC_FLAG_TERMINATE), but vec_setup() does not reserve the terminator entry. Up to LOCAL_VEC_ENTRIES it uses the local array of LOCAL_VEC_ENTRIES pointers, above that it allocates exactly len pointers. The terminator therefore lands one entry past the end of the local array when len is LOCAL_VEC_ENTRIES, and one entry past the end of the allocation when len is larger.  len comes from the number of \"//&\" separated components in the label name and label_count_strn_entries() does not bound it. An unprivileged task reaches the parse by writing to /proc/self/attr/apparmor/current or through lsm_set_self_attr(2), both of which go through do_setattr(), and the name is parsed before the change_profile permission is checked. The query_label() path behind the securityfs .access file, which is mode 0666, performs no permission check at all. Every component has to resolve to a loaded profile, so a system with policy loaded is required.  The other two VEC_FLAG_TERMINATE users work on a label vec that aa_label_alloc() has already sized with \"+ 1 for null terminator entry on vec\". Reserve the same entry in vec_setup() and DEFINE_VEC(). Passing len + 1 from the caller instead would move len == LOCAL_VEC_ENTRIES out of the local array and into kzalloc().",
                                "cve_priority": "medium",
                                "cve_public_date": "2026-09-11 20:20:00 UTC"
                            },
                            {
                                "cve": "CVE-2026-80852",
                                "url": "https://ubuntu.com/security/CVE-2026-80852",
                                "cve_description": "In the Linux kernel, the following vulnerability has been resolved:  tls: device: fix out-of-bounds write in tls_append_frag()  Found with syzkaller and a local syzbot instance running on top of a netdevsim TLS offload emulation; tls_device.c is otherwise only reachable on a machine with a NIC that implements the offload.  tls_push_data() only checks whether the open record still has room for another frag at the bottom of its loop, and the MSG_MORE early break skips that check.  The record survives to the next syscall with the frag count it already had, and tls_append_frag() does not check either, so with TLS_TX_ZEROCOPY_RO every splice(SPLICE_F_MORE) of a byte or two adds a non-coalescing pipe page and num_frags walks off the end of tls_record_info.frags[MAX_SKB_FRAGS].  Once the record is pushed, tls_push_record() runs the same index over sg_tx_data[MAX_SKB_FRAGS] and the sg_set_page() writes land on the destruct_work that follows it, which the workqueue then calls.  The byte limit is fine because copy drops to 0 and the loop falls through to the same check; the frag count has no such feedback.  Push the record rather than keep a full one open, which is what a plain TCP socket does - tcp_sendmsg_locked() uses tcp_mark_push() and new_segment in both the copy and the MSG_SPLICE_PAGES paths, and tls_sw already sets full_record when the sk_msg ring fills up, MSG_MORE or not.    BUG: KASAN: slab-out-of-bounds in tls_append_frag ( net/tls/tls_device.c:269)   Write of size 8 at addr ffff8881104d1530 by task tls_oob/450    CPU: 2 UID: 0 PID: 450 Comm: tls_oob Not tainted 7.2.0-rc7+ #329 PREEMPT   Call Trace:    <TASK>    dump_stack_lvl (lib/dump_stack.c:94 lib/dump_stack.c:120)    print_report (mm/kasan/report.c:378 mm/kasan/report.c:482)    kasan_report (mm/kasan/report.c:595)    tls_append_frag (net/tls/tls_device.c:269)    tls_push_data (net/tls/tls_device.c:518)    tls_device_sendmsg (net/tls/tls_device.c:583)    inet_sendmsg (net/ipv4/af_inet.c:865)    sock_sendmsg (net/socket.c:775 net/socket.c:790 net/socket.c:813)    splice_to_socket (fs/splice.c:884)    do_splice (fs/splice.c:936 fs/splice.c:1349)    __do_splice (fs/splice.c:1431)    __x64_sys_splice (fs/splice.c:1634 fs/splice.c:1616)    do_syscall_64 (arch/x86/entry/syscall_64.c:63 arch/x86/entry/syscall_64.c:94)    entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:121)    </TASK>  and, once the record is pushed:    UBSAN: array-index-out-of-bounds in net/tls/tls_device.c:300:24   index 18 is out of range for type 'skb_frag_t [17]'   UBSAN: array-index-out-of-bounds in net/tls/tls_device.c:301:41   index 18 is out of range for type 'scatterlist [17]'   UBSAN: array-index-out-of-bounds in net/tls/tls_device.c:302:39   index 18 is out of range for type 'scatterlist [17]'   UBSAN: array-index-out-of-bounds in net/tls/tls_device.c:307:38   index 26 is out of range for type 'scatterlist [17]'    kernel tried to execute NX-protected page - exploit attempt? (uid: 0)   BUG: unable to handle page fault for address: ffffea000411a680   #PF: supervisor instruction fetch in kernel mode   #PF: error_code(0x0011) - permissions violation   Oops: Oops: 0011 [#1] SMP KASAN PTI   Workqueue: ktls_device_destruct 0xffffea000411a680   RIP: 0010:0xffffea000411a680   Call Trace:    <TASK>    worker_thread (kernel/workqueue.c:3405 kernel/workqueue.c:3486)    kthread (kernel/kthread.c:436)    ret_from_fork (arch/x86/kernel/process.c:158)    ret_from_fork_asm (arch/x86/entry/entry_64.S:245)    </TASK>",
                                "cve_priority": "high",
                                "cve_public_date": "2026-09-04 16:18:00 UTC"
                            }
                        ],
                        "log": [
                            "",
                            "  * jammy/linux-kvm: 5.15.0-1113.118 -proposed tracker (LP: #2173211)",
                            "",
                            "  [ Ubuntu: 5.15.0-204.214 ]",
                            "",
                            "  * jammy/linux: 5.15.0-204.214 -proposed tracker (LP: #2173225)",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857)",
                            "    - device property: Add cleanup.h based fwnode_handle_put() scope based",
                            "      cleanup.",
                            "    - device property: fix infinite loop in fwnode_for_each_child_node()",
                            "    - ocfs2: validate dx_root extent list fields during block read",
                            "    - nvme-tcp: validate R2T PDU in nvme_tcp_handle_r2t()",
                            "    - staging: rtl8723bs: fix spacing around operators",
                            "    - Bluetooth: btqcomsmd: Convert to platform remove callback returning void",
                            "    - io_uring/rw: end write accounting from ->ki_complete",
                            "    - ALSA: usb-audio: Optimize the copy of packet sizes for implicit fb",
                            "      handling",
                            "    - ALSA: usb-audio: Clamp implicit feedback packet count to URB capacity",
                            "    - perf tools: Fix a asan issue in parse_events_multi_pmu_add()",
                            "    - perf test bpf: Address error about non-null argument for epoll_pwait 2nd",
                            "      arg",
                            "    - zram: fixup read_block_state()",
                            "    - nfsd: size fh_verify server sockaddr slot by xpt_locallen",
                            "    - nfsd: check nfsd4_acl_to_attr() return value in nfsd4_create()",
                            "    - coresight: etm3x: Fix cntr_val_show() to match cntr_val_store() behavior",
                            "    - kernel/params.c: Use kstrtobool() instead of strtobool()",
                            "    - params: Do not go over the limit when getting the string length",
                            "    - params: Use size_add() for kmalloc()",
                            "    - params: Sort headers",
                            "    - params: Fix multi-line comment style",
                            "    - dmaengine: Add devm_dma_request_chan()",
                            "    - i2c: mxs: fix DMA channel leak on probe error",
                            "    - power: supply: rt9455: Convert to i2c's .probe_new()",
                            "    - i2c: core: Introduce i2c_client_get_device_id helper function",
                            "    - power: supply: max17040: Convert to i2c's .probe_new()",
                            "    - power: supply: max17040: drop incorrect I2C functionality check",
                            "    - hwrng: stm32 - Fix runtime PM cleanup on registration failure",
                            "    - spi: bcm63xx: disable clock on resume failure",
                            "    - staging: sm750fb: fix mono image source stride mismatch in",
                            "      lynxfb_ops_imageblit()",
                            "    - ftrace: Synchronize the initialization of ftrace_ops",
                            "    - arm64: allow pte_offset_map() to fail",
                            "    - mm/mremap: reset unfaulted VMA page offset for MREMAP_DONTUNMAP",
                            "    - media: rkvdec: Propagate platform_get_irq() errors",
                            "    - media: zoran: Avoid freeing a registered video_device twice",
                            "    - scsi: qla2xxx: Fix 64G link speed reporting in get_data_rate",
                            "    - ring-buffer: Acquire the lock with irqsave in rb_wake_up_waiters()",
                            "    - smb: client: fix file type corruption in cifs_reparse_point_to_fattr()",
                            "    - smb: client: avoid leaking refcount when cifs_sb_tlink() fails",
                            "    - watchdog: rtd119x: Use devm_clk_get_enabled() helper",
                            "    - perf/x86/intel: Remove anythread_deprecated bit from perf_capabilities",
                            "    - smb3: make query_on_disk_id open context consistent and move to common",
                            "      code",
                            "    - net: ipconfig: Remove outdated comment and indent code block",
                            "    - pinctrl: sunxi: Refactor register/offset calculation",
                            "    - pinctrl: sunxi: Use devm_clk_get_enabled() helpers",
                            "    - pinctrl: sunxi: keep a shadow copy of the data register output latches",
                            "    - net: ena: Remove autopolling mode",
                            "    - netfilter: nf_tables: set->ops->insert returns opaque set element in",
                            "      case of EEXIST",
                            "    - smb: client: validate POSIX create context length",
                            "    - Bluetooth: btusb: Add IMC Networks QCA9377 to quirks table",
                            "    - HID: core: remove #ifdef CONFIG_PM from hid_driver",
                            "    - HID: hid-alps: use default remove for hid device",
                            "    - HID: hid-alps: Use pm_ptr instead of #ifdef CONFIG_PM",
                            "    - smb/client: use stack-allocated smb2_file_all_info in",
                            "      smb3_query_mf_symlink()",
                            "    - smb/client: pass cifs_open_info_data to SMB2_open()",
                            "    - smb: client: close handle after create-context parsing failure",
                            "    - ALSA: usb-audio: Apply IGNORE_CTL_ERROR quirk to all Audient devices",
                            "    - of/irq: Fix remaining refcount leaks in of_irq_init()",
                            "    - wifi: cfg80211: avoid double free if updating BSS fails",
                            "    - drm/msm/a6xx: Avoid a nullptr dereference when speedbin setting fails",
                            "    - openvswitch: add nf_ct_is_confirmed check before assigning the helper",
                            "    - rds_tcp: close NULL deref window in rds_tcp_set_callbacks",
                            "    - of/irq: add missing of_node_put() for interrupt parent node",
                            "    - ALSA: caiaq: unregister the input device when probe fails",
                            "    - perf/core: Fix WARN in perf_sigtrap()",
                            "    - scsi: qla2xxx: Fix NVMe abort reference leak on repeated abort",
                            "    - mtd: core: clear out unregistered devices a bit more",
                            "    - mtd: core: Drop duplicate NULL checks around nvmem_unregister()",
                            "    - mtd: core: Fix refcount error in del_mtd_device()",
                            "    - mtd: use refcount to prevent corruption",
                            "    - mtd: call external _get and _put in right order",
                            "    - nvmet: preserve device path on allocation failure",
                            "    - of/overlay: don't create \"//\" paths for fragments targeting the root",
                            "    - ASoC: wm8903: Move the DRC QR threshold to the register that holds it",
                            "    - ASoC: codecs: rt274: Fix format setting for 44100 rate",
                            "    - Bluetooth: hci_core: free the HCI ID if naming fails",
                            "    - netfilter: ipset: do not update comments from kernel-side adds",
                            "    - net: systemport: Fix RUNT MIB counter register offset calculation",
                            "    - net/sched: fq_codel: match the no-drop threshold to the packet size",
                            "    - net/sched: sch_codel: match the no-drop threshold to the packet size",
                            "    - tcp: refresh TS.Recent for accepted old ACKs",
                            "    - ipvs: fix missing counter decrement in lblc",
                            "    - ipvs: do not create invisible templates",
                            "    - net: add and use skb_get_hash_net",
                            "    - i2c: at91: release DMA channels when probe defers",
                            "    - PCI: Accept AtomicOps already enabled by the hypervisor",
                            "    - drm/radeon: Read the VRAM VBIOS signature with readb()",
                            "    - kgdboc: Fix tty driver reference leak in configure_kgdboc()",
                            "    - Input: atkbd - skip deactivate for Lenovo IdeaPad Slim 3 15IWC11",
                            "    - Input: i8042 - add nomux quirk for Fujitsu LIFEBOOK U7410",
                            "    - Input: synaptics - add LEN205b entry to smbus_pnp_ids for ThinkPad T490",
                            "    - Input: synaptics - limit T440p InterTouch quirk to LEN0036",
                            "    - USB: cdc-acm: fix racy TIOCMIWAIT implementation",
                            "    - usb: hub: use shorter 120ms post resume hold for SS root hubs",
                            "    - usb: ohci-da8xx: disable controller wakeup on cleanup",
                            "    - usb: ohci-s3c2410: disable controller wakeup on removal",
                            "    - usb: ohci-st: disable controller wakeup on removal",
                            "    - usb: typec: ucsi: Get the connector fwnode based on reg value",
                            "    - usb: typec: ucsi: displayport: Current CAM OOB index fixup",
                            "    - tty: amiserial: fix broken TIOCMIWAIT",
                            "    - tty: serial: qcom_geni_serial: Keep console RX functional after deep",
                            "      idle",
                            "    - serial: tegra: don't clear the Tx FIFO on an Rx-only reset",
                            "    - serial: vt8500: Fix clock reference leak in vt8500_serial_probe()",
                            "    - Bluetooth: hci_core: Fix inquiry cache timestamps on 64-bit systems",
                            "    - mtd: rawnand: vf610_nfc: fix reads on chips with more than 64 bytes of",
                            "      OOB",
                            "    - mtd: spinand: fix zero oobavail when no ECC engine is used",
                            "    - USB: serial: cp210x: add Corsair AX1500i Power Supply",
                            "    - USB: serial: quatech2: fix baud rate overflow",
                            "    - USB: serial: ssu100: fix baud rate overflow",
                            "    - USB: serial: option: add support for SIMCom SIM8260C",
                            "    - USB: serial: option: add Quectel EG060W",
                            "    - USB: serial: option: add Compal EXM-G1x support",
                            "    - USB: serial: option: add Quectel RG660QB",
                            "    - USB: serial: option: add Compal EXC-T1 support",
                            "    - iio: accel: sca3000: fix frequency divider condition check",
                            "    - iio: adc: sun4i-gpadc-iio: drop underflowing pm_runtime_put() calls",
                            "    - iio: proximity: isl29501: Fix return type of isl29501_register_write",
                            "    - iio: proximity: vcnl3020: fix ISR bitmask check in IRQ handler",
                            "    - iio: trigger: cancel reenable_work before freeing trigger",
                            "    - Revert \"scsi: sd: sd_zbc: Use logical blocks as unit when querying",
                            "      zones\"",
                            "    - SUNRPC: fix gssx_dec_option_array error path bugs",
                            "    - vc_screen: reload vc pointer before if (ret) in vcs_write() to avoid UAF",
                            "    - mtd: rawnand: vf610_nfc: fix false bitflips on reads of erased pages",
                            "    - wifi: wl12xx: Drop if with an always false condition",
                            "    - wifi: wlcore: Convert to platform remove callback returning void",
                            "    - wifi: wlcore: Fix runtime PM leak in wlcore_remove()",
                            "    - net: usb: qmi_wwan: add Quectel EG120K-EA",
                            "    - serial: imx: Convert to platform remove callback returning void",
                            "    - usb: gadget: at91_udc: Convert to platform remove callback returning",
                            "      void",
                            "    - usb: typec: tcpm: fix debug accessory mode detection for sink ports",
                            "    - usb: typec: tcpm: constrain TCPM_SOURCING_VBUS event handling",
                            "    - drm/amd/pm/si: Check AMD_IS_MOBILITY flag for PPSMC_SYSTEMFLAG_GPIO_DC",
                            "    - soc: qcom: geni-se: Correct QUP Core ICC vote constants",
                            "    - usb: dwc3: gadget: fix IRQ storm on invalid event buffer count",
                            "    - arm64: errata: Factor out broken AMU const counter cap",
                            "    - [Config] enable ARM64_WORKAROUND_BROKEN_AMU_CONSTCNT",
                            "    - arm64: errata: Add Cortex-A725 erratum 3821522 workaround",
                            "    - [Config] arm64: errata: Add Cortex-A725 erratum 3821522 workaround",
                            "    - iio: buffer: serialize buffer teardown with mode claims",
                            "    - KVM: arm64: Don't use the VMA to size stage-2 block mappings for",
                            "      VM_PFNMAP",
                            "    - fsverity: add dependency on 64K or smaller pages",
                            "    - drm/amd/display: check dc_state_create_copy() for NULL in dm_suspend",
                            "    - drm/amd/pm/si: Fix updating clock limits on AC/DC",
                            "    - drm/amdgpu: reset VI ASIC on MacBookPro15,1",
                            "    - drm/amdgpu: reset VI ASIC on MacBookPro14,3",
                            "    - drm/amdgpu: fix for coding style issues",
                            "    - usb: octeon-hcd: fix the FIFO-flush timeout computation",
                            "    - usb: ohci-spear: Remove unnecessary NULL check before",
                            "      clk_disable_unprepare()",
                            "    - usb: ohci-spear: disable controller wakeup on removal",
                            "    - usb: typec: ucsi: acpi: Assume UCSI 1.2 on Acer Nitro ANV15-41",
                            "    - tty: reformat kernel-doc in tty_io.c",
                            "    - Input: s6sy761 - fix resume ordering and restore sensing",
                            "    - tty: vt: fix memory leak in vc_allocate()",
                            "    - serial: fix TIOCMIWAIT race",
                            "    - drm/amd/display: Mark DCE 6.4 as not APU",
                            "    - mtd: spinand: Enable QE on all dies",
                            "    - USB: serial: clean up core error labels",
                            "    - tty: introduce and use tty_port_tty_vhangup() helper",
                            "    - mm/hugetlb: fix avoid_reserve to allow taking folio from subpool",
                            "    - iio: adc: aspeed: propagate reset deassert errors",
                            "    - iio: adc: max1363: sign-extend bipolar differential channel reads",
                            "    - HID: core: introduce hid_safe_input_report()",
                            "    - HID: uhid: convert to hid_safe_input_report()",
                            "    - crypto: drbg - Fix ineffective sanity check",
                            "    - ipv4: stop PMTU walk when nexthop group shrinks",
                            "    - Revert \"wifi: libertas: reject short monitor TX frames\"",
                            "    - sctp: copy zeroed stats to user in sctp_getsockopt_pr_streamstatus()",
                            "      when !streamoute",
                            "    - keys: finalize persistent keyring timeout after link attempt",
                            "    - dm-snap: reject the transient exception store for snapshot-merge",
                            "    - mmc: cavium-octeon: destroy slot platform devices on remove",
                            "    - mmc: cavium-thunderx: destroy slot platform devices on remove",
                            "    - net: usb: ax88179_178a: fix rx frame length for non-last packets",
                            "    - nvme: fix swapped ZRASF zone state values for full and read only",
                            "    - scsi: qedi: Initialize callback state before registration",
                            "    - drm/gud: don't keep a connector without a CRTC as connector_state",
                            "    - drm/amdgpu: make Mac FB workaround generic",
                            "    - fs: refuse fspick() on internal superblocks",
                            "    - drm/dp: don't mark the AUX backlight enabled when enabling failed",
                            "    - drm/aspeed: Balance the display clock enable on teardown",
                            "    - ASoC: adau1372: fix invalid default state of output ASRC and DAC muxes",
                            "    - net/mlx5e: Order ICOSQ cc update after CQ doorbell",
                            "    - mtd: fix use-after-free in mtd release",
                            "    - mtd: Clean refcounting with MTD_PARTITIONED_MASTER",
                            "    - mtd: maps: vmu-flash: Fix the (mtd core) switch to ref counters",
                            "    - mtd: fix double free and WARN_ON in add_mtd_device() error paths",
                            "    - dlm: validate length in dlm_search_rsb_tree",
                            "    - openvswitch: vport: fix self-deadlock on release of tunnel ports",
                            "    - smb: client: reject short Next offsets in parse_server_interfaces()",
                            "    - can: fix unique skb identifier regression under RPS",
                            "    - drm/amd/display: Don't replace a sink mode that shares the native totals",
                            "    - HID: hid-steam: Fix cleanup in probe()",
                            "    - HID: hid-steam: Make client_opened a counter",
                            "    - HID: steam: Fully unregister controller when hidraw is opened",
                            "    - HID: steam: Clean up locking",
                            "    - selinux: fix data race on AVC latest_notif",
                            "    - EDAC/amd64: Mask UMC chip select to the four implemented selects",
                            "    - mm/mremap: fix locked_vm leak by splitting VMA for MREMAP_DONTUNMAP",
                            "    - mm/mremap: fix locked_vm leak from MREMAP_DONTUNMAP self-merge",
                            "    - netfilter: nf_tables: fix bidirectional offload regression",
                            "    - net: team: Remove unused team_mode_op, port_enabled",
                            "    - net: team: Rename port_disabled team mode op to port_tx_disabled",
                            "    - Bluetooth: RFCOMM: connect the session socket without rfcomm_mutex",
                            "    - pmdomain: rockchip: fix clock leak on domain probe failure",
                            "    - pmdomain: rockchip: don't ignore clock lookup errors on attach",
                            "    - pmdomain: rockchip: propagate subdomain add errors",
                            "    - drm/amdgpu: copy debugfs register data outside the GRBM/SRBM locks",
                            "    - namespace: check the target before walking it in do_mount_setattr()",
                            "    - fcntl: refuse F_SET_RW_HINT on an immutable inode",
                            "    - netfilter: nf_tables: fix crash when nf_trace is enabled",
                            "    - tty: finish kernel-doc of tty_struct members",
                            "    - tty: add break_wait kernel-doc",
                            "    - xfrm: prevent policy_hthresh.work from racing with netns teardown",
                            "    - xfs: log items should have a xlog pointer, not a mount",
                            "    - xfs: aborting inodes on shutdown may need buffer lock",
                            "    - xfs: fix super block buf log item UAF during force shutdown",
                            "    - xfs: buffer pins need to hold a buffer reference",
                            "    - xfs: xfs_ifree_cluster vs xfs_iflush_shutdown_abort deadlock",
                            "    - xfs: catch stale AGF/AGF metadata",
                            "    - xfs: rearrange code in xfs_buf_item.c",
                            "    - xfs: factor out stale buffer item completion",
                            "    - xfs: fix unmount hang with unflushable inodes stuck in the AIL",
                            "    - power: supply: ds2780: Fix ds2780_get_capacity() returning raw value",
                            "    - ASoC: stm32: spdifrx: fix synchronization state check",
                            "    - ASoC: cs42l56: Put the Limiter Cushion control on the limiter register",
                            "    - ASoC: cs42l52: Fix the NG Type Switch bit",
                            "    - ASoC: pcm3168a: Fix the DAC zero flag polarity bit",
                            "    - ASoC: max98371: Fix the Speaker DHT Min Volume bits",
                            "    - ASoC: wm8978: Fix the 128x oversampling switch bits",
                            "    - ASoC: nau8822: Fix the 128x oversampling switch bits",
                            "    - netlink: remove netlink_broadcast_filtered",
                            "    - netlink: Reverse the patch which removed filtering",
                            "    - nios2: fix __wsum type degradation in csum_fold()",
                            "    - scsi: st: Save the visited block for the partition the drive is in",
                            "    - samples: pidfd: fix userprogs typo",
                            "    - clone: add CLONE_AUTOREAP",
                            "    - exit: fix lost-update race on the child_subreaper bitfields",
                            "    - tools: gpio: fix building from the top level with O=",
                            "    - i2c: qcom-cci: Fix HALT_ACK reset request being dropped",
                            "    - drm/amdgpu/sdma3: Work around POLL_REGMEM / FENCE hang",
                            "    - tracing: Fix the shift out of bounds in the log2 histogram modifier",
                            "    - cgroup: fix spurious SIGKILL of CLONE_INTO_CGROUP children",
                            "    - dm cache: fix demotion stats in passthrough mode",
                            "    - dm cache: fix issue with background work locking",
                            "    - dm-ebs: fix incorrect device offset check in ebs_ctr()",
                            "    - tipc: protect node reset trace dump with node lock",
                            "    - drm/amdgpu: Fix VCE 3 ring align_mask",
                            "    - KVM: x86/mmu: Preserve nested TDP shadow page tables if they are used as",
                            "      roots",
                            "    - tracing/histograms: Reject non-stacktrace fields for synthetic",
                            "      stacktrace fields",
                            "    - dm-integrity: require stable writes for internal hash modes",
                            "    - cifs: add revalidation on FSCTL failure in smb2_duplicate_extents()",
                            "    - SAUCE: Revert \"md: move initialization and destruction of 'io_acct_set'",
                            "      to md.c\"",
                            "    - md: move initialization and destruction of 'io_acct_set' to md.c",
                            "    - net_sched: codel: fix stale state for empty flows in fq_codel",
                            "    - Bluetooth: L2CAP: access chan->conn safely in get/setsockopt",
                            "    - Bluetooth: L2CAP: refuse __l2cap_chan_add if chan already has conn",
                            "    - tracing: Reject incomplete event filter expressions",
                            "    - tracing: Save the event file instead of the compatible histogram",
                            "    - tracing: Unregister field variable histograms when the command fails",
                            "    - tracing: Fix 64-bit and signed histogram fields on 32-bit kernels",
                            "    - keys: Avoid the owner account dereference in named keyring lookup",
                            "    - keys: Check the authorization payload in process keyring searches",
                            "    - keys: Protect the type name while describing a key",
                            "    - keys: make keyring indexes independent of kernel addresses",
                            "    - keys: Protect the read method check against type removal",
                            "    - KEYS: Fix key_reject_and_link() race with keyring restriction",
                            "    - KEYS: trusted: Fix blob allocation size in tpm2_key_decode()",
                            "    - keys/trusted_keys: return immediately after TPM unseal failure",
                            "    - io-wq: order the exit bit against worker creation task work",
                            "    - signal: don't retarget shared signals in a dying thread group",
                            "    - Linux 5.15.224",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99115",
                            "    - ksmbd: fill in FileSysIdentifier in FS_POSIX_INFORMATION",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99113",
                            "    - ksmbd: zero the FS_OBJECT_ID_INFORMATION buffer before filling it in",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99114",
                            "    - ksmbd: initialize FileSystemControlFlags in FS_CONTROL_INFORMATION",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99132",
                            "    - xfs: don't hold buffer locks across sync transaction commit in",
                            "      xfs_sync_sb_buf",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99135",
                            "    - dm-integrity: fix infinite loop on discard with large tag size",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99118",
                            "    - drm/i915/dmc: Harden DMC firmware payload parsing",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99169",
                            "    - futex: Fix mm reuse handling for FUT_OFF_MMSHARED",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99161",
                            "    - i2c: viai2c-wmt: Fix clock leak in wmt_i2c_probe()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99077",
                            "    - ipv4: udp: Create exceptions before socket matching",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99123",
                            "    - vsock/virtio: validate packet source for connected sockets",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-89987",
                            "    - mm/huge_memory: transfer the pmd dirty bit to the folio on zap",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-80572",
                            "    - Input: byd - synchronize timer deletion before freeing private data",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99180",
                            "    - unicode: free the map after a grace period",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99179",
                            "    - watch_queue: Fix note pool publication race in watch_queue_set_size()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-89912",
                            "    - KVM: arm64: vgic-its: Don't dereference a NULL collection on ITT save",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99156",
                            "    - scsi: st: Fix use-after-free race between st_remove() and st_open()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99112",
                            "    - net/sched: cls_flower: validate mask pointer after nla_next()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99117",
                            "    - net: bridge: mcast: don't truncate the port group walk on teardown",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-74405",
                            "    - OPP: Fix race between OPP addition and lookup",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-74739",
                            "    - net/sched: cls_u32: skip hash tables in u32_bind_class()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-64015",
                            "    - security/keys: fix missed RCU read section on lookup",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-74672",
                            "    - mm/vmalloc: acquire init_mm lock on huge vmap to avoid ptdump UAF",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99121",
                            "    - ipv4: avoid divide by zero in fib_rebalance",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99124",
                            "    - s390/pci: Fix leak of uninitialized kernel data in SCLP report",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99126",
                            "    - s390/ctcm: Prevent XID null dereference",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99127",
                            "    - page_pool: keep frag_offset aligned for odd-sized requests",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99128",
                            "    - sctp: validate chunk length in the inqueue parser",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99133",
                            "    - net/iucv: fix the recvmsg window update",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99136",
                            "    - dm-crypt: fix a tiny race condition in crypt_dec_pending",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99138",
                            "    - tcp: fix use-after-free in do_tcp_getsockopt(TCP_CC_INFO)",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99100",
                            "    - wifi: p54: validate firmware record lengths",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99140",
                            "    - tracing: Fix hist trigger timestamps for buffered events",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99150",
                            "    - drm/amdgpu: don't drop the runtime PM reference twice in amdgpu_gpr",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99152",
                            "    - scsi: libiscsi: Validate the task named by a management response",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99153",
                            "    - scsi: libiscsi: Validate the ITT reflected in a Reject PDU",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99154",
                            "    - scsi: libiscsi: Reject a negative task index from parse_pdu_itt",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99165",
                            "    - sctp: revalidate output stream after association connect wait",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99166",
                            "    - net: rds: fix uninitialized trans dereference in CM event handler",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99167",
                            "    - net/sched: fix use-after-free in __tcf_action_put()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99175",
                            "    - fsnotify: prevent mark additions during connector teardown",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99176",
                            "    - KVM: nVMX: Reset MMU back to the root MMU if loading L2 state fails for",
                            "      !VM-Entry",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99181",
                            "    - autofs: ignore notification errors from a replaced pipe",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99201",
                            "    - netlink: avoid hashing the network namespace pointer",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99203",
                            "    - pipe: preserve existing fasync readers on writer setup failure",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99204",
                            "    - ocfs2/dlm: Protect the recovery list during debugfs reads",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99206",
                            "    - scsi: target: iscsi: Fix race in discovery auth updates",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99211",
                            "    - netlink: reset skb headers before unicast and multicast filtering",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99212",
                            "    - net/rds: don't let the rdma_cm destroy an id RDS still owns on route",
                            "      failure",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99213",
                            "    - vsock: treat TCP_CLOSING as once-established",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99216",
                            "    - Drivers: hv: Don't reset VMBus connection state on error/exit paths",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2022-50167",
                            "    - bpf: fix potential 32-bit overflow when accessing ARRAY map element",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99082",
                            "    - KVM: x86: Use active memslots for the per-vCPU MMIO cache",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99083",
                            "    - ksmbd: fix heap out-of-bounds write in krb5_authenticate()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98977",
                            "    - namespace: handle mount locking for automounts correctly",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98992",
                            "    - namespace: don't copy an unmounted mount tree",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98981",
                            "    - namespace: unhash a dentry before detaching the mounts on it",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99005",
                            "    - drm/i915/gt: Unmask interrupts only when ACTIVE is true",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99007",
                            "    - drm/fb-helper: defer setup when fbdev_probe() fails, not just on -EAGAIN",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99019",
                            "    - scsi: ch: Do not keep references to data transfer element devices",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99024",
                            "    - optee: register TEE devices only once fully initialized",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99036",
                            "    - dm: fix reading free memory in do_resume",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98985",
                            "    - namespace: check the mounts before reading their parents in pivot_root()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98993",
                            "    - namespace: don't inherit MNT_UMOUNT in clone_mnt()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99002",
                            "    - drm/vmwgfx: validate pitch coming from userspace",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99027",
                            "    - net: team: stop reusing skb after queue override",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-64190",
                            "    - net: team: fix NULL pointer dereference in team_xmit during mode change",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99041",
                            "    - ip6_gre: remove obsolete ERSPAN PMTU update",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-97935",
                            "    - tracing: Set the trace clock before registering the histogram trigger",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98944",
                            "    - HID: steam: Refactor registration",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98945",
                            "    - HID: steam: Rearrange teardown sequence",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2025-40135",
                            "    - ipv6: use RCU in ip6_xmit()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2025-38728",
                            "    - smb3: fix for slab out of bounds on mount to ksmbd",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-31678",
                            "    - openvswitch: defer tunnel netdev_put to RCU release",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99088",
                            "    - net: openvswitch: validate transport header presence in set_ipv6_addr",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98950",
                            "    - flow_dissector: avoid u16 truncation of hlen in bpf_flow_dissect()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98955",
                            "    - flow_dissector: avoid u16 truncation of skb->len when computing thoff",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99089",
                            "    - ASoC: samsung: i2s: enable op_clk in probe to balance runtime PM",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98956",
                            "    - ASoC: adau1372: allow sleepy powerdown GPIOs",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98964",
                            "    - nvmet: use the local P2P device on metadata allocation failure",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98967",
                            "    - cxgb4/ch_ktls: disable softirqs around tid_list erases",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98969",
                            "    - net/sched: em_text: reject unterminated algo before autoload",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98970",
                            "    - drm/vc4: Free the BO cache size list on teardown",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98971",
                            "    - gpio: exar: initialize the ID before registering its cleanup",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98979",
                            "    - namespace: refuse an automount below a mount that is in no namespace",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98984",
                            "    - dcache: don't put a mountpoint on a dentry that's being removed",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98990",
                            "    - namespace: check a submount for references right before unmounting it",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99095",
                            "    - drm/vc4: drain the hangcheck timer and works on V3D unbind",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99006",
                            "    - drm/i915/gem: Prevent overstepping exec array boundary",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99008",
                            "    - Bluetooth: RFCOMM: Fix NULL tty_dev dereference in rfcomm_dev_shutdown",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99010",
                            "    - Bluetooth: RFCOMM: free the skb when the DLC has no owner",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99015",
                            "    - Bluetooth: hci_sock: Serialize dead-device detachment",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99022",
                            "    - regulator: ltc3676: don't read the write-only HRST and CLIRQ registers",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99025",
                            "    - openvswitch: fix soft lockup in the netlink flow dump",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99031",
                            "    - net: bridge: avoid recursive multicast port cleanup",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99032",
                            "    - net/smc: protect clcsock lifetime in smc_getname",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99033",
                            "    - net/packet: guard the ll header push in packet_rcv_spkt()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99034",
                            "    - mmc: sdhci-sprd: disable runtime PM on remove",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99035",
                            "    - mmc: mtk-sd: Cancel request timeout work on remove",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99037",
                            "    - dm-crypt: reject the lmk IV mode with AEAD ciphers",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99038",
                            "    - memstick: rtsx_usb_ms: complete requests after eject instead of dropping",
                            "      them",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99039",
                            "    - memstick: core: wait for request completion before freeing card",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99040",
                            "    - KEYS: Fix add_key() race with keyring restriction",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99045",
                            "    - ibmveth: h_free logical LAN on open-fail after register",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99049",
                            "    - gpio: xilinx: fix runtime PM leak on request error path",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99052",
                            "    - selinux: preserve NATIVE_LABELS on already-initialized sb in",
                            "      set_mnt_opts",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99053",
                            "    - tipc: hold a reference to nodes found by link name",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99054",
                            "    - tipc: destroy topsrv workqueues before closing connections",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99056",
                            "    - strparser: make sure __strp_recv isn't running before tearing down the",
                            "      parser",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99057",
                            "    - xen/netfront: don't leak the skb when xennet_fill_frags() fails",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99058",
                            "    - workqueue: Fix NULL current_pwq deref in chained work check",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99059",
                            "    - wireguard: noise: reject response consumption after intermediate",
                            "      initiation",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99061",
                            "    - wifi: brcmfmac: fix P2P device removal race in brcmf_detach()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99063",
                            "    - dm ioctl: don't let data_start run past the buffer",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99067",
                            "    - btrfs: scrub: fix local_root reference leak in",
                            "      scrub_print_warning_inode()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99070",
                            "    - ipv6: do not warn on route notification size race",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99071",
                            "    - ipv4: do not warn on route notification size race",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99072",
                            "    - ipv4: stop route notification sizing when nexthop group shrinks",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98686",
                            "    - smb: client: discard post-EOF pagecache when extending a file via zero",
                            "      range",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98700",
                            "    - wifi: mac80211: set info->band for 802.3 encap offload frames",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98716",
                            "    - KVM: SVM: Use the active VMCB's MSR bitmap when checking if MSR is",
                            "      intercepted",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99080",
                            "    - fs: Free any excess xarray nodes in clear_inode()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98709",
                            "    - wifi: mac80211: count only matching reservations in reserved switch",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98708",
                            "    - wifi: mac80211: keep paired old chanctx alive",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98752",
                            "    - tty: port: fix tty_port_tty_vhangup() race",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-99081",
                            "    - bnxt_en: fix DMA mapping length for padded small packets",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98696",
                            "    - USB: serial: fix driver deregistration order",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98705",
                            "    - wifi: mac80211: account proxy paths against the mesh path limit",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98722",
                            "    - mtd: block2mtd: Fix divide error when erase_size is zero",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98695",
                            "    - USB: serial: fix ioctl hangup race",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98694",
                            "    - thunderbolt: Fix KASAN reported use-after-free when request is canceled",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98704",
                            "    - wifi: mac80211: keep fallback association elements alive",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98707",
                            "    - wifi: mac80211: shut down RX BA session timer on teardown",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98749",
                            "    - tty: serial: max3100: shut down timer before freeing port",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98751",
                            "    - tty: abort break signalling on hangup",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98753",
                            "    - tty: tty_port: restore TTY_IO_ERROR on activation failure",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98762",
                            "    - USB: dwc2: shut down wakeup timer before freeing HCD state",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98784",
                            "    - drm/amdgpu/gfx6: fix firmware leak on teardown",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98779",
                            "    - drm/amdgpu: fix ACP MFD device leak on init failure",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98742",
                            "    - ALSA: seq: Serialize compat port-info ioctls",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98655",
                            "    - perf: Require kernel access for text poke events",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98750",
                            "    - tty: fix saved termios reset race",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-89638",
                            "    - smb: client: clear setuid/setgid bit on write with",
                            "      cifsacl/modefromsid/posix extensions",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98375",
                            "    - xen/netfront: drop RX packets with a short Ethernet header",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-89738",
                            "    - usb: gadget: at91_udc: drain polled-VBUS timer/work before udc is freed",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-89740",
                            "    - serial: imx: serialize imx_uart_ports[] lifetime",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-74341",
                            "    - wifi: wcn36xx: fix heap overflow from oversized firmware HAL response",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-74406",
                            "    - vxlan: Fix potential null-ptr-deref in vxlan_gro_prepare_receive().",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-46265",
                            "    - RDMA/hns: Fix WQ_MEM_RECLAIM warning",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98681",
                            "    - smb: client: split cifsFileInfo bitfields to avoid shared-byte RMW races",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-89539",
                            "    - SUNRPC: reject duplicate CREDS_VALUE options",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-93179",
                            "    - drm/amd/powerplay: fix VoltageObjectInfo zero-stride loop and OOB read",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2023-52561",
                            "    - arm64: dts: qcom: sdm845-db845c: Mark cont splash memory region as",
                            "      reserved",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2023-53651",
                            "    - Input: exc3000 - properly stop timer on shutdown",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2023-53733",
                            "    - net: sched: cls_u32: Undo tcf_bind_filter if u32_replace_hw_knode",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98657",
                            "    - iio: proximity: pulsedlight: fix iio_device left registered on PM setup",
                            "      failure",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98662",
                            "    - iio: light: gp2ap020a00f: drain irq_work after free_irq",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98663",
                            "    - iio: imu: adis16480: fix unprotected debugfs reads",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98664",
                            "    - iio: imu: adis16400: fix unprotected debugfs reads",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98666",
                            "    - iio: gyro: adis16136: fix unprotected debugfs reads",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98671",
                            "    - iio: adc: sun4i-gpadc-iio: clean up on thermal zone registration failure",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98679",
                            "    - iio: accel: kxcjk-1013: reject duplicate event disable",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98687",
                            "    - thunderbolt: Reject oversized XDomain properties responses",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98697",
                            "    - USB: serial: fix dynamic id driver deregistration race",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98698",
                            "    - wifi: mac80211: handle empty FILS association request payload",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98701",
                            "    - wifi: mac80211: release mesh path quota on failed additions",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98703",
                            "    - wifi: mac80211: minstrel_ht: validate fixed rate index",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98706",
                            "    - wifi: mac80211: drain PS delivery work during station teardown",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98710",
                            "    - wifi: iwlegacy: 3945: free EEPROM data on remove",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98711",
                            "    - wifi: cw1200: fix TX padding OOB read leaking heap data to device",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98721",
                            "    - mtd: rawnand: cadence: Initialize IRQ state before requesting IRQ",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98726",
                            "    - nvme-multipath: fix underflow in ANA log bounds checks",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98856",
                            "    - kprobes: Skip disarmed probes when checking optkprobe overlap",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98857",
                            "    - ipvs: bound LBLCR and LBLC cache growth",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98732",
                            "    - Bluetooth: btintel: fix buffer over-read in btintel_hw_error()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98735",
                            "    - Bluetooth: hci_core: Serialize ACL scheduling with channel deletion",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98739",
                            "    - Bluetooth: RFCOMM: Fix initial port reference race",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98741",
                            "    - ALSA: ua101: reject mismatched capture/playback packet sizes",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98940",
                            "    - ASoC: qcom: lpass-cpu: use DAI table index for playback constraints",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98748",
                            "    - serial: 8250_bcm7271: fix use-after-free in brcmuart_remove()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98754",
                            "    - tty: vcc: hold port lock when clearing tty pointer in vcc_cleanup",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98755",
                            "    - tty: vcc: zero-initialize control packet in vcc_send_ctl()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98756",
                            "    - usb: cdns3: Fix NULL pointer dereference in cdns3_pci_probe",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98757",
                            "    - usb: cdns3: fix use-after-free in cdns3_gadget_exit()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98760",
                            "    - usb: typec: tipd: fix uninitialized typec_partner_desc in",
                            "      tps6598x_connect()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98761",
                            "    - usb: typec: tcpm: recover after failure to start the frs ams",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98763",
                            "    - usb: core: clear both ep_in and ep_out for non-ep0 control endpoints",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98764",
                            "    - usb: gadget: f_fs: Fix NULL pointer dereference in",
                            "      FUNCTIONFS_ENDPOINT_DESC",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98765",
                            "    - USB: gadget: dummy-hcd: Fix wait for outstanding request completions",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98766",
                            "    - usb: gadget: aspeed-vhub: cancel wake work on device removal",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98769",
                            "    - usb: gadget: f_uac1_legacy: validate bRequest index in",
                            "      generic_{set,get}_cmd",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98771",
                            "    - usb: storage: sierra_ms: reject short SWoC info transfers",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98772",
                            "    - USB: serial: fix port tear down use-after-free",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98775",
                            "    - nitro_enclaves: fix use-after-free on SLOT_ALLOC failure",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98790",
                            "    - perf: Fix race between perf_event_exit_task() and perf_pending_task()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98934",
                            "    - ipv6: sr: use skb_get_hash_net() in seg6_make_flowlabel()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2022-49622",
                            "    - netfilter: nf_tables: avoid skb access on nf_stolen",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98794",
                            "    - ipvs: filter some flags received in the backup server",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98805",
                            "    - tipc: prevent GCM nonce reuse on peer key changes",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98811",
                            "    - net/sched: cls_api: reclaim an empty proto on the error path",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98812",
                            "    - net/mctp: publish the mctp_dev only after it is initialised",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98819",
                            "    - Bluetooth: btintel: validate DDC record lengths",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98823",
                            "    - wifi: cfg80211: preserve hidden-group beacon IE ownership",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98936",
                            "    - wifi: ath11k: reset ar->num_stations on hardware start",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98831",
                            "    - of/overlay: don't leak fragment references when changeset init fails",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98833",
                            "    - mtd: core: call _get_device() with the master MTD",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-89860",
                            "    - scsi: qla2xxx: Initialize NVMe abort_work once at submission",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-53353",
                            "    - hsr: Remove WARN_ONCE() in hsr_addr_is_self().",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98836",
                            "    - ALSA: line6: reject oversized playback packets",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98838",
                            "    - vt: skip screen update for DEC alignment test on backgroup consoles",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98568",
                            "    - vxlan: use one headroom snapshot for neighbour replies",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2024-49901",
                            "    - drm/msm/adreno: Assign msm_gpu->pdev earlier to avoid nullptrs",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98846",
                            "    - sctp: check RCV_SHUTDOWN after the sendmsg connect wait",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98847",
                            "    - rtc: spear: initialize IRQ state before requesting alarm IRQ",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98850",
                            "    - net/packet: prevent TX_RING byte count overflow",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98851",
                            "    - netfilter: nft_flow_offload: drop flowtable reference on init error path",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98854",
                            "    - of/overlay: only treat a positive changeset id as registered",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98855",
                            "    - of/overlay: put property on deadprops only after changeset add succeeds",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98862",
                            "    - audit: fix exe mark UAF in kill_rules()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98450",
                            "    - smb: client: close completed creates on compound wait errors",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98502",
                            "    - HID: alps: unregister DualPoint Stick input device on remove",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98456",
                            "    - Bluetooth: mgmt: fix race in read_unconf_index_list()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98451",
                            "    - smb: client: use finish_no_open() for non-regular inodes",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98484",
                            "    - netfilter: nf_tables: skip expired catchall elements on insert and",
                            "      delete",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98486",
                            "    - net: ena: fix MMIO read buffer leak on probe failure",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98493",
                            "    - net: ipconfig: bound DHCP option construction",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98454",
                            "    - smb: client: fix create context out-of-bounds reads",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98490",
                            "    - net: openvswitch: conntrack: fix helper UAF due to extensions realloc",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98507",
                            "    - mm/rmap: fix missing barrier between anon_vma init and vma->anon_vma",
                            "      publish",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98519",
                            "    - drm/amdgpu: Fix runtime PM leak in amdgpu_debugfs_test_ib_show()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98549",
                            "    - tcp: prevent collapsing skbs across boundary in rtx queue",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98544",
                            "    - bna: prevent IOC timer rearm during teardown",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98172",
                            "    - smb: client: fix smbd_connection leak on cifs_get_tcp_session() error",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98192",
                            "    - wifi: wcn36xx: Fix potential use-after-free in TX ack timer teardown",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98198",
                            "    - hwmon: (pwm-fan) Stop RPM timer before freeing tach data",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98409",
                            "    - watchdog: rtd119x: Avoid division by zero",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98245",
                            "    - btrfs: take commit root semaphore when iterating in",
                            "      mark_block_group_to_copy()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98264",
                            "    - ALSA: virtio: reset device before deleting virtqueues",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-97558",
                            "    - smb: client: fix cifsFileInfo reference leak in deferred close",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-97616",
                            "    - net/sched: act_api: release all action references on NEWACTION failure",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-97939",
                            "    - ipmr: account multicast table and route memory",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-89837",
                            "    - f2fs: fix dentry folio leak in find_in_level",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-89838",
                            "    - f2fs: limit recovery filename logging to stored length",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-97530",
                            "    - scsi: qla2xxx: Fix soft lockup polling continuation IOCB signature",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98386",
                            "    - scsi: qla2xxx: Use memset_io() to clear QLAFX00 request ring slot",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-89848",
                            "    - scsi: qla2xxx: Quiesce response IRQ before freeing request queue",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-97532",
                            "    - scsi: qla2xxx: Null out freed pointers in qla2x00_mem_alloc() error path",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-89877",
                            "    - media: saa7164: fix cleanup on resource allocation failure",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-93239",
                            "    - arm64: mm: Fix the lockless page-table walk in show_pte()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-90023",
                            "    - usb: gadget: f_mass_storage: fix null pointer dereference in",
                            "      fsg_common_set_num_buffers()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-93200",
                            "    - i3c: master: Fix use-after-free of master->this",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-93199",
                            "    - i3c: master: Do not treat master device as a duplicate target",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-89441",
                            "    - mmc: via-sdmmc: cancel card-detect work on remove",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-89465",
                            "    - power: supply: rt9455: quiesce delayed work before teardown",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-93231",
                            "    - lockd: fix swapped arguments in nlmsvc_match_ip()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-89552",
                            "    - params: fix charp corruption on allocation failure",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-89640",
                            "    - cifs: fix loff_t underflow in cifs_remap_file_range() when len == 0",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-89672",
                            "    - nfsd: gate nfs2 setacl by argp->mask",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-89685",
                            "    - nfsd: fix clock domain mismatch in clients_still_reclaiming()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-89707",
                            "    - nfsd: release path refs on follow_down() error",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-89719",
                            "    - zram: fix out-of-bounds access in read_block_state()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-89763",
                            "    - KEYS: trusted: Fix TPM teardown ordering",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-80851",
                            "    - gtp: serialize PDP context updates",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-80861",
                            "    - usb: xhci: bail out of setup if the controller is inaccessible",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98377",
                            "    - vlan: require the MAC header to be present in __vlan_insert_inner_tag()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98170",
                            "    - smb: client: fix OOB struct field reads in move_smb2_ea_to_cifs()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98171",
                            "    - smb: client: fix next_buffer UAF and NextCommand bounds in compound PDUs",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98169",
                            "    - smb: client: fix potential OOB read in smb3_enum_snapshots()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-98193",
                            "    - wifi: libipw: reject TKIP frames without a full MIC",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-97555",
                            "    - smb: client: fix heap overflow in DACL owner/group rewrite",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-97557",
                            "    - smb: client: avoid leaking refcount in cifs_queue_oplock_break()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-97564",
                            "    - smb: client: reject userspace cifs.idmap descriptions",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-97615",
                            "    - net: bridge: use option bits for CFM/MRP frame handlers",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-97901",
                            "    - genetlink: pin family module during policy dump",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-97908",
                            "    - Bluetooth: btqcomsmd: destroy RPMsg endpoints before freeing hci_dev",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-97925",
                            "    - tick/broadcast: Plug clockevents replacement race",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-93285",
                            "    - f2fs: embed f2fs_gc_kthread in f2fs_sb_info",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-97529",
                            "    - scsi: qla2xxx: Validate BSG request_len before reading vendor_cmd[]",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-97536",
                            "    - scsi: qla2xxx: Fix use-after-free of qpair work on queue teardown",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-97537",
                            "    - scsi: qla2xxx: Fix queue teardown NULL dma_free and bitmap locking",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-89859",
                            "    - scsi: qla2xxx: Zero dport diagnostics buffer to avoid info leak",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-89921",
                            "    - KVM: s390: Zero initialize data structures for inject_pfault_token",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-89972",
                            "    - nvme: add missing SRCU grace period in error path",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-89988",
                            "    - kprobes: Protect kprobe_blacklist with RCU",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-90002",
                            "    - ftrace: Take trace_array reference before accessing its ftrace_ops",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-90016",
                            "    - staging: rtl8723bs: fix OOB read in rtw_restruct_wmm_ie()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-90029",
                            "    - usb: storage: realtek_cr: fix use-after-free on disconnect",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-80947",
                            "    - wifi: rtl8xxxu: fix use-after-free from rx_urb_wq on stop",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-89481",
                            "    - nvme-tcp: fix host memory disclosure on R2T for a read command",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-89492",
                            "    - ocfs2: validate directory-index entry counts when reading metadata",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-89553",
                            "    - nouveau/gem: reserve the bo in the info ioctl around the vma lookup",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-89625",
                            "    - HID: sony: fix UAF of ghl_poke_timer / ghl_urb at driver unbind",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-89633",
                            "    - smb: client: fix OOB read/write from unvalidated DataOffset in",
                            "      coalesce_t2()",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-89652",
                            "    - ceph: bound copied dentry name length in NFS export get_name",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-89680",
                            "    - nfsd: fix nfsd_file leak on inter-server COPY setup failure",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-89761",
                            "    - apparmor: fix out-of-bounds write when null terminating a label vec",
                            "  * Jammy update: v5.15.224 upstream stable release (LP: #2172857) //",
                            "    CVE-2026-80852",
                            "    - tls: device: fix out-of-bounds write in tls_append_frag()",
                            ""
                        ],
                        "package": "linux-kvm",
                        "version": "5.15.0-1113.118",
                        "urgency": "medium",
                        "distributions": "jammy",
                        "launchpad_bugs_fixed": [
                            2173211,
                            2173225,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857,
                            2172857
                        ],
                        "author": "Ubuntu Kernel Preparation Bot <ubuntu-kernel-bot@canonical.com>",
                        "date": "Mon, 09 Nov 2026 16:21:29 +0000"
                    }
                ],
                "notes": "linux-modules-5.15.0-1113-kvm version '5.15.0-1113.118' (source package linux-kvm version '5.15.0-1113.118') was added. linux-modules-5.15.0-1113-kvm version '5.15.0-1113.118' has the same source package name, linux-kvm, as removed package linux-headers-5.15.0-1112-kvm. As such we can use the source package version of the removed package, '5.15.0-1112.117', as the starting point in our changelog diff. Kernel packages are an example of where the binary package name changes for the same source package. Using the removed package source package version as our starting point means we can still get meaningful changelog diffs even for what appears to be a new package.",
                "is_version_downgrade": false
            }
        ],
        "snap": []
    },
    "removed": {
        "deb": [
            {
                "name": "linux-headers-5.15.0-1112-kvm",
                "from_version": {
                    "source_package_name": "linux-kvm",
                    "source_package_version": "5.15.0-1112.117",
                    "version": "5.15.0-1112.117"
                },
                "to_version": {
                    "source_package_name": null,
                    "source_package_version": null,
                    "version": null
                },
                "cves": [],
                "launchpad_bugs_fixed": [],
                "changes": [],
                "notes": null,
                "is_version_downgrade": false
            },
            {
                "name": "linux-image-5.15.0-1112-kvm",
                "from_version": {
                    "source_package_name": "linux-signed-kvm",
                    "source_package_version": "5.15.0-1112.117",
                    "version": "5.15.0-1112.117"
                },
                "to_version": {
                    "source_package_name": null,
                    "source_package_version": null,
                    "version": null
                },
                "cves": [],
                "launchpad_bugs_fixed": [],
                "changes": [],
                "notes": null,
                "is_version_downgrade": false
            },
            {
                "name": "linux-kvm-headers-5.15.0-1112",
                "from_version": {
                    "source_package_name": "linux-kvm",
                    "source_package_version": "5.15.0-1112.117",
                    "version": "5.15.0-1112.117"
                },
                "to_version": {
                    "source_package_name": null,
                    "source_package_version": null,
                    "version": null
                },
                "cves": [],
                "launchpad_bugs_fixed": [],
                "changes": [],
                "notes": null,
                "is_version_downgrade": false
            },
            {
                "name": "linux-modules-5.15.0-1112-kvm",
                "from_version": {
                    "source_package_name": "linux-kvm",
                    "source_package_version": "5.15.0-1112.117",
                    "version": "5.15.0-1112.117"
                },
                "to_version": {
                    "source_package_name": null,
                    "source_package_version": null,
                    "version": null
                },
                "cves": [],
                "launchpad_bugs_fixed": [],
                "changes": [],
                "notes": null,
                "is_version_downgrade": false
            }
        ],
        "snap": []
    },
    "notes": "Changelog diff for Ubuntu 22.04 jammy image from daily image serial 20261117 to 20261119",
    "from_series": "jammy",
    "to_series": "jammy",
    "from_serial": "20261117",
    "to_serial": "20261119",
    "from_manifest_filename": "daily_manifest.previous",
    "to_manifest_filename": "manifest.current"
}