Kernel warning via unlocked CTS state update
Published May 1, 2024 · Updated May 11, 2026
Race condition in affected Linux kernels allows local users to trigger a kernel warning through the mxs-auart CTS interrupt path. The mxs_auart_irq_handle() handler calls uart_handle_cts_change() while updating CTS state without holding the serial port's uport->lock, violating the callee's locking requirement. Reachability requires an NXP i.MX28 system using the mxs-auart driver, and the documented failure occurred while the Bluetooth driver initialized.
Summary
What happened
Race condition in affected Linux kernels allows local users to trigger a kernel warning through the mxs-auart CTS interrupt path. The mxs_auart_irq_handle() handler calls uart_handle_cts_change() while updating CTS state without holding the serial port's uport->lock, violating the callee's locking requirement. Reachability requires an NXP i.MX28 system using the mxs-auart driver, and the documented failure occurred while the Bluetooth driver initialized.
The record
- CVE
- CVE-2024-27000
- Published
- May 1, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
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=3.18
- Affected versionversion=4d90bb147ef6b91f529a21b498ff2b5fdc6785b4 <0dc0637e6b16158af85945425821bfd0151adb37
- Affected versionversion=4d90bb147ef6b91f529a21b498ff2b5fdc6785b4 <21535ef0ac1945080198fe3e4347ea498205c99a
- Affected versionversion=4d90bb147ef6b91f529a21b498ff2b5fdc6785b4 <2c9b943e9924cf1269e44289bc5e60e51b0f5270
- Affected versionversion=4d90bb147ef6b91f529a21b498ff2b5fdc6785b4 <479244d68f5d94f3903eced52b093c1e01ddb495
- Affected versionversion=4d90bb147ef6b91f529a21b498ff2b5fdc6785b4 <54c4ec5f8c471b7c1137a1f769648549c423c026
- Affected versionversion=4d90bb147ef6b91f529a21b498ff2b5fdc6785b4 <56434e295bd446142025913bfdf1587f5e1970ad
- Affected versionversion=4d90bb147ef6b91f529a21b498ff2b5fdc6785b4 <5f40fd6ca2cf0bfbc5a5c9e403dfce8ca899ba37
- Affected versionversion=4d90bb147ef6b91f529a21b498ff2b5fdc6785b4 <94b0e65c75f4af888ab2dd6c90f060f762924e86
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.
Weakness, pattern, technique
No sourced classifications are available.
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