CVE-2026-43264: fbdev: of: display_timing: fix refcount leak in of_get_display_timings()
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.11% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 20881ad42e651c69d89eb38a2042838187900fd6, 2b22e4fe1273c24f405ed7903349c4bbd82b6368, 3ed019654234edb8625c05d05e15d40f74e64f70.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 20881ad42e651c69d89eb38a2042838187900fd6, 2b22e4fe1273c24f405ed7903349c4bbd82b6368, 3ed019654234edb8625c05d05e15d40f74e64f70 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- May 6, 2026
- Updated
- Jun 17, 2026
- EPSS
- 0.1% · 1th percentile
- CWE
- —
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel3.9 and later · before 5.10.252
- linux linux kernel5.11 and later · before 5.15.202
- linux linux kernel5.16 and later · before 6.1.165
- linux linux kernel6.2 and later · before 6.6.128
- linux linux kernel6.7 and later · before 6.12.75
- linux linux kernel6.13 and later · before 6.18.16
- linux linux kernel6.19 and later · before 6.19.6
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 3.9affected
- cc3f414cf2e404130584b63d373161ba6fd24bc2 and later · before 20881ad42e651c69d89eb38a2042838187900fd6affected · git
- cc3f414cf2e404130584b63d373161ba6fd24bc2 and later · before b5bdcc5afbff845834d04d651773cb6b47db5dd3affected · git
- cc3f414cf2e404130584b63d373161ba6fd24bc2 and later · before 2b22e4fe1273c24f405ed7903349c4bbd82b6368affected · git
- cc3f414cf2e404130584b63d373161ba6fd24bc2 and later · before 3ed019654234edb8625c05d05e15d40f74e64f70affected · git
- cc3f414cf2e404130584b63d373161ba6fd24bc2 and later · before d6f34bbff07476c6abb8672c89d217824871c5edaffected · git
- cc3f414cf2e404130584b63d373161ba6fd24bc2 and later · before 69290f2d3999c5fa1a7f5d5593cfc5461fa3ee64affected · git
- cc3f414cf2e404130584b63d373161ba6fd24bc2 and later · before c5734f9030a8b1e13868d1641b5163d8e659306eaffected · git
- cc3f414cf2e404130584b63d373161ba6fd24bc2 and later · before eacf9840ae1285a1ef47eb0ce16d786e542bd4d7affected · git
- before 3.9not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.170-1 | 6.1.170-1 |
| Debian:13 | linux | before 6.12.85-1 | 6.12.85-1 |
| Debian:14 | linux | before 6.19.6-1 | 6.19.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2026-43261May 6, 2026 · arm64: Add support for TSV110 Spectre-BHB mitigation22Monitor
- ← EarlierCVE-2026-43262May 6, 2026 · gfs2: fiemap page fault fix22Monitor
- Later →CVE-2026-43265May 6, 2026 · KVM: x86: Ignore -EBUSY when checking nested events from vcpu_block()22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 20881ad42e651c69d89eb38a2042838187900fd6 | Vendor (CNA) |
| Linux Linux | 2b22e4fe1273c24f405ed7903349c4bbd82b6368 | Vendor (CNA) |
| Linux Linux | 3ed019654234edb8625c05d05e15d40f74e64f70 | Vendor (CNA) |
| Linux Linux | 69290f2d3999c5fa1a7f5d5593cfc5461fa3ee64 | Vendor (CNA) |
| Linux Linux | b5bdcc5afbff845834d04d651773cb6b47db5dd3 | Vendor (CNA) |
| Linux Linux | c5734f9030a8b1e13868d1641b5163d8e659306e | Vendor (CNA) |
| Linux Linux | d6f34bbff07476c6abb8672c89d217824871c5ed | Vendor (CNA) |
| Linux Linux | eacf9840ae1285a1ef47eb0ce16d786e542bd4d7 | Vendor (CNA) |
| debian:linux | 6.1.170-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0213 · May 12, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/2b22e4fe1273c24f405ed7903349c4bbd82b6368
- git.kernel.org/stable/c/3ed019654234edb8625c05d05e15d40f74e64f70
- git.kernel.org/stable/c/69290f2d3999c5fa1a7f5d5593cfc5461fa3ee64
- git.kernel.org/stable/c/b5bdcc5afbff845834d04d651773cb6b47db5dd3
- git.kernel.org/stable/c/c5734f9030a8b1e13868d1641b5163d8e659306e
- git.kernel.org/stable/c/d6f34bbff07476c6abb8672c89d217824871c5ed
- git.kernel.org/stable/c/eacf9840ae1285a1ef47eb0ce16d786e542bd4d7
Vendor advisories and official records. Exploit/PoC links are deliberately left out.