Linux: Use After Free
CVE-2026-68104 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 4d7c10b0bf09d90c81818752decbdb1966b62702, 493adf29d66f23888f0e29888b6bc9512acd0825, 2e406b86144c1f732eb344f1f1e09043856cfc33 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.13% 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 4d7c10b0bf09d90c81818752decbdb1966b62702 or 493adf29d66f23888f0e29888b6bc9512acd0825 or 2e406b86144c1f732eb344f1f1e09043856cfc33 or bdfc7f1e0900ef1361b828c4f69b72701f8a0a86, whichever matches your release line, or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Linux | Linux | 25030321ba2860c56651429a4f28d94a6483d952 up to, but not including, 4d7c10b0bf09d90c81818752decbdb1966b62702; 25030321ba2860c56651429a4f28d94a6483d952 up to, but not including, 493adf29d66f23888f0e29888b6bc9512acd0825; 25030321ba2860c56651429a4f28d94a6483d952 up to, but not including, 2e406b86144c1f732eb344f1f1e09043856cfc33; 25030321ba2860c56651429a4f28d94a6483d952 up to, but not including, bdfc7f1e0900ef1361b828c4f69b72701f8a0a86; 25030321ba2860c56651429a4f28d94a6483d952 up to, but not including, 5c0a82283271759fff445ac27182072f200a888c; 25030321ba2860c56651429a4f28d94a6483d952 up to, but not including, 08fee493e0261f9e4120a5c8e7e42e8a723574e8; 25030321ba2860c56651429a4f28d94a6483d952 up to, but not including, 930a5dc3df4aa5e10393134bd5313d616dbebaf6; 25030321ba2860c56651429a4f28d94a6483d952 up to, but not including, 28c9b3c5dc35cc790d11e26ca3fc6e068be63998; and 1 more ranges | 4d7c10b0bf09d90c81818752decbdb1966b62702, 493adf29d66f23888f0e29888b6bc9512acd0825, 2e406b86144c1f732eb344f1f1e09043856cfc33, bdfc7f1e0900ef1361b828c4f69b72701f8a0a86, 5c0a82283271759fff445ac27182072f200a888c, 08fee493e0261f9e4120a5c8e7e42e8a723574e8 |
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 CNA.
Official description
In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: invoke pm_genpd_remove() before freeing genpd Call pm_genpd_remove() to unregister from global list prior to releasing acp_genpd memory, and clear the pointer after free. (cherry picked from commit cd8650d7a91ee8b768e202354672553faa5cc1f2)
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
Other references
- git.kernel.org/stable/c/08fee493e0261f9e4120a5c8e7e42e8a723574e8
- git.kernel.org/stable/c/28c9b3c5dc35cc790d11e26ca3fc6e068be63998
- git.kernel.org/stable/c/2e406b86144c1f732eb344f1f1e09043856cfc33
- git.kernel.org/stable/c/493adf29d66f23888f0e29888b6bc9512acd0825
- git.kernel.org/stable/c/4d7c10b0bf09d90c81818752decbdb1966b62702
- git.kernel.org/stable/c/5c0a82283271759fff445ac27182072f200a888c
- git.kernel.org/stable/c/930a5dc3df4aa5e10393134bd5313d616dbebaf6
- git.kernel.org/stable/c/bdfc7f1e0900ef1361b828c4f69b72701f8a0a86
Recent Use After Free vulnerabilities
- 7.8 High severity
- 9.8 Critical severity
- 7.5 High severity
- 8.8 High severity
- 7.8 High severity
- 7.8 High severity
Spotted an error? Tell us.