'AgentCorruption' Puts AWS Environments at Risk With Single Prompt

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.
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:

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.
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.

What Happened: Bipartisan leaders from the powerful House Energy and Commerce Committee launched an inquiry on Wednesday into the Amateur Athletic Union, criticizing the sprawling youth sports organization for its handling of child sexual abuse allegations and demanding answers, citing reporting by ProPublica and The Washington Post.
What They Said: “It is unacceptable that AAU is failing to implement standard reforms to protect child athletes, and is misleading the public, parents, and athletes about preventative measures in place within AAU sports,” the letter reads.
The committee chair, Kentucky Republican Brett Guthrie, called ProPublica and The Post’s reporting “deeply disturbing” in a statement on Thursday, saying it “raises serious questions about the organization’s actions over the past decade.”
“Our Committee is seeking information on how the AAU’s policies have potentially fallen short, and what needs to be done in order to protect young athletes,” Guthrie said.”
The members of the committee, which in 2018 investigated systemic failures surrounding sexual abuse by former USA Gymnastics doctor Larry Nassar and others, said in the letter that they were “seeing parallels” between its past investigation and “what is being uncovered within the AAU today.”
The letter is addressed to Jo Mirza, the AAU’s president, and asks detailed questions about the organization’s operations, taking the extra step of demanding a briefing from Mirza to the committee by Oct. 21. Among questions about its safety policies and coach training, the committee asks Mirza to lay out how many sexual abuse allegations the nonprofit receives each year and how many coaches it disciplines, information that has long been shrouded in secrecy. The AAU declined to provide the data to ProPublica and The Post. The AAU does not publish a list of banned coaches like many other youth sports groups do, and ProPublica and The Post found that it has used confidential arbitration clauses to keep lawsuits from child sexual abuse victims from being heard in open court.
The letter is signed by Guthrie, ranking Democrat Frank Pallone Jr. from New Jersey and representatives in charge of oversight and investigations.
Background: ProPublica and The Post found that the AAU, which has some 760,000 athletes and coaches nationwide, is failing on nearly every level to adequately protect young athletes from sexual abuse — breaking pledges it made in the wake of a 2011 sexual abuse scandal involving its CEO and young basketball players.
The investigation found that the AAU has become a haven for coaches suspected of abuse, according to a review of public disciplinary lists and interviews with current and former executives from six national sports governing bodies and other key stakeholders.
The AAU, the investigation found, does not offer child abuse prevention training, though it claims to the public that it does. And ProPublica and The Post found that it has suppressed allegations of sexual misconduct, including against another top executive in 2018.
Why It Matters: The committee is one of the key congressional groups charged with overseeing the federal youth sports safety system. It has the power to push for changes in child safety law — and to force transparency from organizations like the AAU, which has repeatedly failed to deliver on past promises of reform.
In 2018, in the wake of the allegations against Nassar, scrutiny from Congress led to the passage of a law known as the Safe Sport Act. It created the U.S. Center for SafeSport, an oversight group, to investigate allegations of sexual misconduct and gave it the power to suspend or ban coaches for life.
But SafeSport has jurisdiction only over national sports governing bodies, like USA Gymnastics and USA Volleyball, that are overseen by the Olympic and Paralympic Committee — meaning much of the law does not apply to the AAU.
The law does require “all amateur sports organizations” — not just governing bodies — to “offer and provide consistent training to all adult members … regarding prevention and reporting of child abuse.” The Energy and Commerce Committee’s letter cites that provision of the law and demands that the AAU explain how it complies.
Response: In a statement, the AAU said, “As always, we will cooperate fully and respond appropriately to any questions or requests from congressional committees or U.S. government agencies.”
Previously, the AAU told ProPublica and The Post that it is “committed to protecting its athletes through comprehensive protection policies overseen by our Compliance Department,” and said it has an “ongoing commitment to providing a safe, secure, supportive, and trusted environment where athletes can thrive.”
The post U.S. Lawmakers Launch Sexual Abuse Probe of Youth Sports Giant AAU appeared first on ProPublica.
Grâce à notre fantastique communauté de traducteurs et traductrices, #PeerTube est traduit dans près de 40 langues !
Vous aussi, vous pouvez contribuer à traduire PeerTube en utilisant notre plateforme auto-hébergée #Weblate !
Bonjour
j’ai utilisé un modèle framaform pour un questionnaire mais je n’arrive pas à le paramétrer pour que les personnes qui répondent n’aient pas à s’inscrire car c’est un frein a leur participation
comment faire
1 message - 1 participant(e)

When SpaceX’s giant Starship rocket exploded over the Caribbean last year, the internet lit up with videos from airline passengers, island tourists and locals showing flaming debris shooting across the sky. Even some airline pilots recorded the fiery aftermath as planes scrambled to move out of its path.
Some of those videos of Starship’s seventh test flight — including ones taken from Disney and Royal Caribbean cruise ships and a Club Med resort — went on to play a role in the company’s efforts to count and track pieces of debris after the explosion, a report obtained by ProPublica says.
The report — obtained by ProPublica from the Federal Aviation Administration through a freedom of information request — shows video captured a fireball, then a shower of sparkling debris in the sky moments after the explosion. It includes maps pinpointing where the images were shot, which helped the company understand how debris tumbled to earth after the blast.
“At 1 minute 42 seconds, the debris cloud is observed transiting behind the cruise ship,” says the report, which SpaceX provided the FAA two weeks after the so-called mishap.
Such reports are required by federal rules in the days after a rocket failure and are supposed to describe what happened and where hazardous debris landed. The information is key for the FAA’s efforts to keep busy air traffic corridors safe at a time of rapid growth in the commercial space industry as companies like SpaceX develop and test rockets that they hope will eventually reach the moon and Mars.
During launches, the FAA preventively closes airspace. It has also been forced to clear areas quickly after test flights of massive spacecraft went wrong.
Starship flights 7 and 8 broke apart last year and scattered debris above airline traffic over the Caribbean. Before Flight 9, the FAA moved to greatly increase the size of the airspace it walled off pre-launch.
The agency defined its no-fly zones, which are closed to airplane traffic during a launch, and its so-called debris response areas, which are closed after a mishap, using information from SpaceX and modeling from Space Force, the branch of the military that deals with the nation’s space interests, to predict where debris might fall.
Nearly doubling those pre-launch no-fly zones “only makes sense if the prior margin was judged inadequate rather than just unlucky,” said Moriba Jah, a professor of aerospace engineering at the University of Texas at Austin.
Earlier this year, the FAA issued a warning that rocket launches could “significantly reduce safety” for airplanes, after ProPublica reported that 21 planes appeared to make sudden turns to exit or avoid an FAA-designated emergency no-fly zone in the minutes after the Flight 7 explosion. Such disruptions are likely to become more frequent. SpaceX is seeking to launch Starship up to 76 times a year from Cape Canaveral, Florida.
The FAA provided ProPublica the reports on Starship flights 7, 8 and 9 — all of which involved mishaps — after we requested them under the Freedom of Information Act. The FAA redacted the vast majority of all three reports, citing, among other things, exemptions in the law that protect confidential business information from disclosure. The blackouts were, in part, a reflection of SpaceX’s objections; FAA allowed the company to challenge the release of information it deemed proprietary.
The FAA refused to release information that would show SpaceX’s estimates of where debris fell during the three rocket failures. It’s unclear what the agency or the company knows about how close any airplanes came to falling debris.
“Withholding the underlying debris estimates makes it impossible for anyone outside SpaceX and FAA to check whether that pattern is improving or repeating,” Jah said. “Given a regulator already revised its own safety margins once, the public has a real interest in seeing the data behind both the old margin and the new one.”
The unredacted part of the report did not show whether the debris from the Flight 7 explosion fell where SpaceX and the FAA expected it to. But the references to Disney and Club Med guests’ video suggest SpaceX did not have a full picture of where the debris landed without them. “I would read it as evidence their own tracking did not carry cleanly through the debris cloud phase, so they used the public to fill the gap,” Jah said.

SpaceX did not respond to requests for comment. The company has said that it learns from its mistakes and that each test improves Starship’s reliability. Last December, it said on X that “SpaceX is committed to responsibly using airspace during launches and reentries, prioritizing public safety to protect people on the ground, at sea, and in the air.”
The FAA did not respond to a request for comment, nor did Disney, Royal Caribbean or Club Med.
Ron Madler, a professor of aerospace engineering at Embry-Riddle Aeronautical University, said the videos could help SpaceX “either confirm their breakup models or possibly to improve them.”
The mishap report for Flight 8, which rained debris near the Bahamas, said before that flight’s explosive failure, SpaceX did not have the proper “test stand” that was capable of testing the rocket’s engines “for a full Starship mission.” The remainder of the page was blacked out, so it was unclear from the report whether the company had found another way to fully test the engines before launch.
Flights 7 and 8 both involved the same model. Both ended in engine-related failures.
Text in the report around the statement about the test stand was redacted. But Jah said it “means some part of the engine’s actual flight behavior was being verified for the first time in flight rather than on the ground.”
John Crassidis, an aerospace engineering professor at the University at Buffalo, said launching before having a fully capable test stand was likely “a cost-saving decision.” In building rockets, he said, SpaceX CEO Elon Musk has used both the old approach of launching and then fixing any issues that arise, and the newer approach of running simulations and ground tests first to head off problems.
“Doing too much of the old school can lead to too many mishaps and cost overruns,” he said. “Doing too much of the new school leads to long times to get things done and a reduction in flexibility.”
The post Club Med, a Disney Cruise and an Exploding Starship: SpaceX Used Bystander Videos to Track Falling Debris appeared first on ProPublica.
Pour les résultats des sondages, on peut exporter le tableau, mais comment exporter les réponses sous forme de graphiques créés par framaform ?
1 message - 1 participant(e)

The nation’s largest professional group of pediatricians has renewed its call for a nationwide ban on the sale and distribution of unpasteurized milk and other raw dairy products, according to a policy statement it published earlier this week.
The revised guidance from the American Academy of Pediatrics warns of the serious health risks from consuming raw dairy products, particularly for children, as well as pregnant and immunocompromised people.
“More and more people are discussing this as a potentially healthful thing to do, when in fact it’s a highly risky thing to do,” said the academy’s president, Dr. Andrew Racine. “So our responsibility, as the leading voice of pediatric healthcare in the United States that’s dedicated to the health and well-being of children, is to make sure that the accurate, evidence-based information is out there.”
The revised statement follows ProPublica reporting that dived deep into the causes and severe consequences of America’s current fascination with raw milk, which has not been heated to kill off harmful bacteria. Once limited to the fringes of health-food culture, unpasteurized milk has morphed into a widespread movement rooted in wellness trends and institutional distrust. Today, more than 10 million Americans drink it.
Most scientists and health experts agree that raw milk has no significant, proven nutritional benefits over its pasteurized counterpart and that it cannot treat or cure any disease. It also subjects its consumers to over 100 times the risk of foodborne illness, which can be especially dangerous for young children. Before milk pasteurization was widely adopted a century ago, thousands of children died each year from diseases linked to contaminated dairy.
As it has grown in popularity in recent years, raw dairy products have contributed to numerous outbreaks of pathogenic diseases, such as salmonella and E. coli. Over the past two years, nine states have experienced outbreaks that regulators have linked to raw dairy. Just last month, federal regulators linked an E. coli outbreak to unpasteurized cheese. Thirteen people fell ill, more than half of whom were young children.
As illnesses have surged, high-level lawmakers and government officials, including Health Secretary Robert F. Kennedy Jr., have championed the industry instead of curbing it. In his federal role, Kennedy said he was “advocating” for raw milk and celebrated the release of a report to Make America Healthy Again with a toast of raw-milk shooters in the White House. The health department did not respond to ProPublica’s questions about the new professional guidance or the pediatric group’s call for a ban on raw milk sales.
Rep. Rosa DeLauro, a Connecticut Democrat who chairs the Congressional Food Safety Caucus, told ProPublica that she is taking the guidance of the academy “very seriously.”
“They see firsthand what these illnesses can do to children,” she said in an emailed statement. “Right now, Secretary of Health and Human Services RFK Jr. cannot even bring himself to tell parents not to give it to their kids.”
DeLauro said she was “supportive of any policy that reduces risk of exposure to harmful foods,” including putting warning labels on raw-milk products and maintaining adequate funding for outbreak prevention and tracking.
Federal law restricts the sale of raw milk across state lines, but states can decide how it can be sold within their boundaries. In recent years, proponents have fought to increase access to raw milk within states, often opposing efforts to limit its sales. People can legally purchase raw milk in all but a handful of states, either directly from a store or from a farmer, or even as “pet food.”
Last week, ProPublica detailed the case of two girls severely sickened last year after consuming raw goat milk from an unregulated farm in southern California. The state, which is teeming with black-market dairies, did little to punish the farmer who sold the families the milk. It allowed her to provide her own sample for testing, weeks after the outbreak began, and did not independently sample her grounds for traces of the pathogen, as state investigators have done in other cases. (The farmer told ProPublica that her milk, which tested negative for pathogens, did not cause the outbreak and claimed the families had knowingly bought milk that was not for human consumption, which they deny.)
The mother of one of the girls, a toddler who nearly died, had read about the purported benefits of unpasteurized milk on a site for the Raw Milk Institute, a nonprofit founded by Mark McAfee, one of the nation’s most prolific sellers. In a profile of the California farmer, ProPublica chronicled how social media influencers have amplified his claims and helped him build what is now a $30 million-a-year business even as regulators have linked it to more than a dozen recalls and outbreaks that have sickened hundreds. (McAfee previously defended the claims made on the institute’s website and maintained to ProPublica that raw milk still has therapeutic benefits.)
Members of the academy said they read and circulated ProPublica’s reporting as they drafted their statement.
“This product is being marketed to families as being beneficial for their kids,” said Dr. Adam Ratner, a pediatric infectious disease doctor in New York City and one of the lead authors of the academy’s revised statement. “They don’t see the risks, and unwittingly they end up making a decision that is much more dangerous.”
The academy first published a policy statement on raw milk in 2014, endorsing a nationwide ban on its sale and encouraging its members to reach out to state representatives to advocate for such a restriction. The statement published this week reaffirms this appeal with recent epidemiological evidence. In addition, it cites a growing concern of highly pathogenic avian influenza, which has been shown to contaminate unpasteurized milk.
Racine, the academy’s president, told ProPublica that the policy was also updated on account of “the rise in the discussion about the alleged benefits of raw milk and the fact that more people are experimenting with using it.”
“Prevention really is the best single way to keep children healthy and safe, and this is a preventive move,” he said. “The more that we can disseminate this information to a greater number of people, the healthier we’re going to be able to keep the children of this country.”
The post American Academy of Pediatrics Renews Call for Ban on Raw Milk appeared first on ProPublica.
Le limitazioni su Android dello Smart Tag 3 di Samsung sono emerse come una doccia fredda per molti, gettando un'ombra su quello che sembrava un lancio quasi perfetto. Quando Samsung ha presentato il suo nuovo tracker, l'entusiasmo era palpabile, soprattutto per l'apertura verso l'ecosistema Apple.
Ma cosa è successo sul fronte Android? La realtà, purtroppo, si è rivelata molto diversa dalle aspettative iniziali.
Ricordi l'annuncio iniziale? Samsung aveva reso i suoi tracker compatibili con gli iPhone, una mossa strategica per ampliare la propria base di utenti. Poco dopo, una dichiarazione ufficiale sembrava confermare la notizia più attesa: la compatibilità con qualsiasi dispositivo Android dotato di Google Play Store. Sembrava la mossa perfetta per un ecosistema aperto e competitivo. Questa comunicazione aveva generato un'ondata di ottimismo. Infatti i possessori di Pixel, Xiaomi e altri brand potevano finalmente considerare l'acquisto di uno Smart Tag, anche per proteggersi da eventuali stalker. Purtroppo, la speranza è durata molto poco.
A fare chiarezza, involontariamente, è stata la redazione di Android Authority. Hanno provato a configurare il nuovo Smart Tag 3 di Samsung utilizzando un Google Pixel. Il risultato è stato un secco messaggio di incompatibilità.
Questo semplice test ha svelato una realtà ben diversa da quella promessa. Di fronte all'evidenza, Samsung ha dovuto fare marcia indietro. La nuova dichiarazione ha cancellato ogni dubbio: il dispositivo funziona solo ed esclusivamente con smartphone Galaxy. Un cambio di rotta di 180 gradi che ha lasciato molti utenti delusi.
Perché esiste questa limitazione così stringente? Il problema non risiede nell'hardware del tracker, ma nel software necessario per il suo funzionamento.
Per utilizzare lo Smart Tag 3 di Samsung sono infatti necessarie due applicazioni specifiche:
La dichiarazione iniziale di compatibilità universale era, con ogni probabilità, frutto di un errore di comunicazione interna. Un passo falso che ha generato false aspettative e confusione.
Per eliminare ogni dubbio, un portavoce di Samsung ha chiarito la situazione in modo inequivocabile. Ha affermato che lo Smart Tag 3 "si connette e funziona attualmente solo con i dispositivi Galaxy [...] e al momento non ci sono piani per supportare altri dispositivi Android."
Nessuna promessa, nessuna roadmap futura. La decisione è chiara. L'ecosistema Smart Tag rimane un'esclusiva per gli utenti Samsung su Android. Una scelta che, se da un lato rafforza il brand, dall'altro delude una vasta fetta di mercato.
In sintesi, la situazione è molto semplice. Se possiedi uno smartphone Samsung Galaxy, lo Smart Tag 3 resta un ottimo prodotto. Se invece hai un dispositivo di un altro brand, devi guardare altrove. Il tracker non funzionerà con il tuo telefono, nonostante le dichiarazioni iniziali.
Questa vicenda insegna a valutare con attenzione le comunicazioni aziendali, attendendo sempre le conferme pratiche. Per chi possiede uno smartphone non Samsung, questa notizia cambia completamente le carte in tavola.
L'articolo Smart Tag 3 di Samsung e le limitazioni su Android proviene da sicurezza.net.