Audit Linux privileges now to limit compromise, escalation, and system-wide damage. Review Linux Privileges×

Alerts This Week
Warning Icon 1 477
Alerts This Week
Warning Icon 1 477

Stay Ahead With Linux Security News

Filter%20icon Refine news
X Clear Filters
X Clear Filters
View More

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?

No answer selected. Please try again.
Please select either existing option or enter your own, however not both.
Please select minimum {0} answer(s).
Please select maximum {0} answer(s).
/main-polls/157-should-linux-servers-automatically-install-security-updates?task=poll.vote&format=json
157
radio
0
[{"id":506,"title":"Yes \u2014 critical security patches should install automatically.","votes":0,"type":"x","order":1,"pct":0,"resources":[]},{"id":507,"title":"No \u2014 every update should be tested before deployment.","votes":2,"type":"x","order":2,"pct":66.67,"resources":[]},{"id":508,"title":"Only critical vulnerabilities should auto-install.","votes":0,"type":"x","order":3,"pct":0,"resources":[]},{"id":509,"title":"I patch when Reddit starts panicking.","votes":1,"type":"x","order":4,"pct":33.33,"resources":[]}] ["#ff5b00","#4ac0f2","#b80028","#eef66c","#60bb22","#b96a9a","#62c2cc"] ["rgba(255,91,0,0.7)","rgba(74,192,242,0.7)","rgba(184,0,40,0.7)","rgba(238,246,108,0.7)","rgba(96,187,34,0.7)","rgba(185,106,154,0.7)","rgba(98,194,204,0.7)"] 350
bottom 200
Loading...

Explore Latest Linux Security news

We found -2 articles for you...
210

Mak's Security Roundup: Prioritizing This Week's Critical Updates

Before you close out the week, check what still needs to be patched. . The list is not small. Ubuntu and Red Hat pushed kernel updates. OpenVPN and OpenShift both received security fixes. Several everyday Linux components were patched too, including Vim, nginx, cifs-utils, LibVNCServer, nghttp2, and Perl. That is the kind of week administrators can easily write off as routine. It should not be. These are the updates that keep small openings from turning into real access. Why This Week Looks Different One notable trend this week is the sheer volume of vendor advisories rather than a single dominant vulnerability. Ubuntu and Red Hat released updates across kernels, enterprise platforms, VPN software, and commonly deployed utilities. That pattern reflects today's Linux security landscape, where reducing risk often depends more on maintaining patch discipline than responding to one high-profile event. Linux Kernel Security Updates Kernel updates are easy to postpone because they usually mean a reboot. That's exactly why they keep showing up on patch backlogs. This week's updates include fixes for privilege escalation and container-related issues . Those aren't the vulnerabilities I'd be comfortable leaving unpatched for long. If someone already has a foothold on a server, the kernel is often where they try to go next. The less time those flaws sit in production, the better. Strengthening the Perimeter: OpenVPN The OpenVPN 2.7.5 update addresses seven security vulnerabilities, including issues with DNS handling, TLS-Crypt-v2 implementation, and proxy behavior. As the "front door" of the modern distributed enterprise, VPN gateways are inherently exposed and must be prioritized. Because VPN gateways are internet-facing, administrators should prioritize these updates to reduce the risk of unauthorized access, denial-of-service conditions, or other attacks addressed by the released fixes. Patching ensures that your remote access infrastructure remains a secure gateway ratherthan an entry point for unauthorized actors. Orchestration Integrity: OpenShift Red Hat OpenShift 4.19.36 and OpenShift 4.15.66 include security updates for the platform’s container infrastructure. As organizations shift toward microservices, OpenShift has become the operating system of the data center. Because OpenShift manages workloads across the cluster, a compromise of the orchestration layer can have broad security implications. Keeping OpenShift current helps reduce the risk of attackers exploiting vulnerabilities that could expose administrative components, workloads, or sensitive configuration data. Reducing that exposure also limits their ability to gain broader visibility or control over the production environment. Maintaining the Ubiquitous "Plumbing" Beyond the headline infrastructure components, several widely deployed utilities—including Vim , nginx , cifs-utils , LibVNCServer , nghttp2 , and Perl —received security attention this week. These utilities are the "plumbing" of Linux, used in almost every deployment and serving as dependencies for larger applications. Widely deployed utilities often become part of larger attack chains because they are present on so many systems. Delaying these seemingly minor updates can leave commonly deployed software exposed, creating opportunities for attackers to incorporate them into larger attack chains after gaining an initial foothold. Supply Chain Vigilance via Hardened Images Red Hat continues to ship updates for Hardened Images , including AI Base Images and container images. This reflects the industry shift toward "secure-by-design" infrastructure. Relying on stale base images is a common way organizations introduce known vulnerabilities into production. While automated scanners can quickly identify these vulnerabilities, your environment remains at risk until the underlying images are updated to a hardened baseline. The New Security Reality This week’s activity provides a vital snapshot ofthe current threat landscape, highlighting several key takeaways for security and infrastructure teams: Adopt a "Time-to-Exploit" Mindset: For internet-facing software, the window between public disclosure and exploitation is increasingly measured in hours or days, making timely patching more important than ever. Move Beyond Silos: You cannot secure your environment by patching in isolation. You must treat kernels, containers, and VPNs as a single, interdependent surface. Prioritize Ruthlessly: If your team is overwhelmed, follow this hierarchy: 1. Internet-facing services: (VPN gateways, web servers). 2. Kernel and privilege escalation fixes: (Reducing the risk of host compromise and container escape). 3. Ubiquitous utilities: (Vim, Perl, etc., to block lateral movement). What Matters Most This Week If this week's updates have one thing in common, it's that none of them can really be ignored. Kernel patches, VPN software, container platforms, and the tools that quietly support Linux systems all received security fixes. That's becoming a pretty normal week for Linux administrators. Nobody has an unlimited maintenance window. If you have to make choices, start with the systems that are easiest for an attacker to reach. Kernel updates shouldn't sit in the queue for long either, especially when they address privilege escalation or container-related issues. After that, work through the remaining utilities before they become next month's backlog. How is your team handling the growing volume of Linux security updates without falling behind on day-to-day operations? . Stay updated on critical patches for Linux systems from Ubuntu and Red Hat, vital to protect against threats.. Linux Kernel Security, OpenVPN Security Updates, Red Hat Patches, Ubuntu Updates, OpenShift Security. . MaK Ulac

Calendar%202 Jul 03, 2026 User Avatar MaK Ulac Security Vulnerabilities
67

FreeS/WAN Weekly Report: IPsec Implementation on Zaurus and RedHat Issues

This issue, we have reports of FreeS/WAN running on the Sharp Zaurus (item 1) and having a few small issues with RedHat 8.0 (item 2). Claudia Schmeing has posted a new revision of our interoperation document (item 3). Item 4 has a great discussion on the use of routing protocols with FreeS/WAN.. . . . This issue, we have reports of FreeS/WAN running on the Sharp Zaurus (item 1) and having a few small issues with Red Hat 8.0 (item 2). Claudia Schmeing has posted a new revision of our interoperation document (item 3). Item 4 has a great discussion on the use of routing protocols with FreeS/WAN. . Investigate the implementations of FreeS/WAN on the Sharp Zaurus, while delving into routing strategies and addressing RedHat complications.. IPsec Security, FreeS/WAN Integration, Zaurus Connectivity. . LinuxSecurity.com Team

Calendar%202 Oct 16, 2023 User Avatar LinuxSecurity.com Team Cryptography
78

CentOS Migration and Future Open Source Options Amid Red Hat Changes

The recent news regarding Red Hat’s decision to limit access to the source code of their Red Hat Enterprise Linux (RHEL) distribution has garnered considerable attention. "It is wise to make sure security and IT compliance aspects are addressed. Perhaps more open source Linux distributions will appear in the near future and offer another alternative to CentOS Linux." . Starting in 2004, right from its inception, every iteration of the commercial RHEL offering triggered a corresponding release of CentOS. These iterations mirrored RHEL, albeit with modifications to eliminate the Red Hat branding and other minor updates. The presence of open source CentOS Linux facilitated swift installation of a free RHEL variant, rendering it accessible for diverse purposes spanning from development to production environments. In January 2014, Red Hat joined the CentOS project. Under a new CentOS governing board, they became the main sponsor and driver of the CentOS project. They continued to be an open source downstream alternative to RHEL. On December 8, 2020, the CentOS project and Red Hat set a new end-of-life (EOL) date for CentOS Linux 8. They shifted focus and investment into a new Linux distribution, CentOS Stream, with a rolling release model. EOL means that the community stops releases regardless of the severity of a bug or a vulnerability. Today, CentOS versions 6 and 8 are already EOL, and version 7 is the last, with EOL set for June 30, 2024. This announcement immediately sparked new projects to fill the CentOS gap. New open source projects such as Rocky Linux and AlmaLinux took off quickly, gaining contributors, sponsors and users. Fast forward to June 21, 2023, when Red Hat announced it would no longer publicly publish RHEL on git.centos.org. The link for this article located at DevOps.com is no longer available. . CentOS's evolution, influenced by Red Hat, transitioned to CentOS Stream, leading to new projects like Rocky and AlmaLinux that emphasize reliability andstability in Linux. CentOS Migration, Red Hat Changes, Open Source Options, Linux Distribution Changes. . LinuxSecurity.com Team

Calendar%202 Sep 09, 2023 User Avatar LinuxSecurity.com Team Vendors/Products
News Add Esm H340

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?

No answer selected. Please try again.
Please select either existing option or enter your own, however not both.
Please select minimum {0} answer(s).
Please select maximum {0} answer(s).
/main-polls/157-should-linux-servers-automatically-install-security-updates?task=poll.vote&format=json
157
radio
0
[{"id":506,"title":"Yes \u2014 critical security patches should install automatically.","votes":0,"type":"x","order":1,"pct":0,"resources":[]},{"id":507,"title":"No \u2014 every update should be tested before deployment.","votes":2,"type":"x","order":2,"pct":66.67,"resources":[]},{"id":508,"title":"Only critical vulnerabilities should auto-install.","votes":0,"type":"x","order":3,"pct":0,"resources":[]},{"id":509,"title":"I patch when Reddit starts panicking.","votes":1,"type":"x","order":4,"pct":33.33,"resources":[]}] ["#ff5b00","#4ac0f2","#b80028","#eef66c","#60bb22","#b96a9a","#62c2cc"] ["rgba(255,91,0,0.7)","rgba(74,192,242,0.7)","rgba(184,0,40,0.7)","rgba(238,246,108,0.7)","rgba(96,187,34,0.7)","rgba(185,106,154,0.7)","rgba(98,194,204,0.7)"] 350
bottom 200