NVD / CVE Program· CNA Linux

CVE-2026-45956: drm/exynos: vidi: use priv->vidi_dev for ctx lookup in vidi_connection_ioctl()

Noroxi assessment

Priority: Monitor (action score 31/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.17% (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 21ca24ba51a2c28bcc4df9d7e5a40b0eb66ab76d, 2987642c5213508c6c9e718324c0d5289a92c474, 65d1213baffa363f2eb1117b1dc7acc573b890f8.
Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 21ca24ba51a2c28bcc4df9d7e5a40b0eb66ab76d, 2987642c5213508c6c9e718324c0d5289a92c474, 65d1213baffa363f2eb1117b1dc7acc573b890f8 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: drm/exynos: vidi: use priv->vidi_dev for ctx lookup in vidi_connection_ioctl() vidi_connection_ioctl() retrieves the driver_data from drm_dev->dev to obtain a struct vidi_context pointer. However, drm_dev->dev is the exynos-drm master device, and the driver_data contained therein is not the vidi component device, but a completely different device. This can lead to various bugs, ranging from null pointer dereferences and garbage value accesses to, in unlucky cases, out-of-bounds errors, use-after-free errors, and more. To resolve this issue, we need to store/delete the vidi device pointer in exynos_drm_private->vidi_dev during bind/unbind, and then read this exynos_drm_private->vidi_dev within ioctl() to obtain the correct struct vidi_context pointer.

HighCVSS 7.8 · v3.1—No exploit Fix available

Memory safety

Published: May 27, 2026
Updated: Oct 21, 2026
EPSS: 0.1% · 6th percentile
CWE: CWE-416

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 31 / 40 · 7.8 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.1%

CNA vs NVD score

NVD: —
CNA · Linux: 7.8; NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

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

Is your version affected? Check it

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 help

Affected 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 kernel4.3 and later · before 5.10.253
linux linux kernel5.11 and later · before 5.15.203
linux linux kernel5.16 and later · before 6.1.167
linux linux kernel6.2 and later · before 6.6.130
linux linux kernel6.7 and later · before 6.18.14
linux linux kernel6.19 and later · before 6.19.4

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
- 4.3affected
- cf67cc9a29ac19c98bc4fa0e6d14b0c1f592d322 and later · before 2987642c5213508c6c9e718324c0d5289a92c474affected · git
- cf67cc9a29ac19c98bc4fa0e6d14b0c1f592d322 and later · before 65d1213baffa363f2eb1117b1dc7acc573b890f8affected · git
- cf67cc9a29ac19c98bc4fa0e6d14b0c1f592d322 and later · before 875fa28690e93ed5296c31d3344556c6bb867234affected · git
- cf67cc9a29ac19c98bc4fa0e6d14b0c1f592d322 and later · before 21ca24ba51a2c28bcc4df9d7e5a40b0eb66ab76daffected · git
- cf67cc9a29ac19c98bc4fa0e6d14b0c1f592d322 and later · before e1aed617eb80b49eac2f8c7bb7a0990f641dd59baffected · git
- cf67cc9a29ac19c98bc4fa0e6d14b0c1f592d322 and later · before b5fc86d753dd4c281a943b92f0eef02d31af03d7affected · git
- cf67cc9a29ac19c98bc4fa0e6d14b0c1f592d322 and later · before a540f767642f75240a6c35f6a65b69e44cfcea9daffected · git
- cf67cc9a29ac19c98bc4fa0e6d14b0c1f592d322 and later · before d3968a0d85b211e197f2f4f06268a7031079e0d0affected · git
- before 4.3not 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	from 0	—
Debian:14	linux	before 6.18.14-1	6.18.14-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

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 KEV
89Now
CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
85Now
CVE-2016-5195Race condition in mm/gup.c in the Linux kernel 2.x through 4.x before 4.8.3 allows local users to gain privileges by leveraging incorrect haKEV
83Now

Published before and after this one in the same product

← EarlierCVE-2026-45949May 27, 2026 · hwrng: core - use RCU and work_struct to fix race condition
18Monitor
← EarlierCVE-2026-45955May 27, 2026 · md/md-llbitmap: fix percpu_ref not resurrected on suspend timeout
28Monitor
Later →CVE-2026-45959May 27, 2026 · crypto: ccp - Fix a crash due to incorrect cleanup usage of kfree
31Monitor

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	21ca24ba51a2c28bcc4df9d7e5a40b0eb66ab76d	Vendor (CNA)
Linux Linux	2987642c5213508c6c9e718324c0d5289a92c474	Vendor (CNA)
Linux Linux	65d1213baffa363f2eb1117b1dc7acc573b890f8	Vendor (CNA)
Linux Linux	875fa28690e93ed5296c31d3344556c6bb867234	Vendor (CNA)
Linux Linux	a540f767642f75240a6c35f6a65b69e44cfcea9d	Vendor (CNA)
Linux Linux	b5fc86d753dd4c281a943b92f0eef02d31af03d7	Vendor (CNA)
Linux Linux	d3968a0d85b211e197f2f4f06268a7031079e0d0	Vendor (CNA)
Linux Linux	e1aed617eb80b49eac2f8c7bb7a0990f641dd59b	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.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

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 researchers

Finders, 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-0290 · Jun 2, 2026(Linux Kernel Güvenlik Bildirimi)

All national notices →

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: high · data can be read
Integrity: high · data or configuration can be modified
Availability: high · the service can be disrupted

Attack vector: Local
Attack complexity: Low
Privileges required: Low
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: High
Availability impact: High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-secondary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

The bug in code

The whole CWE-416 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1free(dev->buf);
2/* ... another thread is still running ... */
3process(dev->buf);

Fixed

1lock(&dev->lock);
2free(dev->buf);
3dev->buf = NULL;
4unlock(&dev->lock);

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✗ → ✓Sep 28, 2026, 10:11 PM UTC

For records you follow, these changes also arrive as notifications. →

References

git.kernel.org/stable/c/21ca24ba51a2c28bcc4df9d7e5a40b0eb66ab76d

Show all references (7 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records