CVE-2024-42279

linux: In the Linux kernel, the following vulnerability has been resolved: spi: microchip-core: ensure TX and RX FIFOs are...

CVE-2024-42279 is fixed in 22 products on 1 platform, first by DEBIAN-CVE-2024-42279, released August 17, 2024. It is not reported as exploited. Patch Radar priority: Routine.

Routine
CVSS
5.5
medium
Exploitation
None reported
No vendor assessment
CISA KEV
Not listed
Not in the Known Exploited Vulnerabilities catalog
EPSS
0.0023
14th percentile

In the Linux kernel, the following vulnerability has been resolved: spi: microchip-core: ensure TX and RX FIFOs are empty at start of a transfer While transmitting with rx_len == 0, the RX FIFO is not going to be emptied in the interrupt handler. A subsequent transfer could then read crap from the previous transfer out of the RX FIFO into the start RX buffer. The core provides a register that will empty the RX and TX FIFOs, so do that before each transfer.

Where it's fixed

ProductFixed inFixReleased
Linux
dtb-aarch64 · opensuse-leap 15.6 6.4.0-150600.23.22.1 SUSE-SU-2024:3383-1 Sep 23, 2024
kernel-64kb · opensuse-leap 15.6 6.4.0-150600.23.22.1 SUSE-SU-2024:3383-1 Sep 23, 2024
kernel-64kb · sles 15.6 6.4.0-150600.23.22.1 SUSE-SU-2024:3383-1 Sep 23, 2024
kernel-azure · opensuse-leap 15.6 6.4.0-150600.8.11.1 SUSE-SU-2024:3194-1 Sep 10, 2024
kernel-azure · sles 15.6 6.4.0-150600.8.11.1 SUSE-SU-2024:3194-1 Sep 10, 2024
kernel-debug · opensuse-leap 15.6 6.4.0-150600.23.22.1 SUSE-SU-2024:3383-1 Sep 23, 2024
kernel-default · opensuse-leap 15.6 6.4.0-150600.23.22.1 SUSE-SU-2024:3383-1 Sep 23, 2024
kernel-default · sles 15.6 6.4.0-150600.23.22.1 SUSE-SU-2024:3383-1 Sep 23, 2024
kernel-default-base · opensuse-leap 15.6 6.4.0-150600.23.22.1.150600.12.8.3 SUSE-SU-2024:3383-1 Sep 23, 2024
kernel-default-base · sles 15.6 6.4.0-150600.23.22.1.150600.12.8.3 SUSE-SU-2024:3383-1 Sep 23, 2024
kernel-docs · opensuse-leap 15.6 6.4.0-150600.23.22.1 SUSE-SU-2024:3383-1 Sep 23, 2024
kernel-docs · sles 15.6 6.4.0-150600.23.22.1 SUSE-SU-2024:3383-1 Sep 23, 2024
kernel-kvmsmall · opensuse-leap 15.6 6.4.0-150600.23.22.1 SUSE-SU-2024:3383-1 Sep 23, 2024
kernel-livepatch-SLE15-SP6-RT_Update_2 · sles 15.6 1-150600.1.3.2 SUSE-SU-2024:3195-1 Sep 10, 2024
kernel-livepatch-SLE15-SP6_Update_4 · sles 15.6 1-150600.13.3.3 SUSE-SU-2024:3383-1 Sep 23, 2024
kernel-obs-build · opensuse-leap 15.6 6.4.0-150600.23.22.1 SUSE-SU-2024:3383-1 Sep 23, 2024
kernel-obs-build · sles 15.6 6.4.0-150600.23.22.1 SUSE-SU-2024:3383-1 Sep 23, 2024
kernel-obs-qa · opensuse-leap 15.6 6.4.0-150600.23.22.1 SUSE-SU-2024:3383-1 Sep 23, 2024
kernel-rt · opensuse-leap 15.6 6.4.0-150600.10.8.3 SUSE-SU-2024:3195-1 Sep 10, 2024
kernel-rt_debug · opensuse-leap 15.6 6.4.0-150600.10.8.3 SUSE-SU-2024:3195-1 Sep 10, 2024
kernel-source · opensuse-leap 15.6 6.4.0-150600.23.22.1 SUSE-SU-2024:3383-1 Sep 23, 2024
kernel-source · sles 15.6 6.4.0-150600.23.22.1 SUSE-SU-2024:3383-1 Sep 23, 2024
kernel-source-azure · opensuse-leap 15.6 6.4.0-150600.8.11.1 SUSE-SU-2024:3194-1 Sep 10, 2024
kernel-source-azure · sles 15.6 6.4.0-150600.8.11.1 SUSE-SU-2024:3194-1 Sep 10, 2024
kernel-source-rt · opensuse-leap 15.6 6.4.0-150600.10.8.3 SUSE-SU-2024:3195-1 Sep 10, 2024
kernel-syms · opensuse-leap 15.6 6.4.0-150600.23.22.1 SUSE-SU-2024:3383-1 Sep 23, 2024
kernel-syms · sles 15.6 6.4.0-150600.23.22.1 SUSE-SU-2024:3383-1 Sep 23, 2024
kernel-syms-azure · opensuse-leap 15.6 6.4.0-150600.8.11.1 SUSE-SU-2024:3194-1 Sep 10, 2024
kernel-syms-azure · sles 15.6 6.4.0-150600.8.11.1 SUSE-SU-2024:3194-1 Sep 10, 2024
kernel-syms-rt · opensuse-leap 15.6 6.4.0-150600.10.8.1 SUSE-SU-2024:3195-1 Sep 10, 2024
kernel-zfcpdump · opensuse-leap 15.6 6.4.0-150600.23.22.1 SUSE-SU-2024:3383-1 Sep 23, 2024
kernel-zfcpdump · sles 15.6 6.4.0-150600.23.22.1 SUSE-SU-2024:3383-1 Sep 23, 2024
linux · Debian 13.5 (trixie) 6.10.3-1 DEBIAN-CVE-2024-42279 Aug 17, 2024
linux · Debian 14 6.10.3-1 DEBIAN-CVE-2024-42279 Aug 17, 2024

Patch Radar data is free to use with attribution. Terms and how to credit it.

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.