CyberSecBulletin
CVE-2025-22088NVD status: Modified

Linux: Use After Free

CVE-2025-22088 is a critical-severity use after free vulnerability in Linux, with a CVSS 3.1 base score of 9.8 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists versions bc1db4d8f1b0dc480d7d745a60a8cc94ce2badd4, 667a628ab67d359166799fad89b3c6909599558a, a114d25d584c14019d31dbf2163780c47415a187 as the first without the flaw, so updating Linux to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.55% chance of exploitation within 30 days, which is low compared with other CVEs.

Patch this week

Critical severity: a successful attack would have severe impact.

What to do

  1. Update Linux to bc1db4d8f1b0dc480d7d745a60a8cc94ce2badd4 or 667a628ab67d359166799fad89b3c6909599558a or a114d25d584c14019d31dbf2163780c47415a187 or 78411a133312ce7d8a3239c76a8fd85bca1cc10f, whichever matches your release line, or a later version.
  2. Update Linux Kernel to 6.1.134 or 6.6.87 or 6.12.23 or 6.13.11, whichever matches your release line, or a later version.
  3. Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinux920d93eac8b97778fef48f34f10e58ddf870fc2a up to, but not including, bc1db4d8f1b0dc480d7d745a60a8cc94ce2badd4; 920d93eac8b97778fef48f34f10e58ddf870fc2a up to, but not including, 667a628ab67d359166799fad89b3c6909599558a; 920d93eac8b97778fef48f34f10e58ddf870fc2a up to, but not including, a114d25d584c14019d31dbf2163780c47415a187; 920d93eac8b97778fef48f34f10e58ddf870fc2a up to, but not including, 78411a133312ce7d8a3239c76a8fd85bca1cc10f; 920d93eac8b97778fef48f34f10e58ddf870fc2a up to, but not including, 7aa6bb5276d9fec98deb05615a086eeb893854ad; 920d93eac8b97778fef48f34f10e58ddf870fc2a up to, but not including, 83437689249e6a17b25e27712fbee292e42e7855; 6.0bc1db4d8f1b0dc480d7d745a60a8cc94ce2badd4, 667a628ab67d359166799fad89b3c6909599558a, a114d25d584c14019d31dbf2163780c47415a187, 78411a133312ce7d8a3239c76a8fd85bca1cc10f, 7aa6bb5276d9fec98deb05615a086eeb893854ad, 83437689249e6a17b25e27712fbee292e42e7855
LinuxLinux Kernel6.0 up to, but not including, 6.1.134; 6.2 up to, but not including, 6.6.87; 6.7 up to, but not including, 6.12.23; 6.13 up to, but not including, 6.13.11; 6.14 up to, but not including, 6.14.26.1.134, 6.6.87, 6.12.23, 6.13.11, 6.14.2

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
NoneNo account or login is needed.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Scored by CNA.

Scoring systemScoreSeverityScored by
CVSS 3.19.8CriticalCNA
CVSS 3.17.8HighCISA (ADP)

Official description

In the Linux kernel, the following vulnerability has been resolved: RDMA/erdma: Prevent use-after-free in erdma_accept_newconn() After the erdma_cep_put(new_cep) being called, new_cep will be freed, and the following dereference will cause a UAF problem. Fix this issue.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Use After Free

The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory belongs to the code that operates on the new pointer.

How developers prevent this class of flaw

  • Choose a language that provides automatic memory management.
  • When freeing pointers, be sure to set them to NULL once they are freed. However, the utilization of multiple or complex data structures may lower the usefulness of this strategy.

More Use After Free vulnerabilities (CWE-416)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Recent Use After Free vulnerabilities

Spotted an error? Tell us.