Vulnerabilidades

*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> Bluetooth: fix UAF in l2cap_sock_cleanup_listen() vs l2cap_conn_del()<br /> <br /> bt_accept_dequeue() unlinks a not-yet-accepted child from the parent<br /> accept queue and release_sock()s it before returning, so the returned<br /> sk has no caller reference and is unlocked.<br /> <br /> l2cap_sock_cleanup_listen() walks these children on listening-socket<br /> close. A concurrent HCI disconnect drives hci_rx_work -&gt;<br /> l2cap_conn_del() which runs l2cap_chan_del() + l2cap_sock_kill() and<br /> frees the child sk and its l2cap_chan; cleanup_listen() then uses both:<br /> <br /> BUG: KASAN: slab-use-after-free in l2cap_sock_kill<br /> l2cap_sock_kill / l2cap_sock_cleanup_listen / __x64_sys_close<br /> Freed by: l2cap_conn_del -&gt; l2cap_sock_close_cb -&gt; l2cap_sock_kill<br /> <br /> This is distinct from the two fixes already in this area: commit<br /> e83f5e24da741 ("Bluetooth: serialize accept_q access") serialises the<br /> accept_q list/poll and takes temporary refs inside bt_accept_dequeue(),<br /> and CVE-2025-39860 serialises the userspace close()/accept() race by<br /> calling cleanup_listen() under lock_sock() in l2cap_sock_release().<br /> Neither covers l2cap_conn_del() running from hci_rx_work, so this UAF<br /> still reproduces on current bluetooth/master.<br /> <br /> Take the reference at the source: bt_accept_dequeue() does sock_hold()<br /> while sk is still locked, before release_sock(); callers sock_put().<br /> cleanup_listen() pins the chan with l2cap_chan_hold_unless_zero() under<br /> a brief child sk lock (serialising vs l2cap_sock_teardown_cb()), drops<br /> it before l2cap_chan_lock(), and skips a duplicate l2cap_sock_kill() on<br /> SOCK_DEAD. conn-&gt;lock is not taken here: cleanup_listen() runs under<br /> the parent sk lock and that would invert<br /> conn-&gt;lock -&gt; chan-&gt;lock -&gt; sk_lock (lockdep).<br /> <br /> KASAN/SMP: an unprivileged listen/close vs HCI-disconnect race produced<br /> 12 use-after-free reports per run before this change; 0, and no lockdep<br /> report, over 1600+ raced iterations after it on bluetooth/master.

*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> Bluetooth: L2CAP: use chan timer to close channels in cleanup_listen()<br /> <br /> l2cap_chan_close() removes the channel from conn-&gt;chan_l, which<br /> must be done under conn-&gt;lock. cleanup_listen() runs under the<br /> parent sk_lock, so acquiring conn-&gt;lock would invert the<br /> established conn-&gt;lock -&gt; chan-&gt;lock -&gt; sk_lock order.<br /> <br /> Instead of calling l2cap_chan_close() directly, schedule<br /> l2cap_chan_timeout with delay 0 to close the channel<br /> asynchronously. The timeout handler already acquires conn-&gt;lock<br /> and chan-&gt;lock in the correct order.<br /> <br /> The timer is only armed when chan-&gt;conn is still set: if it is<br /> already NULL, l2cap_conn_del() has already processed this channel<br /> (l2cap_chan_del + l2cap_sock_teardown_cb + l2cap_sock_close_cb),<br /> so there is nothing left to do. If l2cap_conn_del() races in<br /> after the timer is armed, __clear_chan_timer() inside<br /> l2cap_chan_del() cancels it; if the timer has already fired, the<br /> handler returns harmlessly because chan-&gt;conn was cleared.

*** Pendiente de traducción *** A malicious actor with access to the network and low privileges could exploit an Improper Input Validation vulnerability found in UniFi Access Application to execute a Command Injection on the host device.

*** Pendiente de traducción *** A malicious actor with access to the network and low privileges could exploit a series of authenticated SQL Injection vulnerabilities found in UniFi Talk Application to escalate privileges on the host device.

*** Pendiente de traducción *** A malicious actor with access to the network could exploit an Improper Access Control vulnerability found in UniFi Connect Application to execute a Command Injection on the host device.

*** Pendiente de traducción *** The Minifilter communication port for driver `GFAC_Sys_x64.sys` in Little Orbit GFAC allows a local attacker to access privileged driver functionality via a communication interface that lacks appropriate access restrictions.

*** Pendiente de traducción *** An improper validation vulnerability for driver `GFAC_Sys_x64.sys` in Little Orbit GFAC allows a local attacker to escalate privileges to SYSTEM and execute arbitrary code in kernel mode via crafted messages sent through a Minifilter communication port.

*** Pendiente de traducción *** A NULL pointer dereference vulnerability for driver `GFAC_Sys_x64.sys` in Little Orbit GFAC allows a local attacker to cause a denial of service via crafted requests that trigger a system crash.

*** Pendiente de traducción *** Missing authentication for critical function vulnerability in TR7 Cyber ​​Defense Inc. WAF-ASP allows Authentication Abuse.<br /> <br /> This issue affects WAF-ASP: from v1.0.324.900 before v1.4.0.117.

*** Pendiente de traducción *** The Divi Form Builder plugin for WordPress is vulnerable to Arbitrary File Upload leading to Remote Code Execution in all versions up to and including 5.1.8. This is due to insufficient file extension validation in the do_image_upload() function where user-supplied input from the acceptFileTypes POST parameter is directly interpolated into a regular expression used to validate uploaded files. Attackers can specify PHP-executable extensions such as .phtml, .phar, .php5, or .php7 to bypass the plugin&amp;#39;s .htaccess protection which only blocks .php files specifically. Additionally, on Nginx-based servers, the .htaccess protection is completely ineffective as Nginx does not process .htaccess files. This makes it possible for unauthenticated attackers (who can obtain a nonce from any public page containing a form) to upload executable PHP files to the publicly accessible /wp-content/uploads/de_fb_uploads/ directory and achieve Remote Code Execution by accessing the uploaded file via HTTP. The vulnerability was partially patched in version 5.1.3.

*** Pendiente de traducción *** luci-app-travelmate (and the travelmate package) contain a privilege-escalation flaw: a LuCI/rpcd session holding the luci-app-travelmate write ACL is granted config-wide UCI write access to the travelmate configuration. While the LuCI UI restricts the auto-login script picker to /etc/travelmate/*.login, this is only a frontend restriction. The backend travelmate service (running as root) reads the raw UCI &amp;#39;script&amp;#39; and &amp;#39;script_args&amp;#39; values and executes the configured path when the captive-portal auto-login branch (f_check() in travelmate-functions.sh) is reached. An attacker with delegated write permissions can set script to /bin/sh and script_args to attacker-controlled arguments, resulting in arbitrary command execution as root. Confirmed in luci-app-travelmate/travelmate 2.4.5-r3; the sink is still present in travelmate 2.4.6-1 and no patched version is known.

*** Pendiente de traducción *** PraisonAI before 0.1.7 fails to validate that project_id in issue create and update request bodies belongs to the URL workspace. An attacker can create issues referencing projects from other workspaces, causing cross-tenant data pollution in project statistics aggregation without workspace constraints.