CVE-2026-43264: Linux kernel · fbdev: of: display_timing: fix refcount leak in of_get_display_timings()
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in eacf9840ae1285a1ef47eb0ce16d786e542bd4d7 : update Linux kernel when convenient.
Data as of 6 Nov 2026, 15:49 UTC
Rated by Threat Radar · No CVSS score from NVD or the CNA
Thin evidence
One scorer or none- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers cannot reliably automate steps 1–4 of the kill chain
- Technical impact
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2026-11-06.
- Patch
- Available – fixed in eacf9840ae1285a1ef47eb0ce16d786e542bd4d7, d6f34bbff07476c6abb8672c89d217824871c5ed, c5734f9030a8b1e13868d1641b5163d8e659306e +5
Exploitation evidence
Disclosed: evidence found.
CVE published 6 May 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 6 Nov 2026.
What to do
Upgrade to a fixed release listed under Affected software.
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
|
| LinuxLinux | Affected
| Fixed in
|
Description
In the Linux kernel, the following vulnerability has been resolved: fbdev: of: display_timing: fix refcount leak in of_get_display_timings() of_parse_phandle() returns a device_node with refcount incremented, which is stored in 'entry' and then copied to 'native_mode'. When the error paths at lines 184 or 192 jump to 'entryfail', native_mode's refcount is not decremented, causing a refcount leak. Fix this by changing the goto target from 'entryfail' to 'timingfail', which properly calls of_node_put(native_mode) before cleanup.
References
- git.kernel.org/stable/c/20881ad42e651c69d89eb38a2042838187900fd6 (opens in a new tab)
- git.kernel.org/stable/c/b5bdcc5afbff845834d04d651773cb6b47db5dd3 (opens in a new tab)
- git.kernel.org/stable/c/2b22e4fe1273c24f405ed7903349c4bbd82b6368 (opens in a new tab)
- git.kernel.org/stable/c/3ed019654234edb8625c05d05e15d40f74e64f70 (opens in a new tab)
- git.kernel.org/stable/c/d6f34bbff07476c6abb8672c89d217824871c5ed (opens in a new tab)
- git.kernel.org/stable/c/69290f2d3999c5fa1a7f5d5593cfc5461fa3ee64 (opens in a new tab)
- git.kernel.org/stable/c/c5734f9030a8b1e13868d1641b5163d8e659306e (opens in a new tab)
- git.kernel.org/stable/c/eacf9840ae1285a1ef47eb0ce16d786e542bd4d7 (opens in a new tab)