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

CVE-2024-40907

A bug in the Linux kernel’s ionic network driver can cause a kernel panic when packets are transmitted, leading to a system crash. The issue occurs because a freed memory page is reused without being cleared. The vulnerability has been fixed in newer kernel releases.

publishedJul 12, 2024
last modifiedAug 4, 2026
sourcesNVD
severity · cvss
9.8
critical · how bad it is
exploitation · epss
<1%
15th 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 users running versions that include the ionic driver, particularly kernel 6.9 and earlier. Any system that has not yet applied the patch is vulnerable.

02

Real-world impact

An attacker could trigger a kernel panic, causing the affected system to crash and become unavailable. This results in a denial‑of‑service for the host and any services running on it.

03

Why this severity

The CVSS score of 9.8 reflects that the flaw can be exploited remotely (network access) with no authentication or user interaction, and it completely compromises confidentiality, integrity, and availability. The low attack complexity and lack of required privileges make it highly dangerous.

04

What to do about it

official fix available
recommended steps
  1. 01Upgrade the Linux kernel to a version that includes the ionic driver fix (e.g., kernel 6.10 or later).
  2. 02Reboot the system to load the updated kernel.

NVD description indicates the vulnerability has been resolved in the kernel.

05

Timeline

  1. Jul 12, 2024 · Jul 12, 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 · 1d 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 →