CVE-2025-39715: parisc: Revise gateway LWS calls to probe user read access

Published Sep 5, 2025
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

parisc: Revise gateway LWS calls to probe user read access

We use load and stbys,e instructions to trigger memory reference interruptions without writing to memory. Because of the way read access support is implemented, read access interruptions are only triggered at privilege levels 2 and 3. The kernel and gateway page execute at privilege level 0, so this code never triggers a read access interruption. Thus, it is currently possible for user code to execute a LWS compare and swap operation at an address that is read protected at privilege level 3 (PRIVUSER).

Fix this by probing read access rights at privilege level 3 and branching to lwsfault if access isn't allowed.

Affected Software

8 affected componentsFixes available
Linux Linux kernel
Microsoft azl3 kernel 6.6.96.2-1
Microsoft azl3 kernel 6.6.96.2-2
Linux Linux kernel>=5.17<6.1.149
Linux Linux kernel>=6.2<6.6.103
Linux Linux kernel>=6.7<6.12.44
Linux Linux kernel>=6.13<6.16.4
Debian Debian Linux=11.0

Event History

Sep 5, 2025
CVE Published
via MITRE·05:21 PM
Data Sourced
via MITRE·05:21 PM
Description
Data Sourced
via NVD·06:15 PM
RemedyDescriptionSeverityAffected Software
Sep 7, 2025
Data Sourced
via Microsoft·01:11 AM
DescriptionSeverityWeaknessAffected Software
Updated
via Microsoft·01:11 AM
SeverityAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2025-39715?

CVE-2025-39715 is classified as a moderate severity vulnerability in the Linux kernel.

2

How do I fix CVE-2025-39715?

To fix CVE-2025-39715, update the Linux kernel to the latest version that addresses this vulnerability.

3

What systems are affected by CVE-2025-39715?

CVE-2025-39715 affects various versions of the Linux kernel, particularly those utilizing parisc architecture.

4

What are the potential impacts of CVE-2025-39715?

The potential impacts of CVE-2025-39715 include unauthorized access to memory and possible disruption of system stability.

5

Has CVE-2025-39715 been disclosed publicly?

Yes, CVE-2025-39715 has been publicly disclosed along with its mitigation details.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203