CyberSecBulletin
CVE-2025-21786NVD status: Analyzed

Linux: Use After Free

CVE-2025-21786 is a high-severity use after free vulnerability in Linux, with a CVSS 3.1 base score of 7.8 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. The record lists versions e7c16028a424dd35be1064a68fa318be4359310f, 835b69c868f53f959d4986bbecd561ba6f38e492, e76946110137703c16423baf6ee177b751a34b7e 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.23% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update Linux to e7c16028a424dd35be1064a68fa318be4359310f or 835b69c868f53f959d4986bbecd561ba6f38e492 or e76946110137703c16423baf6ee177b751a34b7e, whichever matches your release line, or a later version.
  2. Update Linux Kernel to 6.12.16 or 6.13.4, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinux68f83057b913467a999e1bf9e0da6a119668f769 up to, but not including, e7c16028a424dd35be1064a68fa318be4359310f; 68f83057b913467a999e1bf9e0da6a119668f769 up to, but not including, 835b69c868f53f959d4986bbecd561ba6f38e492; 68f83057b913467a999e1bf9e0da6a119668f769 up to, but not including, e76946110137703c16423baf6ee177b751a34b7e; 6.11e7c16028a424dd35be1064a68fa318be4359310f, 835b69c868f53f959d4986bbecd561ba6f38e492, e76946110137703c16423baf6ee177b751a34b7e
LinuxLinux Kernelbefore 6.12.16; 6.13 up to, but not including, 6.13.46.12.16, 6.13.4

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
LocalThe attacker needs local access or must trick a user into running something.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
LowA basic user account is enough.
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:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by CISA (ADP).

Official description

In the Linux kernel, the following vulnerability has been resolved: workqueue: Put the pwq after detaching the rescuer from the pool The commit 68f83057b913("workqueue: Reap workers via kthread_stop() and remove detach_completion") adds code to reap the normal workers but mistakenly does not handle the rescuer and also removes the code waiting for the rescuer in put_unbound_pool(), which caused a use-after-free bug reported by Cheung Wall. To avoid the use-after-free bug, the pool’s reference must be held until the detachment is complete. Therefore, move the code that puts the pwq after detaching the rescuer from the pool.

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.