CVE-2026-46300

This vulnerability is in how the Linux kernel processes network packets. Under certain packet-handling conditions, it can forget a safety label about shared memory fragments, which can lead to wrong behavior—like crashes or corrupted data—when the network stack later tries to modify those fragments. Think of it like losing a “do not edit directly” sticky note on shared pages: later steps may edit in place when they shouldn’t.

This matters if you run Linux kernel versions on these products: linux kernel, astra linux, red hat enterprise linux, red hat openshift container platform, AlmaLinux, red os, and red hat enterprise linux for nvidia. The attack is described as local with low authentication and no user interaction, so it’s mainly a concern where an attacker can run or influence requests from the same system context that triggers the kernel networking paths. The risk depends on reachability into the kernel networking processing that uses the coalescing behavior; exact “default exposure” is not yet known from the findings.

Verdict: AMBER. Even though no CISA KEV entry and no clear dated public exploitation report were found, this is a kernel memory-handling issue that can cause crashes or data corruption when triggered by a local low-auth attacker. Prioritize patching on affected systems through your standard update pipeline, especially on hosts where untrusted local users or services may be present.