Kernel memory corruption via QRTR RCU race
Published Jun 24, 2026 · Updated Jun 24, 2026
Use-after-free in the QRTR port removal path in Linux Kernel allows local users to corrupt kernel memory through a race. The qrtr_port_remove function calls __sock_put before erasing the socket from qrtr_ports and waiting for the RCU grace period, so concurrent readers can call sock_hold after the reference count reaches zero. The race requires local low-privileged access and concurrent port removal and lookup; exploitation compromises kernel confidentiality, integrity, and availability.
Summary
What happened
Use-after-free in the QRTR port removal path in Linux Kernel allows local users to corrupt kernel memory through a race. The qrtr_port_remove function calls __sock_put before erasing the socket from qrtr_ports and waiting for the RCU grace period, so concurrent readers can call sock_hold after the reference count reaches zero. The race requires local low-privileged access and concurrent port removal and lookup; exploitation compromises kernel confidentiality, integrity, and availability.
The record
- CVE
- CVE-2026-52947
- Published
- Jun 24, 2026
- Updated
- Jun 24, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-416, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 24, 2026CVE publishedPublication date reported by the CVE source.
- Jun 24, 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=4.7
- Affected versionversion=bdabad3e363d825ddf9679dd431cca0b2c30f881 <03bfa95e452e2b6ccd76a332060ae4feaf5ad84d
- Affected versionversion=bdabad3e363d825ddf9679dd431cca0b2c30f881 <2047c2aa0963bb2872fd722300a15bcb441a4c00
- Affected versionversion=bdabad3e363d825ddf9679dd431cca0b2c30f881 <2aa4c12723fe432e623462a3be42a197a128722b
- Affected versionversion=bdabad3e363d825ddf9679dd431cca0b2c30f881 <3b20ec8f31e8a6a6782243f473b0abd3463621df
- Affected versionversion=bdabad3e363d825ddf9679dd431cca0b2c30f881 <474293d90880622fde9d2430fb0165767090f7b3
- Affected versionversion=bdabad3e363d825ddf9679dd431cca0b2c30f881 <7de2d447072be3b1a76793f034432338fc9c494b
- Affected versionversion=bdabad3e363d825ddf9679dd431cca0b2c30f881 <a2171131ecda1ed61a594a1eb715e75fdad0fef5
- Affected versionversion=bdabad3e363d825ddf9679dd431cca0b2c30f881 <ab269990ed58143a92a263be1bee626d82ac03da
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