CVE-2021-46973: net: qrtr: Avoid potential use after free in MHI send
In the Linux kernel, the following vulnerability has been resolved:
net: qrtr: Avoid potential use after free in MHI send
It is possible that the MHI ul_callback will be invoked immediately
following the queueing of the skb for transmission, leading to the
callback decrementing the refcount of the associated sk and freeing the
skb.
As such the dereference of skb and the increment of the sk refcount must
happen before the skb is queued, to avoid the skb to be used after free
and potentially the sk to drop its last refcount..
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel memory safety flaw in the QRTR MHI send path. A local attacker could potentially trigger use-after-free behavior and gain high impact over confidentiality, integrity, and availability. The source bundle does not show active exploitation or product-specific appliance exposure.
Executive priority
Prioritize normal high-severity kernel patching, especially on multi-user systems, developer workstations, and hosts running untrusted workloads. No source indicates emergency active exploitation, but kernel memory corruption can create broad compromise impact if reachable locally.
Technical view
The flaw is CWE-416 use-after-free. An MHI transmit callback may run immediately after an skb is queued, decrementing the socket reference and freeing the skb before later dereference/refcount handling. Kernel stable commits move skb dereference and socket refcount increment before queueing.
Likely exposure
Exposure is limited to systems running affected Linux kernel builds that include the vulnerable QRTR/MHI code path. The bundle lists Linux kernel 5.8-era affected code and stable fixes associated with 5.10.35, 5.11.19, 5.12.2, and 5.13. Distro backports must be verified.
Exploitation context
The CVSS vector is local, low complexity, no privileges, and no user interaction. The provided KEV field is false, and the bundle contains no evidence of active exploitation. Treat this as serious kernel risk where untrusted local code can run.
Researcher notes
Focus validation on kernel provenance, stable commit inclusion, and whether the QRTR/MHI path is built and reachable. The source bundle gives root cause and fix direction, but not exploitability details, affected distributions, or operational mitigations beyond applying fixed kernel code.
Mitigation direction
Upgrade to a kernel containing the referenced stable fixes.
Check Linux vendor or distribution advisories for backported fixed packages.
Prioritize shared systems where untrusted local users or workloads run.
If patching is delayed, reduce local code execution exposure where practical.
Validation and detection
Inventory Linux kernel versions across servers, endpoints, and images.
Confirm whether vendor kernels include the referenced stable commits or equivalent backports.
Identify systems using kernel builds with QRTR/MHI support enabled.
Run regression testing before production kernel rollout.
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.
cwe · low confidence lookup
CWE-416: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
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.
1CVSS vectors
3Timeline events
2ADP providers
5Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-416 · source CWE mapping
Use After Free
Use After Free represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.