Tag

Memory Corruption

All articles tagged with #memory corruption

technology14 days ago•3 min saved

Linux kernel pedit COW flaw lets local users gain root by poisoning in-memory binaries

A Linux kernel flaw in the traffic-control pedit action (CVE-2026-46331, 'pedit COW') lets a local unprivileged user corrupt the in-memory page cache and inject a root payload into a cached setuid binary, yielding root access without touching disk. The exploit requires unprivileged user namespaces with CAP_NET_ADMIN and has been demonstrated on RHEL 10 and Debian 13; Ubuntu variants show mixed susceptibility due to AppArmor defaults. Patches have been released by vendors; recommended actions are patching and rebooting, or mitigating by disabling the act_pedit module or turning off unprivileged user namespaces. Because the overwrite hits memory, file-integrity scans may miss it, and a compromised host should be treated as such.

via The Hacker News|

#cve-2026-46331 #linux-kernel #memory-corruption

security3 months ago•24 min saved

Ancient Telnet Hole Sparks Modern Worry: CVE-2026-32746 Pre-Auth RCE in Telnetd

Researchers analyze CVE-2026-32746, a pre-auth RCE in GNU inetutils Telnetd via a LINEMODE SLC buffer overflow. The issue stems from overflowing a small slcbuf when processing SLC triplets during LINEMODE negotiation, with exploitation heavily dependent on OS and architecture (64-bit vs 32-bit); while a reliable full RCE wasn't achieved across tested targets, a heap leak and an arbitrary-free primitive were demonstrated, potentially enabling code execution under favorable libc conditions. The vulnerability affects inetutils Telnetd and many forks across major distros (Ubuntu, Debian, FreeBSD, NetBSD, macOS, etc.), and patches have not been widely released at publication time. Detection strategies include probing for LINEMODE support and non-invasive overflow checks; watchTowr provides a detection artifact generator. Patch urgently, but note there is no universal fixed version yet; users should build from fixed commits or apply vendor mitigations.

via watchTowr Labs|

#cve-2026-32746 #inetutils #memory-corruption

spacetechnology2 years ago•2 min saved

"NASA Engineers Work to Restore Contact with Voyager 1, 15 Billion Miles Away"

NASA engineers have identified corrupted memory as the cause of Voyager 1's data transmission issues and are working on a remote fix for the hardware problem from 15 billion miles away. The corrupted memory, likely caused by either wear and tear or energetic particles, is hindering the spacecraft's Flight Data System (FDS) from operating normally. Despite being out of physical reach, engineers are optimistic about finding a software solution to enable Voyager 1 to resume sending science and engineering data back to Earth.

via The Register|

#hardware-issue #memory-corruption #nasa

spacetechnology2 years ago•3 min saved

"NASA Pinpoints Voyager 1's Data Transmission Glitch"

NASA engineers have identified a small portion of corrupted memory as the cause of Voyager 1's transmission issues, preventing the Flight Data System (FDS) from operating normally. The spacecraft, located 15 billion miles from Earth, has been beaming unreadable data for nearly five months. Despite the challenges posed by its distance and communication delays, engineers are optimistic about finding a way for the FDS to operate without the unusable memory hardware, allowing Voyager 1 to resume transmitting science and engineering data.

via Ars Technica|

#memory-corruption #nasa #space-probe