Linux: Use After Free
CVE-2025-22068 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 7e3497d7dacb5aee69dd9be842b778083cae0e75, 5491400589e7572c2d2627ed6384302f7672aa1d, 9158359015f0eda00e521e35b7bc7ebce176aebf 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.21% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Linux to 7e3497d7dacb5aee69dd9be842b778083cae0e75 or 5491400589e7572c2d2627ed6384302f7672aa1d or 9158359015f0eda00e521e35b7bc7ebce176aebf or 8741d0737921ec1c03cf59aebf4d01400c2b461a, whichever matches your release line, or a later version.
- Update Linux Kernel to 6.12.23 or 6.13.11 or 6.14.2, whichever matches your release line, or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Linux | Linux | 216c8f5ef0f209a3797292c487bdaa6991ab4b92 up to, but not including, 7e3497d7dacb5aee69dd9be842b778083cae0e75; 216c8f5ef0f209a3797292c487bdaa6991ab4b92 up to, but not including, 5491400589e7572c2d2627ed6384302f7672aa1d; 216c8f5ef0f209a3797292c487bdaa6991ab4b92 up to, but not including, 9158359015f0eda00e521e35b7bc7ebce176aebf; 216c8f5ef0f209a3797292c487bdaa6991ab4b92 up to, but not including, 8741d0737921ec1c03cf59aebf4d01400c2b461a; 6.7 | 7e3497d7dacb5aee69dd9be842b778083cae0e75, 5491400589e7572c2d2627ed6384302f7672aa1d, 9158359015f0eda00e521e35b7bc7ebce176aebf, 8741d0737921ec1c03cf59aebf4d01400c2b461a |
| Linux | Linux Kernel | 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.2 | 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
- 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 NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 7.8 | High | NVD |
| CVSS 3.1 | 7.8 | High | CISA (ADP) |
Official description
In the Linux kernel, the following vulnerability has been resolved: ublk: make sure ubq->canceling is set when queue is frozen Now ublk driver depends on `ubq->canceling` for deciding if the request can be dispatched via uring_cmd & io_uring_cmd_complete_in_task(). Once ubq->canceling is set, the uring_cmd can be done via ublk_cancel_cmd() and io_uring_cmd_done(). So set ubq->canceling when queue is frozen, this way makes sure that the flag can be observed from ublk_queue_rq() reliably, and avoids use-after-free on uring_cmd.
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.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
Recent Use After Free vulnerabilities
- 8.8 High severity
- 7.8 High severity
- 7.8 High severity
- 9.8 Critical severity
- 7.8 High severity
- 7.8 High severity
Spotted an error? Tell us.