NVD / CVE Program· CNA Linux

CVE-2022-50417: drm/panfrost: Fix GEM handle creation ref-counting

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.16% (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 0b70f6ea4d4f2b4d4b291d86ab76b4d07394932c, 3f9feffa8a5ab08b4e298a27b1aa7204a7d42ca2, 4217c6ac817451d5116687f3cc6286220dc43d49.

Low priority for now. Upgrade to Linux Linux 0b70f6ea4d4f2b4d4b291d86ab76b4d07394932c, 3f9feffa8a5ab08b4e298a27b1aa7204a7d42ca2, 4217c6ac817451d5116687f3cc6286220dc43d49 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/panfrost: Fix GEM handle creation ref-counting panfrost_gem_create_with_handle() previously returned a BO but with the only reference being from the handle, which user space could in theory guess and release, causing a use-after-free. Additionally if the call to panfrost_gem_mapping_get() in panfrost_ioctl_create_bo() failed then a(nother) reference on the BO was dropped. The _create_with_handle() is a problematic pattern, so ditch it and instead create the handle in panfrost_ioctl_create_bo(). If the call to panfrost_gem_mapping_get() fails then this means that user space has indeed gone behind our back and freed the handle. In which case just return an error code.

HighCVSS 7.8 · v3.1—No exploit Fix available

Memory safety

BDU:2026-03271

Published: Sep 18, 2025
Updated: Aug 5, 2026
EPSS: 0.1% · 5th 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%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: 7.8
CNA · Linux: 7.8; agree

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 kernel5.2 and later · before 5.10.163
linux linux kernel5.11 and later · before 5.15.87
linux linux kernel5.16 and later · before 6.0.19
linux linux kernel6.1 and later · before 6.1.5
linux linux kernel6.2

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
- 5.2affected
- f3ba91228e8e917e5bd6c4b72bfe846933d17370 and later · before 0b70f6ea4d4f2b4d4b291d86ab76b4d07394932caffected · git
- f3ba91228e8e917e5bd6c4b72bfe846933d17370 and later · before 4f1105ee72d8c7c35d90e3491b31b2d9d6b7e33aaffected · git
- f3ba91228e8e917e5bd6c4b72bfe846933d17370 and later · before 3f9feffa8a5ab08b4e298a27b1aa7204a7d42ca2affected · git
- f3ba91228e8e917e5bd6c4b72bfe846933d17370 and later · before ba3d2c2380e7129b525a787489c0b7e819a3b898affected · git
- f3ba91228e8e917e5bd6c4b72bfe846933d17370 and later · before 4217c6ac817451d5116687f3cc6286220dc43d49affected · git
- before 5.2not affected · semver
- 5.10.163 and later · up to and including 5.10.*not affected · semver
- 5.15.87 and later · up to and including 5.15.*not affected · semver
- 6.0.19 and later · up to and including 6.0.*not 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.7-1	6.1.7-1

Same product

linux: all records

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-2022-50415Sep 18, 2025 · parisc: led: Fix potential null-ptr-deref in start_task()
22Monitor
← EarlierCVE-2022-50416Sep 18, 2025 · irqchip/wpcm450: Fix memory leak in wpcm450_aic_of_init()
22Monitor
Later →CVE-2022-50418Sep 18, 2025 · wifi: ath11k: mhi: fix potential memory leak in ath11k_mhi_register()
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	0b70f6ea4d4f2b4d4b291d86ab76b4d07394932c	Vendor (CNA)
Linux Linux	3f9feffa8a5ab08b4e298a27b1aa7204a7d42ca2	Vendor (CNA)
Linux Linux	4217c6ac817451d5116687f3cc6286220dc43d49	Vendor (CNA)
Linux Linux	4f1105ee72d8c7c35d90e3491b31b2d9d6b7e33a	Vendor (CNA)
Linux Linux	ba3d2c2380e7129b525a787489c0b7e819a3b898	Vendor (CNA)
debian:linux	6.1.7-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 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).

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-primary

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:10 PM UTC

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

References

git.kernel.org/stable/c/0b70f6ea4d4f2b4d4b291d86ab76b4d07394932c

Show all references (4 more)

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

All records