PatchSiren cyber security CVE debrief
CVE-2026-46047 Linux CVE debrief
A use-after-free vulnerability exists in the Linux kernel's Qualcomm IPC Router (QRTR) namespace driver. The flaw occurs in the driver's remove callback, where a race condition between packet arrival and workqueue destruction can lead to memory corruption. Specifically, if a packet arrives after `destroy_workqueue()` is called but before `sock_release()` completes, the `qrtr_ns_data_ready()` callback attempts to queue work on the destroyed workqueue, dereferencing freed memory. The fix involves saving the default `sk_data_ready` callback during initialization and restoring it at the start of the remove callback, ensuring that packet arrivals after workqueue destruction do not trigger the vulnerable code path. Additionally, the fix ensures RX threads complete before workqueue destruction to prevent concurrent use of the callback.
- Vendor
- Linux
- Product
- Unknown
- CVSS
- HIGH 7.8
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-05-27
- Original CVE updated
- 2026-06-16
- Advisory published
- 2026-05-27
- Advisory updated
- 2026-06-16
Who should care
Organizations running Linux systems with Qualcomm-based hardware utilizing the QRTR subsystem, particularly embedded and mobile platforms, IoT devices with Qualcomm modems, and telecommunications infrastructure relying on Qualcomm IPC Router services. System administrators maintaining kernel modules that may be dynamically loaded and unloaded should prioritize this fix due to the race condition triggerability during module lifecycle operations.
Technical summary
The vulnerability resides in `net/qrtr/ns.c`, the Qualcomm IPC Router namespace service driver. During module removal, the driver destroys its workqueue via `destroy_workqueue()` before releasing its socket via `sock_release()`. This creates a window where incoming packets can trigger the `qrtr_ns_data_ready()` callback, which attempts to queue work items on the destroyed workqueue. The fix implements a two-part mitigation: (1) saving the original `sk_data_ready` callback pointer during `qrtr_ns_init()` and restoring it at the beginning of the remove callback, preventing any post-destruction packet arrivals from reaching the vulnerable callback; and (2) ensuring RX thread completion before workqueue destruction to eliminate in-flight callback usage. The kernel commits referenced provide backports to multiple stable kernel branches.
Defensive priority
high
Recommended defensive actions
- Apply kernel patches from stable branches when available through distribution security channels
- Monitor vendor security advisories for backported fixes to affected long-term support kernel versions
- Review systems utilizing Qualcomm IPC Router (QRTR) functionality for namespace service exposure
- Prioritize patching on systems where QRTR namespace driver modules may be loaded and unloaded dynamically
- Validate kernel build configurations to ensure QRTR_NS is either disabled or patched on affected systems
Evidence notes
Vulnerability description sourced from official CVE record and NVD entry. Fix commits identified in kernel.org stable tree. No CVSS score or severity assigned by NVD at time of publication (status: Awaiting Analysis). Vendor attribution marked as low confidence requiring review based on reference domain analysis.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-46047 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-46047
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-46047 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-46047
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/0f313eb6a8f6dffa491373cf3afab979fa1c02f4
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/2e127ceb1c415e246076d8e09e23e443a7a2038f
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/7809fea20c9404bfcfa6112ec08d1fe1d3520beb
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/db3c60ec772de30acae92d560dfcc5258e58dbe8
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/f96779e916576e81430ebb326baff6e433fef8ae
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.