|
1825 Monetary Lane Suite #104 Carrollton, TX
Do a presentation at NTLUG.
What is the Linux Installation Project?
Real companies using Linux!
Not just for business anymore.
Providing ready to run platforms on Linux
|
Show Descriptions... (Show All)
(Two Column)
- [$] The end of __get_user() and __put_user()
Linus Torvalds rarely writes significant amounts of kernel code these days, sothe mergingof a 48-part patch series from him is an unusual event. This series,destined for the 7.4 kernel release, performs some long-delayed kernelcleanup by removing a couple of the primitives used to access user-space memoryfrom the kernel. What was once a best practice has long been superseded,but it can take time for such changes to work their way through a body ofcode this large.
- KeePassXC 2.8.0 released
Version2.8.0 of the KeePassXC password-management application has beenreleased.
The new release brings a lot of long-awaited new features, many bugfixes, andseveral security updates. Among the major features are the migration from Qt5 toQt6, Auto-Type on Wayland (Linux), configurable keyboard shortcuts, remotedatabase synchronization with external tools, quick unlock with password onmacOS, and quick unlock via Polkit on Linux. Version 2.8.0 is also the firstversion for which we ship native ARM64 builds for Windows and an experimentalAArch64 (i.e., ARM64) AppImage for Linux.
See the changelogfor a full list of new features, major changes, and bug fixes.
- [$] Rust features in the future
There are several Rust features that kernel developers have been hoping tostabilize, but Josh Triplett wanted to describe all of the otherfeatures that the Rust project is currently working on. He spoke about the topicat Kangrejos 2026, leaving the assembled kernel developers with several ideasabout how to use these upcoming Rust features in the kernel.The features included refinements to the type system, small syntax improvements, and asmarter borrow checker.
- Security updates for Thursday
Security updates have been issued by AlmaLinux (.NET 10.0, .NET 8.0, .NET 9.0, cockpit-files, cockpit-machines, fetchmail, glycin-loaders, go-toolset:rhel8, golang, hostapd, jackson-core, kernel, kernel-rt, librsvg2, lrzsz, mariadb11.8, openexr, openssh, openssl, perl-DBI:1.641, python-urllib3, python3.12-urllib3, qt5-qtbase, rust-sequoia-sq, and xorg-x11-server-Xwayland), Arch Linux (php and php-legacy), Debian (bind9, firefox-esr, nginx, php8.2, and php8.4), Fedora (ca-certificates, dolphin, gnome-shell-extension-gsconnect, libdigidocpp, linux-firmware, nicotine+, perl-ExtUtils-Typemaps-Default, php, python-cairosvg, qdigidoc, rust-rustls-webpki, rust-webpki-root-certs, and rust-webpki-roots), Gentoo (PHP), Mageia (php8.5, php8.4), Oracle (perl-URI), Red Hat (go-toolset:rhel8, golang, grafana-pcp, kernel, kernel-rt, nodejs-nodemon, nodejs22, nodejs24, nodejs:22, nodejs:24, rhc, and sudo), Slackware (php), SUSE (aliyun-cli, bouncycastle, buildah, ca-certificates-mozilla, chromedriver, cifs-utils, cyrus-sasl, docker, firefox, gimp, git-bug, GraphicsMagick, libheif, libpng16, libraw, libsoup-2_4-1, mutt, onefetch, openexr, openssh, openssl-certs, php7, php8, poppler, python-hpack, python310, python313-Django4, qemu, rootlesskit, tiff, xwayland, and yt-dlp), and Ubuntu (c-ares, ghostscript, libsoup3, libxs-parse-keyword-perl, nss, php5, php7.0, php7.2, php7.4, php8.1, php8.3, php8.5, poppler, pyjwt, u-boot, and unbound).
- [$] LWN.net Weekly Edition for October 22, 2026
Inside this week's LWN.net Weekly Edition:
Front: Android vendor hooks; Reproducible builds and kernel integrity; Rust data structures; NFS server changes; Setting no_new_privs for PID 1; Rust XArray; Rust cross-crate declarations; 7.3 statistics; Nix flakes. Briefs: eMudhra CA compromise; PHP RCEs; Node.js and musl vulnerabilities; GNOME OS; OpenBSD 8.0; Ubuntu 26.10; TAB results; Quotes; ... Announcements: Newsletters, conferences, security updates, patches, and more.
- Today's PHP Security Release, and How We're Strengthening PHP Security (PHP Foundation)
The PHP Foundation has put out ablog entry explaining how the vulnerabilities disclosed today cameabout and why they took so long to fix.
To fix the OOM problem, the PHP security team developed several competing approaches, but each came with its own trade-offs: backward compatibility breaks, new denial-of-service potential, or requiring changes to many third-party extensions which seemed impossible to coordinate. The PHP security team, operating on consensus, struggled to choose between these and feared the repercussions of shipping the wrong choice. Combined with the lack of a known path to remote code execution and the small team of core developers with the necessary deep knowledge of the engine occupied with many responsibilities, this decision process caused work on a fix to stall and restart repeatedly over months. We won't pretend otherwise: the delay was a structural failure, caused by both the security team's decision process and its lack of resources.
- More vulnerabilities in widely deployed software
The Node.js project hasreleaseda number of security updates to fix, among other vulnerabilities, aremote-code-execution bug affecting programs that use Brotli compression. And,in case any programmers who use compiled languages thought they could relax, themusl libc project has also announced anew vulnerability: anout-of-boundswrite that could potentially lead to remote code execution, although thathas not been demonstrated.
- Upstreaming Tyr: Rust, DRM, and the Linux Kernel (Collabora)
The Collabora blog providesan update on Tyr, a driver for Arm Mali GPUs.
One of our biggest challenges has been developing Tyr while the Rust kernel abstractions and driver interfaces are also being developed. As the driver interfaces are naturally revised and improved, we have rewritten Tyr several times to adapt to the larger Rust ecosystem. This not only makes progress much slower than it would be with a mature API, but also stalls progress for capabilities, such as job scheduling, while the abstraction is properly designed, reviewed, tested, and merged upstream.
But working in this evolving environment is also precisely where Tyr is able to provide the most value. As a user of these new Rust abstractions, Tyr helps to expose their requirements and limitations.
- [$] Understanding Nix flakes
Nix flakes are anexperimental feature of the Nix package-managementtool designed to build projects in a more self-contained and reproducibleway. Despite the feature's experimental status, it has become increasinglypopular for open-source projects to publish flake.nix files that offerpredefined development environments and build automation even when thoserepositories may not offer an upstream package or module for the NixOS Linux distribution. AlthoughNix flakes have a complicated history, and the path for stabilization isuncertain, flakes can provide useful capabilities for projects that choose toinclude them.
- Omarchy 4.0.5 Released With Better NVIDIA Laptop Support
The Omarchy project has released Omarchy 4.0.5, introducing a substantial collection of hardware compatibility improvements, desktop performance optimizations, security fixes, and package updates for the Arch Linux-based operating system. Released on October 18, 2026, the update focuses on refining the existing desktop experience while preparing the distribution for its next major feature release.
- Several Linux Kernel Vulnerabilities Accidentally Posted To Public Kernel Mailing List
Seemingly as an accident, overnight several new Linux kernel vulnerability reports were posted to the public Linux kernel mailing list rather than the private security mailing list. The vulnerabilities have yet to be patched on mainline but at least in some cases there are patches undergoing testing or queued in "-next" branches. The CVSS scores are as high as 9.0...
- Linux-based industrial Pi controller supports stackable I/O modules
Synergy Logic has launched the SLM-RP4, a UL-listed industrial edge controller based on the Raspberry Pi 4 platform. The DIN rail-mounted system integrates OpenPLC support and accommodates up to eight stackable I/O modules, providing a maximum of 128 I/O points for industrial automation, data acquisition, and IIoT applications. The SLM-RP4 uses Broadcom’s BCM2711 processor, featuring […]
- Solder-down COM brings i.MX95 to Linux dev kit
ADLINK’s I-Pi OSM IMX95 is an industrial development kit based on NXP’s six-core i.MX95 processor with an integrated 2 TOPS NPU. It pairs a solder-down OSM 1.2 module with a 4-inch carrier board, offering dual Gigabit Ethernet, display connectivity, and expansion options for edge AI applications. The I-Pi OSM IMX95 integrates ADLINK’s OSM-IMX95 computer-on-module with […]
- To Make Way For Data Centers, Google Will Pay Others to Use Less Power
Google is funding one of the nation's largest "virtual power plants," paying homes and businesses indirectly to reduce electricity consumption during periods of peak demand so more grid capacity can be available for data centers. Under its expanded deal with Voltus, the program could provide up to 1,070 megawatts in the Mid-Atlantic PJM grid -- roughly the output of a large nuclear reactor. The New York Times reports: That electricity won't come from new power plants. Instead, Voltus will sign up homes and businesses and give them financial incentives to curb their usage when local power demand is high or the grid is strained. Many of these reductions could occur automatically, such as through smart thermostats that dial back air-conditioning during peak summer hours or batteries that can provide temporary on-site power. Each of these tweaks frees up only a small amount of power on its own. But by aggregating them across thousands of businesses and homes, Voltus says it can reliably provide lots of extra capacity when it's most needed, and do so within a few years. While tech companies will likely ultimately need to build traditional power plants if they want to keep building large data centers, this approach could be a faster, cheaper and less-polluting option in the interim. "We really see virtual power plants as a critical short-term solution," said Ellen Zuckerman, head of energy market development for North and South America at Google. "It's a way to invest in our communities, really double down on our clean energy ambition, but also meet capacity at speed and scale."
Read more of this story at Slashdot.
- Microsoft Says October Updates Didn't Actually Fix VPN Issues
joshuark shares a report from BleepingComputer: Microsoft says it mistakenly flagged a bug causing Always On VPN connection issues as fixed in the October 2026 Windows 11 cumulative updates. Always On VPN replaced the legacy DirectAccess technology and supports domain-joined, non-domain-joined, and Microsoft Entra ID-joined devices running Windows 10, Windows 11, and Windows Server. It runs in the background and establishes secure tunnels back to the user's corporate network whenever their device connects to the internet. Microsoft first acknowledged the issue in a service alert sent to IT administrators in late September, saying it was triggered on systems running Windows 11 24H2 and later after installing the September 2026 security updates when the initial Always On VPN connection failed (e.g., when using automatic protocol selection with IKEv2 and SSTP). "When automatic protocol selection or protocol fallback was configured, affected VPN connections could remain stuck in a Connecting state or fail to connect after an initial connection attempt failed," it said. "In some cases, subsequent connection attempts could display the error, 'The specified port is already in use.'" After releasing the October 2026 Patch Tuesday Windows 11 cumulative updates, Microsoft marked the bug as resolved, but in a Tuesday update it said the issues weren't actually addressed and that a fix would ship later. "This disclosure was mistakenly updated to Resolved status on October 13, 2026. We have returned its status to Mitigated," it said in a service alert sent to IT admins. "A resolution for this issue is planned to be included in an update to be released in the coming weeks. We apologize for any inconvenience or confusion." While Microsoft continues working on a permanent solution, it shared a temporary fix that requires affected customers to choose one of two VPN tunneling protocols to work around the issue.
Read more of this story at Slashdot.
- The Browser Company Retires Its Arc Browser, Pushes Users to Dia
The Browser Company is shutting down its Arc browser on December 22 and encouraging users to migrate to Dia, its newer AI-powered browser for Apple Silicon Macs and Windows 11 PCs. Thurrott reports: In the message explaining why it was sunsetting Arc, The Browser Company explained that maintaining two separate browsers was difficult to justify, especially from a security perspective. "Dia was built from the ground up to meet today's security standards, so that's where our engineering and security teams will focus moving forward," the company wrote. The retirement of Arc will be gradual: While nothing changes for existing Arc users, it's no longer possible to create new Arc accounts as of today. On November 23, tab sync, Browse for Me, and other AI features will be disabled on the iOS and Android versions of Arc. Lastly, the desktop version of Arc will stop working on December 22, and Arc accounts will be deactivated.
Read more of this story at Slashdot.
- Moderna Shares Plunge After Leak of Cancer Vaccine Data
Moderna shares plunged as much as 25% after partial clinical trial data leaked for its personalized cancer vaccine developed with Merck, despite the full results showing promising outcomes for melanoma patients. Analysts attribute the selloff largely to inflated investor expectations rather than disappointing clinical results. CNBC reports: The personalized vaccine, known as intismeran autogene, paired with Merck's immunotherapy Keytruda reduced the risk of recurrence or death in certain melanoma patients by 42% compared with Keytruda alone. The data also showed the shot along with Keytruda reduced the risk of cancer spreading to distant parts of the body or death by 38%, compared with just the immunotherapy. The companies say about 82% of patients who received the personalized cancer vaccine alongside Keytruda were alive without their melanoma returning at two years, compared with 70% of those who received Keytruda alone. [...] Investors see the targeted vaccine as a possible breakthrough treatment, with the potential to be used in other forms of cancer in the future. It could also offer Moderna a critical additional commercial product in its pipeline, following vaccines for Covid-19, the flu and respiratory syncytial virus. "We assert this relative reduction in recurrence/death is clinically meaningful," said BMO Capital Markets analyst Evan Seigerman. "Such a reaction likely reflects inflated expectations into the full data release, rather than a true indictment on the efficacy of the combo therapy." UBS analysts said "this is overall a strong data set" and gives more confidence in upcoming studies of the vaccine in kidney and bladder cancers. They added the stock reaction may be due more to massive expectations than disappointing data.
Read more of this story at Slashdot.
- Bose Is Buying Skullcandy
An anonymous reader quotes a report from Wired: Longtime audio giant Bose announced on Wednesday that it's acquiring Skullcandy, the lifestyle brand known for its bass-heavy headphones. Skullcandy will remain a separate company within Bose's Premium Consumer Audio business and will still be based in Park City, Utah. The acquisition isn't out of left field. Bose has lent its audio expertise to Skullcandy over the past year under its Sound by Bose licensing program. Skullcandy designs the headphones and then works with Bose on the audio front. The relationship began with the Skullcandy Method 360 ANC earbuds in 2025 and more recently, with the Crusher 1080 ANC headphones in July. [...] This is hardly Bose's first audio acquisition (though it may be the most mainstream). Bose acquired McIntosh Group, owners of luxury audio brands McIntosh Laboratory and Sonus Faber, back in 2024. But Bose seems to be after Skullcandy's connection to its community. "What does the brand stand for? Does it have meaning for consumers? Is it relevant to a group of consumers that, frankly, we otherwise aren't reaching?" Bose CEO Lila Snyder tells WIRED. "If you think about McIntosh, Sonus Faber, and Skullcandy, they all fit into that realm. Skullcandy gives us access to a customer base that we think we're largely missing with the Bose brand." That's why Bose has no plans to relocate Skullcandy from Park City, Utah, which Snyder says is the epicenter of board sports culture. "We want to make sure we're right at the heart of it, as they always have been," she says. Skullcandy products are also affordable, especially compared to other Bose products and Bose-owned brands, which lets Bose compete at both ends of the market.
Read more of this story at Slashdot.
- Zoe Kleinman: PHP Is the Cyber Equivalent of an Unexploded Bomb
BBC technology editor Zoe Kleinman likens the recently discovered PHP security vulnerabilities to an unexploded bomb, writing, "The PHP story feels like the cyber equivalent of an unexploded bomb -- I have never seen such a dramatic, public and global response to a cyber event that hasn't happened yet." Although no successful attacks have been confirmed, the AI-assisted discovery of long-hidden flaws has triggered a worldwide security scramble, with websites taken offline as a precaution and administrators racing to deploy patches before attackers can exploit the vulnerabilities. From the report: The weaknesses found in the PHP programming language, which is used by millions of websites, had been quietly resting there for years and are not easy to exploit. One cyber security researcher told me he'd been up all night trying to do it as an experiment, but it was proving very difficult. [...] It was supposed to be kept quiet until everyone had a chance to fix their sites -- but the news was leaked. From that point the clock started ticking. As I write this, there are no reports that anyone or anything has succeeded in using the flaws to attack a site. "There's a real dilemma," said Prof Alan Woodward from Surrey University. "How do you alert people they need to be ready, and then that a patch is urgently required, whilst not alerting attackers? Basically you're telling everyone about the problem at the same time and hoping the defenders aren't awake enough to act as soon as the patch is out." But we do know from large web companies like Cloudflare and Palo Alto Networks that millions of attempts have been made. We probably won't know for a while whether it has worked for any criminals, because the companies affected might not be aware yet either. As far as we know the unexploded bomb remains intact for now, and for some experts this is a success. "We've seen how a team of people supported by the large AI company have used AI to find the problem, work for months together to solve it and get everybody ready to be safe and secure," Gina Neff, Professor of Responsible AI at Queen Mary University, told the Today Program on BBC Radio 4. "We have enormous capability to handle these risks."
Read more of this story at Slashdot.
- Anthropic Takes On Muse With Claude Duet
Anthropic has launched Claude Duet, an AI agent aimed at professionals and small businesses that competes with Meta's Muse and OpenAI's Dots. Here's Anthropic's description of what it can do: Each morning, it sends you a short brief on the most important items across your connected apps. Throughout the day, it keeps tabs on those apps and messages you only when something needs your attention. You can also hand it tasks of all shapes -- from simple administrative tasks of scheduling meetings to more complex ones, such as building dashboards with dozens of tools, creating financial or sales forecasts, prototyping, and building web apps. The Verge reports: Claude Duet pulls in memory, skills, and connected apps from Claude, and it has a virtual machine with a browser that it can use for completing work. Before any big step, like sending a payment or deleting something, Claude Duet messages you for approval. Given that Duet may be taking action on sensitive information, it has a new "new dedicated classifier and safety system prompt" that are "designed to reject requests to share the strictest tier of information," such as credit card numbers. Anthropic says Claude Duet is currently an "early version" and that it "still might misread a thread or miscalibrate what's urgent." It's also not "as strong" at personal errands like booking tickets.
Read more of this story at Slashdot.
- Several Linux Kernel Vulnerabilities Accidentally Posted To Public Kernel Mailing List
Trend Micro's Zero Day Initiative appears to have accidentally disclosed several unpatched Linux kernel vulnerabilities on the public LKML instead of the private security list, including two CVSS 9.0 flaws that could enable remote code execution through SMB Direct and KSMBD. "This seemingly was a mistake with Linux's second-in-command Greg Kroah-Hartman responding to each report asking about their submission to the public mailing list," adds Phoronix. The newly-disclosed vulnerabilities include: ZDI-CAN-33549 as a CVSS 9.0 scored vulnerability for SMB Direct remote code execution vulnerability due to integer underflow. For this one there is a patch in a Git branch of code intended for Linux v7.5 but now presumably will be expedited for getting to mainline. ZDI-CAN-33774 as a KSMBD race condition that can lead to remote code execution. Another CVSS 9.0 rated vulnerability. ZDI-CAN-33367 is a vulneravbility for skbuff skb_zerocopy in the network code that can lead to local privilege escalation. For this one Linux kernel developers received a security report from another source last week over the same issue and a patch is expected to be posted soon. ZDI-CAN-34068 as a VMWGFX VMware graphics driver bug with an out-of-bounds write leading to local privilege escalation. ZDI-CAN-34076 an uninitialized resource in the NVMET code leading to information disclosure. ZDI-CAN-32005 was also posted to the mailing list a day prior for a search-domain TCP query stack buffer overflow leading to local privilege escalation.
Read more of this story at Slashdot.
- Google Staff Resign In Backlash Over Its AI Contracts With Military
An anonymous reader quotes a report from the BBC: Google is facing a backlash from some staff members over the company's deployment of its AI technology for military use. The BBC has spoken to several tech workers who have either recently resigned from Google's AI company, Google DeepMind, or are in the process of leaving, over concerns with the tech firm's military contracts. Sofia Liguori, a London-based research engineer, is one of them. She resigned from Google DeepMind this week and spoke about her concerns exclusively with the BBC, despite her contract restricting her from doing so. "Realizing my company is pushing more and more for AI systems in military operations makes me feel ashamed to work at Google," Liguori said, speaking in a personal capacity. [...] After working for the company for three years, Liguori said she decided to resign over Google's increasing work with the US and Israeli militaries. "I don't agree with this direction and this has led me to lose faith in my company being true to its stated ethical values," she said. Those values, according to Google's AI Principles, include implementing AI with "human oversight" and aligning the technology with "international law and human rights." But former and current staff at the company, and experts the BBC spoke to, said they were concerned about the level of human oversight at critical moments. The tech workers said they are particularly worried about the AI military deals signed this year, because they greatly increase the scope of what the Pentagon can use the technology for. Andreas Kirsch, an AI researcher, also resigned from Google DeepMind earlier this month over his concerns. Kirsch told the BBC that he believes "Google's governance and oversight are not sufficient or meaningful enough to deploy AI safely and responsibly in military and classified settings" or "to develop artificial superintelligence safely in the future." "Google seems to have no right to control or veto how the Pentagon uses its AI and also seems to have limited visibility into how it's being deployed," he added. [...] Employees at Google have told the BBC that staff are scared to speak out about AI safety and its uses in warfare because their employment contracts prohibit them from publicly criticizing the company. "In principle I'm not allowed to criticize Google for the duration of my life," Sofia Liguori told the BBC. But she decided to do so "because I believe it's important for these things to be known and I also think that talking about facts is not criticizing." Liguori added that at Google "people are scared of retaliation and putting their career at risk. You feel you are being watched, you can't speak." A current employee at Google DeepMind, who declined to be named for fear of retaliation, told the BBC that "a lot of motivated employees who signed up for [the company's] original mission could leave -- but there's also a pipeline of people at the start of the careers who could fill those positions. It could be a changing of the guard." Another Google DeepMind staff member, who also wished to remain anonymous, told the BBC: "A lot of people have left the company that feel strongly about this [how Google DeepMind has changed its ethics position]." "Some people are putting up a fight, others are thinking: 'it's a big company. What do you expect to change?'", the employee said. In response, a Google spokesperson told the BBC: "We work with public sector organisations worldwide and follow a consistent process for reviewing and entering these contracts, including compliance with our acceptable use policies and AI principles." "We also have dedicated channels for employees to safely raise any concerns -- ranging from business ethics to misconduct -- and have strict workplace policies in place to prevent retaliation of any kind."
Read more of this story at Slashdot.
- Airbnb Bans Making Guests Do Dishes, Take Out the Trash
Airbnb is banning hosts from requiring guests to perform time-consuming checkout chores, including washing dishes, stripping beds, doing laundry, and taking trash off-site. The updated policy applies to reservations booked on or after November 20. The Verge reports: Airbnb is displaying hosts' requests more prominently now in a new "rules and requests" section on listings. You might see an "includes cleaning requests" warning if a host leaves chore requests in their listing after the new policy goes into effect. Hosts aren't allowed to sneak in extra rules in messages to guests or on signs around their property, either. Some hosts pushed back on the house rules restrictions on Airbnb's forums, saying they pose health risks and arguing that guests can simply choose not to stay at listings with overly-strict rules. Airbnb says there can be exceptions to the limits on checkout chores, like asking guests to "dispose of trash in an animal-proof container in bear country."
Read more of this story at Slashdot.
- Security: Why Linux Is Better Than Windows Or Mac OS
Linux is a free and open source operating system that was released in 1991 developed and released by Linus Torvalds. Since its release it has reached a user base that is greatly widespread worldwide. Linux users swear by the reliability and freedom that this operating system offers, especially when compared to its counterparts, windows and [0]
- Essential Software That Are Not Available On Linux OS
An operating system is essentially the most important component in a computer. It manages the different hardware and software components of a computer in the most effective way. There are different types of operating system and everything comes with their own set of programs and software. You cannot expect a Linux program to have all [0]
- Things You Never Knew About Your Operating System
The advent of computers has brought about a revolution in our daily life. From computers that were so huge to fit in a room, we have come a very long way to desktops and even palmtops. These machines have become our virtual lockers, and a life without these network machines have become unimaginable. Sending mails, [0]
- How To Fully Optimize Your Operating System
Computers and systems are tricky and complicated. If you lack a thorough knowledge or even basic knowledge of computers, you will often find yourself in a bind. You must understand that something as complicated as a computer requires constant care and constant cleaning up of junk files. Unless you put in the time to configure [0]
- The Top Problems With Major Operating Systems
There is no such system which does not give you any problems. Even if the system and the operating system of your system is easy to understand, there will be some times when certain problems will arise. Most of these problems are easy to handle and easy to get rid of. But you must be [0]
- 8 Benefits Of Linux OS
Linux is a small and a fast-growing operating system. However, we can’t term it as software yet. As discussed in the article about what can a Linux OS do Linux is a kernel. Now, kernels are used for software and programs. These kernels are used by the computer and can be used with various third-party software [0]
- Things Linux OS Can Do That Other OS Cant
What Is Linux OS? Linux, similar to U-bix is an operating system which can be used for various computers, hand held devices, embedded devices, etc. The reason why Linux operated system is preferred by many, is because it is easy to use and re-use. Linux based operating system is technically not an Operating System. Operating [0]
- Packagekit Interview
Packagekit aims to make the management of applications in the Linux and GNU systems. The main objective to remove the pains it takes to create a system. Along with this in an interview, Richard Hughes, the developer of Packagekit said that he aims to make the Linux systems just as powerful as the Windows or [0]
- What’s New in Ubuntu?
What Is Ubuntu? Ubuntu is open source software. It is useful for Linux based computers. The software is marketed by the Canonical Ltd., Ubuntu community. Ubuntu was first released in late October in 2004. The Ubuntu program uses Java, Python, C, C++ and C# programming languages. What Is New? The version 17.04 is now available here [0]
- Ext3 Reiserfs Xfs In Windows With Regards To Colinux
The problem with Windows is that there are various limitations to the computer and there is only so much you can do with it. You can access the Ext3 Reiserfs Xfs by using the coLinux tool. Download the tool from the official site or from the sourceforge site. Edit the connection to “TAP Win32 Adapter [0]
- I cant believe PowerShell is actually good!
Earlier this year, I needed to learn PowerShell scripting for one Windows-related project, and I have tried it out a few more times on Mac. It has quickly become one of my favorite tools for automation and scripting—taking on jobs that I would have otherwise tried to do with Node.js, Shortcuts, macOS Automator, or heaven forbid, Bash scripts. I get it now. PowerShell is great, even if you dont use it as your shell, and even if youre on Mac or Linux. ↫ Corbin Davenport I dont use the shell often enough on any of my main machines to have much of an idea about the strenghths and weaknesses of PowerShell compared to more traditional shells, but this is definitely not the first time Ive heard a lot of praise for it from people otherwise knee-deep in the UNIX and traditional shell world. There really must be something to this, and since PowerShell is also available on Linux and macOS, its pretty straightforward to give it a go without having to deal with Windows.
- Garmin revamps and opens up Connect developer API program
Earlier this year, Garmin closed its Connect API developer program because it was being flooded with AI!-generated applications to the point it couldnt handle them anymore. What made it worse was that half of the applications were never actually used, not even once. It also didnt help that Garmin treated every single application to the program the same way, whether it was from a hobbyist just wanting access to their own data, to a massive corporation developing a popular service used by god knows how many people. Today, the company has relaunched the program, and its been considerably overhauled. While hobbyist use of the API is going to be free which is way better than it was before once you hit a thousand users, youre going to have to start paying. Still, Garmin’s shift here towards charging for API access will set a dangerous precedent for the industry. Especially for a company that bills itself as a (or the?) premium sports hardware provider. On the flip side, there’s simply no ignoring the flood of mostly AI apps that take up resources at Garmin and elsewhere to support. Heck, my inbox is flooded with these apps daily requesting reviews. It sounds like when Garmin shut off access to the API last spring, they were seeing inbound API requests at a daily scale that they’d previously only seen over a period of weeks. Simply put, there’s no good answer. ↫ Ray Maker at DC Rainmaker The excesses of the easy availability of AI! code generation impacts the entire industry. At least one good thing has come out of this: hobbyists can now access the Connect API developer program much easier than before.
- Examining the macOS gcc binary
If you’ve ever written C (or c++) on a mac, you’ll know that the so-called gcc is just clang in disguise. Most people (fairly) assume that this is just an alias, but this is not true! It’s a binary! Now, what is this binary? I naively assumed that it would just be shelling out to clang but it turns out the answer is more interesting than that. ↫ juliethefoxcoon Its all smoke and mirrors.
- Unikernels in OCaml
Unlike traditional OSs that separate user applications from the kernel, a unikernel bundles everything into a single, isolated image that runs directly on a hypervisor (like KVM, BHyve, or OpenVMM). Because it removes unnecessary drivers and background services, a unikernel is extremely small, fast to boot, and efficient with resources. Here, we will learn how to develop and deploy unikernels built using the OCaml language and the Solo5 unikernel. These are the two fundamental components that will then enable us to develop our own applications in the form of unikernels, which we can subsequently deploy using Albatross. ↫ Unikernels in OCaml Some light reading for the weekend.
- How to install an app on your Commodore 64
Graybeards like me remember trying to painstakingly type source code from a magazine. This is a very accurate account of what a young computer user in 1986 needed to do to get a new game for the Commodore 64, complete with an immersive emulation. It’s time to install an app! But here in 1986, we still call them “programs,” not apps. So, you’ll want to set aside some time to get started installing a program.
- Apple stops pretending macOS is UNIX
Early 2025, I wrote about how I think macOS UNIX certification was basically a lie. It required so many convoluted and cumbersome changes to macOS that literally nobody applies to their system that it the certification had kind of become a farce. At the end of the article I wondered for how much longer Apple would be playing this little charade to hammer macOS through a meaningless UNIX-shaped hole, and it turns out the answer was about 18 months!. When you go to the Open Groups website and the list of certified UNIX operating systems, macOS is no longer listed. For the past few weeks, it was still listed if you drilled down specifically to the UNIX 03 certification, but that, too, has now been removed. Assuming macOS 27 doesnt return in the near future with a brand new certification, we can safely say that Apple got tired of paying a few employees to get its desktop operating system certified. With one more operating system gone from the list, theres now only one UNIX operating systems left: AIX. While the registry also lists HP-UX, z/OS, and UnixWare/OpenServer, those either only conform to really old UNIX certifications (from the 90s), or simply arent developed anymore (HP sunset HP-UX at the end of last year). Only one operating system version conforms to the latest version of the certification, UNIX 07, and thats AIX 7.2 TL5 and later!, which possibly includes AIX 7.3, the most recent version of AIX. Not that any of this really matters.
- OpenBSD 8.0 released
Hot on the heels of Wine being ported to OpenBSD, we now have the release of OpenBSD 8.0. It adds hibernate support for arm64, switches the sparc64 toolchain to LLVM, and updates the DRM graphics drivers to Linux 6.18.53, which also adds support for Intel Arc A-Series (DG2/Alchemist) graphics cards. Theres a whole bunch of improvements, fixes, and changes for RISC-V and ARM in general, of course, as well as to the various Wi-Fi drivers. On top of that, it also comes with new versions of OpenSSH and LibreSSL, as well as a massive list of other improvements and fixes. If youve never installed OpenBSD before, be sure to read this detailed guide to know what to do once everythings installed, while listening to the official release song, of course.
- Apple adds mystery folder to your PATH and everyone is apparently just okay with that
Apparently, macOS 27 comes with a small mystery people are trying to figure out. Recently, while troubleshooting a PATH issue, I noticed an entry for /pkg/env/global/bin. At first, I worried that something had gone horribly wrong. Turns out, this is part of macOS 27.0… though no one is sure what it’s for yet. In a post about how macOS’s boot volume structure has been updated, Howard Oakley explains that the pkg directory was added to the Data volume in macOS 26.4, but not added to the root of the Signed System Volume until 27.0. He also notes that this is sort of a big deal. The weird thing is, as far as I can tell, no one seems to know what this new directory is for! It’s odd that Apple would update their filesystem structure, add it to everyone’s PATH, and there not be some explicable reason. ↫ Gavin Anderegg I guess well find out eventually, but this does highlight something that I find extremely unsettling about this. With proprietary software like macOS, you literally are at the mercy of whatever Apple decides to do to your! operating system. You install an update, and aside from all the documented changes, theres going to be changes you simply have no idea what theyre for, or why theyre there. Dont get me wrong, theres obviously not something nefarious going on in this particular case, but it still feels wild to me that people just willingly accept this. In the open source world, stuff like this simply does not happen. Youre not going to install a bunch of Fedora updates one day and find a mysterious, undocumented folder in your PATH. Such a change will be documented, but even in the unlikely event its not, you can just go through the commit history and find out exactly why the new folder is there, and what its intended purpose is or is going to be. Considering the state of the world and the people corporations like Apple really answer to, I would not be comfortable with letting them dictate even something as simple as my PATH.
- Wine ported to OpenBSD, runs modern Windows games
In what is quite a major achievement, Wine has been ported and made to work on OpenBSD. We have since tested several dozens of 64-bit Windows software, mostly successfully. See screenshots, livestream recordings for example. Even the Remaster of The Witcher 3 which released just last month runs, and runs well (requires adding in vkd3d-proton; see README; livestream which looks less fluent than it is due to the on-system recording with ffmpeg). ↫ Thomas Frohwein The biggest limitation seems to be the lack of support for WoW64, so 32bit Windows software wont work. Still, this is a massive milestone for OpenBSD, and makes especially gaming a somewhat viable option on OpenBSD.
- Single-partition encrypted NetBSD 11 root
What if a regular, normal NetBSD installation is too plebeian for you? This is a quick overview which attempts to synthesize DW Armstrongs tutorial on NetBSD encryption with the cgdroot page from the NetBSD wiki in a single MBR partition, divided into multiple disklabel slices to preserve MBR entries. ↫ indigoparadox Web Zone What if you need this?
- Omarchy 4.0.5 Released With Better NVIDIA Laptop Support
by George Whittaker
The Omarchy project has released Omarchy 4.0.5, introducing a substantial collection of hardware compatibility improvements, desktop performance optimizations, security fixes, and package updates for the Arch Linux-based operating system. Released on October 18, 2026, the update focuses on refining the existing desktop experience while preparing the distribution for its next major feature release.
Among the most important changes are improved NVIDIA hybrid graphics support for laptops, an updated Linux 7.2.8 kernel featuring the BORE scheduler, and compatibility improvements for Qt 6.12. The release also resolves boot-related black screens, fixes audio problems affecting certain Dell and USB speaker configurations, corrects Steam graphics driver selection, and improves the reliability of several desktop utilities.
Although version 4.0.5 is primarily a maintenance release, its improvements extend across many of the components that determine how smoothly a Linux desktop operates. From faster application launches and more responsive desktop panels to stronger security defaults and more reliable hardware detection, the update demonstrates Omarchy's continued emphasis on delivering a preconfigured Linux environment that requires relatively little manual setup.
Omarchy Continues Refining Its Arch Linux Desktop Experience
Omarchy is an opinionated Arch Linux-based distribution designed to provide a ready-to-use development and desktop environment built around the Hyprland Wayland compositor. Rather than presenting users with a minimal installation that requires extensive customization, Omarchy combines a carefully selected collection of applications, themes, keyboard shortcuts, and system configurations into a cohesive desktop experience.
The distribution has attracted attention among developers and experienced Linux users who appreciate keyboard-driven workflows, tiling window management, and the flexibility of Arch Linux without necessarily wanting to configure every component manually. Its desktop environment emphasizes efficient navigation, integrated development tools, and a consistent visual design, while retaining access to Arch's extensive software repositories.
Version 4.0.5 continues that approach by concentrating on problems that can interrupt everyday workflows. The release improves hardware compatibility, corrects regressions introduced by newer software packages, and reduces unnecessary delays in common desktop operations. Rather than introducing a dramatic redesign, the developers have focused on making the existing environment more predictable and responsive.
Go to Full Article
- KDE Plasma 6.8 Marks 30 Years With a Major Shift to Wayland and a More Powerful Linux Desktop
by George Whittaker
The KDE Project has officially released KDE Plasma 6.8, introducing a substantial collection of desktop improvements while celebrating three decades of open-source software development. Released on October 14, 2026, exactly 30 years after Matthias Ettrich announced the original KDE project, this anniversary edition brings significant changes to display management, accessibility, graphics performance, remote desktop functionality, system monitoring, and application theming.
Perhaps the most consequential development is KDE's decision to retire native X11 desktop sessions in Plasma 6.8, completing its transition toward Wayland as the primary display architecture. The release also introduces NVIDIA triple buffering by default, improved HDR support, a more capable remote desktop server, CPU affinity controls in System Monitor, and expanded capabilities for the experimental Union theming engine. These improvements reflect KDE's effort to modernize the Linux desktop while maintaining the customization and flexibility that have defined Plasma for years.
Plasma 6.8 is therefore more than a commemorative release. It represents an important architectural transition for one of Linux's most widely used desktop environments, with changes that affect both everyday users and developers building applications for the next generation of Linux desktops.
KDE Celebrates Three Decades of Open-Source Desktop Development
KDE's history began on October 14, 1996, when Matthias Ettrich proposed creating a consistent graphical desktop environment for Unix-like operating systems. At the time, Linux was becoming increasingly capable as a free operating system, but its graphical experience remained fragmented. Users could choose from several window managers and applications, yet there was no universally integrated desktop environment comparable to the commercial graphical systems available elsewhere.
The original KDE initiative sought to address that limitation by building a cohesive desktop around the Qt application framework. Over the following decades, the project evolved through several major generations, introducing increasingly sophisticated desktop technologies while expanding into applications, development frameworks, mobile interfaces, and other open-source projects.
Plasma 6.8 arrives as KDE marks its 30th anniversary, but its development priorities are focused primarily on the future. Rather than introducing a purely cosmetic anniversary edition, KDE has concentrated on modernizing underlying desktop infrastructure while improving accessibility, usability, and performance. The result is a release that combines immediately visible enhancements with architectural changes intended to support future development.
Go to Full Article
- Linux Moves Closer to Retiring the x32 ABI After Years of Limited Adoption
by George Whittaker
Linux kernel developers are renewing efforts to retire the x32 application binary interface (ABI), a little-used compatibility feature that attempted to combine the advantages of 64-bit processors with the smaller memory footprint of 32-bit applications. A revised patch series submitted on October 8, 2026, proposes the first steps toward disabling the interface, potentially ending support for an architecture experiment introduced more than 14 years ago.
The latest proposal comes from Sebastian Andrzej Siewior, a Linux kernel developer at Linutronix who has been working on the removal effort throughout 2026. Rather than immediately deleting every component associated with x32, the proposed approach would first prevent the feature from being enabled through normal kernel configuration. This would give remaining users and distribution maintainers an opportunity to respond before the underlying implementation is removed.
The effort reflects a broader challenge in Linux development: maintaining compatibility with older or rarely used technologies while keeping the kernel manageable, secure, and efficient. Although x32 offered theoretical performance and memory advantages, it never achieved widespread adoption. With conventional x86_64 software dominating modern Linux systems, developers are increasingly questioning whether the additional maintenance burden remains justified.
Understanding the Linux x32 ABI
The x32 ABI was introduced with Linux kernel 3.4 in 2012 as an alternative to conventional 32-bit and 64-bit application environments. Its goal was to provide applications with access to the architectural improvements of x86_64 processors while retaining smaller data types and pointers associated with 32-bit software.
Traditional 32-bit x86 applications use the i386 ABI, which operates with a more limited register set and 32-bit execution conventions. Standard x86_64 applications, meanwhile, benefit from additional general-purpose registers, wider registers, and modern calling conventions, but they normally use 64-bit pointers. Those larger pointers can increase memory consumption in applications that maintain large numbers of pointer-heavy data structures.
The x32 ABI attempted to offer a compromise. Applications would execute using the x86_64 instruction set and its larger register file while retaining 32-bit integers, long values, and pointers. This programming model is commonly described as ILP32, meaning that integers, long integers, and pointers are all 32 bits wide.
The distinction can be illustrated by comparing the expected sizes of common C data types:
Go to Full Article
- Google's Kage Project Rethinks Linux Kernel Security With Isolated Device Drivers
by George Whittaker
Google is exploring a new approach to Linux kernel security that could significantly change how device drivers interact with the operating system. The experimental project, known as Kage, uses compiler-based sandboxing to isolate drivers inside the kernel, potentially limiting the damage caused by memory corruption, programming errors, and exploitable vulnerabilities without requiring drivers to run as separate user-space processes.
The research was presented at the Linux Plumbers Conference 2026, held October 5–7, with Stanford University and Google researcher Zachary Yedidia discussing how LLVM's Lightweight Fault Isolation (LFI) technology can create restricted execution environments for native kernel code. Unlike conventional isolation techniques, which often depend on separate processes or virtual machines, Kage attempts to preserve the performance advantages of kernel-space execution while reducing the amount of memory individual drivers can access.
Early prototypes have already demonstrated the concept using NVMe storage, networking, and Wi-Fi drivers. However, Kage remains an experimental research project rather than a feature available in mainstream Linux distributions. Its developers are still investigating performance, hardware access, and compatibility with more complicated drivers, including graphics hardware.
Why Device Drivers Remain a Major Linux Security Challenge
Linux device drivers are responsible for connecting the operating system to hardware components, including graphics cards, network adapters, storage controllers, USB devices, and wireless chipsets. Most traditional Linux drivers execute in kernel space, giving them privileged access to system resources and the ability to interact directly with hardware. This architecture is one reason Linux can deliver high performance across such a broad range of devices, but it also creates a significant security challenge.
When an ordinary application encounters a memory error, the operating system can often terminate that process without affecting the rest of the system. Kernel drivers operate under different conditions. Because they typically share the kernel's address space and privileges, an invalid memory access or exploitable vulnerability can affect unrelated kernel components, potentially resulting in a system crash, privilege escalation, or complete compromise of the operating system.
The challenge becomes more complicated when considering the enormous number of drivers supported by Linux. Some are maintained by large organizations with extensive testing infrastructure, while others receive contributions from smaller development teams or individual maintainers. Even carefully reviewed drivers can contain bugs, particularly when they interact with complicated hardware, asynchronous operations, and memory-management mechanisms.
Go to Full Article
- Speech Synthesis on Linux: Adding a Voice to Scripts and Systems
by George Whittaker
Linux users have long had a pragmatic relationship with text-to-speech. The classic open-source engines have been available for years, wired into accessibility tools and the occasional script, dependable but unmistakably robotic. They do the job where the job is simply to convert text to some kind of speech, but the mechanical output has kept them out of anything where the voice actually matters. The arrival of high-quality speech synthesis delivered over an API changes what is possible, letting Linux users add genuinely natural voices to scripts, services, and applications without hosting a heavyweight model themselves.
The Familiar Trade-Off
Anyone who has used the traditional Linux speech engines knows the trade-off. They are free, local, and scriptable, which fits the Linux ethos perfectly, but the voices are clearly synthetic. For accessibility and for utilitarian tasks where intelligibility is all that counts, that has been acceptable. For anything user-facing where the quality of the voice shapes the experience, it has not.
The alternative of running a modern, high-quality speech model locally is possible but comes with real costs: significant computational requirements, model management, and the ongoing maintenance of a demanding piece of infrastructure. For many use cases, particularly on servers, embedded systems, or ordinary workstations, that overhead is disproportionate to the need. This is the gap that an API-based approach fills, offering the quality of a large modern model without the burden of hosting one.
The API Approach on Linux
Delivering speech synthesis over an API fits naturally into how Linux users already build things. Rather than installing and maintaining a model, you make a request to a service and receive audio back, which you can then play, save, or pipe into whatever comes next. A Go to Full Article
- Archinstall 4.5 Released with AArch64 Support, Real-Time Kernels, and Major Installer Fixes
by George Whittaker
The Arch Linux project has released Archinstall 4.5, the latest version of its guided text-based installer, bringing expanded AArch64 support, new real-time Linux kernel options, additional translations, security improvements, and numerous fixes for installation workflows.
Archinstall 4.5 was released on September 29, 2026, roughly three months after Archinstall 4.4. The new version arrives just ahead of Arch Linux's October installation media refresh and has already been packaged as archinstall 4.5-1 for Arch Linux repositories.
While Archinstall remains optional, it provides users with a guided way to configure an Arch Linux installation without manually performing every step described in the Arch installation guide. Version 4.5 concentrates primarily on hardware support, installer reliability, security, and expanding the range of systems that can use the guided installation process.
AArch64 Support Gets a Major Upgrade
One of the biggest changes in Archinstall 4.5 is improved support for AArch64, the 64-bit ARM architecture.
The installer can now handle GRUB and Limine EFI installations on AArch64 systems. It also gains support for the proper AArch64 root partition type GUID.
Previously, parts of Archinstall's bootloader configuration were more heavily oriented toward x86_64 installations. The latest changes make its guided installation workflow more useful on ARM64 hardware.
AArch64 has become increasingly important throughout the Linux ecosystem. The architecture can now be found in cloud servers, development boards, laptops, workstations, and specialized computing platforms.
Supporting both GRUB and Limine EFI installations gives Archinstall more flexibility when preparing these systems.
GRUB Can Now Be Installed on AArch64
GRUB remains one of the most widely used Linux bootloaders, and Archinstall 4.5 extends its installation logic to AArch64 EFI systems.
This allows ARM64 installations to use a bootloader workflow much closer to what Archinstall already provides on conventional x86_64 UEFI computers.
The change doesn't mean every ARM device will automatically become compatible with Arch Linux. ARM hardware can still have highly platform-specific firmware and boot requirements.
It does, however, remove an important Archinstall limitation for AArch64 machines that provide conventional UEFI environments.
Limine EFI Support Expands to ARM64
The same architectural expansion applies to Limine.
Limine is a modern multiprotocol bootloader supported as one of Archinstall's bootloader choices. Archinstall 4.5 extends its EFI installation support to AArch64 as well.
Go to Full Article
- systemd 262 Released with Static PID 1, Intel TDX, TPM Improvements, and New Container Features
by George Whittaker
The systemd project has officially released systemd 262, delivering another substantial update to the system and service manager used by most major Linux distributions. The final release was tagged on September 22, 2026, following three release candidates earlier in the month.
Systemd 262 introduces improvements across service management, containers, virtualization, encrypted storage, TPM security, networking, journal recovery, system updates, and unattended installations. Among the most interesting additions are the ability to build systemd as a single statically linked PID 1 binary, Intel TDX support in systemd-vmspawn, Live Update Orchestrator integration, improved TPM-backed encryption, and new fallback unit files embedded directly into the systemd manager.
The release also contains a rather unusual development safeguard: an AI/LLM canary intended to help identify code contributions generated by AI that haven't been properly reviewed by a human before submission.
systemd 262 Is Officially Available
The final systemd 262 source was tagged by systemd developer Luca Boccassi on September 22.
The upstream tag identifies commit 8cc40e0c5e9234bf45084751ac53b1fbfe70b492 as systemd v262, following release candidates published throughout September.
The release has already begun reaching Linux distribution development repositories.
Debian accepted systemd 262-1 into Debian Unstable on September 22, while Fedora has prepared systemd 262 packages for Fedora 45.
As usual, the speed at which systemd 262 reaches ordinary users will depend on each distribution's update policy.
systemd Can Now Become a Single Static PID 1 Binary
One of the most interesting changes in systemd 262 is support for building systemd as a single statically linked PID 1 and executor binary.
The feature is primarily intended for extremely small container environments.
Normally, systemd depends on a collection of dynamically linked libraries and supporting components. That architecture makes sense for a complete Linux distribution, but containers sometimes need a much smaller runtime environment.
The new static configuration makes it possible to create a more self-contained systemd executable suitable for minimal container images.
These builds avoid dynamically loading optional libraries and use simplified mechanisms for resolving users and groups rather than relying on the complete Name Service Switch infrastructure.
This doesn't mean normal Linux distributions will suddenly replace their standard systemd packages with a giant static executable. The capability is specifically useful for specialized container and minimal-system deployments.
Go to Full Article
- Ubuntu Container Escape Vulnerability Gets Public Exploit Before Kernel Patch Arrives
by George Whittaker
Ubuntu administrators running containerized workloads have a new Linux kernel security problem to watch closely. Public exploit code is now available for CVE-2026-80521, a Linux kernel use-after-free vulnerability that can allow an unprivileged process inside a container to escape and obtain root privileges on the underlying host.
Security firm DepthFirst published its research and exploit on September 22, 2026, demonstrating the attack against Ubuntu 26.04 LTS. The underlying Linux kernel vulnerability had already been fixed upstream on August 6, but as of September 23, Ubuntu's security tracker still lists the main kernel package in Ubuntu 26.04 LTS as "Vulnerable, work in progress," while Ubuntu 24.04 LTS is also listed as vulnerable.
The situation is particularly important for Docker, Kubernetes, cloud infrastructure, and other environments that run potentially untrusted workloads because the vulnerable kernel functionality can be reached through ordinary operations available inside standard containers.
There is currently no confirmed evidence that CVE-2026-80521 is being actively exploited in real-world attacks, and the vulnerability isn't listed in CISA's Known Exploited Vulnerabilities catalog. The availability of working public exploit code nevertheless makes the patch gap considerably more important.
CVE-2026-80521 Is a Linux Kernel Vulnerability
Although Ubuntu is receiving much of the attention because the newly published exploit specifically targets it, CVE-2026-80521 is fundamentally a Linux kernel vulnerability.
The problem exists in the kernel's AF_UNIX socket subsystem, specifically within its garbage collection mechanism.
AF_UNIX sockets, commonly called Unix-domain sockets, provide local inter-process communication between applications running on the same system.
Unlike conventional network sockets, they don't need to communicate across a network. They are widely used by Linux applications and services for fast communication between local processes.
They also support passing file descriptors between processes through SCM_RIGHTS messages, and it is the kernel's management of these references that creates the conditions for CVE-2026-80521.
A Race Condition Leads to Use-After-Free
At the technical level, CVE-2026-80521 involves a race condition inside the AF_UNIX garbage collector.
The kernel needs to track references between Unix sockets when file descriptors are passed between processes. Circular references can develop, where one socket effectively references another while that socket references something else in the same group.
Linux represents these relationships internally and periodically determines which references can safely be removed.
Go to Full Article
- Fedora Linux 45 Beta Released with Python 3.15, GCC 16.2, and Major Security Changes
by George Whittaker
The Fedora Project has officially released Fedora Linux 45 Beta, giving users an early look at the technologies expected to form the foundation of the final Fedora 45 release. The beta became available on September 15, 2026, after Fedora's Quality team approved Release Candidate 1.3 for publication.
Fedora 45 Beta brings significant changes throughout the operating system, including Python 3.15, GCC 16.2, glibc 2.44, GNU Binutils 2.47, Go 1.27, LLVM 23, Podman 6, stricter RPM signature verification, improved DNF5 protections, a new userspace virtual console, standardized desktop secret storage, and substantial installer improvements.
The release is available across Fedora Workstation, KDE Plasma Desktop, Server, Cloud, IoT, Atomic Desktops, Spins, and Labs, although a few prerelease images are excluded.
Fedora 45 Beta Is Now Available
Fedora Linux 45 Beta represents the final major public testing milestone before Fedora 45 reaches stable status.
Fedora describes its beta releases as code-complete previews that closely represent what users should expect from the final version. Development isn't finished, however, and bugs or incomplete migrations can still be discovered during real-world testing.
Fedora 45 Beta is currently available in several major editions:
Fedora Workstation 45 Beta Fedora KDE Plasma Desktop 45 Beta Fedora Server 45 Beta Fedora Cloud 45 Beta Fedora IoT 45 Beta Fedora Atomic Desktops Fedora Spins Fedora Labs
Existing Fedora installations can also be upgraded to the beta using Fedora's DNF system-upgrade process.
Fedora's official Workstation download page confirms Beta 1.3 images for both x86_64 and AArch64 systems.
A New Virtual Console with kmscon
One of Fedora 45's more unusual system-level changes is the replacement of the traditional in-kernel console with kmscon.
Fedora describes kmscon as a modern userspace virtual terminal implementation that provides smoother rendering, better internationalization and font handling, improved visual integration, and security improvements compared with the older console infrastructure.
This affects the virtual terminals users encounter outside their normal graphical desktop session.
Most desktop users spend relatively little time interacting directly with these consoles, but they remain important for troubleshooting, system administration, servers, recovery operations, and systems running without a graphical environment.
Moving that functionality into userspace also gives Fedora more flexibility for future development instead of relying entirely on the legacy kernel console implementation.
Go to Full Article
|
