Overly broad permissions can turn one compromised account into a much larger security problem. Learn how to reduce unnecessary access, review privileges, and apply least privilege across modern Linux systems. Review Linux Privileges
Security Vulnerabilities 
security advisory moderate
security advisory moderate For organizations that run a self-hosted Git platform, it’s no longer just about hosting static code repositories. Today, Git servers are responsible for deployment pipelines, API tokens, SSH keys, package repositories, and the automation scripts that push code directly. Confirm that the upgrade addresses known vulnerabilities but also provides production environments. . That makes them trusted systems within the development environment and attractive targets for attackers looking to move...
Jul 20, 2026
Server Securitydata privacy automation
data privacy automation Every system admin has lived through the same Monday morning ritual. A queue of forty tickets, half of them password resets, permission errors, or disk space warnings that any experienced technician could resolve in under two minutes. The other half require actual judgment. For years, automation promised that software would eventually sort the two apart on its own. That promise is now being tested in production Linux environments. . Early results are reshaping how IT teams think about tier-1...
Jul 17, 2026
Privacydata collection automation
data collection automation You're running a web scraping project to collect pricing data from e-commerce sites. You set up a pool of datacenter proxies, launch your scripts, and within minutes — banned . CAPTCHAs everywhere. Your data pipeline stops before it really begins. . It's a frustrating scenario that plays out daily in ad verification, market research, and multi-account management. The website doesn't know you're doing legitimate research or monitoring. It just sees traffic coming from IP ranges it recognizes as...
Jul 17, 2026
Security Trends security advisory social engineering
security advisory social engineering Business Email Compromise used to be a numbers game — mass-blasted emails, broken English, an obvious "URGENT WIRE TRANSFER" subject line. That era is over. Generative AI has turned BEC into a tailored, low-noise operation that mimics writing style, voice, and even video presence. This piece looks at what's actually changed under the hood, what defenders are testing in response, and why so many organizations are still structurally unprepared for it. . The Infrastructure Problem Nobody Wants to...
Jul 17, 2026
Security Trends cybersecurity Linux documentation
cybersecurity Linux documentation Linux operating systems have gained prominence due to their stability, adaptability, and excellent security options. In the case of developing documentation, designing cybersecurity dashboards, or educational material, visuals are of vital importance when it comes to making things clear. The use of icons allows one to understand the message regarding alerts, authorization, encryption, authentication, or the state of the system just by looking at the visual cue without having to read long...
Jul 17, 2026
Refine news
X Clear Filters
Get the latest News and Insights
Get the latest Linux and open source security news straight to your inbox.
Community Poll
Should Linux servers automatically install security updates?
Trending News
Loading...
Explore Latest Linux Security news
We found 36 articles for you...
210
security advisorydenial of servicecriticalLinux: X.Org Critical Flaws Advisory CVE-2025-49176 to CVE-2025-49180
Let’s cut to the chase—if you’re running any system with X.Org X server or Xwayland versions prior to the latest patches , your setup may be dangerously exposed to vulnerabilities that stretch from data leaks to outright instability. These are not hypothetical problems or edge-case issues buried deep in some obscure configuration. We’re talking about flaws that impact core extensions many of you rely on every day, whether you’re maintaining workstations, servers, or production systems. . Several CVEs—five in total—have been identified, each tied to critical bugs introduced in various historical versions of X.Org and its components over the years. The scope of the affected systems is broad, covering decades of deployments, and while that may sound overwhelming, resolving these weaknesses boils down to understanding their nature, confirming you’re affected, and applying the appropriate fixes. Let’s dissect these vulnerabilities. CVE-2025-49176: Integer Overflow in Big Requests Extension The Big Requests extension—a feature present since X11R6.0—has been found to mishandle unusually large request sizes. Essentially, an attacker could craft a request that surpasses integer size limits during processing, bypassing safeguards intended to block them. This isn’t just sloppy error-handling; it opens the door to undefined behaviors that could affect system stability or be leveraged for further attacks. Imagine your guardrails on memory allocation disappearing mid-operation. That’s what happens here—the size validation slips up, and suddenly your server is operating outside the expected bounds. The fix? Patch to xorg-server-21.1.17 or xwayland-24.1.7, where this behavior has been corrected in commit 0885e0b2. CVE-2025-49177: Data Leak in XFIXES Extension The problem with XFixesSetClientDisconnectMode—the handler for a command used in the XFIXES extension—is how it mismatches request lengths. This flaw is subtle but dangerous; if a client sends a misaligned request,residual data from previous commands may be exposed. For workloads handling sensitive information or multi-user environments, this is a glaring issue. This vulnerability dates back to XWayland-22.0.99.1 (the release candidate for XWayland 22.1) and Xorg server 21.0.99.1, meaning systems built on these versions or older could be leaking data with every wrong-sized request. If confidentiality matters in your setup, patch immediately—look for commit ab02fb96 in the fixed versions. CVE-2025-49178: Unprocessed Client Requests Due to Leftover Bytes This one’s messy. The vulnerability stems from how shared buffers between clients are managed. Leftover bytes from one client request—bytes meant to be ignored—aren’t always purged correctly. Worse, these residual bytes could be consumed by an entirely different client’s request, causing hangs, glitches, and even denial-of-service scenarios. The root issue traces back to Xorg 1.10.0, but if you trace deployments across enterprise networks, you’ll probably find this older version still limping along on legacy setups. The fix in xorg-server-21.1.17 eliminates this cross-client interference ( commit d55c54ce ). If your systems rely on a mix of modern and legacy clients, this oversight is a ticking time bomb. CVE-2025-49179: Integer Overflow in X Record Extension The X Record Extension’s function RecordSanityCheckRegisterClients() has been exposed as vulnerable to yet another integer overflow. This mistake affects systems dating back to X11R6.1, allowing malicious actors to bypass request length checks. It’s a low-level vulnerability, yes, but handling malformed requests at this level can snowball into instability and exploits down the line. Patch to xorg-server-21.1.17 or xwayland-24.1.7, where fixes for this flaw have been committed ( see 2bde9ca4 ). CVE-2025-49180: Integer Overflow in RandR Extension The RandR extension was meant to better handle display properties, but in RRChangeProviderProperty(), there’s mishandling ofinteger overflow issues. These overflow errors could allow improper allocation of memory, risking anything from system instability to outright crashes. It first appeared in Xorg server 1.12.99.901, but its impact remains relevant for many active deployments. To mitigate, the bug has been patched in the latest versions of both Xorg-server and Xwayland. Notably, two separate commits— 3c3a4b76 and 0235121c —address this weakness. Which Systems Are At Risk? If you’re running anything predating xorg-server-21.1.17 or xwayland-24.1.7, you’re likely vulnerable to at least one (and possibly all) of these exploits. These flaws impact cornerstone X server functionality—extensions many of us assume are solidly built—and echo throughout organizations relying on aging deployments. Legacy systems, particularly those in heavily customized environments, are a high-risk category here. Considering the breadth of affected versions (some dating back decades), the responsibility falls on admins to evaluate their systems carefully. Whether you’ve rolled out custom distributions or are relying on once-stable deployments in critical infrastructure, these vulnerabilities demand immediate attention. What Can I Do to Mitigate Risk? If your systems are impacted by these flaws, there are several measures you can take to secure your data and mitigate risk: Apply the Fixes: First things first: upgrade your systems to xorg-server-21.1.17 and xwayland-24.1.7. This is non-negotiable. The patched releases address all five CVEs described above. Validate Your Changes: Take time to review the specific commits mentioned (e.g., 0885e0b2 , ab02fb96 ). Understanding what’s been fixed enables better long-term auditing for systems handling sensitive or mission-critical workloads. Monitor Vulnerability Reports: Follow the X.Org mailing list or GitLab repository. These platforms remain critical for staying plugged into emerging threats, particularly in open-source ecosystems where historicalflaws can lurk for years before discovery. Our Final Thoughts: Why This Matters for Security-Conscious Admins The open-source community’s strength lies in the transparency of its platforms, but transparency alone doesn’t guarantee security, especially when flaws trace their roots back decades. These vulnerabilities highlight the need for due diligence, especially in environments where legacy software plays a role. While upgrading and patching can feel like administrative tedium, ignoring these fixes risks systems that are unstable at best and actively exploitable at worst. Admins, take this as a wake-up call. For every fix deployed today, there’s a system out there still running the buggy version someone swore would “never need another update.” Let yours not be one of them! . Five critical CVEs in X.Org X Server and Xwayland require immediate upgrades to protect against severe data leaks.. X.Org security,Xwayland vulnerabilities,Linux patching,X server issues. . Brittany Day
Jun 18, 2025
•
Security Vulnerabilities
83
security advisorydata leakside-channel attackSLAM Threat: Intel LAM, AMD UAI, ARM TBI - Data Leak Risks
Researchers have identified a new exploit impacting upcoming processors called “Spectre based on Linear Address Masking” (SLAM). This side-channel-based attack exploits the new security features in Intel (Linear Address Masking (LAM)), AMD (Upper Address Ignore (UAI)), and ARM (Top Byte Ignore (TBI) chips. Specifically, the SLAM attack is a transient execution technique exploiting the new memory improvement features to leak sensitive data like password hashes. . According to the researchers who discovered this bug, SLAM exploits a “previously unexplored class of Spectre disclosure gadgets” that involve pointer chasing. Unlike the Standard (masked) gadgets, the unmasked gadgets are common code patterns across different software and are even available with the Linux Kernel that doesn’t include masked gadgets. Unlike other side-channel attacks, SLAM threatens a wider range of systems, including Linux. In their study, the researchers emulated the Intel LAM feature on Ubuntu to demonstrate how the SLAM attack exploits the unmasked gadgets to leak arbitrary ASCII kernel data from a userland process. Check out the article linked below for more information on how this attack works and an awesome video showing the SLAM attack leaking password hashes on Ubuntu! . New SLAM attack using Intel, AMD, and ARM features risks data exposure and security integrity across systems.. SLAM Attack, CPU Security, Spectre Exploit, Data Security, Linux Kernel Exploit. . LinuxSecurity.com Team
Dec 17, 2023
•
Hacks/Cracks
76
security advisorymemory flawdata leakIntel and AMD Processors Data Risk: Downfall and Zenbleed Threats
[BLACK HAT] Googlers have lately found not one but two more security vulnerabilities in Intel and AMD processors that can be exploited to steal sensitive data from a vulnerable computer's memory. . Specifically, there's one flaw in Intel components, and one in AMD. Both can be abused by malware running on a system, or a rogue logged-in user, to lift passwords, secrets, and other data out of memory that should be off limits. This should be concerning for those who use shared servers in the cloud. The Intel vulnerability, found by Daniel Moghimi and dubbed Downfall , was addressed on Tuesday, nearly a year after its private disclosure. The AMD vulnerability, found by Tavis Ormandy and named Zenbleed , was patched , to a degree, in July after being reported privately in mid-May, as we previously covered . . Recent vulnerabilities identified in Intel and AMD processors present significant risks for data leakage, threatening the security of cloud-based servers.. Intel Data Leak, AMD Security Flaw, Memory Breach, Cloud Malware, Processor Vulnerabilities. . Brittany Day
Aug 14, 2023
•
Organizations/Events
83
security advisorysoftware deploymentdata leakPyTorch Nightly Builds Compromised: Urgent Action Required
Users who deployed the nightly builds of PyTorch between Christmas and New Year's Eve likely received a rogue package as part of the installation that siphoned off sensitive data from their systems. The incident was the result of an attack called dependency confusion that continues to impact package managers and development environments if hardening steps are not taken. . "If you installed PyTorch nightly on Linux via pip between December 25, 2022, and December 30, 2022, please uninstall it and torchtriton immediately, and use the latest nightly binaries (newer than December 30, 2022)," the PyTorch maintainers said in a security advisory . PyTorch is a framework for developing machine learning applications in the fields of computer vision and natural language processing that is a continuation of the older and no longer maintained Torch library. PyTorch was originally developed by Meta AI, the artificial intelligence laboratory of Meta, Inc., but is now an open-source project maintained by the PyTorch Foundation under the Linux Foundation's umbrella. . Individuals using PyTorch's nightly builds from late December 2022 could have inadvertently downloaded a malicious module that jeopardized private information.. PyTorch, Supply Chain Attack, Dependency Confusion, Package Security, Data Protection. . LinuxSecurity.com Team
Jan 05, 2023
•
Hacks/Cracks
210
security advisorymoderatememory corruptionIntel: CVE-2022-4139 Moderate: Kernel Graphics Driver Data Leak Issue
CVE-2022-4139 was made public as an i915 kernel graphics driver security issue affecting all Gen12 graphics -- from integrated Tigerlake graphics up through the latest Raptor Lake graphics as well as the in-development Meteor Lake code plus the discrete GPUs of DG2/Alchemist and Arctic Sound. . Intel has disclosed CVE-2022-4139 as an incorrect GPU TLB flushing issue within their Linux kernel graphics driver. In some cases the translation lookaside buffer (TLB) is not flushed at all. At the very least there could be random memory corruption or data leaks while it's not yet been determined if specific memory could be targeted on affected Linux kernel versions up to this point. All versions from Linux 5.4 up through today's latest kernel versions are believed to be impacted when using Intel Gen12 integrated/discrete graphics. This though amounts to an Intel driver issue and not a hardware problem itself. Linus Torvalds just merged this five lines of code for mitigating the TLB invalidation on Intel Gen12 graphics for the video and compute engines. The link for this article located at Phoronix is no longer available. . Intel revealed a flaw involving GPU TLB flushing within their Linux kernel driver, impacting Gen12 graphics ranging from Tigerlake through Raptor Lake.. Intel Graphics Driver, Kernel Patch, GPU TLB Issue, Linux Kernel Security, Memory Corruption. . Brittany Day
Dec 02, 2022
•
Security Vulnerabilities
210
security advisorysecurity issuecritical threatOracle VM VirtualBox Data Leak: Critical Host Exposure Issue
Security researcher Jason Donenfeld who is known for leading the development of the WireGuard open-source software has outlined a new security vulnerability affecting the Oracle VM VirtualBox software. . When SIMD registers are used within interrupt handlers, it's possible for VirtualBox to leak data from the host to guest VMs. Donenfeld explained on the kernel mailing list: I wrote a tiny reproducer that should be pretty reliable for testing this, attached below. I think this proves my working theory. Run this in a VirtualBox VM, and then move your mouse around or hit the keyboard, or do something that triggers the add_{input,disk}_randomness() path from a hardirq handler. On my laptop, for example, the trackpoint goes via hardirq, but the touchpad does not. As soon as I move the trackpoint around, the below program prints "XSAVE is borked!". Also, note that this isn't just "corruption" of the guest VM, but also leaking secret contents of the host VM into the guest. So you might really want to make sure VirtualBox issues a fix for this before 5.18, as it's arguably security sensitive. The link for this article located at Phoronix is no longer available. . VirtualBox has encountered a severe security flaw that exposes sensitive host data to guest systems. Immediate patching advised.. VirtualBox Security, Oracle VM Vulnerability, Data Leak Threat, Host Data Exposure. . Brittany Day
May 23, 2022
•
Security Vulnerabilities
210
security advisorysecurity issuesecurity patchLinux Kernel Security Advisory: 32-Bit Arm Devices—Information Disclosure
Security researchers have discovered an information disclosure vulnerability in the Linux kernel that can be exploited to leak data, at least on 32-bit Arm devices. A patch for the vulnerability has already been merged in the mainline kernel. . Disclosed by experts at Cisco Talos, the bug, tracked as CVE-2020-28588, could allow an attacker to view the contents of the kernel stack memory and can also be used as a springboard for further compromise. The Cisco researchers first discovered this issue on an Azure Sphere device version 20.10, which is a 32-bit Arm device that runs a patched Linux kernel. . Unveil the recently identified data leak vulnerability within the Linux kernel, which presents threats to 32-bit Arm architecture devices.. Linux Kernel Exploit, Data Leak Vulnerability, Arm Security Threats. . Brittany Day
Apr 30, 2021
•
Security Vulnerabilities
210
security advisorymoderatesecurity issueLinux Kernel ARM Threat: CVE-2020-28588 Moderate Data Leak Advisory
An information disclosure vulnerability in the Linux kernel that exposes stack memory (tracked as CVE-2020-28588 ) can be exploited to leak data and act as a springboard for further compromise. . Disclosed by Cisco Talos researchers on Tuesday , the bug is described as an information disclosure vulnerability "that could allow an attacker to view Kernel stack memory." The kernel is a key component of the open source Linux operating system. The vulnerability, tracked as CVE-2020-28588 , was found in the proc/pid/syscall functionality of 32-bit ARM devices running the OS. . Revealed by Microsoft Security, this vulnerability is a privacy breach within the Windows OS that may result in unauthorized data access.. Linux Kernel Security, Data Leak Issues, Information Disclosure. . Brittany Day
Apr 28, 2021
•
Security Vulnerabilities
Get the latest News and Insights
Get the latest Linux and open source security news straight to your inbox.
Community Poll
Should Linux servers automatically install security updates?
Trending News
Search Topics
Powered By
Linux Security - Your source for Top Linux News, Advisories, HOWTOs and Feature Releases
QUICK LINKS
subscribe to newsletters!
Like staying secure? So do we.
Sign up for updates, tips, and alerts!