โŒ

Reading view

There are new articles available, click to refresh the page.

Someone Forked systemd Over Its New Birth Date Field

The blog Linuxiac reports: A new systemd fork has appeared with a specific purpose: removing systemd's recently added support for storing a user's birth date in JSON user records. The fork, called Liberated systemd, published its first tagged release as v261 shortly after the official systemd 261 release. In other words, the fork follows upstream systemd while reverting the change that added the new optional birthDate field. Importantly, this is not a new init system, a wider redesign of systemd, or a general-purpose alternative to the upstream project. Its stated purpose is to remain close to upstream systemd while removing what the author describes as "surveillance enablement"... The author recommends testing the fork in a virtual machine before using it on real hardware and warns nightly builds are more likely to be unstable than named releases.

Read more of this story at Slashdot.

After Six Years Of Work and Over 360 Patches, Linux 7.2 Finally Removes Bug-Prone strncpy

Tech Times reports: Linux 7.2's merge window closed out a cleanup campaign on Friday that most kernel developers had stopped expecting to see end: the complete removal of strncpy(), a C string-copy function that the kernel's own documentation labels "actively dangerous," from every subsystem, driver, and architecture-specific file in the kernel source tree. The merge landed June 20, 2026. After around 362 commits spread across six years of incremental work, no call site using the function remained, and the function itself โ€” including the last per-CPU-architecture optimized implementations โ€” was struck from the source. The removal matters beyond housekeeping. strncpy() is a persistent source of a specific class of memory error: kernel buffers that contain sensitive data can leak bytes past an unterminated string boundary, a pattern that enables memory disclosure vulnerabilities. Eliminating the function from the tree removes that entire class from the kernel's attack surface โ€” and, critically, makes strncpy() unavailable to any future contributor, turning a best-practice suggestion into an enforced policy. Phoronix notes it's replaced by five different functions: In place of strncpy, Linux kernel code should use strscpy() for NUL terminated destinations, strscpy_pad() for NUl-terminated destinations with zero-padding, strtomem_pad() for non-NUL-terminated fixed-width fields, memcpy_and_pad() for bounded copies with explicit padding, or memcpy() for known-length memory copies. "The reason five functions were needed," explains Tech Times, "is that different parts of the kernel were using strncpy() for five semantically distinct memory operations โ€” each with a different intent, different termination requirement, and different padding behavior. " The original function obscured all of those differences under a single ambiguous name. The 362-commit campaign to replace it was, in effect, a codebase-wide audit that forced every call site to declare its actual intent in code That is an engineering outcome with lasting value: the kernel's string-handling semantics are now explicit where they were previously implicit, and future maintainers can read a function name and understand what a copy operation actually does.

Read more of this story at Slashdot.

Preparing for the worst

PATCH WATCH By Susan Bradley We might be a bit busy in the next few months. Not with updates, but dealing with headlines. Why? Because AI tools are now turning to the task of reviewing a lot of code that hasnโ€™t been looked at in a long time. First up? No, not Windows. Not Apple. [โ€ฆ]

โ€˜Copy Failโ€™ is a real Linux security crisis wrapped in AI slop

Attackers are actively exploiting a Linux vulnerability in the wild, and researchers warn that the fallout could be broad โ€” anyone with authenticated local access can leverage it to gain total control of a system.ย 

But the story behind CVE-2026-31431 is almost as interesting as the bug itself. Theori, the company that discovered the bug, leaned heavily on AI to find and initially disclose it. The result is a case study thatย  underscores the challenges that occur when the relentless hunt for defects collides with marketing impulses and inflated AI-generated language that was long on bluster but lacked technical details.ย 

Theori dubbed the high-severity vulnerability โ€œCopy Failโ€ with a vanity domain containing AI-generated content, and warned that every mainstream Linux kernel built since 2017 is in scope of potential exploitation resulting in root access.ย 

Theoriโ€™s AI-powered penetration testing platform, Xint, discovered the local privilege-escalation flaw in a Linux kernel moduleย and reported it to the Linux kernel security team March 23. Major Linux distributions affected by the vulnerability had issued patches prior to Theoriโ€™s disclosure, which it published alongside a proof-of-concept exploit.ย 

The Cybersecurity and Infrastructure Security Agency added CVE-2026-31431 to its known exploited vulnerabilities catalog Friday.

Researchers have yet to determine how many organizations have been impacted by the flaw, but they noted that critical requirements for exploitation, specifically local access achieved through a separate exploit or pathway to unauthorized access, should limit potential exposure.

โ€œThe attacker would need to have already established a foothold on the target system either through some means of legitimate access or another exploit,โ€ Spencer McIntyre, secure researcher at Rapid7, told CyberScoop. โ€œThatโ€™s a large limiting factor since this vulnerability would therefore need to be paired with another.โ€

Theoriโ€™s disclosure turned heads among other vulnerability researchers who noted the defectโ€™s broad potential impact, but also for lacking details about the proof-of-concept exploit.ย 

โ€œThe exploit is real, there is something to worry about, but understandably, teams now have to do additional validation to know how to parse the extreme AI FUD (fear, uncertainty and doubt) from [Theoriโ€™s] blog post,โ€ Caitlin Condon, vice president of security research at VulnCheck, told CyberScoop.ย 

โ€œItโ€™s not helpful that the blog is AI slop, because it detracts from technical reality,โ€ she added.ย 

Theori acknowledges it used AI to discover and describe the vulnerability, explaining that itโ€™s focusing on finding and fixing a large amount of defects.ย 

โ€œWe used AI to help craft the disclosure site and the blog post to help speed things up, but all material was thoroughly reviewed by our internal teams for accuracy,โ€ said Tim Becker, senior security researcher at Theori.ย 

Theori is intentionally withholding additional details until the patch is broadly applied, he added.

โ€œWe stand by our technical description of the vulnerability. Helping downstream users to understand the impact of a security bug has always been a challenge for security researchers,โ€ Becker said. โ€œCopy Fail allows for trivial privilege escalation on most desktop and server Linux distributions. It also has implications for containerization including Kubernetes.โ€

Other researchers have drawn similar conclusions, noting that exploitation can be automated and doesnโ€™t require specialization.ย 

Meanwhile, hundreds of additional proof-of-concept exploits have surfaced since the vulnerability was disclosed five days ago. โ€œAs expected, the majority of these appear to be copycat AI PoCs that do nothing but add banners or different colors to the command-line interface. Many new PoCs are simply ports of the original AI PoC to a different programming language,โ€ Condon said.ย 

โ€œOrganizations should exercise caution when running untested research artifacts, including AI-generated exploit code that isnโ€™t fully explained,โ€ she added.ย 

Becker said Theori is aware of the burden defenders confront, and insists the companyโ€™s reports contain enough information for organizations to quickly triage and validate its findings.

The post โ€˜Copy Failโ€™ is a real Linux security crisis wrapped in AI slop appeared first on CyberScoop.

โŒ