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

CVE-2024-46690

A flaw in the Linux kernel’s NFS daemon can cause the system to crash or potentially allow arbitrary code execution when handling certain lease requests. The bug involves an unsafe pointer dereference that was not properly checked. The issue has been fixed in recent kernel releases.

publishedSep 13, 2024
last modifiedAug 4, 2026
sourcesNVD
severity · cvss
9.8
critical · how bad it is
exploitation · epss
<1%
8th 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, especially those running version 6.11 or later that include the NFS server component. System administrators and operators of Linux servers that export or mount NFS shares are affected.

02

Real-world impact

An attacker who can send crafted NFS requests could crash the NFS service, leading to a denial of service. If the memory corruption is exploited further, it could allow the attacker to execute arbitrary code on the server.

03

Why this severity

The CVSS score of 9.8 reflects that the vulnerability can be exploited over the network with no authentication or user interaction, and it compromises confidentiality, integrity, and availability of the affected system.

04

What to do about it

official fix available
recommended steps
  1. 011. Update the Linux kernel to version 6.11 or later, which contains the patch for the NFS daemon.
  2. 022. Reboot the system or reload the kernel to apply the update.

NVD description indicates the issue has been resolved in kernel 6.11

05

Timeline

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