NVD / CVE Program· CNA Linux

CVE-2022-50454: drm/nouveau: fix a use-after-free in nouveau_gem_prime_import_sg_table()

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 3aeda2fe6517cc52663d4ce3588dd43f0d4124a7, 540dfd188ea2940582841c1c220bd035a7db0e51, 56ee9577915dc06f55309901012a9ef68dbdb5a8.

Low priority for now. Upgrade to Linux Linux 3aeda2fe6517cc52663d4ce3588dd43f0d4124a7, 540dfd188ea2940582841c1c220bd035a7db0e51, 56ee9577915dc06f55309901012a9ef68dbdb5a8 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/nouveau: fix a use-after-free in nouveau_gem_prime_import_sg_table() nouveau_bo_init() is backed by ttm_bo_init() and ferries its return code back to the caller. On failures, ttm will call nouveau_bo_del_ttm() and free the memory.Thus, when nouveau_bo_init() returns an error, the gem object has already been released. Then the call to nouveau_bo_ref() will use the freed "nvbo->bo" and lead to a use-after-free bug. We should delete the call to nouveau_bo_ref() to avoid the use-after-free.

HighCVSS 7.8 · v3.1—No exploit Fix available

Memory safety

BDU:2026-01631

Published: Oct 1, 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%

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.4 and later · before 5.4.220
linux linux kernel5.5 and later · before 5.10.150
linux linux kernel5.11 and later · before 5.15.75
linux linux kernel5.16 and later · before 5.19.17
linux linux kernel6.0 and later · before 6.0.3

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.4affected
- 019cbd4a4feb3aa3a917d78e7110e3011bbff6d5 and later · before 56ee9577915dc06f55309901012a9ef68dbdb5a8affected · git
- 019cbd4a4feb3aa3a917d78e7110e3011bbff6d5 and later · before 5d6093c49c098d86c7b136aba9922df44aeb6944affected · git
- 019cbd4a4feb3aa3a917d78e7110e3011bbff6d5 and later · before 861f085f81fd569b02cc2c11165a9e6cca144424affected · git
- 019cbd4a4feb3aa3a917d78e7110e3011bbff6d5 and later · before 3aeda2fe6517cc52663d4ce3588dd43f0d4124a7affected · git
- 019cbd4a4feb3aa3a917d78e7110e3011bbff6d5 and later · before 7d80473e9f12548ac05b36af4fb9ce80f2f73509affected · git
- 019cbd4a4feb3aa3a917d78e7110e3011bbff6d5 and later · before 540dfd188ea2940582841c1c220bd035a7db0e51affected · git
- before 5.4not affected · semver
- 5.4.220 and later · up to and including 5.4.*not affected · semver
- 5.10.150 and later · up to and including 5.10.*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.0.3-1	6.0.3-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-50452Oct 1, 2025 · net: sched: cake: fix null pointer access issue when cake_init() fails
22Monitor
← EarlierCVE-2022-50453Oct 1, 2025 · gpiolib: cdev: fix NULL-pointer dereferences
22Monitor
Later →CVE-2022-50456Oct 1, 2025 · btrfs: fix resolving backrefs for inline extent followed by prealloc
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	3aeda2fe6517cc52663d4ce3588dd43f0d4124a7	Vendor (CNA)
Linux Linux	540dfd188ea2940582841c1c220bd035a7db0e51	Vendor (CNA)
Linux Linux	56ee9577915dc06f55309901012a9ef68dbdb5a8	Vendor (CNA)
Linux Linux	5d6093c49c098d86c7b136aba9922df44aeb6944	Vendor (CNA)
Linux Linux	7d80473e9f12548ac05b36af4fb9ce80f2f73509	Vendor (CNA)
Linux Linux	861f085f81fd569b02cc2c11165a9e6cca144424	Vendor (CNA)
debian:linux	6.0.3-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/3aeda2fe6517cc52663d4ce3588dd43f0d4124a7

Show all references (5 more)

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

All records