Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1359 CNY

100%

CVE-2024-50221— drm/amd/pm: Vangogh: Fix kernel memory out of bounds write

Quick assessment

Affected
Linux Linux
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

Linux kernel是美国Linux基金会的开源操作系统Linux所使用的内核。 Linux kernel存在安全漏洞,该漏洞源于内核内存越界写入。

CVSS 7.8 · High EPSS 0.24% · P15

Possible ATT&CK Techniques 1 AI

T1068 · Exploitation for Privilege Escalation

Affected Version Matrix 8

VendorProduct Version RangeStatus
Linux Linux 41cec40bc9baba83d36a0718ea94bfe63189274a< f111de0f010308949254ee1cc45df8e6b8e1d7d4 affected
41cec40bc9baba83d36a0718ea94bfe63189274a< f8fd9f0d57af4f8f48b383ec28287af85b47cb9f affected
41cec40bc9baba83d36a0718ea94bfe63189274a< 4aa923a6e6406b43566ef6ac35a3d9a3197fa3e8 affected
6.6 affected
< 6.6 unaffected
6.6.63≤ 6.6.* unaffected
6.11.7≤ 6.11.* unaffected
6.12≤ * unaffected
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2024-50221

Vulnerability Information

Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
drm/amd/pm: Vangogh: Fix kernel memory out of bounds write
Source: CVE Program / CVE List V5
Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved: drm/amd/pm: Vangogh: Fix kernel memory out of bounds write KASAN reports that the GPU metrics table allocated in vangogh_tables_init() is not large enough for the memset done in smu_cmn_init_soft_gpu_metrics(). Condensed report follows: [ 33.861314] BUG: KASAN: slab-out-of-bounds in smu_cmn_init_soft_gpu_metrics+0x73/0x200 [amdgpu] [ 33.861799] Write of size 168 at addr ffff888129f59500 by task mangoapp/1067 ... [ 33.861808] CPU: 6 UID: 1000 PID: 1067 Comm: mangoapp Tainted: G W 6.12.0-rc4 #356 1a56f59a8b5182eeaf67eb7cb8b13594dd23b544 [ 33.861816] Tainted: [W]=WARN [ 33.861818] Hardware name: Valve Galileo/Galileo, BIOS F7G0107 12/01/2023 [ 33.861822] Call Trace: [ 33.861826] <TASK> [ 33.861829] dump_stack_lvl+0x66/0x90 [ 33.861838] print_report+0xce/0x620 [ 33.861853] kasan_report+0xda/0x110 [ 33.862794] kasan_check_range+0xfd/0x1a0 [ 33.862799] __asan_memset+0x23/0x40 [ 33.862803] smu_cmn_init_soft_gpu_metrics+0x73/0x200 [amdgpu 13b1bc364ec578808f676eba412c20eaab792779] [ 33.863306] vangogh_get_gpu_metrics_v2_4+0x123/0xad0 [amdgpu 13b1bc364ec578808f676eba412c20eaab792779] [ 33.864257] vangogh_common_get_gpu_metrics+0xb0c/0xbc0 [amdgpu 13b1bc364ec578808f676eba412c20eaab792779] [ 33.865682] amdgpu_dpm_get_gpu_metrics+0xcc/0x110 [amdgpu 13b1bc364ec578808f676eba412c20eaab792779] [ 33.866160] amdgpu_get_gpu_metrics+0x154/0x2d0 [amdgpu 13b1bc364ec578808f676eba412c20eaab792779] [ 33.867135] dev_attr_show+0x43/0xc0 [ 33.867147] sysfs_kf_seq_show+0x1f1/0x3b0 [ 33.867155] seq_read_iter+0x3f8/0x1140 [ 33.867173] vfs_read+0x76c/0xc50 [ 33.867198] ksys_read+0xfb/0x1d0 [ 33.867214] do_syscall_64+0x90/0x160 ... [ 33.867353] Allocated by task 378 on cpu 7 at 22.794876s: [ 33.867358] kasan_save_stack+0x33/0x50 [ 33.867364] kasan_save_track+0x17/0x60 [ 33.867367] __kasan_kmalloc+0x87/0x90 [ 33.867371] vangogh_init_smc_tables+0x3f9/0x840 [amdgpu] [ 33.867835] smu_sw_init+0xa32/0x1850 [amdgpu] [ 33.868299] amdgpu_device_init+0x467b/0x8d90 [amdgpu] [ 33.868733] amdgpu_driver_load_kms+0x19/0xf0 [amdgpu] [ 33.869167] amdgpu_pci_probe+0x2d6/0xcd0 [amdgpu] [ 33.869608] local_pci_probe+0xda/0x180 [ 33.869614] pci_device_probe+0x43f/0x6b0 Empirically we can confirm that the former allocates 152 bytes for the table, while the latter memsets the 168 large block. Root cause appears that when GPU metrics tables for v2_4 parts were added it was not considered to enlarge the table to fit. The fix in this patch is rather "brute force" and perhaps later should be done in a smarter way, by extracting and consolidating the part version to size logic to a common helper, instead of brute forcing the largest possible allocation. Nevertheless, for now this works and fixes the out of bounds write. v2: * Drop impossible v3_0 case. (Mario) (cherry picked from commit 0880f58f9609f0200483a49429af0f050d281703)
Source: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Source: CVE Program / CVE List V5
Vulnerability Type
N/A
Source: CVE Program / CVE List V5
Vulnerability Title
Linux kernel 安全漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
Linux kernel是美国Linux基金会的开源操作系统Linux所使用的内核。 Linux kernel存在安全漏洞,该漏洞源于内核内存越界写入。
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)

Affected Products

Vendor Product Affected Versions CPE Subscribe
Linux Linux 41cec40bc9baba83d36a0718ea94bfe63189274a ~ f111de0f010308949254ee1cc45df8e6b8e1d7d4 -
Linux Linux 6.6 -

II. Public POCs for CVE-2024-50221

# POC Description Source Link Shenlong Link
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2024-50221

请登录查看更多情报信息。

Patches & Fixes for CVE-2024-50221 (2)

Same Patch Batch · Linux · 2024-11-09 · 49 CVEs total

CVE-2024-50215 8.1 HIGH nvmet-auth: assign dh_key to NULL after kfree_sensitive
CVE-2024-50246 7.8 HIGH fs/ntfs3: Add rough attr alloc_size check
CVE-2024-50237 7.8 HIGH wifi: mac80211: do not pass a stopped vif to the driver in .get_txpower
CVE-2024-50235 7.8 HIGH wifi: cfg80211: clear wdev->cqm_config pointer on free
CVE-2024-50250 7.8 HIGH fsdax: dax_unshare_iter needs to copy entire blocks
CVE-2024-50230 7.8 HIGH nilfs2: fix kernel bug due to missing clearing of checked flag
CVE-2024-50253 7.8 HIGH bpf: Check the validity of nr_words in bpf_iter_bits_new()
CVE-2024-50225 7.8 HIGH btrfs: fix error propagation of split bios
CVE-2024-50217 7.8 HIGH btrfs: fix use-after-free of block device file in __btrfs_free_extra_devids()
CVE-2024-50262 7.8 HIGH bpf: Fix out-of-bounds write in trie_get_next_key()
CVE-2024-50261 7.8 HIGH macsec: Fix use-after-free while sending the offloading packet
CVE-2024-50241 7.5 HIGH NFSD: Initialize struct nfsd4_copy earlier
CVE-2024-50256 7.5 HIGH netfilter: nf_reject_ipv6: fix potential crash in nf_send_reset6()
CVE-2024-50247 7.3 HIGH fs/ntfs3: Check if more than chunk-size bytes are written
CVE-2024-50248 7.1 HIGH ntfs3: Add bounds checking to mi_enum_attr()
CVE-2024-50257 7.0 HIGH netfilter: Fix use-after-free in get_info()
CVE-2024-50222 7.0 HIGH iov_iter: fix copy_page_from_iter_atomic() if KMAP_LOCAL_FORCE_MAP
CVE-2024-50239 phy: qcom: qmp-usb-legacy: fix NULL-deref on runtime suspend
CVE-2024-50260 sock_map: fix a NULL pointer dereference in sock_map_link_update_prog()
CVE-2024-50244 fs/ntfs3: Additional check in ni_clear()

Showing top 20 of 49 CVEs. View all on vendor page &rarr; →

IV. Related Vulnerabilities

V. Comments for CVE-2024-50221

No comments yet


Leave a comment