CVE-2021-46995: can: mcp251xfd: mcp251xfd_probe(): fix an error pointer dereference in probe
In the Linux kernel, the following vulnerability has been resolved:
can: mcp251xfd: mcp251xfd_probe(): fix an error pointer dereference in probe
When we converted this code to use dev_err_probe() we accidentally
removed a return. It means that if devm_clk_get() it will lead to an
Oops when we call clk_get_rate() on the next line.
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel reliability issue in the MCP251xFD CAN bus driver. If clock acquisition fails during driver startup, the kernel may dereference an error pointer and crash with an Oops. Business urgency is highest for systems that use this CAN controller path, especially operational or embedded Linux deployments.
Executive priority
Treat as targeted operational reliability risk, not a broad internet-facing emergency. Patch during normal kernel maintenance unless affected CAN-enabled systems are safety-critical or experiencing probe-time crashes.
Technical view
The mcp251xfd_probe() path lost a return after conversion to dev_err_probe(). When devm_clk_get() fails, execution continues and clk_get_rate() is called on an error pointer. The source identifies Linux 5.12-related affected code and stable kernel fixes in referenced upstream commits.
Likely exposure
Exposure appears limited to Linux systems with the mcp251xfd CAN driver present and exercised during device probing. The bundle does not show network reachability, privilege escalation, data theft, or broad default exposure evidence.
Exploitation context
No active exploitation is reported in the provided sources, and the CVE is not marked KEV. The documented impact is a kernel Oops during probe when devm_clk_get() fails; no public exploit path is described in the bundle.
Researcher notes
Evidence is narrow: the source describes a missing return causing error-pointer dereference after devm_clk_get() failure. No CVSS, CWE, exploitability details, or downstream distro status are provided. Validate impact against actual hardware, kernel config, and vendor backport metadata.
Mitigation direction
Update to a vendor kernel containing the referenced stable fixes.
Check distribution or device vendor advisories for backported kernel packages.
Prioritize systems using MCP251xFD CAN hardware or this kernel driver.
Avoid relying on unsupported local patches without vendor validation.
Validation and detection
Inventory Linux kernel versions and affected device fleets.
Confirm whether the mcp251xfd CAN driver is built, loaded, or probed.
Review kernel logs for Oops events involving mcp251xfd_probe().
Verify installed kernels include the referenced stable commits or vendor backports.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2021-46995 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.