Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-46215: drm: Set old handle to NULL before prime swap in change_handle

Noroxi assessment

Priority: Monitor (action score 31/100)

  • Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.22% (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 5e28b7b94408897e41c63477aabc9e1db439bc8c, 61bd96d3e5472c253f9c1ab77608f0c8aaa9d025, 672464dd53231509c9c771110798c56d4660e19e.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 5e28b7b94408897e41c63477aabc9e1db439bc8c, 61bd96d3e5472c253f9c1ab77608f0c8aaa9d025, 672464dd53231509c9c771110798c56d4660e19e 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: Set old handle to NULL before prime swap in change_handle There was a potential race condition in change_handle. The ioctl briefly had a single object with two idr entries; a concurrent gem_close could delete the object and remove one of the handles while leaving the other one dangling, which could subsequently be dereferenced for a use-after-free. To fix this, do the same dance that gem_close itself does. (f6cd7daecff5 drm: Release driver references to handle before making it available again) First idr_replace the old handle to NULL. Later, if the prime operations are successful, actually close it. create_tail required a similar dance to avoid a similar problem. (bd46cece51a3 drm/gem: Fix race in drm_gem_handle_create_tail()) It idr_allocs the new handle with NULL, then swaps in the correct object later to avoid races. We don't need to do that here, since the only operations that could race are drm_prime, and change_handle holds the prime lock for the entire duration. v2: cleanups of error paths

HighCVSS 7.8 · v3.1—Proof of concept Fix available
Published
May 28, 2026
Updated
Aug 5, 2026
EPSS
0.2% · 13th percentile

Report tools

JSON

Action score

31

Monitor

Low priority for now.

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

CISA SSVC decision

Exploitation
proof of concept
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

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
  • Proof of concept exists, no weaponized module
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-46215

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

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.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel6.18 and later · before 6.18.32
  • linux linux kernel6.19 and later · before 7.0.9
  • linux linux kernel7.1

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

    • 6.18affected
    • 53096728b8910c6916ecc6c46a5abc5c678b58d9 and later · before 672464dd53231509c9c771110798c56d4660e19eaffected · git
    • 53096728b8910c6916ecc6c46a5abc5c678b58d9 and later · before 61bd96d3e5472c253f9c1ab77608f0c8aaa9d025affected · git
    • 53096728b8910c6916ecc6c46a5abc5c678b58d9 and later · before 5e28b7b94408897e41c63477aabc9e1db439bc8caffected · git
    • before 6.18not affected · semver
    • 6.18.32 and later · up to and including 6.18.*not affected · semver
    • 7.0.9 and later · up to and including 7.0.*not affected · semver
    • 7.1 and laternot affected · original_commit_for_fix

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:10kernelbefore 6.12.0-211.37.1.el10_26.12.0-211.37.1.el10_2
AlmaLinux:10kernel-64kbefore 6.12.0-211.37.1.el10_26.12.0-211.37.1.el10_2
AlmaLinux:10kernel-64k-corebefore 6.12.0-211.37.1.el10_26.12.0-211.37.1.el10_2
AlmaLinux:10kernel-64k-debugbefore 6.12.0-211.37.1.el10_26.12.0-211.37.1.el10_2
AlmaLinux:10kernel-64k-debug-corebefore 6.12.0-211.37.1.el10_26.12.0-211.37.1.el10_2
AlmaLinux:10kernel-64k-debug-develbefore 6.12.0-211.37.1.el10_26.12.0-211.37.1.el10_2
AlmaLinux:10kernel-64k-debug-devel-matchedbefore 6.12.0-211.37.1.el10_26.12.0-211.37.1.el10_2
AlmaLinux:10kernel-64k-debug-modulesbefore 6.12.0-211.37.1.el10_26.12.0-211.37.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-corebefore 6.12.0-211.37.1.el10_26.12.0-211.37.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-extrabefore 6.12.0-211.37.1.el10_26.12.0-211.37.1.el10_2
AlmaLinux:10kernel-64k-develbefore 6.12.0-211.37.1.el10_26.12.0-211.37.1.el10_2
AlmaLinux:10kernel-64k-devel-matchedbefore 6.12.0-211.37.1.el10_26.12.0-211.37.1.el10_2
AlmaLinux:10kernel-64k-modulesbefore 6.12.0-211.37.1.el10_26.12.0-211.37.1.el10_2
AlmaLinux:10kernel-64k-modules-corebefore 6.12.0-211.37.1.el10_26.12.0-211.37.1.el10_2
AlmaLinux:10kernel-64k-modules-extrabefore 6.12.0-211.37.1.el10_26.12.0-211.37.1.el10_2
AlmaLinux:10kernel-abi-stablelistsbefore 6.12.0-211.37.1.el10_26.12.0-211.37.1.el10_2
AlmaLinux:10kernel-corebefore 6.12.0-211.37.1.el10_26.12.0-211.37.1.el10_2
AlmaLinux:10kernel-cross-headersbefore 6.12.0-211.37.1.el10_26.12.0-211.37.1.el10_2
AlmaLinux:10kernel-debugbefore 6.12.0-211.37.1.el10_26.12.0-211.37.1.el10_2
AlmaLinux:10kernel-debug-corebefore 6.12.0-211.37.1.el10_26.12.0-211.37.1.el10_2
AlmaLinux:10kernel-debug-develbefore 6.12.0-211.37.1.el10_26.12.0-211.37.1.el10_2
AlmaLinux:10kernel-debug-devel-matchedbefore 6.12.0-211.37.1.el10_26.12.0-211.37.1.el10_2
AlmaLinux:10kernel-debug-modulesbefore 6.12.0-211.37.1.el10_26.12.0-211.37.1.el10_2
AlmaLinux:10kernel-debug-modules-corebefore 6.12.0-211.37.1.el10_26.12.0-211.37.1.el10_2

+96

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • 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

Published before and after this one in the same product

  • ← EarlierCVE-2026-46212May 28, 2026 · batman-adv: bla: prevent use-after-free when deleting claims
    35Monitor
  • ← EarlierCVE-2026-46213May 28, 2026 · HID: appletb-kbd: fix UAF in inactivity-timer cleanup path
    31Monitor
  • Later →CVE-2026-46216May 28, 2026 · drm/xe/hdcp: Add NULL check for media_gt in intel_hdcp_gsc_check_status()
    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 / packageFixed versionSource
Linux Linux5e28b7b94408897e41c63477aabc9e1db439bc8cVendor (CNA)
Linux Linux61bd96d3e5472c253f9c1ab77608f0c8aaa9d025Vendor (CNA)
Linux Linux672464dd53231509c9c771110798c56d4660e19eVendor (CNA)
almalinux:kernel6.12.0-211.37.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k6.12.0-211.37.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-core6.12.0-211.37.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug6.12.0-211.37.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-core6.12.0-211.37.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-devel6.12.0-211.37.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched6.12.0-211.37.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules6.12.0-211.37.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules-core6.12.0-211.37.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra6.12.0-211.37.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-devel6.12.0-211.37.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-devel-matched6.12.0-211.37.1.el10_2 · AlmaLinux:10Package registry (OSV)
debian:linux7.0.9-1 · Debian:14Package registry (OSV)
red hat:kernel-64k-debug-debuginfo0:6.12.0-211.37.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-debug-devel0:6.12.0-211.37.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-debug-devel-matched0:6.12.0-211.37.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-debuginfo0:6.12.0-211.37.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-devel0:6.12.0-211.37.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-devel-matched0:6.12.0-211.37.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debug-debuginfo0:6.12.0-211.37.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debug-devel0:6.12.0-211.37.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debug-devel-matched0:6.12.0-211.37.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debuginfo0:6.12.0-211.37.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debuginfo-common-aarch640:6.12.0-211.37.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debuginfo-common-ppc64le0:6.12.0-211.37.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
rocky linux:kernel0:6.12.0-211.37.1.el10_2 · Rocky Linux:10Package registry (OSV)

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

  • Proof-of-concept repository on GitHub ×3

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Proof-of-concept repository on GitHubstars:112026-06-18
Proof-of-concept repository on GitHubstars:32026-07-11
Proof-of-concept repository on GitHubstars:52026-07-19

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.

  1. Published
  2. First PoC+21 d
  3. TodayNov 4, 2026+160 d

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.

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.

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.

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

Vulnerable

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

Fixed

c
lock(&dev->lock);free(dev->buf);dev->buf = NULL;unlock(&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

  1. Fix✗ → ✓

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

References

All records