Kernel crash via unchecked ioremap failure
Published Mar 25, 2024 · Updated May 11, 2026
NULL pointer dereference in the Fujitsu FMVJ18x PCMCIA driver in affected Linux kernels allows local users to crash the kernel. The fmvj18x_get_hwinfo() function continues after ioremap() returns NULL and dereferences the failed I/O-memory mapping instead of rejecting device initialization. Reaching the fault requires local low-privileged access, the Fujitsu driver and hardware path, and an ioremap() failure; the bounded impact is a kernel crash.
Summary
What happened
NULL pointer dereference in the Fujitsu FMVJ18x PCMCIA driver in affected Linux kernels allows local users to crash the kernel. The fmvj18x_get_hwinfo() function continues after ioremap() returns NULL and dereferences the failed I/O-memory mapping instead of rejecting device initialization. Reaching the fault requires local low-privileged access, the Fujitsu driver and hardware path, and an ioremap() failure; the bounded impact is a kernel crash.
The record
- CVE
- CVE-2021-47149
- Published
- Mar 25, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-476, T1499.004
- 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=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <22049c3d40f08facd1867548716a484dad6b3251
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <52202be1cd996cde6e8969a128dc27ee45a7cb5e
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <6dbf1101594f7c76990b63c35b5a40205a914b6b
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <71723a796ab7881f491d663c6cd94b29be5fba50
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <7883d3895d0fbb0ba9bff0f8665f99974b45210f
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <b92170e209f7746ed72eaac98f2c2f4b9af734e6
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <c4f1c23edbe921ab2ecd6140d700e756cd44c5f7
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <f14bf57a08779a5dee9936f63ada0149ea89c5e6
- Affected versionversion=2.6.12
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