CVE-2024-35818
published 2024-05-17CVE-2024-35818: In the Linux kernel, the following vulnerability has been resolved: LoongArch: Define the __io_aw() hook as mmiowb() Commit fb24ea52f78e0d595852e ("drivers…
PriorityP419medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.17%
6.7th percentile
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:radeo
Affected
14 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 6.1.85-1 (bookworm) | linux 6.1.85-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | >= fa96b57c149061f71a70bd6582d995f6424fbbf4 < 97cd43ba824aec764f5ea2790d0c0a318f885167 | 97cd43ba824aec764f5ea2790d0c0a318f885167 |
| linux | linux | >= fa96b57c149061f71a70bd6582d995f6424fbbf4 < d7d7c6cdea875be3b241d7d39873bb431db7154d | d7d7c6cdea875be3b241d7d39873bb431db7154d |
| linux | linux | >= fa96b57c149061f71a70bd6582d995f6424fbbf4 < 0b61a7dc6712b78799b3949997e8a5e94db5c4b0 | 0b61a7dc6712b78799b3949997e8a5e94db5c4b0 |
| linux | linux | >= fa96b57c149061f71a70bd6582d995f6424fbbf4 < 9adec248bba33b1503252caf8e59d81febfc5ceb | 9adec248bba33b1503252caf8e59d81febfc5ceb |
| linux | linux | >= fa96b57c149061f71a70bd6582d995f6424fbbf4 < 9c68ece8b2a5c5ff9b2fcaea923dd73efeb174cd | 9c68ece8b2a5c5ff9b2fcaea923dd73efeb174cd |
| linux | linux_kernel | >= 0 < 6.1.85-1 | 6.1.85-1 |
| linux | linux_kernel | >= 0 < 6.7.12-1 | 6.7.12-1 |
| linux | linux_kernel | >= 0 < 6.7.12-1 | 6.7.12-1 |
| linux | linux_kernel | >= 5.19 < 6.1.84 | 6.1.84 |
| linux | linux_kernel | >= 6.2 < 6.6.24 | 6.6.24 |
| linux | linux_kernel | >= 6.7 < 6.7.12 | 6.7.12 |
| linux | linux_kernel | >= 6.8 < 6.8.3 | 6.8.3 |
CVSS provenance
nvdv3.15.5MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
osv5.5MEDIUM
vendor_debian5.5MEDIUM
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.
Red Hat
kernel: LoongArch: Define the __io_aw() hook as mmiowb()
vendor_redhat·2024-05-17·CVSS 5.5
CVE-2024-35818 [MEDIUM] kernel: LoongArch: Define the __io_aw() hook as mmiowb()
kernel: LoongArch: Define the __io_aw() hook as mmiowb()
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 simila
Debian
CVE-2024-35818: linux - In the Linux kernel, the following vulnerability has been resolved: LoongArch: ...
vendor_debian·2024·CVSS 5.5
CVE-2024-35818 [MEDIUM] CVE-2024-35818: linux - In the Linux kernel, the following vulnerability has been resolved: LoongArch: ...
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 dri
OSV
CVE-2024-35818: In the Linux kernel, the following vulnerability has been resolved: LoongArch: Define the __io_aw() hook as mmiowb() Commit fb24ea52f78e0d595852e ("dr
osv·2024-05-17·CVSS 5.5
CVE-2024-35818 [MEDIUM] CVE-2024-35818: In the Linux kernel, the following vulnerability has been resolved: LoongArch: Define the __io_aw() hook as mmiowb() Commit fb24ea52f78e0d595852e ("dr
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 dri
GHSA
GHSA-4gg5-g35c-mghx: In the Linux kernel, the following vulnerability has been resolved:
LoongArch: Define the __io_aw() hook as mmiowb()
Commit fb24ea52f78e0d595852e ("
ghsa_unreviewed·2024-05-17
CVE-2024-35818 [MEDIUM] CWE-667 GHSA-4gg5-g35c-mghx: In the Linux kernel, the following vulnerability has been resolved:
LoongArch: Define the __io_aw() hook as mmiowb()
Commit fb24ea52f78e0d595852e ("
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
No detection rules found.
No public exploits indexed.
https://git.kernel.org/stable/c/0b61a7dc6712b78799b3949997e8a5e94db5c4b0https://git.kernel.org/stable/c/97cd43ba824aec764f5ea2790d0c0a318f885167https://git.kernel.org/stable/c/9adec248bba33b1503252caf8e59d81febfc5cebhttps://git.kernel.org/stable/c/9c68ece8b2a5c5ff9b2fcaea923dd73efeb174cdhttps://git.kernel.org/stable/c/d7d7c6cdea875be3b241d7d39873bb431db7154dhttps://git.kernel.org/stable/c/0b61a7dc6712b78799b3949997e8a5e94db5c4b0https://git.kernel.org/stable/c/97cd43ba824aec764f5ea2790d0c0a318f885167https://git.kernel.org/stable/c/9adec248bba33b1503252caf8e59d81febfc5cebhttps://git.kernel.org/stable/c/9c68ece8b2a5c5ff9b2fcaea923dd73efeb174cdhttps://git.kernel.org/stable/c/d7d7c6cdea875be3b241d7d39873bb431db7154d
2024-05-17
Published