Kernel crash via unchecked NULL TX buffer write
Published May 1, 2024 · Updated May 11, 2026
NULL-pointer dereference in the MediaTek SPI driver in Linux allows attackers to crash affected systems via SPI transfers. The interrupt handler writes through trans->tx_buf without first checking whether the spi_transfer TX buffer is NULL. The driver and MediaTek SPI hardware must be present and processing a transfer with no TX buffer; the resulting invalid-memory write interrupts service by crashing the kernel.
Summary
What happened
NULL-pointer dereference in the MediaTek SPI driver in Linux allows attackers to crash affected systems via SPI transfers. The interrupt handler writes through trans->tx_buf without first checking whether the spi_transfer TX buffer is NULL. The driver and MediaTek SPI hardware must be present and processing a transfer with no TX buffer; the resulting invalid-memory write interrupts service by crashing the kernel.
The record
- CVE
- CVE-2024-27028
- Published
- May 1, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-476, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 1, 2024CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1ce24864bff40e11500a699789412115fdf244bf <1784053cf10a14c4ebd8a890bad5cfe1bee51713
- Affected versionversion=1ce24864bff40e11500a699789412115fdf244bf <2342b05ec5342a519e00524a507f7a6ea6791a38
- Affected versionversion=1ce24864bff40e11500a699789412115fdf244bf <55f8ea6731aa64871ee6aef7dba53ee9f9f3b2f6
- Affected versionversion=1ce24864bff40e11500a699789412115fdf244bf <62b1f837b15cf3ec2835724bdf8577e47d14c753
- Affected versionversion=1ce24864bff40e11500a699789412115fdf244bf <766ec94cc57492eab97cbbf1595bd516ab0cb0e4
- Affected versionversion=1ce24864bff40e11500a699789412115fdf244bf <a20ad45008a7c82f1184dc6dee280096009ece55
- Affected versionversion=1ce24864bff40e11500a699789412115fdf244bf <bcfcdf19698024565eff427706ebbd8df65abd11
- Affected versionversion=1ce24864bff40e11500a699789412115fdf244bf <bea82355df9e1c299625405b1947fc9b26b4c6d4
- Affected versionversion=1ce24864bff40e11500a699789412115fdf244bf <c10fed329c1c104f375a75ed97ea3abef0786d62
- Affected versionversion=4.11
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo