Skip to main content
VulnerabilityPublished Updated

CVE-2025-38443: Linux kernel · nbd: fix uaf in nbd_genl_connect() error path

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in d46186eb7bbd9a11c145120f2d77effa8d4d44c2 : patch Linux kernel soon.

Data as of 5 Nov 2026, 21:20 UTC

Severity
High

Rated High by Threat Radar's AI analysis · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-05.

Patch
Available – fixed in d46186eb7bbd9a11c145120f2d77effa8d4d44c2, cb121c47f364b51776c4db904a6a5a90ab0a7ec5, aa9552438ebf015fc5f9f890dbfe39f0c53cf37e +3

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Jul 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 6497ef8df568afbf5f3e38825a4590ff41611a54, < d46186eb7bbd9a11c145120f2d77effa8d4d44c2
Fixed in
  • d46186eb7bbd9a11c145120f2d77effa8d4d44c2
LinuxLinuxAffected
  • ≥ 6497ef8df568afbf5f3e38825a4590ff41611a54, < cb121c47f364b51776c4db904a6a5a90ab0a7ec5
Fixed in
  • cb121c47f364b51776c4db904a6a5a90ab0a7ec5
LinuxLinuxAffected
  • ≥ 6497ef8df568afbf5f3e38825a4590ff41611a54, < aa9552438ebf015fc5f9f890dbfe39f0c53cf37e
Fixed in
  • aa9552438ebf015fc5f9f890dbfe39f0c53cf37e
LinuxLinuxAffected
  • ≥ 6497ef8df568afbf5f3e38825a4590ff41611a54, < 8586552df591e0a367eff44af0c586213eeecc3f
Fixed in
  • 8586552df591e0a367eff44af0c586213eeecc3f
LinuxLinuxAffected
  • ≥ 6497ef8df568afbf5f3e38825a4590ff41611a54, < 91fa560c73a8126868848ed6cd70607cbf8d87e2
Fixed in
  • 91fa560c73a8126868848ed6cd70607cbf8d87e2
LinuxLinuxAffected
  • ≥ 6497ef8df568afbf5f3e38825a4590ff41611a54, < 002aca89753f666d878ca0eb8584c372684ac4ba
Fixed in
  • 002aca89753f666d878ca0eb8584c372684ac4ba

AI-suggested

A fix is available and has been applied in the Linux kernel source code as indicated by the fixed commit hashes. Users and administrators should update to a Linux kernel version that includes these fixes. Since this is not a cloud service, manual patching or kernel upgrade is required to remediate this vulnerability.

Description

A use-after-free vulnerability exists in the Linux kernel's nbd driver in the nbd_genl_connect() error path. The issue occurs because the device is not properly stopped on certain error paths after nbd_start_device() has been called, leading to use of freed memory by recv_work. This flaw has been fixed by moving nbd_start_device() after backend file creation.

References

Community reviews

Loading reviews…