CVE-2026-99753: Linux kernel · drm/loongson: Fix double free on BO initialization failure
Source GCVE Database
Not known to be exploited · fixed in f086dbdeb6e56510e158a853d752c6d8ed9e0674 : update Linux kernel when convenient.
Data as of 20 Nov 2026, 08:04 UTC
Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in f086dbdeb6e56510e158a853d752c6d8ed9e0674, dd76e36520a9553a4416412aa114217541218f97, c8da4789c0c916fed4d546a2b07423151e5f9d59 +1
Exploitation evidence
Disclosed: evidence found.
CVE published 20 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.
What to do
Upgrade Linux kernel to f086dbdeb6e56510e158a853d752c6d8ed9e0674, dd76e36520a9553a4416412aa114217541218f97, c8da4789c0c916fed4d546a2b07423151e5f9d59 or 6ad25544f1dd24ac512e4d03b5613f4d6d40576d.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
A fix has been implemented in the Linux kernel to correct the double free condition by properly managing buffer object cleanup ownership. Users should update to the fixed kernel version once available. No additional mitigation steps are indicated.
Description
A double free vulnerability was identified and fixed in the drm/loongson component of the Linux kernel. The flaw occurs when buffer object initialization fails, leading to the buffer being freed twice due to improper ownership handling during cleanup. This issue was resolved by adjusting the cleanup ownership logic to prevent double freeing on failure paths.
References
- nvd.nist.gov/vuln/detail/CVE-2026-99753 (opens in a new tab)
- git.kernel.org/stable/c/6ad25544f1dd24ac512e4d03b5613f4d6d40576d (opens in a new tab)
- git.kernel.org/stable/c/c8da4789c0c916fed4d546a2b07423151e5f9d59 (opens in a new tab)
- git.kernel.org/stable/c/dd76e36520a9553a4416412aa114217541218f97 (opens in a new tab)
- git.kernel.org/stable/c/f086dbdeb6e56510e158a853d752c6d8ed9e0674 (opens in a new tab)