Kernel memory corruption via unlocked driver override read
Published May 6, 2026 · Updated May 6, 2026
Use-after-free in the rpmsg core of the Linux Kernel allows local users to disclose or corrupt kernel memory through concurrent sysfs access. In drivers/rpmsg/rpmsg_core.c, driver_override_show() reads the override string without device_lock while the store path can replace and free it. An rpmsg device and write access to its driver_override attribute are required; winning the race exposes stale kernel data, corrupts memory, or triggers a kernel oops or panic.
Summary
What happened
Use-after-free in the rpmsg core of the Linux Kernel allows local users to disclose or corrupt kernel memory through concurrent sysfs access. In drivers/rpmsg/rpmsg_core.c, driver_override_show() reads the override string without device_lock while the store path can replace and free it. An rpmsg device and write access to its driver_override attribute are required; winning the race exposes stale kernel data, corrupts memory, or triggers a kernel oops or panic.
The record
- CVE
- CVE-2025-71274
- Published
- May 6, 2026
- Updated
- May 6, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-416, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 6, 2026CVE publishedPublication date reported by the CVE source.
- May 6, 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=39e47767ec9b22f844c2a07c9d329256960d4021 <2e4a70f3c30910427e5ea848b799066d67b963d5
- Affected versionversion=39e47767ec9b22f844c2a07c9d329256960d4021 <392c6b68334aa0e0ae9aba95c0a366bcb0d92f5d
- Affected versionversion=39e47767ec9b22f844c2a07c9d329256960d4021 <42023d4b6d2661a40ee2dcf7e1a3528a35c638ca
- Affected versionversion=39e47767ec9b22f844c2a07c9d329256960d4021 <47615557447185917afa432b7958f87583c417cb
- Affected versionversion=39e47767ec9b22f844c2a07c9d329256960d4021 <7654e6e3cd6bdee9602f6063b3c670bd556d7e61
- Affected versionversion=39e47767ec9b22f844c2a07c9d329256960d4021 <90c8353f471821d7ccd4fe573a2402e056192494
- Affected versionversion=39e47767ec9b22f844c2a07c9d329256960d4021 <954557957177c3c13d7c655976665b1170da5e50
- Affected versionversion=39e47767ec9b22f844c2a07c9d329256960d4021 <d66b8074c555e8abb0ae19eea1c9f3635498bdde
- Affected versionversion=4.18
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