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

Goal: 1000 CNY · Raised: 1359 CNY

100%
Buy Us a Coffee

CVE-2024-35818— LoongArch: Define the __io_aw() hook as mmiowb()

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 存在安全漏洞。目前尚无此漏洞的相关信息，请随时关注CNNVD或厂商公告。

AI Predicted 5.5 Difficulty: Hard EPSS 0.17% · P6

Possible ATT&CK Techniques 1 AI

T1059 · Command and Scripting Interpreter

Affected Version Matrix 12

VendorProduct Version RangeStatus
Linux Linux fa96b57c149061f71a70bd6582d995f6424fbbf4< 97cd43ba824aec764f5ea2790d0c0a318f885167 affected
fa96b57c149061f71a70bd6582d995f6424fbbf4< d7d7c6cdea875be3b241d7d39873bb431db7154d affected
fa96b57c149061f71a70bd6582d995f6424fbbf4< 0b61a7dc6712b78799b3949997e8a5e94db5c4b0 affected
fa96b57c149061f71a70bd6582d995f6424fbbf4< 9adec248bba33b1503252caf8e59d81febfc5ceb affected
fa96b57c149061f71a70bd6582d995f6424fbbf4< 9c68ece8b2a5c5ff9b2fcaea923dd73efeb174cd affected
5.19 affected
< 5.19 unaffected
6.1.84≤ 6.1.* unaffected
… +4 more rows
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2024-35818

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
LoongArch: Define the __io_aw() hook as mmiowb()
Source: CVE Program / CVE List V5
Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved: LoongArch: Define the __io_aw() hook as mmiowb() Commit fb24ea52f78e0d595852e ("drivers: Remove explicit invocations of mmiowb()") remove all mmiowb() in drivers, but it says: "NOTE: mmiowb() has only ever guaranteed ordering in conjunction with spin_unlock(). However, pairing each mmiowb() removal in this patch with the corresponding call to spin_unlock() is not at all trivial, so there is a small chance that this change may regress any drivers incorrectly relying on mmiowb() to order MMIO writes between CPUs using lock-free synchronisation." The mmio in radeon_ring_commit() is protected by a mutex rather than a spinlock, but in the mutex fastpath it behaves similar to spinlock. We can add mmiowb() calls in the radeon driver but the maintainer says he doesn't like such a workaround, and radeon is not the only example of mutex protected mmio. So we should extend the mmiowb tracking system from spinlock to mutex, and maybe other locking primitives. This is not easy and error prone, so we solve it in the architectural code, by simply defining the __io_aw() hook as mmiowb(). And we no longer need to override queued_spin_unlock() so use the generic definition. Without this, we get such an error when run 'glxgears' on weak ordering architectures such as LoongArch: radeon 0000:04:00.0: ring 0 stalled for more than 10324msec radeon 0000:04:00.0: ring 3 stalled for more than 10240msec radeon 0000:04:00.0: GPU lockup (current fence id 0x000000000001f412 last fence id 0x000000000001f414 on ring 3) radeon 0000:04:00.0: GPU lockup (current fence id 0x000000000000f940 last fence id 0x000000000000f941 on ring 0) radeon 0000:04:00.0: scheduling IB failed (-35). [drm:radeon_gem_va_ioctl [radeon]] *ERROR* Couldn't update BO_VA (-35) radeon 0000:04:00.0: scheduling IB failed (-35). [drm:radeon_gem_va_ioctl [radeon]] *ERROR* Couldn't update BO_VA (-35) radeon 0000:04:00.0: scheduling IB failed (-35). [drm:radeon_gem_va_ioctl [radeon]] *ERROR* Couldn't update BO_VA (-35) radeon 0000:04:00.0: scheduling IB failed (-35). [drm:radeon_gem_va_ioctl [radeon]] *ERROR* Couldn't update BO_VA (-35) radeon 0000:04:00.0: scheduling IB failed (-35). [drm:radeon_gem_va_ioctl [radeon]] *ERROR* Couldn't update BO_VA (-35) radeon 0000:04:00.0: scheduling IB failed (-35). [drm:radeon_gem_va_ioctl [radeon]] *ERROR* Couldn't update BO_VA (-35) radeon 0000:04:00.0: scheduling IB failed (-35). [drm:radeon_gem_va_ioctl [radeon]] *ERROR* Couldn't update BO_VA (-35)
Source: CVE Program / CVE List V5
CVSS Information
N/A
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 存在安全漏洞。目前尚无此漏洞的相关信息，请随时关注CNNVD或厂商公告。
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 fa96b57c149061f71a70bd6582d995f6424fbbf4 ~ 97cd43ba824aec764f5ea2790d0c0a318f885167 -
Linux Linux 5.19 -

II. Public POCs for CVE-2024-35818

# 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-35818

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

Other References for CVE-2024-35818 (5)

Same Patch Batch · Linux · 2024-05-17 · 135 CVEs total

CVE-2023-52687 9.8 CRITICAL crypto: safexcel - Add error handling for dma_map_sg() calls
CVE-2024-35856 8.8 HIGH Bluetooth: btusb: mediatek: Fix double free of skb in coredump
CVE-2024-35804 8.8 HIGH KVM: x86: Mark target gfn of emulated atomic instruction as dirty
CVE-2024-35843 8.8 HIGH iommu/vt-d: Use device rbtree in iopf reporting path
CVE-2024-35811 8.8 HIGH wifi: brcmfmac: Fix use-after-free bug in brcmf_cfg80211_detach
CVE-2024-27415 8.8 HIGH netfilter: bridge: confirm multicast packets before passing them up the stack
CVE-2024-27416 8.8 HIGH Bluetooth: hci_event: Fix handling of HCI_EV_IO_CAPA_REQUEST
CVE-2024-27404 8.2 HIGH mptcp: fix data races on remote_id
CVE-2023-52669 8.2 HIGH crypto: s390/aes - Fix buffer overread in CTR mode
CVE-2024-35834 8.2 HIGH xsk: recycle buffer in case Rx queue was full
CVE-2024-35789 8.0 HIGH wifi: mac80211: check/clear fast rx for non-4addr sta VLAN changes
CVE-2024-35830 7.8 HIGH media: tc358743: register v4l2 async device only after successful setup
CVE-2024-35835 7.8 HIGH net/mlx5e: fix a double-free in arfs_create_groups
CVE-2024-35827 7.8 HIGH io_uring/net: fix overflow check in io_recvmsg_mshot_prep()
CVE-2023-52662 7.8 HIGH drm/vmwgfx: fix a memleak in vmw_gmrid_man_get_node
CVE-2024-35817 7.8 HIGH drm/amdgpu: amdgpu_ttm_gart_bind set gtt bound flag
CVE-2024-35808 7.8 HIGH md/dm-raid: don't call md_reap_sync_thread() directly
CVE-2024-35793 7.8 HIGH debugfs: fix wait/cancellation handling during remove
CVE-2024-35798 7.8 HIGH btrfs: fix race in read_extent_buffer_pages()
CVE-2024-35814 7.8 HIGH swiotlb: Fix double-allocation of slots due to broken alignment handling

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

IV. Related Vulnerabilities

Same product: Linux
Same vendor: Linux

V. Comments for CVE-2024-35818

No comments yet

Leave a comment