CVE-2024-42249
published 2024-08-07CVE-2024-42249: In the Linux kernel, the following vulnerability has been resolved: spi: don't unoptimize message in spi_async() Calling spi_maybe_unoptimize_message() in…
PriorityP49low3.3CVSS 3.1
AVLACLPRLUINSUCNILAN
EPSS
0.19%
9.1th percentile
In the Linux kernel, the following vulnerability has been resolved:
spi: don't unoptimize message in spi_async()
Calling spi_maybe_unoptimize_message() in spi_async() is wrong because
the message is likely to be in the queue and not transferred yet. This
can corrupt the message while it is being used by the controller driver.
spi_maybe_unoptimize_message() is already called in the correct place
in spi_finalize_current_message() to balance the call to
spi_maybe_optimize_message() in spi_async().
Affected
7 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 6.9.10-1 (forky) | linux 6.9.10-1 (forky) |
| linux | linux | — | — |
| linux | linux | >= 7b1d87af14d9ae902ed0c5dc5fabf4eea5abdf02 < 8b9af6d67517ce4a0015928b3cf35bfd2b1bc1c2 | 8b9af6d67517ce4a0015928b3cf35bfd2b1bc1c2 |
| linux | linux | >= 7b1d87af14d9ae902ed0c5dc5fabf4eea5abdf02 < c86a918b1bdba78fb155184f8d88dfba1e63335d | c86a918b1bdba78fb155184f8d88dfba1e63335d |
| linux | linux_kernel | >= 0 < 6.9.10-1 | 6.9.10-1 |
| linux | linux_kernel | >= 0 < 6.9.10-1 | 6.9.10-1 |
| linux | linux_kernel | >= 6.9 < 6.9.10 | 6.9.10 |
CVSS provenance
nvdv3.13.3LOWCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
osv3.3LOW
vendor_debian3.3LOW
vendor_redhat3.3LOW
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: spi: don't unoptimize message in spi_async()
vendor_redhat·2024-08-07·CVSS 3.3
CVE-2024-42249 [LOW] CWE-99 kernel: spi: don't unoptimize message in spi_async()
kernel: spi: don't unoptimize message in spi_async()
In the Linux kernel, the following vulnerability has been resolved:
spi: don't unoptimize message in spi_async()
Calling spi_maybe_unoptimize_message() in spi_async() is wrong because
the message is likely to be in the queue and not transferred yet. This
can corrupt the message while it is being used by the controller driver.
spi_maybe_unoptimize_message() is already called in the correct place
in spi_finalize_current_message() to balance the call to
spi_maybe_optimize_message() in spi_async().
Package: kernel (Red Hat Enterprise Linux 6) - Not affected
Package: kernel (Red Hat Enterprise Linux 7) - Out of support scope
Package: kernel-rt (Red Hat Enterprise Linux 7) - Out of support scope
Package: kernel (Red Hat Enterprise Linux 8
Debian
CVE-2024-42249: linux - In the Linux kernel, the following vulnerability has been resolved: spi: don't ...
vendor_debian·2024·CVSS 3.3
CVE-2024-42249 [LOW] CVE-2024-42249: linux - In the Linux kernel, the following vulnerability has been resolved: spi: don't ...
In the Linux kernel, the following vulnerability has been resolved: spi: don't unoptimize message in spi_async() Calling spi_maybe_unoptimize_message() in spi_async() is wrong because the message is likely to be in the queue and not transferred yet. This can corrupt the message while it is being used by the controller driver. spi_maybe_unoptimize_message() is already called in the correct place in spi_finalize_current_message() to balance the call to spi_maybe_optimize_message() in spi_async().
Scope: local
bookworm: resolved
bullseye: resolved
forky: resolved (fixed in 6.9.10-1)
sid: resolved (fixed in 6.9.10-1)
trixie: resolved (fixed in 6.9.10-1)
OSV
CVE-2024-42249: In the Linux kernel, the following vulnerability has been resolved: spi: don't unoptimize message in spi_async() Calling spi_maybe_unoptimize_message(
osv·2024-08-07·CVSS 3.3
CVE-2024-42249 [LOW] CVE-2024-42249: In the Linux kernel, the following vulnerability has been resolved: spi: don't unoptimize message in spi_async() Calling spi_maybe_unoptimize_message(
In the Linux kernel, the following vulnerability has been resolved: spi: don't unoptimize message in spi_async() Calling spi_maybe_unoptimize_message() in spi_async() is wrong because the message is likely to be in the queue and not transferred yet. This can corrupt the message while it is being used by the controller driver. spi_maybe_unoptimize_message() is already called in the correct place in spi_finalize_current_message() to balance the call to spi_maybe_optimize_message() in spi_async().
GHSA
GHSA-jvrg-cvpm-4p85: In the Linux kernel, the following vulnerability has been resolved:
spi: don't unoptimize message in spi_async()
Calling spi_maybe_unoptimize_messag
ghsa_unreviewed·2024-08-07
CVE-2024-42249 [LOW] GHSA-jvrg-cvpm-4p85: In the Linux kernel, the following vulnerability has been resolved:
spi: don't unoptimize message in spi_async()
Calling spi_maybe_unoptimize_messag
In the Linux kernel, the following vulnerability has been resolved:
spi: don't unoptimize message in spi_async()
Calling spi_maybe_unoptimize_message() in spi_async() is wrong because
the message is likely to be in the queue and not transferred yet. This
can corrupt the message while it is being used by the controller driver.
spi_maybe_unoptimize_message() is already called in the correct place
in spi_finalize_current_message() to balance the call to
spi_maybe_optimize_message() in spi_async().
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
2024-08-07
Published