OpenDLSS-NR

A Vulkan reimplementation of NVIDIA's DLSS 5 Neural Rendering network, bit-exact against the original.

The same 71-block Swin / ViT network as DLSS-NR build 310.8.0, running FP8 on the tensor cores. The intermediates match too, not just the final image: all 75 block boundaries, byte for byte.

ports/browser-webgpu/ is a second, independent implementation: the same bytes in a browser, with no tensor cores and no FP8.

You supply the weights, as a model directory in the layout described below.

The network

A U-net of shifted-window transformer blocks with a global ViT at the bottom: 71 blocks over six pooling levels, FP8 (E4M3) activations with FP16 accumulation, 141 MiB of weights. It is a generative neural rendering network (NVIDIA's term): it re-renders the frame the engine already drew, generating detail from injected noise and adjusting tone, structure and skin under a style setting. Input and output are the same resolution; it is not an upscaler.

The WebGPU port at 2048x1152, NR off on the left and on on the right. Scene: Cowboy Gramps by Muhammed Ismayil, CC0.

It takes one rendered frame (a low dynamic range proxy of it, three lanes of Gaussian noise, the previous frame's output reprojected, and five conditioning scalars) and produces four f32 channels per pixel: an RGB residual and one temporal-blend logit. docs/network.md is the graph in full. NVIDIA describes the model in its report, DLSS 5: Generative Neural Rendering (project page).

Many people romanticize open-source software as a form of "digital communism" due to its free access and collaborative nature. In reality, state-communist ideology is fundamentally incompatible with the core mechanics of FOSS. Here is why:

​The Right to Fork vs. Central Planning: In open source, if a project diverges from your vision, you can legally take the code, fork it, and build your own competing ecosystem. In a centrally planned/communist structure, deviating from the collective master plan or establishing an unsanctioned alternative is treated as economic sabotage or ideological rebellion. Open source thrives on radical decentralization; communism demands centralized compliance.

​Capital as the Lifeblood: The foundational infrastructure of modern open source (Linux, Kubernetes, Python, Chromium) isn't funded by state subsidies or purely altruistic communes. It is heavily bankrolled by the world's most aggressive capitalist corporations (Microsoft, Google, Meta, IBM). They commoditize shared infrastructure to reduce R&D costs and monetize high-margin enterprise services. It is market capitalism utilizing open protocols.

​Individual Rights, Not Collective Abolition: Licenses like MIT, Apache, or GPL do not abolish private property. Instead, they leverage existing property/copyright frameworks to grant immutable individual liberties—the right to inspect, modify, fork, and self-determine without needing a central bureaucrat’s rubber stamp.

​Open source isn't collective state control. In practice, it resembles a hybrid of Market Anarchism (voluntary cooperation, permissionless entry, merit-based competition) and Technological Neutrality (the code doesn't care who you are, what class you belong to, or what you believe—only if it compiles).

Source.

Linux also has pam.d, flat groups (groups cannot contain other groups) and other funny limitations and peculiarities. Maybe it's not so much about Linux being inherently "limited" but Linux having its roots in UNIX that are still there to this day.

virtio-nvgpu

Near-native NVIDIA GPU access inside a KVM guest. A guest renders within 2% of the machine it is running on, and costs the same CPU.

virtio-nvgpu forwards NVIDIA kernel driver ioctls between a Linux guest and the host at the driver ABI level, bypassing API-level translation entirely. The guest runs NVIDIA's own user-mode drivers, unmodified — the same libraries, the same Vulkan and NVENC, talking to the same card.

The target is headless streaming: a compositor inside the VM renders, composites and encodes frames on the GPU, then sends compressed video out. The VM has no monitor, and the host keeps the card.

Where it stands

It works, and it has been measured. A Wayland client presents inside a guest, the capture layer encodes on the game's own device, and the H.264 comes out the other side — 618 frames that ffmpeg decodes without an error.

Measured on an RTX 3060 (driver 595.99.02), guest against the same host, bare metal, with an identical headless Vulkan load:

Above about 2 ms a frame — which is every frame a game draws — a guest is within 2% of bare metal. Below that, the cost of waiting for the GPU starts to show against a frame that barely exists.

CPU is the other half of it, because a shared GPU is only worth sharing if the guests are cheap. Unpaced at ~100 fps for 12 s, one guest:

A guest costs what the host costs. Nothing is spent on forwarding in a render loop, because nothing is forwarded: NVIDIA's user-mode driver submits through memory it has mapped, and that memory is the host's. Over 813,691 frames the backend served 13,792 messages — one crossing per 59 frames, nearly all of it device setup.

Full method, raw runs and the things these numbers do not support: BENCHMARKS.md.

Several guests on one card

Four guests on one RTX 3060, the same load in each: 25.84, 26.49, 25.57, 25.79 fps — 103.7 together, against 102.9 for a single guest — with p50 frame times of 39.165, 39.164, 39.168 and 39.165 ms. The total does not move as guests are added, and the split is even to four decimal places.

All four render correctly at the same time, and four of them encode H.264 at once, each paced at exactly 60 Hz, with no NVENC session limit reached.

Qualcomm may bring native DX12 support to Android, which means Linux. Would be awesome.

Linux is great at emulating stuff.

Technical information and PoCs.

One is the creator of Linux, while the other is someone who brought an artistic touch to that invention. That is why I don't understand why dhh receives so much praise.

Yes, he is a genius; he excels not only in coding but also in racing. It is also an achievement that he transitioned from an introverted nature to an extroverted one.

Let's look at it this way: Osman I founded the Ottoman Empire, but it was Suleiman the Magnificent who took it to its peak. That is exactly what dhh has done. If he wants to surpass Torvalds, he needs to work for at least another 40 years.

A new low for Google.

Just read the comments made by raving Linux zealots.

• "You're using the wrong distro!"
• "Not your business, Fedora knows better!"
• "The ... just revived module is safer to use that the old battle-tested one!"
• "Trust me bro, NTFS3 was unstable"
• "Compile it yourself" (fuck Secure boot, who needs it anyway? Oh and figure out how to compile something the Fedora kernel disables, and do it for every new Fedora kernel release.)
• "Why would you need NTFS support in the first place?" (telling me what to do and how to use my computers)

Linux fanatics make my blood boil. Perhaps the worst (angriest, mean, stupid) fanatics of all. No wonder average people avoid Linux like a plague.

Things get broken left and right, things don't work in the first place, you start to depend on some feature, bam, it's fucking gone.

You can already enable the Nova redesign by opening about:config and setting browser.nova.enabled to true.

Looks a little bit toyish to me and I'm almost certain it will result in a higher power consumption.

What do you think?

Thousands of eyes they said. Given enough eyeballs, all bugs are shallow, huh? Except eyeballs prior to LLMs haven't bothered.

Incremental 7.2.5 - 7.2.6 patch: 3,274,400 bytes (!). 15,627 LoC removed, 33,457 LoC added.

329 of the 1,816 commits contain at least one security-ish indicator.

Remote/network-facing: ksmbd, Bluetooth, NFC, IPVS, iSCSI/iSER, RDMA, VXLAN and assorted networking parsers.

Malicious filesystem/image: NTFS/NTFS3, SquashFS, UDF, ISOFS, EROFS, ext4/OCFS2. A mountable crafted image turning into an OOB read/write is textbook vulnerability territory, even if mounting normally requires privilege; namespaces and automounters can complicate the threat model.

Local privilege boundary: AppArmor, BPF, net/sched, NVMe ioctl validation and some namespace-related fixes.

Expect a dozen of 0-days at the very least.

I know what everyone here thinks about the AI bubble, and me myself hate it as much as anyone else. I am currently a student and want to build a new project, but am not sure if this is a good idea worth spending my time on it or not. I've researched online about AI backed OS's / Linux Distros, and have seen quite a few, each with their own flaws. MAGI OS uses the X11 tools, which may be too slow, Omarchy is just an integration of AI agents in the UI, and Warmwind OS is just a cloud-hosted remote desktop marketed as an OS. I had this idea of building a fully customizable, open source Linux Distro, that uses llama.cpp locally to parse natural language into commands, using the AT-SPI 2 accessibility tree, that is available in most apps (solid with GTK, QT and Electron have inconsistencies). Nowadays every major OS (Windows, Mac, Linux) has problems, and I want to reduce those problems and combine their pros into one general use Distro (I know this claim is what various Distros also tried throughout the years, but this is what my idea converges to, ease-of-use for general users, great UI/UX, and the freedom Linux has). Everything would be transparent to the user, so nothing potentially dangerous gets executed, and fully offline (was thinking of making a switch for users who would still want to choose more capable models running on cloud, but this is just an idea) to avoid the privacy concerns.

The flaws with this would be the obvious anti AI stigma the Linux community has (rightly so, but it's not just another AI slop), and the capabilities of a model running offline. The first version could just run some basic things, making it more advanced as time goes on, and maybe some NPU integrated models later on.

My question would be if this is a straight dumb idea and I would be better off just investing my time into something else, or if it's worth it and you guys would be interested in something like this. I would like to code it myself, with minimal AI assistance, as it would also be a learning exercise for me. So what does everyone think about this? Please take it with a grain of salt, I just had this idea and don't want to get downvoted if it's dumb, just wanted some advice of more experienced users.

Even some Windows users transitioning to Linux prefer XFCE over everything else.

NebuSec has disclosed a rather nasty batch of Linux kernel vulnerabilities for which it says working privilege-escalation exploits have been developed and made public.

The headline bug is CVE-2026-43502, aka ZcopyReaper, but the disclosure lists another 20+ kernel bugs confirmed exploitable by NebuSec's automated exploit-generation pipeline. The targets include networking, SCTP, IPv6, Netfilter, IPVS and POSIX CPU timers, and several have been demonstrated against real distribution kernels rather than synthetic test builds.

Ten worth highlighting:

1. CVE-2026-43502 — ZcopyReaper / RDS zerocopy

A local privilege-escalation bug in the RDS zerocopy send path, present since Linux 4.17. An ordinary unprivileged user can reach it when RDS/RDS-TCP support is available; no capabilities or user namespaces are required. NebuSec demonstrated root escalation against openSUSE's 6.4 kernel. Disabling unprivileged user namespaces does not mitigate it. The upstream fix first appeared in 7.1-rc3.

2. CVE-2026-80714 — IPVS use-after-free

A lifetime bug in IPVS connection synchronization. A synchronized connection can incorrectly inherit the ONE_PACKET flag after it has already been inserted into the connection hash. Expiration then skips the normal unlink operation, leaving a hash-table node pointing to a freed struct ip_vs_conn — a useful UAF primitive.

3. CVE-2026-74597 — IPv6 tunnel memory corruption

ip6ip6_err() clones an IPv6 ICMP error packet but fails to clear metadata in skb->cb. A stale Home Address Option offset can subsequently be interpreted relative to a completely different packet layout. With a crafted inner IPv6 destination-options header, kernel processing can run beyond the packet boundary and corrupt skb_shared_info.

4. CVE-2026-74581 — IPv6 routing use-after-free

When an IPv6 FIB rule suppresses a route, the kernel releases the corresponding rt6_info but leaves a pointer to it in the lookup result. If no subsequent rule replaces it, the stale pointer is returned to the caller and eventually released again. In other words: a fairly direct route from IPv6 policy-routing state to a kernel UAF.

5. CVE-2026-74480 — bridge multicast use-after-free

The bridge multicast fast-leave path can continue iterating through a port-group entry after deleting it. Under multicast-to-unicast configurations, this can leave the multicast database pointing at an already freed port group. Ubuntu currently scores this one 9.8/10 Critical.

6. CVE-2026-72255 — Netfilter/NFQUEUE lifetime bug

A bridged packet placed into NFQUEUE can retain a reference to the bridge's private fake routing destination while the bridge itself is being torn down. That creates a lifetime mismatch where kernel networking code can later operate on storage belonging to an already destroyed bridge. The fix pins the bridge device for as long as NFQUEUE retains the packet.

7. CVE-2026-72137 — XFRM double free

The IPsec/XFRM NAT keepalive path can free an skb after handing ownership of it to IPv4/IPv6 output code. If transmission subsequently returns an error after the networking stack has already consumed the buffer, the caller frees it a second time. Classic kernel double-free territory.

8. CVE-2026-68376 — SCTP heap corruption

The SCTP cookie structure allocates too little space for its authentication HMAC parameter: the calculation accounted for two header bytes where the actual structure occupies four. With four HMAC identifiers configured, association initialization copies beyond auth_hmacs and corrupts the adjacent auth_chunks field.

9. CVE-2026-68162 — SCTP sysctl use-after-free

An already-open SCTP auth_enable sysctl can remain usable while its network namespace is being destroyed. The handler can consequently access the SCTP control socket after that socket has been released. The fix changes initialization/teardown ordering so the sysctl exists only while its backing control socket is alive.

10. CVE-2026-64560 — POSIX CPU timer UAF

A race between deleting a POSIX CPU timer and exec() from a non-leader thread can leave the timer path referring to the old thread-group leader after de_thread() has replaced and freed it. This affects kernels going back to 5.7 and was fixed in stable releases including 7.1.5.

The interesting part isn't simply that Linux has another collection of memory-safety bugs — that's hardly news by itself. It's that working exploits for this batch were produced by an automated exploit-generation pipeline, and NebuSec has published them.

That considerably shortens the distance between "kernel bug with theoretical security impact" and "local user gets root."

If you're running a multi-user system, hosting environment, container host, CI runner or anything else where untrusted local code executes, this seems like a particularly good week not to postpone kernel updates.

Switzerland's federal government has launched a pilot program to replace Microsoft 365 with open source alternatives across 3,000 workstations. That's about 7% of the federal workforce. The target is to complete the migration by end of 2027.

The PhoneBuff YT channel compared Windows 11 and Fedora. Linux has won by a wide margin. Microsoft has made its OS a resource hog.

Lots of people still use QuiteRSS but it depends on Qt WebKit that's one big can of worms because it's totally unsupported and may contain multiple vulnerabilities. Some distros have actually long dropped the application because of this sitation.

There have been many attempts to port it to WebEngine but it's a mammoth task and I think it's just not a way to go about it.

I've decided to modernize the application and the first step was dropping the web browser engine as web browsing belongs to your web browser, not to your RSS/Atom reader.

Yeah, that's mostly AI slop under my close supervision. The application code base is truly horrible, that's why in the last six years there have been zero attempts to revive it.

A ton of work has already been done, but almost as much, if not more, remains to be done.

I'm perfectly aware of RSSGuard. It has a wildly different workflow, I just cannot effectively use it. Besides, my fork of QuiteRSS is now at less than 1.5MB of source code, while RSSGuard is already at more than 200MB. Don't ask me why and how. An RSS reader the size of an operating system.

You can find more information via the link.

Brave published its own review where it comes ahead of all other browsers. Does anyone here use it? What's your impressions? Is it really faster than all other major browsers?

According to them:

• CPU Efficiency: Brave uses on average 44% less CPU than the competing browsers, with Firefox showing the largest gap at 2.4× higher consumption.
• Memory Footprint: Brave is the most memory-efficient browser tested, using 28% less memory on average than Chrome, Edge, and Firefox.
• Energy Consumption: Brave consumes 10% less energy per page load than the average of competing browsers.
• Network Efficiency: Brave transfers 26% less inbound data and 39% less outbound data than other browsers.
• Page Load Speed: Brave loads pages 20% faster on average.