CVE-2021-1116
published 2021-10-27CVE-2021-1116: NVIDIA GPU Display Driver for Windows contains a vulnerability in the kernel mode layer (nvlddmkm.sys), where a NULL pointer dereference in the kernel, created…
PriorityP418medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.21%
11.6th percentile
NVIDIA GPU Display Driver for Windows contains a vulnerability in the kernel mode layer (nvlddmkm.sys), where a NULL pointer dereference in the kernel, created within user mode code, may lead to a denial of service in the form of a system crash.
Affected
5 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| nvidia | gpu_display_driver | >= 390 < 392.68 | 392.68 |
| nvidia | gpu_display_driver | >= 460 < 463.15 | 463.15 |
| nvidia | gpu_display_driver | >= 470 < 472.39 | 472.39 |
| nvidia | gpu_display_driver | >= 490 < 496.49 | 496.49 |
| nvidia | nvidia_gpu_display_driver | — | — |
CVSS provenance
nvdv3.15.5MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvdv2.02.1LOWAV:L/AC:L/Au:N/C:N/I:N/A:P
vendor_redhat5.5MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
GHSA-h2xf-5f3q-g28p: NVIDIA GPU Display Driver for Windows contains a vulnerability in the kernel mode layer (nvlddmkm
ghsa_unreviewed·2022-05-24
CVE-2021-1116 [MEDIUM] CWE-476 GHSA-h2xf-5f3q-g28p: NVIDIA GPU Display Driver for Windows contains a vulnerability in the kernel mode layer (nvlddmkm
NVIDIA GPU Display Driver for Windows contains a vulnerability in the kernel mode layer (nvlddmkm.sys), where a NULL pointer dereference in the kernel, created within user mode code, may lead to a denial of service in the form of a system crash.
Red Hat
kernel: btrfs: fix memory leak in __add_inode_ref()
vendor_redhat·2024-06-19·CVSS 5.5
CVE-2021-47585 [MEDIUM] CWE-404 kernel: btrfs: fix memory leak in __add_inode_ref()
kernel: btrfs: fix memory leak in __add_inode_ref()
In the Linux kernel, the following vulnerability has been resolved:
btrfs: fix memory leak in __add_inode_ref()
Line 1169 (#3) allocates a memory chunk for victim_name by kmalloc(),
but when the function returns in line 1184 (#4) victim_name allocated
by line 1169 (#3) is not freed, which will lead to a memory leak.
There is a similar snippet of code in this function as allocating a memory
chunk for victim_name in line 1104 (#1) as well as releasing the memory
in line 1116 (#2).
We should kfree() victim_name when the return value of backref_in_log()
is less than zero and before the function returns in line 1184 (#4).
1057 static inline int __add_inode_ref(struct btrfs_trans_handle *trans,
1058 struct btrfs_root *root,
1059 struct btrfs_p
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
2021-10-27
Published