Vulnary
← back to the feed
Critical· 9.8official fix available

CVE-2024-26853

A flaw in the Linux kernel’s XDP_REDIRECT handling can corrupt memory and crash the system. It occurs when a network frame cannot be transmitted and is mistakenly freed twice. The result is a kernel panic that can be triggered by sending heavy traffic through an Intel i225 NIC.

publishedApr 17, 2024
last modifiedAug 4, 2026
sourcesNVD
severity · cvss
9.8
critical · how bad it is
exploitation · epss
<1%
47th percentile · chance of exploitation in 30 days
(ai-assisted) A model wrote this summary from the official data, so double-check it against the source before you act on it. Read the official advisory →
auto-deletes from the system
counting…on Sep 4, 2026

An official fix is available, so this entry is kept for 30 days and then removed automatically.

01

Who is affected

Linux kernel 6.8 and earlier, especially systems using Intel i225 network adapters and XDP_REDIRECT programs. Any user running a kernel that has not been patched for CVE-2024-26853 is at risk.

02

Real-world impact

An attacker can send crafted traffic that forces the kernel to crash, causing a denial‑of‑service. The crash can be triggered remotely over the network without any authentication.

03

Why this severity

The CVSS score of 9.8 reflects that the vulnerability is exploitable from the network, requires no privileges, and compromises confidentiality, integrity, and availability. The lack of authentication and the high impact of a kernel panic make it critical.

04

What to do about it

official fix available
recommended steps
  1. 01Upgrade the Linux kernel to a version that includes the CVE‑2024‑26853 fix. The patch is incorporated in the latest stable kernel releases. After upgrading, reboot the system to load the new kernel.

NVD-referenced vendor advisory

05

Timeline

  1. Apr 17, 2024 · Apr 17, 2024
    Published
    Disclosed and added to the National Vulnerability Database.
  2. Aug 4, 2026 · 2d ago
    Advisory updated
    The NVD record was last revised.
  3. Aug 5, 2026 · 22h ago
    Official fix available
    A vendor patch or mitigation now exists — see the remediation steps above.
06

How it’s attacked

Attack vectorNetwork (remote)
Attack complexityLow
Privileges requiredNone
User interactionNone needed
ScopeUnchanged
Confidentiality impactHigh
Integrity impactHigh
Availability impactHigh
07

References & advisories

(ai-assisted) A model wrote this summary from the official data, so double-check it against the source before you act on it. Read the official advisory →