CyberSecBulletin
CVE-2026-53119NVD status: Analyzed

Linux: Use After Free

CVE-2026-53119 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 13d201bd840d2e2a645ef899f81342cd27ced346, 2c5507010fc3b8e2bd596c63c88f6ad39a69b1c4, 4dc755d86deed88789540d960e421124bad4c568 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.18% 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 13d201bd840d2e2a645ef899f81342cd27ced346 or 2c5507010fc3b8e2bd596c63c88f6ad39a69b1c4 or 4dc755d86deed88789540d960e421124bad4c568 or 8a700b1fc94df4d847a04f14ebc7f8532592b367, whichever matches your release line, or a later version.
  2. Update Linux Kernel to 6.12.91 or 6.18.33 or 7.0.10, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinux12046f8c77e0ed6d41beabde0edbb729499c970b up to, but not including, 13d201bd840d2e2a645ef899f81342cd27ced346; 12046f8c77e0ed6d41beabde0edbb729499c970b up to, but not including, 2c5507010fc3b8e2bd596c63c88f6ad39a69b1c4; 12046f8c77e0ed6d41beabde0edbb729499c970b up to, but not including, 4dc755d86deed88789540d960e421124bad4c568; 12046f8c77e0ed6d41beabde0edbb729499c970b up to, but not including, 8a700b1fc94df4d847a04f14ebc7f8532592b367; 6.1113d201bd840d2e2a645ef899f81342cd27ced346, 2c5507010fc3b8e2bd596c63c88f6ad39a69b1c4, 4dc755d86deed88789540d960e421124bad4c568, 8a700b1fc94df4d847a04f14ebc7f8532592b367
LinuxLinux Kernel6.11 up to, but not including, 6.12.91; 6.13 up to, but not including, 6.18.33; 6.19 up to, but not including, 7.0.106.12.91, 6.18.33, 7.0.10

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.

Official description

In the Linux kernel, the following vulnerability has been resolved: platform/wmi: use generic driver_override infrastructure When a driver is probed through __driver_attach(), the bus' match() callback is called without the device lock held, thus accessing the driver_override field without a lock, which can cause a UAF. Fix this by using the driver-core driver_override infrastructure taking care of proper locking internally. Note that calling match() from __driver_attach() without the device lock held is intentional. [1]

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. Record last changed materially (score, affected products, status or references).

References

Recent Use After Free vulnerabilities

Spotted an error? Tell us.