News report
CISA Flags Three Linux Kernel Flaws as Actively Exploited
CISA added three Linux kernel vulnerabilities in kTLS, ebtables and AF_ALG to its Known Exploited Vulnerabilities catalog, with a September 21 federal remediation deadline.
On this page
| CVE | Kernel area | What the flaw does | Exposure notes |
|---|---|---|---|
| CVE-2025-39682 | kTLS receive path | Mishandles a zero-length record from rx_list, allowing later TLS records to be processed under incorrect assumptions | Red Hat says the issue is reachable when kernel TLS is in use |
| CVE-2026-53266 | ebtables SNAT | ARP hardware-address rewriting can write into an underlying nonlinear socket-buffer page | Red Hat says exploitation requires specific bridge netfilter rules and can lead to memory corruption, denial of service or local privilege escalation |
| CVE-2025-39964 | AF_ALG crypto API | Concurrent writes to one AF_ALG socket can interleave data and corrupt per-socket state | Red Hat describes a local-user path that can crash the system or corrupt cryptographic-operation results |
The CISA deadline is not a universal Linux end-user deadline
The September 21 date comes from CISA’s federal remediation policy; it should not be read as an operating-system-wide expiration date for every Linux PC. Consumer and enterprise distributions ship different kernel versions and frequently backport security fixes without changing to the newest upstream kernel version, so a version number alone is not enough to establish whether a particular installation is vulnerable.
For ordinary Linux users, the practical check is the security status published by the distribution that supplied the kernel. Systems running an unsupported kernel deserve particular attention because CISA explicitly notes that affected products can include end-of-life or end-of-service releases for two of the entries. Installing the distribution’s fixed kernel normally also means making sure the machine actually boots that fixed kernel afterward.
Why the distinction between CISA, upstream and distribution status matters
Linux kernel security fixes move through several layers. Upstream stable commits correct the underlying kernel code, but distributions decide which fixes need to be backported into the kernels they support. CISA’s KEV catalog adds another signal: evidence that attackers are actually using a vulnerability. Those three facts answer different questions and should not be collapsed into a single claim that every kernel below some version is unsafe.
Red Hat’s assessments illustrate the configuration dependence. It describes CVE-2025-39682 as a kTLS flaw that can be triggered only when the TLS ULP is in use, offers disabling the tls module as a mitigation, and describes CVE-2026-53266 as dependent on particular bridge netfilter rules. For CVE-2025-39964, Red Hat says preventing the af_alg module from loading can mitigate the issue. Those are vendor-specific mitigations rather than universal instructions for every distribution.
The useful takeaway for PC and server owners is therefore targeted rather than alarmist: because CISA has confirmed exploitation, check your distribution’s advisories for these three CVE identifiers, install the fixed kernel package when your system is affected, and do not assume that an old-looking kernel version is unpatched if your distribution backports security fixes.
Sources
Primary and technical sources
These sources support the reporting and analysis above. Current stories are updated when later evidence materially changes the facts.
01 Cybersecurity and Infrastructure Security Agency
Known Exploited Vulnerabilities Catalog02 Red Hat Product Security
CVE-2025-39682 Linux kernel kTLS vulnerability03 Red Hat Product Security
CVE-2026-53266 Linux kernel ebtables vulnerability04 Red Hat Product Security
CVE-2025-39964 Linux kernel AF_ALG vulnerability
Related
Continue from here
Useful next steps selected from the same technical reference and publication system.
Technical guide
Windows Page File Explained: Virtual Memory and Commit Limit
Understand what the Windows page file does, how it extends the system commit limit, how paging differs from RAM use, and why crash dumps can depend on it.
Tool
DDR Memory Latency Calculator
Convert DDR data rate and CAS latency cycles into CAS timing in nanoseconds.
Compatibility & upgrades
Laptop RAM Upgrade Compatibility: SODIMM, Soldered Memory, DDR4/DDR5, Capacity, and Mixed Modules
Check whether laptop RAM is actually upgradeable, then verify SODIMM versus soldered memory, DDR generation, slots, capacity, speed, and exact-model limits before buying.
Tool
DDR Memory Bandwidth Calculator
Calculate theoretical peak DDR memory bandwidth from transfer rate, bus width per channel, and active channel count.