Vulnerabilities

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> scsi: target: iscsi: Fix use-after-free in iscsit_dec_conn_usage_count()<br /> <br /> In iscsit_dec_conn_usage_count(), the function calls complete() while<br /> holding the conn-&gt;conn_usage_lock. As soon as complete() is invoked, the<br /> waiter (such as iscsit_close_connection()) may wake up and proceed to free<br /> the iscsit_conn structure.<br /> <br /> If the waiter frees the memory before the current thread reaches<br /> spin_unlock_bh(), it results in a KASAN slab-use-after-free as the function<br /> attempts to release a lock within the already-freed connection structure.<br /> <br /> Fix this by releasing the spinlock before calling complete().

The Advanced AJAX Product Filters plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 3.1.9.6 via deserialization of untrusted input in the shortcode_check function within the Live Composer compatibility layer. This makes it possible for authenticated attackers, with Author-level access and above, to inject a PHP Object. No known POP chain is present in the vulnerable software, which means this vulnerability has no impact unless another plugin or theme containing a POP chain is installed on the site. If a POP chain is present via an additional plugin or theme installed on the target system, it may allow the attacker to perform actions like delete arbitrary files, retrieve sensitive data, or execute code depending on the POP chain present. Note: This vulnerability requires the Live Composer plugin to also be installed and active.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> md: suspend array while updating raid_disks via sysfs<br /> <br /> In raid1_reshape(), freeze_array() is called before modifying the r1bio<br /> memory pool (conf-&gt;r1bio_pool) and conf-&gt;raid_disks, and<br /> unfreeze_array() is called after the update is completed.<br /> <br /> However, freeze_array() only waits until nr_sync_pending and<br /> (nr_pending - nr_queued) of all buckets reaches zero. When an I/O error<br /> occurs, nr_queued is increased and the corresponding r1bio is queued to<br /> either retry_list or bio_end_io_list. As a result, freeze_array() may<br /> unblock before these r1bios are released.<br /> <br /> This can lead to a situation where conf-&gt;raid_disks and the mempool have<br /> already been updated while queued r1bios, allocated with the old<br /> raid_disks value, are later released. Consequently, free_r1bio() may<br /> access memory out of bounds in put_all_bios() and release r1bios of the<br /> wrong size to the new mempool, potentially causing issues with the<br /> mempool as well.<br /> <br /> Since only normal I/O might increase nr_queued while an I/O error occurs,<br /> suspending the array avoids this issue.<br /> <br /> Note: Updating raid_disks via ioctl SET_ARRAY_INFO already suspends<br /> the array. Therefore, we suspend the array when updating raid_disks<br /> via sysfs to avoid this issue too.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> wifi: iwlwifi: Implement settime64 as stub for MVM/MLD PTP<br /> <br /> Since commit dfb073d32cac ("ptp: Return -EINVAL on ptp_clock_register if<br /> required ops are NULL"), PTP clock registered through ptp_clock_register<br /> is required to have ptp_clock_info.settime64 set, however, neither MVM<br /> nor MLD&amp;#39;s PTP clock implementation sets it, resulting in warnings when<br /> the interface starts up, like<br /> <br /> WARNING: drivers/ptp/ptp_clock.c:325 at ptp_clock_register+0x2c8/0x6b8, CPU#1: wpa_supplicant/469<br /> CPU: 1 UID: 0 PID: 469 Comm: wpa_supplicant Not tainted 6.18.0+ #101 PREEMPT(full)<br /> ra: ffff800002732cd4 iwl_mvm_ptp_init+0x114/0x188 [iwlmvm]<br /> ERA: 9000000002fdc468 ptp_clock_register+0x2c8/0x6b8<br /> iwlwifi 0000:01:00.0: Failed to register PHC clock (-22)<br /> <br /> I don&amp;#39;t find an appropriate firmware interface to implement settime64()<br /> for iwlwifi MLD/MVM, thus instead create a stub that returns<br /> -EOPTNOTSUPP only, suppressing the warning and allowing the PTP clock to<br /> be registered.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> wifi: mac80211: don&amp;#39;t WARN for connections on invalid channels<br /> <br /> It&amp;#39;s not clear (to me) how exactly syzbot managed to hit this,<br /> but it seems conceivable that e.g. regulatory changed and has<br /> disabled a channel between scanning (channel is checked to be<br /> usable by cfg80211_get_ies_channel_number) and connecting on<br /> the channel later.<br /> <br /> With one scenario that isn&amp;#39;t covered elsewhere described above,<br /> the warning isn&amp;#39;t good, replace it with a (more informative)<br /> error message.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> LoongArch: Set correct protection_map[] for VM_NONE/VM_SHARED<br /> <br /> For 32BIT platform _PAGE_PROTNONE is 0, so set a VMA to be VM_NONE or<br /> VM_SHARED will make pages non-present, then cause Oops with kernel page<br /> fault.<br /> <br /> Fix it by set correct protection_map[] for VM_NONE/VM_SHARED, replacing<br /> _PAGE_PROTNONE with _PAGE_PRESENT.

The Ultimate Member – User Profile, Registration, Login, Member Directory, Content Restriction &amp; Membership Plugin plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the filter parameters (e.g., &amp;#39;filter_first_name&amp;#39;) in all versions up to, and including, 2.11.1 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link.

An arbitrary code execution vulnerability exists in the Code Stream directive functionality of OpenCFD OpenFOAM 2506. A specially crafted OpenFOAM simulation file can lead to arbitrary code execution. An attacker can provide a malicious file to trigger this vulnerability.

Path traversal vulnerability in the AMR Printer Management 1.01 Beta web service, which allows remote attackers to read arbitrary files from the underlying Windows system by using specially crafted path traversal sequences in requests directed to the web management service. The service is accessible without authentication and runs with elevated privileges, amplifying the impact of the vulnerability. An attacker can exploit this condition to access sensitive and privileged files on the system using path traversal payloads. Successful exploitation of this vulnerability could lead to the unauthorized disclosure of internal system information, compromising the confidentiality of the affected environment.

A vulnerability was detected in ChaiScript up to 6.1.0. The impacted element is the function chaiscript::str_less::operator of the file include/chaiscript/chaiscript_defines.hpp. The manipulation results in use after free. The attack requires a local approach. The attack requires a high level of complexity. The exploitability is regarded as difficult. The exploit is now public and may be used. The project was informed of the problem early through an issue report but has not responded yet.

A weakness has been identified in huggingface smolagents 1.24.0. Impacted is the function requests.get/requests.post of the component LocalPythonExecutor. Executing a manipulation can lead to server-side request forgery. It is possible to launch the attack remotely. The exploit has been made available to the public and could be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.

Reflected Cross-Site Scripting (XSS) vulnerability in the Graylog Web Interface console, version 2.2.3, caused by a lack of proper sanitization and escaping in HTML output. Several endpoints include segments of the URL directly in the response without applying output encoding, allowing an attacker to inject and execute arbitrary JavaScript code when a user visits a specially crafted URL. Exploitation of this vulnerability may allow script execution in the victim&amp;#39;s browser and limited manipulation of the affected user&amp;#39;s session context, through the  &amp;#39;/system/index_sets/&amp;#39; endpoint.