Kernel crash via unchecked mailbox allocation failure
Published May 24, 2024 · Updated May 11, 2026
NULL pointer dereference in the Linux kernel qlcnic driver allows local users to crash the kernel during receive-ring setup. qlcnic_83xx_add_rings dereferences cmd.req.arg without checking whether alloc_mbx_args failed to allocate the mailbox arguments. Reachability requires the qlcnic driver and an allocation failure while additional receive rings are configured; the static-analysis report notes that this condition is hard to trigger.
Summary
What happened
NULL pointer dereference in the Linux kernel qlcnic driver allows local users to crash the kernel during receive-ring setup. qlcnic_83xx_add_rings dereferences cmd.req.arg without checking whether alloc_mbx_args failed to allocate the mailbox arguments. Reachability requires the qlcnic driver and an allocation failure while additional receive rings are configured; the static-analysis report notes that this condition is hard to trigger.
The record
- CVE
- CVE-2021-47542
- Published
- May 24, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-476, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 24, 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=7f9664525f9cb507de9198a395a111371413f230 <15fa12c119f869173f9b710cbe6a4a14071d2105
- Affected versionversion=7f9664525f9cb507de9198a395a111371413f230 <3a061d54e260b701b538873b43e399d9b8b83e03
- Affected versionversion=7f9664525f9cb507de9198a395a111371413f230 <550658a2d61e4eaf522c8ebc7fad76dc376bfb45
- Affected versionversion=7f9664525f9cb507de9198a395a111371413f230 <57af54a56024435d83e44c78449513b414eb6edf
- Affected versionversion=7f9664525f9cb507de9198a395a111371413f230 <b4f217d6fcc00c3fdc0921a7691f30be7490b073
- Affected versionversion=7f9664525f9cb507de9198a395a111371413f230 <bbeb0325a7460ebf1e03f5e0bfc5c652fba9519f
- Affected versionversion=7f9664525f9cb507de9198a395a111371413f230 <c5ef33c1489b2cd74368057fa00b5d2183bb5853
- Affected versionversion=7f9664525f9cb507de9198a395a111371413f230 <e2dabc4f7e7b60299c20a36d6a7b24ed9bf8e572
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