A security researcher discovered 15 potential Linux Kernel vulnerabilities related to race conditions in the Virtual File System (VFS) layer, focusing on non-atomic file operations such as rename and chown. These flaws could allow local privilege escalation (LPE) by exploiting timing windows where security checks and critical operations are not atomic. The researcher developed a proof-of-concept exploit and a real-time mitigation based on CPU time monitoring but faced dismissal from Google’s bug bounty program. No official patches or CVEs exist yet, and no known exploits are in the wild. The vulnerabilities stem from architectural oversights in kernel transaction atomicity, posing critical risks to system integrity and security. European organizations relying on Linux systems could be significantly impacted, especially those with high-value targets or sensitive data. Immediate mitigation involves kernel-level atomic operation fixes and monitoring for abnormal CPU usage during vulnerable operations. Countries with large Linux deployments and strategic infrastructure are most at risk. The threat severity is assessed as critical due to the potential for full system compromise without user interaction or authentication.
Multiple London councils experienced disruption to their IT systems due to a cyberattack reported in late November 2025. The attack affected various council services, causing operational interruptions and potential data access issues. While specific technical details and attack vectors have not been disclosed, the incident is classified as high severity due to its impact on public sector infrastructure. No known exploits or vulnerabilities have been publicly identified in relation to this attack. European organizations, especially local government bodies, should be alert to similar threats targeting critical municipal services. Mitigation should focus on enhancing incident response capabilities, network segmentation, and continuous monitoring of council IT environments. The UK is the most directly affected country, with potential spillover risks to other European nations with similar council IT infrastructures. Given the disruption scale and public service impact, the suggested severity is high. Defenders should prioritize rapid detection, containment, and recovery measures to minimize service downtime and data compromise risks.
Sha1-Hulud is a newly identified cyber threat involving supply chain compromise and covert command and control (C2) communications using application layer protocols. Attackers exploit link-local IP addresses such as 169.254.169.254 and 169.254.170.2, commonly associated with cloud metadata services, to bypass perimeter defenses and blend malicious traffic with legitimate communications. A JavaScript component named bun_environment.js has been identified as part of the attack chain.
Insufficient validation within Xilinx Run Time framework could allow a local attacker to escalate privileges from user space to kernel space, potentially compromising confidentiality, integrity, and/or availability.
CVE-2025-52539 is a high-severity stack-based buffer overflow vulnerability in AMD's Xilinx Run Time (XRT) environment. It allows a local attacker to read or corrupt data via the advanced extensible interface (AXI), potentially impacting confidentiality, integrity, and availability. The vulnerability requires local access but no privileges or user interaction. Exploitation could lead to data leakage or system disruption. No known exploits are currently reported in the wild. European organizations using XRT in FPGA or hardware acceleration deployments are at risk. Mitigation involves applying vendor patches once available and restricting local access to trusted users. Countries with significant industrial, telecommunications, and research sectors using Xilinx products are more likely to be affected. The CVSS score is 7.3, indicating a high severity threat.
In the Linux kernel, the following vulnerability has been resolved: scsi: pm80xx: Fix array-index-out-of-of-bounds on rmmod Since commit f7b705c238d1 ("scsi: pm80xx: Set phy_attached to zero when device is gone") UBSAN reports: UBSAN: array-index-out-of-bounds in drivers/scsi/pm8001/pm8001_sas.c:786:17 index 28 is out of range for type 'pm8001_phy [16]' on rmmod when using an expander. For a direct attached device, attached_phy contains the local phy id. For a device behind an expander, attached_phy contains the remote phy id, not the local phy id. I.e. while pm8001_ha will have pm8001_ha->chip->n_phy local phys, for a device behind an expander, attached_phy can be much larger than pm8001_ha->chip->n_phy (depending on the amount of phys of the expander). E.g. on my system pm8001_ha has 8 phys with phy ids 0-7. One of the ports has an expander connected. The expander has 31 phys with phy ids 0-30. The pm8001_ha->phy array only contains the phys of the HBA. It does not contain the phys of the expander. Thus, it is wrong to use attached_phy to index the pm8001_ha->phy array for a device behind an expander. Thus, we can only clear phy_attached for devices that are directly attached.
In the Linux kernel, the following vulnerability has been resolved: net/ip6_tunnel: Prevent perpetual tunnel growth Similarly to ipv4 tunnel, ipv6 version updates dev->needed_headroom, too. While ipv4 tunnel headroom adjustment growth was limited in commit 5ae1e9922bbd ("net: ip_tunnel: prevent perpetual headroom growth"), ipv6 tunnel yet increases the headroom without any ceiling. Reflect ipv4 tunnel headroom adjustment limit on ipv6 version. Credits to Francesco Ruggeri, who was originally debugging this issue and wrote local Arista-specific patch and a reproducer.
Time-of-check time-of-use race condition for some ACAT before version 3.13 within Ring 3: User Applications may allow a denial of service. Unprivileged software adversary with an authenticated user combined with a high complexity attack may enable denial of service. This result may potentially occur via local access when attack requirements are not present without special internal knowledge and requires active user interaction. The potential vulnerability may impact the confidentiality (none), integrity (none) and availability (high) of the vulnerable system, resulting in subsequent system confidentiality (none), integrity (none) and availability (none) impacts.
CVE-2025-40092 is a high-severity vulnerability in the Linux kernel's USB gadget function (f_ncm). It involves improper error handling in the bind path, where a stale notify request is freed incorrectly after a bind/unbind cycle, leading to a NULL pointer dereference. This flaw can cause kernel crashes and potentially allow an attacker with local privileges to compromise system integrity. The issue affects multiple Linux kernel versions prior to fixed releases in the 5.15.0 series. A patch is available and has been incorporated in various updated kernel versions.
A vulnerability in the Linux kernel's perf subsystem for ARM SPE was fixed by preventing an overflow in the PERF_IDX2OFF() macro. The issue involved improper casting of nr_pages, which could cause overflow when handling large AUX buffer sizes of 2 GiB or more. This flaw was addressed by casting nr_pages to unsigned long. Multiple versions of the linux-azure kernel prior to specific fixed releases are affected. The vulnerability has a high severity score and could allow an attacker with local privileges to compromise system confidentiality, integrity, and availability.
A use-after-free vulnerability was discovered and fixed in the Linux kernel's smc subsystem, specifically in the __pnet_find_base_ndev() function. The flaw occurs when a network device (net_device) is freed before its reference count is properly held, leading to unsafe memory access during connection setup. This issue was reported by syzbot and affects multiple kernel versions prior to the fixed releases. The vulnerability has a high severity score and could allow an attacker with local privileges to compromise system confidentiality, integrity, and availability. Official patches have been released to address this flaw.
CVE-2025-40018 is a use-after-free vulnerability in the Linux kernel's IP Virtual Server (ipvs) FTP module. The flaw occurs during network namespace cleanup when the ip_vs_ftp unregister function is called prematurely before all connections with valid application pointers are flushed. This can lead to memory corruption and potentially allow an attacker with local privileges to compromise system integrity. The issue has been fixed by deferring the unregister operation until all connections are properly cleaned up. Multiple Linux kernel versions are affected, and patches have been released.
A high-severity vulnerability (CVE-2025-40019) in the Linux kernel's cryptographic ESSIV implementation was fixed by moving the ssize check to the start of the essiv_aead_crypt function. This ensures proper validation for decryption and in-place encryption operations. The flaw affected multiple Ubuntu kernel versions prior to 5.4.0-1154.164~18.04.1 and others. Updates addressing this issue are available for various Ubuntu releases, including 18.04 LTS and 20.04 LTS. Users must apply these updates and reboot to fully mitigate the risk. The vulnerability could potentially allow an attacker with local privileges to compromise system security.
Multiple security vulnerabilities were found in the Linux kernel version linux-realtime-6.14, including a significant flaw affecting some AMD processors that may allow local attackers to infer data from previous stores, potentially leaking privileged information. These vulnerabilities impact numerous kernel subsystems and architectures, posing a risk of system compromise. A patch is available to address these issues.
CVE-2025-39993 is a use-after-free vulnerability in the Linux kernel's media remote control (rc) subsystem, specifically in the iMON driver. The flaw arises because the driver improperly releases USB device references during disconnect without coordinating with ongoing operations, leading to potential use-after-free conditions. This can cause system crashes or allow an attacker with local privileges to compromise system integrity. The issue has been fixed by adding proper synchronization and early exit checks in affected functions. Multiple Linux kernel versions are affected, and patches are available.
CVE-2025-9970 is a medium severity vulnerability in ABB MConfig up to version 1.4.9.21, involving cleartext storage of sensitive information in memory. This weakness (CWE-316) could potentially expose sensitive data during runtime. The vulnerability requires local access with high attack complexity and privileges, and user interaction is needed for exploitation. No known exploits are reported in the wild. There is no information about an available patch or official remediation from the vendor at this time.
In the Linux kernel, the following vulnerability has been resolved: crypto: ccp - Always pass in an error pointer to __sev_platform_shutdown_locked() When 9770b428b1a2 ("crypto: ccp - Move dev_info/err messages for SEV/SNP init and shutdown") moved the error messages dumping so that they don't need to be issued by the callers, it missed the case where __sev_firmware_shutdown() calls __sev_platform_shutdown_locked() with a NULL argument which leads to a NULL ptr deref on the shutdown path, during suspend to disk: #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page PGD 0 P4D 0 Oops: Oops: 0000 [#1] SMP NOPTI CPU: 0 UID: 0 PID: 983 Comm: hib.sh Not tainted 6.17.0-rc4+ #1 PREEMPT(voluntary) Hardware name: Supermicro Super Server/H12SSL-i, BIOS 2.5 09/08/2022 RIP: 0010:__sev_platform_shutdown_locked.cold+0x0/0x21 [ccp] That rIP is: 00000000000006fd <__sev_platform_shutdown_locked.cold>: 6fd: 8b 13 mov (%rbx),%edx 6ff: 48 8b 7d 00 mov 0x0(%rbp),%rdi 703: 89 c1 mov %eax,%ecx Code: 74 05 31 ff 41 89 3f 49 8b 3e 89 ea 48 c7 c6 a0 8e 54 a0 41 bf 92 ff ff ff e8 e5 2e 09 e1 c6 05 2a d4 38 00 01 e9 26 af ff ff <8b> 13 48 8b 7d 00 89 c1 48 c7 c6 18 90 54 a0 89 44 24 04 e8 c1 2e RSP: 0018:ffffc90005467d00 EFLAGS: 00010282 RAX: 00000000ffffff92 RBX: 0000000000000000 RCX: 0000000000000000 ^^^^^^^^^^^^^^^^ and %rbx is nice and clean. Call Trace: <TASK> __sev_firmware_shutdown.isra.0 sev_dev_destroy psp_dev_destroy sp_destroy pci_device_shutdown device_shutdown kernel_power_off hibernate.cold state_store kernfs_fop_write_iter vfs_write ksys_write do_syscall_64 entry_SYSCALL_64_after_hwframe Pass in a pointer to the function-local error var in the caller. With that addressed, suspending the ccp shows the error properly at least: ccp 0000:47:00.1: sev command 0x2 timed out, disabling PSP ccp 0000:47:00.1: SEV: failed to SHUTDOWN error 0x0, rc -110 SEV-SNP: Leaking PFN range 0x146800-0x146a00 SEV-SNP: PFN 0x146800 unassigned, dumping non-zero entries in 2M PFN region: [0x146800 - 0x146a00] ... ccp 0000:47:00.1: SEV-SNP firmware shutdown failed, rc -16, error 0x0 ACPI: PM: Preparing to enter system sleep state S5 kvm: exiting hardware virtualization reboot: Power down Btw, this driver is crying to be cleaned up to pass in a proper I/O struct which can be used to store information between the different functions, otherwise stuff like that will happen in the future again.
In the Linux kernel, the following vulnerability has been resolved: net: rfkill: gpio: Fix crash due to dereferencering uninitialized pointer Since commit 7d5e9737efda ("net: rfkill: gpio: get the name and type from device property") rfkill_find_type() gets called with the possibly uninitialized "const char *type_name;" local variable. On x86 systems when rfkill-gpio binds to a "BCM4752" or "LNV4752" acpi_device, the rfkill->type is set based on the ACPI acpi_device_id: rfkill->type = (unsigned)id->driver_data; and there is no "type" property so device_property_read_string() will fail and leave type_name uninitialized, leading to a potential crash. rfkill_find_type() does accept a NULL pointer, fix the potential crash by initializing type_name to NULL. Note likely sofar this has not been caught because: 1. Not many x86 machines actually have a "BCM4752"/"LNV4752" acpi_device 2. The stack happened to contain NULL where type_name is stored