CVE-2022-50369: drm/vkms: Fix null-ptr-deref in vkms_release()
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.20% (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 0b8f390e2251191f1b179cc87f65d54c96565f0d, 1f9836f95271e7acf016667eee0aeae3386f9645, 2fe2a8f40c21161ffe7653cc234e7934db5b7cc5.
Low priority for now. Upgrade to Linux Linux 0b8f390e2251191f1b179cc87f65d54c96565f0d, 1f9836f95271e7acf016667eee0aeae3386f9645, 2fe2a8f40c21161ffe7653cc234e7934db5b7cc5 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/vkms: Fix null-ptr-deref in vkms_release() A null-ptr-deref is triggered when it tries to destroy the workqueue in vkms->output.composer_workq in vkms_release(). KASAN: null-ptr-deref in range [0x0000000000000118-0x000000000000011f] CPU: 5 PID: 17193 Comm: modprobe Not tainted 6.0.0-11331-gd465bff130bf #24 RIP: 0010:destroy_workqueue+0x2f/0x710 ... Call Trace: <TASK> ? vkms_config_debugfs_init+0x50/0x50 [vkms] __devm_drm_dev_alloc+0x15a/0x1c0 [drm] vkms_init+0x245/0x1000 [vkms] do_one_initcall+0xd0/0x4f0 do_init_module+0x1a4/0x680 load_module+0x6249/0x7110 __do_sys_finit_module+0x140/0x200 do_syscall_64+0x35/0x80 entry_SYSCALL_64_after_hwframe+0x46/0xb0 The reason is that an OOM happened which triggers the destroy of the workqueue, however, the workqueue is alloced in the later process, thus a null-ptr-deref happened. A simple call graph is shown as below: vkms_init() vkms_create() devm_drm_dev_alloc() __devm_drm_dev_alloc() devm_drm_dev_init() devm_add_action_or_reset() devm_add_action() # an error happened devm_drm_dev_init_release() drm_dev_put() kref_put() drm_dev_release() vkms_release() destroy_workqueue() # null-ptr-deref happened vkms_modeset_init() vkms_output_init() vkms_crtc_init() # where the workqueue get allocated Fix this by checking if composer_workq is NULL before passing it to the destroy_workqueue() in vkms_release().
- Published
- Sep 17, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 10th percentile
- CWE
- CWE-476
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.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
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 kernel4.20 and later · before 5.10.173
- linux linux kernel5.11 and later · before 5.15.99
- linux linux kernel5.16 and later · before 6.1.16
- linux linux kernel6.2 and later · before 6.2.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
- 4.20affected
- 6c234fe37c57627a5baf96f552afa1fae2b67d4d and later · before 0b8f390e2251191f1b179cc87f65d54c96565f0daffected · git
- 6c234fe37c57627a5baf96f552afa1fae2b67d4d and later · before 1f9836f95271e7acf016667eee0aeae3386f9645affected · git
- 6c234fe37c57627a5baf96f552afa1fae2b67d4d and later · before 596f1ba3987e601e31a5abf1f75ce1d2635aceacaffected · git
- 6c234fe37c57627a5baf96f552afa1fae2b67d4d and later · before 57031c474c3a920ea73afeb5dc352e537f5793eeaffected · git
- 6c234fe37c57627a5baf96f552afa1fae2b67d4d and later · before 2fe2a8f40c21161ffe7653cc234e7934db5b7cc5affected · git
- before 4.20not affected · semver
- 5.10.173 and later · up to and including 5.10.*not affected · semver
- 5.15.99 and later · up to and including 5.15.*not affected · semver
- 6.1.16 and later · up to and including 6.1.*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 |
|---|---|---|---|
| AlmaLinux:8 | kernel-rt | before 4.18.0-553.70.1.rt7.411.el8_10 | 4.18.0-553.70.1.rt7.411.el8_10 |
| AlmaLinux:8 | kernel-rt-core | before 4.18.0-553.70.1.rt7.411.el8_10 | 4.18.0-553.70.1.rt7.411.el8_10 |
| AlmaLinux:8 | kernel-rt-debug | before 4.18.0-553.70.1.rt7.411.el8_10 | 4.18.0-553.70.1.rt7.411.el8_10 |
| AlmaLinux:8 | kernel-rt-debug-core | before 4.18.0-553.70.1.rt7.411.el8_10 | 4.18.0-553.70.1.rt7.411.el8_10 |
| AlmaLinux:8 | kernel-rt-debug-devel | before 4.18.0-553.70.1.rt7.411.el8_10 | 4.18.0-553.70.1.rt7.411.el8_10 |
| AlmaLinux:8 | kernel-rt-debug-modules | before 4.18.0-553.70.1.rt7.411.el8_10 | 4.18.0-553.70.1.rt7.411.el8_10 |
| AlmaLinux:8 | kernel-rt-debug-modules-extra | before 4.18.0-553.70.1.rt7.411.el8_10 | 4.18.0-553.70.1.rt7.411.el8_10 |
| AlmaLinux:8 | kernel-rt-devel | before 4.18.0-553.70.1.rt7.411.el8_10 | 4.18.0-553.70.1.rt7.411.el8_10 |
| AlmaLinux:8 | kernel-rt-modules | before 4.18.0-553.70.1.rt7.411.el8_10 | 4.18.0-553.70.1.rt7.411.el8_10 |
| AlmaLinux:8 | kernel-rt-modules-extra | before 4.18.0-553.70.1.rt7.411.el8_10 | 4.18.0-553.70.1.rt7.411.el8_10 |
| Debian:12 | linux | before 6.1.20-1 | 6.1.20-1 |
| Red Hat:enterprise_linux:8::baseos | bpftool | before 0:4.18.0-553.70.1.el8_10 | 0:4.18.0-553.70.1.el8_10 |
| Red Hat:enterprise_linux:8::baseos | bpftool-debuginfo | before 0:4.18.0-553.70.1.el8_10 | 0:4.18.0-553.70.1.el8_10 |
| Red Hat:enterprise_linux:8::baseos | kernel | before 0:4.18.0-553.70.1.el8_10 | 0:4.18.0-553.70.1.el8_10 |
| Red Hat:enterprise_linux:8::baseos | kernel-abi-stablelists | before 0:4.18.0-553.70.1.el8_10 | 0:4.18.0-553.70.1.el8_10 |
| Red Hat:enterprise_linux:8::baseos | kernel-core | before 0:4.18.0-553.70.1.el8_10 | 0:4.18.0-553.70.1.el8_10 |
| Red Hat:enterprise_linux:8::baseos | kernel-debug | before 0:4.18.0-553.70.1.el8_10 | 0:4.18.0-553.70.1.el8_10 |
| Red Hat:enterprise_linux:8::baseos | kernel-debug-core | before 0:4.18.0-553.70.1.el8_10 | 0:4.18.0-553.70.1.el8_10 |
| Red Hat:enterprise_linux:8::baseos | kernel-debug-debuginfo | before 0:4.18.0-553.70.1.el8_10 | 0:4.18.0-553.70.1.el8_10 |
| Red Hat:enterprise_linux:8::baseos | kernel-debug-devel | before 0:4.18.0-553.70.1.el8_10 | 0:4.18.0-553.70.1.el8_10 |
| Red Hat:enterprise_linux:8::baseos | kernel-debug-modules | before 0:4.18.0-553.70.1.el8_10 | 0:4.18.0-553.70.1.el8_10 |
| Red Hat:enterprise_linux:8::baseos | kernel-debug-modules-extra | before 0:4.18.0-553.70.1.el8_10 | 0:4.18.0-553.70.1.el8_10 |
| Red Hat:enterprise_linux:8::baseos | kernel-debuginfo | before 0:4.18.0-553.70.1.el8_10 | 0:4.18.0-553.70.1.el8_10 |
| Red Hat:enterprise_linux:8::baseos | kernel-debuginfo-common-aarch64 | before 0:4.18.0-553.70.1.el8_10 | 0:4.18.0-553.70.1.el8_10 |
+87
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-2022-50367Sep 17, 2025 · fs: fix UAF/GPF bug in nilfs_mdt_destroy31Monitor
- ← EarlierCVE-2022-50368Sep 17, 2025 · drm/msm/dsi: fix memory corruption with too many bridges31Monitor
- Later →CVE-2022-50370Sep 17, 2025 · i2c: designware: Fix handling of real but unexpected device interrupts22Monitor
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 | 0b8f390e2251191f1b179cc87f65d54c96565f0d | Vendor (CNA) |
| Linux Linux | 1f9836f95271e7acf016667eee0aeae3386f9645 | Vendor (CNA) |
| Linux Linux | 2fe2a8f40c21161ffe7653cc234e7934db5b7cc5 | Vendor (CNA) |
| Linux Linux | 57031c474c3a920ea73afeb5dc352e537f5793ee | Vendor (CNA) |
| Linux Linux | 596f1ba3987e601e31a5abf1f75ce1d2635aceac | Vendor (CNA) |
| almalinux:kernel-rt | 4.18.0-553.70.1.rt7.411.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-rt-core | 4.18.0-553.70.1.rt7.411.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-rt-debug | 4.18.0-553.70.1.rt7.411.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-rt-debug-core | 4.18.0-553.70.1.rt7.411.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-rt-debug-devel | 4.18.0-553.70.1.rt7.411.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-rt-debug-modules | 4.18.0-553.70.1.rt7.411.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-rt-debug-modules-extra | 4.18.0-553.70.1.rt7.411.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-rt-devel | 4.18.0-553.70.1.rt7.411.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-rt-modules | 4.18.0-553.70.1.rt7.411.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-rt-modules-extra | 4.18.0-553.70.1.rt7.411.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| debian:linux | 6.1.20-1 · Debian:12 | Package registry (OSV) |
| red hat:bpftool | 0:4.18.0-553.70.1.el8_10 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:bpftool-debuginfo | 0:4.18.0-553.70.1.el8_10 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:kernel | 0:4.18.0-553.70.1.el8_10 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:kernel-abi-stablelists | 0:4.18.0-553.70.1.el8_10 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:kernel-core | 0:4.18.0-553.70.1.el8_10 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:kernel-debug | 0:4.18.0-553.70.1.el8_10 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:kernel-debug-core | 0:4.18.0-553.70.1.el8_10 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:kernel-debug-debuginfo | 0:4.18.0-553.70.1.el8_10 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:kernel-debug-devel | 0:4.18.0-553.70.1.el8_10 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:kernel-debug-modules | 0:4.18.0-553.70.1.el8_10 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:kernel-debug-modules-extra | 0:4.18.0-553.70.1.el8_10 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:kernel-debuginfo | 0:4.18.0-553.70.1.el8_10 · Red Hat:enterprise_linux:8::baseos | 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).
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)
CWE-476 · NULL Pointer DereferenceCVSS 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 (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.