In the Linux kernel, the following vulnerability has been resolved: ipvs: fix NULL deref in ip_vs_add_service error path When ip_vs_bind_scheduler() succeeds in ip_vs_add_service(), the local variable sched is set to NULL. If ip_vs_start_estimator() subsequently fails, the out_err cleanup calls ip_vs_unbind_scheduler(svc, sched) with sched == NULL. ip_vs_unbind_scheduler() passes the cur_sched NULL check (because svc->scheduler was set by the successful bind) but then dereferences the NULL sched parameter at sched->done_service, causing a kernel panic at offset 0x30 from NULL. Oops: general protection fault, [..] [#1] PREEMPT SMP KASAN NOPTI KASAN: null-ptr-deref in range [0x0000000000000030-0x0000000000000037] RIP: 0010:ip_vs_unbind_scheduler (net/netfilter/ipvs/ip_vs_sched.c:69) Call Trace: <TASK> ip_vs_add_service.isra.0 (net/netfilter/ipvs/ip_vs_ctl.c:1500) do_ip_vs_set_ctl (net/netfilter/ipvs/ip_vs_ctl.c:2809) nf_setsockopt (net/netfilter/nf_sockopt.c:102) [..] Fix by simply not clearing the local sched variable after a successful bind. ip_vs_unbind_scheduler() already detects whether a scheduler is installed via svc->scheduler, and keeping sched non-NULL ensures the error path passes the correct pointer to both ip_vs_unbind_scheduler() and ip_vs_scheduler_put(). While the bug is older, the problem popups in more recent kernels (6.2), when the new error path is taken after the ip_vs_start_estimator() call.
A vulnerability has been found in chatchat-space Langchain-Chatchat up to 0.3.1.3. Impacted is the function files of the file libs/chatchat-server/chatchat/server/api_server/openai_routes.py of the component OpenAI-Compatible File Upload API. Such manipulation of the argument file.filename leads to time-of-check time-of-use. Access to the local network is required for this attack to succeed. The attack requires a high level of complexity. The exploitability is considered difficult. The exploit has been disclosed to the public and may be used. The project was informed of the problem early through an issue report but has not responded yet.
In the Linux kernel, the following vulnerability has been resolved: net: mana: fix use-after-free in add_adev() error path If auxiliary_device_add() fails, add_adev() jumps to add_fail and calls auxiliary_device_uninit(adev). The auxiliary device has its release callback set to adev_release(), which frees the containing struct mana_adev. Since adev is embedded in struct mana_adev, the subsequent fall-through to init_fail and access to adev->id may result in a use-after-free. Fix this by saving the allocated auxiliary device id in a local variable before calling auxiliary_device_add(), and use that saved id in the cleanup path after auxiliary_device_uninit().
CVE-2026-43015 is a use-after-free vulnerability in the Linux kernel's macb network driver related to clock (clk) handling during PCI glue driver removal. The issue occurs because platform_device_unregister() may still attempt to use registered clocks during runtime resume callbacks, leading to a use-after-free condition. The vulnerability has been addressed by saving pointers to clocks into local variables before the platform device is unregistered to prevent invalid memory access.
CVE-2026-31700 is a time-of-check to time-of-use (TOCTOU) race condition vulnerability in the Linux kernel's net/packet subsystem affecting the tpacket_snd() function when PACKET_VNET_HDR is enabled. The vulnerability arises because the vnet_hdr structure is read directly from a shared mmap'd TX ring buffer without copying to a local stack variable, allowing concurrent userspace modification between validation and use. This flaw was fixed by copying vnet_hdr to a stack-local variable before validation and use, aligning with other kernel consumers of vnet_hdr.
In the Linux kernel, the following vulnerability has been resolved: idpf: fix PREEMPT_RT raw/bh spinlock nesting for async VC handling Switch from using the completion's raw spinlock to a local lock in the idpf_vc_xn struct. The conversion is safe because complete/_all() are called outside the lock and there is no reason to share the completion lock in the current logic. This avoids invalid wait context reported by the kernel due to the async handler taking BH spinlock: [ 805.726977] ============================= [ 805.726991] [ BUG: Invalid wait context ] [ 805.727006] 7.0.0-rc2-net-devq-031026+ #28 Tainted: G S OE [ 805.727026] ----------------------------- [ 805.727038] kworker/u261:0/572 is trying to lock: [ 805.727051] ff190da6a8dbb6a0 (&vport_config->mac_filter_list_lock){+...}-{3:3}, at: idpf_mac_filter_async_handler+0xe9/0x260 [idpf] [ 805.727099] other info that might help us debug this: [ 805.727111] context-{5:5} [ 805.727119] 3 locks held by kworker/u261:0/572: [ 805.727132] #0: ff190da6db3e6148 ((wq_completion)idpf-0000:83:00.0-mbx){+.+.}-{0:0}, at: process_one_work+0x4b5/0x730 [ 805.727163] #1: ff3c6f0a6131fe50 ((work_completion)(&(&adapter->mbx_task)->work)){+.+.}-{0:0}, at: process_one_work+0x1e5/0x730 [ 805.727191] #2: ff190da765190020 (&x->wait#34){+.+.}-{2:2}, at: idpf_recv_mb_msg+0xc8/0x710 [idpf] [ 805.727218] stack backtrace: ... [ 805.727238] Workqueue: idpf-0000:83:00.0-mbx idpf_mbx_task [idpf] [ 805.727247] Call Trace: [ 805.727249] <TASK> [ 805.727251] dump_stack_lvl+0x77/0xb0 [ 805.727259] __lock_acquire+0xb3b/0x2290 [ 805.727268] ? __irq_work_queue_local+0x59/0x130 [ 805.727275] lock_acquire+0xc6/0x2f0 [ 805.727277] ? idpf_mac_filter_async_handler+0xe9/0x260 [idpf] [ 805.727284] ? _printk+0x5b/0x80 [ 805.727290] _raw_spin_lock_bh+0x38/0x50 [ 805.727298] ? idpf_mac_filter_async_handler+0xe9/0x260 [idpf] [ 805.727303] idpf_mac_filter_async_handler+0xe9/0x260 [idpf] [ 805.727310] idpf_recv_mb_msg+0x1c8/0x710 [idpf] [ 805.727317] process_one_work+0x226/0x730 [ 805.727322] worker_thread+0x19e/0x340 [ 805.727325] ? __pfx_worker_thread+0x10/0x10 [ 805.727328] kthread+0xf4/0x130 [ 805.727333] ? __pfx_kthread+0x10/0x10 [ 805.727336] ret_from_fork+0x32c/0x410 [ 805.727345] ? __pfx_kthread+0x10/0x10 [ 805.727347] ret_from_fork_asm+0x1a/0x30 [ 805.727354] </TASK>
In the Linux kernel, the following vulnerability has been resolved: udp: Fix wildcard bind conflict check when using hash2 When binding a udp_sock to a local address and port, UDP uses two hashes (udptable->hash and udptable->hash2) for collision detection. The current code switches to "hash2" when hslot->count > 10. "hash2" is keyed by local address and local port. "hash" is keyed by local port only. The issue can be shown in the following bind sequence (pseudo code): bind(fd1, "[fd00::1]:8888") bind(fd2, "[fd00::2]:8888") bind(fd3, "[fd00::3]:8888") bind(fd4, "[fd00::4]:8888") bind(fd5, "[fd00::5]:8888") bind(fd6, "[fd00::6]:8888") bind(fd7, "[fd00::7]:8888") bind(fd8, "[fd00::8]:8888") bind(fd9, "[fd00::9]:8888") bind(fd10, "[fd00::10]:8888") /* Correctly return -EADDRINUSE because "hash" is used * instead of "hash2". udp_lib_lport_inuse() detects the * conflict. */ bind(fail_fd, "[::]:8888") /* After one more socket is bound to "[fd00::11]:8888", * hslot->count exceeds 10 and "hash2" is used instead. */ bind(fd11, "[fd00::11]:8888") bind(fail_fd, "[::]:8888") /* succeeds unexpectedly */ The same issue applies to the IPv4 wildcard address "0.0.0.0" and the IPv4-mapped wildcard address "::ffff:0.0.0.0". For example, if there are existing sockets bound to "192.168.1.[1-11]:8888", then binding "0.0.0.0:8888" or "[::ffff:0.0.0.0]:8888" can also miss the conflict when hslot->count > 10. TCP inet_csk_get_port() already has the correct check in inet_use_bhash2_on_bind(). Rename it to inet_use_hash2_on_bind() and move it to inet_hashtables.h so udp.c can reuse it in this fix.
The kernel-rt packages provide the Real Time Linux Kernel, which enables fine-tuning for systems with extremely high determinism requirements.
Security Fix(es):
* kernel: Linux kernel:A use-after-free in bridge multicast in br_multicast_port_ctx_init (CVE-2025-38248)
* kernel: Bluetooth: MGMT: Fix possible UAFs (CVE-2025-39981)
* kernel: mlxsw: spectrum_mr: Fix use-after-free when updating multicast route stats (CVE-2025-68800)
* kernel: Linux kernel: Denial of Service via unsafe requeue in rxrpc_recvmsg (CVE-2026-23066)
* kernel: Linux kernel: Local denial of service and memory leak in DAMON sysfs via setup failure (CVE-2026-23144)
* kernel: Linux kernel: Use-after-free in bonding module can cause system crash or arbitrary code execution (CVE-2026-23171)
* kernel: macvlan: fix error recovery in macvlan_common_newlink() (CVE-2026-23209)
* kernel: net/sched: cls_u32: use skb_header_pointer_careful() (CVE-2026-23204)
* kernel: kernel: Privilege escalation or denial of service via use-after-free in nf_tables_addchain() (CVE-2026-23231)
For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.
A vulnerability in the Linux kernel IPv6 implementation allows a local attacker with CAP_NET_RAW capability to cause a kernel panic (denial of service) by triggering an integer overflow in the ip6_datagram_send_ctl() function. This occurs due to a 16-bit length accumulator wrapping when processing multiple IPV6_DSTOPTS control messages, leading to insufficient buffer headroom and a subsequent skb_under_panic() call. The issue affects certain Linux kernel versions and requires local privileges or user namespaces with CAP_NET_RAW. A patch is available to fix this flaw.
CVE-2026-54411 is a timing discrepancy vulnerability in the Linux-PAM pam_userdb module that allows a local or network-adjacent attacker to recover plaintext passwords by measuring authentication response times. This flaw requires the pam_userdb module to be explicitly configured to store and compare credentials in plaintext, which is not the default or recommended setting in Red Hat Enterprise Linux. The impact is limited by the need for repeated authentication attempts and specific non-default configurations. Red Hat has issued an update including patched RPMs for the pam package to address this issue.
CVE-2026-5777 is a high-severity vulnerability in the EGATE Atom 3X Projector caused by the Android Debug Bridge (ADB) service being exposed on the local network without authentication. This allows an unauthenticated attacker on the same network to gain root-level access to the device, resulting in full compromise. The vulnerability is identified as CWE-306 (Missing Authentication for Critical Function). No official patch or remediation guidance is currently available from the vendor. There are no known exploits in the wild at this time.
Multiple vulnerabilities were discovered in the AppArmor Linux kernel Security Module (LSM) and other Linux kernel subsystems affecting the linux-intel-iot-realtime kernel. These flaws could allow an unprivileged local attacker to load, replace, or remove arbitrary AppArmor profiles, potentially causing denial of service, exposure of sensitive kernel memory, local privilege escalation, or container escape. Additional issues affect ARM64 architecture, Cryptographic API, Netfilter, and network traffic control. A security update fixing these issues is available and requires a system reboot and recompilation of third-party kernel modules.
CVE-2026-5684 is a high-severity stack-based buffer overflow vulnerability in the Tenda CX12L router firmware version 16.03.53.12. The flaw exists in the function fromwebExcptypemanFilter within the /goform/webExcptypemanFilter file. Exploitation requires local network access and involves manipulating the 'page' argument to trigger the overflow. The vulnerability has been publicly disclosed, but no official patch or remediation guidance is currently available from the vendor. There are no known exploits in the wild at this time.
CVE-2026-31396 is a use-after-free vulnerability in the Linux kernel's macb network driver related to the Precision Time Protocol (PTP) clock. The PTP clock is registered each time the network interface is opened and destroyed when it is closed. However, it can still be accessed via the ethtool get_ts_info call while the interface is present but after the clock has been freed, leading to a use-after-free condition. This flaw can cause kernel memory corruption and potentially allow an attacker with local privileges to compromise system integrity.
CVE-2026-5457 is a medium severity vulnerability in the PropertyGuru AgentNet Singapore App for Android versions up to 23.7.10. The issue involves the use of hard-coded cryptographic keys within the app's BuildConfig.java file, specifically related to the SEGMENT_ANDROID_WRITE_KEY and SEGMENT_TOS_WRITE_KEY arguments. Exploitation requires local access to the device. The vendor has not responded to the disclosure, and no official patch or remediation guidance is currently available. The vulnerability has a CVSS 4.8 score, indicating moderate risk. There are no known exploits in the wild at this time.
CVE-2026-35540 is a medium severity vulnerability in Roundcube Webmail versions before 1.6.14. It involves insufficient sanitization of CSS in HTML email messages, which may allow server-side request forgery (SSRF) or information disclosure if stylesheet links reference local network hosts. The vulnerability affects Roundcube Webmail 1.6.0 and has a CVSS score of 5.4. No official patch or remediation information is currently available from the vendor. There are no known exploits in the wild at this time.
A flaw was found in firewalld. A local unprivileged user can exploit this vulnerability by mis-authorizing two runtime D-Bus (Desktop Bus) setters, setZoneSettings2 and setPolicySettings. This mis-authorization allows the user to modify the runtime firewall state without proper authentication, leading to unauthorized changes in network security configurations.
Frigate is a network video recorder (NVR) with realtime local object detection for IP cameras. In version 0.17.0, a low-privilege authenticated user restricted to one camera can access snapshots from other cameras. This is possible through a chain of two authorization problems: `/api/timeline` returns timeline entries for cameras outside the caller's allowed camera set, then `/api/events/{event_id}/snapshot-clean.webp` declares `Depends(require_camera_access)` but never actually validates `event.camera` after looking up the event. Together, this allows a restricted user to enumerate event IDs from unauthorized cameras and then fetch clean snapshots for those events. Version 0.17.1 fixes the issue.