Kernel crash via uninitialized rp2 interrupt ports
Published Mar 25, 2024 · Updated May 11, 2026
NULL pointer dereference in the Linux rp2 serial driver allows local users to crash the kernel by triggering a device interrupt. rp2_probe registers rp2_uart_interrupt before asynchronous firmware loading finishes, and a missing firmware image leaves rp2_card ports uninitialized for the handler. The path requires a configured RocketPort EXPRESS or INFINITY PCI/PCIe adapter and an interrupt before port initialization; the demonstrated consequence is a kernel crash.
Summary
What happened
NULL pointer dereference in the Linux rp2 serial driver allows local users to crash the kernel by triggering a device interrupt. rp2_probe registers rp2_uart_interrupt before asynchronous firmware loading finishes, and a missing firmware image leaves rp2_card ports uninitialized for the handler. The path requires a configured RocketPort EXPRESS or INFINITY PCI/PCIe adapter and an interrupt before port initialization; the demonstrated consequence is a kernel crash.
The record
- CVE
- CVE-2021-47169
- Published
- Mar 25, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-476
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 25, 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.9
- Affected versionversion=7d9f49afa451d8565d00a5cea39acf9bb26feb50 <016002848c82eeb5d460489ce392d91fe18c475c
- Affected versionversion=7d9f49afa451d8565d00a5cea39acf9bb26feb50 <1cc57cb32c84e059bd158494f746b665fc14d1b1
- Affected versionversion=7d9f49afa451d8565d00a5cea39acf9bb26feb50 <1e04d5d5fe5e76af68f834e1941fcbfa439653be
- Affected versionversion=7d9f49afa451d8565d00a5cea39acf9bb26feb50 <35265552c7fe9553c75e324c80f45e28ff14eb6e
- Affected versionversion=7d9f49afa451d8565d00a5cea39acf9bb26feb50 <6a931ceb0b9401fe18d0c500e08164bf9cc7be4b
- Affected versionversion=7d9f49afa451d8565d00a5cea39acf9bb26feb50 <915452f40e2f495e187276c4407a4f567ec2307e
- Affected versionversion=7d9f49afa451d8565d00a5cea39acf9bb26feb50 <9b07b6973f7359e2dd6a9fe6db0c142634c823b7
- Affected versionversion=7d9f49afa451d8565d00a5cea39acf9bb26feb50 <c697244ce940ec07e2d745ccb63ca97fc0266fbc
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
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