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

CVE-2023-54269

A critical bug in the Linux kernel’s RPC subsystem can cause a double free, potentially crashing the system. The flaw occurs when an RPC request is deferred twice, leading to an invalid memory reference. The issue has been fixed in recent kernel releases.

publishedDec 30, 2025
last modifiedAug 4, 2026
sourcesNVD
severity · cvss
9.8
critical · how bad it is
exploitation · epss
<1%
7th 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 3, 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 older kernel versions that have not applied the latest security updates. Typical users include system administrators and anyone maintaining Linux servers or devices.

02

Real-world impact

An attacker could trigger the double free by sending specially crafted RPC requests, causing the kernel to crash or potentially execute arbitrary code if the crash is exploitable. This could lead to denial of service or privilege escalation on the affected system.

03

Why this severity

The CVSS score of 9.8 reflects the vulnerability’s high impact on confidentiality, integrity, and availability, and the fact that it can be exploited remotely without authentication or user interaction.

04

What to do about it

official fix available
recommended steps
  1. 01Verify the current kernel version on your system.
  2. 02Install the latest kernel update from your distribution’s official repositories, which includes the fix for the double‑free bug.

NVD description indicates the issue has been resolved in kernel updates.

05

Timeline

  1. Dec 30, 2025 · Dec 30, 2025
    Published
    Disclosed and added to the National Vulnerability Database.
  2. Aug 4, 2026 · 1d ago
    Advisory updated
    The NVD record was last revised.
  3. Aug 4, 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 →