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

CVE-2024-46865

A critical vulnerability in the Linux kernel's fou module could allow an attacker to use an uninitialized variable, leading to potential compromise of confidentiality, integrity, and availability. The flaw has been resolved in the kernel source, and applying the appropriate kernel update mitigates the risk. No known exploitation or public exploit is currently reported.

publishedSep 27, 2024
last modifiedAug 4, 2026
sourcesNVD
severity · cvss
9.8
critical · how bad it is
exploitation · epss
<1%
13th 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 versions 5.10.226, 5.15.167, 6.1.110, 6.6.51, and 6.10.10 are listed as affected.

02

Real-world impact

If exploited, an attacker could achieve high impact on confidentiality, integrity, and availability of the system.

03

Why this severity

The CVSS v3.1 base score is 9.8 (Critical) due to network‑adjacent attack vector, low attack complexity, no privileges or user interaction required, and high impacts across all three security properties.

04

What to do about it

official fix available
recommended steps
  1. 011. Obtain the latest Linux kernel update from your distribution that includes the fix for CVE-2024-46865.
  2. 022. Install the kernel update according to your distribution's standard procedure.
  3. 033. Reboot the system to load the patched kernel.

NVD-referenced vendor advisory (NVD description states the vulnerability has been resolved)

05

Timeline

  1. Sep 27, 2024 · Sep 27, 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

NVD advisory ↗Search 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 →