Vulnerabilities

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> Bluetooth: btnxpuart: Fix out-of-bounds firmware read in nxp_recv_fw_req_v3()<br /> <br /> During the v3 firmware download the controller sends a v3_data_req with a<br /> 32 bit offset and a 16 bit len. nxp_recv_fw_req_v3() checks only the lower<br /> bound of the offset and then sends firmware from that offset.<br /> <br /> nxpdev-&gt;fw_dnld_v3_offset = offset - nxpdev-&gt;fw_v3_offset_correction;<br /> serdev_device_write_buf(nxpdev-&gt;serdev, nxpdev-&gt;fw-&gt;data +<br /> nxpdev-&gt;fw_dnld_v3_offset, len);<br /> <br /> Nothing checks that fw_dnld_v3_offset + len stays within nxpdev-&gt;fw-&gt;size,<br /> so a controller that asks for an offset or length past the firmware image<br /> makes the driver read past the end of nxpdev-&gt;fw-&gt;data and send that<br /> memory back over UART.<br /> <br /> nxp_recv_fw_req_v1() already bounds the same write. Add the equivalent<br /> check to the v3 path, reject the request when it falls outside the firmware<br /> image, and zero len on the error path so the fw_v3_prev_sent bookkeeping at<br /> free_skb stays consistent.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> Bluetooth: btmtksdio: fix infinite loop in btmtksdio_txrx_work()<br /> <br /> Every once in a while we see a hung btmtksdio_flush() task:<br /> <br /> INFO: task kworker/u17:0:189 blocked for more than 122 seconds.<br /> __cancel_work_timer+0x3f4/0x460<br /> cancel_work_sync+0x1c/0x2c<br /> btmtksdio_flush+0x2c/0x40<br /> hci_dev_open_sync+0x10c4/0x2190<br /> [..]<br /> <br /> It all boils down to incorrect time_is_before_jiffies() usage in<br /> btmtksdio_txrx_work(). The btmtksdio_txrx_work() loop is expected<br /> to be terminated if running for longer than 5*HZ. However the<br /> timeout check is twisted: time_is_before_jiffies(old_jiffies + 5*HZ)<br /> evaluates to true when old_jiffies + 5*HZ is in the past i.e. when a<br /> timeout has occurred. Using OR with time_is_before_jiffies(txrx_timeout)<br /> means that:<br /> - before the 5-second timeout: the condition is `int_status || false`,<br /> so it loops as long as there are pending interrupts.<br /> - after the 5-second timeout: the condition becomes `int_status || true`,<br /> which is always true.<br /> <br /> When the loop becomes infinite btmtksdio_txrx_work() loop never<br /> terminates and never releases the SDIO host.<br /> <br /> Fix loop termination condition to actually enforce a 5*HZ timeout.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> Bluetooth: fix UAF in bt_accept_dequeue()<br /> <br /> bt_accept_get() takes a temporary reference before dropping the accept<br /> queue lock. bt_accept_dequeue() currently drops that reference before<br /> bt_accept_unlink(), leaving only the queue reference.<br /> <br /> bt_accept_unlink() drops the queue reference. The subsequent<br /> sock_hold() therefore accesses freed memory if it was the final<br /> reference, as observed by KASAN during listening L2CAP socket cleanup.<br /> <br /> Retain the temporary queue-walk reference through unlink and hand it to<br /> the caller on success. Drop it explicitly on the closed and<br /> not-yet-connected paths.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> Bluetooth: bnep: pin L2CAP connection during netdev registration<br /> <br /> bnep_add_connection() reads the L2CAP connection without holding the<br /> channel lock, then passes its HCI device to register_netdev(). Controller<br /> teardown can clear and release that connection concurrently, leaving the<br /> network device registration path to dereference a freed parent device.<br /> <br /> Take a reference to the L2CAP connection while holding the channel lock.<br /> Retain it until register_netdev() has taken the parent device reference.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> netfilter: flowtable: IPIP tunnel hardware offload is not yet support<br /> <br /> No driver supports for IPIP tunnels yet, give up early on setting up the<br /> hardware offload for this scenario.<br /> <br /> This patch adds a stub that can be enhanced to add more configuration<br /> that are currently not supported. As of now, the offload work is<br /> enqueued to the worker, then ignored if the hardware offload<br /> configuration is not supported.<br /> <br /> Check the NF_FLOW_HW flag to know if this entry was already tried once<br /> to be offloaded so this is not retried on refresh when unsupported. Move<br /> NF_FLOW_HW flag check to nf_flow_offload_add(). If this NF_FLOW_HW flag<br /> is unset the _del and _stats variants are never called.<br /> <br /> This can be updated later on to skip hardware offload work to be queued<br /> in case hardware offload does not support it.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> netfilter: ebtables: terminate table name before find_table_lock()<br /> <br /> update_counters() and compat_update_counters() forward a user-supplied<br /> 32-byte table name to find_table_lock() without NUL-terminating it. On a<br /> lookup miss, find_inlist_lock() calls try_then_request_module(..., "%s%s",<br /> "ebtable_", name), and vsnprintf() reads past the name field and the<br /> stack object until it hits a zero byte.<br /> <br /> BUG: KASAN: stack-out-of-bounds in string (lib/vsprintf.c:648 lib/vsprintf.c:730)<br /> Read of size 1 at addr ffff8880119dfb20 by task exploit/147<br /> Call Trace:<br /> ...<br /> string (lib/vsprintf.c:648 lib/vsprintf.c:730)<br /> vsnprintf (lib/vsprintf.c:2945)<br /> __request_module (kernel/module/kmod.c:150)<br /> do_update_counters.isra.0 (net/bridge/netfilter/ebtables.c:371 net/bridge/netfilter/ebtables.c:380)<br /> update_counters (net/bridge/netfilter/ebtables.c:1440)<br /> do_ebt_set_ctl (net/bridge/netfilter/ebtables.c:2573)<br /> nf_setsockopt (net/netfilter/nf_sockopt.c:101)<br /> ip_setsockopt (net/ipv4/ip_sockglue.c:1424)<br /> raw_setsockopt (net/ipv4/raw.c:847)<br /> __sys_setsockopt (net/socket.c:2393)<br /> ...<br /> <br /> compat_do_replace() shares the same unterminated name via<br /> compat_copy_ebt_replace_from_user(); terminate it there too so all<br /> find_table_lock() callers behave alike. The other callers already<br /> terminate the name after the copy.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> netfilter: ebtables: module names must be null-terminated<br /> <br /> We need to explicitly check the length, else we may pass non-null<br /> terminated string to request_module().

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> ksmbd: fix UAF of struct file_lock in SMB2_LOCK deferred-lock cancellation<br /> <br /> When a blocking byte-range lock request is deferred in the<br /> FILE_LOCK_DEFERRED path, ksmbd registers the asynchronous work into<br /> the connection&amp;#39;s async_requests list via setup_async_work(). The cancel<br /> callback smb2_remove_blocked_lock() holds a reference to the flock.<br /> <br /> If the lock waiter is subsequently woken up but the work state is no<br /> longer KSMBD_WORK_ACTIVE (e.g., due to a concurrent cancellation), the<br /> cleanup path calls locks_free_lock(flock) without dequeuing the work from<br /> the async_requests list. Concurrently, smb2_cancel() walks the list<br /> under conn-&gt;request_lock and invokes the cancel callback, which then<br /> dereferences the already freed &amp;#39;flock&amp;#39;. This leads to a slab-use-after-free<br /> inside __wake_up_common.<br /> <br /> Fix this by restructuring the cleanup logic after the worker returns<br /> from ksmbd_vfs_posix_lock_wait(). Move list_del(&amp;smb_lock-&gt;llist) and<br /> release_async_work(work) to the top of the cleanup block. This guarantees<br /> that the async work is completely dequeued and serialized under<br /> conn-&gt;request_lock before locks_free_lock(flock) is called, rendering<br /> the flock unreachable for any concurrent smb2_cancel().

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> ksmbd: serialize QUERY_DIRECTORY requests per file<br /> <br /> smb2_query_dir() stores a pointer to its stack-allocated private data in<br /> the ksmbd_file readdir_data. Concurrent QUERY_DIRECTORY requests using the<br /> same file handle can overwrite this pointer while an iterate_dir() callback<br /> is still using it, resulting in a stack use-after-free.<br /> <br /> Add a per-file mutex and hold it while accessing the shared directory<br /> enumeration state. The lock covers scan restart, dot entry state,<br /> readdir_data setup and iteration, and response construction. This prevents<br /> another request from replacing readdir_data.private before the current<br /> request has finished using it and also serializes the shared file position.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> ksmbd: add a permission check for FSCTL_SET_ZERO_DATA<br /> <br /> FSCTL_SET_ZERO_DATA in smb2_ioctl() destroys file data via<br /> ksmbd_vfs_zero_data() -&gt; vfs_fallocate(PUNCH_HOLE/ZERO_RANGE) after<br /> checking only the share-level KSMBD_TREE_CONN_FLAG_WRITABLE, with no<br /> per-handle access check. A handle opened with only FILE_WRITE_ATTRIBUTES<br /> still yields an FMODE_WRITE filp (FILE_WRITE_ATTRIBUTES is part of<br /> FILE_WRITE_DESIRE_ACCESS_LE, so smb2_create_open_flags() opens it<br /> O_WRONLY), so the vfs_fallocate FMODE_WRITE check does not stop it; only<br /> the missing fp-&gt;daccess gate would. Reproduced on mainline 7.1-rc7 with<br /> KASAN by an authenticated SMB client: a FILE_WRITE_ATTRIBUTES-only handle<br /> zeroed 4096 bytes of file data it had no FILE_WRITE_DATA right to<br /> (6/6; a FILE_READ_DATA-only handle was correctly denied).<br /> <br /> This is the unfixed sibling of commit cc57232cae23 ("ksmbd: fix FSCTL<br /> permission bypass by adding a permission check for FSCTL_SET_SPARSE").<br /> Because SET_ZERO_DATA writes data (not an attribute), require<br /> FILE_WRITE_DATA.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> ksmbd: add permission checks for FSCTL_DUPLICATE_EXTENTS_TO_FILE<br /> <br /> The FSCTL_DUPLICATE_EXTENTS_TO_FILE arm of smb2_ioctl() overwrites the<br /> destination file&amp;#39;s data via vfs_clone_file_range() with neither the<br /> share-level KSMBD_TREE_CONN_FLAG_WRITABLE check nor a per-handle<br /> fp-&gt;daccess check that the other write-bearing arms carry. A client can<br /> overwrite destination data on a read-only share, or from a handle opened<br /> with only FILE_WRITE_ATTRIBUTES (which still yields an FMODE_WRITE filp).<br /> FILE_WRITE_ATTRIBUTES-only destination handle overwrote the file&amp;#39;s data via<br /> the clone. Add both checks, matching the FSCTL_SET_SPARSE permission fix;<br /> require FILE_WRITE_DATA since this writes data.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> ksmbd: prevent path traversal bypass by restricting caseless retry<br /> <br /> ksmbd_vfs_path_lookup() enforces LOOKUP_BENEATH to restrict path<br /> resolution within the share root. When a crafted path attempts to<br /> escape the share boundary using parent-directory components (&amp;#39;..&amp;#39;),<br /> vfs_path_parent_lookup() detects this and immediately fails,<br /> returning -EXDEV.<br /> <br /> However, a bug exists in __ksmbd_vfs_kern_path() under caseless mode.<br /> The function fails to intercept the -EXDEV error and erroneously<br /> falls through to the caseless retry logic, which is intended only<br /> for genuinely missing files. During this retry process, the path<br /> is reconstructed, leading to an unintended LOOKUP_BENEATH bypass<br /> that allows write-capable users to create zero-length files or<br /> directories outside the exported share.<br /> <br /> Fix this by ensuring that the execution only proceeds to the caseless<br /> lookup retry when the error is specifically -ENOENT. Any other errors,<br /> such as -EXDEV from a path traversal attempt, must be returned immediately.