CVE-2025-71274: rpmsg: core: fix race in driver_override_show() and use core helper
In the Linux kernel, the following vulnerability has been resolved:
rpmsg: core: fix race in driver_override_show() and use core helper
The driver_override_show function reads the driver_override string
without holding the device_lock. However, the store function modifies
and frees the string while holding the device_lock. This creates a race
condition where the string can be freed by the store function while
being read by the show function, leading to a use-after-free.
To fix this, replace the rpmsg_string_attr macro with explicit show and
store functions. The new driver_override_store uses the standard
driver_set_override helper. Since the introduction of
driver_set_override, the comments in include/linux/rpmsg.h have stated
that this helper must be used to set or clear driver_override, but the
implementation was not updated until now.
Because driver_set_override modifies and frees the string while holding
the device_lock, the new driver_override_show now correctly holds the
device_lock during the read operation to prevent the race.
Additionally, since rpmsg_string_attr has only ever been used for
driver_override, removing the macro simplifies the code.
Security readout for executives and security teams
Plain-English summary
A local user may trigger a timing flaw in Linux’s rpmsg driver configuration handling. One operation can free a configuration string while another operation is reading it, causing use-after-free memory access. The supplied CVSS score is 7.8 because successful exploitation could potentially compromise confidentiality, integrity, and availability, although the bundle provides no evidence of exploitation in the wild.
Executive priority
Prioritize affected multi-user, embedded, or operationally sensitive Linux systems where untrusted local access exists. Treat this as a high-priority patching issue, but not an internet-wide emergency: the documented attack path is local, and no active exploitation is supported by the supplied evidence.
Technical view
The rpmsg driver_override_show function read driver_override without holding device_lock, while the store path could modify and free that string under the lock. Concurrent reads and writes could therefore cause a use-after-free. The fix replaces the specialized macro, uses driver_set_override for updates, and holds device_lock during reads. The CVSS vector indicates local access, low complexity, low privileges, and no user interaction.
Likely exposure
Exposure is limited to Linux systems containing the vulnerable rpmsg implementation where a low-privileged local actor can reach the relevant driver_override interface. The supplied affected-version data is ambiguous and should not be treated as reliable fixed-version boundaries. Confirm exposure through distribution advisories, kernel package changelogs, or presence of the referenced stable fixes.
Exploitation context
The CVSS vector describes a local, low-privileged attack with low complexity and no user interaction. The record is not listed in KEV, and the supplied sources provide no evidence of active exploitation or a public exploit. Practical exploitation may depend on winning the race and the target’s memory behavior; those details are not established here.
Researcher notes
No CWE is assigned in the bundle. The root cause is an unlocked read racing with a locked update and free of driver_override. Eight Linux stable commits are referenced, suggesting branch-specific backports. Researchers should avoid inferring version boundaries from the flattened affected-version list and instead validate commit ancestry or vendor backport status.
Mitigation direction
Apply a vendor kernel update containing the appropriate referenced stable fix.
Reboot into the updated kernel after installation.
If updates are unavailable, request distribution-specific mitigation guidance.
Reduce unnecessary untrusted local account access until remediation is complete.
Validation and detection
Inventory running kernel versions and identify systems using rpmsg functionality.
Check vendor advisories and package changelogs for CVE-2025-71274 coverage.
Verify the running kernel contains an applicable referenced fix or vendor backport.
Confirm systems rebooted successfully into the remediated kernel.
Reassess local-user access to relevant rpmsg driver_override interfaces.
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-2025-71274 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.
1CVSS vectors
3Timeline events
0ADP providers
9Source links
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.